
Acid of Rain
In this plugin, a danger zone has been created that simulates acid rain with four threat levels. A protective suit has also been created to help you survive in this area. You will find yourself in a world where instead of the usual boundaries of Minecraft,
Tags
Creators
Details
1.5b
Compatibility
Changes
AcidOfRain 1.5b
Major technical update for AcidOfRain.
Compatibility
- Added support for Minecraft / Paper
1.21-1.21.11. - Tested plugin startup on Paper
1.21.11. - Improved compatibility across Paper API versions in the 1.21.x branch.
Commands
- Reworked the main
/acidraincommand. - Added convenient subcommands:
/acidrain help/acidrain status/acidrain recipes/acidrain time/acidrain reload
- Legacy short commands are still supported:
/aon,/aoff,/aset,/aexpand,/astatus,/asuit,/arecipes,/atime.
Status Panel
- Fully redesigned
/acidrain status. - Status is now shown as a compact chat panel.
- Shows the player’s current zone.
- Shows distance to the safe zone and each danger zone.
- If the player is already inside a zone, the distance shows
0 blocks.
Zones
- Fixed zone border calculations.
- Zones are now correctly calculated from the safe zone border.
- Status display and real zone effects now use the same zone logic.
Protection Suit
- Improved protection suit behavior.
- Suit color can now be configured.
- Added an option for randomized suit colors.
Performance and Stability
- Fixed old compilation issues.
- Optimized acid rain particles.
- Fixed invalid particle effect usage.
- Improved Paper/Folia scheduler usage.
- Fixed mob attribute compatibility across different 1.21.x Paper API versions.
Administration
- Added
/acidrain reloadto reload config and language. - Updated permissions:
acidrain.useacidrain.suitacidrain.notifyacidrain.admin
Internal build: 1.5b Public Modrinth version: 1.5b
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:AxfWAbAL:FkhWCKbk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AxfWAbAL:FkhWCKbk"
}
