Also the difference with the new tiles and 3 tiles from Reuben 2 (some examples)

Mhmm, IMO the round corners fo the watter look better, maybe i'd need both and use some at some places and some at other places...

Or just some hex

In the original games, there were some annoyances that would be nice to see fixed indeed in this new version:

-In most calc RPGs, including the entire Illusiat and Reuben series, to talk to NPCs or interact with stuff, you must walk towards it, with no need to press the action key. However, in Reuben Quest, this makes it particularly annoying to walk around on maps with lots of water, as this makes Reuben fill his bottle with water (or let you select one to fill). Since there aren't extreme speed concerns like the original game, I think you should be fine making it so you have to press 2nd to interact with stuff.

I'll do that you interact with objects by facing 'em and hitting 2nd, i already kinda implimented that.

Read...

-In the original games, if you destroy rocks/plants or push blocks around, their position resets after battles. This was due to extreme RAM shortage that forced me to delete the entire map data during battles. You could possibly fix that too.

Will do

-Due to limited space in my sprite sheet (back then, xLIB only let you use 83 tiles at once and only Pic0 could be used), this forced me to not do any proper masking for mountain borders surrounding darker tiles such as trees and water, along with other tiles. This results in some maps looking weird. You could possibly add the extra following tiles to the game and fix those borders? The first ones are mainly for Reuben 1, while the 2nd row is for Reuben 2.

Will do if somebody will make me sprites.....
EDIT: I should learn to read too, i just spotted the sprites >.>

For using full use the token 'Full' to enable full speed mode
and to return a value for a subroutine, just have the last line of it be like A+B and then you can do MYFUNC()+3->VARIABLE

And IIRC there is already such a thing - for without peephole-optimizations hit ZOOM instead of ENTER when compiling

According to the readme:
 ​L₁: 768 bytes (​saveSScreen) Volatility: LOW
 ​L₂: 531 bytes (​statVars) Volatility: LOW (Some shells, including MirageOS, use this for mostly non-vital storage)

Or it only needs me to have a messy code........

Ok, so I added now these 8x9 character images with walking etc. and i added more maps and added a delay so that it isn't over-fast.
I'll do that you interact with objects by facing 'em and hitting 2nd, i already kinda implimented that.
I would do a screenie, but every time i send the source to wabbitemu it says 'invalid file format', same with the compiled app
EDIT: Oh, and i could do with my current engine rather easily up to 8*16 characters, with the background being correctly afterwards.

yeah, i recall xeda making something that allowed you to store variables on different ram pages that are normally not reachable