Re: SBBJ v2
Posted: 31 Dec 2018, 17:20
First of all, very impressive! I'm running SBBJ v2.50 on my iMac, and you've done a lot of work. Kudos!
I don't know if you're still working on this . . . or on a v3 . . . or not. But if you were, I thought of a couple of things that might count as improvements, might make the coding more straightforward, might work around some of the _difficulties_ in coding . . . or some combination thereof. For whatever they're worth, here are my thoughts...
UI/Detection
Right now, you ask for “Regions” (1-5) and “Deep Regions” (2-5), which spawns anywhere from three to five boxes (labeled 0-4), the middle three of which now might-or-might-not be deep throat regions. Would it make the programming easier to change the way these boxes get set up? What if Box 0 was renamed “T” and was meant to always represent/delineate the tip of the phallus? Similarly, what if Boxes 1 and 2 were renamed “SH1” and “SH2” and were used to define the mandatory endpoints of each suck. Then, with these three regions being MANDATORY, you could merely ask the user to input how many “Deep Regions” they desired (0-3), and these could spawn boxes labeled “DT1,” “DT2,” and “DT3.” (Or you could move this to “Session/Deep Throat,” as I’ll describe in the next section . . .)
This might make the coding simpler -- particularly when it comes to users who want to utilize the “Head must stay in mouth” option under Session/Suck Options. If they DID want that option, then once Box “T” is turned on, it must remain on else it generates a fail. You could then also have an option for “Must perform full in-and-out” (which would require the sequence “T”-on, “SH1”-on, “SH2”-on, “SH2”-off, “SH1”-off, “T”-off to avoid a fail). The third option could then be, “Doesn’t matter,” and in this case, you wouldn’t have to check for Box “T” at all -- you could just check for “SH1”-on, “SH2”-on, “SH2”-off, “SH1”-off.
Session/Deep Throat
Under “Chances,” might I suggest an alternative for “Reduction per DT Region (%)”? What if you replaced it with (first) a line that said “DT1 Frequency (%)” that was preset to 100% _and could not be changed by the user_, and then two more lines which would be greyed-out until activated by checking radio boxes which would read “DT2 Frequency (%)” and “DT3 Frequency (%).” These two would be preset to 0% but _could_ be changed by the user . . . with whatever the user assigns to these two lower lines coming _out_ of the FIRST line (so it always adds up to 100%). For example -- the user clicks the radio box for the second line and changes it to 20%. The top line updates down to 80%. Now “Random Chance %” still assigns how frequently a deep throat will come up . . . but now the later lines dictate that there will be a 1-in-5 chance of the user needing to trigger “DT2” to pass. If the user decides to bump the second line down to 15% but then check the radio box for the _third_ line and makes that 5%, the top line (while briefly updating to 85%) will still be at 80%, but now there’s a 1-in-20 chance that the user will need to trigger “DT3” to pass.
You could also then use these user inputs instead of the inputs from “UI/Detection.” If the user never checked “Trigger Deep Throat” in “Session/Punishment” and keeps “Random Chance %” at zero in “Session/Deep Throat,” then you’d just need “T,” “SH1,” and “SH2.” If the user _did_ check “Trigger Deep Throat” OR bumped “Random Chance %” to a non-zero value, then you’d have “T,” SH1,” “SH2,” and “DT1.” And filling non-zero values in the other two lines would generate regions “DT2” and “DT3.”
Also -- under “Special Feats,” might I suggest (strictly for the sake of clarity) that you put “Reward for Held DT Past Minimum (per second)” ABOVE the other prompt . . . and then rename that other prompt “Maximum Cap for Held DT Reward”?
As an additional thought -- perhaps if you stopped the suck speed timer when the deep throat hold time minimum threshold gets CROSSED . . . and then start it again when the deep throat ends. This might simultaneously respect the intent of the suck speed timer AND eliminate the conflict that arises by trying to reward a longer DT hold.
Again -- a very impressive effort, particularly as you're not in this for a paycheck or a payday. Please feel free to totally ignore any of my thoughts that you don't find worthwhile.
I don't know if you're still working on this . . . or on a v3 . . . or not. But if you were, I thought of a couple of things that might count as improvements, might make the coding more straightforward, might work around some of the _difficulties_ in coding . . . or some combination thereof. For whatever they're worth, here are my thoughts...
UI/Detection
Right now, you ask for “Regions” (1-5) and “Deep Regions” (2-5), which spawns anywhere from three to five boxes (labeled 0-4), the middle three of which now might-or-might-not be deep throat regions. Would it make the programming easier to change the way these boxes get set up? What if Box 0 was renamed “T” and was meant to always represent/delineate the tip of the phallus? Similarly, what if Boxes 1 and 2 were renamed “SH1” and “SH2” and were used to define the mandatory endpoints of each suck. Then, with these three regions being MANDATORY, you could merely ask the user to input how many “Deep Regions” they desired (0-3), and these could spawn boxes labeled “DT1,” “DT2,” and “DT3.” (Or you could move this to “Session/Deep Throat,” as I’ll describe in the next section . . .)
This might make the coding simpler -- particularly when it comes to users who want to utilize the “Head must stay in mouth” option under Session/Suck Options. If they DID want that option, then once Box “T” is turned on, it must remain on else it generates a fail. You could then also have an option for “Must perform full in-and-out” (which would require the sequence “T”-on, “SH1”-on, “SH2”-on, “SH2”-off, “SH1”-off, “T”-off to avoid a fail). The third option could then be, “Doesn’t matter,” and in this case, you wouldn’t have to check for Box “T” at all -- you could just check for “SH1”-on, “SH2”-on, “SH2”-off, “SH1”-off.
Session/Deep Throat
Under “Chances,” might I suggest an alternative for “Reduction per DT Region (%)”? What if you replaced it with (first) a line that said “DT1 Frequency (%)” that was preset to 100% _and could not be changed by the user_, and then two more lines which would be greyed-out until activated by checking radio boxes which would read “DT2 Frequency (%)” and “DT3 Frequency (%).” These two would be preset to 0% but _could_ be changed by the user . . . with whatever the user assigns to these two lower lines coming _out_ of the FIRST line (so it always adds up to 100%). For example -- the user clicks the radio box for the second line and changes it to 20%. The top line updates down to 80%. Now “Random Chance %” still assigns how frequently a deep throat will come up . . . but now the later lines dictate that there will be a 1-in-5 chance of the user needing to trigger “DT2” to pass. If the user decides to bump the second line down to 15% but then check the radio box for the _third_ line and makes that 5%, the top line (while briefly updating to 85%) will still be at 80%, but now there’s a 1-in-20 chance that the user will need to trigger “DT3” to pass.
You could also then use these user inputs instead of the inputs from “UI/Detection.” If the user never checked “Trigger Deep Throat” in “Session/Punishment” and keeps “Random Chance %” at zero in “Session/Deep Throat,” then you’d just need “T,” “SH1,” and “SH2.” If the user _did_ check “Trigger Deep Throat” OR bumped “Random Chance %” to a non-zero value, then you’d have “T,” SH1,” “SH2,” and “DT1.” And filling non-zero values in the other two lines would generate regions “DT2” and “DT3.”
Also -- under “Special Feats,” might I suggest (strictly for the sake of clarity) that you put “Reward for Held DT Past Minimum (per second)” ABOVE the other prompt . . . and then rename that other prompt “Maximum Cap for Held DT Reward”?
As an additional thought -- perhaps if you stopped the suck speed timer when the deep throat hold time minimum threshold gets CROSSED . . . and then start it again when the deep throat ends. This might simultaneously respect the intent of the suck speed timer AND eliminate the conflict that arises by trying to reward a longer DT hold.
Again -- a very impressive effort, particularly as you're not in this for a paycheck or a payday. Please feel free to totally ignore any of my thoughts that you don't find worthwhile.