
ZombieApocalypseSSS
ZombieApocalypseSSS is a comprehensive Minecraft plugin that transforms your server into a thrilling zombie survival apocalypse. Featuring advanced zombie AI, evolving variants, player infection mechanics, psychological horror elements, and dynamic events
3.7
Compatibility
Changes
ZombieApocalypseSSS - Multi-File Configuration Update
Architecture & Management
-
Modular Configuration System : Successfully split the massive config.yml into 5 specialized files for better organization and easier maintenance:
- config.yml : Global settings (Language, Worlds, Spawn Control).
- zombies.yml : Zombie types, AI behavior, block breaking, and evolution phases.
- items.yml : Weapons (Guns, Katanas, Bats), survival gear, and ammo stats.
- events.yml : Blood Moon, Supply Drop loot tables, and Boss settings.
- mechanics.yml : Infection, Bleeding, Campfire of Hope, and Sanity systems.
-
Dynamic Resource Management : Added automatic generation for all new configuration files if they are missing from the plugin folder. Core Improvements
-
Enhanced Reload System : Updated /zapoc reload to hot-reload all 5 configuration files simultaneously.
-
Task Synchronization : Refactored WorldEventTask , PlayerStatusTask , and PsychologicalHorrorTask to dynamically update their internal variables whenever the config is reloaded without requiring a server restart.
-
Singleton Pattern Access : Implemented global getters in the main class for easy access to sub-configs across all services. Technical Fixes
-
Code Cleanup : Removed redundant method definitions and fixed duplicate variable declarations in the main class.
-
Dependency Handling : Fixed missing FileConfiguration imports in background tasks.
-
Stability : Resolved potential NullPointerException risks during the initial plugin enable phase by ensuring config load order. Build Information
-
Version : 3.7 (Refactored)
-
Output : ZombieApocalypseSSS-1.0.jar
-
Platform : Paper/Spigot 1.21.1 (Java 21)
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:pSQD27Eo:j1336BnN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pSQD27Eo:j1336BnN"
}
