Monday, November 23, 2015

Options

So, here's what the sex encounter template code looks like:

(if: $partnerPleasure >= $partnerThreshold)[(goto: "Orgasm")](if: $pPleasure <= $pleasureThreshold)[(set: $skill1 to "Normal")(set: $skill2 to "Intimate")(display: "intercourseCalc")(display: "Menu")(set: $maxPassage to 3)(display: "randomPass")
(if: $randomPassage is 1)[](if: $randomPassage is 2)[](if: $randomPassage is 3)[]
(set: $maxPassage to 3)(display: "randomPass")
(if: $randomPassage is 1)[](if: $randomPassage is 2)[](if: $randomPassage is 3)[] (if: $partnerPleasure <= $partnerThreshold * .33)[](if: $partnerPleasure > ($partnerThreshold * .33) and < ($partnerThreshold * .66))[](if: $partnerPleasure >= ($partnerThreshold * .66)) (if: $pPleasure < ($pleasureThreshold * .33))[](if: $pPleasure >= ($pleasureThreshold * .33) and < ($pleasureThreshold * .66))[](if: $pPleasure >= ($pleasureThreshold * .66))[]

(link: "1")[(goto: "1")]
(link: "2")[(goto: "2")]
(link: "3")[(goto: "3")]
](else:)[(goto: "Orgasm")]

And between every one of those [ ] brackets, I have to put in roughly one paragraph. There would be 3 pages of these for one sexual position and that's not including any special variations. And then imagine that during the first 5 hours, from 7am to 12pm, there is the possibility for 3-4 sex scenes for Kevin-Judy and probably another 3-4 in the afternoon and 3-4 in the evening. Variations and specific player choices need to be accounted for, such as whether you're wearing a condom or not, whether your mother's wearing a towel and whatever else could change up the day... all in all, it's compounding and pretty crazy. All of that with consideration that besides the basic structure of the last story, it all needs to be newly written AND coded.

Putting the code down in a regular text editor is out of the question because it would look like a jumbled mess (see above). I can't even space things properly because Twine recognizes a line break in code as a line break in text, so in order to make it so that the text doesn't start in the bottom or middle of the page, I'll have to keep things like this. I suspect that there will be a lot more typos in this upcoming version and will most likely set up a separate blogspot page to take in debug and typo fixes. I still do not know how much longer it will take, but I'll try my darnedest to get it finish ASAP. I know there's really no time frame, but I'd rather do it sooner than later.

4 comments:

  1. Looks like is getting really quite complex now huh, seems you've really got your work cut out for you, also from what I understood from what you said is that you want to make a break in the coding for the sake of formatting and making it easier to read correct? Not sure if this page will help you at all: http://twinery.org/wiki/syntax

    From what I've read and it is a similar code C# is that
    should be what you're looking for, it is the webpage toward the bottom with a definition if it helps at all.

    ReplyDelete
  2. Okay so apparently that command works on this site, what I was trying to say is < br >, just take out the spaces on that tag.

    ReplyDelete
  3. I recommend chatting with the dev for Free Cities since he's also doing Twine, although likely a different version than you, but you might be able to learn some stuff from him.

    ReplyDelete
  4. The coding isn't really a problem, it's just a lot more time consuming than I thought it'd be because of the variations, re-writing and coding 3-punch combo. Someone asked if it would be easier doing it from one perspective before the other. I'll answer it here, that that's not really the case anymore because gender only acts as a content barrier. Yes, it's extra coding, but I'd rather have both male and female choices being written at the same time than doing completely male and coming back for female. Organization isn't THAT bad, it's just an annoyance to account for. The typo's are the real problem, but they're small fries in the long run.

    ReplyDelete