1.0.1.16-hotfix
Compatibility
Required content
Changes
Tinker's Newlife 1.0.1.16-hotfix
A hotfix on top of 1.0.1.16. Everything from 1.0.1.16 is unchanged except what is listed below.
Fixes
The slingshot can now be assembled at the Tinker Station / Tinker's Anvil
The slingshot's station data was incomplete, so the tool could not be put together in the crafting interface even though the item itself existed. This is now shipped in full:
- Station layout (
tinkering/station_layouts/slingshot.json): three input slots — twotconstruct:bow_limb(bow limbs) and onetconstruct:bowstring(bowstring) — laid out exactly like Tinkers' own longbow, with its ownsortIndexthat does not collide with any other tool of this mod. - Tool definition (
tinkering/tool_definitions/slingshot.json): part listbow_limb / bow_limb / bowstring, primary part 0, random tier-1 default materials, base 120 durability / 0 attack damage / 1.0 attack speed, 1.25x durability multiplier, 1 ability slot + 3 upgrade slots. - Text: the group title, the per-slot labels (bow limb / bow limb / bowstring) and the
group description now exist in both
zh_cnanden_us, so the interface shows real names instead of raw translation keys.
Verification done on this build: the game log reports Loaded 38 station slot layouts and
Loaded 70 tool definitions with no error line for tinkersnewlife:slingshot.
The Missing textures ... _tconstruct_unknown warnings in the same log are normal Tinkers
behaviour for a tool whose display stack carries no materials yet (several other tools of this
mod, including the yoyo, produce the same line) and do not affect the crafting interface.
Notes
Nothing else was changed. This hotfix contains no new items, no balance changes and no recipe changes beyond making the slingshot reachable in the station interface.
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:Oh5HCnWt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QHl6W6lh:Oh5HCnWt"
}

