All versions
1.1.0
Release
Devourer of Gods 1.1.0last month 15.2K
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Unavailable version
Changes
V1.1.0 (Performance patch & Misc features)
Performance
- Model LOD - Segments that's past a configurable distance will now draw less cubes.
- Buried-segment culling - Segments that's burried in the ground and not visible to any player will now be not rendered
- Removed an unessesary animation controller that ran every tick
- Removed entity shadows on DoG
- Optimized Boss Bar draw calls - The music analyzer was lagging quite a bit in phase two, now simular ones are batched together. Little impact on visuals
- Chunk tickets - No longer force loads chunks in a 3x3 radius when dashing (causes severe lag on specific modpacks), instead now only ticking around head, and load-only for the rest of the body.
- Effect lifetimes moved to client tick (more reliable)
- Removed redundent per-frame entity scan (that existed for some reason, I'm kinda stupid)
Mod now runs fine on an i7-2600 👍️
Drops & Loot
- New music disc (Sprite by bobasuar!) - Scourage of the Universe (Eulogy for the Ego) by DM DOKURO. Guarenteed drop upon first kill, 10% after (First kill is a loot condition
dog:first_kill) - Drops now glow and never despawn
/dog disc resetrearms the firstkill, ops only
Moddability
- Taunts are now datapack-driven - check mod description
- Added
#forge:bossestag to DoG head - Server config (common) now syncs to client upon join & edit
Fixes
- DoG going invisible while alive & attacking
- Departure cinematic not showing for players who died and respawned
- Canon lines being interrupted by taunts
Changes
- Default config updated. If you have old configs, run
/dog config defaults - Summon item no longer gets consumed by default
Notifiers
- Warning when view & simulation distance below 12 (common cause for segments dissapearing & going invisible)
- Warning when default config is now outdated
Optional dependencies
Any compatible version
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:xbaJsoWt:Mmiakzph"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xbaJsoWt:Mmiakzph"
}

