No, change several names, sorry ^^

Ah, well you have a few options, there. The section that checks which token you have is this:
push hl
ld hl, $C8*2
or a
sbc hl, de
add hl, de ;essentially, cp DE
pop hl
This returns Z if you have the right token, NZ if you don't. If you are changing a lot of token names, you would be better off using a look-up table. In your case, though, I think you are only changing a few tokens, so you can try to test like this:
ld hl, tokenHook
ld de, smallEditRam ;nothing touches this, ever
ld bc, tokenHookEnd-tokenHook
ldir ;copy it to a place where it won't get destroyed

ld a, 1 ;1 means ram
ld hl, smallEditRam
bcall(_enableTokenHook)
ret

tokenHook:
.db $83 ;necessary for hooks, indicates that it hasn't been overwritten
push hl
;Test the first token
;DE contains the token
ld hl, $C8*2 ;sinh(
or a
sbc hl, de
add hl, de ;essentially, cp DE
        jr z, cscToken
;Test the next token
ld hl, $CA*2 ;cosh(
or a
sbc hl, de
add hl, de ;essentially, cp DE
pop hl
ret nz
secToken:
ld hl, secText-tokenHook+smallEditRam-1
        ret
cscToken:
pop hl
ld hl, cscText-tokenHook+smallEditRam-1
ret
cscText:
.db 4, "csc(" ;length, then string
SecToken:
.db 4, "sec("

tokenHookEnd:


Thanks And I now have a command for grayscale sprites and tilemaps o.o That should help folks, I think

Thanks much, Deep Thought!

I finally learned how to do grayscale properly and now I want to pass on that knowledge for Grammer programmers. This has been possible with Grammer for a while, I just never understood the theory behind making it flickerless and beautiful looking. So here goes:

For three level grayscale, we have it very easy. You have a gray buffer and a black buffer In the gray buffer, you set any gray pixels to on and leave the rest alone. In the black buffer, you set the black pixels on and leave the rest alone. Now you need to display it and this is where it gets fun.

Normally, you would have flicker and if you have ever attempted and failed grayscale like me, you know what I am talking about. So how do you get around this? You set any gray pixels on an alternating cycle. How is this achieved? You use a checkerboard pattern and use AND logic on the buffer. So every other cycle, a gray pixel is displayed, but you want to display black pixels every cycle. So you OR the black buffer with that buffer, too. So here is an example using a tilemap:
!E→E                               ;This makes E alternate between 0 and 1. This tells us the cycle we are on.
Fill(+2                              ;This uses one of the checkerboard patterns. It alternates with E
Pt-Change(0,M,G,W,X,Y,1   ;Draws a tilemap using the gray tileset with AND logic
Pt-Change(0,M,B,W,X,Y,3    ;Draws the same tilemap with the blcak tileset with OR logic
DispGraph                         ;Now display
As long as you display it enough, this will make rather beautiful 3 level grayscale. I am currently working on other levels of grayscale as well as additions for grayscale drawing (possibly).

Anyways, here are some programs to play with. I would show a screenie, but WabbitEmu cannot capture it nearly as well as it looks on an actual calculator.

EDIT: Posted a pic and that is pretty accurate with how it look on an actual calc

Well, I am talking to Runer about it right now... Grayscale? I posted an example of a grayscale tilemapper before and it works quickly. Also, I think I might have made the tilemapper faster >.>

And I would also point out that the HUD is almost certainly being redrawn every time the character moves o.o I am working on a routine that will draw tilemaps to a section of the screen, so if he uses that, he won't have to redraw every time. However, that will only speed it up more. I think yeong may need something in to add a delay...
Xeda112358 has an idea...

Holy, wow that is great! o.o

First, when it copies the portion of the appvar, does it copy entire appvars into RAM, copy portion, and deletes it?

When you copy a portion, it only copies that portion. It doesn't copy the whole thing and delete portions.

Also, is there a way to save front buffer to back buffer? It will be nice.

You will specifically want Fill(8,b. You can either create your own 768-byte buffer (in an appvar) or you can use 9872h if you aren't going to use the default particle buffer. Also, using those Fill( commands, you can use logic to combine two buffers on the screen. For example, you can use OR logic as well as AND logic.

Also, Yeong, I think I am going to work on the next tilemap option as one to draw to a portion of the screen. This way, an HUD is more easily done(you won't have to redraw it every time you move).