Does it really work for the TI-83+ BE? I used MirageOS and when I tried to play the game (excuse me), all I got was a black screen (see screenshot below). I thought it was my calculator's fault but I tested it on Wabbitemu and it was the same result. I can still kind of make out the box as you can see in the screenshot but obviously I can't see where I'm going.

Lol, oops. I forgot that 83+ BE's don't have extra ram pages. I could possibly make a temporary appVar to hold the screen data, I only need 2,500 bytes.

@Magic Banana
I was thinking of adding in min/max jumps, that's pretty easy to do. The super jump is present in the ipod version as well, so I didn't feel bad about leaving it in. Here is why it happens:

When you make contact with a block, the game figures out how far overlapping you are with it. If you are in the top three pixels, which is normal for small drops, it just says you're on top and makes you jump. The super jump happens when you jump so close to the block that you brush the corner, make a frame where you are within three, and then jump off the top. If you to tap 2nd instead of holding it, you actually jump to the level of the block and stop. (I just did it.)

The way this happens actually causes a problem then because even though it looks like one jump, you are still jumping twice according to code. Which means that it doesn't count towards making your jump count smaller. I think I do the minimum jumps every time, so I'm not sure adding the stat would make much of a difference.


Since we're talking about how the game works, it should also be noted that blocks can't kill you if you are travelling faster than 3 pixels per frame. Although I'm not sure if this can be exploited.

Seeing that a garbage collect fixed it, it would mean there is another way to make a group straddle a page boundary that causes problems. If you can find a way to repeat the problem, I can fix it. But until I can watch the variables in an emulator that does the error memory, I really can't fix it.

With school coming up soon I uploaded this to ticalc. The only changes that I made was adding a pause button. I didn't put a level editor in because I feel like people wouldn't really want to make their own because the defaults are already good enough. Plus I'm lazy.

Here is the link. Go and get it.

Quote from: thepenguin77 on August 05, 2010, 09:59:59 am

Sir, I was just thinking, how smart is your kld routine? I am just worried that if you had data like .db $45, $CD, $FF, $00, that kld would mess with it.

I'm not sure what you mean by this.  You can use kld to replace ld, and when it runs, it just gets replaced with ld anyway.  At runtime, it's no different than coding for TIOS.

I spoke before I understood. When you said it only has to be run once, I thought that you would put rst 8h at the start of your program and every single call or ld would be changed. I forgot it was a macro every time.

I have no idea. But it's really helpful when people bring me their calcs at school that have "Viruses." Basically some font hook gone crazy, sometimes on purpose.

PTT does have one fatal flaw though, it kills all hooks, but not OFFSCRPT. Which means make an OFFSCRPT that disables it, all you have to do is off/on and you're good to go.

I had to change ld (op1), a to ld (op2), a. I accidentally made the whole answer negative.

I had one laying around too, optimized it a little though.

hook:
add a, e
or a
jr nz, quitZ

bcall(_Op2Set1) ;op 2 = 1

ld a, r
and %00000001
rrca
ld (op1), a ;neg or positive
bcall(_FPAdd)
quitZ:
cp a
ret
hookEnd:

And to make it epic, store it at smallEditRam, its a 108 byte area that no one ever uses. That way, it won't get destroyed.

I would press F5.