Good day everybody.

I was working on my coremod and when i launched mc, changes didn't get applied. After i discovered that my coremod is not even called.

Now, i found this in log:

[21:06:45] [main/INFO] [sTDOUT]: [net.minecraft.client.main.Main:main:160]: Completely ignored arguments: [-Dfml.coreMods.load, code.elix_x.coremods.antiidconflict.AntiIdConflictCore]

Here's my program argument:

-Dfml.coreMods.load=code.elix_x.coremods.antiidconflict.AntiIdConflictCore

And my coremod:

package code.elix_x.coremods.antiidconflict;

import java.util.Map;

import org.apache.logging.log4j.LogManager;
import org.apache.logging.log4j.Logger;

import cpw.mods.fml.relauncher.IFMLLoadingPlugin;
import cpw.mods.fml.relauncher.IFMLLoadingPlugin.MCVersion;
import cpw.mods.fml.relauncher.IFMLLoadingPlugin.Name;
import cpw.mods.fml.relauncher.IFMLLoadingPlugin.SortingIndex;
import cpw.mods.fml.relauncher.IFMLLoadingPlugin.TransformerExclusions;

@Name(AntiIdConflictBase.MODID)
@TransformerExclusions("code.elix_x.coremods.antiidconflict.core")
@MCVersion("1.7.10")
@SortingIndex(1001)
public class AntiIdConflictCore implements IFMLLoadingPlugin {

public static final Logger logger = LogManager.getLogger("AIC Core");

public static final String BiomesInitTransformer = "code.elix_x.coremods.antiidconflict.core.transformers.BiomesInitTransformer";

public static final String[] transformers = new String[]{BiomesInitTransformer};

@Override
public String[] getASMTransformerClass() {
	logger.info("Getting transformers");
	return transformers;
}

@Override
public String getModContainerClass() {
	return null;
}

@Override
public String getSetupClass() {
	return null;
}

@Override
public void injectData(Map<String, Object> data) {
	logger.info("Loading");
}

@Override
public String getAccessTransformerClass() {
	return null;
}

}

 

Can anybody explain what has changed? Did i miss something in update logs? Should i re-update forge?

 

Thanks for help!

If you have any questions - just ask!

You set system properties via a JVM argument, not program argument.

No.

Also, i know that it's not loaded because none of 2 info statements is present in the log.

What I meant was that system properties need to be set as JVM arguments, not program arguments.

I tried both. I even tried putting it in program arguments and in VM arguments. Still not working.

-Dfml.coreMods.load=code.elix_x.coremods.antiidconflict.AntiIdConflictCore

Note the equals sign.

 

Why do you need to make a coremod? FML handles ID conflicts internally.

Why do you need to make a coremod? FML handles ID conflicts internally.

Never mind, just took a closer look at your code and I see why.

 

It looks like you have tried it with the equals sign but showed us the log of a run without the equals sign, given that they're shown as two separate arguments. Try with the equals sign in the JVM arguemtns

-Dfml.coreMods.load=code.elix_x.coremods.antiidconflict.AntiIdConflictCore

Note the equals sign.

 

Why do you need to make a coremod? FML handles ID conflicts internally.

Never mind, just took a closer look at your code and I see why.

 

It looks like you have tried it with the equals sign but showed us the log of a run without the equals sign, given that they're shown as two separate arguments. Try with the equals sign in the JVM arguemtns

FML handles item an block ids. But not biomes for example.

 

I tried putting this argument everywhere where i can put it. Still no luck.

I tried both. I even tried putting it in program arguments and in VM arguments. Still not working.

That is impossible™.

Yeah.

Just tried reinstalling workspace and "reassembling" argument. Put it in both VM and program arguments... And it worked.

Something very very very weird just happened.