Jump to content
View in the app

A better way to browse. Learn more.

Forge Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Featured Replies

Posted

Normally when you start minecraft (usually through the generated run configurations), your mcmod.info will contain stuff like `${version}` and `${mcversion}`. While I am aware that these will be fixed when actually building the code (processResources is called), I want to be able to run them in addition to my `replaceIn` and `replace` snippets before being able to test. Obviously the generated configurations will not have this happen. I considered runClient, and for a while it actually used to work, but now it no longer works, and I am at a loss. Additionally, while `processResources` works perfectly fine as I'm building, the `replace` stuff does not. How can I resolve these issues?

 

build.gradle

buildscript {
    repositories {
        jcenter()
        maven {
            name = "forge"
            url = "https://files.minecraftforge.net/maven"
        }
    }
    dependencies {
        classpath "net.minecraftforge.gradle:ForgeGradle:2.1-SNAPSHOT"
    }
}

apply plugin: "net.minecraftforge.gradle.forge"

version = "0.1"
group = "org.frontear"
archivesBaseName = "MyMod"
targetCompatibility = sourceCompatibility = JavaVersion.VERSION_1_8

minecraft {
    version = "1.8.9-11.15.1.2318-1.8.9"
    mappings = "stable_22"

    replaceIn 'MyMod.java'
    replace '${modid}': archivesBaseName.toLowerCase(), '${version}': project.version
}

repositories {
    mavenCentral()
}

processResources {
    // this will ensure that this task is redone when the values change.
    inputs.property "modid", archivesBaseName.toLowerCase()
    inputs.property "name", archivesBaseName
    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 modid, name, version and mcversion
        expand "modid": archivesBaseName.toLowerCase(), "name": archivesBaseName, "version": project.version, "mcversion": project.minecraft.version
    }

    // copy everything else, thats not the mcmod.info
    from(sourceSets.main.resources.srcDirs) {
        exclude "mcmod.info"
    }
}

 

MyMod.java

package org.frontear.mymod;

import net.minecraft.init.Blocks;
import net.minecraftforge.fml.common.Mod;
import net.minecraftforge.fml.common.event.FMLInitializationEvent;

@Mod(modid = "${modid}", version = "${version}") public class MyMod {
	@Mod.EventHandler public void init(FMLInitializationEvent event) {
		// some example code
		System.out.println("DIRT BLOCK >> " + Blocks.dirt.getUnlocalizedName());
	}
}

 

mcmod.info

[
  {
    "modid": "${modid}",
    "name": "${name}",
    "description": "Blah blah blah, something something something",
    "version": "${version}",
    "mcversion": "${mcversion}",
    "url": "",
    "updateUrl": "",
    "authorList": [
      "Frontear"
    ],
    "credits": "",
    "logoFile": "",
    "screenshots": [],
    "dependencies": []
  }
]

 

Edited by Frontear

I am a human and this action was performed manually. Please contact Frontear if you have any questions or concerns.

  • Author

I just restarted my IDE and everything decided to work fine. I just had to fix an issue with `MISSING REPLACEMENT DATA FOR RUN_DIR`, which was fixed by adding `runDir = "run"` into the `minecraft` area. 

I am a human and this action was performed manually. Please contact Frontear if you have any questions or concerns.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.