Minecraft Forums

Make sure your interface is in a different package than your mixin. That package is excluded from class loading

Run the setupDecompWorkspace gradle task. This should be one of the first things you do if you follow any modern Minecraft modding tutorial.

In the files menu, click the name of the file without actually downloading it. That will show you the changelog.

It mentions it uses textures now.

Quote from Ayria»

Can't wait for 1.12 version!

Quote from TrevorPlz»

While I had to modify this solution quite a lot, and I don't quite to seem understand it finally (figured it out as I was about to ask more questions) understand the parentheses related to $1 now, as it selects the number of the grouping they make. I underestimated the destination portion of the filtering section in returning essentially variable information. Thanks for your help and patience.

Quote from ccar795»

Clean installed minecraft, forge and liteloader and it launches again no problem. What's weird is that it didn't do this last week when I last played and just started happening today. What could have caused this error in the first place? Thank you for the help btw.

Quote from stitch2k1»

Would that be messing everything up?

Possibly. Optifine likes to add local variables, which messes up mixins. I'll need to figure out what those variables are and account for them.

Updated to 1.11.2 now. https://github.com/MineLittlePony/MineLittlePony/releases/tag/1.11.2.0

.. Does anyone still come here?

Just got around to updating to 1.11. Downloads are on both curse and github.

Quote from SolarEntropy»

I was having the same issue as LouisLOurson, however, after following through the video about Sponge replacing the git with LiteLoaders, trying to run "setupDecompWorkspace", the task ":recompileMc" failed caused by the following:

Caused by: java.lang.NoSuchMethodError: org.gradle.api.logging.LoggingManager.setLevel(Lorg/gradle/api/logging/LogLevel;)Lorg/gradle/api/logging/LoggingManager;
	at net.minecraftforge.gradle.user.TaskRecompileMc.doStuff(TaskRecompileMc.java:89)
	at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:75)
	at org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore$StandardTaskAction.doExecute(DefaultTaskClassInfoStore.java:133)
	at org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore$StandardTaskAction.execute(DefaultTaskClassInfoStore.java:126)
	at org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore$StandardTaskAction.execute(DefaultTaskClassInfoStore.java:115)
	at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:623)
	at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:606)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:80)
	at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:61)

I'm aware that it's a dependency issue, but I'm new to using Gradle and completely baffled as to what to do about it. Can anyone assist me?

So I have pushed the 1.12.2 artefacts up to the repo, this is an interesting version bump and most if not all 1.12.1 mods will load under 1.12.2 with no changes. The following notes are for mod developers:

• I have set the 1.12.2 LiteLoader to support the 1.12.r2 version string because most mods for 1.12.1 will load under this version, so as per my standard of using the r-numbers I have set 1.12.2 to support r2 but for the purposes of mods who are not compatible with 1.12.2, 1.12.2 also supports r-number r3 in case a 1.12.4 comes out which is also compatible.
In short, mods which have deployed using the r-number for 1.12.1 (which includes my mods macros and wecui) will work without changes on 1.12.2. Those deploying without the r-number can either make a release with the r-number if they are compatible, can make a release with r3 if they know they are not compatible, or can make a release using straight-up 1.12.2 if they know they're likely to break with even minor changes.


• For reference, the changes I was able to easily observe between 1.12.1 and 1.12.2 are (direct from my notes) as follows:

Notch  Searge                                              Notes
aex    net/minecraft/entity/item/EntityEnderPearl          Method "changeDimension" added
aqn    net/minecraft/block/BlockFarmland                   Minor changes to "turn to dirt" logic
blj    net/minecraft/client/gui/GuiDownloadTerrain         Keepalive logic removed, moved into NetHandler
blr    net/minecraft/client/gui/GuiMainMenu                Added "edition" field and edition overlay
blt    net/minecraft/client/gui/GuiWinGame                 Added "edition" field and edition overlay
jd     net/minecraft/network/play/server/SPacketKeepAlive  keepalive id int to long
lj     net/minecraft/network/play/client/CPacketKeepAlive  keepalive id int to long
pa     net/minecraft/network/NetHandlerPlayServer          keepalive logic changes




• Mixin was bumped to 0.7.4 but these are internal changes which don't affect anything really.

