Tags
Creators
Details
Licensed MIT
Published 3 weeks ago
Updated last week
All versions
1.5.0
Release
SpookySeason 1.5.03 weeks ago 46
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
Platforms
Folia
Paper
Changes
1.5.0
Added
- Zone targets (
raid.target.mode: zone): a box defined in the plugin configuration and set up in game with/spookyraid zone pos1|pos2|save. Requires no other plugin. The plugin warns at start if the spawn ring lies inside the zone.
Fixed
- Defenders' splash potions had no effect on attackers while
raid.waves.friendlyFirewas off: wither, poison and magic damage was cancelled regardless of its source. Only damage caused by the raid itself is cancelled now. - Ranged attackers walked up to the objective instead of stopping at
raid.waves.rangedReach. An attacker within reach of a living objective now holds its position. - The wave leader survived a wave timeout and was never removed afterwards.
- The objective target counted as ready before its visuals had been placed. With
countdownSeconds: 0a failed placement went unnoticed. - Trading with a villager during the trick-or-treat cooldown showed the cooldown message on every click.
- Periodic tasks logged exceptions without a stack trace.
Changed
- Rewards are items and experience given through the inventory API instead of console commands.
Raid rewards are configured under
raid.rewards.victoryandraid.rewards.consolation, season-end rewards underseasonEndRewards.ranks, each with anitemslist (MATERIAL:amount) and anxpvalue. Items that do not fit into the inventory are dropped at the player's feet. Existing configurations are migrated on start: the old command lists are replaced by the new sections andseasonEndRewards.commandsis removed. - Configuration keys of removed features are cleaned up on every start.
- The entity scheduler is resolved on the
Entityinterface instead of the concrete entity class. - Zone corner selections are stored in a concurrent map.
- Code defaults for
raid.target.objective.reachandraid.defeat.effect.durationSecondsmatch the shipped configuration. /spookyraidusage listszone.
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:dv910YUb:uOy0JNRf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dv910YUb:uOy0JNRf"
}

