I’m a big fan of the VoxelMap mod, and unfortunately, when my server changed to 1.12.2, there was no VoxelMap available.

This allows for faster loading – which is one of the reasons why Liteloader is lite – but it means your mod breaks when bcj becomes bcx and your mod still references bcj. This means the translation phase – and the time associated with that – is running before mods are distributed, your whatever.litemod already references the bcj name. LiteLoader, on the other hand, does this translation while you compile the mod.

That’s why small updates to the client don’t cause Forge mods to break. jar still used the BlockState name when the mod gets loaded, that name gets translated to the real name of the client you’re currently using. So, when your mod is using code that accesses a block int the world, you use the BlockState class when your mod is loaded, that name – BlockState – needs to be mapped to the name the client is using – bcj, or bcx, or whatever.įorge does this dynamically. The people who wrote the Minecraft Coder Pack, the software that Forge and LiteLoader build on, made tables to reverse map those names to meaningful ones, and they do that for every new version of Minecraft. And, in new versions of the client, this mapping changes the class that used to be abc may be abf now. The problem behind this is, Mojang obfuscates their client classes, meaning they assign more or less random meaningless names to them, like abc or aj or bcx. But when the changes are very minor, like 1.12 to 1.12.1 to 1.12.2, most of the time, plugins will still work.Īs long as they’re forge mods. When there’s a lot of changes to the client itself, then, well, mods have to adjust to these changes. Which is easy if you’re running a plain vanilla client, but can be quite an annoyance when you’re using mods, and your mod author doesn’t update them in time. Every now and then, there is a new minecraft subversion, and when your favourite server updates, you need to update as well.

Adobe flash player version 4