Direct download of latest version: http://www.omnimaga.org/index.php?action=dlattach;topic=4938.0;attach=4410
a hard level http://www.omnimaga.org/index.php?action=dlattach;topic=4938.0;attach=4416
some more levels http://ourl.ca/7535/140139

---

Since sometime in July, I've been working on porting The World's Hardest Game to Axe.  Finally, I've finished it.
In this game, you pick up 'coins' while avoiding enemies and then try to reach the finish.  Some levels may be easy, while others may be harder.
I went further than the flash version goes, however, and made a level editor.  The levels are created as appvars, but you can export them to linking-program-friendly programs and back again.
 

The game is compatible with the 83+BE, yet it contains a Full Speed Mode option.
More screenies.
 

Known bugs

Using teacher key (DEL), sometimes the location of the player sprite is shifted around, specifically from the very top to the very bottom.

Also, full speed is not reactivated on continue.  It's probably more of an asset than a bug to the person playing it, though.

Sometimes, an enemy seems to get corrupted and is displayed something like a pair of parenthesis while moving twice as fast.



Compile the level editor as an app.  The game can be a program.  The sample level needs to be imported before it can be played.  Just do it at the level select screen.
Also I feel that I should inform you that this program may cause you to lose the game...

EDIT: Current version here (link goes to the post)

I loved this game!

Oh it's normal. An unsigned APP is like a trial app for the calc. Back in the days, there were paid apps on TI website. After 16 runs these apps delete themselves.

I see that you posted the source for all this Darl, want me to try to help optimize it?

The parenthesis is 2 ball sprites xored on top of each-other with one slightly shifted.  You likely initialized 2 sprites there by mistake instead of 1.  Cool game by the way

The parenthesis is 2 ball sprites xored on top of each-other with one slightly shifted.  You likely initialized 2 sprites there by mistake instead of 1.  Cool game by the way

xor?  What is that?
In any case, I didn't use that.

Maybe I should explain how the appvar is structured.
The first 96 bytes are the static map. That's the walls, start, finish, coins, and respawn points.
The rest of it is the enemies.  Each enemy has three bytes.
1st byte: destination
2nd byte: direction
3rd byte: current location
The starting location is determined by its placement in the appvar.  They are moved one pixel in the direction (2nd byte) until the current location (3rd byte) is equal to the destination (1st byte).  Then, it reverses until it reaches the starting position, again determined by its location in the appvar.
My guess is that I somehow messed up the equation that references the enemies and it refers--and moves and draws--the same enemy twice or something.

Oh and another thing.  Sometimes, when I add another enemy before the faulty enemy, it suddenly starts behaving or another one might turn into a pair of parenthesis and go twice as fast.

That makes sense.  The way I have the sprites display is Pt-Change( .

My guess is that I somehow messed up the equation that references the enemies and it refers--and moves and draws--the same enemy twice or something.

I think I may have done something wrong in an optimization that I tried to do.  They're doing the exact same thing, the duplicate being one pixel behind.