erich666
commented
1 year ago Note: if you do want to add new block types (but display them as standard blocks) you can now use the Translate script command. Video here: https://youtu.be/GXozY3HCCn4
And if you just want to use the new textures in a beta for existing blocks, download the beta version, go to "C:\Users\erich\AppData\Roaming.minecraft\versions\24w14potato" or wherever your versions are stored, select the .jar file and unzip that file into C:\temp\blocks. Copy tilemaker.exe and terrainBase.png from the Mineways\TIleMaker directory into c:\temp, then type in a CMD window in C:\temp:
TileMaker.exe -o terrainMine.png
This will produce a file "terrainMine.png", which you can then read into Mineways using File | Open Terrain FIle.
I get this every now and then, so time to write a short answer as to why I don't support the in-development beta of Minecraft.
Super-short answer: it's extra work.
Short answer: And, it's confusing. I'll add some block in beta, fully test it so that it works properly with waterlogging, with attaching to fences, with affecting water height level, with whatever else. Then on release they'll change the behavior just a bit, or the name, or the geometry, or not. This means I need to retest the block to see that it's still valid. Sometimes I'll forget to do so and a bug that could have been avoided will creep in.
Having been burnt by this a number of times in the past, I simply don't bother with the beta until it's truly out. Counting through my "how to do it" instructions, it's a 19-step process to add one block. Doing that twice per block - no thanks.