I have been able to narrow down the bug consistently to one specific routine: the routine that eliminates cleared rows (and is always called except when there are highlighted rows). It crashes rarely in single player on my 83 Plus, but nearly always crashes in multiplayer mode, especially when DCS is involved. Also, the link routines have issues as well. I'll post an update as soon as I can.

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.

UPDATE: Version 0.7

Here are the new features:

• Fixed crash bug in DCS
• Fixed random/faulty linkplay messages (now the worst you can get is a 3 second lag when you clear a row, which looks cool anyway )
• You can see your opponent's grid height in multiplayer! (Finally working) In solo mode, that gauge is instead a timer that slowly rises to the top, and you win when the gauge hits the top. In Single Player, when you clear The Wall, it jacks up the gauge 1/8th of the way there.

Please download and tell me what you think!

There is no attachment...

I just put it there. Thanks for the fast response, though.

Nice!  Thanks for the quick updates. 

SAD DAY!  :'(

The compiled Eitrix just hit the 8811 byte limit! I was adding a score system to the game, and the game immediately crashed when code broke into the fourth page. Now all progress will be stopped until I hunker down and optimize the thing to death.

(And before anyone suggests I compile as an APP, that is not an option to me, because not only would that lock me out of any possibility of CALCnet, but also, my calc likes to turn off randomly, and if it turns off while the APP is writing, I lose everything).

That's really sad, also because it can't be compiled as an App. Good Luck with optimizing, perhaps you can ask help in the forums with that?

My idea: Ask Runer for optimizing, he's an optimizing guru.

Quote from: aeTIos on May 09, 2011, 10:34:45 am

My idea: Ask Runer for optimizing, he's an optimizing guru.

Just make sure to ask to keep it readable..

the two don't mix well