Actually, I see a lot of potential for that .org command
That would help me with my data, and this would also allow people to write ramcodes very easily, even ones using absolute jumps.
edit the token used could be the same as #Realloc but with a ^r.

So you'd like to see this command added to Axe ? #Realloc^r being the equivalent of .org 0 ? Why not, it could be very useful... and it's also getting very low level    ! But another token should be used, with an opening parenthesis, to allow reallocating at any address (not only 0).

It doesn't waste anything if I add an constant to another constant, but it does waste if I add a constant to a calculation that doesn't end with a constant addition.

Yes, indeed. But in your case (°CST1-°CST2→°CST3), it only wastes some bytes in the source program.

---

Talking about assembly, Axe Parser could also allow inserting text inside the Asm( command (interpreted as chars, not tokens). Currently, if I want to do this : Asm(..."HELLO!"...), I have to write Asm(...('H')^r('e')^r('l')^r('l')^r('o')^r('!')^r...), which is not very convenient !

Well yeah, I could theoretically rewrite that in assembly and use spasm... but given the size of the file already, you understand why I ask if there's an "easy" solution Actually, I could maybe add the "-°CST1" in my code since it is always the same constant for everyone. It would just waste an addition.And thanks

Yes, of course, I understand ! If your problem can be solved by only writing -°CST1 from times to times, then it's easier. Even though it'd have been better to generate the data in assembly, because you would have been able to define constants and flags with #define, and the data would have been more readable. (The only problem being then to copy by hand all the data generated in assembly into the Axe source.)

Moreover, it shouldn't waste an addition in the compiled program : doing math with constants is parsed by Axe and only the result is put in the compiled program each time you use the constant.

For now, we can do this
[]→°CST
°CST1-°CST2→°CST3

But we can't do this:
[]-°CST1→°CST2

Could this possibility be added ? Basically, I have this file

Spoiler For Spoiler:

*See Hayleia's original message*

And I need to retract a constant to every "[]→", so I don't feel like doing things like
[]→°TEMP
°TEMP-°CST1→°CST2
for each of them

edit Alternatively, is there a way to "compile with .org 0" ?

For the time being, can't you generate the data in assembly (thus allowing you the use of .org 0) and then include it in Axe with the command Asm( ? Otherwise, the possibility of using constants this way is a good idea. By the way, your game looks nice !

This looks cool have you tried making the sprite turn to face the direction its going?

Thank you ! I haven't tried yet, it's on my to-do list. I'll maybe chose to redraw another sprite, symmetrical this time : it should be easier than changing the way the display works. I'll see...

That looks nice so if I understand correctly, that's Axe with bits of ASM in it, and you want to eventually redo it entirely in ASM ?

Thanks ! You're good at finding great games 

Yes, made in Axe, with parts in assembly. I started by writing the game in Axe, and then I added some parts in assembly (such as the code to search level packs through the VAT, the code to load a level and decompress it, etc.). I think I saved 1000 bytes by writing some parts to assembly.

And I'd like to translate the full code in assembly, to save some more bytes. It'll also improve the speed of the game, which is required if I want to add some new features to the game.

Hi, everyone !

Today, after approximately one month of work, I'm pleased to present you BOULDASH, a Boulderdash clone, one of my favorites games. It runs at 6 MHz, uses animated sprites, let you chose between level packs, reads levels (appvars) from archive (without unarchiving), takes less that 4000 bytes, and should be bug-free !

The game's protagonist [...] must dig through caves, [collecting diamonds to unlock the exit], while avoiding [moving creatures] as well as obstacles like falling rocks, and the constant danger of being crushed or trapped by an avalanche, or killed by an underground explosion.

Download here ! To play the game : - use the arrow keys to move - [ENTER] to suicide while playing - [CLEAR] at anytime to quit Working on a level editor... beta version here.

The game is almost finished, and already playable. I'm still working on it : I'd like to port it to assembly, to add a bar at the bottom of the screen with time and diamonds counter, to add new objects, and to change other little things. Once the game finished, I'll probably publish the code source. Currently, it's unreadable : I mixed Axe and assembly (though it's possible to make the game in pure Axe), nothing is commented, and I optimized the code everywhere.

You can ask me any question, tell me what you think of it, and send me ideas of features to add/improve.

What do you mean by "variable" ? Because Memkit, an Axiom that is included in Axe's zip, can already add or remove bytes in an appvar for example.

By "variable", I mean any OS variable : it can be an appvar, a program, etc. It was already possible    ? Then this feature should be added to Axe, it's so useful !