I was joking because he used a big word
I guess the "speak English" thing is only an English idiom ^^;

But anyway, I'm still thinking out how to do the Samus engine. I'm starting to see how I could handle the 8x16 sprite. I don't think that's much of an issue. The real issue is still jumping. I could use an 8x16 sprite for jumping but that would mean no spin jumping. If I stuck to spin jumping, I'd have an 8x8 sprite but then I wouldn't know how to rig that into the engine.

I meant KBs accessible by normal means, not KBs total. Whoops.

Anyway, yeah, we aren't sure but with a such a smaller chip, it seems likely to me (but who am I to doubt an integrated circuit by its size?)

[edit] Doesn't it kind of make sense though? The TI-OS doesn't USE the full 128KB of RAM. The only way to do so is to code your own application that does which is a feat that not any average Joe Shmoe can do. Seems logical TI would try to cut back on costs by replacing the TA3 chip with a cheaper and smaller TA1 chip (which could simply only have 64KB of RAM, 48 accessible due to configuration?)

Interesting theory you have going there. I'm glad we've got a solid line of reasoning going for this issue.

Oh, and for the record, my calc's serial number is S-0704 and the ASM write test program gave an okay.

Yup, you can have pretty much as many conditions as you want in an If or While.
Glad I helped some

Very nice
As for spells, you should totally have a "rickroll" spell
J/k, my honest suggestion would be to go with some of the RPG staples like "Cure" and "Fire" as starting spells then progress to stronger and more unique spells like "HolyAura" and "Inferno" rather than the 1-10 level up thing. While this may not be easier, isn't it more satisfying to cast "DracoInferno" (Dragon Inferno) on your enemy instead of Fire10 or something?

Anywho, can't wait to see what you come up with

I was trying to replicate the morphball's look in all of the 2-D metroid games where it constantly rotates even when not moving.

I have been working with Builderboy on (read: Builderboy has been gratuitously showing me how to build) a physics/movement engine for Return to Maridia.

This is going to be fairly complex. As of now I have plans to use 2 separate engines: one for Samus (an 8x16 sprite) and one for her morph ball (an 8x8 sprite). Thanks to Builderboy, the 8x8 sprite engine is mostly done. From there I will be perfecting the engine to my tastes and extrapolating from it to create the 8x16 sprite one. Then comes the issue of tying both together and adding map and interaction bits to it.

Fun, neh?

Oh, and here's a screeny of the morphball engine as it is so far (which also shows off 2 of the game's power-ups )

Note: the screenie is probably half as fast as the actual engine

Nice! Sounds familiar kind of. I like it a lot