Can someone please send me an example LogHelper for mc1.8?

My Logger won't accept FMLLog.getLogger() as a parent.

 

package net.dimensionshift.mod;

import java.util.logging.Level;
import java.util.logging.Logger;

import net.minecraftforge.fml.common.FMLLog;

public class DimensionShiftLogHelper {
private static Logger logger = Logger.getLogger(DimensionShift.MODID);

public static void init() {
logger.setParent(FMLLog.getLogger());                                               <-- I can't cast FMLLog.getLogger() to Logger
}

public static void log(Level logLevel, String message) {
logger.log(logLevel, message);
}
}

FMLLog.getLogger()

returns a

org.apache.logging.log4j.Logger

, and you use a

java.util.logging.Logger

.

Yeah, I know.  I already tried all other possible imports, but nothing worked.

My question is how I can create something similar to this in 1.8.

Why can't you use the already existing

FMLLog

?

Ok, thx.

It works now if I use LogManager.getLogger(DimensionShift.MODID).info("TEST  TEST  TEST"); directly, but as soon as I try to move  LogManager.getLogger(DimensionShift.MODID) to a new class it stops working. Any ideas why?

 

public static void log(Level level, String msg){
	LogManager.getLogger(DimensionShift.MODID).log(level, msg);
}

 

	DimensionShiftLogHelper.log(Level.ALL, "Loading DimensionShift Version " + VERSION);

Oh....

It can be useful wrapping the logger in another class, if only to save a few characters when using it:

LogHelper.info("message") vs. MyMainMod.logger.info("Message").

 

Anyway, you can also get your Logger instance specifically for your mod from FMLPreInitializationEvent:

@Mod.EventHandler
public void preInit(FMLPreInitializationEvent event) {
logger = event.getModLog();
}

 

Similar to LogManager.getLogger("YourModId"), but it has the FML log as its parent, keeps formatting consistency in the console for all those log messages, and can be configured from the config/logging.properties file.

Yeah, I realized all this when I read the answer above.

I feel really dumb right now.

 

thx anyway.

If "MyMod.logger" is too much to type for you... shorten it with a static import (pseudocode):

 

import static MyMod.logger;

...

logger.info("hello world");

That's neat, but the main point of my post was about the benefits of getting the log from FMLPreInitializationEvent instead of using Apache's LogManager directly.

I tried both variants, but there was no visible differences.

What exactly is the advantage of getting the log from the PreInit Event?

Hm, maybe there isn't a difference any more, but there used to be. Well, just listen to diesieben

 

EDIT: Yeah, looks like the documentation is completely wrong, as event.getModLog just returns LogManager.getLogger with your mod id... Before FML switched to the Apache logger, though, I remember it being useful.