Hmm I never used the language but maybe someone could invite him here or something. It could be a bug since the language didn't have many updates (although I think it's supposed to be finished). Not a lot of people used it since 68K almost completely died since 2006.

If I remember, it was kinda like Axe Parser in style, but unlike Axe Parser, it required an extra launcher to run programs. In Axe you could choose any shell you want or none at all. The language had huge potential, though. I guess the 89 not being as popular anymore just never allowed it to take off like Axe did. (Actually back then the 83+ community was really quiet too, but not as bad as the 68K)

Just out of curiosity, can you utilize the full screen space with Newprog? That was always something that bothered me about TI-89 BASIC.

Ahh, that's good then. ^^

I don't know about newprog, but IIRC in 83+ BASIC pixel test is the fastest(or one of the fastest) ways to do collision detection.

Does the language has severe memory limitations like MLC had on the 86 btw? In that language you could only use one array/list, for example, so if you were making an RPG you could only have one map (with possibly 8-9 rooms in it) and the entire game couldn't be more than 8 KB in size.

For collision detection, assuming all of your tiles are square and there aren't any irregular shapes in the collision area of your tiles, what i generally do is something like this. If you are going up, add the y velocity to the current y position and check what tile is in that new y position. If it is passable, save the new y position. If it isn't passable, you need to save (old y position % F8h): essentially, remove the y offset so that it is aligned to the tile. When checking collisions below you, you'll need to add 2 (if your coordinates are stored in multiples of 8) or 16 (if they're stored in pixels) to the y position before checking, since you need to check the position below the player. If it isn't passable, then just remove the y offset from the new coordinates and store that. If you're only going to be moving 1 pixel at a time, it can be simplified a little since you won't need to worry about aligning the player to the next tile (they will already be aligned). You can also limit your checks to every 16 pixels, but i like to do it every frame since it makes it easier for example to test if you are standing in lava and need to do damage to the player, etc.

*Edit AOC* in order to prevent 8) from turning into a smiley emoticon, check the "Don't use smileys" box when posting.