Links
Tags
Creators
Details
Licensed MPL-2.0
Published 3 months ago
Updated 4 months ago
All versions
1.5
Release
Split client/server architecture for 1.21.114 months ago 493
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client and server
Required content
Changes
Pyre 1.5.0 for Minecraft 1.21.11
Second release of Pyre for Minecraft 1.21.11.
Added
- Split side-aware architecture inside one mod jar
- Dedicated client initializer and client-only lifecycle handling
- Client-side explosion effect manager
- Client-side particle budgeting for explosion spam
- Client-side explosion sound coalescing
- Client-side explosion clustering for local effect smoothing
- Separate server and client config sections
- Client-only mixin path for explosion packet handling
- Cleanup for client state on world unload and disconnect
Changed
- Kept the real vanilla-faithful TNT and explosion optimizer on the server or integrated-server path
- Moved shared and server-safe logic under common packages
- Isolated client-only classes from dedicated-server classloading
- Improved side safety and overall project structure
Compatibility
- Client-side smoothing only affects local explosion effects
- Server-side optimization remains the real gameplay-safe optimization path
- Does not change TNT fuse timing, explosion power, block destruction, entity damage, or knockback
- Does not modify packet semantics or rendering backend internals
Notes
- Built for Fabric on Minecraft 1.21.11
- Use the Pyre jar built for Minecraft 1.21.11
- In singleplayer, both server-side optimization and client-side smoothing can run
- In multiplayer without Pyre on the server, only local client-side effect smoothing applies
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:O3sS4ohN:OjM8Keui"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:O3sS4ohN:OjM8Keui"
}

