Most people code on calc, because there would be no purpose to coding on an emulator. It would be slower having to use a mouse to click the keys, or if using a keyboard it would seem weird because the keys are mapped way differently. Also, the only reason most people test on an emulator is if they are testing an ASM program so in the event of a crash they dont damage their calculator. Coding on calc also gives you the advantage of being able to test instantly. As Kevin said you can write BASIC on a PC, but the only good editor is the one that was distributed with TI's old graphlink (as far as I know anyways). That software is rather hard to find though these days, unless you know someone that has a copy lying around.

Wow, I know nothing of starcraft, so half of your post was latin to me . But yea I know what ya mean, I thought I was da shiznit, but apparantley not . It's still fun to play online though even with the skill gap. Besides, I'm working on getting better so soon I will PWN them all MUAHAHAH even Isai (yea........................ right)

Different card rarities now exist in this game . Here are the different rarities and the probability that you will pull one (from a card pack);
Common 75%
Uncommon 20%
Rare 5%
Also, here are the number of each type of rarity per set;(which also happens to follow the same ratio)
60 card set:
45 common cards per set
12 uncommon cards per set
3 rare cards per set.

The save/load deck system is more or less complete. I have been running some numbers to determine what kind of space this game is going to take up, and here's what i've come up with so far.
3 Starter decks (60 cards each) and 6 60 card expansion sets 4872 bytes
Current Deck list:                                                                7571 bytes
Pictures for all the cards (540 cards, 32b apiece at 16x16 size)17280 bytes
Game text for card names and card effects:                           38880 bytes
Total:                                                                                 68603 bytes
As you can see, it gets fairly large, and this is without the actual program, which as of now i have no idea how big it will be. I'd really like to find a way to shrink this somehow, as most of the space is taken up by graphics and text. On another note, it seems that I will be able to allow the user to save multiple decks (I'm thinking 3 at max) without to much hassle or without taking up too much space. So what do you guys think? I'm open to suggestions.

Hey, that's great news. Most people I know were kinda upset at the thought of Ness not being in the new game. Jigglypuff returning to smash is good news as well. Now if the could just hurry up and release the new game...

Eh, who really knows? Someone with to much time on their hands no doubt. Methinks Kevin's new project is ROL4  ^_^ :O  ^_^

Alright, thanks alot, I will defintley check out the seq( funciton. It looks like this method may be faster and should save space as well. What is the value of B in the above example?

could you post some sample code? I'm not exactly sure what you mean. I could see doing it like this:(off the top of my head)
0.12345678->A
1->dim L1
1->C
For I,1,8
AC->B
B->L1(dimL1)
1+dimL1->dim L1
ipart(A-A->A
10C->C
End
I'm unfamilar with the seq( command also, so I dont know how it works.