Paper Configuration Details
The Paper configuration file is
paper.yml. Paper uses this file, along with
server.properties to control your server's feature and performance options
- Controls the global on/off state for timings, we do not recommend you disable it
- Makes timings data more specific with entity and other information
- We recommend you leave this on, at least until you get your server tuned as you want it
- Sets whether timings hides your server name (as set in server.properties) when pasting to the web
- Information to hide from pasted config entries
- How often history snapshots are taken, more often means more data
- How much history, in total, to keep per paste
General Settings - Server-wide
- Whether or not the server should prevent people from spamming interaction packets to lag the server
- Load the servers permission.yml BEFORE plugins. Bukkit/Spigot behavior was after, resulting in plugins not seeing those permission in onEnable. Defaults to true. Set to false to go back to Bukkit behavior.
- Should server sleep between every chunk save. Will cause memory issues if you enable this.
- If disabled, Players should not be able to collide with each other. If enabled (default, vanilla), it will use the players scoreboard team setting. Setting this to false will not impact non player collisions unless you also enable allow-non-player-entities-on-scoreboards and then disable collision for that team.
- Sets whether the server is to save empty scoreboard teams.
- We do not recommend you enable this. Many plugins abuse empty scoreboard teams for sidebars and other features, saving them will increase join lag.
- The size of the region file cache.
- The number of threads to use for asynchronous chunk loading
- Cranking this value super high doesn't make everything really fast, only mess with this as needed.
- Determines if the server should set an entities health before it fires the death event.
truewould be seen as the correct value by many, however it may break plugins, so
falseis the default.
'default': - This prefix will allow you to specify which worlds the below settings apply to, "default" will make them apply to all worlds
- Do we print all of the below settings in startup console
- NOTE: All the below settings will require new chunk generation to take effect
- Should canyons generate in the world
- Should caves generate in the world
- Should dungeons generate in the world
- Should fortresses generate in the world
- Should mineshafts generate in the world
- Should monuments generate in the world
- Should strongholds generate in the world
- Should temples generate in the world
- Should vilages generate in the world
- Should bedrock be generated as a single flat layer
- The speed at which baby zombies will move
- The player moves at 0.1, for reference
- Minimum amount of ticks before a fish will appear at the end of the fishing line
- Maximum amount of ticks before a fish will appear at the end of the fishing line
- Player food exhaustion rate for breaking blocks
- Player food exhaustion rate for swimming
- Distance in blocks from the player at which mobs will be randomly selected for removal
- Distance in blocks from the player at which all mobs will be removed immediately
- Height at which falling block entities should be removed from the game
- (0 is disabled)
- Height at which tnt entities should be removed from the game
- (0 is disabled)
- Should the server remove bad mob spawner tile entities to prevent crashes
- Should we use the optimized explosion algorithm
- (removes dead entities in explosion radius)
- Rate at which mob spawners are checked for spawn conditions, in ticks
- Should we use optimized caching for chunk maps
- (performance improvement when sending data for areas that don't change much)
- How loud should TNT explosions be
- Should we disable the end credits when a player leaves the end
- Should the server disable the chest block's detection of ocelots and cats standing on them
- (improves performance)
- Should the player take damage in (or above) the nether ceiling
- Should lava drain faster than normal
- Should water drain faster than normal
- Speed in ticks at which lava will flow in overworld
- Speed in ticks at which lava will flow in nether
- Minimum height at which squids will spawn
- Maximum height at which squids will spawn
- Maximum height cacti will grow to
- Maximum height reeds will grow to
- Should entities get knocked back by explosions
- Speed at which water will flow when adjacent to lava
- (useful for limiting wall gen)
- Reverts the newer TNT and FallingBlock behaviors to a style more similar to Minecraft 1.7.
- Should we use the hopper-check delay option in spigot.yml.
- (disabled in vanilla Spigot, this lets you re-enable it)
- Should undead horses be able to be leashed
- How often should we update container inventories, in ticks.
- (changes visible when moving inventory, recommended to not set above 5)
- Should the server ever experience a thunder weather-state.
- Should ice and snow generate in snowy biomes.
- Queues light updates to happen at the end of each tick, after all other work has been done.
- May skip some in low-TPS situations.
- Should chunks have Regional Difficulty enabled. Setting this to false will ensure all chunks are treated equally. In Vanilla, the longer a player is in a chunk, the difficulty will rise.
- Should all chunks be eligible to spawn slime entities
- Should players be able to tab-complete block locations in supported commands
- How many ticks to despawn arrows from a non player. -1 will use the spigot.yml arrow despawn rate config.
- Whether or not to fire the BlockPhysicsEvent for redstone activity. This is VERY UNLIKELY to ever need to be true, unless a bad plugin is listening to the wrong event. Setting this false will have drastic impact to performance with heavy redstone. Plugins should be using BlockRedstoneEvent to detect redstone, not Physics Event.
- How many ticks between each grass block ticks in attempt to spread. Raising this value will improve performance but slow down grass spreading. 1 is vanilla (every tick)
- Should the server keep the spawn chunks loaded at all times
- Configure how far your spawn should keep chunks loaded.
- The spawns chunk is included in this range. If you set a range of 7, a box of 14x14 will stay loaded, not 15x15. This is the way Vanilla handles it.
- Default value will be based on your view distance for that world defined in spigot.yml, capped to 8. However the value itself is not capped to 8, just the default if you have not set it.
- Once set, you may go over 8 chunks. Recommended 0-1 for development servers and unused worlds to drastically speed up server start up time!
- Vanilla defaults this to true, however when this setting is false, Paper will drastically reduce the performance impact of non player collisions. You would only ever need to set this to true if you intend to use /scoreboard team join teamname @e syntax to force non players into a team. It is recommended to not set this to true unless you know you are trying to do something that this blocks.
- Attempts to use vanilla scoreboard information to provide name coloring in chat.
- Helpful for vanilla maps or vanilla map authors.
- Sets whether lootable blocks and entities should automatically refill after a certain time period.
- Sets whether a player who has already looted a lootable should be prevented from looting it a second time
- If enabled, a different item seed will be used on refill, meaning a different set of items will be filled than the prior time.
- The number of times a lootable may be refilled, where -1 means infinitely.
- The minimum amount of time before a lootable can be refilled.
- Accepts values of seconds
4h, or days
- The maximum amount of time before a lootable will be refilled.
- Accepts values of seconds
4h, or days
- Should we tick frosted ice at all, as needed for melting and other effects
- Sets the minimum delay for potion effects on frosted ice
- Sets the maxmimum delay for potion effects on frosted ice