Another mcmod.Info Issue.

[TrueSalt]

Okay, so lets cut out the middle man and let me just say that I have been looking for hours to no avail on how to get my mcmod.info file to actually appear in-game. I will do the same that another poster did, though his post doesn't help as I believe it is for an older version and as such the issue may have returned at some point along the way. I am using the latest version of Forge 1.12.2, Java version 1.8.0_221 x64, and am doing this in IntelliJ IDEA. The strangest thing about this all is that over on a friends PC, he got the mcmod.info file to register in-game with literally everything being the same. I think that is what is throwing me off so much right now.

All the code:

  Reveal hidden contents

 

minedditions.java

package com.coarsed.minedditions;

import net.minecraft.init.Blocks;
import net.minecraftforge.fml.common.Mod;
import net.minecraftforge.fml.common.Mod.EventHandler;
import net.minecraftforge.fml.common.event.FMLInitializationEvent;
import net.minecraftforge.fml.common.event.FMLPostInitializationEvent;
import net.minecraftforge.fml.common.event.FMLPreInitializationEvent;
import org.apache.logging.log4j.Logger;

@Mod(modid = minedditions.MODID, name = minedditions.NAME, version = minedditions.VERSION)
public class minedditions
{
    public static final String MODID = "minedditions";
    public static final String NAME = "Minedditions";
    public static final String VERSION = "Dirt";

    private static Logger logger;

    @EventHandler
    public void preInit(FMLPreInitializationEvent event)
    {
        System.out.println(NAME + " " + VERSION + " is digging straight down!");
        logger = event.getModLog();
    }
    public void init(FMLInitializationEvent event)
    {
		System.out.println(NAME + " " + VERSION + " is going too deep!");
        logger.info("DIRT BLOCK >> {}", Blocks.DIRT.getRegistryName());
    }
    public void postInit(FMLPostInitializationEvent event)
	{
    	System.out.println(NAME + " " + VERSION + " has found diamonds!");
    }

}

 

mcmod.info

[{
	"modid": "minedditions",
	"name": "Minedditions",
	"description": "Additions we believe should be in there.",
	"version": "${version}",
	"mcversion": "${mcversion}",
	"logoFile": "",
	"authors": ["Salt", "Corrupted"],
	"credits": "Coarsed Team",
	"parent": "",
	"screenshots": [],
	"dependencies": []
}]

 

build.gradle

buildscript {
    repositories {
        jcenter()
        maven { url = "https://files.minecraftforge.net/maven" }
    }
    dependencies {
        classpath 'net.minecraftforge.gradle:ForgeGradle:2.3-SNAPSHOT'
    }
}
apply plugin: 'net.minecraftforge.gradle.forge'
//Only edit below this line, the above code adds and enables the necessary things for Forge to be setup.


version = "Dirt"
group = "mod.coarsed.minedditions" // http://maven.apache.org/guides/mini/guide-naming-conventions.html
archivesBaseName = "Minedditions"

sourceCompatibility = targetCompatibility = '1.8' // Need this here so eclipse task generates correctly.
compileJava {
    sourceCompatibility = targetCompatibility = '1.8'
}

minecraft {
    version = "1.12.2-14.23.5.2838"
    runDir = "run"
    
    // the mappings can be changed at any time, and must be in the following format.
    // snapshot_YYYYMMDD   snapshot are built nightly.
    // stable_#            stables are built at the discretion of the MCP team.
    // Use non-default mappings at your own risk. they may not always work.
    // simply re-run your setup task after changing the mappings to update your workspace.
    mappings = "snapshot_20171003"
    // makeObfSourceJar = false // an Srg named sources jar is made by default. uncomment this to disable.
}

dependencies {
    // you may put jars on which you depend on in ./libs
    // or you may define them like so..
    //compile "some.group:artifact:version:classifier"
    //compile "some.group:artifact:version"
      
    // real examples
    //compile 'com.mod-buildcraft:buildcraft:6.0.8:dev'  // adds buildcraft to the dev env
    //compile 'com.googlecode.efficient-java-matrix-library:ejml:0.24' // adds ejml to the dev env

    // the 'provided' configuration is for optional dependencies that exist at compile-time but might not at runtime.
    //provided 'com.mod-buildcraft:buildcraft:6.0.8:dev'

    // the deobf configurations:  'deobfCompile' and 'deobfProvided' are the same as the normal compile and provided,
    // except that these dependencies get remapped to your current MCP mappings
    //deobfCompile 'com.mod-buildcraft:buildcraft:6.0.8:dev'
    //deobfProvided 'com.mod-buildcraft:buildcraft:6.0.8:dev'

    // for more info...
    // http://www.gradle.org/docs/current/userguide/artifact_dependencies_tutorial.html
    // http://www.gradle.org/docs/current/userguide/dependency_management.html

}

processResources {
    // this will ensure that this task is redone when the versions change.
    inputs.property "version", project.version
    inputs.property "mcversion", project.minecraft.version

    // replace stuff in mcmod.info, nothing else
    from(sourceSets.main.resources.srcDirs) {
        include 'mcmod.info'
                
        // replace version and mcversion
        expand 'version':project.version, 'mcversion':project.minecraft.version
    }
        
    // copy everything else except the mcmod.info
    from(sourceSets.main.resources.srcDirs) {
        exclude 'mcmod.info'
    }
}

 

 

 

 

 

Edited August 27, 2019 by TrueSalt
Fixed formating

[DaemonUmbra]

I seem to remember something about mcmod.info not appearing in-game when run in the IDE, try building the mod and running it in a regular client