Tags
Creators
Details
Licensed LGPL-3.0-only
Published 4 years ago
All versions
1.0.27X4347
Beta
Hbm's Nuclear Tech Mod 1.0.27X4347 for Minecraft 1.7.104 years ago 234
Compatibility
Minecraft: Java Edition
1.7.10
Platform
Forge
Supported environments
Client and server
Changes
Added
/ntmreload- Reloads custom recipes
- Will print the exception code to chat and the entire stacktrace to the log if something goes wrong
- Herbal paste
- Combines the effects of pirfenidone, siox and weak radaway
- Comes with a ton of bad side effects, as well as potion sickness
- Much cheaper than "proper" medication
- Dead plants
- Makes oily wastelands much more fashionable
[ Press F1 for help ]- Also known as "world in a jar" or "stare"
- A cheap knockoff of Create's ponder system
- Currently offers presentations on:
- SILEX & FEL
- Firebox
- Stirling engine
- Gas centrifuge
- FEnSU
- More educational presentations will come out soon!
Changed
- V1 no longer reduces max health
- Removed factory cores and tile entities for good
- Too bad that the average factory user can't read
- Removed dynospheres, good riddance
- Nightshade can now be crafted into poison powder
- Foxglove can be used to make herbal paste or stimpaks
- Updated some plant textures
- Shredders can now use custom recipes (largely untested, be careful)
Fixed
- Fixed custom recipe inputs without meta specified defaulting to meta 2 instead of 0
- Fixed misleading tooltip regarding heat produced by RBMK fuel rods
- Fixed duckoids being able to receive digamma
- Fixed FEL laser often rendering behind the SILEX instead of going through it
- Fixed BAT9000 and heavy magnetic storage not dropping anything when broken
- Fixed battery delta display being inconsistent in IO mode
- Fixed autocrafter being able to receive stacks >1 containing items with containers
Compat
- Added an compat class for external use (
com.hbm.util.CompatExternal) - The class and the methods within will always remain the same from an API standpoint, the implementation might change in the future
- Offers the following static methods:
getCoreFromPos(World world, int x, int y, int z) returns TileEntity: uses the multiblock system to obtain the core tile entity from any block that is part of the multiblockgetBufferedPowerFromTile(TileEntity tile) returns long: returns the power stored within that tilegetMaxPowerFromTile(TileEntity tile) returns long: returns the capacity of that tilegetEnergyPriorityFromTile(TileEntity tile) returns int: returns a charge priority 0-2getFluidInfoFromTile(TileEntity tile) returns ArrayList<Object[]>: returns a list of all internal fluid tanks of that tile
- For more information, check out the javadocs within the class
MD5: b59bb35e0c7e98b99a9a0670bea88386
SHA1: a80421556518346b906febd801092b8f60ff84a0
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:M4Z75E5X:b0E3M3Sc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:M4Z75E5X:b0E3M3Sc"
}

