1.0.1.24-hotfix
Compatibility
Required content
Changes
Tinker's Newlife 1.0.1.24-hotfix This is a hotfix on top of 1.0.1.24 and contains exactly one change: log spam.
The log was flooded with Tool stack constructed using non-modifiable tool (Render thread, ~120 lines/second) Symptom: while the "Construct / blueprint" item-picker screen was open, the log spammed that warning at roughly 120 lines per second; crafting Tinker bullets or using Miner's Vision also produced occasional entries. Cause: the warning itself is printed by TConstruct (ToolStack warns when handed a Tinker tool item without NBT). This mod was the caller: ConstructSelectScreen created new ItemStack(tinker tool) every frame to draw icons, and two Tinker tools were visible in the grid — two warnings per frame, ~120/s. Fixed: Construct screen: display stacks for Tinker items are now initialised once and cached (ToolStack.createTool(..., MaterialNBT.EMPTY) + updateStack), reused for rendering and tooltips; Tinker bullets: ammo is initialised via createTool instead of ToolStack.from on an empty stack; Materialisation and Miner's Vision: check ToolStack.isInitialized first and treat empty stacks as "no materials / no modifier". For players: just install this build — no TConstruct config change needed. For absolute silence, set logInvalidToolStack to IGNORE in config/tconstruct-common.toml (default WARNING). Notes Version 1.0.1.24-hotfix (same baseline as 1.0.1.24, only this fix differs). Replace the old tinkersnewlife-1.0.1.24.jar; do not install both. Not yet verified in-game.
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:QHl6W6lh:q00rIAxj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QHl6W6lh:q00rIAxj"
}

