Troubleshooting
- Latest version
- 2.5.2
- Minecraft
- 26.x
- Platforms
- Spigot / Paper / Folia
BoostedMonsters — Troubleshooting
- Plugin does not load: check Java 25, a compatible server API and the first startup exception. No database or resource pack is needed.
- No automatic mobs: check SpawnStatus, enabled variants with positive weights, disabled worlds, player game modes, population limits, loaded chunks and light. Surface spawning also needs night or a storm; both surface and underground spawning cannot be disabled.
- Standing still produces nothing: movement is required by default. After the initial position is recorded, move at least requiredPlayerMovement blocks, or disable requirePlayerMovement for testing.
- A weight does not behave like a percent: SpawnChance is relative to other enabled weights. Zero excludes automatic selection, while manual test spawning remains possible.
- No extra loot: check Drops.Enabled, the player-kill requirement, the monster's persistent identification, enabled valid materials, entry chances and the global stack cap. Vanilla mobs with only a renamed display name are not identified as custom monsters.
- Configuration changed unexpectedly: inspect Config-broken backups and migration warnings. Check YAML types, casing and indentation. Do not edit CfgVersion or rename registered monster IDs.
- Manual spawning fails or load is high: use an open location, especially for StormcallerGhast. For automatic load, increase spawnPeriod or lower mobsPerRun, search attempts and population caps. Test changes on new mobs and read debugLogging output; GUI numerical steps are shown on each item.