Reply to Re: I thought I knew what this thread was about...
If you don't have an account, just leave the password field blank.
: At first, I thought I knew what this thread was about, and the solution to the problem. But given the answers to it, I'm now confused.
: My advice was to simply change the name of the variable &magic to something else. I had something similar, but different in BFTG. Sphinx had made the global variable called &map. I had script with the local variable, &map_number. Every time I would run that script, &map_number would always call &map instead. So, to fix the problem, I just changed the name of the local variable to something else. The script then worked fine.
The engine really messes up local variables with names like a glabal var with a suffix (e.g. local &goldkey will not work properly because of the global &gold). This is not the case if both vars are globals (not sure about both locals, though)
: My advice was to simply change the name of the variable &magic to something else. I had something similar, but different in BFTG. Sphinx had made the global variable called &map. I had script with the local variable, &map_number. Every time I would run that script, &map_number would always call &map instead. So, to fix the problem, I just changed the name of the local variable to something else. The script then worked fine.
The engine really messes up local variables with names like a glabal var with a suffix (e.g. local &goldkey will not work properly because of the global &gold). This is not the case if both vars are globals (not sure about both locals, though)
