> > This means when it displays the ending, you still have options that are availible from the start...
>
> Yes, that's one of the problems. But if there is interest in this approach, I may be able to make a "suppress constant options" command for this. For that matter, a "suppress inventory" command is just as feasible.

Heh. Personally, this has all been purely academic really, at the moment I have no intention do this. Maybe in my next (assuming there is one) game...

> This example doesn't handle the case where the player attempts one ending more than once. This can be handled in the "ending" location with one global per ending, but it's probably better handled in the locations that *lead* to the "ending" location. That way you can use their state variables instead and disallow their respective "win" options from becoming available after they've been selected once.

Hmm, there's no reason why you have to disallow their win options. Just have the counter for v99 at the location itself. Like:

c s=0
_____ * 1a Win Via Path 1.
__________ v 1 = 1
__________ v 99 + 1
__________ s + 1
__________ g ending

c s=1
_____ * 1b Win Via Path 1.
__________ v 1 = 1
__________ g ending

And the same thing for location 2, of course with v 1 = 2 instead of v 1 = 1. And the ending file has all "v 99 + 1" lines removed.

This way you can see an ending you've seen more than once, as it will only change v99 the first time you see it. It's more or less the same, but I think this is a little bit better (as it wouldn't make sense for the ending to no longer be around if you _undid_ it).