Guest User

Untitled

a guest
Nov 2nd, 2012
64
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 7.18 KB | None | 0 0
  1. #> This is the configuration of NoLagg, in here you can enable or disable features as you please
  2. #> For more information, you can visit the following websites:
  3. #> http://dev.bukkit.org/server-mods/nolagg/
  4. #> http://forums.bukkit.org/threads/nolagg.36986/
  5.  
  6. # Manages chunk loading and sending to clients using various new settings
  7. chunks:
  8. # Whether Chunks should be loaded on startup
  9. enabled: false
  10. # The minimum chunk sending rate (chunks/tick)
  11. minRate: 0.25
  12. # The maximum chunk sending rate (chunks/tick)
  13. maxRate: 1.5
  14. # If you use a plugin that depends on the net server handler for packets, disable this
  15. # For example, Raw Critics' Ore Obfuscation does not function with this enabled.
  16. # Orebfuscator is supported and works with this enabled.
  17. bufferedLoader:
  18. # Whether or not to use the buffered packet loader to reduce new memory allocation
  19. enabled: true
  20. # The amount of threads to use to compress the chunk packets (increase if it can't keep up)
  21. threadCount: 4
  22. # Sets whether the dynamic view distance should be enforced
  23. # If you use maxTPS, set this to false, or it will conflict!
  24. useDynamicView: false
  25. # Sets multiple view distances for different amounts of loaded chunks (chunk_count: view_chunks)
  26. # To disable, remove all chunk: view nodes. The view is smoothed out between nodes
  27. # The dynamic view distance will never be higher than the server view distance!
  28. dynamicView:
  29. - 0 = 13
  30. - 5000 = 13
  31. - 10000 = 13
  32. - 60000 = 13
  33. # Sets in what order chunks are sent to the client
  34. # Available modes: SLOPE and SPIRAL
  35. sendOrder: SLOPE
  36.  
  37. # Can examine server tick rate performance
  38. examine:
  39. # Whether Examine should be loaded on startup
  40. enabled: false
  41.  
  42. # The maximum time in ticks a generated examine report can be
  43. # It can be increased, but the generated file might be too large for the viewer to handle
  44. maxExamineTime: 72000
  45.  
  46. # Can monitor and log server and player performance statistics
  47. monitor:
  48. # Whether Monitor should be loaded on startup
  49. enabled: false
  50. # The interval at which new performance snapshots are generated
  51. monitorInterval: 40
  52. # Whether or not to start logging server performance on startup
  53. startLoggingOnStartup: false
  54.  
  55. # The server notifies players (with a permission) when the tick rate drops below the threshold
  56. lagNotifier:
  57. # Enable or disable this feature
  58. enabled: false
  59. # The interval in miliseconds to send this message (1000 ms = 1 second)
  60. interval: 10000
  61. # The tick rate at which it starts broadcasting
  62. threshold: 15.0
  63. # The message to send to these players
  64. message: '&cThe server can''t keep up!'
  65.  
  66. # Buffers items in chunks to prevent lag-outs because of lots of items
  67. itembuffer:
  68. # Whether ItemBuffer should be loaded on startup
  69. enabled: true
  70. # The maximum amount of items allowed per chunk
  71. maxItemsPerChunk: 80
  72.  
  73. # Stacks nearby items to counter item-drop spammers and reduce item count on the server
  74. itemstacker:
  75. # Whether ItemStacker should be loaded on startup
  76. enabled: true
  77. # The block radius to look for other items when stacking
  78. # You can set it for multiple worlds
  79. radius:
  80. default: 1.0
  81. # The amount of (physical) items needed to form one stack
  82. threshold: 2
  83. # The interval in ticks at which item stacking is performed (1 tick = 1/20 sec)
  84. interval: 20
  85.  
  86. # The item types (materials) to ignore during item stacking, buffering and spawn limits
  87. # Use 'orb' to ignore experience orbs
  88. ignoredItemTypes:
  89. - DIAMOND_PICKAXE
  90. - WOODEN_HOE
  91.  
  92. # Attempts to fix block and sky lighting bugs in worlds
  93. lighting:
  94. # Whether Lighting should be loaded on startup
  95. enabled: true
  96. # Whether or not lighting is automatically fixed when a new chunk is generated
  97. auto: true
  98.  
  99. # Keeps entity counts below multiple configured thresholds
  100. spawnlimiter:
  101. # Whether SpawnLimiter should be loaded on startup
  102. enabled: false
  103.  
  104. # Entity type or group names that can be removed from loaded chunks
  105. # If you don't want certain already spawned entities removed while the server runs,
  106. # Remove them from this list
  107. forceRemoved:
  108. - monsters
  109. - itemcobblestone
  110. - itemdirt
  111. - itemsand
  112. - itemgravel
  113.  
  114. # The general spawn limits (natural spawning)
  115. # For more information, see http://dev.bukkit.org/server-mods/nolagg/pages/spawn-limits-nolagg/
  116. spawnlimits:
  117. # The default spawn limits per world, overridden by world limits
  118. default:
  119. mob: 800
  120. cow: 60
  121. creepers: 30
  122. monsters: 400
  123. # The world-specific spawn limits
  124. worlds:
  125. world1:
  126. monsters: 300
  127. world2:
  128. chickens: 30
  129. # The global spawn limits
  130. global:
  131. mobs: 6000
  132.  
  133. # The spawn limits for mob spawners
  134. # For more information, see http://dev.bukkit.org/server-mods/nolagg/pages/spawn-limits-nolagg/
  135. mobSpawnerLimits:
  136. # The default spawn limits per world, overridden by world limits
  137. default:
  138. mob: 700
  139. zombie: 30
  140. # The world-specific spawn limits
  141. worlds:
  142. world3:
  143. cavespider: 0
  144. creativeworld:
  145. mob: 0
  146. # The global spawn limits
  147. global:
  148. mob: 2000
  149.  
  150. # Replaces explosion creation with a faster version and buffers TNT ignites to prevent TNT server crashes
  151. tnt:
  152. # Whether TNT should be loaded on startup
  153. enabled: true
  154. # The interval (in ticks) at which TNT is detonated by explosions
  155. detonationInterval: 1
  156. # How many TNT is detonated by explosions per interval
  157. detonationRate: 10
  158. # The explosion crater size factor
  159. explosionRadiusFactor: 1.0
  160. # The amount of explosion packets to send to the clients per tick
  161. explosionRate: 5
  162. # If TNT explosions can change non-TNT blocks
  163. changeBlocks: true
  164.  
  165. # Alters the way worlds are saved to reduce disk usage and to force proper saves
  166. saving:
  167. # Whether Saving should be loaded on startup
  168. enabled: true
  169. # The tick interval at which the server saves automatically (20 ticks = 1 second)
  170. autoSaveInterval: 400
  171. # The amount of chunks saved every tick when autosaving
  172. # If saving causes severe tick lag, lower it, if it takes too long, increase it
  173. autoSaveBatchSize: 20
  174. # Whether NoLagg will attempt to write all world data to the region files at a set interval
  175. # This is done on another thread, so don't worry about the main thread lagging while this happens
  176. writeDataEnabled: true
  177. # The tick interval at which the server actually writes the chunk data to file (20 ticks = 1 second)
  178. writeDataInterval: 12000
  179.  
  180. # Common features such as the clear and garbage collect commands
  181. common:
  182. # Whether Common should be loaded on startup
  183. enabled: true
  184.  
  185. # Several shortcuts you can use for the /nolagg clear(all) command
  186. clearShortcuts:
  187. enemies:
  188. - monster
  189. notneutral:
  190. - monster
  191. - item
  192. - tnt
  193. - egg
  194. - arrow
  195.  
  196. # Notifies the current stack trace of the main thread when the server freezes
  197. threadlocknotifier:
  198. # Whether ThreadLockNotifier should be loaded on startup
  199. enabled: true
  200.  
  201. # Notifies when a main-thread only event is called from another thread to detect instabilities it may cause
  202. threadcheck:
  203. # Whether ThreadCheck should be loaded on startup
  204. enabled: true
Advertisement
Add Comment
Please, Sign In to add comment