Still a problem with dialogs (SOLVED)

[Hans]

My last topic was locked. But I'm still wondering why my dialog script doesn't work!

The code is:

@S  // dialog startup entry point
@1  // option 1
Ego: Nope...
option-off 1
option-on 2
stop
@2  // option 2
Ego: I don't think so.
option-off 2
option-on 1
stop

Why doesn't it start option 2 the second time?

[Ashen]

Try putting 'return' after the @S. I think it's running the first bit of available code when you start the dialog again, even though option 1 is technically turned off.

However, if this is all you've using the dialog for, why not just use variables and script it? (Or even use SSH's MultiResponse module.)

I locked the original topic because the question you asked was covered in the manual. This is a different question, so I'll leave them as seperate threads.

[Hans]

That's it! 
That's exactly it!

**--__--** ((TOPIC LOVED)) **--__--**

[Khris]

Just for future reference:
The script doesn't care if an option is on or off; "@1", "@2" aso., just like "@S", are just entry points, i.e. the script will run from those points until it encounters return or stop, regardless whether the options of the encountered @X-lines are on or off.

Turning options on or off will only affect whether they are displayed on the GUI or not.

So, like Ashen said, it's usually necessary to put a return before "@1".