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 publishes a developer-facing Java API under the api.hbm root package, giving addon authors access to the same power networks, fluid pipelines, radiation system, conveyor belts, and pneumatic tube infrastructure used internally by the mod itself. The API is versioned and distributed through a dedicated Maven repository, so you can depend on a specific build number and receive full IDE support via the provided sources JAR. Because NTM targets Minecraft 1.7.10 with Forge, the API follows the patterns of that era — tile-entity interfaces, ForgeDirection sided logic, and NBT-backed state — all of which are documented below alongside the recommended Gradle setup.

​
Maven Dependency

NTM releases are hosted at https://maven.ntmr.dev/releases. The artifact ships three classifiers:
ClassifierPurpose
(none)Obfuscated runtime JAR (for production)
:devDeobfuscated JAR — use as implementation in your workspace
:srcSource attachment — use as compileOnly for Javadoc/navigation
1

Add the NTM Maven repository

Add the repository declaration to your build.gradle repositories block.
2

Declare the dependencies

Pick a build number from the NTM releases page and substitute it below.
3

Run setupDecompWorkspace

Run ./gradlew setupDecompWorkspace (or the equivalent for your IDE) so ForgeGradle can map the deobfuscated JAR correctly.
build.gradle
repositories {
    maven {
        name "NTM Releases"
        url "https://maven.ntmr.dev/releases"
    }
}

dependencies {
    def ntmBuildNumber = "5687" // Replace with the build you target

    implementation "com.hbm:HBM-NTM:1.0.27_X${ntmBuildNumber}:dev"
    compileOnly  "com.hbm:HBM-NTM:1.0.27_X${ntmBuildNumber}:src"
}
The :dev classifier is the deobfuscated (MCP-named) version of the mod. Always use :dev as your implementation dependency so method names match your development workspace. The base JAR (no classifier) is the production-obfuscated artifact and should not be used during development.

​
Maven Coordinates

FieldValue
Repository URLhttps://maven.ntmr.dev/releases
Group IDcom.hbm
Artifact IDHBM-NTM
Version pattern1.0.27_X{buildNumber}

​
API Package Reference

The api.hbm root splits into focused sub-packages. Each package exposes only the interfaces and helpers you need; NTM’s internal implementation classes remain hidden inside com.hbm.
NTM’s proprietary High Energy (HE) power system. Implement IEnergyProviderMK2, IEnergyReceiverMK2, or IEnergyConductorMK2 to participate in the network. Nodespace and PowerNetMK2 manage the global node registry and per-tick distribution logic. IBatteryItem covers chargeable items such as batteries and capacitors.Not compatible with RF or FE. There is no conversion factor.
The current fluid transport layer. IFluidConnectorMK2 and IFluidConnectorBlockMK2 let tiles and blocks join fluid networks. IFluidPipeMK2 adds node-creation helpers for pipe tile entities. FluidNetMK2 drives per-tick transfer across pressure tiers. IFillableItem covers fluid-carrying items such as canisters and buckets.
The original fluid interfaces — IFluidStandardReceiver, IFluidStandardSender, and IFluidStandardTransceiver — are still functional but marked @Deprecated. They now delegate to their MK2 equivalents. Prefer the fluidmk2 variants for new code.
A collection of block-level capability interfaces: IBlowable and IFuckingExplode for explosion interactions, ICrucibleAcceptor for crucible-compatible blocks, IDrillInteraction and IMiningDrill for drill machinery, IInsertable for item insertion, ILaserable for laser targeting, IPileNeutronReceiver for nuclear pile neutron acceptance, IRadioControllable for radio-frequency control, and IToolable for wrench-like tool interactions.
Four interfaces control the conveyor belt subsystem: IConveyorBelt for belt blocks, IConveyorItem for items that ride conveyors, IConveyorPackage for wrapped item packages, and IEnterableBlock for blocks that items can enter (e.g. chutes).
IRadiationImmune grants an entity complete immunity to NTM radiation. IResistanceProvider allows custom damage threshold/resistance values per incoming damage source — useful for armored or naturally resistant entities. IRadarDetectableNT (preferred) and the deprecated IRadarDetectable make custom entities visible on NTM radar screens. RadarEntry is the data packet sent to clients for radar rendering.
A small collection of item-level capability interfaces: IDepthRockTool for tools that can mine bedrock-equivalent depth rock, IDesignatorItem for missile designator/targeting items, IGasMask for gas mask items with filter slot management, and IGunHUDProvider for items that supply custom status bars and ammo readouts to the gun HUD.
IPneumaticConnector connects tile entities to NTM’s pneumatic tube network for automated item transport. ISlotMonitorProvider exposes an inventory’s slot state to the SlotMonitor / StackCache system, enabling remote inventory inspection by tube controllers.
IRecipeRegisterListener provides a callback invoked during SerializableRecipe.initialize() for each recipe class that loads. Addon mods use this to inject their own recipes into NTM machines at the correct moment in the loading sequence.
ILoadedTile is a base marker used by both the energy and fluid connector hierarchies. IInfoProviderEC exposes data to the EnergyControl monitoring mod. IHeatSource marks tiles that emit heat into the environment.
IRORInfo, IRORInteractive, and IRORValueProvider form the Redstone-Over-Radio subsystem, allowing wireless redstone-like signalling between blocks. RORFunctionException is thrown on invalid function calls through this channel.

​
Inter-Mod Communications (IMC)

The IMC handler system (com.hbm.handler.imc.IMCHandler) is deprecated and no longer recommended. The NTM maintainers note that it is cumbersome to maintain, breaks on recipe reload, and that IRecipeRegisterListener is the correct modern alternative for recipe injection. The IMC handlers for Blast Furnace, Centrifuge, and Crystallizer recipes remain in the codebase for backwards compatibility only.
For runtime integration without a compile-time dependency, IMC messages were once the recommended path. Today, addon mods that need to add recipes should instead implement IRecipeRegisterListener and register it during their FMLInitializationEvent: 
// In your mod's init event
SerializableRecipe.registerListener(new MyRecipeListener());

​
Applied Energistics 2 Compatibility

NTM ships an internal AE2 compatibility handler (ICompatNHNEI) that bridges NTM’s item and fluid networks with AE2’s network storage and crafting pipeline. Addons that need to expose custom NTM-adjacent items to AE2 should follow the same NEI/AE2 registration patterns NTM uses internally — registering items through Forge’s ore dictionary and ensuring NEI handler compatibility via the IMCHandlerNHNEI pathway.

​
Explore the API

Energy API

Implement IEnergyProviderMK2, IEnergyReceiverMK2, or IEnergyConductorMK2 to connect your tile entities to NTM’s HE power network.

Fluid API

Connect to the MK2 fluid network with IFluidConnectorMK2, or carry fluids on items with IFillableItem.

Hazard API

Register radiation values for your items and make entities radiation-aware with IRadiationImmune and IResistanceProvider.

Build docs developers (and LLMs) love

Get started for freeTalk to us