In short, most stuff should "just work" unless it's touching any of the stuff above. The obf did not change other than the added methods, 1.12.1 and 1.12.2 are obf-compatible.

Quote from Dats_ME»

Darn Mojang went and updated to 1.11.2 and broke LiteLoader LOL provided yet another free bug-fix release to the community which unfortunately breaks mods for a short while MCP gets updated.

LiteLoader is a lightweight mod bootstrap designed to provide very basic loader functionality for mods which don't need to modify game mechanics. It is designed to run alongside Minecraft Forge and Forge Mod Loader (FML) and LiteLoader mods will virtually never conflict with Forge mods.

• Simple, easy-to-use client modding API, perfect for client-side mods like Mini Maps, Chat Tools, and other HUD mods.
• Bytecode-based event injection system which provides super-efficient event handling, and can be easily extended by mods as necessary
• Compatibile with Minecraft Forge and FML thanks to dynamic injection
• Built-in mod version validation which allows LiteLoader to identify and load only valid mods - no more crashes caused by accidentally loading out-of-date mods
• Easy to install and compatible with all launchers supporting the Mojang Tweak System (launchwrapper)
• Extensible "LiteAPI" core allows more complex APIs such as BlazeLoader to be built on top of LiteLoader
• Sleek in-game user interface provides mod management, mod configuration panels, error reporting and in-game log viewer:

Installing LiteLoader is pretty straightforward and if you're familiar with the process, visit the download page to grab the latest installer for your version of Minecraft. If you're new to LiteLoader follow the instructions below








ShadersMod supports installation stand-alone, and also alongside Minecraft Forge but can easily be installed alongside LiteLoader even when Minecraft Forge is not in use. If you are creating an installation including Forge simply follow the instructions and download the Forge Edition and put it in your mods directory. If you do not have Forge then download the Non-Forge Edition and put it in your .minecraft/mods/<version> folder where <version> is the version of Minecraft you're using, eg. for 1.8 it would be .minecraft/mods/1.8


Official downloads are available from the download page:



Development builds are available from the Jenkins build server:



Current development builds are available for Minecraft 1.9, Minecraft 1.8.9 and Minecraft 1.8 and are not supported in any way, shape or form. Use development builds at your own risk as they are likely to be unstable and may contain critical bugs which can corrupt your world cause crashes. You have been warned!


Looking for mods for LiteLoader? Then look no further than the LiteLoader Mods List.



If you are a mod developer and would like to have your mod added to the list, or have the existing entry amended then simply post below or drop me a PM here on the forums.


LiteLoader is aimed squarely at mods which only change the client in some way; some good examples might be a mini-map, a mod which overhauls the in-game chat or a client-side macro system. This type of mod doesn't generally need the awesome power of something like Minecraft Forge to function, so asking players to install an API that's several times larger than the mod itself doesn't make sense. It must however coexist peacefully alongside Forge (so that players can use both platforms if they want to!) and LiteLoader does this.

LiteLoader was primarily developed for use by The VoxelModPack Team but is source available to allow mod developers to make their own mods using the platform.

As a modder, if you're looking for a loader to help you add a new block, item, mob or mechanic into the game, then LiteLoader isn't for you and you should check out Minecraft Forge. If you want to make a mod that displays something on the screen like a heads-up FPS counter, provides an in-game IRC window, or anything else that doesn't alter game mechanics then LiteLoader is probably perfect for you!

• What is this for and why do I need it?
Like other loaders and API's, LiteLoader doesn't do much on its own. If you want to run a LiteLoader mod then you need LiteLoader, if you don't then you don't need it! In general, the mods which use LiteLoader will link to this thread as a place to download the loader and provide support.


• Can I load Forge or ModLoader mods with this?
No, LiteLoader is a standalone API used by some client-only mods, however you can run it at the same time as Forge or FML and it won't conflict, so if you want to use Forge mods and Lite mods, then that's fine!


• The game won't load when I specify multiple tweaks, what gives?
Try changing the order of the tweaks, sometimes the load order is important since the first tweak is the "primary" one. Try putting liteloader's tweaker first for example.


• I have a mac, and after installing the 1.5.2 version of LiteLoader I have no sounds at all!
This isn't LiteLoader's fault, there is a problem with the mac archiver that causes it to overwrite the "com" folder inside you minecraft jar with the LiteLoader one instead of merging it. Unfortunately the "com" folder contains the sound codecs for the game!

