Tags
Creators
Details
Licensed MIT
Published 3 years ago
Updated 2 weeks ago
All versions
1.21.1-0.12.19
Alpha
1.21.1-0.12.192 weeks ago 133
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
- Arrows shot from Baykok's Bow now do 25% extra damage (like they did in 1.12.2, I apparently forgot to port that over to the newer versions)
- Added the block tag
totemic:supports_tipito specify which blocks Tipis can be placed on - Fixed Baykok's Bow not shooting tipped arrows when they are used
- Fixed waking up outside the Tipi after sleeping in it
- Fixed Wind Chime congestion particles not being visible immediately
- Fixed Totem Pole breaking particles having the wrong color
- (@Spagles) Fixed a potential crash with the ceremony HUD
- (@Spagles) Small performance improvement for ceremonies that affect blocks, such as the Zaphkiel Waltz
- Large-scope internal changes to facilitate future porting to other mod loaders
- KubeJS integration: Added warning when setting an empty or invalid item for a music instrument
- KubeJS integration: Added an explicit error when setting an incorrect number of selectors for a ceremony
- Now requires at least NeoForge version 21.1.233
API changes:
- The API jar now includes compiled class files in addition to the sources
- Moved the parts of the API that are specific to NeoForge (capabilities, data maps, events) to the subpackage pokefenn.totemic.api.neoforge
- CeremonyInstance and DefaultMusicAcceptor no longer implement INBTSerializable (but the (de)serializeNBT methods are still there)
Optional dependencies
Any compatible version
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| Totemic-neoforge-1.21.1-0.12.19-api.jar | Unknown | 57.52 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:tS54LAQx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GLffYJtD:tS54LAQx"
}

