Everything you need to master CustomDisasters v3.5.2
β Requirements:
plugins//disasters editorhttps://customdisasters.online/editor/ABC123| Command | Description | Permission | Alias |
|---|---|---|---|
/disasters editor |
Open cloud management interface | customdisasters.admin |
/disaster editor |
/disaster start <name> |
Start a specific disaster | customdisasters.start |
β |
/disaster stop |
Stop current active disaster | customdisasters.stop |
β |
/disaster list |
Show all available disasters | customdisasters.list |
β |
/disaster status v3.5.1 |
Check active disaster & remaining time | customdisasters.status |
β |
/disaster reload |
Reload all configurations | customdisasters.reload |
β |
/disaster difficulty <level> |
Set global difficulty (1-5) | customdisasters.admin |
β |
For Server Admins (LuckPerms/PermissionEx):
For the first time, one plugin jar works on all versions:
Full support with fallbacks
Optimized particle system
Latest features & APIs
Optional persistent storage for statistics and analytics:
Admins are notified when new versions are available:
Step 1: Create a MySQL database and user:
Step 2: Edit config.yml:
disaster_history - Track all disaster events
| Column | Type | Purpose |
|---|---|---|
| id | INT | Unique identifier |
| disaster_name | VARCHAR(255) | Name of the disaster |
| start_time | TIMESTAMP | When it started |
| duration_seconds | INT | How long it lasted |
player_disaster_stats - Per-player metrics
| Column | Type | Purpose |
|---|---|---|
| player_uuid | VARCHAR(36) | Unique player ID |
| total_deaths | INT | Deaths during disasters |
| disasters_experienced | INT | Disasters survived |
| last_disaster_date | TIMESTAMP | Last participation |
Query your disaster stats for analytics dashboards:
Create powerful disasters with this structure:
Set custom multipliers for each difficulty level:
Control visual intensity and effects:
Add custom audio (OGG format) to plugins/CustomDisasters/sounds/
Solutions:
ping google.com/permission setuser Admin customdisasters.admin/disaster reloadCauses:
Fix: Create a new session: /disasters editor
Check these:
particle-density: 100/disaster reloadDebug steps:
mysql -h localhost -u disasters -p customdisasterssudo systemctl status mysqlnetstat -tulpn | grep 3306mysql: enabled: falseChecklist:
/disaster reload if neededLag during disasters?
Always check logs/latest.log for detailed error messages:
A: No! MySQL is completely optional. All core features work without it. Enable it only if you want statistics and backups.
A: Yes! Edit YAML files directly in plugins/CustomDisasters/custom/ then run /disaster reload. Cloud editor requires internet.
A: Works best with Paper, but compatible with Spigot 1.19+. We recommend Paper for better performance and features.
A: Yes! Each admin gets their own session. Different disasters can be edited simultaneously.
A: Your edits are safe! Click "Save Changes" and they'll apply when the server is back up.
A: OPs automatically get notified when joining the server if an update is available. Direct link to Modrinth is included.
A: Yes! Use the Smart Scheduling system. Set min/max intervals in config.yml and disasters will trigger automatically.
A: 1.19.x, 1.20.x, and 1.21.x. One jar works everywhere!
A: Report issues on Modrinth or check GitHub issues.
A: Join our community on Discord for support, ideas, and updates! Link available on Modrinth.
Can't find what you're looking for? Reach out to the community or check the download page!
Back to Home Download & Support