On a related note: have you also been plagued by those ERR:VERSION errors in programs and groups? I think I must have fixed those version bytes a kajillion times at school for people who couldn't transfer their favorite game to their friend. ('Where's Matthias gone? URGENT!!' Gaahhh...)

I haven't got a clue how those version bytes got changed, though. Anyone?

Well, since I'm hanging out here anyway, I could just as well post this:


I've decided not to use 'original' rogue storyline. Derivatives like Angband and such have inspired me to create 'rare' and 'unique' monsters (don't know if these existed in the original rogue. Angband is the only roguelike I ever managed to beat (protip: kill Morgoth!)).
I'm still thinking about it, but I'll post my mind in this thread while the story takes shape.

One Sure Thing: the objective of the game is to kill The Mata Mata, a giant turtle with |_|b4r m4dz1k p0wrz.

(inside info: Mata is my totem animal in our scouts... Info about the 'real' turtle: http://en.wikipedia.org/wiki/Mata_mata)

I think it does this:

(assuming you mean the ASM part)

Basically, it creates an appvar (removes it first if it existed) with the size specified in the first two bytes of savesscreen, and the name by the 9 bytes at HL. Then it returns a pointer (in HL) to the data start of the appvar. There you can start writing data.

The load routine works analogously.
I assume HL always points to ans in Axe, and (savesscreen); (savesscreen+1) contains the value of A? (sorry if I'm wrong, I didn't bother checking)




SirCmpwn's example does just that: it supplies the name of an appvar in ans, then length in A, next, it creates an appvar, storing the pointer to A. Then he writes to the location A is pointing to.
(I assume {A} is a pointer dereference operator)


EDIT: SirCmpwn, would you be so kind to remove the commented-out lines in your listing (code+hex) files next time? No offense intended, but it's a bit harder to read IMO.

The calcUtil credits refer to NoShell and Brandon iirc.

I've never done grayscale, but there's a first time for everything.

By the way, I'm planning to do this in an app. Seems like I'm gonna need those 16KB. (I'm at 4KB now, nostub, and although the movement code will shrink when I rewrite it to center the player, it's still big). What do you guys think?


ld a,1
ld (appInfo+2),a
bcall(50CBh)

ld a,$7E
bcall(_eraseFlash)

Or something similar... (it should erase the certificate, but I'm not sure if this will work without extra Weird Stuff)

No worries, during the Easter break (do you have that in the US?) I'll probably have plenty of time for coding, except for a few days of work/scouts/school trip. That's all.