NTM on Modrinth

NTM on CurseForge

Official NTM Wiki

Bobcat's Blog (the blag), you can find lengthy yapping, upcoming features and some secrets here.

This is for 1.7.10! For 1.12, check out these projects:

• NTM Reloaded: https://github.com/TheOriginalGolem/Hbm-s-Nuclear-Tech-GIT/releases
• NTM Extended Edition (Alcater): https://github.com/Alcatergit/Hbm-s-Nuclear-Tech-GIT/releases

For 1.18, try Martin's remake: https://codeberg.org/MartinTheDragon/Nuclear-Tech-Mod-Remake/releases

Simply navigate to "Releases" on the right side of the page, download links for the compiled JAR as well as the corresponding source code are under the "Assets" category below the changelog. Make sure to review all changelogs when updating!

Tired of waiting until the next version comes out? Here is a tutorial on how to compile the very newest version yourself: Please note that these installation instructions are assuming you're running Microsoft Windows operating system. Linux users should know what to do by looking at the same guide.

1. Make sure you have JDK8 installed. If not, download it from adoptium.net
2. If you don't have git installed, download&install it from here.
3. Open up "Git Bash":
   • Press Windows Button, type "Git Bash" and press ENTER
4. Enter the directory where you would like the sources to be (advanced users can use any directory)

    cd $HOME/Downloads

5. Download the source code:

    git clone https://github.com/HbmMods/Hbm-s-Nuclear-Tech-GIT.git

4. Enter the source code directory

    cd Hbm-s-Nuclear-Tech-GIT

5. Build the mod

    ./gradlew build

6. Locate the mod file.
   1. Open up your file explorer.
   2. Navigate to the location where you downloaded the sources.
      • If you exactly followed step 1, it should be C:/Users/%USER%/Downloads.
   3. Enter the downloaded source tree.
   4. Navigate to build/libs.
   5. Grab the "HBM-NTM-.jar" one.
      • This is your mod file. You can install it like any other mod by putting it into your mods directory.

If you want to make some changes to the mod, follow this guide:

1. Follow steps 1-2 from Building from source section
2. Create a directory where the repository will reside, using a name that is not "Hbm-s-Nuclear-Tech-GIT"
3. Download the forge src from here and extract it into the directory.
4. Download the source code:

• Using Git Bash, enter wherever your directory is located:

    cd $HOME/Downloads

• Download the source code:

    git clone https://github.com/HbmMods/Hbm-s-Nuclear-Tech-GIT.git

• Move or copy every file within the new folder into your directory, making sure to overwrite any files.
• Feel free to delete the remaining folder and rename your directory (such as "Hbm-s-Nuclear-Tech-GIT")

5. Enter the source directory

    cd Hbm-s-Nuclear-Tech-GIT

6. Setup forge decompilation workspace

    ./gradlew setupDecompWorkspace

7. Generate eclipse files

    ./gradlew eclipse

8. Switch to the eclipse folder inside your directory as a workspace.
9. If necessary, make sure that Eclipse is using the JDK8.
   • On Linux, enter Windows>Preferences>Java>Installed JREs.
     • Click search to navigate to /usr/lib/jvm and open it. Select the Java 8 JDK (e.g., java-8-openjdk).
     • Afterwards, enter Execution Environment, select JavaSE-1.8, and select the jre listed as a [perfect match]
   • On Windows, you may need to set your JAVA_HOME.
     • Search for Environment Variables and click Edit the System Environment Variables.
     • Click Environment Variables. Click new under System Variables.
     • Enter JAVA_HOME under Variable Name and enter the path to your JDK 8 under Variable Value (e.g., C:\Program-Files\Java\jdk1.8.0_102).
     • In Eclipse, now enter Windows>Preferences>Java>Installed JREs.
     • Click Add Standard VM; in the JRE home, navigate to the directory where the JDK is installed, then click finish and select it.
10. Code!

Weapon animations in NTM are stored in JSON files, which are used alongside OBJ models to produce high quality animations with reasonable filesizes. Import/Export Blender addons are available for versions 2.79, 3.2, and 4.0 in tools, and they should function reasonably well in newer versions as well. See the comments in the header of the export scripts for usage instructions.

NTM has certain behaviors intended to fix vanilla code or to increase compatibility in certain cases where it otherwise would not be possible. These behaviors have the potential of not playing well with other mods, and while no such cases are currently known, here's a list of them.

Thermos servers (along with its forks such as Crucible) have a "performance" feature that causes all tile entity ticking to slow down if there's no player present in the same chunk. For obvious reasons, this will heavily impact machines and cause phantom issues that, not having knowledge of this "performance" feature, are near impossible to diagnose. By default, NTM will crash on servers running the Thermos base code and print a lengthy message informing server owners about this "performance" feature as well as how to fix the issues it causes. The error message is printed in plain English on the top of the crash log, failure to read (as well as understand) it will leave the server inoperable.

