Thanks Runer leafiness, it makes perfect sense. I changed it to 12, and then I changed it to 64 (which is quite a lot). However, the player just goes on and on to the left.

I think it's because of the comparisons (signed, unsigned), I just used >> and << on all of them, I did it in a sort of random way. Am I doing it wrong?

Hm, it could be optimized but bleh.
How are you handling the keypresses?  And what exactly do you mean by "not really working"?


EDIT: hm ninja'd.  offtopic but how does the ninja notifier thing warn you?

Could someone give me an example of how to store data in a program itself? For example, if I wanted to store the highscore in the program.

Thanks, that looks like what I need. Is there any way to do this in pure Axe, and is there any possibility of a "write-back' function in axe?

So how would that work? Would I get a pointer to the program, then automagically find where the data is, and then edit it? I think that is what you mean, but some example code would be great.

A far simpler way to use write-back is to compile your program for MirageOS or DoorsCS. This will require that the program be run by a shell that allows easy write-back in the form of you simply modifying data in your running program, and the shell will then write any changes back to the original copy.

Yes, but you can still turn writeback off.  I think it's better to force it.

I don't think you should force write-back. If a user has write-back disabled, they probably have it off for a good reason and would be annoyed if your program ignores that they purposely disabled write-back.

True.  I'm just thinking about the user that doesn't know what the writeback option does and then complains about his game not saving because I've been that person before.

Most shells have an option to enable/disable writeback. I forget about ion. Asm() technically has writeback automatically enabled since in order to run it you have to have it unarchived unless you are using zStart or DCS' homerun hook or something like that.