I've been having a bug in making my game for the competition, not seen it before and I can't seem to get rid of it. 'set numeric <gogo; -1>' produces the bug in the log 'ERROR: No such collectable 'gogo; -1'' Then when I try to use the variable it gives 'ERROR: No numeric variable 'gogo' defined.' I searched for 'collectable' in the help files and it returned nothing yet there is a 'collectable variable' listing on the debug menu on quest, which contains nothing during my game.

Any ideas?

Works for me - what asl-version are you using? Could you send me the whole ASL file, or at least enough of it for me to reproduce the problem?

XD I found the bug just after uploading it to give you... 'asl-version <30>' Silly me... Sorry Alex.

I get something similar - but it actually does set the variable/flag.

ERROR:

INTERNAL ERROR: 35601 - 'Element not found' occurred processing script line 'set string <T.CLASSIC.VERSION; 0.6>'

Attached are the two files.
.. or at least the second file WOULD be attached if I *COULD* attach it.
*sigh* renamed it to .asl extension.

You can change T.CLASSIC.VERSION to t.classic.version. If even one letter is capitalized the error persists. (Well, I didn't check all the combinations: I tried t.CLASSIC.VERSION and t.classic.versioN; both failed, and I made an assumption.)

I had that problem when pulling in something I'd written in a previous ASL version (3.53 I think) to 4.0x. Again, it was because of capitalization. But when I write anything from scratch in 4.0x, capitalization doesn't cause a problem. Not sure how that is even possible.

Actually, none of my string variables are capitalized! So disregard my last comment about capitilized string variables working - they don't. (I *knew* that was impossible.) Numeric variables can be capitalized.

The other thing is that even though you get this error, the capitalized string variables are still set to their proper values, and can be referenced without error in the rest of the script. But they show up value-less in the 'String Variables' list via the run-time debug menu.

There is a bug with capitalised variable names in the current version, which is fixed in version 4.0.5 (I'm slightly changing the version numbering convention by the way)

Oh right - I didn't check the string variables list (since I was running a command and getting the correct output).

I was thinking about loosing the capitalization but it didn't look right to me.
I thought the caps bug was fixed in the last update, since it actually output stuff, and didn't crash for me.

Cheers for the info fellas.