Links
Tags
Creators
Details
1.1.1
Compatibility
Changes
Changes
disable-collisionsis nowfalseby default. With collisions off, entity cramming no longer kills silverfish, so if a farm keeps running while nobody kills them, they pile up without any limit and can bring the TPS down a lot. With collisions on, cramming keeps at most 24 in the same spot.
You can still set disable-collisions: true for a bigger saving (about 35% to 57% instead of 20% to 35%) if silverfish are always killed soon after they arrive. See the README for details.
Default config
enabled: true
disable-collisions: false
prevent-drowning: true
push-off-campfires: true
worlds: []
Requirements
- Paper 26.2
- Java 25
Updating
Replace the jar and restart the server. Your config file is kept as it is, so if it has disable-collisions: true, change it to false yourself and run /fsf reload.
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:xANx2Obd:3dET5kOq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xANx2Obd:3dET5kOq"
}

