Hey tifreak, how goes Pokemon Purple?

I'm making slow bouts of progress, working out the code to switch pokemon around in battles.

Haha, yeah, like that's going to happen :p

So, some good news. I've gotten through the code for ZPP and I've managed to figure out where to insert the code for switching out pokemon in battle and have even managed to get a bit written down on paper, code wise. I don't seem to have the code written out for ZMISC, which houses the code for the stats screen, so I need to deal with that yet so I can make sure there are no conflictions within that code and ZPP for the switch out. Once the stats bit is done, then I just have to write the switch out code, which will constitute storing the important date from L_1 to the correct LP# depending on the first active slot in L_PRTY. Then from that point, I pull the next slot over and dump that into L_1, then bring back the battle screen, erase the pokemon and HP data, then redraw it, then allow the enemy to attack. (For testing purposes, I'm just going to have 'Enemy attacks!' and might even have it deal 1 pt of damage to try to work out the hp bar going down.)

I actually just had an idea to that end as well. First I calculate the length of that line, and store that to a variable. Then I calculate the damage and recalculate the line the length. Then it's just a matter of using the Line(#,#,#,#,0 with the two values obtained, should allow to subtract the damage part of the hp bar without needing to clear it out and re-rendering it.

I can't even really warrant a guess on how many programs, though I will be moving a bit of them into appvars when I can start dropping map data over into them. As to size, I wouldn't be surprised if this broke 250kb. It's already over 100k as it stands, without taking into account variables and lists.

Thanks. I am pretty stringent on testing for bugs as I add each new thing to make sure it all works, but I am always capable of missing things :p

It's pure basic, but uses xcopy(or celtic II, I don't remember) for copying data back and forth and a small asm hex sprite utility written by Ben Ryves for one part of the game.

*Edit* It might be 15 mhz only simply because those calcs, have more storage space.