Well, I am not totally sure how strings work on the 89...

You store your map data to a string, which is simple enough. I have used it for graphics on the homescreen, and for the graphscreen with 8x8 tiles. What you have to do is take how many per row, and then how many per column, multiply, and that has to be the length of the string. Using a converter for tiles (the homescreen just requires the output command) you have the screen place the tiles and what not. Then you need to determine where the character starts at.

Say, for intents and purposes, the tile map is 8x16, and the character starts on the 5 row, 3rd from the left. 4*16 is 64, +3 is 67. so you need to set a variable to 67. Please note that there is a command on the 83/83+ that allows us to go through a string, starting at a defined point, ending at a defined point that will show what is there.

any who, when moving left or right 1 space, you ass/subtract 1. when moving up or down, you add/subtract 16. if moving from screen to screen, up/down requires add/subtract 112, while moving left/right from screen to screen requires add/subtract 15.

This of course varies with screen and map sizes...

If I knew more about strings and stuff on the 89, I would be able to provide more detailed info on it...

lol, but I prefer the string detection, since it is much faster, and consumes a third less of space...

Ok, matrix detection is extremely simple on the 8x series. Since the matrix only handles numbers, you have to use a converter to change the numbers into what it is you want displayed. You can also use the numbers to determine hit detection, since in the case of the 8x, you have an 8x16 screen, you have an 8x16 matrix, so you can use the variables that control the character to also navigate the matrix at the same time. You would just need conditions that would search [A](var+/-1,var+/-1), the conditions depending on which key is pressed.

The map data itself is figured by a coordinate system, kinda like a grid on a map. I use 0,0 as the top left corner, and work my way down. This map data is then stored into any matrix that you wish to use.

You also have to comprise the hit detection in to two parts for this to work, without getting dimension errors. This would be edge-of-screen detection, and not-at-the-edge-of-screen detection, basically a bunch of < and > symbols.

The events are easily handled, as there is a line of code that searches to see if the character is standing on a spot that isn't empty. You do not have to make sure about walls and stuff, since the hit detection does that when you move the character.

I think that is everything...

I really need to take a look at that stuff...

Some people don't like the run indicator, and really don't like asm, since some people think it is always unstable, so something like that they eat up...

lol, Well, I am not that great at writing things. Thanks.

I was trying to make it easily understanable, without making it like I am trying to teach newbies... Did I succeed?

Also:

QUOTE

Of course I dont need it much since I know how to do most of that stuff

Thanks, we can use all the elite we can get!

I also just finished my article on the 3 forms of hit detection, I just need to get it uploaded...

hang on, gotta dig for it...

http://calcgames.org/cgi-bin/teemz/teemz.cgi?board=_master&action=opentopic&topic=886&forum=Discussion