well made :D but i got an idea on how to make it simpler: use "map()" (draw the map) and "mset(x,y,spr)" (set a tile on the map) so you dont have to use a table ;)

@851523, The history of drawing approach is in my opinion the best starting point for an image editor, as the undo feature that is a must have will require rewriting a lot of the code if you went for the map() based approach first.
If the tool is expanded to serious levels, both approaches are needed simultaneously anyway :

• history only makes things laggy after the draw list becomes too long.
• map only make mistakes irreversibly destroy the WIP image.
  With both, you have no lag during drawing operations, and only lag when undoing that requires to replay all the drawing operations except the last.
  It is possible to get no lag even with undo at the price of extra memory by saving a screen snapshot every few draw actions so you only have to redraw from the last screen snapshot instead of from the very start.
  If @TehBeeKnee and you are interested in a collab to expand the tool to a more serious level, I'm in.

@RealShadowCaster
All of these ideas sound great but i wouldnt be able to implement it, i am very beginner.

@TehBeeKnee, do you have previous experience with other programming languages ? I could help you with the pico-8 and lua specifics.

@RealShadowCaster I know the basics of python, some javascript and a little c#. But im planning to learn lua.