Works flawlessly. However, your way of coding is a bit awkward. I have found a lot of things which aren't necessary, and things which could be optimized much.
For example. You used strings for variables which you only give the values "0", "1" etc. Why not just numbers? And when you want to store them to a string you use string(...), while they already are strings.
Also,
with(oMapBlock) {x+=8
myposx=x/8
myposy=y/8
}
Could be changed to:
with(oMapBlock) {x+=8
myposx+=1
}
The reset_map script uses two the same loops. Why don't you use one loop?
There are a few other things as well. But I can conclude that you didn't optimize your code.
I'm still giving you a 9 because it's great nontheless.
The only problem I see is that there is no set room transition system, but that isnt too big of deal 10/10
#8
Posted by
Alert Games on March 28, 2008 at 12:31 pm
TWAL INT, STFU. Don't just rate things 10/10 when you don't even open them just to get friended, because you get hated. 'nuff said. Anyways, this is awesome. 10/10 for brilliance.
Thank you for your feedback everybody!
C-Ator9, thatīs really strange. When I moved from GM6 to GM7 the opposite was happening (rectangles were 1px bigger, lines were too low/right). I guess Iīll have to switch to sprites.
As for the editor coding style, it was done in a rush, just to make the game map. Thank you for the advise!
nodata10101
This is the map system Iīm using in my project. It describes the game map using strings in arrays. 
