Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/hbmmods/hbm-s-nuclear-tech-git/llms.txt

Use this file to discover all available pages before exploring further.

HBM’s Nuclear Tech Mod uses a standard Minecraft Forge 1.7.10 Gradle build chain. Building from source lets you test the absolute latest changes before they appear in a numbered release, or iterate on your own modifications without waiting for a full release cycle. The process is straightforward on both Windows and Linux, though you must use JDK 8 — no other Java version is supported by ForgeGradle 1.x. This guide walks through every step from a fresh machine to a working .jar file, and also covers how to depend on a published NTM release from Maven when you are writing your own addon mod.

​
Prerequisites

Before you begin, make sure the following tools are available on your machine:
ToolMinimum versionDownload
JDK 8 (Temurin recommended)8u302+adoptium.net
GitAny recent versiongit-scm.com
Forge 1.7.10 src (for IDE setup only)10.13.4.1614files.minecraftforge.net
Linux users: The steps below are written for Windows / Git Bash, but Linux equivalents are obvious — replace gradlew.bat with ./gradlew and use your distribution’s package manager to install git and openjdk-8-jdk.

​
Building the JAR (headless / CI)

Use this flow when you just want a compiled .jar — no IDE needed.
1

Install JDK 8 and Git

Download and install Temurin JDK 8 and Git. On Windows, open Git Bash for all subsequent commands.
2

Clone the repository

cd $HOME/Downloads
git clone https://github.com/HbmMods/Hbm-s-Nuclear-Tech-GIT.git
cd Hbm-s-Nuclear-Tech-GIT
3

Run the build

./gradlew build
Gradle will automatically download ForgeGradle, deobfuscate Minecraft, compile all sources, and produce the output JARs. This step requires an active internet connection on the first run and may take several minutes.
4

Locate the output JAR

After the build finishes, navigate to build/libs/ inside the cloned directory. Grab the file named HBM-NTM-<version>.jar (the plain one — not :dev or :src). Drop it into your Minecraft mods/ folder like any other mod.
build/libs/
├── HBM-NTM-1.0.27_X5719.jar        ← install this
├── HBM-NTM-1.0.27_X5719-dev.jar    ← development artifact
└── HBM-NTM-1.0.27_X5719-src.jar    ← sources

​
IDE Setup for Eclipse

Eclipse is the officially supported IDE for NTM development, as ForgeGradle 1.x ships an eclipse task that generates .classpath and .project files automatically.
1

Merge Forge src into the cloned directory

Download the Forge 1.7.10 source distribution from files.minecraftforge.net and extract it into a directory. Then copy/move all files from the cloned Hbm-s-Nuclear-Tech-GIT folder into that Forge directory, overwriting any conflicts.
2

Run setupDecompWorkspace

./gradlew setupDecompWorkspace
This decompiles and deobfuscates Minecraft so that you can browse vanilla code inside the IDE.
3

Generate Eclipse project files

./gradlew eclipse
4

Open the workspace in Eclipse

In Eclipse, switch to the eclipse/ subdirectory inside your project directory as the workspace root. Eclipse will pick up the generated .project automatically.
5

Configure JDK 8 in Eclipse

  1. Search for Environment Variables → Edit the System Environment Variables.
  2. Under System Variables, click New.
  3. Set Variable Name to JAVA_HOME and Variable Value to the JDK 8 installation path (e.g., C:\Program Files\Java\jdk1.8.0_102).
  4. In Eclipse, go to Window → Preferences → Java → Installed JREs.
  5. Click Add Standard VM, navigate to the JDK 8 directory, and click Finish. Select it as the default.
6

Start coding

Your workspace is ready. Source changes are hot-reloaded inside the Forge development run configuration generated by ./gradlew eclipse.

​
IDE Setup for IntelliJ IDEA

IntelliJ does not receive a dedicated ForgeGradle 1.x task in NTM’s build.gradle, but the standard Forge 1.7.10 IntelliJ workflow works fine.
1

Run setupDecompWorkspace

./gradlew setupDecompWorkspace
2

Import the Gradle project

Open IntelliJ and choose File → Open, then select the build.gradle file in the repository root. IntelliJ will import the Gradle project and resolve all dependencies automatically.
3

Set the Project SDK to JDK 8

Go to File → Project Structure → Project and set the SDK to your installed JDK 8 (version 1.8). Do the same under File → Project Structure → Modules if needed.
4

Run the Minecraft client

Use the Gradle tool window (View → Tool Windows → Gradle) and run the runClient task, or create an Application run configuration pointing to GradleStart with the working directory set to eclipse/.
IntelliJ occasionally ignores the sourceCompatibility = '1.8' setting defined in build.gradle and compiles with a newer SDK. If you see UnsupportedClassVersionError at runtime, double-check that both the Project SDK and the Gradle JVM (under Settings → Build, Execution, Deployment → Build Tools → Gradle) are set to JDK 8.

​
Using NTM as a Maven Dependency

NTM publishes pre-built JARs to its own Maven repository at https://maven.ntmr.dev/releases. Each release is versioned as 1.0.27_X{buildNumber} — for example, 1.0.27_X5687. Three classifiers are published per build:
ClassifierUse case
(none)Re-obfuscated runtime JAR — install in mods/
:devDeobfuscated artifact for compile-time IDE resolution
:srcSources JAR for IDE source attachment
Add the following to your mod’s build.gradle: 
repositories {
    maven {
        name "NTM Releases"
        url "https://maven.ntmr.dev/releases"
    }
}

dependencies {
    def ntmBuildNumber = "5687" // change to the release you need

    implementation "com.hbm:HBM-NTM:1.0.27_X${ntmBuildNumber}:dev"
    compileOnly   "com.hbm:HBM-NTM:1.0.27_X${ntmBuildNumber}:src"
}
The :dev artifact is a non-obfuscated JAR that lets ForgeGradle resolve NTM class names during compilation without re-obfuscation issues. The :src artifact is optional but highly recommended — it wires source code into your IDE so you can browse NTM internals directly.
The group ID is com.hbm and the artifact ID is HBM-NTM. Check the Modrinth releases page or GitHub Releases for the latest build number.

​
Platform Notes

  • Use Git Bash (installed with Git for Windows) rather than cmd.exe or PowerShell. The gradlew wrapper is a shell script.
  • If Gradle cannot find javac, set the JAVA_HOME environment variable to your JDK 8 installation directory (e.g., C:\Program Files\Java\jdk1.8.0_102) and restart Git Bash.
  • Avoid placing the repository in a path with spaces (e.g., C:\Users\My User\Downloads). Use a short, space-free path like C:\Dev\ntm.

Build docs developers (and LLMs) love

Get started for freeTalk to us