My own home brewed UI, one I created several years ago with a tile map editor I made ages ago. It's not anything complex, or else I would just release the library by itself... But also, it doesn't scale. I mean, I can think of ways to do it? But it feels like, for this project, it would work better ...

Oh, and it doesn't use tilemaps for backgrounds (eg, the grid based thing you're talking about). It just uses png backgrounds for layers.

Screenshots in that thread are already outdated, since I've tweaked the tools a bit.

I've been working on one for about two months now, made a lot of progress (though at the moment I'm refactoring code, simplifying, and expanding, as well as working on getting more screen real estate for certain areas, etc). https://love2d.org/forums/viewtopic.php?f=5&t=92187 I've done similar s...

huh, I guess this project is dead now?

LOL

Duh, of course. I'll do that in a bit.

LOL yeah, eventually this will be moved to a different thread, since it's gone beyond just a few thoughts, lol. I ended up refactoring and streamlining how it was handling sprite objects and in game entities, to make it more powerful on the user end. And, for those of us who know Lua, being able to ...

Naw, I know exactly what I'm doing with some of these ideas. For example, the meta-tool idea combined with plugins actually creates a smaller scope for me as a coder- I know how to create plugin architectures that are very versatile and powerful, and I've already got one built here that works and is...

Haha, yes, I was just thinking "maybe I should start a different thread with something more like "Magic Pixel devlog" or something! Dunno if I mentioned it earlier, but I decided to go with Magic Pixel as the name of the editor and engine. Oh, speaking of which, I made a rough logo an...

I'm thinking about using this https://love2d.org/forums/viewtopic.php?t=89025 For allowing in editor code editing, just to make some editing simple and similar to Pico 8 (but also allowing people to edit outside of it). This would be for Cutscene scripting, or object scripting (but not plugin script...

(ignore the 162, 167, was just debugging some mouse code)