UPDATE: 0.6.1!

Here's the new code.

EDIT: And here's what's new about it!

• Two new specials: the Flip and the Tower of EIT
• You can now beat the CPU! A gauge on the far right indicates how long the computer has left
• *Attempted* to let you see the opponent's grid height in multiplayer
• Some new optimizations to make the code faster

There are still a few bugs, like the random crashing bug in DCS and strange, buggy messages in link mode (sometimes it says YOU WIN even though you didn't). However, I finally whittled down the crashing bug to a bug in the CLB (cascade cleared rows) subroutine, where if the top row was marked to clear, a bug in the For loop structure would cause all of memory, including my program, to cascade down and crash. I'll post an update when I confirm that the bug is actually fixed.

There's also "Trick", but because Tricks is spelled with an X, the singular version loses its charm.  Maybe "Trik"?

Yeah, I though of that as well, but didn't post it. The cereals this doesn't work for are those that end in "Crunch."
One thing that you might want to do for some cereals is to change the names entirely, like "Cocoa Pepples" becomes "Cocoa Stone" (read with a deep announcer voice) or something.

I actually don't know any ASM. My only previous experience with low level ASM was the Apple //e's 6502 assembly. That language is incredibly inefficient: 3 registers, 7 flags, different three letter codes for every possible command (LDA, LDX, LDY are all load instructions for different registers), the fact that conditional jumping and relative jumping are inseperable, and multiple NOP operands (not just one). Not to mention that the text editor is quite lacking (no INS mode) and that the bytes of the graphics screen follow the criss-cross interlace pattern of a TV, simply because two OR gates were too expensive in 1977. I didn't vote because of how hard and useless 6502 ASM is.

And also, quite frankly, there are over 9000 Mario clones already. The world needs something new and exciting. Soon, I'm going to start writing a little paper on applying Darwin's theory of evolution to game design.

I merged both topics.

Also a NES emulator would probably be a bit hard, because it's a different processor to emulate than the z80. The Game Boy processor was closer to the z80 so it was easier to emulate.

That said, as Yunhua98 points out, you should start with a smaller project if you are new to TI programming. Mario is a huge project to undertake and is not recommended for anyone that has less than one year of programming and when I say one year, I really mean non-stop.

I second what DJ said. Mario has complex stuff like gravity, powerups, and not to mention all those enemies. Perhaps the simplest game you could start with in any language is a number guessing game. Then you could move to something strategic/turn-based, because that doesn't require constant input. Then you can move to an action game.

EDIT: And I just realized I'm Level 5!

But you can just do

Code: [Select]

sub(R)

Lbl R
X-3^27
Return
And save on space.

I think what he means is a replacement routine, where instead of calling the subroutine, the code is inserted inline. I'd like to see that implemented somehow (maybe parsing from the label until a Return is encountered).

Oh, yes, and on the compile menu, I'd also like to be able to hold STAT or something while pressing ENTER to suppress automatic backup creation (like compiling after a RAM clear).

I can't debug the program because no debugger geared for Axe exists. However, what I have noticed is that the crash always occurs when the program starts, meaning that there is something faulty with the code in every situation. However, whenever I output text characters to mark where it crashes, it always works fine, but then crashes when I remove the output commands.