Oh, hell! SG and SetGlobal aren't the same

[temnix]

I've been struggling to get my dialogue to work, where I need to set a global and check it a few states later. No matter what I did, though, the global change simply wouldn't register until the end of the conversation. Then it occured to me to write Global("G","GLOBAL",0) and SetGlobal("G","GLOBAL",1) instead of the convenient shortcuts - G("G",0) and SG("G",1). And what do you know, it started working right away! I don't know if the problem is with G or SG, but the old format succeeds where the shorthand fails.

Edited April 17, 2021 by temnix

[argent77]

SetGlobal() and SG() are different script actions.

Only actions listed in INSTANT.IDS are executed within dialog states by the engine. Everything else is added to the action queue and executed only when the dialog ends. SetGlobal() is listed, SG() is not.

[temnix]

How nice would it be to have this little detail in the Gibberlings' Actions guide!

[argent77]

It's mentioned in the IESDP (if you know what you're looking for).

[temnix]

That's pretty funny. I can find it, if I know where to look. That ought to help me the next time I misplace my apartment keys.

[jastey]

9 hours ago, temnix said:

That ought to help me the next time I misplace my apartment keys.

And even with these, searching for them if you do not know where to look will not help you at all, hmm?

[subtledoctor]

Oh, this guy doesn’t do search. It’s beneath him apparently. 

Edited April 18, 2021 by subtledoctor

[temnix]

You are full of shit, as always. Here are the two facts about the matter: 1) the actions are different; 2) the entries in the Actions section of the guide say nothing about the difference.