Fixed a bug where Mythic Mobs were either being removed when they shouldn't or weren't being removed when they should
The timer intervals are now per-world instead of on a global level, meaning one world can remove entities every 5 minutes whereas another world can be set to 15 minutes
The countdown-on-command option was removed due to the complexity of this new system and will now default to skipping the countdowns
It's possible I missed something in testing, so please submit an issue on GitHub if you come across any bugs
Updated the logic for determining when the entity removal task should be run. Previously, an interval set to 1 would wait 1 minute, then start the countdown task, then remove the entities. If you had a warning set to 30 seconds, the entity removal gap was effectively 1.5 minutes. With this update, an interval of 1 and warning set to 30 seconds will continue to run the task every 1 actual minute.
Updated the MythicMobs dependency
World names will now be included in the debug dump
PlaceholderAPI placeholders:
%entityclearer_remaining_minutes% | The time in minutes until the next clear task is run
%entityclearer_remaining_seconds% | The time in seconds until the next clear task is run
%entityclearer_remaining_seconds_left% | The time in seconds until the next clear task is run, minus the time the minutes placeholder already accounted for
The DROPPED_ITEM entity will now be ignored by the nearby entities and spawn reasons check - however, it is still advised to use Paper's alternate item despawn rates instead
Removed the spawn-reason code from the bStats metrics - the performance impact to this update should be negligible so updating doesn't really need to be a priority if you're lazy like me
Removed the show-if-zero option because it added extra unnecessary complexity to the clearing task (may re-add this in the future - if you really liked the feature, please create a feature request on GitHub about it if one doesn't exist already)
The previous method for grabbing the server's current TPS was often too sensitive and would trigger if the TPS dropped below the threshold for even a second. This new update will now get the average TPS from the past 5 seconds, to ensure that the server is actually lagging.
Config changes:
Code (YAML):
low-tps: # Should the entity removal task be triggered when the TPS is low? enabled: false
# Below what TPS should the plugin remove the entities? threshold: 17
# Should the plugin remove the entities instantly or trigger the countdown? # Warning: If the TPS is too low and remove-instantly is false, the plugin may # not be able to remove the entities before the server crashes remove-instantly: true
# Should there be a chat message sent to players with the `entityclearer.lowtps` # permission stating that the TPS is low? chat: true
chat-message: "&c&lWarning: TPS low &8&l(&7&l{TPS}&8&l)&c&l! Removing entities..."
This update completely remade the TPS monitoring system, so it will now work on all server versions instead of only Paper and its forks.
Config changes:
Code (YAML):
low-tps: # Should the entity removal task be triggered when the TPS is low? enabled: false
# How often in seconds should the plugin check the TPS of the server? check-rate: 5
# Below what TPS should the plugin remove the entities? threshold: 17
# Should the plugin remove the entities instantly or trigger the countdown? # Warning: If the TPS is too low and remove-instantly is false, the plugin may # not be able to remove the entities before the server crashes remove-instantly: true
# Should there be a chat message sent to players with the `entityclearer.lowtps` # permission stating that the TPS is low? chat: true
chat-message: "&c&lWarning: TPS low &8&l(&7&l{TPS}&8&l)&c&l! Removing entities..."
# This plugin uses bStats metrics # https://bstats.org/plugin/bukkit/EntityClearer/10915 # Metrics can be disabled in the bStats config.yml
Code (YAML):
low-tps: # Should the entity removal task be triggered when the TPS is low? # This feature requires Paper (https://papermc.io/) enabled: false
# How often in seconds should the plugin check the TPS of the server? check-rate: 10
# Below what TPS should the plugin remove the entities? threshold: 17.00
# Should the plugin remove the entities instantly or trigger the countdown? # Warning: If the TPS is too low and remove-instantly is true, the plugin may # not be able to remove the entities before the server crashes remove-instantly: true
# Should there be a chat message sent to players with the `entityclearer.lowtps` # permission stating that the TPS is low? chat: true
chat-message: "&c&lWarning: TPS low &8&l(&7&l{TPS}&8&l)&c&l! Removing entities..."