Tags
Creators
Details
Licensed MIT
Published 3 weeks ago
Updated last week
All versions
1.7.0
Release
SpookySeason 1.7.0last week 142
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
Platforms
Folia
Paper
Purpur
Changes
1.7.0
Added
- Blood rain (
/bloodrain,bloodRain): particle drops around every player in three combinable styles, optional real rain for just those players, stronger undead nearby; also by chance in blood moon nights. - The raid leader phases through obstacles towards the target when stuck (
raid.waves.leaderPhaseSeconds,leaderPhaseDistance).
Fixed
- The raid leader never damaged the target (
raid.waves.leaderTargetDamage,leaderReach); in zone or region mode it now counts as a breach. - The raid leader kept wandering off the target on its own (vanilla stroll, panic and flee goals, e.g. from wolves).
- The raid's own archers hit the leader and its horse.
- Ghost spawns failed on MC 26.x (
INSTANT_EFFECTrequires particle data there). - Jumpscares ignored darkness: the light level was read inside the broken block.
- Deleted reward ranks and zone or name entries came back with every start.
- A Horseman already roaming the world became the raid leader and could hold up the wave; the leader is now always spawned at the target.
- Ghosts, the trick mob and the random boss spawn failed on Peaceful.
- Trick-or-treat was blocked for non-operators in every WorldGuard region; door and villager access now follow the protection plugins.
- Raid rewards for offline defenders and rewards missed through a logout are kept for the next join.
- Season-end rewards were limited to ten ranks.
/spooky offended a running raid without telling the players.- Raid objective labels froze after their chunk was reloaded.
- Zone names with a dot broke the configuration; removing the selected zone left it selected.
- Player data files are written atomically.
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:NNvrsPt1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dv910YUb:NNvrsPt1"
}

