- Csatlakozott
- 2021, Már. 15
- Üzenetek
- 55
Használata a következő:
Másold ki majd illeszd be a `/plugins/ClearLag/config.yml` fájlba.
Plugin: https://www.spigotmc.org/resources/clearlagg.68271
Spoiler
#--------------------------------------------------------------------#
# ClearLag Configuration File #
#--------------------------------------------------------------------#
# Configure to your liking, reload the config by tying: /lagg reload #
# - #
# Here is a helpful tutorial on this configuration setup! (Updated) #
# http://dev.bukkit.org/bukkit-plugins/clearlagg/pages/config-setup/ #
#--------------------------------------------------------------------#
# All possible mob names: https://goo.gl/cch8YK #
#--------------------------------------------------------------------#
config-version: 17
# -- 'use-internal-tps' Should clearlag just use the calculated internal TPS? (Improves accuracy)
# -- 'language' Clearlag supports multiple languages (English, Spanish, Japanese) translated by the community
settings:
language: English
auto-update: true
enable-api: true
use-internal-tps: true
#Controls ALL of Clearlag's broadcasting. Disabling this will disable ALL broadcasting on Clearlag
# -- 'enabled' Should clearlag broadcast messages at all? (Example: Auto-removal, warnings, ect)
# -- 'use-permission-for-broadcasts' Should clearlag use permissions?
# -- 'permission' What is the permission? (By default, it's bukkit's default)
global-broadcasts:
enabled: true
use-permission-for-broadcasts: false
permission: bukkit.broadcast
#Monitors your server's main thread for locking/freezing. Helps figure out what's causing lag-spikes
# NOTE: This will outprint mostly just stacktraces. It's up to YOU to interpret the stacktrace
# NOTE: (!Important!) Clearlag will print EVERYTHING to your Spigot/Bukkit server logs!
# NOTE: A large 'Garbage collection time' generally means the spike was caused by the Garbage collector (Memory issue basically..)
# -- 'enabled' Should this be enabled (Prints data to your logs, not ingame chat)
# -- 'min-elapsed-time' How long (IN MILLISECONDS) of a server-tick constitutes a freeze/lock? I don't recommend going under ~80
# -- 'check-interval' How often (IN MILLISECONDS) should the server be checked? Lower the number, more accurate the timings
# -- 'follow-stack' Should Clearlag keep printing the stacktrace every time it changes (Can be very spammy)?
# Help-> https://dev.bukkit.org/projects/clearlagg/pages/finding-the-cause-of-lag-spikes
lag-spike-helper:
enabled: false
min-elapsed-time: 500
check-interval: 100
follow-stack: true
#Limits the amount of item transfers for all the hoppers in a single chunk
# -- 'transfer-limit' How many transfers per check interval until the hopper should be disabled
# -- 'check-interval' In seconds, on what interval should the transfer limit be reset
hopper-limiter:
enabled: false
transfer-limit: 5
check-interval: 1
#Meters your ram usage. If it goes above 'limit', run 'commands:'
# NOTE: It's perfectly normal for your server to be using a lot of memory. The JVM's garbage collector will automatically free memory.
# NOTE: Only use this if you have very little memory that can't support the server
# -- 'ram-limit' is in MB, do not set it exactly to your max allocated ram amount
# -- 'interval' is how often clearlag will check your ram usage
# -- 'commands' lists the commands that will be ran upon hitting your ram-limit
ram-meter:
enabled: false
interval: 20
ram-limit: 5000
commands:
- 'lagg killmobs'
- 'lagg clear'
#Configure what the '/lagg halt' command does
# -- 'remove-entities' remove entities such as items, primed-tnt, and mobs
# -- 'disable-natural-entity-spawning' disables the server's natural world spawning
# -- 'halted' this section defines which actions should be halted during '/lagg halt'
halt-command:
remove-entities: true
disable-natural-entity-spawning: true
halted:
fire: true
fire-burn: true
explosion: true
decay: true
block-fade: true
block-form: true
block-spread: true
block-natural-change: true
#This limits how fast a user can move by walking or flying in a single tick (20 ticks a second)
#I HIGHLY recommend you use this on servers with increased player-speed/fly to prevent chunk overload
#You may also use Spigot's internal speed limiters to achieve the same goal if present on your version (better performance)
# -- 'move-max-speed' Max speed on foot
# -- 'fly-max-speed' Max speed while flying
player-speed-limiter:
enabled: false
move-max-speed: 0.7
fly-max-speed: 0.8
#Set the age of specific items when they're first spawned so they naturally despawn faster, or slower then others
#Recommended for servers with a lot of item-entities consisting mostly of useless items (Such as stone)
#Material list: https://hub.spigotmc.org/javadocs/spigot/org/bukkit/Material.html
# -- 'items' Lists the material names of the entities with their spawn-age (In seconds)
item-spawn-age-setter:
enabled: false
items:
stone: 240
grass: 240
cobblestone: 240
log: 240
stone_axe: 240
stone_pickaxe: 240
stone_sword: 240
wooden_axe: 240
wooden_pickaxe: 240
wooden_sword: 240
rotten_flesh: 240
gravel: 240
dirt: 240
leather: 200
sand: 240
bone: 240
beef: 240
chicken: 160
rabbit: 240
salmon: 240
cactus: 210
wool: 180
arrow: 160
PORKCHOP: 240
potato: 240
RED_TULIP: 240
#Should mobs be nerfed to prevent over-breeding to reduce CPU usage (And possibly raise TPS)
#When mobs are stuck too close, collisions are extremely intensive putting a pretty mean load on the server
# -- 'max-mobs' means how many bably/adult animals are allowed within the 'check-radius'
# -- 'check-radius' is the radius of what clearlag will check for 'max-mobs'
mob-breeding-limiter:
enabled: false
max-mobs: 6
check-radius: 15
#Should clearlag purge logs under /logs when the server starts?
# -- 'days-old' means how many days old can the log be to be deleted
log-purger:
enabled: false
days-old: 3
#What type of entities SHOULD NOT be removed while doing /lagg area?
area-filter:
- Itemframe
- Minecart
- Wolf
- Villager
- Horse
- ARMOR_STAND
#Should clearlag reset the config, or attempt to update your config on updates
# -- 'force-update' is whether or not clearlag will reset your config with a newer version
# -- settings this to false will make clearlag update your config rather then resetting
config-updater:
force-update: false
#This limits the mob egg spawners so players cannot "overload" the server with them
# -- 'check-radius' is the radius clearlag will check for nearby entities
# -- 'max-mobs' is how many entities may be in the radius before the spawning is blocked
mobegg-limiter:
enabled: false
check-radius: 8
max-mobs: 5
#Disable new chunk generation, or just put a cap on how many can load at once.
#May cause many bugs with Spigot 1.8+, not recommended!
# -- 'create-new-chunks' disables or enables chunk creation. false would disallow new chunks
# -- !UNSTABLE ON SPIGOT BUILDS!
chunk-limiter:
enabled: false
limit: 6000
create-new-chunks: true
#This modifies the view range of entities
# -- Lower it is, the better your entity tick will be and the more CPU cycles you'll save
# -- If it's too high, expect bugs / lots of lag
mob-range:
enabled: false
zombie: 30
skeleton: 30
creeper: 20
#How long should items/Mobs be left on the ground
# -- live-time's go by ticks (20 ticks a second)
live-time:
enabled: false
interval: 10
mobtimer: true
itemtimer: true
arrowtimer: true
arrowkilltime: 15
moblivetime: 600
itemlivetime: 240
#This option disallows the placement of too many tnt-minecarts
# -- 'radius' is the radius clearlag will check for TNT-Minecarts
tnt-minecart:
enabled: false
max: 2
radius: 6
#This option reduces global dispenser fire rate
# -- 'time' is in milliseconds
dispenser-reducer:
enabled: false
time: 100
#This option reduces the explosions of mass amounts of tnt, and reduces tnt lag
# -- 'check-radius' is the radius clearlag will check for primed TNT
# -- 'max-primed' is the max primed TNT within the radius allowed before clearlag begins to remove
tnt-reducer:
enabled: false
check-radius: 5
max-primed: 3
#This option reduces fire spread rate
# -- 'time' is in milliseconds
firespread-reducer:
enabled: false
time: 2000
#How many entities should one chunk be allowed to hold?
# -- 'entities' lists all the entities that will be counted
# and possibly removed.
chunk-entity-limiter:
enabled: false
limit: 10
entities:
- Squid
- Zombie
- Skeleton
- Creeper
- Chicken
- Pig
- Sheep
- Cow
- Horse
# - Pig liveTime=100
Másold ki majd illeszd be a `/plugins/ClearLag/config.yml` fájlba.
Plugin: https://www.spigotmc.org/resources/clearlagg.68271
Spoiler
#--------------------------------------------------------------------#
# ClearLag Configuration File #
#--------------------------------------------------------------------#
# Configure to your liking, reload the config by tying: /lagg reload #
# - #
# Here is a helpful tutorial on this configuration setup! (Updated) #
# http://dev.bukkit.org/bukkit-plugins/clearlagg/pages/config-setup/ #
#--------------------------------------------------------------------#
# All possible mob names: https://goo.gl/cch8YK #
#--------------------------------------------------------------------#
config-version: 17
# -- 'use-internal-tps' Should clearlag just use the calculated internal TPS? (Improves accuracy)
# -- 'language' Clearlag supports multiple languages (English, Spanish, Japanese) translated by the community
settings:
language: English
auto-update: true
enable-api: true
use-internal-tps: true
#Controls ALL of Clearlag's broadcasting. Disabling this will disable ALL broadcasting on Clearlag
# -- 'enabled' Should clearlag broadcast messages at all? (Example: Auto-removal, warnings, ect)
# -- 'use-permission-for-broadcasts' Should clearlag use permissions?
# -- 'permission' What is the permission? (By default, it's bukkit's default)
global-broadcasts:
enabled: true
use-permission-for-broadcasts: false
permission: bukkit.broadcast
#Monitors your server's main thread for locking/freezing. Helps figure out what's causing lag-spikes
# NOTE: This will outprint mostly just stacktraces. It's up to YOU to interpret the stacktrace
# NOTE: (!Important!) Clearlag will print EVERYTHING to your Spigot/Bukkit server logs!
# NOTE: A large 'Garbage collection time' generally means the spike was caused by the Garbage collector (Memory issue basically..)
# -- 'enabled' Should this be enabled (Prints data to your logs, not ingame chat)
# -- 'min-elapsed-time' How long (IN MILLISECONDS) of a server-tick constitutes a freeze/lock? I don't recommend going under ~80
# -- 'check-interval' How often (IN MILLISECONDS) should the server be checked? Lower the number, more accurate the timings
# -- 'follow-stack' Should Clearlag keep printing the stacktrace every time it changes (Can be very spammy)?
# Help-> https://dev.bukkit.org/projects/clearlagg/pages/finding-the-cause-of-lag-spikes
lag-spike-helper:
enabled: false
min-elapsed-time: 500
check-interval: 100
follow-stack: true
#Limits the amount of item transfers for all the hoppers in a single chunk
# -- 'transfer-limit' How many transfers per check interval until the hopper should be disabled
# -- 'check-interval' In seconds, on what interval should the transfer limit be reset
hopper-limiter:
enabled: false
transfer-limit: 5
check-interval: 1
#Meters your ram usage. If it goes above 'limit', run 'commands:'
# NOTE: It's perfectly normal for your server to be using a lot of memory. The JVM's garbage collector will automatically free memory.
# NOTE: Only use this if you have very little memory that can't support the server
# -- 'ram-limit' is in MB, do not set it exactly to your max allocated ram amount
# -- 'interval' is how often clearlag will check your ram usage
# -- 'commands' lists the commands that will be ran upon hitting your ram-limit
ram-meter:
enabled: false
interval: 20
ram-limit: 5000
commands:
- 'lagg killmobs'
- 'lagg clear'
#Configure what the '/lagg halt' command does
# -- 'remove-entities' remove entities such as items, primed-tnt, and mobs
# -- 'disable-natural-entity-spawning' disables the server's natural world spawning
# -- 'halted' this section defines which actions should be halted during '/lagg halt'
halt-command:
remove-entities: true
disable-natural-entity-spawning: true
halted:
fire: true
fire-burn: true
explosion: true
decay: true
block-fade: true
block-form: true
block-spread: true
block-natural-change: true
#This limits how fast a user can move by walking or flying in a single tick (20 ticks a second)
#I HIGHLY recommend you use this on servers with increased player-speed/fly to prevent chunk overload
#You may also use Spigot's internal speed limiters to achieve the same goal if present on your version (better performance)
# -- 'move-max-speed' Max speed on foot
# -- 'fly-max-speed' Max speed while flying
player-speed-limiter:
enabled: false
move-max-speed: 0.7
fly-max-speed: 0.8
#Set the age of specific items when they're first spawned so they naturally despawn faster, or slower then others
#Recommended for servers with a lot of item-entities consisting mostly of useless items (Such as stone)
#Material list: https://hub.spigotmc.org/javadocs/spigot/org/bukkit/Material.html
# -- 'items' Lists the material names of the entities with their spawn-age (In seconds)
item-spawn-age-setter:
enabled: false
items:
stone: 240
grass: 240
cobblestone: 240
log: 240
stone_axe: 240
stone_pickaxe: 240
stone_sword: 240
wooden_axe: 240
wooden_pickaxe: 240
wooden_sword: 240
rotten_flesh: 240
gravel: 240
dirt: 240
leather: 200
sand: 240
bone: 240
beef: 240
chicken: 160
rabbit: 240
salmon: 240
cactus: 210
wool: 180
arrow: 160
PORKCHOP: 240
potato: 240
RED_TULIP: 240
#Should mobs be nerfed to prevent over-breeding to reduce CPU usage (And possibly raise TPS)
#When mobs are stuck too close, collisions are extremely intensive putting a pretty mean load on the server
# -- 'max-mobs' means how many bably/adult animals are allowed within the 'check-radius'
# -- 'check-radius' is the radius of what clearlag will check for 'max-mobs'
mob-breeding-limiter:
enabled: false
max-mobs: 6
check-radius: 15
#Should clearlag purge logs under /logs when the server starts?
# -- 'days-old' means how many days old can the log be to be deleted
log-purger:
enabled: false
days-old: 3
#What type of entities SHOULD NOT be removed while doing /lagg area?
area-filter:
- Itemframe
- Minecart
- Wolf
- Villager
- Horse
- ARMOR_STAND
#Should clearlag reset the config, or attempt to update your config on updates
# -- 'force-update' is whether or not clearlag will reset your config with a newer version
# -- settings this to false will make clearlag update your config rather then resetting
config-updater:
force-update: false
#This limits the mob egg spawners so players cannot "overload" the server with them
# -- 'check-radius' is the radius clearlag will check for nearby entities
# -- 'max-mobs' is how many entities may be in the radius before the spawning is blocked
mobegg-limiter:
enabled: false
check-radius: 8
max-mobs: 5
#Disable new chunk generation, or just put a cap on how many can load at once.
#May cause many bugs with Spigot 1.8+, not recommended!
# -- 'create-new-chunks' disables or enables chunk creation. false would disallow new chunks
# -- !UNSTABLE ON SPIGOT BUILDS!
chunk-limiter:
enabled: false
limit: 6000
create-new-chunks: true
#This modifies the view range of entities
# -- Lower it is, the better your entity tick will be and the more CPU cycles you'll save
# -- If it's too high, expect bugs / lots of lag
mob-range:
enabled: false
zombie: 30
skeleton: 30
creeper: 20
#How long should items/Mobs be left on the ground
# -- live-time's go by ticks (20 ticks a second)
live-time:
enabled: false
interval: 10
mobtimer: true
itemtimer: true
arrowtimer: true
arrowkilltime: 15
moblivetime: 600
itemlivetime: 240
#This option disallows the placement of too many tnt-minecarts
# -- 'radius' is the radius clearlag will check for TNT-Minecarts
tnt-minecart:
enabled: false
max: 2
radius: 6
#This option reduces global dispenser fire rate
# -- 'time' is in milliseconds
dispenser-reducer:
enabled: false
time: 100
#This option reduces the explosions of mass amounts of tnt, and reduces tnt lag
# -- 'check-radius' is the radius clearlag will check for primed TNT
# -- 'max-primed' is the max primed TNT within the radius allowed before clearlag begins to remove
tnt-reducer:
enabled: false
check-radius: 5
max-primed: 3
#This option reduces fire spread rate
# -- 'time' is in milliseconds
firespread-reducer:
enabled: false
time: 2000
#How many entities should one chunk be allowed to hold?
# -- 'entities' lists all the entities that will be counted
# and possibly removed.
chunk-entity-limiter:
enabled: false
limit: 10
entities:
- Squid
- Zombie
- Skeleton
- Creeper
- Chicken
- Pig
- Sheep
- Cow
- Horse
# - Pig liveTime=100
