Castle Paradox

Bagne · Last edited by Bagne on Fri Dec 04, 2009 10:56 am; edited 1 time in total

Ok, I've got a "write global" command that isn't working. This is really weird, so brace yourselves.

I was debugging a script with the "show value" command. I narrowed the problem down to a single line - the middle one shown here:

TMC · Posted: Thu Dec 03, 2009 8:49 pm Post subject:

I hope you are using at least Xocolatl+2, because of this bugfix in X+2:

Bagne · Posted: Thu Dec 03, 2009 9:13 pm Post subject:

I'm using the nightly.
I'm also using high ID globals (3000 - 4000ish) for other stuff, and they're working fine.

This is what I did:

ShakeyAir · Joined: 27 Apr 2004 Posts: 93

i have had random issues with global variable 0. i got a couple of errors while working on tetris when i had my array start at global variable ID 0. i just assumed it was causing some odd computation somewhere. i switched to starting the array at global ID 1, and honestly, in every subsequent script, i just havent made a global variable 0.

TMC · Posted: Thu Dec 03, 2009 9:46 pm Post subject:

Yes, I'm guessing that you are accidentally overwriting the value of global variable 0 somewhere. It could be because 0 is usually returned from script commands when an error occurs, so there might be unintended 0's flying about.

You can check the values of all global variables in the script debugger if you want to (without having to comprehend the rest of debugger). Press F10 twice, then V twice. Scroll up and down with + and -.

'@global variable name' is the id number of a global variable - it's a constant automatically created for you.
_________________
"It is so great it is insanely great."

Bagne · Posted: Fri Dec 04, 2009 4:58 am Post subject:

Ok, well I have quarantined a copy of my .rpg file in case anyone wants to see it (now or in the future).

I don't know if the "zeros flying about" was meant for me or ShakeyAir or both -
If meant for me, I don't see how this could apply in my case. The code I initially posted was verbatim. Nothing happens between the "write global" and the "show value". There are no functions being called or anything.

Also, following your instructions, I can see the global's state in the debugger, and it's clear that when I start my game, the "write global" doesn't work the first time my script is called. After that, it's fine.

Should I report this, or is it too vague?
_________________
Working on rain and cloud formation

TMC · Posted: Fri Dec 04, 2009 8:04 am Post subject:

Was directed at both of you. I meant that perhaps WaddiSwitch is accidentally getting set to 0 sometime between the 'beginning' script and that one.

You can email me a copy of your game and scripts if you want, and I'm sure I'll be able to tell you what's going on within a couple minutes.
_________________
"It is so great it is insanely great."

Bagne · Posted: Fri Dec 04, 2009 10:52 am Post subject:

Ooooh. I see.
You're right, that's exactly what happened.
When you start the game, WaddiSwitch is set to 1, and then some obsolete code set it back to 0 :-(

Man - that's so confusing! I was accidentally looking at two globals (ID 0 and ID 1) and not one ... and it's entirely by coincidence that WaddiSwitch should get reset to the proper value when it's first used.

Thanks.

Shoot - I wanted to show you my game :-P
I was getting excited at the idea of someone else playing it.
Maybe I should just post it, despite the fact that it only so far contains vague puzzles with unidentified objectives.
_________________
Working on rain and cloud formation