I am working on my first ChoiceScript game, and so far it’s going well. I have learned the basics of the language, and I feel comfortable with it. I am curious about the best/most efficient way to program the following scene type though, since choices/scenes like this are going to be pretty common…

I personally going for the conventional way, the first method. This way, I still have a total control of what will be said by both A&B characters, giving them distinct personality. Of course, coding the first method is a hella nightmare, but it’s much easier to read than coding the third one; I’m o…

The control flow doesn’t reduce the use of labels in *if. What they does is removing the *goto requirements on every #options, which in turn eliminate the consequent *labels.

Implicit control flow also prevents the requirement of *gotos in *if statements.

Even without implicit control flow, *if statements don’t need a *goto (unless you’re using *else, or want them to take the reader somewhere other than the next line). My game is peppered with *goto-free *ifs. Edit: though many of them will be multi-replace functions in Game 2. That’s another option…

I usually prefer labels, as I make less of a mess using them. If statements are prone to all sorts of bugs and errors, at least for me, so labels it is.

Sounds a gosub routine to fetch the character details might prove helpful. If you’ve got more than two pairs of characters. If you’re text flavour is different multireplace is probably your tidiest best. If you’re changes are a lot heavier you’ll need to move towards if/goto special labels/scenes.

[image] EclecticEccentric: implicit control flow can be used to prevent massive numbers of labels Very helpful! Thanks :slight_smile: [image] Havenstone: *if statements don’t need a *goto (unless you’re using *else, or want them to take the reader somewhere other than the next line). M…

Gosub permit youto use *return into your code. With this you can gosub to a “character B” specific scene/test/routine that do stuff and then *return to your previous scene thus averting a break in your game flux. Another feature I love in gosub is that any *temp variable you declared will work norm…

I recommend using multireplace for small stuff that isn’t worth creating variables for. Minor dialogue changes or differences in reaction. Etc.

Best Way to Code Differentiated Scenes

Game Development ChoiceScript Help

EclecticEccentric August 27, 2018, 8:18am 3

It might be worthwhile to not that implicit control flow can be used to prevent massive numbers of labels in *if statements.

Topic		Replies	Views
Separate scenes for every choice? ChoiceScript Help	7	2099	October 11, 2015
Help! I've written myself into a corner ChoiceScript Help	14	1898	November 4, 2014
Lateral Scenes? ChoiceScript Help	9	1038	February 11, 2018
Falling out of a choice statement ChoiceScript Help	9	447	May 30, 2024
Strange skipping over scenes ChoiceScript Help	19	978	September 18, 2021

Best Way to Code Differentiated Scenes

Related topics