One of the most common "performance" mods on 1.7.10, Optifine, achieves an increase in performance by breaking small things in spots that are usually hard to notice, although this can cause severe issues with NTM. A short list of problems, along with some solutions, follows:

• Get rid of Optifine and use one of the many other, less intrusive performance mods.
• Blocks with connected textures may become invisible. This can be fixed by toggling triangulation (I do not know what or where this setting is, I just have been told that it exists and that it can fix the problem) or multicore chunk rendering (same here).
• Entity "optimization" has a tendency to break chunkloading, this is especially noticeable with missiles which rely heavily on chunkloading to work, causing them to freeze mid-air. It's unclear what setting might fix this, and analysis of Optifine's source code (or rather, lack thereof) has not proven useful either.

In older versions, Angelica caused issues regarding model rendering, often times making 3D models transparent. Ever since the switch to VBOs, models work fine. Another issue was blocks with connected textures not rendering at all, but this too was fixed, meaning as of time of writing there are no major incompatibilities known with Angelica. However there a few minor issues that persist, but those can be fixed:

• Often times when making a new world, all items appear as white squares. Somehow, scrolling though the NEI pages fixes this permanently
• Reeds will render weirdly, this is an incompatibility with the "Compact Vertex Format" feature. Disabling it will make reeds look normal

NTM adds a few small things to the skybox using a custom skybox renderer. Minecraft can only have a single skybox renderer loaded, so setting the skybox to the NTM custom one would break compatibility with other mods' skyboxes. To mend this, NTM employs a chainloader. This chainloader will detect if a different skybox is loaded, save a reference to that skybox and then use NTM's skybox, which when used will also make sure to run the previous modded skybox renderer. In the event that NTM's skybox were to cause trouble, it can be disabled with the config option 1.31_enableSkyboxes.

A world provider is a piece of code that minecraft can load to determine certain aspects of how the world should be handled, like light levels, sky color, day/night cycle, etc. In order for the Tom impact effects to work, NTM employs such a world provider, although this is known to cause issues with Hardcore Darkness. The world provider can be disabled with the config option 1.32_enableImpactWorldProvider.

An often overlooked aspect of Minecraft is its stats, the game keeps track of how many of an item were crafted, placed, broken, etc. By default, Minecraft can only handle vanilla items, modded items would not show up in the stats window. Forge does little to fix this, and since NTM has to keep track of certain things (such as the use of an acidizer for spawning Mask Man) it will run its own code which re-registers all stats for all modded items. In the event that re-registering causes issues, or another mod already does this better already, this behavior can be disabled with the config option 1.33_enableStatReRegistering.

An often annoying aspect of modded Minecraft is its keybinds. Even though multiple binds can be assigned the same key, all but one will show up as "conflicting" and only the non-conflicting one will work. Which one this is is usually arbitrary, and there is no reason to have such limitation. Often times keybinds are only applicable in certain scenarios, and a commonly found degree of overlap is within reason. Therefore, NTM will run its own key handling code which allows conflicting keybinds to work. If there should be any issues with this behavior, it can be disabled with the config option 1.34_enableKeybindOverlap.

There is a common crash caused by Minecraft's render distance slider going out of bounds, this usually happens when uninstalling a mod that extends the render distance (like Optifine) or when downgrading the Minecraft version (newer versions have higher render distance caps). To prevent crashes, the mod will attempt to decrease the render distance if it's above 16 unless Optifine is installed. If this behavior is not desired (for example, because another mod that allows higher render distance is being used), it can be disabled with the config option 1.25_enableRenderDistCheck.

In some modpacks (exact mods needed to replicate this are unknown), it's possible that invalid registered items may cause problems for NEI handlers. To prevent crashes, the ComparableStack class used to represent stacks will default to a safe registered item, and print a log message. In certain situations, this may cause dozens of errors to be printed at once, potentially even lagging the game. If that happens, the log message (but not the error handling) can be disabled with the config option 1.28_enableSilentCompStackErrors.

By default, the sound system only allows a limited amount of sounds to run at once (28 regular sounds and 4 streaming sounds), this causes issues when there's many machines running at once, since their looped sounds will constantly interrupt each other, causing them to immediately restart, which in some isolated cases has proven to cause massive lagspikes. To prevent this, NTM will increase the sound limit to 1000 regular sounds and 50 streaming sounds, this can be disabled with the config option 1.39_enableSoundExtension.

This software is licensed under the GNU Lesser General Public License version 3. In short: This software is free, you may run the software freely, create modified versions, distribute this software and distribute modified versions, as long as the modified software too has a free software license (with an exception for linking to this software, as stated by the "Lesser" part of the LGPL, where this may not be required). You win this round, Stallman. The full license can be found in the LICENSE and LICENSE.LESSER files.