To work around this, either manually merge the new "com" folder into the existing one in the minecraft jar, or use the Mac LiteLoader Patcher made by chattahippie, which automates the installation.


• I installed a mod into my "mods" folder but it's not detected by LiteLoader.
First, check that the mod is for the correct version of Minecraft. LiteLoader includes a version-checking system designed to prevent out-of-date mods from loading and crashing your client. If the versions mismatch then LiteLoader will not load the mod. For example if you have a mod for Minecraft 1.5.1 do not expect it to work on Minecraft 1.5.2!

Secondly, ensure that the file extension is .litemod. Some browsers detect that the files are .zip files and rename them to .zip when you download. LiteLoader requires the files to have the .litemod extension in order to recognise them as mods.


• Can I redistribute LiteLoader in my mod pack?
Yes, see the Permissions section below.


• Can I make a custom version of LiteLoader and redistribute it?
In general, no. The reason for this is that LiteLoader is an API (albeit a small one), and having multiple incompatible versions of an API in the wild is confusing for users and makes tracking bugs and issues very difficult. We do however work with mod developers who would like custom extensions to LiteLoader or would like to integrate the loader itself into their mod. Please note that LiteLoader's source code is protected by copyright and you may not redistribute the source without permission.


• Where can I find information about making LiteLoader mods?
See the section Developing LiteLoader Mods below.


• Where can I find the source code?
develop.liteloader.com can be used to access the LiteLoader GitLab site.


• When will the next version be out?
Asking for updates is against the Minecraft Forum rules, if you're waiting for an update just be patient. One of LiteLoader's goals is to keep its footprint small to make updating easy, so in general the update speeds are very fast.


• Can I run LiteLoader and Forge at the same time?
Yes, they are designed to coexist, you can install both without any problems.


• Won't running two loaders cause some kind of performance impact?
To cut a long story short, no. The loader is a tiny portion of the general footprint of the game and any mods you might install that use those loaders. Any impact on performance as a result of using multiple loaders is entirely lost in the general overhead of running the game itself.


• Where can I report bugs?
If you have a question or a problem that you are not sure if it's a bug, then ask right here in this thread. Alternatively if you find a bug in LiteLoader itself you can submit a new issue on the LiteLoader GitLab.


• Can I request new features?
Yes, but bear in mind that LiteLoader's core remit is to stay as light-weight as possible. This means I will generally only add functionality to the loader if it makes sense for it to be there. LiteLoader will never support adding blocks and items to the game so don't ask.


• I accidentally my entire Minecraft. Is this bad?
Probably. If in doubt add more cowbell.

You are free to redistribute unmodified LiteLoader binaries in any mod pack or compilation, including on third-party distribution platforms such as Feed The Beast provided that the distribution remains free, eg. no ad.fly links or similar.

You are free to use the source code to research LiteLoader internals but you may not redistribute modified versions of the loader. You may not redistribute the source code in any form without written permission.

I would also request that you do not redistribute development builds, these are subject to change often and support is not provided, redistributing them is strongly discouraged.


Developing mods for LiteLoader is based around usage of the Minecraft Coder Pack so you should be familiar with MCP before you start.

Some (very brief and incomplete) documentation is available on the LiteLoader Docs page and I will be adding to this over time. I also recommend taking a look at my tutorial video showing how to get up and running with MCP, LiteLoader and Eclipse (if you can tolerate my voice for that long!) which covers everything from start to finish. Currently pending an update since the switch to gradle, watch this space.

If you get stuck feel free to ask questions here in the thread, I always try to help when I can. Or you can find me on IRC espernet #liteloader and #sponge.





Feel free to ask any questions or any other comments you have here in the thread, we will do our best to answer them!
In the meantime, happy Minecrafting

Quote from OverSpeed301»

Hello !

I have installed Liteloader on a modpack, and there is a bug between LiteLoader and Ships mod. There is the stacktrace : (when I launch the game)

The developper of the mod says that is maybe inside Liteloader. http://www.minecraftforum.net/forums/mapping-and-modding/minecraft-mods/1444787-ships-mod-build-sailable-ships-out-of-blocks?comment=3220


Thanks !