Zugg Software :: View topic - [3.30 pro] Async(?) GMCP processing causing variable population problems

Novice Joined: 23 Jun 2005 Posts: 32

Bug:

GMCP processing seems to be async, so variables calling %gmcp without eval returns 1 rather than the value.

Reproduction:

Take the following code:

Posted: Sun Oct 03, 2010 7:33 pm

No, you shouldn't be using %eval.

How is your @CurHealth variable being initialized in your session? You realize that it will normally save this variable across sessions so unless you are setting it in some other script, that might be causing the problem. You need some way of determining the first time your trigger fires so that it can initialize these variables properly.

I have no idea why %eval is making any difference, but it is definitely not something I recommend using in the GMCP trigger since %eval causes the entire compiler and parser to be executed which is slow, so it can lag your session.

Novice Joined: 23 Jun 2005 Posts: 32

1. I actually had the variables set before I created the script. I didn't include the definitions in the code because the trigger would create them on its own.
2. I had no other sessions/windows open. I closed cmud, opened it, escape, file, connect, achaea.com 23, login, open settings, paste. Look around a bit, walk around a few rooms, come back, check variables.
3. This is NOT something that happens the first time the triggers fire. I can see uninitialized vars being a problem, but these are filled EVERY PROMPT.

Below is the definition for my vars: