Yeah that's possible and depends on my laziness. Same goes for switchable graphics/ASCII stuff.

Yeah I'm already splitting any data from the executable. The appvar is generated with SPASM so it's really easy to change any resource in it, including translating, porting other Illusiat games or making a whole new game out of it.

Well, this is an RPG engine actually, but I'm designing it specifically for Illusiat.

Will this support Illusiat 12-like graphics? (where walls are more 3D-esque than flat)

I don't really get what you mean.

Also for the text engine, does it split text by line automatically if a word is too long or not? If that's the case, this might make translation easier, since you wouldn't need to manually align each line of text with the screen width.

Yeah I'll try do do auto word wrapping but I think that a line break control character would be easier to code.

For word wrapping, I did that in a useless project I made and never released (it's a port of the Pipotron to calculators), using a very stupid method:

-copy your string somewhere
-go through the whole string to replace all spaces with zeros, and while you're at it, count the number of spaces (which gives the number of words)
-set pencol and penrow where you want to write to, and set n to 0
-time for the loop
-  save the screen buffer
-  display the n^th word (at pencol,penrow)
-  if pencol is too high (read offscreen)
-    recall the screen
-    set pencol and penrow to a new line
-  else
-    n++ obviously
-  end
-end the loop if you've displayed all the words (hence why you counted them beforehand)

(I am too lazy to check if the algorithm is in the right order, but it should look like that and if something is missing, I'm sure you'll know how to fix it).

Yes, I made that useless program with the small font because the sentences don't fit on the screen with the big font.

Well that already works. Basically, the routine tries to display word by word, and if the word finishes offscreen, it erases it and re-writes it to a new line, then continues writing. The only "problem" is that I may have calibrated the "offscreen detection" a bit low, so there is always quite a few empty pixels on the right.

oh ok, I wasn't sure since in your screenshot there was one particularly short line.

That must be because the next word is a long one.

How do you do the offscreen detection btw? Do you just count the total amount of pixels each char in the word takes or is that what pencol do?

That is what pencol does. Basically, pencol is the x position of your pen. When you have written a word, your pen is at the end of the word. And if your pen is no longer on the screen (if pencol>width_of_screen) it means that your word was too long to fit on the screen.

I was sure that pencol and such stuff was only for the homescreen...

For the homescreen, its curcol (and currow), not pencol (and penrow).