Links
Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated 5 months ago
All versions
3.0.0
Release
MysticHorror 3.0.05 months ago 782
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
Platforms
Paper
Purpur
Spigot
Changes
MysticHorror 3.0.0 Changelog
Update Type: Major Release
⨠Added
- Structure System: Added
/mh structurecommand.- Ability to spawn 20+ temporary and permanent horror structures (Cross, Altar, Gallows, Grave, etc.).
- Automatic world cleanup: Temporary structures despawn with particles and sound effects.
- Resource Pack Support: Integrated support for 3 custom sound events (client-side resource pack required).
- Advanced Particle Engine: Each event now features unique particle effects for deeper immersion.
- Interactive Spawning: Structures now appear with build animations and audio cues.
- New Local Events: Introduced 15 new frightening effects (
monster_appear,radio_spam, etc.).
āļø Changes
- Command Overhaul: Improved tab-completion and argument handling.
- Performance Optimizations: Enhanced efficiency for mass event triggers on low-end servers.
- Balance Adjustments: Rebalanced spawn chances for rare global events.
- Complete Config Rewrite: The configuration file has been completely restructured.
- Separate sections for
local-events,global-events,structures, andsounds. - Added
allowed-playerslist for command access control. - New options:
global-events.interval,global-events.chance-min,global-events.chance-max,global-events.cooldown-min,global-events.cooldown-max. - Per-event enable/disable toggles for fine-grained control.
- Old config files will be automatically updated with defaults on first launch.
- Separate sections for
š Fixed
- Fixed configuration loading issues on first startup.
- Resolved conflicts with plugins using custom Action Bar implementations.
- Fixed a bug where players in different dimensions couldn't hear global events.
- Patched memory leaks during prolonged server uptime.
š Deprecated / Removed
- Removed support for Minecraft versions below 1.20.1.
- Removed legacy
CommandSpammechanic (now integrated intoMassHysteriaevent).
New config:
yaml
allowed-players:
- mscgroup
- unknown
local-events:
enabled: true
interval: 10
chance-min: 5
chance-max: 15
cooldown-min: 60
cooldown-max: 180
global-events:
enabled: true
interval: 30
chance-min: 2
chance-max: 8
cooldown-min: 180
cooldown-max: 300
structures:
enabled: true
max-per-world: 50
auto-cleanup: 300 # seconds
sounds:
enabled: true
custom-sounds: true
resource-pack-url: "https://example.com/mystichorror-resources.zip"
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:1WvKh6Bp:t8Ve2dL5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1WvKh6Bp:t8Ve2dL5"
}
