Ok so what I was talking about, I call them hooks. They are called before updating the screen and must handle map rendering. And actually it's the magic solution to all the problems an RPG can encounter :
-Teleportation/hub menu trigger. Just a matter of loading a new map and/or setting cordinates, or calling a routine.
-Objects on the ground. Alter the rendering and add key/position checks.
-Events. Duh.
-Cutscene trigger, yes these will be code.
-Tons of awesome sh*t like fancy grapical effects.

Also to make data creation easier, 0 in the vector table will make the engine call the default map renderer.
By the way the vector tables and routines that go with them are the only things that will go in the executable. Unless I make them into an external program disguised as an appvar and have the main engine as an app. This will be last resort if both can't fit in the app.

I'm finnishing off the map engine before I work on these.

You guys have no idea how epic of an idea this was. I implemented teleportation with three lines thanks to this system. That's right, three small lines of code.
Also, the executable stands at 1.7k with the debug features disabled.

Hehe. Hooks will do the trick.

Well actually thanks to the way the engine is designed I could also do it in a separate loop from the main one which will also help override user input because pressing keys during the ride is obviously not a good idea. Or I could go with a water flow thingy that simulates holding a key. I still have time to figure it out don't worry.

Interesting so far. For the final game I definitively think that the cavern could use some different graphics. though. If you stick to flat walls, there were some useful graphics from ROL3 that you could use

Also the demo made me lose >.<

On a side note; one feature that would be cool but might take quite a lot of code space is if you could view a list of key items you received through the game. For example, if you got keys, plant seeds, a papyrus, etc, they would now show up in your inventory so you would know you already got them. Currently, when you find a dungeon item you can't see it in your inventory due to RAM constraints.

Also the ability to see how many items of each kind you have in battle and in the ability menu it would be nice to know which magic will get equipped if applicable.

The screenshot Streetwalrus wanted

oh, also, will the character sprite be a different one eventually?

Just started the battle engine. I'm working on the battle screen right now and would like input as to whether or not I should show the enemy's health knowing the original didn't. I'm taking inspiration from Pokémon's long existing layout as well as the original Illusiat 11.