Template fix + more mod support + credits rename

[MikiP98]

I fixed the template files, they still miss some of the optimisations that can be done in both PoTater and iProperties
I've made my own template preprocessor named iProperties that allowes for some additional automation that leads to the reduction of work. It is also easy to work with.

IDK how well iProperties to PoTater conversion works at this moment, but I can fix remaining conversion bugs, and you can keep only PoTater version while I will keep iProperties at least until PoTater implements support for using groups inside the groups, the format differences are minimal.

[null511]

I still don't see why you went so far out of scope instead of just adding what you already had like requested. I'm certainly not sorting through all these changes, or the multiple versions you've introduced.

[null511]

Also the changes you've made to the existing templates are invalid/do not work.

[MikiP98]

I still don't see why you went so far out of scope instead of just adding what you already had like requested. I'm certainly not sorting through all these changes, or the multiple versions you've introduced.

Fair, the inability to use groups in groups is too much of a limitation though, having it in a python pip package is very nice too (though I have not tested if it works yet)

[MikiP98]

Also the changes you've made to the existing templates are invalid/do not work.

Yeah...
The PoTater conversion was done very quickly
I will have to fix it

[null511]

Fair, the inability to use groups in groups is too much of a limitation though, having it in a python pip package is very nice too (though I have not tested if it works yet)

And that's where you lose me, because you had no problem making all these changes in the block.properties file directly, where you don't have any kind of templating/grouping at all. But when asked to update the templates which at least support groups, it's now not enough for you? Also it doesn't look like you've even run your templater on this branch, because there are no changes to any of the final block/entity/item files, nor any changes in the define files.

[MikiP98]

Fair, the inability to use groups in groups is too much of a limitation though, having it in a python pip package is very nice too (though I have not tested if it works yet)

And that's where you lose me, because you had no problem making all these changes in the block.properties file directly, where you don't have any kind of templating/grouping at all. But when asked to update the templates which at least support groups, it's now not enough for you? Also it doesn't look like you've even run your templater on this branch, because there are no changes to any of the final block/entity/item files, nor any changes in the define files.

I thought that if I have to use templates, at least it should have a greater use case.
Auto numbering may be a big feature for you, but it is a minor improvement for me, your groups/my variables how ever decreased the template file size almost 11 times compared to normal block.properties (the size reduction might still be improved).
The not working PoTater version is almost 10 times smaller too, but it has a lot of duplicates and isn't working right now because of 1 more limitation that I have to account for in the PoTater conversion, and the result will be less then ideal...

[null511]

Auto numbering may be a big feature for you, but it is a minor improvement for me

Just want to be clear here, auto-numbering and auto-defines are the entire reason these templates exist, and were added by me for floodfill in Bliss. Manually updating/synchronizing hundreds of indices without it is not maintainable. Any group/variable features beyond that are purely for convenience.

If you want to change tooling and take over floodfill/template support that's fine by me and between you and xonk.

[MikiP98]

If you want to change tooling and take over floodfill/template support that's fine by me and between you and xonk.

Well, I won't say yes as I have no idea what responsibilities come with that. I don't know how to write shaders (yet!). I can make small edits and add mod support to modded blocks in properties files, but I'm afraid that will be it

After most recent commits, there is a chance that the PoTater property files are working, you should give iProperties a try, it does support the auto numbering as well, but if you don't want to you can fix (if broken) the new PoTater properties files and edit them, and I will then bring the edits into my iProperties