How about ... 84C integration?!

Yeah pretty much, plus i hope i have coded things a little better this time around anyway .

I have also added a 'replaceTile' function which will search a tilemap string and replace the specified tileID with another. Can be useful for easy 2-frame tile animations.

... base 37? Or do you mean 4-bits per tile? (So 1 hex character).

I thought I had asked everyone their thoughts and everyone seemed to agree on TIOS strings with hex chars @ 2 bytes per tile.

How would you dynamically change tiles (like remove obstacles etc) if your data is in FlashROM?

Axe would be awesome, It should have been ported already!

Well the bgpic's are 4x4 pixels but you are correct about the 8x8 sprites.

Although you can draw sprites of any size, they are broken into 8x8 tiles when defining them.

I have managed to bring the code back up to speed since the data loss, and it is appropriately backed up .

So far the list is:

Tilemap 8x8, 256 colour tiles, tiledata stored as strings
Sprites any size, clipped with transparency
Custom tile/sprite pic's, 128x64, 256 colours stored as appvars, unlimited number (custom named), can be archived
Custom 'bgpic' 80x60, 256 colours stored as appvars, unlimited number (custom named), can be archived
getTile returns tile in Ans
getKey with flexibility routines, can test for multiple keys in 1 call, can check for tile collisions etc
User variables, 256 * 16-bit variables (or memory slots) that most functions utilise (can still use TIOS for calculations etc but will need to store in a user variable for some routines)

Planned:
Text routine
Line & shape drawing
ExecuteArchivedProg (just a copy+paste from old xLIB really)
More getKey support routines
Sprite collision routine
Other stuff ...

Now that I have some basic functionality, ill see if I can make a decent test program.

Yeah, currently the pixels are 4x4 and it is a pretty low resolution image. But with the addition of colour it can be used effectively. I still need to fix a small issue with them but for the best part they are good to go.

I am still wondering about the best way to store tilemaps, im still leaning towards HEX Strings. xLIB will have some support routines to make working with string tilemaps a little easier like:

getTile - return tile at x,y in Ans
setTile - set tile at x,y in tilemap
numToStr - convert number to string in Ans
strToNum - convert string to number in Ans
moveXYCT - adjust x,y depending on keypresses and check for tile collision

Any other ideas?

Of course! The more information the better as far as im concerned.

Newbie to the platform will need something fresh to get started with.