This repository was archived by the owner on Jul 22, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6
Chunk processor
boy0001 edited this page Apr 9, 2015
·
11 revisions
This is a new feature, not a magical solution to all your problems. The chunk processor isn't perfect, and it is your fault if it fails to mitigate crashes / corrupt chunks and the likes (Although feel free to create a ticket if you think it's something it could prevent in future).
The chunk processor will process chunks before they are saved / loaded from disk. It is lightweight at the moment with the following capabilities:
- Clear entities if a dangerous amount is detected
- Clear blockstates if a dangerous amount is detected
The purpose of the processor is to:
- Decrease server lag
- Prevent potentially dangerous chunks being saved / loaded from disk
- Prevent repeated server crashes from dangerous chunks
The usual causes of dangerous chunks are:
- People abusing WorldEdit
- People abusing VoxelSniper
- Any other tool you have that can be used to spam entites / blocks
Configuration is done through the settings.yml
chunk-processor:
// If the processor is enabled
enabled: true
/// The maximum number of entities required in a chunk before it is deemed a source of lag
max-entities: 512
// The maximum number of blockstates allowed per chunk
max-blockstates: 4096For more information about blockstates see: https://hub.spigotmc.org/javadocs/spigot/org/bukkit/block/package-tree.html (or do a google search)