Yes and no. The pokemon sprites were already part of the game, 17k, as were the names, which was another 1300 bytes or so. The hurt was the 1k of weight and height data, and the 14k or so of text for the pokedex entries.

Thanks, I tried to make sure that it was at its fastest, I am sure there are things that can be done to it to make it faster, but not truly important now, just got to make the entire game work first. In the end, the 83+ won't be able to play this game anyways.

all the sprite data is in the form of hacked hex, basically, and displayed using a special program from benryves to recognize my special character I use.

As to 84+, it is something we shall see pending how much memory I end up using. *shrugs* I have no real idea at this time, only thing I can promise is that it will be on the SE calcs.

Aaah ok I see, thanks for the info ^^

Not too bad so far, considering it's Pokémon in TI-BASIC with few ASM used.

I would guestimate it being around 15%? give or take, it's really hard to tell with the scope and complexity that this game represents.

I am contemplating making the events list be based in an app var, due to memory reasons. A 150 element list takes up roughly 1500 bytes while a program with around 150 '0s' takes up around 300 bytes. Kind of a no brainer in that regard, and I can read the data from the appvar from flash, and only have to unarchive it occasionally, instead of like a list and having it in RAM to read.

Not sure I want to do this with the pokedex yet or not. It could potentially slow down the program significantly since it has to call for each instance of the name showing up. The event setup wouldn't be a massive blow on speed, since it gets called every once in a while.

Just some more idle contemplations on my part I guess, to help lower memory usage.

Thoughts?