Did someone say optimize?

First download Looks nice! Tiles seem to be really different from what you have in the screenshot, though... But then I suck at using emus.

What does the installer do, by the way?

EDIT: Weird, when I restarted Wabbit, the tiles seemed to turn normal again, like the ones you had in your shot

The music restarting thing I can easily fix, as I know exactly where in my code that's happening, so it shouldn't be too hard to fix.  I'm also contemplating how to do the map transition animation, like when going through a door, or up or down stairs, the screen fades to black, then back. I know I can do this with contrast manipulation, but I just have to find the right values.

I'm also working on the intro. I managed to start implementing special values into the text routine, like what squidgetx is doing for Ash: Phoenix. Currently, a value of [01] displays the player's name and and a value [02] displays the rival's name. I'll implement other ones later, but it's a start. I'm also trying to work out a name input routine like the one in the original game. I have to try and dig up my old PicArc archive (hopefully I still have a copy) of the GUI it used in my old Celtic III build of the intro.

how are you managing room linking in a quick/concise fashion? things like that tend to get tricky when there are four+ different link tiles on the same map.

Eventually, I'll have it looping through a list of data whenever a non-zero tile in the collision layer is stepped on in order to find where it links to. For the purposes of this test, it only supports one link. The collision layer is actually how I handle collision and object interaction, and eventually, NPCs.

Eventually, I'll have it looping through a list of data whenever a non-zero tile in the collision layer is stepped on in order to find where it links to. For the purposes of this test, it only supports one link. The collision layer is actually how I handle collision and object interaction, and eventually, NPCs.

i had a brainthought:

when a tile is stepped on you could have a parser run through the map data left to right, top to bottom from the beginning of your collision layer, adding one to a counter every time a link tile is encountered, and then append the map number to which the player should be directed(as well as the link tile number on that map where he will be appearing) to the end of the map data. it might be a little slow, but it's very small as well and could deal with 256 maps/link tiles per map =D.

Quote from: finale

Eventually, I'll have it looping through a list of data whenever a non-zero tile in the collision layer is stepped on in order to find where it links to. For the purposes of this test, it only supports one link. The collision layer is actually how I handle collision and object interaction, and eventually, NPCs.

i had a brainthought:

when a tile is stepped on you could have a parser run through the map data left to right, top to bottom from the beginning of your collision layer, adding one to a counter every time a link tile is encountered, and then append the map number to which the player should be directed(as well as the link tile number on that map where he will be appearing) to the end of the map data. it might be a little slow, but it's very small as well and could deal with 256 maps/link tiles per map =D.

Could you explain this a little more, or give an example program. I need something like this for one of my projects.

Am I missing something?  I thought this was in Hybrid Basic?
that said, that lookS AMAZING!