The only issue with pics is that there can only be 1 event tile per 16x8 area and its location is hard-coded with if/then/else in a program depending of where you are on the dungeon map. Would this be a problem with scrolling maps? (the program was executed everytime you reached the egde of a map, while in your case it might need to be executed everytime you walk around and require large if conditions )

Ah ok. I was more worried about a massive speed loss or something due to checking every single frame. Also what about the river?

Yeah you might need to do like I did or what people would do for NPCs in a RPG, like the pathway you mention. If I remember, my way of doing it was ridiculously huge, though.

Does it get slower as you add new subprograms and data? TI-BASIC has this problem when the VAT gets cluttered. I hope that isn't the same for Grammer.  >.<

Or could you maybe switch to 3 level grayscale for dungeons?

Ok but what do you think is slowing down the game more and more? In Metroid II, I was adding absolutely nothing to the walking engine over the development, yet the game was running 2x slower once finished than when I first started. Illusiat 13 had a similar problem but not as bad.

Hmm I wonder if this is a Grammer bug... it seems weird >.<

Well good luck

Yeah, we discussed on IRC what was causing the slow down. The way Yeong was doing it was due to lack of variables, so I pointed him in the direction of a command to backup or restore the current 54 variables all at once >.> This way, he can use the preferred method which is probably a few thousand times faster.