-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Insane high cpu usage when blocking mob spawning #68
Comments
There's really not a good way to block mob spawning, as minecraft and mods will just haphazardly try to spawn them if they feel like it. If you think there's a much better method, please let me know. |
This sort of thing usually needs forge-level tinkering to accomplish. CustomMobSpawner and JustAnotherSpawner handle mob spawning (and denial thereof), but don't involve regions or permissions. This seems to be uncharted territory for Sponge. |
I'll keep this open, but i don't think there's a good solution any time soon. |
Where's the code for denying mob spawns, so I can also help find a solution? |
Hello! Please be aware that many of the open issues may be closed soon, in preparation of the beta release of FoxGuard 2.0. We have not yet determined if we are going to create a new repo, or use the current one, however, if we use the current one, this issue will be closed. If the issue occurs again at a later date in FoxGuard 2.0, please make a new issue and reference this one. Thank you! |
It seems that rather than disabling it attempting to spawn mobs, it instead just keeps blocking every single attempt, which when covering a large area, causes massive lag and cpu usage.
The text was updated successfully, but these errors were encountered: