
Auto Totem
Automatically moves a Totem of Undying from your inventory to your offhand. Toggled on/off via a hotkey (default: O, For 26.2+ = J). Settings menu (key B or via Mod Menu): statistics HUD and totem usage notification HUD. PvP helper. QoL. Fabric
Tags
Creators
Details
2.1.0
Compatibility
Required content
Changes
Changelog
Unreleased
- Fixed two compile errors on 1.21.1-1.21.4 (toggle message, sound check).
- Added contact links and the mod icon.
2.1.0 (Minecraft 1.21.1-1.21.4)
New
- Equip delay: choose how many ticks to wait before the totem goes to your offhand (0 = as fast as possible).
- Health threshold mode (off by default). The totem is moved to your offhand only when your health drops to the threshold you set, and goes back to its slot once you have healed. Optional "equip after first hit" on top of that.
- Custom notification sound: import a WAV, AIFF or AU file from your computer. While it is in use, the normal totem sound is muted so the two don't overlap. Volume is adjustable.
- The settings screen is now a single page split into boxes. Both HUDs are visible and draggable at the same time.
Changed
- The stats HUD is off by default. Existing configs are switched off once on first launch of this version.
- Ported to Mojang's official mappings.
Fixed
- The dark background of the settings screen was drawn on top of the buttons.
- The HUD "size" setting scaled the box but not the text. Now both scale.
- The key category showed up as a raw translation key in the controls menu.
- The stats HUD used hard-coded Russian units regardless of the game language.
- Respawning or changing dimension could count as a totem being used.
- The auto-equip no longer fires in creative and spectator mode, where it only caused desyncs.
2.0.1
- Settings screen, Mod Menu support, stats HUD and notification HUD.
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:Hyjm2AuJ:Bu32rsuW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Hyjm2AuJ:Bu32rsuW"
}
