Tags
Creators
Details
Licensed LGPL-3.0-only
Published 2 years ago
Updated 3 weeks ago
All versions
2.0.0
Release
Florum Sporum 2.0.0 (1.21.11)- I Used To Rule The World10 months ago 1,386
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
➕ Additions
- Added seven gamerules for the purpose of configuring some of Florum Sporum's server-side behaviors. Consider this the "first pass", and make sure to report any bugs you find!
| Registry Identifier | Description | Default Value | Value Bounds |
|---|---|---|---|
florum-sporum:spore_blossom_growth_chance |
The chance for a spore blossom to advance one growth stage, per random-tick. Set to 0 to disable random-tick growth. | 0.1 | 0.0...1.0 |
florum-sporum:spore_blossom_unfurl_interval |
The time between spore blossom unfurling stages. | 10 ticks | 1...2,147,483,647 |
florum-sporum:spore_blossom_entity_check_interval |
The time from when an entity leaves the spore blossom's collision box to when it begins unfurling. | 60 ticks | 1...2,147,483,647 |
florum-sporum:panda_default_max_sneeze_interval |
The maximum time between passive panda sneezes. Set to 0 to disable. | 6000 ticks | 0...2,147,483,647 |
florum-sporum:panda_weak_max_sneeze_interval |
The maximum time between passive weak panda sneezes. Set to 0 to disable. | 500 ticks | 0...2,147,483,647 |
florum-sporum:panda_spore_shower_max_sneeze_interval |
The maximum time between panda sneezes when in a spore shower. Set to 0 to disable. | 100 ticks | 0...2,147,483,647 |
florum-sporum:panda_spore_shower_check_depth |
How close the spore blossom needs to be in order to trigger panda sneezes. | 8 blocks | 1...2,147,483,647 |
🔧 Changes
- The codebase now uses official Mojang mappings in preparation (and practice!) for 26.1.
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:3KmV3g7F:ouSPKqqP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3KmV3g7F:ouSPKqqP"
}

