It doesn't. I've found out the error though, its because when i run runClient, it starts with forge version 204, however this bug has been fixed in the latest version
--fml.forgeGroup, net.minecraftforge, --fml.forgeVersion, 25.0.204,
I've installed the latest version of forge, but do you know how to make it so runClient uses the latest version, not 204?
Edit: Fixed it, ty for the help
Hey, I'm having the same error here, I've ran the installer for the latest 1.13.2 forge version, but when i run runClient, it starts forge with version 204.
--fml.forgeGroup, net.minecraftforge, --fml.forgeVersion, 25.0.204,
how can I tell the directory where my mod files are to use the latest version i installed
Yeah, I've removed the example mod from the directory, the client still loads but it just shows a screen saying "Error loading mods" "Forge has failed to load correctly (null)," there hasn't been any crashing
I'm new to modding - I setup an environment for 1.13.2 mod development, I created a Main class, pack.mcmeta and META-INF folder with mods.toml and I ran runClient to see if the mod would load. It's running into an NPE when its loading and I'm not sure what the issue is. Any help would be appreciated.
Here's the pastebin of the error: https://pastebin.com/EVtzYkrf
The NPE is at JarVersionLookupHandler, so I think I'm not setting up something with the version correctly?
Main class :
package com.matt.mod;
import net.minecraftforge.fml.common.Mod;
@Mod(Main.MOD_ID)
public class Main {
public static final String MOD_ID = "test";
}
mods.toml
modLoader="javafml" #mandatory
loaderVersion="[25,)" #mandatory
[[mods]] #mandatory
modId="test" #mandatory
version="1.0" #mandatory
displayName="Test" #mandatory
description='''
DESCRIPTION
'''
What am I doing wrong?
5 replies
Important Information
By using this site, you agree to our Terms of Use.