Links
Tags
Creators
Details
Licensed Apache-2.0
Published 2 months ago
Updated last week
All versions
0.1.16
Beta
totem-vanilla-tweaks 0.1.162 months ago 7
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Unavailable version
Changes
TotemVanillaTweaks 0.1.16 Beta
Critical runtime hotfix
- Fixed a Minecraft 26.2 production-runtime crash when a skeleton was loaded or spawned.
- The 0.1.15 distribution could contain a mixed namespace method descriptor (
DifficultyInstance.getDifficulty()returning an intermediaryclass_1267type), causing aNoSuchMethodErrorduring finite skeleton ammunition initialization. - Aligned TotemVanillaTweaks with the existing TotemCore 26.2 build policy by keeping Modern Yarn only as a development naming layer and disabling distribution remapping with
fabric.loom.dontRemap=true.
Verification hardening
- Added a production-runtime Client GameTest gate using Loom's production run task.
- The new regression test boots a real Minecraft 26.2 singleplayer/integrated server in the distribution namespace, summons a skeleton through the server command path, waits for the
ServerEntityEvents.ENTITY_LOADammunition initialization callback, then kills the skeleton. - The production test uses an isolated Gradle dependency cache so named-development Fabric API tweaker normalization cannot contaminate the official production namespace.
- Existing Server GameTests, Client GameTests, and the Dedicated Server + Target Client + Observer Client three-JVM Observer E2E remain release gates.
Requirements
- Minecraft 26.2
- Fabric Loader 0.19.3+
- Fabric API 0.154.2+26.2 or newer compatible 26.2 build
- Java 25+
- TotemCore >=0.7.0 <0.8.0 (0.7.11 recommended)
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:mEcpkZT2:11iXoEVq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mEcpkZT2:11iXoEVq"
}

