Want a better Minecraft server? Read about SpigotMC here!
Separate names with a comma.
You're using the wrong minecraft version for that MA version. Disabling custom damage will probably fix this.
I'm not sure what the issue is then. There's a couple options like this which could be part of it. "Only enable bonus spawns on one world?: false"...
Did you check if it was working in the normal world? I've never seen an issue with this.
It should work fine in most cases with copy/paste. Some monsters have quirks about them to watch out for, though I wouldn't know which.
Try a fresh config, let me know if that fixes it. Some settings will cause this error which didn't before the update.
To my knowledge it should still work.
None that I know of. The code is including in the jar if you want to make one for private use with MA as a starting point.
Try this version. https://www.spigotmc.org/resources/monster-apocalypse.12122/update?update=98153
Mega-aggro has to also be enabled. Try using the zombie world mode near the top of the config first, it should include a good setting for this.
Might be depends on if they changed mc version
I think frustration was in milliseconds or ticks, not sure which. Maybe it was seconds. Try a higher setting though.
You're welcome guys :)
Please update to 19.7 everyone. The issue was recurring due to the design of Spigot's website hiding the newer version of 19.6. 19.7 will work...
Deleted 19.6. Versioning issues were preventing the bugfix from showing.
- Due to an update to Spigot which categorizes monsters differently,...
blainicus updated Monster Apocalypse with a new update entry:
Monster Apocalypse Version 19.7 for MC 1.11.0
Read the rest of this update entry...
Ok, I've fully updated everything and tested again, still can't produce the bug. You have some sort of file issue in your server setup, somehow....
Deleted 19.6 download since it doesn't work at all.
Please make sure you are on 19.6b, 19.6 is the bugged version. Make sure you also have no config file. Here is the 'working' version, I have been...
Delete your old config file. Haven't been able to replicate the bug after doing that myself.