Alex

While this is a commendable feature, I don't think it is a good solution. It would be more useful and flexible to allow mods to define custom HUD mesh elements...

Stu hasn't been around in a while and bell07 is the skinsdb maintainer, but I'll throw in my two cents anyway. This will break any mod that has hard-coded frame...

There is no rendering performance change. The only "loss" is a barely larger model file size.

> Design proposal: > ... Let's not continue the Minetest norm of making things more complicated than they need to be. This PR works. It will continue to work in...

> Your ToDos are missing `string.trim` which has been documented as well. Ah, indeed. My parsing script missed it due to using `:` notation. Added and marked.

> Why all the `{type-}` macros rather than just ``? The type name alone is ambiguous and not explicit. Macros should be prefixed for categorization anyway. > "Usage" is redundant...

I was [recently reminded](https://github.com/minetest/minetest/pull/14263#issuecomment-1960571921) of some other issues with the current Minetest documentation, specifically difficulty keeping PRs up to date with a changing doc file and inability to clearly classify...

Background music might be nice.

> I don't see myself using the editing feature I don't see why we couldn't make it both a previewer and editor.

> @GreenXenith If you validate the concept I will start making the extension use this. @AFCMS Concept is good :+1: