English 🇺🇸 / Русский 🇷🇺 / 简体中文 🇨🇳 / 한국어 🇰🇷 / Українська 🇺🇦

HBM's Nuclear Tech Mod Community Edition

A definitive port of HBM's Nuclear Tech Mod from 1.7.10 to 1.12.2, the most completed one among others. Came from necessity as other developers have failed to update and maintain other forks.

Important

FOLLOW THE ISSUE TEMPLATE WHILE REPORTING ISSUES
Due to the amount of issues we get daily, we enforce strict issue report guidelines stated in the templates.
Failure to follow the templates will result in closing and locking of the issue without a warning. Rule does not apply retroactively. Please respect our time and make sure issue reports are of quality.

Note

If you have Universal Tweaks installed, set B:"Disable Fancy Missing Model" to false to fix model rotation
This can be found at config/Universal Tweaks - Tweaks.cfg

Is it survival ready?

While there is still a lot of bugfixing to be done, the mod itself has been proven to be in a state where it can be played in survival without fatal crashes, though it still has many minor/substantial bugs to be fixed and some rather minor things to be ported.

Is the mod compatible with NTM: Extended edition addons/shaders?

Sadly, no. Installing EE addons will most likely result in crashes, making the modpack unplayable; due to having the new gun system ported, shaders are also incompatible and will cause heavy visual artifacts when holding a gun.
Also shaders are incompatible with NTM skybox; this can be fixed in 'config/hbm -> hbm.cfg' by changing the line 'B:1.00_enableSkybox=true' to 'false'.
We're looking forward to fixing shader-related issues, though this will take time.

How different is it from Extended edition?

Extended worlds are fully incompatible!
We have rewritten ~75% of the entire mod, porting every single feature we can. The amount of changes is difficult to track at this point. I invite you to check our GitHub issues, as we use them to track missing/added content.

Why not improve the Extended edition?

Alcater has not updated his version on Curseforge for more than 1.5 years, his version as many performance bottlenecks and weird approaches to implementation of some features. Not to mention his refusal to work with us, hence we decided to fork and work separately.

If it's in development, why publish it on CurseForge?

We seek bug reports.
It is more than obvious to us that without presence on websites such as curse, modrinth, our reach is severely diminished. We want to make players aware that there is a proper port in the works, and therefore help us either via bug reports and directly, via pull requests.We always seek new contributors.

Will this version have modifications for specific mod pack use?

No!
While the port was started as part of the warfactory project, It is maintained as a standalone mod. Any changes are in order to ensure compatibility, stability, or ease development for mod pack developers, however no direct changes for specific mod packs will be implemented.

Will you port it to 1.1x/1.2x?

We don't plan to do so, no.
We need to stay committed to one version at a time. Fragmentation, and the insane amount of separate teams that worked on this mod, is what killed the mod's chance to be ported. This is why we want to centralize our efforts on one version at a time.

For development Java 25 is used!

We have JvmDowngrader to target Java 8 bytecode seamlessly while still using modern syntax and apis.

General quickstart

1. Clone this repository.
2. Prepare JDK 25
3. Run task setupDecompWorkspace (this will setup workspace, including MC sources deobfuscation)
4. Ensure everything is OK. Run task runClient (should open minecraft client with mod loaded)

• Always use gradlew (Linux/MACOS) or gradlew.bat (Win) and not gradle for tasks. So each dev will have consistent environment.

Development quirks for Apple M-chip machines.

Since there are no natives for ARM arch, therefore you will have to use x86_64 JDK (the easiest way to get the right one is IntelliJ SDK manager)

You can use one of the following methods:

• GRADLE_OPTS env variable export GRADLE_OPTS="-Dorg.gradle.java.home=/path/to/your/desired/jdk"
• additional property in gradle.properties (~/.gradle or pwd) org.gradle.java.home=/path/to/your/desired/jdk
• direct usage with -D param in terminal ./gradlew -Dorg.gradle.java.home=/path/to/your/desired/jdk wantedTask

Troubleshooting:

1. If you see that even when using x86_64 JDK in logs gradle treats you as ARM machine. Do following:
   1. Clear workspace git fetch; git clean -fdx; git reset --hard HEAD (IMPORTANT: will sync local to git, and remove all progress)
   2. Clear gradle cache rm -rf ~/.gradle (IMPORTANT: will erase WHOLE gradle cache)
   3. Clear downloaded JVMs rm -rf /path/to/used/jvm (path to used jvm can be found in /run/logs/latest.log like this Java is OpenJDK 64-Bit Server VM, version 1.8.0_442, running on Mac OS X:x86_64:15.3.2, installed at /this/is/the/path)
   4. Repeat quickstart.

Maven

Snapshots

These represent the latest commit for a given version.

repositories {
    maven {
        name "Warfactory Snapshots"
        url "https://repo.warfactory.co/snapshots"
    }
}
dependencies {
    // Java 8, unobfuscated
    implementation "com.hbm:ntm-ce:2.1.1.0-SNAPSHOT:dev"
    // Java 25, unobfuscated
    implementation "com.hbm:ntm-ce-java25:2.1.1.0-SNAPSHOT:dev"
    // Java 8, obfuscated
    implementation "com.hbm:ntm-ce:2.1.1.0-SNAPSHOT"
    // Java 25, obfuscated
    implementation "com.hbm:ntm-ce-java25:2.1.1.0-SNAPSHOT"
}

Releases

These correspond to a CurseForge / Modrinth release.

repositories {
    maven {
        name "Warfactory Releases"
        url "https://repo.warfactory.co/releases"
    }
}
dependencies {
    // Java 8, unobfuscated
    implementation "com.hbm:ntm-ce:2.1.1.0:dev"
    // Java 25, unobfuscated
    implementation "com.hbm:ntm-ce:2.1.1.0:dev-java25"
    // Java 8, obfuscated
    implementation "com.hbm:ntm-ce:2.1.1.0"
    // Java 25, obfuscated
    implementation "com.hbm:ntm-ce:2.1.1.0:java25"
}

Normally you should use unobfuscated jars for development.
If you are on Cleanroom and is using JDK 25 then both Java 8 and Java 25 variants are fine; otherwise the Java 8 ones are recommended.