small update: All data/progress made yesterday that was lost was recovered yesterday in about 20 minutes . Due to some progress on the enemy generation formulas, I didn't manage to recover the full 1.6 kb that I talked about earlier. The battle engine currently sits at 9249 bytes though (as opposed to the original size of 10500 bytes)

O.o if it stays like that after clear the only possible explanation I could think of is that you have A LOT of programs and appvars on your calc or something... names of programs/appvars take up a small amount of memory, even if they're in archive. Hidden MOS/DCS programs take up even more space. For me, after RAM clear I only have ~22900 free because of all of my progs/appvars (I'd say I easily have >100 combined )

oh and also, I think you can't run MOS programs from archive if you don't have enough free RAM to house it.

ROMs are illegal to distribute since they're copyrighted, so you have to go download them illegally yourself rip them from your own cartridges

lost the battle engine main program in a bad crash today....

fortunately I have a day old backup, and I didn't lose all the progress today since a lot of it are in external subprograms.

The battle engine (once I recode what I finished today) will be 1600 bytes lighter

Oh cool, thanks. So I'm guessing that the lack of an argument inside the {} is because it is taking HL as its argument, which is 'pointer' because when you store pointer to r2 it is stored to HL....like ans....kk i'm learning

Does every Axe operation leave stuff in HL?

Woooo text parser thing is going great. Basically, I'm writing a sort of parser that reads NPC data and interprets it as code (key words: sort of). This will save a lot of space both in the executable and in the NPC data appvar (I hope)

Currently can : read/display text. wait for input before advancing, ask the player yes/no and write to conversation flags (thanks Hot_Dog, Runer112 and nemo!)

This is the data used in the screenie:
"Hi. This is text. Pressa key now " [07] "Do you like cheese?" [01][02] " Awesome" [04][03] " Why not?"[04][07][14 0207][02]"DONT TALK TO ME"[16 0207][04][03]"I TOLD YOU TO STOP BOTHERING ME"[04][00]


The commands I have right now are
[07] pause
[01] yes/no box returns 0 for yes and 1 for no stored to A
[14] check bit specified by the next two bytes: the first byte is the pointer to the byte + L4, the second is the bit#. Returns 0 or 1 stored to A
[16] write to bit, same syntax as [14]
[02] Effectively, it's If A=0
[03] If A=1
[04] End
[00] End conversation

Planned commands will be a newline command, a print player name command, initiate battle, and give item.

With this method, I can/will be able to have about 200 unique NPC conversations, averaging 100 bytes in length (about 4 lines of text)

Runer: Thanks, but I need a routine that will take the pointer and bit # as arguments, so I think Hot_Dog's {Pointer} or %00000100 will be sufficient

Hot_Dog; I'm using the bits as flags to show whether the player has completed a certain task or not, so I guess they need to be constant.

So I'm going to go with, if you were going to write it as a subroutine with r1 being the pointer and r2 being the bit number (in Axe's way, with 0 being the most significant), the best way to do this is {r1} or e^(7-r2)→{r1}

Or is it more efficient to write it out every time? (no subroutine calling) just tested it, I think subroutine is better (9 bytes per call I think) and I think the code is ~41 bytes