Minecraft crashes every time I try to rocket elytra up a ladder. It doesn't happen in vanilla, but it does happen when I'm using a Liteloader profile, even with no mods. I'm playing single player and haven't tested it on a server, but I'm able to recreate it every time. I don't think I'm doing anything super crazy here, but I haven't seen anyone else reporting it. I believe I'm using the most recent version of Liteloader for 1.12.
Here's the crash report.
---- Minecraft Crash Report -------- Minecraft Crash Report ----// I feel sad now
Time: 6/27/17 7:45 PMDescription: Exception in server tick loop
java.lang.NullPointerException: Exception in server tick loop at com.mumfrey.liteloader.core.PlayerEventState.onTick(PlayerEventState.java:95) at com.mumfrey.liteloader.core.event.HandlerList$IEventState15.onTick(HandlerList$IEventState15.java:100) at com.mumfrey.liteloader.core.LiteLoaderEventBroker.onServerTick(LiteLoaderEventBroker.java:411) at net.minecraft.server.MinecraftServer.handler$onServerTick$zza000(SourceFile:1395) at net.minecraft.server.MinecraftServer.D(SourceFile) at net.minecraft.server.MinecraftServer.C(SourceFile:560) at chb.C(SourceFile:154) at net.minecraft.server.MinecraftServer.run(SourceFile:464) at java.lang.Thread.run(Thread.java:745)
A detailed walkthrough of the error, its code path and all known details is as follows:---------------------------------------------------------------------------------------
-- System Details --Details: Minecraft Version: 1.12 Operating System: Windows 8.1 (amd64) version 6.3 Java Version: 1.8.0_25, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 263601384 bytes (251 MB) / 471031808 bytes (449 MB) up to 1060372480 bytes (1011 MB) LiteLoader Brand: 1.12-SNAPSHOT-r1F07073-b2-2 LiteLoader Mods: none LaunchWrapper: 10 active transformer(s) - Transformer: org.spongepowered.asm.mixin.transformer.MixinTransformer$Proxy - Transformer: com.mumfrey.liteloader.transformers.event.EventProxyTransformer - Transformer: com.mumfrey.liteloader.launch.LiteLoaderTransformer - Transformer: com.mumfrey.liteloader.client.transformers.CrashReportTransformer - Transformer: org.spongepowered.asm.mixin.transformer.MixinTransformer$Proxy - Transformer: com.mumfrey.liteloader.transformers.event.EventTransformer - Transformer: com.mumfrey.liteloader.common.transformers.LiteLoaderPacketTransformer - Transformer: com.mumfrey.liteloader.client.transformers.MinecraftTransformer - Transformer: com.mumfrey.liteloader.transformers.event.json.ModEventInjectionTransformer - Transformer: org.spongepowered.asm.mixin.transformer.MixinTransformer$Proxy JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M IntCache: cache: 0, tcache: 0, allocated: 12, tallocated: 94 Profiler Position: N/A (disabled) Player Count: 1 / 8; [oo['Willard21'/396, l='Macro Mania', x=26.49, y=21.78, z=6.48]] Type: Integrated Server (map_client.txt) Is Modded: Definitely; Client brand changed to 'LiteLoader'
Can anyone help? I can't find much information about setting up on mac.
you shouldn't have anything to do with updating mcp. The last dev environment that even used mcp (as far as I'm aware) is 1.8. Since then, everything's been handled with Gradle's SetupDecompWorkspace, IDE specific tasks (Eclipse, IntelliJ), and Build. I'm not sure what tutorial you're using to set up your workspace, but the one on the actual liteloader website is severely outdated, and you should use this tutorial instead: . Just keep in mind that whenever it has you clone from a git repository for sponge, just use this url instead: http://develop.liteloader.com/liteloader/ExampleMod.git
Rollback Post to RevisionRollBack
Have an idea for a mod? Join me on Discord or let me know here! (I prefer Discord though)
Keep track of the latest news and updates by following my twitter!
Feel like playing MC with me? Join me on the official PC Gamer US server here!
you shouldn't have anything to do with updating mcp. The last dev environment that even used mcp (as far as I'm aware) is 1.8. Since then, everything's been handled with Gradle's SetupDecompWorkspace, IDE specific tasks (Eclipse, IntelliJ), and Build. I'm not sure what tutorial you're using to set up your workspace, but the one on the actual liteloader website is severely outdated, and you should use this tutorial instead. Just keep in mind that whenever it has you clone from a git repository for sponge, just use this url instead: http://develop.liteloader.com/liteloader/ExampleMod.git
I don't know if I'm missing something, but that link seems to be an example mod. I can't find any information about actually setting up a workspace, which is what I'm struggling with..?
I don't know if I'm missing something, but that link seems to be an example mod. I can't find any information about actually setting up a workspace, which is what I'm struggling with..?
looks like he accidentally gave you the same link twice. The first one should be Follow that video, and "Just keep in mind that whenever it has you clone from a git repository for sponge, just use this url instead: http://develop.liteloader.com/liteloader/ExampleMod.git "
Sorry about that -- I could have sworn I had the right link pasted in, but after finally getting time to update my other mods (and finally doing so), I may have been more tired than I realized. Went ahead and corrected the original link, but MamiyaOtaru is correct, that is the video I meant to link to
Rollback Post to RevisionRollBack
Have an idea for a mod? Join me on Discord or let me know here! (I prefer Discord though)
Keep track of the latest news and updates by following my twitter!
Feel like playing MC with me? Join me on the official PC Gamer US server here!
I thought I should be mention this. A well known server have had problems with liteloader for some time. I don't know the background or reason for it and it may just very well be intentional. The server is 1.11.2 based. It all started in coincidence with the 1.12 release. So, the problem could be intentional, related to 1,12 compatibility or due to an anti-cheat plugin. I believe it's the last reson.
When you try to login, the server kicks you with the following message:
If you retry login a couple of times, you eventually succeed
That's really bizarre. I can't think why that would be the case unless they just have some kind of over-zealous cheat prevention which is detecting the client brand and rejecting everything except non-vanilla. But in that case it would probably trip on Forge as well unless they make specific exception for that. You could always ask them about it and refer them to me if they have concerns, I've gone out of my way in the past to ensure that server owners are happy with my mods, which is the whole reason stuff like ClientPermissions exists.
The fact that it succeeds if you retry a few times makes me think that it's a bug though.
Just a small idea, maybe the 1.12 fixed something and is sending information that u are using a modded client, and default setting of neatcheatplus(anticheat on most servers) is disallow all mods ?
LiteLoader doesn't try to hide itself in the first place though. It changes the client brand, per the contract, which is sent to the server. It also sends a ClientPermissions request packet if any supported mods are installed, plus the appropriate REGISTER packet for any mods which support plugin channels. So it's not exactly undetectable.
I even reached out to the NoCheatPlus guys in the past to see if they wanted to weave ClientPermissions support into the plugin, because I've always been keen to work with server owners since I used to run servers myself.
Honestly my guess would be that it's more likely a bug in an anticheat plugin than an intentional restriction, because I don't see what benefit there is to banning liteloader itself.
Running MultiMC with only liteloader or moving worlds works. If the fml client log or the MultiMC console output will help let me know and I'll post them.
In the meantime I'm just going to run liteloader for voxelmaps as my son not getting lost is a tad bit more important than making a movable floating empire.
left]
I'm sorry, i'm not sure where this belongs since it's a conflict between mods... hopefully someone can point me in the right direction.
I'm using MultiMC and trying to run liteloader and MovingWorld (Davinci's vessels dependency) on minecraft 1.12 but I'm getting an error:
Forge Mod Loader has found a problem with your minecraft installation
You have mod sources that are duplicate within your system
Mod ID : File name
Running MultiMC with only liteloader or moving worlds works. If the fml client log or the MultiMC console output will help let me know and I'll post them.
In the meantime I'm just going to run liteloader for voxelmaps as my son not getting lost is a tad bit more important than making a movable floating empire.
Thanks in advance[/left]
It's always safe to assume that more information is better. Please post all the logs you can find. However what's also important is whether you're installing liteloader by having forge load it, or whether you've set up a profile with liteloader chained to forge.
It's always safe to assume that more information is better. Please post all the logs you can find. However what's also important is whether you're installing liteloader by having forge load it, or whether you've set up a profile with liteloader chained to forge.
liteloader and forge are installed in whichever way MultiMC does it out of the box using the "Install Forge" and "Install LiteLoader" buttons.
I tried to use spoiler tags/code blocks but it was way too big for the character limit so i used pastebin instead... sorry for any inconvenience.
Looking through those logs I really don't see anything suspicious. I wonder if it's some weird interaction between MultiMC and some container validation FML is doing. The only clue I can give you is that both LiteLoader and MovingWorld use my Mixin subsystem, which is the only "conflict" (it's not a conflict in reality since Mixin is designed to work this way) FML might be detecting.
I would recommend starting with the MultiMC end because they have a good support community, either join #multimc on espernet or they have a discord you can join, both are usually pretty active (and they're bridged, so it doesn't matter which one you join).
If that doesn't work then it may be worth asking over at Forge's forums or IRC channel.
Definitely always provide logs where possible though! Now you have the logs, explain your issue and also link the logs so that developers can look at them.
I'll check out their discord. Thanks for checking it out. I appreciate your help and all the amazing work you've done.
Edit:
TL;DR when using MultiMC make liteloader load before forge
I actually managed to find a solution before going to their discord. I thought a bit about your previous comment, about whether liteloader is chained to forge or being loaded by forge. I went back to the versions and moved liteloader up (above forge) in the load order. This fixed the issue and moving worlds is now working with liteloader using MultiMC. It's strange that MultiMC doesn't have warnings about this or put liteloader on top. All is well now.
The Meaning of Life, the Universe, and Everything.
Join Date:
3/12/2012
Posts:
61
Member Details
I'm unable to begin 1.12 modding due to an error of setupDecompWorkspace:
Working Directory: D:\.....\ExampleMod
Gradle User Home: C:\.....\.gradle
Gradle Distribution: Specific Gradle version 2.9
Gradle Version: 2.9
Java Home: C:\Program Files\Java\jdk1.8.0_131
JVM Arguments: None
Program Arguments: None
Gradle Tasks: setupDecompWorkspace
:extractMcpMappings
Download http://files.minecraftforge.net/maven/de/oceanlabs/mcp/mcp_snapshot/20170713-1.12/mcp_snapshot-20170713-1.12.zip
:liteloaderDeobfCompileDeobfDepTask0
:liteloaderDeobfCompileRemapDepSourcesTask1
:deobfCompileDummyTask
:deobfProvidedDummyTask
:getVersionJson
:downloadClient SKIPPED
:extractDependencyATs SKIPPED
:extractMcpData SKIPPED
:genSrgs
:deobfMcSRG
Applying SpecialSource...
Applying Exceptor...
:decompileMc
:fixMcSourcesPatching failed: minecraft\net\minecraft\client\Minecraft.java
Hunk 1 failed! Cannot find hunk target
while(true) {
try {
- if (!this.field_71425_J) {
- break;
- }
+ while(this.field_71425_J) {
if (!this.field_71434_R || this.field_71433_S == null) {
try {
File state
package net.minecraft.client;
== long code omitted ==
FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':fixMcSources'.
> com.cloudbees.diff.PatchException: Cannot find hunk target
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
BUILD FAILED
Total time: 2 mins 38.196 secs
I tried the old trick of modifying the versions and mapping in build.gradle in the newest ExampleMod (master-48a4b5c6be4fe5ea4f44646d7425bca68076cb91), then I got the error every time.
Here's the content of build.gradle:
buildscript {
repositories {
mavenLocal()
mavenCentral()
maven {
name = "sonatype"
url = "https://oss.sonatype.org/content/repositories/snapshots/"
}
maven {
name = "forge"
url = "http://files.minecraftforge.net/maven"
}
maven {
name = 'sponge'
url = 'http://repo.spongepowered.org/maven'
}
}
dependencies {
classpath 'net.minecraftforge.gradle:ForgeGradle:2.2-SNAPSHOT'
classpath 'org.spongepowered:mixingradle:0.4-SNAPSHOT'
}
}
apply plugin: 'net.minecraftforge.gradle.liteloader'
apply plugin: 'org.spongepowered.mixin'
version = "0.1"
group = "com.mumfrey.examplemod" // http://maven.apache.org/guides/mini/guide-naming-conventions.html
archivesBaseName = "examplemod"
minecraft {
version = "1.12"
mappings = "snapshot_20170713"
runDir = "run"
}
sourceSets {
main {
// Refmap declaration must match the refmap name specified in the json config
refMap = "mixins.example.refmap.json"
}
}
mixin {
defaultObfuscationEnv notch
}
litemod {
json {
name = "test"
mcversion = "1.12"
mixinConfigs += "mixins.example.json"
}
}
jar {
from litemod.outputs
}
The Meaning of Life, the Universe, and Everything.
Join Date:
3/12/2012
Posts:
61
Member Details
So, which version of ForgeGradle should I use? I see 2.3 on GitHub, which is the only version newer than 2.2.
I tried to change it to "classpath 'net.minecraftforge.gradle:ForgeGradle:2.3-SNAPSHOT'", but setupDecompWorkspace still threw the very same error message.
I also tried to change the wrapper from 2.9 to 2.12, then to 2.14, but none of them worked.
This is really frustrating. Maybe you can update your ExampleMod for Minecraft 1.12?
So, which version of ForgeGradle should I use? I see 2.3 on GitHub, which is the only version newer than 2.2.
I tried to change it to "classpath 'net.minecraftforge.gradle:ForgeGradle:2.3-SNAPSHOT'", but setupDecompWorkspace still threw the very same error message.
I also tried to change the wrapper from 2.9 to 2.12, then to 2.14, but none of them worked.
This is really frustrating. Maybe you can update your ExampleMod for Minecraft 1.12?
Yes but did you clean and cleanCache to get rid of the broken part-decompiled artefacts? The mdk for 1.12 is here.
Minecraft crashes every time I try to rocket elytra up a ladder. It doesn't happen in vanilla, but it does happen when I'm using a Liteloader profile, even with no mods. I'm playing single player and haven't tested it on a server, but I'm able to recreate it every time. I don't think I'm doing anything super crazy here, but I haven't seen anyone else reporting it. I believe I'm using the most recent version of Liteloader for 1.12.
Here's the crash report.
---- Minecraft Crash Report -------- Minecraft Crash Report ----// I feel sad now
Time: 6/27/17 7:45 PMDescription: Exception in server tick loop
java.lang.NullPointerException: Exception in server tick loop at com.mumfrey.liteloader.core.PlayerEventState.onTick(PlayerEventState.java:95) at com.mumfrey.liteloader.core.event.HandlerList$IEventState15.onTick(HandlerList$IEventState15.java:100) at com.mumfrey.liteloader.core.LiteLoaderEventBroker.onServerTick(LiteLoaderEventBroker.java:411) at net.minecraft.server.MinecraftServer.handler$onServerTick$zza000(SourceFile:1395) at net.minecraft.server.MinecraftServer.D(SourceFile) at net.minecraft.server.MinecraftServer.C(SourceFile:560) at chb.C(SourceFile:154) at net.minecraft.server.MinecraftServer.run(SourceFile:464) at java.lang.Thread.run(Thread.java:745)
A detailed walkthrough of the error, its code path and all known details is as follows:---------------------------------------------------------------------------------------
-- System Details --Details: Minecraft Version: 1.12 Operating System: Windows 8.1 (amd64) version 6.3 Java Version: 1.8.0_25, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 263601384 bytes (251 MB) / 471031808 bytes (449 MB) up to 1060372480 bytes (1011 MB) LiteLoader Brand: 1.12-SNAPSHOT-r1F07073-b2-2 LiteLoader Mods: none LaunchWrapper: 10 active transformer(s) - Transformer: org.spongepowered.asm.mixin.transformer.MixinTransformer$Proxy - Transformer: com.mumfrey.liteloader.transformers.event.EventProxyTransformer - Transformer: com.mumfrey.liteloader.launch.LiteLoaderTransformer - Transformer: com.mumfrey.liteloader.client.transformers.CrashReportTransformer - Transformer: org.spongepowered.asm.mixin.transformer.MixinTransformer$Proxy - Transformer: com.mumfrey.liteloader.transformers.event.EventTransformer - Transformer: com.mumfrey.liteloader.common.transformers.LiteLoaderPacketTransformer - Transformer: com.mumfrey.liteloader.client.transformers.MinecraftTransformer - Transformer: com.mumfrey.liteloader.transformers.event.json.ModEventInjectionTransformer - Transformer: org.spongepowered.asm.mixin.transformer.MixinTransformer$Proxy JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M IntCache: cache: 0, tcache: 0, allocated: 12, tallocated: 94 Profiler Position: N/A (disabled) Player Count: 1 / 8; [oo['Willard21'/396, l='Macro Mania', x=26.49, y=21.78, z=6.48]] Type: Integrated Server (map_client.txt) Is Modded: Definitely; Client brand changed to 'LiteLoader'
Latest update makes chests disappear.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium1.11 Forge + LiteLoader 1.11 = no sound
Fix?
Try an earlier version of Forge in the interim.
The latest version of Forge is often bugged!
Links to pdf format, downloadable, command lists for (these often clarify/expand descriptions, and where possible link to the author's posting):
MoreCommands: http://www.mediafire.com/view/qjc9c6klcnp660e/CmdLstMoreCommands.pdf
WorldEdit: http://www.mediafire.com/view/bi7r00xd9rgxrrt/WE_Commands.pdf
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumyou shouldn't have anything to do with updating mcp. The last dev environment that even used mcp (as far as I'm aware) is 1.8. Since then, everything's been handled with Gradle's SetupDecompWorkspace, IDE specific tasks (Eclipse, IntelliJ), and Build. I'm not sure what tutorial you're using to set up your workspace, but the one on the actual liteloader website is severely outdated, and you should use this tutorial instead: . Just keep in mind that whenever it has you clone from a git repository for sponge, just use this url instead: http://develop.liteloader.com/liteloader/ExampleMod.git
Have an idea for a mod? Join me on Discord or let me know here! (I prefer Discord though)Keep track of the latest news and updates by following my twitter!
Feel like playing MC with me? Join me on the official PC Gamer US server here!
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI don't know if I'm missing something, but that link seems to be an example mod. I can't find any information about actually setting up a workspace, which is what I'm struggling with..?
looks like he accidentally gave you the same link twice. The first one should be Follow that video, and "Just keep in mind that whenever it has you clone from a git repository for sponge, just use this url instead: http://develop.liteloader.com/liteloader/ExampleMod.git "
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumSorry about that -- I could have sworn I had the right link pasted in, but after finally getting time to update my other mods (and finally doing so), I may have been more tired than I realized. Went ahead and corrected the original link, but MamiyaOtaru is correct, that is the video I meant to link to
Have an idea for a mod? Join me on Discord or let me know here! (I prefer Discord though)Keep track of the latest news and updates by following my twitter!
Feel like playing MC with me? Join me on the official PC Gamer US server here!
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThat's really bizarre. I can't think why that would be the case unless they just have some kind of over-zealous cheat prevention which is detecting the client brand and rejecting everything except non-vanilla. But in that case it would probably trip on Forge as well unless they make specific exception for that. You could always ask them about it and refer them to me if they have concerns, I've gone out of my way in the past to ensure that server owners are happy with my mods, which is the whole reason stuff like ClientPermissions exists.
The fact that it succeeds if you retry a few times makes me think that it's a bug though.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumJust a small idea, maybe the 1.12 fixed something and is sending information that u are using a modded client, and default setting of neatcheatplus(anticheat on most servers) is disallow all mods ?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumLiteLoader doesn't try to hide itself in the first place though. It changes the client brand, per the contract, which is sent to the server. It also sends a ClientPermissions request packet if any supported mods are installed, plus the appropriate REGISTER packet for any mods which support plugin channels. So it's not exactly undetectable.
I even reached out to the NoCheatPlus guys in the past to see if they wanted to weave ClientPermissions support into the plugin, because I've always been keen to work with server owners since I used to run servers myself.
Honestly my guess would be that it's more likely a bug in an anticheat plugin than an intentional restriction, because I don't see what benefit there is to banning liteloader itself.
I'm sorry, i'm not sure where this belongs since it's a conflict between mods... hopefully someone can point me in the right direction.
I'm using MultiMC and trying to run liteloader and MovingWorld (Davinci's vessels dependency) on minecraft 1.12 but I'm getting an error:
You have mod sources that are duplicate within your system
Mod ID : File name
com.elytradev.movingworld.common.asm.coremod : minecraft.jar
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumliteloader and forge are installed in whichever way MultiMC does it out of the box using the "Install Forge" and "Install LiteLoader" buttons.
I tried to use spoiler tags/code blocks but it was way too big for the character limit so i used pastebin instead... sorry for any inconvenience.
Fml Client Latest.log movingworlds liteloader 1.12
MultiMC console output
I probably should have find/replaced my user path with ~ but... oh well, don't feel like redoing it. I'm Chris, nice to meet you!
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumLooking through those logs I really don't see anything suspicious. I wonder if it's some weird interaction between MultiMC and some container validation FML is doing. The only clue I can give you is that both LiteLoader and MovingWorld use my Mixin subsystem, which is the only "conflict" (it's not a conflict in reality since Mixin is designed to work this way) FML might be detecting.
I would recommend starting with the MultiMC end because they have a good support community, either join #multimc on espernet or they have a discord you can join, both are usually pretty active (and they're bridged, so it doesn't matter which one you join).
If that doesn't work then it may be worth asking over at Forge's forums or IRC channel.
Definitely always provide logs where possible though! Now you have the logs, explain your issue and also link the logs so that developers can look at them.
I'll check out their discord. Thanks for checking it out. I appreciate your help and all the amazing work you've done.
Edit:
TL;DR when using MultiMC make liteloader load before forge
I actually managed to find a solution before going to their discord. I thought a bit about your previous comment, about whether liteloader is chained to forge or being loaded by forge. I went back to the versions and moved liteloader up (above forge) in the load order. This fixed the issue and moving worlds is now working with liteloader using MultiMC. It's strange that MultiMC doesn't have warnings about this or put liteloader on top. All is well now.
I'm unable to begin 1.12 modding due to an error of setupDecompWorkspace:
I tried the old trick of modifying the versions and mapping in build.gradle in the newest ExampleMod (master-48a4b5c6be4fe5ea4f44646d7425bca68076cb91), then I got the error every time.
Here's the content of build.gradle:
buildscript { repositories { mavenLocal() mavenCentral() maven { name = "sonatype" url = "https://oss.sonatype.org/content/repositories/snapshots/" } maven { name = "forge" url = "http://files.minecraftforge.net/maven" } maven { name = 'sponge' url = 'http://repo.spongepowered.org/maven' } } dependencies { classpath 'net.minecraftforge.gradle:ForgeGradle:2.2-SNAPSHOT' classpath 'org.spongepowered:mixingradle:0.4-SNAPSHOT' } } apply plugin: 'net.minecraftforge.gradle.liteloader' apply plugin: 'org.spongepowered.mixin' version = "0.1" group = "com.mumfrey.examplemod" // http://maven.apache.org/guides/mini/guide-naming-conventions.html archivesBaseName = "examplemod" minecraft { version = "1.12" mappings = "snapshot_20170713" runDir = "run" } sourceSets { main { // Refmap declaration must match the refmap name specified in the json config refMap = "mixins.example.refmap.json" } } mixin { defaultObfuscationEnv notch } litemod { json { name = "test" mcversion = "1.12" mixinConfigs += "mixins.example.json" } } jar { from litemod.outputs }-
View User Profile
-
View Posts
-
Send Message
Curse PremiumLooks like you're still using ForgeGradle 2.2 in your build script, change that and you should be fine.
So, which version of ForgeGradle should I use? I see 2.3 on GitHub, which is the only version newer than 2.2.
I tried to change it to "classpath 'net.minecraftforge.gradle:ForgeGradle:2.3-SNAPSHOT'", but setupDecompWorkspace still threw the very same error message.
I also tried to change the wrapper from 2.9 to 2.12, then to 2.14, but none of them worked.
This is really frustrating. Maybe you can update your ExampleMod for Minecraft 1.12?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumYes but did you clean and cleanCache to get rid of the broken part-decompiled artefacts? The mdk for 1.12 is here.