Tags
Creators
Details
Licensed MIT
Published 3 years ago
Updated last month
All versions
1.20.1-0.12.18
Release
1.20.1-0.12.189 months ago 1,670
Compatibility
Minecraft: Java Edition
1.20.1
Platforms
Forge
NeoForge
Supported environments
Client and server
Changes
- The Totempedia entries in the Ceremonies category are now locked until the required music instruments are obtained. This should make it less overwhelming for newcomers, as only those Ceremonies will be displayed that are currently performable.
- The Jingle Dress Totempedia entry will now unlock together with the Wind Chime entry.
- In case you get erroneously locked Instrument or Ceremony entries after the update, they should unlock once you place the relevant Instruments in your inventory.
- Added the
medicineBagBlacklistserver config option, which allows specifying Totem Carvings that may not be used in Medicine Bags. - Added a sound when opening, closing or setting the carving of a Medicine Bag.
- Fixed a visual glitch where the music bar in the Ceremony HUD could overflow.
- Added KubeJS integration (documentation pending).
- It can be used mostly the same as in 1.21.1, but an important difference is that, due to a limitation of KubeJS in 1.20.1, you can't use KubeJS's
StartupEvents.registryto register Totemic contents. Instead, useTotemicEvents.registerMusicInstruments, etc.
- It can be used mostly the same as in 1.21.1, but an important difference is that, due to a limitation of KubeJS in 1.20.1, you can't use KubeJS's
API changes: See 1.21.1-0.12.18.
Optional dependencies
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| Totemic-forge-api-1.20.1-0.12.18-sources.jar | Unknown | 25.62 KiB |
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:GLffYJtD:nvkL7sUX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GLffYJtD:nvkL7sUX"
}


