I've set up my workspace, and I've started making a mod, and even though the game functions fine, the logger stops working shortly after starting up, which is a problem, as it's a pretty essential part of my debugging process. A transcript of the relevant parts of the log follows:

[12:10:09] [main/INFO]: Managed to load a deobfuscated Minecraft name- we are in a deobfuscated environment. Skipping runtime deobfuscation
[12:10:09] [main/INFO]: Detected deobfuscated environment, loading log configs for colored console logs.
2018-11-02 12:10:09,638 main ERROR Error processing element LoggerNamePatternSelector ([PatternLayout: null]): CLASS_NOT_FOUND
2018-11-02 12:10:09,639 main ERROR Error processing element TerminalConsole ([Appenders: null]): CLASS_NOT_FOUND
2018-11-02 12:10:09,640 main ERROR Error processing element LoggerNamePatternSelector ([PatternLayout: null]): CLASS_NOT_FOUND
2018-11-02 12:10:09,655 main ERROR Unable to locate appender "Console" for logger config "root"
2018-11-02 12:10:09,874 main ERROR Error processing element LoggerNamePatternSelector ([PatternLayout: null]): CLASS_NOT_FOUND
2018-11-02 12:10:09,875 main ERROR Error processing element TerminalConsole ([Appenders: null]): CLASS_NOT_FOUND
2018-11-02 12:10:09,875 main ERROR Error processing element LoggerNamePatternSelector ([PatternLayout: null]): CLASS_NOT_FOUND
2018-11-02 12:10:09,883 main ERROR Unable to locate appender "Console" for logger config "root"

I'm not really sure where to look to fix this, so I apologise if resources to solve this problem already exist.

5 minutes ago, TheJ-max04 said:

I'm not really sure where to look to fix this

Post your code.

I'd be happy to, but I assure you, the issue was there from the moment I got forge running in eclipse, even when I hadn't set up a mod.

Here's the only piece of code that actually references the logger:

package OurMod.common;

import java.util.Random;

import net.minecraft.block.Block;
import net.minecraft.block.material.Material;
import net.minecraft.creativetab.CreativeTabs;
import net.minecraft.entity.passive.EntityCow;
import net.minecraft.init.Blocks;
import net.minecraft.init.Items;
import net.minecraft.item.Item;
import net.minecraft.item.ItemBlock;
import net.minecraft.item.ItemStack;
import net.minecraft.util.ResourceLocation;
import net.minecraftforge.common.MinecraftForge;
import net.minecraftforge.event.RegistryEvent;
import net.minecraftforge.event.entity.living.LivingDropsEvent;
import net.minecraftforge.fml.common.Mod;
import net.minecraftforge.fml.common.Mod.EventHandler;
import net.minecraftforge.fml.common.SidedProxy;
import net.minecraftforge.fml.common.event.FMLInitializationEvent;
import net.minecraftforge.fml.common.event.FMLPostInitializationEvent;
import net.minecraftforge.fml.common.event.FMLPreInitializationEvent;
import net.minecraftforge.fml.common.eventhandler.SubscribeEvent;
import net.minecraftforge.fml.common.registry.GameRegistry;

import org.apache.logging.log4j.Logger;

import OurMod.common.client.ClientProxy;

@Mod(modid = OurMod.MODID, name = OurMod.NAME, version = OurMod.VERSION)
public class OurMod
{
    public static final String MODID = "ourmod";
    public static final String NAME = "Our Mod";
    public static final String VERSION = "alpha 1";
    public static Logger logger;
    
    public static final String CLIENT = "OurMod.common.client.ClientProxy";
    public static final String SERVER = "OurMod.common.client.ServerProxy";
    @SidedProxy(clientSide = CLIENT, serverSide = SERVER)
    public static IProxy proxy;
    
    @EventHandler
    public void preInit(FMLPreInitializationEvent event)
    {
    	logger = event.getModLog();
    	proxy.preInit(event);
    }
    
    @EventHandler
    public void init(FMLInitializationEvent event)
    {
    	proxy.init(event);
    }
    
    @EventHandler
    public void postInit(FMLPostInitializationEvent event)
    {
    	proxy.postInit(event);
    }
}

I have lots of other files, but they are all very surface level stuff. I'm thinking there must be a problem with my setup.

This happens in Intellij as well. The logging works in forge 2705 and does not work in 2768.

Use a constant and initialise it with LogManager.getLogger(). (That’s what getting the logger has changed to / will change to in more recent versions) Works for me in Forge 2729 and 2768

I've been using LogManager.getLogger() all along. This doesn't work any longer. I recently changed to using event.getModLog() in FMLPreInitialzationEvent per the documentation in the FMLPreInitializationEvent class. This doesn't work in 2768 but does work in 2705. 

Sorry, just realised - Start a new thread, don't hijack someone else's. And post your code in the new thread

Sorry, I am not asking for help. Just trying to back up what TheJ-max04 is saying. The logger appears to be broken for deobfuscated environments like Eclipse or Intellij. And I'm out....

Has anyone found a solution?

Please don't necro old threads. If you have an issue make your own thread.