Tags
Creators
Details
All versions
2.0.0+26.1.2
Beta
Auto Totem+ 2.0.0+26.1.2 (also broken)3 months ago 62
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Client-side
Changes
AutoTotem+ 26.1.2 Port Changelog
Bug fixes: Totem not protecting on death in multiplayer and totem duplication in singleplayer have both been fixed.
Build (build.gradle)
- Loom plugin ID:
fabric-loom→net.fabricmc.fabric-loom - Removed
mappingsline (no longer needed, 26.1 is unobfuscated) - Removed
splitEnvironmentSourceSets() modImplementation/modCompileOnly→implementation/compileOnly- Added
localRuntimefor ModMenu so it loads in dev without bundling - MC version:
26.1→26.1.2 - Fabric API:
0.144.3+26.1→0.149.0+26.1.2 - ModMenu:
14.0.0-beta.1→18.0.0-alpha.8 - Java compatibility set to 25
fabric.mod.json
- Version string updated to
26.1.2 - Minecraft dependency updated to
26.1.2 fabric-key-binding-api-v1→fabric-key-mapping-api-v1
AutoTotemMod.java
KeyBindingHelper→KeyMappingHelper(packagekeymapping.v1)registerKeyBinding→registerKeyMapping- Keybinding category: plain string →
KeyMapping.Category.register(Identifier.fromNamespaceAndPath(...)) Identifierimport:net.minecraft.resources.Identifier- Added
sendSystemMessageon toggle for enable/disable chat feedback - Fixed: totem not protecting on death in multiplayer — replaced client-side inventory swap with proper server-synced packet sequence:
ServerboundSetCarriedItemPacketto select hotbar slot with totemServerboundPlayerActionPacket(SWAP_ITEM_WITH_OFFHAND)to move to offhandServerboundContainerClickPacket(QUICK_MOVE)to move totem from inventory to hotbar if needed- Restores original hotbar selection after equip
- Fixed: totem duplication in singleplayer — caused by same client-side only swap desync, resolved by above
AutoTotemConfigScreen.java
GuiGraphics→GuiGraphicsExtractorrender(...)override →extractRenderState(...)drawString/drawCenteredString→graphics.text(...)- All color values require full ARGB with alpha: e.g.
0xFFFFFF→0xFFFFFFFF - Removed
EditBox.setFilter()— method no longer exists in 26.1 - Added keybind display showing current toggle key
- Added tick delay label and description explaining what the value does
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:uWKQfxMw:O9w8udLb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uWKQfxMw:O9w8udLb"
}

