TheReaperKing wrote:Thanks so much for making this! My students are going to be so happy. I believe that most minecraft skin making sites are using 1.8 so that is why I voted for that and a conversion tool if people need 1.7 but wouldn't they be able to do anything they want in a 1.7 skin in 1.8? Thanks again!!!
TheReaperKing wrote:And my mineyoshi until we get an easy way to make skins I think being able to use minecraft skins in MT is a big deal though I'm certainly for adding in variety!
TheReaperKing wrote:I was trying the editor in class and it kept saying "wrong syntax". I was wondering if you could write out an example of what it should look like. I was trying python format18.py <blaze.png|c:\users\m\desktop\skinconverter\cskins> Where blaze.png is in the cskins. I also tried just format18.py without the python and also taking off the < > and many other things but no dice. I installed python 3.5 and set the paths variable. What am I doing wrong? Thanks so much!!!
TheReaperKing wrote:Thank you so much for the clarification!
Byakuren wrote:I don't think uniqueness is a valid argument here since the 1.8 format can emulate any 1.7 format skin anyway. Being unique by sticking to the old format would be doing so at the cost of strictly less possible skins. Is uniqueness even a good thing with skin format? As long as the default player is a certain model, there's only so much you can do with the skin format. Copying the skin format of Minecraft is a fine and pragmatic way to reduce the work players have to do to have their skins work on both games. If we want to be unique in a way that's beneficial to Minetest, we should look for a skin format that is strictly more powerful than Minecraft skins, meaning that any Minecraft skin could be used in Minetest, but not the other way around.
I voted for support only 1.8 and add a conversion tool. If there is a simple solution for supporting both that scales to future new formats, then I support it.
Users browsing this forum: No registered users and 14 guests