What Eiyeron discovered isn't so much of an Axe bug as it is a lack of a feature that Axe really should have. The issue is that, in the process of deleting or recreating an OS variable, other variables in RAM may be shifted. A common instance of this would occur if your program creates a variable, and later deletes or recreates an OS variable that existed before your program started, then the pointer to the variable you originally created would be invalid.

This is not an issue that an Axe user should need to debug/solve. My identification of the issue required a knowledge of assembly and how the OS structures RAM, and my formulation of the proper solution required a knowledge of an OS feature only exposed to assembly programmers. The behavior Eiyeron saw would most certainly appear to be a bug without this knowledge, thus I do not believe that he should be penalized in any way for asking for assistance with a problem that is not his fault.

---

Here is my suggested solution for anyone having this issue. For up to two OS variables that you keep a pointer to for the duration of the program, the OS can automatically update the pointer if it moves. To take advantage of this feature, I would suggest putting the following one or two variable definitions in your program:

ᴇ84EB→°V1
ᴇ84ED→°V2
The names can be whatever you like, they don't have to be V1 and V2. And if you only need to keep track of one OS variable, you only need one of these definitions. In the body of your program, use these variables instead of standard variables to hold pointers to OS variables that you need to keep track of through possible deletions/recreations of other OS variables.

So we can use...

I have no idea where to start I hadn't ever played TRON myself until two days ago.

Deep thought -> http://www.pictogame.com/fr/play/game/HoENt7lZMvsj_flash-tron-20 can give you an idea of what you have to do.
Hayleia -> yes 4000 bytes is short, kindermoumoute decided that.
You are allowed, but if you are not the author of this axiom then you will lose points.
Yeong -> OMG 30 mn It took me at least two days, and I was working only at this

@aeTIos: It was 1.1.2, but it is also prevalent in probably all of the Axe versions since the start.

I have no idea where to start I hadn't ever played TRON myself until two days ago.

Same But I have ideas >.>

Calcs some more?
(Cry some more joke)

I had coffee today because I have to write a paper due tomorrow (I have not had time). So maybe, if I finish early, I will be up all night programming. Sleep deprived programming is the best o.o <--- still my eyes

The Tron AI is actually easy to make and I've finished it 30 minutes after I read the email O.o

wait, what were all the emails with a bunch of tron attachments from noelthebeast? (did you guys get them too?)