Tags
Creators
Details
0.2.44
Compatibility
Changes
Additions:
- 26.2 support
- Added option to disable shift buying for a specific item in shop with new
disable-shift-buyingproperty- price: 1 iron stack: 1 stone disable-shift-buying: true - Added new configuration option
spawn-resources-on-game-start. This triggers resource spawn for all spawners right when the game starts. Default isfalse. - Added new config option
specials.tnt-sheep.damageto control the tnt damage of TNT Sheep. You can also use thedamageproperty variable on the item in the shop. Default is whateverspecials.auto-igniteable-tnt.damageis currently set, default of that is4.0. - Custom sounds can now be played. Custom sounds must contain a namespace (like
modname:sound) in order to be considered custom sounds. If the namespace cannot be specified (the server version is 1.8), prefix the sound name with;. - Updated translations for Czech.
Fixes:
- Fixed Warp Powder cloning exploit.
- Fixed Spectator Teleportation exploit.
- Fixed handling of water and waterlogged blocks during rebuild.
- Fixed player respawn countdown being off by 1 second.
- Fixed colors for newly created teams being mislabeled as old 0.2.1 colors in the arena file which caused accidental migration for certain colors.
Changes in 0.2.43.1 (not released on Modrinth, but the changes are included in this new release):
Automatic download of Groovy for using groovy shops is no longer provided. If you want to continue using Groovy shops, you can download (and inspect) the plugin-ized version of the runtime manually: https://repo.screamingsandals.org/public/org/screamingsandals/misc/groovy/3.0.16/groovy-3.0.16.jar
It is recommended to rely on YAML shops as Groovy shops are no longer developed.
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:8sg1aj4I:nUPEYDAm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8sg1aj4I:nUPEYDAm"
}

