Thank you so much for taking the time to write all of this and for putting together the videos! Bug reports and feedback like these are incredibly helpful.
Regarding the statistics menu, I believe I’ve fixed all of the issues you mentioned (hopefully xD). I’ve tested the most common scenarios, but there may still be edge cases I haven’t covered yet, so please let me know if you spot anything else.
The mouse issue with the in-game controls on the main menu has also been fixed.
As for the tile editing behavior when there’s already an NPC or item on top of the tile, that’s actually how the engine currently works. TRS always prioritizes selecting sprites over tiles. I do think I can improve that behavior so that, when you already have a tile selected, it prioritizes painting the tile instead. I just haven’t implemented that yet.
The new Logic tab is something I’m also really excited about. I actually made a small tutorial while playing the jam entries on stream, and I plan to create a series of short tutorial videos covering features like that. I’m even considering creating an official TRS YouTube channel dedicated entirely to tutorials and engine updates.
The suggestion about showing how many hits a sword has left is excellent. In fact, I liked it so much that I’ve already implemented it! Swords now have a visible health bar, just like enemies, making it much easier to know when they’re about to break.
The remaining suggestions (renaming enemies, NPC item exchanges, manually controlling the orange “!” indicator, instant game over choices, skill restrictions, etc.) are all on our radar, and we’re discussing the best way to implement them without making the editor unnecessarily complicated or even if some should really be implemented.
Regarding the music warning, that’s a very good point. However, I think it’s ultimately the responsibility of each game creator to make sure they have the rights to use the music they include. Trying to detect or prevent copyrighted music inside the engine would be an extremely difficult problem to solve reliably, so for now I’ll leave that responsibility with the developers.
Thanks again for all the feedback and for participating in the jam. Reports and suggestions like these are what help TRS continue to improve!