Cool

Thanks, but I don't know how many moves I'll have yet.  It very well could reach 60 or 70.  I havn't coded the moves yet, just the code to execute the moves.
I think this explains it better: 7 (Spots you, the ncp, or the enemies could be) * 7 (Different types of moves) = 49.

Different types of moves can be something like this: (This is when it's your turn)
E E E   You NCP
O O O    O    O
O O O
         O    O
    O
         O
X X X
         X    X
The 'O's mean everyone is effected, while the 'X's mean you get to pick one of these to be effected.
This is even more complex, due to the fact that sometimes you have  NCP partner, and sometimes you don't.  Also, the number of enemies can fluctuate between 1 and 5.  This is why progress is slow.

Oh lol just noticed that in his post

And yeah it means both non-playable characters and non-player characters

I've been trying to decide this for the past week:
I don't know how to store move data.  Here are my options:
1: Have 3 lists- Power, Accuracy, and Stamina
2: Have 2 lists- Power, and Accuracy/Stamina (compressed)
3: Have 1 list- All compressed into one element.

Which do you guys reccommend?
Remember: The more compressed the least size, and the least speed.

I'm talking about storing the move data, not the enemy data.  They're pretty close, so I can see how they could be mixed up.

Well, IMHO Speed is #1 bra. Depends on how much data you have also, and if it'll be worth your time and the amount of space it saves.

Speed indeed is always my number 1 priority IMHO, especially in a language as slow as basic. 

...That being said, if you need to use so much memory you get memory errors, it might be time to compress.

500 is fine I think. If the total for the save files gets in the 2000s, then you can always use some compression for save files or abuse programs like XCOPY