API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Jul 15th, 2019
162
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 184.41 KB | None | 0 0
raw download clone embed print report
  1. [00:45:19] [Server thread/INFO]: Starting minecraft server version 1.8.8
  2. [00:45:19] [Server thread/INFO]: Loading properties
  3. [00:45:19] [Server thread/INFO]: Default game type: SURVIVAL
  4. [00:45:19] [Server thread/INFO]: This server is running CraftBukkit version git-PaperSpigot-"8b18730" (MC: 1.8.8) (Implementing API version 1.8.8-R0.1-SNAPSHOT)
  5. [00:45:19] [Server thread/INFO]: Spigot Timings: true - Verbose: true - Interval: 5m - Length: 60m
  6. [00:45:19] [Server thread/INFO]: Server Ping Player Sample Count: 12
  7. [00:45:19] [Server thread/INFO]: Using 4 threads for Netty based IO
  8. [00:45:19] [Server thread/INFO]: Debug logging is disabled
  9. [00:45:19] [Server thread/INFO]: Data value allowed items:
  10. [00:45:19] [Server thread/INFO]: Generating keypair
  11. [00:45:19] [Server thread/INFO]: Starting Minecraft server on 10.0.176.40:41310
  12. [00:45:19] [Server thread/INFO]: Set PluginClassLoader as parallel capable
  13. [00:45:19] [Server thread/ERROR]: Could not load 'plugins/HideandCustomPlugins.jar' in folder 'plugins'
  14. org.bukkit.plugin.UnknownDependencyException: ProtocolLib
  15. at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager.java:219) [server.jar:git-PaperSpigot-"8b18730"]
  16. at org.bukkit.craftbukkit.v1_8_R3.CraftServer.loadPlugins(CraftServer.java:293) [server.jar:git-PaperSpigot-"8b18730"]
  17. at net.minecraft.server.v1_8_R3.DedicatedServer.init(DedicatedServer.java:202) [server.jar:git-PaperSpigot-"8b18730"]
  18. at net.minecraft.server.v1_8_R3.MinecraftServer.run(MinecraftServer.java:563) [server.jar:git-PaperSpigot-"8b18730"]
  19. at java.lang.Thread.run(Thread.java:748) [?:1.8.0_172]
  20. [00:45:20] [Server thread/INFO]: [CleanroomGenerator] Loading CleanroomGenerator v1.0.0
  21. [00:45:20] [Server thread/INFO]: [WorldEdit] Loading WorldEdit v6.1;no_git_id
  22. [00:45:20] [Server thread/INFO]: [Skript] Loading Skript v2.1.2
  23. [00:45:20] [Server thread/INFO]: [WorldGuard] Loading WorldGuard v6.2.1;84bc322
  24. [00:45:20] [Server thread/INFO]: [LotusPierozki] Loading LotusPierozki v1.0
  25. [00:45:20] [Server thread/INFO]: [SkinsRestorer] Loading SkinsRestorer v13.7.1
  26. [00:45:20] [Server thread/INFO]: [MaxBans] Loading MaxBans v2.7
  27. [00:45:20] [Server thread/INFO]: [UltimateStone] Loading UltimateStone v2.5
  28. [00:45:20] [Server thread/INFO]: [Drop] Loading Drop v1.0.0
  29. [00:45:20] [Server thread/INFO]: [PermissionsEx] Loading PermissionsEx v1.23.4
  30. [00:45:20] [Server thread/WARN]: [PermissionsEx] This server is in offline mode. Unless this server is configured to integrate with a supported proxy (see http://dft.ba/-8ous), UUIDs *may not be stable*!
  31. [00:45:20] [Server thread/INFO]: [iConomy] Loading iConomy v7.0
  32. [00:45:20] [Server thread/INFO]: [FeatherBoard] Loading FeatherBoard v1.11.2
  33. [00:45:20] [Server thread/INFO]: [AntiDisconnectSpam] Loading AntiDisconnectSpam v1.0
  34. [00:45:20] [Server thread/INFO]: [ViaVersion] Loading ViaVersion v2.1.2
  35. [00:45:20] [Server thread/INFO]: [ViaVersion] ViaVersion 2.1.2 is now loaded, waiting for boot. (late-bind)
  36. [00:45:20] [Server thread/INFO]: [SDTSpawner] Loading SDTSpawner v1.1
  37. [00:45:20] [Server thread/INFO]: [Tablist] Loading Tablist v1.2.3.7
  38. [00:45:20] [Server thread/INFO]: [Vault] Loading Vault v1.5.3-b37
  39. [00:45:20] [Server thread/INFO]: [ChestShop] Loading ChestShop v3.8.12
  40. [00:45:20] [Server thread/INFO]: [Essentials] Loading Essentials v2.17.0.0
  41. [00:45:20] [Server thread/INFO]: [JoinMessagePlus] Loading JoinMessagePlus v3.1
  42. [00:45:20] [Server thread/INFO]: [ASkyBlock] Loading ASkyBlock v3.0.9.4
  43. [00:45:20] [Server thread/INFO]: [EssentialsChat] Loading EssentialsChat v2.17.0.0
  44. [00:45:20] [Server thread/INFO]: [UltimateCasino] Loading UltimateCasino v1.4.0
  45. [00:45:20] [Server thread/INFO]: [IslandBorder] Loading IslandBorder vBuild 1
  46. [00:45:20] [Server thread/INFO]: [EssentialsSpawn] Loading EssentialsSpawn v2.17.0.0
  47. [00:45:20] [Server thread/INFO]: [Multiverse-Core] Loading Multiverse-Core v2.5-b665
  48. [00:45:20] [Server thread/INFO]: [AuthMe] Loading AuthMe v3.4
  49. [00:45:20] [Server thread/INFO]: [CleanroomGenerator] Enabling CleanroomGenerator v1.0.0
  50. [00:45:20] [Server thread/INFO]: [CleanroomGenerator] CleanroomGenerator v1.0.0 enabled
  51. [00:45:20] [Server thread/INFO]: [Vault] Enabling Vault v1.5.3-b37
  52. [00:45:20] [Server thread/INFO]: [Vault] [Economy] Essentials Economy found: Waiting
  53. [00:45:20] [Server thread/WARN]: iConomy - If you are using Flatfile storage be aware that versions 6, 7 and 8 have a CRITICAL bug which can wipe ALL iconomy data.
  54. [00:45:20] [Server thread/WARN]: if you're using Votifier, or any other plugin which handles economy data in a threaded manner your server is at risk!
  55. [00:45:20] [Server thread/WARN]: it is highly suggested to use SQL with iCo6 or to use an alternative economy plugin!
  56. [00:45:20] [Server thread/INFO]: [Vault] [Economy] iConomy 6 found: Waiting
  57. [00:45:20] [Server thread/INFO]: [Vault] [Permission] PermissionsEx found: Waiting
  58. [00:45:20] [Server thread/INFO]: [Vault] [Permission] SuperPermissions loaded as backup permission system.
  59. [00:45:20] [Server thread/INFO]: [Vault] [Chat] PermissionsEx found: Waiting
  60. [00:45:20] [Server thread/INFO]: [Vault] Enabled Version 1.5.3-b37
  61. [00:45:20] [Server thread/INFO]: [ASkyBlock] Enabling ASkyBlock v3.0.9.4
  62. [00:45:20] [Server thread/INFO]: [ASkyBlock] The Nether is disabled
  63. [00:45:20] [Server thread/INFO]: [ASkyBlock] Loading entity limits
  64. [00:45:20] [Server thread/INFO]: [ASkyBlock] HOPPER will be limited to 1000
  65. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (BEETROOT_BLOCK) in blockvalues.yml blocks section. Skipping...
  66. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (BLACK_GLAZED_TERRACOTTA) in blockvalues.yml blocks section. Skipping...
  67. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (BLACK_SHULKER_BOX) in blockvalues.yml blocks section. Skipping...
  68. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (BLUE_GLAZED_TERRACOTTA) in blockvalues.yml blocks section. Skipping...
  69. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (BLUE_SHULKER_BOX) in blockvalues.yml blocks section. Skipping...
  70. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (BOAT_ACACIA) in blockvalues.yml blocks section. Skipping...
  71. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (BOAT_BIRCH) in blockvalues.yml blocks section. Skipping...
  72. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (BOAT_DARK_OAK) in blockvalues.yml blocks section. Skipping...
  73. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (BOAT_JUNGLE) in blockvalues.yml blocks section. Skipping...
  74. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (BOAT_SPRUCE) in blockvalues.yml blocks section. Skipping...
  75. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (BONE_BLOCK) in blockvalues.yml blocks section. Skipping...
  76. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (BROWN_GLAZED_TERRACOTTA) in blockvalues.yml blocks section. Skipping...
  77. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (BROWN_SHULKER_BOX) in blockvalues.yml blocks section. Skipping...
  78. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (CHORUS_FLOWER) in blockvalues.yml blocks section. Skipping...
  79. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (CHORUS_PLANT) in blockvalues.yml blocks section. Skipping...
  80. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (CONCRETE) in blockvalues.yml blocks section. Skipping...
  81. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (CONCRETE_POWDER) in blockvalues.yml blocks section. Skipping...
  82. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (CYAN_GLAZED_TERRACOTTA) in blockvalues.yml blocks section. Skipping...
  83. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (CYAN_SHULKER_BOX) in blockvalues.yml blocks section. Skipping...
  84. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (END_BRICKS) in blockvalues.yml blocks section. Skipping...
  85. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (FROSTED_ICE) in blockvalues.yml blocks section. Skipping...
  86. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (GRASS_PATH) in blockvalues.yml blocks section. Skipping...
  87. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (GRAY_GLAZED_TERRACOTTA) in blockvalues.yml blocks section. Skipping...
  88. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (GRAY_SHULKER_BOX) in blockvalues.yml blocks section. Skipping...
  89. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (GREEN_GLAZED_TERRACOTTA) in blockvalues.yml blocks section. Skipping...
  90. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (GREEN_SHULKER_BOX) in blockvalues.yml blocks section. Skipping...
  91. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (LIGHT_BLUE_GLAZED_TERRACOTTA) in blockvalues.yml blocks section. Skipping...
  92. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (LIGHT_BLUE_SHULKER_BOX) in blockvalues.yml blocks section. Skipping...
  93. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (LIME_GLAZED_TERRACOTTA) in blockvalues.yml blocks section. Skipping...
  94. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (LIME_SHULKER_BOX) in blockvalues.yml blocks section. Skipping...
  95. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (MAGENTA_GLAZED_TERRACOTTA) in blockvalues.yml blocks section. Skipping...
  96. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (MAGENTA_SHULKER_BOX) in blockvalues.yml blocks section. Skipping...
  97. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (MAGMA) in blockvalues.yml blocks section. Skipping...
  98. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (NETHER_WART_BLOCK) in blockvalues.yml blocks section. Skipping...
  99. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (OBSERVER) in blockvalues.yml blocks section. Skipping...
  100. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (ORANGE_GLAZED_TERRACOTTA) in blockvalues.yml blocks section. Skipping...
  101. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (ORANGE_SHULKER_BOX) in blockvalues.yml blocks section. Skipping...
  102. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (PINK_GLAZED_TERRACOTTA) in blockvalues.yml blocks section. Skipping...
  103. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (PINK_SHULKER_BOX) in blockvalues.yml blocks section. Skipping...
  104. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (PURPLE_GLAZED_TERRACOTTA) in blockvalues.yml blocks section. Skipping...
  105. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (PURPLE_SHULKER_BOX) in blockvalues.yml blocks section. Skipping...
  106. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (PURPUR_BLOCK) in blockvalues.yml blocks section. Skipping...
  107. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (PURPUR_DOUBLE_SLAB) in blockvalues.yml blocks section. Skipping...
  108. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (PURPUR_PILLAR) in blockvalues.yml blocks section. Skipping...
  109. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (PURPUR_SLAB) in blockvalues.yml blocks section. Skipping...
  110. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (PURPUR_STAIRS) in blockvalues.yml blocks section. Skipping...
  111. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (RED_GLAZED_TERRACOTTA) in blockvalues.yml blocks section. Skipping...
  112. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (RED_NETHER_BRICK) in blockvalues.yml blocks section. Skipping...
  113. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (RED_SHULKER_BOX) in blockvalues.yml blocks section. Skipping...
  114. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (SILVER_GLAZED_TERRACOTTA) in blockvalues.yml blocks section. Skipping...
  115. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (SILVER_SHULKER_BOX) in blockvalues.yml blocks section. Skipping...
  116. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (WHITE_GLAZED_TERRACOTTA) in blockvalues.yml blocks section. Skipping...
  117. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (WHITE_SHULKER_BOX) in blockvalues.yml blocks section. Skipping...
  118. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (YELLOW_GLAZED_TERRACOTTA) in blockvalues.yml blocks section. Skipping...
  119. [00:45:20] [Server thread/WARN]: [ASkyBlock] Unknown material (YELLOW_SHULKER_BOX) in blockvalues.yml blocks section. Skipping...
  120. [00:45:20] [Server thread/INFO]: [ASkyBlock] Loaded default island schematic.
  121. [00:45:20] [Server thread/WARN]: Spawner setting of WITHER_SKELETON is unknown for this server. Skipping.
  122. [00:45:20] [Server thread/INFO]: [ASkyBlock] Loaded default nether schematic.
  123. [00:45:20] [Server thread/INFO]: [ASkyBlock] Loading schematic Normalna (island.schematic) for all players, order 1
  124. [00:45:20] [Server thread/WARN]: Spawner setting of WITHER_SKELETON is unknown for this server. Skipping.
  125. [00:45:20] [Server thread/INFO]: [ASkyBlock] Loading schematic NetherBlock Island (nether.schematic) for all players, order 0
  126. [00:45:20] [Server thread/INFO]: [ASkyBlock] Loading schematic Podwójna (double.schematic) for all players, order 2
  127. [00:45:20] [Server thread/INFO]: [ASkyBlock] Loading schematic Trudna (harder.schematic) for all players, order 3
  128. [00:45:20] [Server thread/INFO]: [ASkyBlock] Loading offline messages...
  129. [00:45:20] [Server thread/WARN]: **** SERVER IS RUNNING IN OFFLINE/INSECURE MODE!
  130. [00:45:20] [Server thread/WARN]: The server will make no attempt to authenticate usernames. Beware.
  131. [00:45:20] [Server thread/WARN]: While this makes the game possible to play without internet access, it also opens up the ability for hackers to connect with any username they choose.
  132. [00:45:20] [Server thread/WARN]: To change this, set "online-mode" to "true" in the server.properties file.
  133. [00:45:20] [Server thread/INFO]: **** Beginning UUID conversion, this may take A LONG time ****
  134. [00:45:20] [Server thread/INFO]: Preparing level "world"
  135. [00:45:20] [Server thread/INFO]: -------- World Settings For [world] --------
  136. [00:45:20] [Server thread/INFO]: Anti X-Ray: true
  137. [00:45:20] [Server thread/INFO]: Engine Mode: 1
  138. [00:45:20] [Server thread/INFO]: Hidden Blocks: [14, 15, 16, 21, 48, 49, 54, 56, 73, 74, 82, 129, 130]
  139. [00:45:20] [Server thread/INFO]: Replace Blocks: [1, 5]
  140. [00:45:20] [Server thread/INFO]: Mob Spawn Range: 3
  141. [00:45:20] [Server thread/INFO]: Nerfing mobs spawned from spawners: true
  142. [00:45:20] [Server thread/INFO]: Cactus Growth Modifier: 100%
  143. [00:45:20] [Server thread/INFO]: Cane Growth Modifier: 100%
  144. [00:45:20] [Server thread/INFO]: Melon Growth Modifier: 100%
  145. [00:45:20] [Server thread/INFO]: Mushroom Growth Modifier: 100%
  146. [00:45:20] [Server thread/INFO]: Pumpkin Growth Modifier: 100%
  147. [00:45:20] [Server thread/INFO]: Sapling Growth Modifier: 100%
  148. [00:45:20] [Server thread/INFO]: Wheat Growth Modifier: 100%
  149. [00:45:20] [Server thread/INFO]: NetherWart Growth Modifier: 100%
  150. [00:45:20] [Server thread/INFO]: Entity Activation Range: An 6 / Mo 16 / Mi 2
  151. [00:45:20] [Server thread/INFO]: Entity Tracking Range: Pl 48 / An 48 / Mo 48 / Mi 32 / Other 64
  152. [00:45:20] [Server thread/INFO]: Hopper Transfer: 24 Hopper Check: 24 Hopper Amount: 5
  153. [00:45:20] [Server thread/INFO]: Random Lighting Updates: false
  154. [00:45:20] [Server thread/INFO]: Structure Info Saving: true
  155. [00:45:20] [Server thread/INFO]: Sending up to 10 chunks per packet
  156. [00:45:20] [Server thread/INFO]: Max Entity Collisions: 2
  157. [00:45:20] [Server thread/INFO]: Custom Map Seeds: Village: 10387312 Feature: 14357617
  158. [00:45:20] [Server thread/INFO]: Max TNT Explosions: 100
  159. [00:45:20] [Server thread/INFO]: Tile Max Tick Time: 20ms Entity max Tick Time: 20ms
  160. [00:45:20] [Server thread/INFO]: Item Despawn Rate: 6000
  161. [00:45:20] [Server thread/INFO]: Item Merge Radius: 3.5
  162. [00:45:20] [Server thread/INFO]: Arrow Despawn Rate: 1200
  163. [00:45:20] [Server thread/INFO]: Allow Zombie Pigmen to spawn from portal blocks: true
  164. [00:45:20] [Server thread/INFO]: View Distance: 8
  165. [00:45:20] [Server thread/INFO]: Zombie Aggressive Towards Villager: true
  166. [00:45:20] [Server thread/INFO]: Chunks to Grow per Tick: 650
  167. [00:45:20] [Server thread/INFO]: Clear tick list: false
  168. [00:45:20] [Server thread/INFO]: Experience Merge Radius: 6.0
  169. [00:45:20] [Server thread/INFO]: -------- World Settings For [world] --------
  170. [00:45:20] [Server thread/INFO]: Player blocking damage multiplier set to 0.5
  171. [00:45:20] [Server thread/INFO]: Remove invalid mob spawner tile entities: true
  172. [00:45:20] [Server thread/INFO]: Squids will spawn between Y: 45.0 and Y: 63.0
  173. [00:45:20] [Server thread/INFO]: Max height for cactus growth 3. Max height for reed growth 3
  174. [00:45:20] [Server thread/INFO]: Living Entity Despawn Ranges: Soft: 32 Hard: 128
  175. [00:45:20] [Server thread/INFO]: Water over lava flow speed: 5
  176. [00:45:20] [Server thread/INFO]: Fix TNT cannons: false
  177. [00:45:20] [Server thread/INFO]: Allow undead horse types to be leashed: false
  178. [00:45:20] [Server thread/INFO]: Keep spawn chunk loaded: true
  179. [00:45:20] [Server thread/INFO]: World async lighting: false
  180. [00:45:20] [Server thread/INFO]: WorldServer TickNextTick cap set at 10000
  181. [00:45:20] [Server thread/INFO]: WorldServer TickNextTickList cap always processes redstone: false
  182. [00:45:20] [Server thread/INFO]: -------- World Settings For [world_nether] --------
  183. [00:45:20] [Server thread/INFO]: Anti X-Ray: true
  184. [00:45:20] [Server thread/INFO]: Engine Mode: 1
  185. [00:45:20] [Server thread/INFO]: Hidden Blocks: [14, 15, 16, 21, 48, 49, 54, 56, 73, 74, 82, 129, 130]
  186. [00:45:20] [Server thread/INFO]: Replace Blocks: [1, 5]
  187. [00:45:20] [Server thread/INFO]: Mob Spawn Range: 3
  188. [00:45:20] [Server thread/INFO]: Nerfing mobs spawned from spawners: true
  189. [00:45:20] [Server thread/INFO]: Cactus Growth Modifier: 100%
  190. [00:45:20] [Server thread/INFO]: Cane Growth Modifier: 100%
  191. [00:45:20] [Server thread/INFO]: Melon Growth Modifier: 100%
  192. [00:45:20] [Server thread/INFO]: Mushroom Growth Modifier: 100%
  193. [00:45:20] [Server thread/INFO]: Pumpkin Growth Modifier: 100%
  194. [00:45:20] [Server thread/INFO]: Sapling Growth Modifier: 100%
  195. [00:45:20] [Server thread/INFO]: Wheat Growth Modifier: 100%
  196. [00:45:20] [Server thread/INFO]: NetherWart Growth Modifier: 100%
  197. [00:45:20] [Server thread/INFO]: Entity Activation Range: An 6 / Mo 16 / Mi 2
  198. [00:45:20] [Server thread/INFO]: Entity Tracking Range: Pl 48 / An 48 / Mo 48 / Mi 32 / Other 64
  199. [00:45:20] [Server thread/INFO]: Hopper Transfer: 24 Hopper Check: 24 Hopper Amount: 5
  200. [00:45:20] [Server thread/INFO]: Random Lighting Updates: false
  201. [00:45:20] [Server thread/INFO]: Structure Info Saving: true
  202. [00:45:20] [Server thread/INFO]: Sending up to 10 chunks per packet
  203. [00:45:20] [Server thread/INFO]: Max Entity Collisions: 2
  204. [00:45:20] [Server thread/INFO]: Custom Map Seeds: Village: 10387312 Feature: 14357617
  205. [00:45:20] [Server thread/INFO]: Max TNT Explosions: 100
  206. [00:45:20] [Server thread/INFO]: Tile Max Tick Time: 20ms Entity max Tick Time: 20ms
  207. [00:45:20] [Server thread/INFO]: Item Despawn Rate: 6000
  208. [00:45:20] [Server thread/INFO]: Item Merge Radius: 3.5
  209. [00:45:20] [Server thread/INFO]: Arrow Despawn Rate: 1200
  210. [00:45:20] [Server thread/INFO]: Allow Zombie Pigmen to spawn from portal blocks: true
  211. [00:45:20] [Server thread/INFO]: View Distance: 8
  212. [00:45:20] [Server thread/INFO]: Zombie Aggressive Towards Villager: true
  213. [00:45:20] [Server thread/INFO]: Chunks to Grow per Tick: 650
  214. [00:45:20] [Server thread/INFO]: Clear tick list: false
  215. [00:45:20] [Server thread/INFO]: Experience Merge Radius: 6.0
  216. [00:45:21] [Server thread/INFO]: -------- World Settings For [world_nether] --------
  217. [00:45:21] [Server thread/INFO]: Player blocking damage multiplier set to 0.5
  218. [00:45:21] [Server thread/INFO]: Remove invalid mob spawner tile entities: true
  219. [00:45:21] [Server thread/INFO]: Squids will spawn between Y: 45.0 and Y: 63.0
  220. [00:45:21] [Server thread/INFO]: Max height for cactus growth 3. Max height for reed growth 3
  221. [00:45:21] [Server thread/INFO]: Living Entity Despawn Ranges: Soft: 32 Hard: 128
  222. [00:45:21] [Server thread/INFO]: Water over lava flow speed: 5
  223. [00:45:21] [Server thread/INFO]: Fix TNT cannons: false
  224. [00:45:21] [Server thread/INFO]: Allow undead horse types to be leashed: false
  225. [00:45:21] [Server thread/INFO]: Keep spawn chunk loaded: true
  226. [00:45:21] [Server thread/INFO]: World async lighting: false
  227. [00:45:21] [Server thread/INFO]: WorldServer TickNextTick cap set at 10000
  228. [00:45:21] [Server thread/INFO]: WorldServer TickNextTickList cap always processes redstone: false
  229. [00:45:21] [Server thread/INFO]: -------- World Settings For [world_the_end] --------
  230. [00:45:21] [Server thread/INFO]: Anti X-Ray: true
  231. [00:45:21] [Server thread/INFO]: Engine Mode: 1
  232. [00:45:21] [Server thread/INFO]: Hidden Blocks: [14, 15, 16, 21, 48, 49, 54, 56, 73, 74, 82, 129, 130]
  233. [00:45:21] [Server thread/INFO]: Replace Blocks: [1, 5]
  234. [00:45:21] [Server thread/INFO]: Mob Spawn Range: 3
  235. [00:45:21] [Server thread/INFO]: Nerfing mobs spawned from spawners: true
  236. [00:45:21] [Server thread/INFO]: Cactus Growth Modifier: 100%
  237. [00:45:21] [Server thread/INFO]: Cane Growth Modifier: 100%
  238. [00:45:21] [Server thread/INFO]: Melon Growth Modifier: 100%
  239. [00:45:21] [Server thread/INFO]: Mushroom Growth Modifier: 100%
  240. [00:45:21] [Server thread/INFO]: Pumpkin Growth Modifier: 100%
  241. [00:45:21] [Server thread/INFO]: Sapling Growth Modifier: 100%
  242. [00:45:21] [Server thread/INFO]: Wheat Growth Modifier: 100%
  243. [00:45:21] [Server thread/INFO]: NetherWart Growth Modifier: 100%
  244. [00:45:21] [Server thread/INFO]: Entity Activation Range: An 6 / Mo 16 / Mi 2
  245. [00:45:21] [Server thread/INFO]: Entity Tracking Range: Pl 48 / An 48 / Mo 48 / Mi 32 / Other 64
  246. [00:45:21] [Server thread/INFO]: Hopper Transfer: 24 Hopper Check: 24 Hopper Amount: 5
  247. [00:45:21] [Server thread/INFO]: Random Lighting Updates: false
  248. [00:45:21] [Server thread/INFO]: Structure Info Saving: true
  249. [00:45:21] [Server thread/INFO]: Sending up to 10 chunks per packet
  250. [00:45:21] [Server thread/INFO]: Max Entity Collisions: 2
  251. [00:45:21] [Server thread/INFO]: Custom Map Seeds: Village: 10387312 Feature: 14357617
  252. [00:45:21] [Server thread/INFO]: Max TNT Explosions: 100
  253. [00:45:21] [Server thread/INFO]: Tile Max Tick Time: 20ms Entity max Tick Time: 20ms
  254. [00:45:21] [Server thread/INFO]: Item Despawn Rate: 6000
  255. [00:45:21] [Server thread/INFO]: Item Merge Radius: 3.5
  256. [00:45:21] [Server thread/INFO]: Arrow Despawn Rate: 1200
  257. [00:45:21] [Server thread/INFO]: Allow Zombie Pigmen to spawn from portal blocks: true
  258. [00:45:21] [Server thread/INFO]: View Distance: 8
  259. [00:45:21] [Server thread/INFO]: Zombie Aggressive Towards Villager: true
  260. [00:45:21] [Server thread/INFO]: Chunks to Grow per Tick: 650
  261. [00:45:21] [Server thread/INFO]: Clear tick list: false
  262. [00:45:21] [Server thread/INFO]: Experience Merge Radius: 6.0
  263. [00:45:21] [Server thread/INFO]: -------- World Settings For [world_the_end] --------
  264. [00:45:21] [Server thread/INFO]: Player blocking damage multiplier set to 0.5
  265. [00:45:21] [Server thread/INFO]: Remove invalid mob spawner tile entities: true
  266. [00:45:21] [Server thread/INFO]: Squids will spawn between Y: 45.0 and Y: 63.0
  267. [00:45:21] [Server thread/INFO]: Max height for cactus growth 3. Max height for reed growth 3
  268. [00:45:21] [Server thread/INFO]: Living Entity Despawn Ranges: Soft: 32 Hard: 128
  269. [00:45:21] [Server thread/INFO]: Water over lava flow speed: 5
  270. [00:45:21] [Server thread/INFO]: Fix TNT cannons: false
  271. [00:45:21] [Server thread/INFO]: Allow undead horse types to be leashed: false
  272. [00:45:21] [Server thread/INFO]: Keep spawn chunk loaded: true
  273. [00:45:21] [Server thread/INFO]: World async lighting: false
  274. [00:45:21] [Server thread/INFO]: WorldServer TickNextTick cap set at 10000
  275. [00:45:21] [Server thread/INFO]: WorldServer TickNextTickList cap always processes redstone: false
  276. [00:45:21] [Server thread/INFO]: Preparing start region for level 0 (Seed: 2478252723993360312)
  277. [00:45:21] [Server thread/INFO]: -------- World Settings For [ASkyBlock] --------
  278. [00:45:21] [Server thread/INFO]: Anti X-Ray: true
  279. [00:45:21] [Server thread/INFO]: Engine Mode: 1
  280. [00:45:21] [Server thread/INFO]: Hidden Blocks: [14, 15, 16, 21, 48, 49, 54, 56, 73, 74, 82, 129, 130]
  281. [00:45:21] [Server thread/INFO]: Replace Blocks: [1, 5]
  282. [00:45:21] [Server thread/INFO]: Mob Spawn Range: 3
  283. [00:45:21] [Server thread/INFO]: Nerfing mobs spawned from spawners: true
  284. [00:45:21] [Server thread/INFO]: Cactus Growth Modifier: 100%
  285. [00:45:21] [Server thread/INFO]: Cane Growth Modifier: 100%
  286. [00:45:21] [Server thread/INFO]: Melon Growth Modifier: 100%
  287. [00:45:21] [Server thread/INFO]: Mushroom Growth Modifier: 100%
  288. [00:45:21] [Server thread/INFO]: Pumpkin Growth Modifier: 100%
  289. [00:45:21] [Server thread/INFO]: Sapling Growth Modifier: 100%
  290. [00:45:21] [Server thread/INFO]: Wheat Growth Modifier: 100%
  291. [00:45:21] [Server thread/INFO]: NetherWart Growth Modifier: 100%
  292. [00:45:21] [Server thread/INFO]: Entity Activation Range: An 6 / Mo 16 / Mi 2
  293. [00:45:21] [Server thread/INFO]: Entity Tracking Range: Pl 48 / An 48 / Mo 48 / Mi 32 / Other 64
  294. [00:45:21] [Server thread/INFO]: Hopper Transfer: 24 Hopper Check: 24 Hopper Amount: 5
  295. [00:45:21] [Server thread/INFO]: Random Lighting Updates: false
  296. [00:45:21] [Server thread/INFO]: Structure Info Saving: true
  297. [00:45:21] [Server thread/INFO]: Sending up to 10 chunks per packet
  298. [00:45:21] [Server thread/INFO]: Max Entity Collisions: 2
  299. [00:45:21] [Server thread/INFO]: Custom Map Seeds: Village: 10387312 Feature: 14357617
  300. [00:45:21] [Server thread/INFO]: Max TNT Explosions: 100
  301. [00:45:21] [Server thread/INFO]: Tile Max Tick Time: 20ms Entity max Tick Time: 20ms
  302. [00:45:21] [Server thread/INFO]: Item Despawn Rate: 6000
  303. [00:45:21] [Server thread/INFO]: Item Merge Radius: 3.5
  304. [00:45:21] [Server thread/INFO]: Arrow Despawn Rate: 1200
  305. [00:45:21] [Server thread/INFO]: Allow Zombie Pigmen to spawn from portal blocks: true
  306. [00:45:21] [Server thread/INFO]: View Distance: 8
  307. [00:45:21] [Server thread/INFO]: Zombie Aggressive Towards Villager: true
  308. [00:45:21] [Server thread/INFO]: Chunks to Grow per Tick: 650
  309. [00:45:21] [Server thread/INFO]: Clear tick list: false
  310. [00:45:21] [Server thread/INFO]: Experience Merge Radius: 6.0
  311. [00:45:21] [Server thread/INFO]: -------- World Settings For [ASkyBlock] --------
  312. [00:45:21] [Server thread/INFO]: Player blocking damage multiplier set to 0.5
  313. [00:45:21] [Server thread/INFO]: Remove invalid mob spawner tile entities: true
  314. [00:45:21] [Server thread/INFO]: Squids will spawn between Y: 45.0 and Y: 63.0
  315. [00:45:21] [Server thread/INFO]: Max height for cactus growth 3. Max height for reed growth 3
  316. [00:45:21] [Server thread/INFO]: Living Entity Despawn Ranges: Soft: 32 Hard: 128
  317. [00:45:21] [Server thread/INFO]: Water over lava flow speed: 5
  318. [00:45:21] [Server thread/INFO]: Fix TNT cannons: false
  319. [00:45:21] [Server thread/INFO]: Allow undead horse types to be leashed: false
  320. [00:45:21] [Server thread/INFO]: Keep spawn chunk loaded: true
  321. [00:45:21] [Server thread/INFO]: World async lighting: false
  322. [00:45:21] [Server thread/INFO]: WorldServer TickNextTick cap set at 10000
  323. [00:45:21] [Server thread/INFO]: WorldServer TickNextTickList cap always processes redstone: false
  324. [00:45:21] [Server thread/INFO]: Preparing start region for level 3 (Seed: 2091329287323075022)
  325. [00:45:21] [Server thread/INFO]: Preparing start region for level 1 (Seed: 2478252723993360312)
  326. [00:45:22] [Server thread/INFO]: Preparing start region for level 2 (Seed: 2478252723993360312)
  327. [00:45:22] [Server thread/INFO]: Preparing start region for level 3 (Seed: 2091329287323075022)
  328. [00:45:22] [Server thread/INFO]: [WorldEdit] Enabling WorldEdit v6.1;no_git_id
  329. [00:45:22] [Server thread/INFO]: WEPIF: Using the Bukkit Permissions API.
  330. [00:45:22] [Server thread/INFO]: [WorldEdit] Using com.sk89q.worldedit.bukkit.adapter.impl.Spigot_v1_8_R3 as the Bukkit adapter
  331. [00:45:22] [Server thread/INFO]: [Skript] Enabling Skript v2.1.2
  332. [00:45:22] [Server thread/INFO]: [Skript] Loaded a total of 11504 english aliases
  333. [00:45:22] [Server thread/WARN]: [Skript] There are no aliases defined for the following ids: 165, 166, 167, 168, 169, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197, 409, 410, 411, 412, 413, 414, 415, 416, 423, 424, 425, 427, 428, 429, 430, 431
  334. [00:45:22] [Server thread/INFO]: [Skript] ~ created by & © Peter Güttinger aka Njol ~
  335. [00:45:22] [Server thread/INFO]: [WorldGuard] Enabling WorldGuard v6.2.1;84bc322
  336. [00:45:22] [Server thread/INFO]: [WorldGuard] (world) TNT ignition is PERMITTED.
  337. [00:45:22] [Server thread/INFO]: [WorldGuard] (world) Lighters are PERMITTED.
  338. [00:45:22] [Server thread/INFO]: [WorldGuard] (world) Lava fire is blocked.
  339. [00:45:22] [Server thread/INFO]: [WorldGuard] (world) Fire spread is UNRESTRICTED.
  340. [00:45:22] [Server thread/INFO]: [WorldGuard] Loaded configuration for world 'world'
  341. [00:45:22] [Server thread/INFO]: [WorldGuard] (world_nether) TNT ignition is PERMITTED.
  342. [00:45:22] [Server thread/INFO]: [WorldGuard] (world_nether) Lighters are PERMITTED.
  343. [00:45:22] [Server thread/INFO]: [WorldGuard] (world_nether) Lava fire is blocked.
  344. [00:45:22] [Server thread/INFO]: [WorldGuard] (world_nether) Fire spread is UNRESTRICTED.
  345. [00:45:22] [Server thread/INFO]: [WorldGuard] Loaded configuration for world 'world_nether'
  346. [00:45:22] [Server thread/INFO]: [WorldGuard] (world_the_end) TNT ignition is PERMITTED.
  347. [00:45:22] [Server thread/INFO]: [WorldGuard] (world_the_end) Lighters are PERMITTED.
  348. [00:45:22] [Server thread/INFO]: [WorldGuard] (world_the_end) Lava fire is blocked.
  349. [00:45:22] [Server thread/INFO]: [WorldGuard] (world_the_end) Fire spread is UNRESTRICTED.
  350. [00:45:22] [Server thread/INFO]: [WorldGuard] Loaded configuration for world 'world_the_end'
  351. [00:45:22] [Server thread/INFO]: [WorldGuard] (ASkyBlock) TNT ignition is PERMITTED.
  352. [00:45:22] [Server thread/INFO]: [WorldGuard] (ASkyBlock) Lighters are PERMITTED.
  353. [00:45:22] [Server thread/INFO]: [WorldGuard] (ASkyBlock) Lava fire is blocked.
  354. [00:45:22] [Server thread/INFO]: [WorldGuard] (ASkyBlock) Fire spread is UNRESTRICTED.
  355. [00:45:22] [Server thread/INFO]: [WorldGuard] Loaded configuration for world 'ASkyBlock'
  356. [00:45:22] [Server thread/INFO]: [WorldGuard] Loading region data...
  357. [00:45:23] [Server thread/INFO]: [LotusPierozki] Enabling LotusPierozki v1.0
  358. [00:45:23] [Server thread/INFO]: [SkinsRestorer] Enabling SkinsRestorer v13.7.1
  359. [00:45:23] [Server thread/INFO]: [SkinsRestorer] Detected Minecraft v1_8_R3, using UniversalSkinFactory.
  360. [00:45:23] [Server thread/INFO]: [MaxBans] Enabling MaxBans v2.7
  361. [00:45:23] [Server thread/INFO]: [MaxBans] Using SQLite
  362. [00:45:23] [Server thread/INFO]: [MaxBans] Loading from DB...
  363. [00:45:23] [Server thread/INFO]: [MaxBans] Loading bans
  364. [00:45:23] [Server thread/INFO]: [MaxBans] Loading ipbans
  365. [00:45:23] [Server thread/INFO]: [MaxBans] Loading mutes
  366. [00:45:23] [Server thread/INFO]: [MaxBans] Loading player names...
  367. [00:45:23] [Server thread/INFO]: [MaxBans] Loading IP History
  368. [00:45:23] [Server thread/INFO]: [MaxBans] Loading warn history...
  369. [00:45:23] [Server thread/INFO]: [MaxBans] Loading chat commands...
  370. [00:45:23] [Server thread/INFO]: [MaxBans] Loading history...
  371. [00:45:23] [Server thread/INFO]: [MaxBans] Starting DNS blacklist
  372. [00:45:23] [Server thread/INFO]: [MaxBans] Loading proxys...
  373. [00:45:23] [Server thread/INFO]: [UltimateStone] Enabling UltimateStone v2.5
  374. [00:45:23] [Server thread/INFO]: [UltimateStone] Created by 3rr0r has been started!
  375. [00:45:23] [Server thread/INFO]: [Drop] Enabling Drop v1.0.0
  376. [00:45:23] [Server thread/INFO]: [PermissionsEx] Enabling PermissionsEx v1.23.4
  377. [00:45:23] [Server thread/INFO]: [PermissionsEx] Initializing file backend
  378. [00:45:23] [Server thread/INFO]: [PermissionsEx] Permissions file successfully reloaded
  379. [00:45:23] [Server thread/INFO]: WEPIF: PermissionsEx detected! Using PermissionsEx for permissions.
  380. [00:45:23] [Server thread/INFO]: [Vault][Permission] PermissionsEx hooked.
  381. [00:45:23] [Server thread/INFO]: [Vault][Chat] PermissionsEx_Chat hooked.
  382. [00:45:23] [Server thread/INFO]: [iConomy] Enabling iConomy v7.0
  383. [00:45:23] [Server thread/INFO]: [iConomy - April Fools] Enabled (6 ms)
  384. [00:45:23] [Server thread/INFO]: [iConomy] Hello, I'm Nijikokun. Yes, this is an April Fools joke, but '/money top' was fixed! Enjoy :) - Rare Version!
  385. [00:45:23] [Server thread/INFO]: [Vault][Economy] iConomy 7 hooked.
  386. [00:45:23] [Server thread/INFO]: [FeatherBoard] Enabling FeatherBoard v1.11.2
  387. [00:45:23] [Server thread/INFO]: [FeatherBoard] -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
  388. [00:45:23] [Server thread/INFO]: [FeatherBoard] Plugin: FeatherBoard v1.11.2
  389. [00:45:23] [Server thread/INFO]: [FeatherBoard] Framework version: 2015-01
  390. [00:45:23] [Server thread/INFO]: [FeatherBoard] Author: Maximvdw
  391. [00:45:23] [Server thread/INFO]: [FeatherBoard] Site: http://www.mvdw-software.be/
  392. [00:45:23] [Server thread/INFO]: [FeatherBoard] -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
  393. [00:45:23] [Server thread/INFO]: [FeatherBoard] Loading configuration ...
  394. [00:45:23] [Thread-11/INFO]: [iConomy - April Fools] Purged accounts with default balance.
  395. [00:45:23] [Server thread/INFO]: [FeatherBoard] Loading placeholders ...
  396. [00:45:23] [Server thread/INFO]: [FeatherBoard] Downloading City database ...
  397. [00:45:23] [Server thread/INFO]: [FeatherBoard] ./plugins/MVdWPlugin/db/GeoLiteCity.dat updated
  398. [00:45:23] [Server thread/INFO]: [FeatherBoard] Downloading Country database ...
  399. [00:45:23] [Server thread/INFO]: [FeatherBoard] ./plugins/MVdWPlugin/db/GeoIP.dat updated
  400. [00:45:23] [Server thread/INFO]: [FeatherBoard] Downloading IPV6 database ...
  401. [00:45:23] [Server thread/INFO]: [FeatherBoard] ./plugins/MVdWPlugin/db/GeoIPv6.dat updated
  402. [00:45:23] [Server thread/INFO]: [FeatherBoard] Updater disabled.
  403. [00:45:23] [Server thread/INFO]: [FeatherBoard] Hooked into Multiverse!
  404. [00:45:23] [Server thread/INFO]: [FeatherBoard] Loaded 787 of the 1042 placholders
  405. [00:45:24] [Server thread/INFO]: [FeatherBoard] Adding scoreboard group 'default' ...
  406. [00:45:24] [Server thread/INFO]: [FeatherBoard] Loading messages ...
  407. [00:45:24] [Server thread/INFO]: [FeatherBoard] Loading language file: lang_en
  408. [00:45:24] [Server thread/INFO]: [FeatherBoard] ERROR: Critical startup error. Please update your plugin!
  409. If the error persists after updating, contact Maximvdw through spigot PM
  410. Critical startup error. Please update your plugin!
  411. If the error persists after updating, contact Maximvdw through spigot PM
  412. Critical startup error. Please update your plugin!
  413. If the error persists after updating, contact Maximvdw through spigot PM
  414. Critical startup error. Please update your plugin!
  415. If the error persists after updating, contact Maximvdw through spigot PM
  416. Critical startup error. Please update your plugin!
  417. If the error persists after updating, contact Maximvdw through spigot PM
  418. Critical startup error. Please update your plugin!
  419. If the error persists after updating, contact Maximvdw through spigot PM
  420. Critical startup error. Please update your plugin!
  421. If the error persists after updating, contact Maximvdw through spigot PM
  422. Critical startup error. Please update your plugin!
  423. If the error persists after updating, contact Maximvdw through spigot PM
  424. Critical startup error. Please update your plugin!
  425. If the error persists after updating, contact Maximvdw through spigot PM
  426. Critical startup error. Please update your plugin!
  427. If the error persists after updating, contact Maximvdw through spigot PM
  428. Critical startup error. Please update your plugin!
  429. If the error persists after updating, contact Maximvdw through spigot PM
  430. Critical startup error. Please update your plugin!
  431. If the error persists after updating, contact Maximvdw through spigot PM
  432. Critical startup error. Please update your plugin!
  433. If the error persists after updating, contact Maximvdw through spigot PM
  434. Critical startup error. Please update your plugin!
  435. If the error persists after updating, contact Maximvdw through spigot PM
  436. Critical startup error. Please update your plugin!
  437. If the error persists after updating, contact Maximvdw through spigot PM
  438. Critical startup error. Please update your plugin!
  439. If the error persists after updating, contact Maximvdw through spigot PM
  440. Critical startup error. Please update your plugin!
  441. If the error persists after updating, contact Maximvdw through spigot PM
  442. Critical startup error. Please update your plugin!
  443. If the error persists after updating, contact Maximvdw through spigot PM
  444. Critical startup error. Please update your plugin!
  445. If the error persists after updating, contact Maximvdw through spigot PM
  446. Critical startup error. Please update your plugin!
  447. If the error persists after updating, contact Maximvdw through spigot PM
  448. Critical startup error. Please update your plugin!
  449. If the error persists after updating, contact Maximvdw through spigot PM
  450. Critical startup error. Please update your plugin!
  451. If the error persists after updating, contact Maximvdw through spigot PM
  452. Critical startup error. Please update your plugin!
  453. If the error persists after updating, contact Maximvdw through spigot PM
  454. Critical startup error. Please update your plugin!
  455. If the error persists after updating, contact Maximvdw through spigot PM
  456. Critical startup error. Please update your plugin!
  457. If the error persists after updating, contact Maximvdw through spigot PM
  458. Critical startup error. Please update your plugin!
  459. If the error persists after updating, contact Maximvdw through spigot PM
  460. Critical startup error. Please update your plugin!
  461. If the error persists after updating, contact Maximvdw through spigot PM
  462. Critical startup error. Please update your plugin!
  463. If the error persists after updating, contact Maximvdw through spigot PM
  464. Critical startup error. Please update your plugin!
  465. If the error persists after updating, contact Maximvdw through spigot PM
  466. Critical startup error. Please update your plugin!
  467. If the error persists after updating, contact Maximvdw through spigot PM
  468. Critical startup error. Please update your plugin!
  469. If the error persists after updating, contact Maximvdw through spigot PM
  470. Critical startup error. Please update your plugin!
  471. If the error persists after updating, contact Maximvdw through spigot PM
  472. Critical startup error. Please update your plugin!
  473. If the error persists after updating, contact Maximvdw through spigot PM
  474. Critical startup error. Please update your plugin!
  475. If the error persists after updating, contact Maximvdw through spigot PM
  476. Critical startup error. Please update your plugin!
  477. If the error persists after updating, contact Maximvdw through spigot PM
  478. Critical startup error. Please update your plugin!
  479. If the error persists after updating, contact Maximvdw through spigot PM
  480. Critical startup error. Please update your plugin!
  481. If the error persists after updating, contact Maximvdw through spigot PM
  482. Critical startup error. Please update your plugin!
  483. If the error persists after updating, contact Maximvdw through spigot PM
  484. Critical startup error. Please update your plugin!
  485. If the error persists after updating, contact Maximvdw through spigot PM
  486. Critical startup error. Please update your plugin!
  487. If the error persists after updating, contact Maximvdw through spigot PM
  488. Critical startup error. Please update your plugin!
  489. If the error persists after updating, contact Maximvdw through spigot PM
  490. Critical startup error. Please update your plugin!
  491. If the error persists after updating, contact Maximvdw through spigot PM
  492. Critical startup error. Please update your plugin!
  493. If the error persists after updating, contact Maximvdw through spigot PM
  494. Critical startup error. Please update your plugin!
  495. If the error persists after updating, contact Maximvdw through spigot PM
  496. Critical startup error. Please update your plugin!
  497. If the error persists after updating, contact Maximvdw through spigot PM
  498. Critical startup error. Please update your plugin!
  499. If the error persists after updating, contact Maximvdw through spigot PM
  500. Critical startup error. Please update your plugin!
  501. If the error persists after updating, contact Maximvdw through spigot PM
  502. Critical startup error. Please update your plugin!
  503. If the error persists after updating, contact Maximvdw through spigot PM
  504. Critical startup error. Please update your plugin!
  505. If the error persists after updating, contact Maximvdw through spigot PM
  506. Critical startup error. Please update your plugin!
  507. If the error persists after updating, contact Maximvdw through spigot PM
  508. Critical startup error. Please update your plugin!
  509. If the error persists after updating, contact Maximvdw through spigot PM
  510. Critical startup error. Please update your plugin!
  511. If the error persists after updating, contact Maximvdw through spigot PM
  512. Critical startup error. Please update your plugin!
  513. If the error persists after updating, contact Maximvdw through spigot PM
  514. Critical startup error. Please update your plugin!
  515. If the error persists after updating, contact Maximvdw through spigot PM
  516. Critical startup error. Please update your plugin!
  517. If the error persists after updating, contact Maximvdw through spigot PM
  518. Critical startup error. Please update your plugin!
  519. If the error persists after updating, contact Maximvdw through spigot PM
  520. Critical startup error. Please update your plugin!
  521. If the error persists after updating, contact Maximvdw through spigot PM
  522. Critical startup error. Please update your plugin!
  523. If the error persists after updating, contact Maximvdw through spigot PM
  524. Critical startup error. Please update your plugin!
  525. If the error persists after updating, contact Maximvdw through spigot PM
  526. Critical startup error. Please update your plugin!
  527. If the error persists after updating, contact Maximvdw through spigot PM
  528. Critical startup error. Please update your plugin!
  529. If the error persists after updating, contact Maximvdw through spigot PM
  530. Critical startup error. Please update your plugin!
  531. If the error persists after updating, contact Maximvdw through spigot PM
  532. Critical startup error. Please update your plugin!
  533. If the error persists after updating, contact Maximvdw through spigot PM
  534. Critical startup error. Please update your plugin!
  535. If the error persists after updating, contact Maximvdw through spigot PM
  536. Critical startup error. Please update your plugin!
  537. If the error persists after updating, contact Maximvdw through spigot PM
  538. Critical startup error. Please update your plugin!
  539. If the error persists after updating, contact Maximvdw thro
  540. [00:45:24] [Server thread/INFO]: ugh spigot PM
  541. Critical startup error. Please update your plugin!
  542. If the error persists after updating, contact Maximvdw through spigot PM
  543. Critical startup error. Please update your plugin!
  544. If the error persists after updating, contact Maximvdw through spigot PM
  545. Critical startup error. Please update your plugin!
  546. If the error persists after updating, contact Maximvdw through spigot PM
  547. Critical startup error. Please update your plugin!
  548. If the error persists after updating, contact Maximvdw through spigot PM
  549. Critical startup error. Please update your plugin!
  550. If the error persists after updating, contact Maximvdw through spigot PM
  551. Critical startup error. Please update your plugin!
  552. If the error persists after updating, contact Maximvdw through spigot PM
  553. Critical startup error. Please update your plugin!
  554. If the error persists after updating, contact Maximvdw through spigot PM
  555. Critical startup error. Please update your plugin!
  556. If the error persists after updating, contact Maximvdw through spigot PM
  557. Critical startup error. Please update your plugin!
  558. If the error persists after updating, contact Maximvdw through spigot PM
  559. Critical startup error. Please update your plugin!
  560. If the error persists after updating, contact Maximvdw through spigot PM
  561. Critical startup error. Please update your plugin!
  562. If the error persists after updating, contact Maximvdw through spigot PM
  563. Critical startup error. Please update your plugin!
  564. If the error persists after updating, contact Maximvdw through spigot PM
  565. Critical startup error. Please update your plugin!
  566. If the error persists after updating, contact Maximvdw through spigot PM
  567. Critical startup error. Please update your plugin!
  568. If the error persists after updating, contact Maximvdw through spigot PM
  569. Critical startup error. Please update your plugin!
  570. If the error persists after updating, contact Maximvdw through spigot PM
  571. Critical startup error. Please update your plugin!
  572. If the error persists after updating, contact Maximvdw through spigot PM
  573. Critical startup error. Please update your plugin!
  574. If the error persists after updating, contact Maximvdw through spigot PM
  575. Critical startup error. Please update your plugin!
  576. If the error persists after updating, contact Maximvdw through spigot PM
  577. Critical startup error. Please update your plugin!
  578. If the error persists after updating, contact Maximvdw through spigot PM
  579. Critical startup error. Please update your plugin!
  580. If the error persists after updating, contact Maximvdw through spigot PM
  581. Critical startup error. Please update your plugin!
  582. If the error persists after updating, contact Maximvdw through spigot PM
  583. Critical startup error. Please update your plugin!
  584. If the error persists after updating, contact Maximvdw through spigot PM
  585. Critical startup error. Please update your plugin!
  586. If the error persists after updating, contact Maximvdw through spigot PM
  587. Critical startup error. Please update your plugin!
  588. If the error persists after updating, contact Maximvdw through spigot PM
  589. Critical startup error. Please update your plugin!
  590. If the error persists after updating, contact Maximvdw through spigot PM
  591. Critical startup error. Please update your plugin!
  592. If the error persists after updating, contact Maximvdw through spigot PM
  593. Critical startup error. Please update your plugin!
  594. If the error persists after updating, contact Maximvdw through spigot PM
  595. Critical startup error. Please update your plugin!
  596. If the error persists after updating, contact Maximvdw through spigot PM
  597. Critical startup error. Please update your plugin!
  598. If the error persists after updating, contact Maximvdw through spigot PM
  599. Critical startup error. Please update your plugin!
  600. If the error persists after updating, contact Maximvdw through spigot PM
  601. Critical startup error. Please update your plugin!
  602. If the error persists after updating, contact Maximvdw through spigot PM
  603. Critical startup error. Please update your plugin!
  604. If the error persists after updating, contact Maximvdw through spigot PM
  605. Critical startup error. Please update your plugin!
  606. If the error persists after updating, contact Maximvdw through spigot PM
  607. Critical startup error. Please update your plugin!
  608. If the error persists after updating, contact Maximvdw through spigot PM
  609. Critical startup error. Please update your plugin!
  610. If the error persists after updating, contact Maximvdw through spigot PM
  611. Critical startup error. Please update your plugin!
  612. If the error persists after updating, contact Maximvdw through spigot PM
  613. Critical startup error. Please update your plugin!
  614. If the error persists after updating, contact Maximvdw through spigot PM
  615. Critical startup error. Please update your plugin!
  616. If the error persists after updating, contact Maximvdw through spigot PM
  617. Critical startup error. Please update your plugin!
  618. If the error persists after updating, contact Maximvdw through spigot PM
  619. Critical startup error. Please update your plugin!
  620. If the error persists after updating, contact Maximvdw through spigot PM
  621. Critical startup error. Please update your plugin!
  622. If the error persists after updating, contact Maximvdw through spigot PM
  623. Critical startup error. Please update your plugin!
  624. If the error persists after updating, contact Maximvdw through spigot PM
  625. Critical startup error. Please update your plugin!
  626. If the error persists after updating, contact Maximvdw through spigot PM
  627. Critical startup error. Please update your plugin!
  628. If the error persists after updating, contact Maximvdw through spigot PM
  629. Critical startup error. Please update your plugin!
  630. If the error persists after updating, contact Maximvdw through spigot PM
  631. Critical startup error. Please update your plugin!
  632. If the error persists after updating, contact Maximvdw through spigot PM
  633. Critical startup error. Please update your plugin!
  634. If the error persists after updating, contact Maximvdw through spigot PM
  635. Critical startup error. Please update your plugin!
  636. If the error persists after updating, contact Maximvdw through spigot PM
  637. Critical startup error. Please update your plugin!
  638. If the error persists after updating, contact Maximvdw through spigot PM
  639. Critical startup error. Please update your plugin!
  640. If the error persists after updating, contact Maximvdw through spigot PM
  641. Critical startup error. Please update your plugin!
  642. If the error persists after updating, contact Maximvdw through spigot PM
  643. Critical startup error. Please update your plugin!
  644. If the error persists after updating, contact Maximvdw through spigot PM
  645. Critical startup error. Please update your plugin!
  646. If the error persists after updating, contact Maximvdw through spigot PM
  647. Critical startup error. Please update your plugin!
  648. If the error persists after updating, contact Maximvdw through spigot PM
  649. Critical startup error. Please update your plugin!
  650. If the error persists after updating, contact Maximvdw through spigot PM
  651. Critical startup error. Please update your plugin!
  652. If the error persists after updating, contact Maximvdw through spigot PM
  653. Critical startup error. Please update your plugin!
  654. If the error persists after updating, contact Maximvdw through spigot PM
  655. Critical startup error. Please update your plugin!
  656. If the error persists after updating, contact Maximvdw through spigot PM
  657. Critical startup error. Please update your plugin!
  658. If the error persists after updating, contact Maximvdw through spigot PM
  659. Critical startup error. Please update your plugin!
  660. If the error persists after updating, contact Maximvdw through spigot PM
  661. Critical startup error. Please update your plugin!
  662. If the error persists after updating, contact Maximvdw through spigot PM
  663. Critical startup error. Please update your plugin!
  664. If the error persists after updating, contact Maximvdw through spigot PM
  665. Critical startup error. Please update your plugin!
  666. If the error persists after updating, contact Maximvdw through spigot PM
  667. Critical startup error. Please update your plugin!
  668. If the error persists after updating, contact Maximvdw through spigot PM
  669. Critical startup error. Please update your plugin!
  670. If the error persists after updating, contact Maximvdw through spigot PM
  671. Critical startup error. Please update your plugin!
  672. If the error persists after updating, contact Maximvdw through spig
  673. [00:45:24] [Server thread/INFO]: ot PM
  674. Critical startup error. Please update your plugin!
  675. If the error persists after updating, contact Maximvdw through spigot PM
  676. Critical startup error. Please update your plugin!
  677. If the error persists after updating, contact Maximvdw through spigot PM
  678. Critical startup error. Please update your plugin!
  679. If the error persists after updating, contact Maximvdw through spigot PM
  680. Critical startup error. Please update your plugin!
  681. If the error persists after updating, contact Maximvdw through spigot PM
  682. Critical startup error. Please update your plugin!
  683. If the error persists after updating, contact Maximvdw through spigot PM
  684. Critical startup error. Please update your plugin!
  685. If the error persists after updating, contact Maximvdw through spigot PM
  686. Critical startup error. Please update your plugin!
  687. If the error persists after updating, contact Maximvdw through spigot PM
  688. Critical startup error. Please update your plugin!
  689. If the error persists after updating, contact Maximvdw through spigot PM
  690. Critical startup error. Please update your plugin!
  691. If the error persists after updating, contact Maximvdw through spigot PM
  692. Critical startup error. Please update your plugin!
  693. If the error persists after updating, contact Maximvdw through spigot PM
  694. Critical startup error. Please update your plugin!
  695. If the error persists after updating, contact Maximvdw through spigot PM
  696. Critical startup error. Please update your plugin!
  697. If the error persists after updating, contact Maximvdw through spigot PM
  698. Critical startup error. Please update your plugin!
  699. If the error persists after updating, contact Maximvdw through spigot PM
  700. Critical startup error. Please update your plugin!
  701. If the error persists after updating, contact Maximvdw through spigot PM
  702. Critical startup error. Please update your plugin!
  703. If the error persists after updating, contact Maximvdw through spigot PM
  704. Critical startup error. Please update your plugin!
  705. If the error persists after updating, contact Maximvdw through spigot PM
  706. Critical startup error. Please update your plugin!
  707. If the error persists after updating, contact Maximvdw through spigot PM
  708. Critical startup error. Please update your plugin!
  709. If the error persists after updating, contact Maximvdw through spigot PM
  710. Critical startup error. Please update your plugin!
  711. If the error persists after updating, contact Maximvdw through spigot PM
  712. Critical startup error. Please update your plugin!
  713. If the error persists after updating, contact Maximvdw through spigot PM
  714. Critical startup error. Please update your plugin!
  715. If the error persists after updating, contact Maximvdw through spigot PM
  716. Critical startup error. Please update your plugin!
  717. If the error persists after updating, contact Maximvdw through spigot PM
  718. Critical startup error. Please update your plugin!
  719. If the error persists after updating, contact Maximvdw through spigot PM
  720. Critical startup error. Please update your plugin!
  721. If the error persists after updating, contact Maximvdw through spigot PM
  722. Critical startup error. Please update your plugin!
  723. If the error persists after updating, contact Maximvdw through spigot PM
  724. Critical startup error. Please update your plugin!
  725. If the error persists after updating, contact Maximvdw through spigot PM
  726. Critical startup error. Please update your plugin!
  727. If the error persists after updating, contact Maximvdw through spigot PM
  728. Critical startup error. Please update your plugin!
  729. If the error persists after updating, contact Maximvdw through spigot PM
  730. Critical startup error. Please update your plugin!
  731. If the error persists after updating, contact Maximvdw through spigot PM
  732. Critical startup error. Please update your plugin!
  733. If the error persists after updating, contact Maximvdw through spigot PM
  734. Critical startup error. Please update your plugin!
  735. If the error persists after updating, contact Maximvdw through spigot PM
  736. Critical startup error. Please update your plugin!
  737. If the error persists after updating, contact Maximvdw through spigot PM
  738. Critical startup error. Please update your plugin!
  739. If the error persists after updating, contact Maximvdw through spigot PM
  740. Critical startup error. Please update your plugin!
  741. If the error persists after updating, contact Maximvdw through spigot PM
  742. Critical startup error. Please update your plugin!
  743. If the error persists after updating, contact Maximvdw through spigot PM
  744. Critical startup error. Please update your plugin!
  745. If the error persists after updating, contact Maximvdw through spigot PM
  746. Critical startup error. Please update your plugin!
  747. If the error persists after updating, contact Maximvdw through spigot PM
  748. Critical startup error. Please update your plugin!
  749. If the error persists after updating, contact Maximvdw through spigot PM
  750. Critical startup error. Please update your plugin!
  751. If the error persists after updating, contact Maximvdw through spigot PM
  752. Critical startup error. Please update your plugin!
  753. If the error persists after updating, contact Maximvdw through spigot PM
  754. Critical startup error. Please update your plugin!
  755. If the error persists after updating, contact Maximvdw through spigot PM
  756. Critical startup error. Please update your plugin!
  757. If the error persists after updating, contact Maximvdw through spigot PM
  758. Critical startup error. Please update your plugin!
  759. If the error persists after updating, contact Maximvdw through spigot PM
  760. Critical startup error. Please update your plugin!
  761. If the error persists after updating, contact Maximvdw through spigot PM
  762. Critical startup error. Please update your plugin!
  763. If the error persists after updating, contact Maximvdw through spigot PM
  764. Critical startup error. Please update your plugin!
  765. If the error persists after updating, contact Maximvdw through spigot PM
  766. Critical startup error. Please update your plugin!
  767. If the error persists after updating, contact Maximvdw through spigot PM
  768. Critical startup error. Please update your plugin!
  769. If the error persists after updating, contact Maximvdw through spigot PM
  770. Critical startup error. Please update your plugin!
  771. If the error persists after updating, contact Maximvdw through spigot PM
  772. Critical startup error. Please update your plugin!
  773. If the error persists after updating, contact Maximvdw through spigot PM
  774. Critical startup error. Please update your plugin!
  775. If the error persists after updating, contact Maximvdw through spigot PM
  776. Critical startup error. Please update your plugin!
  777. If the error persists after updating, contact Maximvdw through spigot PM
  778. Critical startup error. Please update your plugin!
  779. If the error persists after updating, contact Maximvdw through spigot PM
  780. Critical startup error. Please update your plugin!
  781. If the error persists after updating, contact Maximvdw through spigot PM
  782. Critical startup error. Please update your plugin!
  783. If the error persists after updating, contact Maximvdw through spigot PM
  784. Critical startup error. Please update your plugin!
  785. If the error persists after updating, contact Maximvdw through spigot PM
  786. Critical startup error. Please update your plugin!
  787. If the error persists after updating, contact Maximvdw through spigot PM
  788. Critical startup error. Please update your plugin!
  789. If the error persists after updating, contact Maximvdw through spigot PM
  790. Critical startup error. Please update your plugin!
  791. If the error persists after updating, contact Maximvdw through spigot PM
  792. Critical startup error. Please update your plugin!
  793. If the error persists after updating, contact Maximvdw through spigot PM
  794. Critical startup error. Please update your plugin!
  795. If the error persists after updating, contact Maximvdw through spigot PM
  796. Critical startup error. Please update your plugin!
  797. If the error persists after updating, contact Maximvdw through spigot PM
  798. Critical startup error. Please update your plugin!
  799. If the error persists after updating, contact Maximvdw through spigot PM
  800. Critical startup error. Please update your plugin!
  801. If the error persists after updating, contact Maximvdw through spigot PM
  802. Critical startup error. Please update your plugin!
  803. If the error persists after updating, contact Maximvdw through spigot PM
  804. Critical startup error. Please update your plugin!
  805. If the error persists after updating, contact Maximvdw through spigot PM
  806. Cr
  807. [00:45:24] [Server thread/INFO]: itical startup error. Please update your plugin!
  808. If the error persists after updating, contact Maximvdw through spigot PM
  809. Critical startup error. Please update your plugin!
  810. If the error persists after updating, contact Maximvdw through spigot PM
  811. Critical startup error. Please update your plugin!
  812. If the error persists after updating, contact Maximvdw through spigot PM
  813. Critical startup error. Please update your plugin!
  814. If the error persists after updating, contact Maximvdw through spigot PM
  815. Critical startup error. Please update your plugin!
  816. If the error persists after updating, contact Maximvdw through spigot PM
  817. Critical startup error. Please update your plugin!
  818. If the error persists after updating, contact Maximvdw through spigot PM
  819. Critical startup error. Please update your plugin!
  820. If the error persists after updating, contact Maximvdw through spigot PM
  821. Critical startup error. Please update your plugin!
  822. If the error persists after updating, contact Maximvdw through spigot PM
  823. Critical startup error. Please update your plugin!
  824. If the error persists after updating, contact Maximvdw through spigot PM
  825. Critical startup error. Please update your plugin!
  826. If the error persists after updating, contact Maximvdw through spigot PM
  827. Critical startup error. Please update your plugin!
  828. If the error persists after updating, contact Maximvdw through spigot PM
  829. Critical startup error. Please update your plugin!
  830. If the error persists after updating, contact Maximvdw through spigot PM
  831. Critical startup error. Please update your plugin!
  832. If the error persists after updating, contact Maximvdw through spigot PM
  833. Critical startup error. Please update your plugin!
  834. If the error persists after updating, contact Maximvdw through spigot PM
  835. Critical startup error. Please update your plugin!
  836. If the error persists after updating, contact Maximvdw through spigot PM
  837. Critical startup error. Please update your plugin!
  838. If the error persists after updating, contact Maximvdw through spigot PM
  839. Critical startup error. Please update your plugin!
  840. If the error persists after updating, contact Maximvdw through spigot PM
  841. Critical startup error. Please update your plugin!
  842. If the error persists after updating, contact Maximvdw through spigot PM
  843. Critical startup error. Please update your plugin!
  844. If the error persists after updating, contact Maximvdw through spigot PM
  845. Critical startup error. Please update your plugin!
  846. If the error persists after updating, contact Maximvdw through spigot PM
  847. Critical startup error. Please update your plugin!
  848. If the error persists after updating, contact Maximvdw through spigot PM
  849. Critical startup error. Please update your plugin!
  850. If the error persists after updating, contact Maximvdw through spigot PM
  851. Critical startup error. Please update your plugin!
  852. If the error persists after updating, contact Maximvdw through spigot PM
  853. Critical startup error. Please update your plugin!
  854. If the error persists after updating, contact Maximvdw through spigot PM
  855. Critical startup error. Please update your plugin!
  856. If the error persists after updating, contact Maximvdw through spigot PM
  857. Critical startup error. Please update your plugin!
  858. If the error persists after updating, contact Maximvdw through spigot PM
  859. Critical startup error. Please update your plugin!
  860. If the error persists after updating, contact Maximvdw through spigot PM
  861. Critical startup error. Please update your plugin!
  862. If the error persists after updating, contact Maximvdw through spigot PM
  863. Critical startup error. Please update your plugin!
  864. If the error persists after updating, contact Maximvdw through spigot PM
  865. Critical startup error. Please update your plugin!
  866. If the error persists after updating, contact Maximvdw through spigot PM
  867. Critical startup error. Please update your plugin!
  868. If the error persists after updating, contact Maximvdw through spigot PM
  869. Critical startup error. Please update your plugin!
  870. If the error persists after updating, contact Maximvdw through spigot PM
  871. Critical startup error. Please update your plugin!
  872. If the error persists after updating, contact Maximvdw through spigot PM
  873. Critical startup error. Please update your plugin!
  874. If the error persists after updating, contact Maximvdw through spigot PM
  875. Critical startup error. Please update your plugin!
  876. If the error persists after updating, contact Maximvdw through spigot PM
  877. Critical startup error. Please update your plugin!
  878. If the error persists after updating, contact Maximvdw through spigot PM
  879. Critical startup error. Please update your plugin!
  880. If the error persists after updating, contact Maximvdw through spigot PM
  881. Critical startup error. Please update your plugin!
  882. If the error persists after updating, contact Maximvdw through spigot PM
  883. Critical startup error. Please update your plugin!
  884. If the error persists after updating, contact Maximvdw through spigot PM
  885. Critical startup error. Please update your plugin!
  886. If the error persists after updating, contact Maximvdw through spigot PM
  887. Critical startup error. Please update your plugin!
  888. If the error persists after updating, contact Maximvdw through spigot PM
  889. Critical startup error. Please update your plugin!
  890. If the error persists after updating, contact Maximvdw through spigot PM
  891. Critical startup error. Please update your plugin!
  892. If the error persists after updating, contact Maximvdw through spigot PM
  893. Critical startup error. Please update your plugin!
  894. If the error persists after updating, contact Maximvdw through spigot PM
  895. Critical startup error. Please update your plugin!
  896. If the error persists after updating, contact Maximvdw through spigot PM
  897. Critical startup error. Please update your plugin!
  898. If the error persists after updating, contact Maximvdw through spigot PM
  899. Critical startup error. Please update your plugin!
  900. If the error persists after updating, contact Maximvdw through spigot PM
  901. Critical startup error. Please update your plugin!
  902. If the error persists after updating, contact Maximvdw through spigot PM
  903. Critical startup error. Please update your plugin!
  904. If the error persists after updating, contact Maximvdw through spigot PM
  905. Critical startup error. Please update your plugin!
  906. If the error persists after updating, contact Maximvdw through spigot PM
  907. Critical startup error. Please update your plugin!
  908. If the error persists after updating, contact Maximvdw through spigot PM
  909. Critical startup error. Please update your plugin!
  910. If the error persists after updating, contact Maximvdw through spigot PM
  911. Critical startup error. Please update your plugin!
  912. If the error persists after updating, contact Maximvdw through spigot PM
  913. Critical startup error. Please update your plugin!
  914. If the error persists after updating, contact Maximvdw through spigot PM
  915. Critical startup error. Please update your plugin!
  916. If the error persists after updating, contact Maximvdw through spigot PM
  917. Critical startup error. Please update your plugin!
  918. If the error persists after updating, contact Maximvdw through spigot PM
  919. Critical startup error. Please update your plugin!
  920. If the error persists after updating, contact Maximvdw through spigot PM
  921. Critical startup error. Please update your plugin!
  922. If the error persists after updating, contact Maximvdw through spigot PM
  923. Critical startup error. Please update your plugin!
  924. If the error persists after updating, contact Maximvdw through spigot PM
  925. Critical startup error. Please update your plugin!
  926. If the error persists after updating, contact Maximvdw through spigot PM
  927. Critical startup error. Please update your plugin!
  928. If the error persists after updating, contact Maximvdw through spigot PM
  929. Critical startup error. Please update your plugin!
  930. If the error persists after updating, contact Maximvdw through spigot PM
  931. Critical startup error. Please update your plugin!
  932. If the error persists after updating, contact Maximvdw through spigot PM
  933. Critical startup error. Please update your plugin!
  934. If the error persists after updating, contact Maximvdw through spigot PM
  935. Critical startup error. Please update your plugin!
  936. If the error persists after updating, contact Maximvdw through spigot PM
  937. Critical startup error. Please update your plugin!
  938. If the error persists after updating, contact Maximvdw through spigot PM
  939. Critical s
  940. [00:45:24] [Server thread/INFO]: tartup error. Please update your plugin!
  941. If the error persists after updating, contact Maximvdw through spigot PM
  942. Critical startup error. Please update your plugin!
  943. If the error persists after updating, contact Maximvdw through spigot PM
  944. Critical startup error. Please update your plugin!
  945. If the error persists after updating, contact Maximvdw through spigot PM
  946. Critical startup error. Please update your plugin!
  947. If the error persists after updating, contact Maximvdw through spigot PM
  948. Critical startup error. Please update your plugin!
  949. If the error persists after updating, contact Maximvdw through spigot PM
  950. Critical startup error. Please update your plugin!
  951. If the error persists after updating, contact Maximvdw through spigot PM
  952. Critical startup error. Please update your plugin!
  953. If the error persists after updating, contact Maximvdw through spigot PM
  954. Critical startup error. Please update your plugin!
  955. If the error persists after updating, contact Maximvdw through spigot PM
  956. Critical startup error. Please update your plugin!
  957. If the error persists after updating, contact Maximvdw through spigot PM
  958. Critical startup error. Please update your plugin!
  959. If the error persists after updating, contact Maximvdw through spigot PM
  960. Critical startup error. Please update your plugin!
  961. If the error persists after updating, contact Maximvdw through spigot PM
  962. Critical startup error. Please update your plugin!
  963. If the error persists after updating, contact Maximvdw through spigot PM
  964. Critical startup error. Please update your plugin!
  965. If the error persists after updating, contact Maximvdw through spigot PM
  966. Critical startup error. Please update your plugin!
  967. If the error persists after updating, contact Maximvdw through spigot PM
  968. Critical startup error. Please update your plugin!
  969. If the error persists after updating, contact Maximvdw through spigot PM
  970. Critical startup error. Please update your plugin!
  971. If the error persists after updating, contact Maximvdw through spigot PM
  972. Critical startup error. Please update your plugin!
  973. If the error persists after updating, contact Maximvdw through spigot PM
  974. Critical startup error. Please update your plugin!
  975. If the error persists after updating, contact Maximvdw through spigot PM
  976. Critical startup error. Please update your plugin!
  977. If the error persists after updating, contact Maximvdw through spigot PM
  978. Critical startup error. Please update your plugin!
  979. If the error persists after updating, contact Maximvdw through spigot PM
  980. Critical startup error. Please update your plugin!
  981. If the error persists after updating, contact Maximvdw through spigot PM
  982. Critical startup error. Please update your plugin!
  983. If the error persists after updating, contact Maximvdw through spigot PM
  984. Critical startup error. Please update your plugin!
  985. If the error persists after updating, contact Maximvdw through spigot PM
  986. Critical startup error. Please update your plugin!
  987. If the error persists after updating, contact Maximvdw through spigot PM
  988. Critical startup error. Please update your plugin!
  989. If the error persists after updating, contact Maximvdw through spigot PM
  990. Critical startup error. Please update your plugin!
  991. If the error persists after updating, contact Maximvdw through spigot PM
  992. Critical startup error. Please update your plugin!
  993. If the error persists after updating, contact Maximvdw through spigot PM
  994. Critical startup error. Please update your plugin!
  995. If the error persists after updating, contact Maximvdw through spigot PM
  996. Critical startup error. Please update your plugin!
  997. If the error persists after updating, contact Maximvdw through spigot PM
  998. Critical startup error. Please update your plugin!
  999. If the error persists after updating, contact Maximvdw through spigot PM
  1000. Critical startup error. Please update your plugin!
  1001. If the error persists after updating, contact Maximvdw through spigot PM
  1002. Critical startup error. Please update your plugin!
  1003. If the error persists after updating, contact Maximvdw through spigot PM
  1004. Critical startup error. Please update your plugin!
  1005. If the error persists after updating, contact Maximvdw through spigot PM
  1006. Critical startup error. Please update your plugin!
  1007. If the error persists after updating, contact Maximvdw through spigot PM
  1008. Critical startup error. Please update your plugin!
  1009. If the error persists after updating, contact Maximvdw through spigot PM
  1010. Critical startup error. Please update your plugin!
  1011. If the error persists after updating, contact Maximvdw through spigot PM
  1012. Critical startup error. Please update your plugin!
  1013. If the error persists after updating, contact Maximvdw through spigot PM
  1014. Critical startup error. Please update your plugin!
  1015. If the error persists after updating, contact Maximvdw through spigot PM
  1016. Critical startup error. Please update your plugin!
  1017. If the error persists after updating, contact Maximvdw through spigot PM
  1018. Critical startup error. Please update your plugin!
  1019. If the error persists after updating, contact Maximvdw through spigot PM
  1020. Critical startup error. Please update your plugin!
  1021. If the error persists after updating, contact Maximvdw through spigot PM
  1022. Critical startup error. Please update your plugin!
  1023. If the error persists after updating, contact Maximvdw through spigot PM
  1024. Critical startup error. Please update your plugin!
  1025. If the error persists after updating, contact Maximvdw through spigot PM
  1026. Critical startup error. Please update your plugin!
  1027. If the error persists after updating, contact Maximvdw through spigot PM
  1028. Critical startup error. Please update your plugin!
  1029. If the error persists after updating, contact Maximvdw through spigot PM
  1030. Critical startup error. Please update your plugin!
  1031. If the error persists after updating, contact Maximvdw through spigot PM
  1032. Critical startup error. Please update your plugin!
  1033. If the error persists after updating, contact Maximvdw through spigot PM
  1034. Critical startup error. Please update your plugin!
  1035. If the error persists after updating, contact Maximvdw through spigot PM
  1036. Critical startup error. Please update your plugin!
  1037. If the error persists after updating, contact Maximvdw through spigot PM
  1038. Critical startup error. Please update your plugin!
  1039. If the error persists after updating, contact Maximvdw through spigot PM
  1040. Critical startup error. Please update your plugin!
  1041. If the error persists after updating, contact Maximvdw through spigot PM
  1042. Critical startup error. Please update your plugin!
  1043. If the error persists after updating, contact Maximvdw through spigot PM
  1044. Critical startup error. Please update your plugin!
  1045. If the error persists after updating, contact Maximvdw through spigot PM
  1046. Critical startup error. Please update your plugin!
  1047. If the error persists after updating, contact Maximvdw through spigot PM
  1048. Critical startup error. Please update your plugin!
  1049. If the error persists after updating, contact Maximvdw through spigot PM
  1050. Critical startup error. Please update your plugin!
  1051. If the error persists after updating, contact Maximvdw through spigot PM
  1052. Critical startup error. Please update your plugin!
  1053. If the error persists after updating, contact Maximvdw through spigot PM
  1054. Critical startup error. Please update your plugin!
  1055. If the error persists after updating, contact Maximvdw through spigot PM
  1056. Critical startup error. Please update your plugin!
  1057. If the error persists after updating, contact Maximvdw through spigot PM
  1058. Critical startup error. Please update your plugin!
  1059. If the error persists after updating, contact Maximvdw through spigot PM
  1060. Critical startup error. Please update your plugin!
  1061. If the error persists after updating, contact Maximvdw through spigot PM
  1062. Critical startup error. Please update your plugin!
  1063. If the error persists after updating, contact Maximvdw through spigot PM
  1064. Critical startup error. Please update your plugin!
  1065. If the error persists after updating, contact Maximvdw through spigot PM
  1066. Critical startup error. Please update your plugin!
  1067. If the error persists after updating, contact Maximvdw through spigot PM
  1068. Critical startup error. Please update your plugin!
  1069. If the error persists after updating, contact Maximvdw through spigot PM
  1070. Critical startup error. Please update your plugin!
  1071. If the error persists after updating, contact Maximvdw through spigot PM
  1072. Critical startup e
  1073. [00:45:24] [Server thread/INFO]: rror. Please update your plugin!
  1074. If the error persists after updating, contact Maximvdw through spigot PM
  1075. Critical startup error. Please update your plugin!
  1076. If the error persists after updating, contact Maximvdw through spigot PM
  1077. Critical startup error. Please update your plugin!
  1078. If the error persists after updating, contact Maximvdw through spigot PM
  1079. Critical startup error. Please update your plugin!
  1080. If the error persists after updating, contact Maximvdw through spigot PM
  1081. Critical startup error. Please update your plugin!
  1082. If the error persists after updating, contact Maximvdw through spigot PM
  1083. Critical startup error. Please update your plugin!
  1084. If the error persists after updating, contact Maximvdw through spigot PM
  1085. Critical startup error. Please update your plugin!
  1086. If the error persists after updating, contact Maximvdw through spigot PM
  1087. Critical startup error. Please update your plugin!
  1088. If the error persists after updating, contact Maximvdw through spigot PM
  1089. Critical startup error. Please update your plugin!
  1090. If the error persists after updating, contact Maximvdw through spigot PM
  1091. Critical startup error. Please update your plugin!
  1092. If the error persists after updating, contact Maximvdw through spigot PM
  1093. Critical startup error. Please update your plugin!
  1094. If the error persists after updating, contact Maximvdw through spigot PM
  1095. Critical startup error. Please update your plugin!
  1096. If the error persists after updating, contact Maximvdw through spigot PM
  1097. Critical startup error. Please update your plugin!
  1098. If the error persists after updating, contact Maximvdw through spigot PM
  1099. Critical startup error. Please update your plugin!
  1100. If the error persists after updating, contact Maximvdw through spigot PM
  1101. Critical startup error. Please update your plugin!
  1102. If the error persists after updating, contact Maximvdw through spigot PM
  1103. Critical startup error. Please update your plugin!
  1104. If the error persists after updating, contact Maximvdw through spigot PM
  1105. Critical startup error. Please update your plugin!
  1106. If the error persists after updating, contact Maximvdw through spigot PM
  1107. Critical startup error. Please update your plugin!
  1108. If the error persists after updating, contact Maximvdw through spigot PM
  1109. Critical startup error. Please update your plugin!
  1110. If the error persists after updating, contact Maximvdw through spigot PM
  1111. Critical startup error. Please update your plugin!
  1112. If the error persists after updating, contact Maximvdw through spigot PM
  1113. Critical startup error. Please update your plugin!
  1114. If the error persists after updating, contact Maximvdw through spigot PM
  1115. Critical startup error. Please update your plugin!
  1116. If the error persists after updating, contact Maximvdw through spigot PM
  1117. Critical startup error. Please update your plugin!
  1118. If the error persists after updating, contact Maximvdw through spigot PM
  1119. Critical startup error. Please update your plugin!
  1120. If the error persists after updating, contact Maximvdw through spigot PM
  1121. Critical startup error. Please update your plugin!
  1122. If the error persists after updating, contact Maximvdw through spigot PM
  1123. Critical startup error. Please update your plugin!
  1124. If the error persists after updating, contact Maximvdw through spigot PM
  1125. Critical startup error. Please update your plugin!
  1126. If the error persists after updating, contact Maximvdw through spigot PM
  1127. Critical startup error. Please update your plugin!
  1128. If the error persists after updating, contact Maximvdw through spigot PM
  1129. Critical startup error. Please update your plugin!
  1130. If the error persists after updating, contact Maximvdw through spigot PM
  1131. Critical startup error. Please update your plugin!
  1132. If the error persists after updating, contact Maximvdw through spigot PM
  1133. Critical startup error. Please update your plugin!
  1134. If the error persists after updating, contact Maximvdw through spigot PM
  1135. Critical startup error. Please update your plugin!
  1136. If the error persists after updating, contact Maximvdw through spigot PM
  1137. Critical startup error. Please update your plugin!
  1138. If the error persists after updating, contact Maximvdw through spigot PM
  1139. Critical startup error. Please update your plugin!
  1140. If the error persists after updating, contact Maximvdw through spigot PM
  1141. Critical startup error. Please update your plugin!
  1142. If the error persists after updating, contact Maximvdw through spigot PM
  1143. Critical startup error. Please update your plugin!
  1144. If the error persists after updating, contact Maximvdw through spigot PM
  1145. Critical startup error. Please update your plugin!
  1146. If the error persists after updating, contact Maximvdw through spigot PM
  1147. Critical startup error. Please update your plugin!
  1148. If the error persists after updating, contact Maximvdw through spigot PM
  1149. Critical startup error. Please update your plugin!
  1150. If the error persists after updating, contact Maximvdw through spigot PM
  1151. Critical startup error. Please update your plugin!
  1152. If the error persists after updating, contact Maximvdw through spigot PM
  1153. Critical startup error. Please update your plugin!
  1154. If the error persists after updating, contact Maximvdw through spigot PM
  1155. Critical startup error. Please update your plugin!
  1156. If the error persists after updating, contact Maximvdw through spigot PM
  1157. Critical startup error. Please update your plugin!
  1158. If the error persists after updating, contact Maximvdw through spigot PM
  1159. Critical startup error. Please update your plugin!
  1160. If the error persists after updating, contact Maximvdw through spigot PM
  1161. Critical startup error. Please update your plugin!
  1162. If the error persists after updating, contact Maximvdw through spigot PM
  1163. Critical startup error. Please update your plugin!
  1164. If the error persists after updating, contact Maximvdw through spigot PM
  1165. Critical startup error. Please update your plugin!
  1166. If the error persists after updating, contact Maximvdw through spigot PM
  1167. Critical startup error. Please update your plugin!
  1168. If the error persists after updating, contact Maximvdw through spigot PM
  1169. Critical startup error. Please update your plugin!
  1170. If the error persists after updating, contact Maximvdw through spigot PM
  1171. Critical startup error. Please update your plugin!
  1172. If the error persists after updating, contact Maximvdw through spigot PM
  1173. Critical startup error. Please update your plugin!
  1174. If the error persists after updating, contact Maximvdw through spigot PM
  1175. Critical startup error. Please update your plugin!
  1176. If the error persists after updating, contact Maximvdw through spigot PM
  1177. Critical startup error. Please update your plugin!
  1178. If the error persists after updating, contact Maximvdw through spigot PM
  1179. Critical startup error. Please update your plugin!
  1180. If the error persists after updating, contact Maximvdw through spigot PM
  1181. Critical startup error. Please update your plugin!
  1182. If the error persists after updating, contact Maximvdw through spigot PM
  1183. Critical startup error. Please update your plugin!
  1184. If the error persists after updating, contact Maximvdw through spigot PM
  1185. Critical startup error. Please update your plugin!
  1186. If the error persists after updating, contact Maximvdw through spigot PM
  1187. Critical startup error. Please update your plugin!
  1188. If the error persists after updating, contact Maximvdw through spigot PM
  1189. Critical startup error. Please update your plugin!
  1190. If the error persists after updating, contact Maximvdw through spigot PM
  1191. Critical startup error. Please update your plugin!
  1192. If the error persists after updating, contact Maximvdw through spigot PM
  1193. Critical startup error. Please update your plugin!
  1194. If the error persists after updating, contact Maximvdw through spigot PM
  1195. Critical startup error. Please update your plugin!
  1196. If the error persists after updating, contact Maximvdw through spigot PM
  1197. Critical startup error. Please update your plugin!
  1198. If the error persists after updating, contact Maximvdw through spigot PM
  1199. Critical startup error. Please update your plugin!
  1200. If the error persists after updating, contact Maximvdw through spigot PM
  1201. Critical startup error. Please update your plugin!
  1202. If the error persists after updating, contact Maximvdw through spigot PM
  1203. Critical startup error. Please update your plugin!
  1204. If the error persists after updating, contact Maximvdw through spigot PM
  1205. Critical startup error. Pl
  1206. [00:45:24] [Server thread/INFO]: ease update your plugin!
  1207. If the error persists after updating, contact Maximvdw through spigot PM
  1208. Critical startup error. Please update your plugin!
  1209. If the error persists after updating, contact Maximvdw through spigot PM
  1210. Critical startup error. Please update your plugin!
  1211. If the error persists after updating, contact Maximvdw through spigot PM
  1212. Critical startup error. Please update your plugin!
  1213. If the error persists after updating, contact Maximvdw through spigot PM
  1214. Critical startup error. Please update your plugin!
  1215. If the error persists after updating, contact Maximvdw through spigot PM
  1216. Critical startup error. Please update your plugin!
  1217. If the error persists after updating, contact Maximvdw through spigot PM
  1218. Critical startup error. Please update your plugin!
  1219. If the error persists after updating, contact Maximvdw through spigot PM
  1220. Critical startup error. Please update your plugin!
  1221. If the error persists after updating, contact Maximvdw through spigot PM
  1222. Critical startup error. Please update your plugin!
  1223. If the error persists after updating, contact Maximvdw through spigot PM
  1224. Critical startup error. Please update your plugin!
  1225. If the error persists after updating, contact Maximvdw through spigot PM
  1226. Critical startup error. Please update your plugin!
  1227. If the error persists after updating, contact Maximvdw through spigot PM
  1228. Critical startup error. Please update your plugin!
  1229. If the error persists after updating, contact Maximvdw through spigot PM
  1230. Critical startup error. Please update your plugin!
  1231. If the error persists after updating, contact Maximvdw through spigot PM
  1232. Critical startup error. Please update your plugin!
  1233. If the error persists after updating, contact Maximvdw through spigot PM
  1234. Critical startup error. Please update your plugin!
  1235. If the error persists after updating, contact Maximvdw through spigot PM
  1236. Critical startup error. Please update your plugin!
  1237. If the error persists after updating, contact Maximvdw through spigot PM
  1238. Critical startup error. Please update your plugin!
  1239. If the error persists after updating, contact Maximvdw through spigot PM
  1240. Critical startup error. Please update your plugin!
  1241. If the error persists after updating, contact Maximvdw through spigot PM
  1242. Critical startup error. Please update your plugin!
  1243. If the error persists after updating, contact Maximvdw through spigot PM
  1244. Critical startup error. Please update your plugin!
  1245. If the error persists after updating, contact Maximvdw through spigot PM
  1246. Critical startup error. Please update your plugin!
  1247. If the error persists after updating, contact Maximvdw through spigot PM
  1248. Critical startup error. Please update your plugin!
  1249. If the error persists after updating, contact Maximvdw through spigot PM
  1250. Critical startup error. Please update your plugin!
  1251. If the error persists after updating, contact Maximvdw through spigot PM
  1252. Critical startup error. Please update your plugin!
  1253. If the error persists after updating, contact Maximvdw through spigot PM
  1254. Critical startup error. Please update your plugin!
  1255. If the error persists after updating, contact Maximvdw through spigot PM
  1256. Critical startup error. Please update your plugin!
  1257. If the error persists after updating, contact Maximvdw through spigot PM
  1258. Critical startup error. Please update your plugin!
  1259. If the error persists after updating, contact Maximvdw through spigot PM
  1260. Critical startup error. Please update your plugin!
  1261. If the error persists after updating, contact Maximvdw through spigot PM
  1262. Critical startup error. Please update your plugin!
  1263. If the error persists after updating, contact Maximvdw through spigot PM
  1264. Critical startup error. Please update your plugin!
  1265. If the error persists after updating, contact Maximvdw through spigot PM
  1266. Critical startup error. Please update your plugin!
  1267. If the error persists after updating, contact Maximvdw through spigot PM
  1268. Critical startup error. Please update your plugin!
  1269. If the error persists after updating, contact Maximvdw through spigot PM
  1270. Critical startup error. Please update your plugin!
  1271. If the error persists after updating, contact Maximvdw through spigot PM
  1272. Critical startup error. Please update your plugin!
  1273. If the error persists after updating, contact Maximvdw through spigot PM
  1274. Critical startup error. Please update your plugin!
  1275. If the error persists after updating, contact Maximvdw through spigot PM
  1276. Critical startup error. Please update your plugin!
  1277. If the error persists after updating, contact Maximvdw through spigot PM
  1278. Critical startup error. Please update your plugin!
  1279. If the error persists after updating, contact Maximvdw through spigot PM
  1280. Critical startup error. Please update your plugin!
  1281. If the error persists after updating, contact Maximvdw through spigot PM
  1282. Critical startup error. Please update your plugin!
  1283. If the error persists after updating, contact Maximvdw through spigot PM
  1284. Critical startup error. Please update your plugin!
  1285. If the error persists after updating, contact Maximvdw through spigot PM
  1286. Critical startup error. Please update your plugin!
  1287. If the error persists after updating, contact Maximvdw through spigot PM
  1288. Critical startup error. Please update your plugin!
  1289. If the error persists after updating, contact Maximvdw through spigot PM
  1290. Critical startup error. Please update your plugin!
  1291. If the error persists after updating, contact Maximvdw through spigot PM
  1292. Critical startup error. Please update your plugin!
  1293. If the error persists after updating, contact Maximvdw through spigot PM
  1294. Critical startup error. Please update your plugin!
  1295. If the error persists after updating, contact Maximvdw through spigot PM
  1296. Critical startup error. Please update your plugin!
  1297. If the error persists after updating, contact Maximvdw through spigot PM
  1298. Critical startup error. Please update your plugin!
  1299. If the error persists after updating, contact Maximvdw through spigot PM
  1300. Critical startup error. Please update your plugin!
  1301. If the error persists after updating, contact Maximvdw through spigot PM
  1302. Critical startup error. Please update your plugin!
  1303. If the error persists after updating, contact Maximvdw through spigot PM
  1304. Critical startup error. Please update your plugin!
  1305. If the error persists after updating, contact Maximvdw through spigot PM
  1306. Critical startup error. Please update your plugin!
  1307. If the error persists after updating, contact Maximvdw through spigot PM
  1308. Critical startup error. Please update your plugin!
  1309. If the error persists after updating, contact Maximvdw through spigot PM
  1310. Critical startup error. Please update your plugin!
  1311. If the error persists after updating, contact Maximvdw through spigot PM
  1312. Critical startup error. Please update your plugin!
  1313. If the error persists after updating, contact Maximvdw through spigot PM
  1314. Critical startup error. Please update your plugin!
  1315. If the error persists after updating, contact Maximvdw through spigot PM
  1316. Critical startup error. Please update your plugin!
  1317. If the error persists after updating, contact Maximvdw through spigot PM
  1318. Critical startup error. Please update your plugin!
  1319. If the error persists after updating, contact Maximvdw through spigot PM
  1320. Critical startup error. Please update your plugin!
  1321. If the error persists after updating, contact Maximvdw through spigot PM
  1322. Critical startup error. Please update your plugin!
  1323. If the error persists after updating, contact Maximvdw through spigot PM
  1324. Critical startup error. Please update your plugin!
  1325. If the error persists after updating, contact Maximvdw through spigot PM
  1326. Critical startup error. Please update your plugin!
  1327. If the error persists after updating, contact Maximvdw through spigot PM
  1328. Critical startup error. Please update your plugin!
  1329. If the error persists after updating, contact Maximvdw through spigot PM
  1330. Critical startup error. Please update your plugin!
  1331. If the error persists after updating, contact Maximvdw through spigot PM
  1332. Critical startup error. Please update your plugin!
  1333. If the error persists after updating, contact Maximvdw through spigot PM
  1334. Critical startup error. Please update your plugin!
  1335. If the error persists after updating, contact Maximvdw through spigot PM
  1336. Critical startup error. Please update your plugin!
  1337. If the error persists after updating, contact Maximvdw through spigot PM
  1338. Critical startup error. Please upd
  1339. [00:45:24] [Server thread/INFO]: ate your plugin!
  1340. If the error persists after updating, contact Maximvdw through spigot PM
  1341. Critical startup error. Please update your plugin!
  1342. If the error persists after updating, contact Maximvdw through spigot PM
  1343. Critical startup error. Please update your plugin!
  1344. If the error persists after updating, contact Maximvdw through spigot PM
  1345. Critical startup error. Please update your plugin!
  1346. If the error persists after updating, contact Maximvdw through spigot PM
  1347. Critical startup error. Please update your plugin!
  1348. If the error persists after updating, contact Maximvdw through spigot PM
  1349. Critical startup error. Please update your plugin!
  1350. If the error persists after updating, contact Maximvdw through spigot PM
  1351. Critical startup error. Please update your plugin!
  1352. If the error persists after updating, contact Maximvdw through spigot PM
  1353. Critical startup error. Please update your plugin!
  1354. If the error persists after updating, contact Maximvdw through spigot PM
  1355. Critical startup error. Please update your plugin!
  1356. If the error persists after updating, contact Maximvdw through spigot PM
  1357. Critical startup error. Please update your plugin!
  1358. If the error persists after updating, contact Maximvdw through spigot PM
  1359. Critical startup error. Please update your plugin!
  1360. If the error persists after updating, contact Maximvdw through spigot PM
  1361. Critical startup error. Please update your plugin!
  1362. If the error persists after updating, contact Maximvdw through spigot PM
  1363. Critical startup error. Please update your plugin!
  1364. If the error persists after updating, contact Maximvdw through spigot PM
  1365. Critical startup error. Please update your plugin!
  1366. If the error persists after updating, contact Maximvdw through spigot PM
  1367. Critical startup error. Please update your plugin!
  1368. If the error persists after updating, contact Maximvdw through spigot PM
  1369. Critical startup error. Please update your plugin!
  1370. If the error persists after updating, contact Maximvdw through spigot PM
  1371. Critical startup error. Please update your plugin!
  1372. If the error persists after updating, contact Maximvdw through spigot PM
  1373. Critical startup error. Please update your plugin!
  1374. If the error persists after updating, contact Maximvdw through spigot PM
  1375. Critical startup error. Please update your plugin!
  1376. If the error persists after updating, contact Maximvdw through spigot PM
  1377. Critical startup error. Please update your plugin!
  1378. If the error persists after updating, contact Maximvdw through spigot PM
  1379. Critical startup error. Please update your plugin!
  1380. If the error persists after updating, contact Maximvdw through spigot PM
  1381. Critical startup error. Please update your plugin!
  1382. If the error persists after updating, contact Maximvdw through spigot PM
  1383. Critical startup error. Please update your plugin!
  1384. If the error persists after updating, contact Maximvdw through spigot PM
  1385. Critical startup error. Please update your plugin!
  1386. If the error persists after updating, contact Maximvdw through spigot PM
  1387. Critical startup error. Please update your plugin!
  1388. If the error persists after updating, contact Maximvdw through spigot PM
  1389. Critical startup error. Please update your plugin!
  1390. If the error persists after updating, contact Maximvdw through spigot PM
  1391. Critical startup error. Please update your plugin!
  1392. If the error persists after updating, contact Maximvdw through spigot PM
  1393. Critical startup error. Please update your plugin!
  1394. If the error persists after updating, contact Maximvdw through spigot PM
  1395. Critical startup error. Please update your plugin!
  1396. If the error persists after updating, contact Maximvdw through spigot PM
  1397. Critical startup error. Please update your plugin!
  1398. If the error persists after updating, contact Maximvdw through spigot PM
  1399. Critical startup error. Please update your plugin!
  1400. If the error persists after updating, contact Maximvdw through spigot PM
  1401. Critical startup error. Please update your plugin!
  1402. If the error persists after updating, contact Maximvdw through spigot PM
  1403. Critical startup error. Please update your plugin!
  1404. If the error persists after updating, contact Maximvdw through spigot PM
  1405. Critical startup error. Please update your plugin!
  1406. If the error persists after updating, contact Maximvdw through spigot PM
  1407. Critical startup error. Please update your plugin!
  1408. If the error persists after updating, contact Maximvdw through spigot PM
  1409. Critical startup error. Please update your plugin!
  1410. If the error persists after updating, contact Maximvdw through spigot PM
  1411. Critical startup error. Please update your plugin!
  1412. If the error persists after updating, contact Maximvdw through spigot PM
  1413. Critical startup error. Please update your plugin!
  1414. If the error persists after updating, contact Maximvdw through spigot PM
  1415. Critical startup error. Please update your plugin!
  1416. If the error persists after updating, contact Maximvdw through spigot PM
  1417. Critical startup error. Please update your plugin!
  1418. If the error persists after updating, contact Maximvdw through spigot PM
  1419. Critical startup error. Please update your plugin!
  1420. If the error persists after updating, contact Maximvdw through spigot PM
  1421. Critical startup error. Please update your plugin!
  1422. If the error persists after updating, contact Maximvdw through spigot PM
  1423. Critical startup error. Please update your plugin!
  1424. If the error persists after updating, contact Maximvdw through spigot PM
  1425. Critical startup error. Please update your plugin!
  1426. If the error persists after updating, contact Maximvdw through spigot PM
  1427. Critical startup error. Please update your plugin!
  1428. If the error persists after updating, contact Maximvdw through spigot PM
  1429. Critical startup error. Please update your plugin!
  1430. If the error persists after updating, contact Maximvdw through spigot PM
  1431. Critical startup error. Please update your plugin!
  1432. If the error persists after updating, contact Maximvdw through spigot PM
  1433. Critical startup error. Please update your plugin!
  1434. If the error persists after updating, contact Maximvdw through spigot PM
  1435. Critical startup error. Please update your plugin!
  1436. If the error persists after updating, contact Maximvdw through spigot PM
  1437. Critical startup error. Please update your plugin!
  1438. If the error persists after updating, contact Maximvdw through spigot PM
  1439. Critical startup error. Please update your plugin!
  1440. If the error persists after updating, contact Maximvdw through spigot PM
  1441. Critical startup error. Please update your plugin!
  1442. If the error persists after updating, contact Maximvdw through spigot PM
  1443. Critical startup error. Please update your plugin!
  1444. If the error persists after updating, contact Maximvdw through spigot PM
  1445. Critical startup error. Please update your plugin!
  1446. If the error persists after updating, contact Maximvdw through spigot PM
  1447. Critical startup error. Please update your plugin!
  1448. If the error persists after updating, contact Maximvdw through spigot PM
  1449. Critical startup error. Please update your plugin!
  1450. If the error persists after updating, contact Maximvdw through spigot PM
  1451. Critical startup error. Please update your plugin!
  1452. If the error persists after updating, contact Maximvdw through spigot PM
  1453. Critical startup error. Please update your plugin!
  1454. If the error persists after updating, contact Maximvdw through spigot PM
  1455. Critical startup error. Please update your plugin!
  1456. If the error persists after updating, contact Maximvdw through spigot PM
  1457. Critical startup error. Please update your plugin!
  1458. If the error persists after updating, contact Maximvdw through spigot PM
  1459. Critical startup error. Please update your plugin!
  1460. If the error persists after updating, contact Maximvdw through spigot PM
  1461. Critical startup error. Please update your plugin!
  1462. If the error persists after updating, contact Maximvdw through spigot PM
  1463. Critical startup error. Please update your plugin!
  1464. If the error persists after updating, contact Maximvdw through spigot PM
  1465. Critical startup error. Please update your plugin!
  1466. If the error persists after updating, contact Maximvdw through spigot PM
  1467. Critical startup error. Please update your plugin!
  1468. If the error persists after updating, contact Maximvdw through spigot PM
  1469. Critical startup error. Please update your plugin!
  1470. If the error persists after updating, contact Maximvdw through spigot PM
  1471. Critical startup error. Please update your
  1472. [00:45:24] [Server thread/INFO]: plugin!
  1473. If the error persists after updating, contact Maximvdw through spigot PM
  1474. Critical startup error. Please update your plugin!
  1475. If the error persists after updating, contact Maximvdw through spigot PM
  1476. Critical startup error. Please update your plugin!
  1477. If the error persists after updating, contact Maximvdw through spigot PM
  1478. Critical startup error. Please update your plugin!
  1479. If the error persists after updating, contact Maximvdw through spigot PM
  1480. Critical startup error. Please update your plugin!
  1481. If the error persists after updating, contact Maximvdw through spigot PM
  1482. Critical startup error. Please update your plugin!
  1483. If the error persists after updating, contact Maximvdw through spigot PM
  1484. Critical startup error. Please update your plugin!
  1485. If the error persists after updating, contact Maximvdw through spigot PM
  1486. Critical startup error. Please update your plugin!
  1487. If the error persists after updating, contact Maximvdw through spigot PM
  1488. Critical startup error. Please update your plugin!
  1489. If the error persists after updating, contact Maximvdw through spigot PM
  1490. Critical startup error. Please update your plugin!
  1491. If the error persists after updating, contact Maximvdw through spigot PM
  1492. Critical startup error. Please update your plugin!
  1493. If the error persists after updating, contact Maximvdw through spigot PM
  1494. Critical startup error. Please update your plugin!
  1495. If the error persists after updating, contact Maximvdw through spigot PM
  1496. Critical startup error. Please update your plugin!
  1497. If the error persists after updating, contact Maximvdw through spigot PM
  1498. Critical startup error. Please update your plugin!
  1499. If the error persists after updating, contact Maximvdw through spigot PM
  1500. Critical startup error. Please update your plugin!
  1501. If the error persists after updating, contact Maximvdw through spigot PM
  1502. Critical startup error. Please update your plugin!
  1503. If the error persists after updating, contact Maximvdw through spigot PM
  1504. Critical startup error. Please update your plugin!
  1505. If the error persists after updating, contact Maximvdw through spigot PM
  1506. Critical startup error. Please update your plugin!
  1507. If the error persists after updating, contact Maximvdw through spigot PM
  1508. Critical startup error. Please update your plugin!
  1509. If the error persists after updating, contact Maximvdw through spigot PM
  1510. Critical startup error. Please update your plugin!
  1511. If the error persists after updating, contact Maximvdw through spigot PM
  1512. Critical startup error. Please update your plugin!
  1513. If the error persists after updating, contact Maximvdw through spigot PM
  1514. Critical startup error. Please update your plugin!
  1515. If the error persists after updating, contact Maximvdw through spigot PM
  1516. Critical startup error. Please update your plugin!
  1517. If the error persists after updating, contact Maximvdw through spigot PM
  1518. Critical startup error. Please update your plugin!
  1519. If the error persists after updating, contact Maximvdw through spigot PM
  1520. Critical startup error. Please update your plugin!
  1521. If the error persists after updating, contact Maximvdw through spigot PM
  1522. Critical startup error. Please update your plugin!
  1523. If the error persists after updating, contact Maximvdw through spigot PM
  1524. Critical startup error. Please update your plugin!
  1525. If the error persists after updating, contact Maximvdw through spigot PM
  1526. Critical startup error. Please update your plugin!
  1527. If the error persists after updating, contact Maximvdw through spigot PM
  1528. Critical startup error. Please update your plugin!
  1529. If the error persists after updating, contact Maximvdw through spigot PM
  1530. Critical startup error. Please update your plugin!
  1531. If the error persists after updating, contact Maximvdw through spigot PM
  1532. Critical startup error. Please update your plugin!
  1533. If the error persists after updating, contact Maximvdw through spigot PM
  1534. Critical startup error. Please update your plugin!
  1535. If the error persists after updating, contact Maximvdw through spigot PM
  1536. Critical startup error. Please update your plugin!
  1537. If the error persists after updating, contact Maximvdw through spigot PM
  1538. Critical startup error. Please update your plugin!
  1539. If the error persists after updating, contact Maximvdw through spigot PM
  1540. Critical startup error. Please update your plugin!
  1541. If the error persists after updating, contact Maximvdw through spigot PM
  1542. Critical startup error. Please update your plugin!
  1543. If the error persists after updating, contact Maximvdw through spigot PM
  1544. Critical startup error. Please update your plugin!
  1545. If the error persists after updating, contact Maximvdw through spigot PM
  1546. Critical startup error. Please update your plugin!
  1547. If the error persists after updating, contact Maximvdw through spigot PM
  1548. Critical startup error. Please update your plugin!
  1549. If the error persists after updating, contact Maximvdw through spigot PM
  1550. Critical startup error. Please update your plugin!
  1551. If the error persists after updating, contact Maximvdw through spigot PM
  1552. Critical startup error. Please update your plugin!
  1553. If the error persists after updating, contact Maximvdw through spigot PM
  1554. Critical startup error. Please update your plugin!
  1555. If the error persists after updating, contact Maximvdw through spigot PM
  1556. Critical startup error. Please update your plugin!
  1557. If the error persists after updating, contact Maximvdw through spigot PM
  1558. Critical startup error. Please update your plugin!
  1559. If the error persists after updating, contact Maximvdw through spigot PM
  1560. Critical startup error. Please update your plugin!
  1561. If the error persists after updating, contact Maximvdw through spigot PM
  1562. Critical startup error. Please update your plugin!
  1563. If the error persists after updating, contact Maximvdw through spigot PM
  1564. Critical startup error. Please update your plugin!
  1565. If the error persists after updating, contact Maximvdw through spigot PM
  1566. Critical startup error. Please update your plugin!
  1567. If the error persists after updating, contact Maximvdw through spigot PM
  1568. Critical startup error. Please update your plugin!
  1569. If the error persists after updating, contact Maximvdw through spigot PM
  1570. Critical startup error. Please update your plugin!
  1571. If the error persists after updating, contact Maximvdw through spigot PM
  1572. Critical startup error. Please update your plugin!
  1573. If the error persists after updating, contact Maximvdw through spigot PM
  1574. Critical startup error. Please update your plugin!
  1575. If the error persists after updating, contact Maximvdw through spigot PM
  1576. Critical startup error. Please update your plugin!
  1577. If the error persists after updating, contact Maximvdw through spigot PM
  1578. Critical startup error. Please update your plugin!
  1579. If the error persists after updating, contact Maximvdw through spigot PM
  1580. Critical startup error. Please update your plugin!
  1581. If the error persists after updating, contact Maximvdw through spigot PM
  1582. Critical startup error. Please update your plugin!
  1583. If the error persists after updating, contact Maximvdw through spigot PM
  1584. Critical startup error. Please update your plugin!
  1585. If the error persists after updating, contact Maximvdw through spigot PM
  1586. Critical startup error. Please update your plugin!
  1587. If the error persists after updating, contact Maximvdw through spigot PM
  1588. Critical startup error. Please update your plugin!
  1589. If the error persists after updating, contact Maximvdw through spigot PM
  1590. Critical startup error. Please update your plugin!
  1591. If the error persists after updating, contact Maximvdw through spigot PM
  1592. Critical startup error. Please update your plugin!
  1593. If the error persists after updating, contact Maximvdw through spigot PM
  1594. Critical startup error. Please update your plugin!
  1595. If the error persists after updating, contact Maximvdw through spigot PM
  1596. Critical startup error. Please update your plugin!
  1597. If the error persists after updating, contact Maximvdw through spigot PM
  1598. Critical startup error. Please update your plugin!
  1599. If the error persists after updating, contact Maximvdw through spigot PM
  1600. Critical startup error. Please update your plugin!
  1601. If the error persists after updating, contact Maximvdw through spigot PM
  1602. Critical startup error. Please update your plugin!
  1603. If the error persists after updating, contact Maximvdw through spigot PM
  1604. Critical startup error. Please update your plugin!
  1605. [00:45:24] [Server thread/INFO]:
  1606. If the error persists after updating, contact Maximvdw through spigot PM
  1607. Critical startup error. Please update your plugin!
  1608. If the error persists after updating, contact Maximvdw through spigot PM
  1609. Critical startup error. Please update your plugin!
  1610. If the error persists after updating, contact Maximvdw through spigot PM
  1611. Critical startup error. Please update your plugin!
  1612. If the error persists after updating, contact Maximvdw through spigot PM
  1613. Critical startup error. Please update your plugin!
  1614. If the error persists after updating, contact Maximvdw through spigot PM
  1615. Critical startup error. Please update your plugin!
  1616. If the error persists after updating, contact Maximvdw through spigot PM
  1617. Critical startup error. Please update your plugin!
  1618. If the error persists after updating, contact Maximvdw through spigot PM
  1619. Critical startup error. Please update your plugin!
  1620. If the error persists after updating, contact Maximvdw through spigot PM
  1621. Critical startup error. Please update your plugin!
  1622. If the error persists after updating, contact Maximvdw through spigot PM
  1623. Critical startup error. Please update your plugin!
  1624. If the error persists after updating, contact Maximvdw through spigot PM
  1625. Critical startup error. Please update your plugin!
  1626. If the error persists after updating, contact Maximvdw through spigot PM
  1627. Critical startup error. Please update your plugin!
  1628. If the error persists after updating, contact Maximvdw through spigot PM
  1629. Critical startup error. Please update your plugin!
  1630. If the error persists after updating, contact Maximvdw through spigot PM
  1631. Critical startup error. Please update your plugin!
  1632. If the error persists after updating, contact Maximvdw through spigot PM
  1633. Critical startup error. Please update your plugin!
  1634. If the error persists after updating, contact Maximvdw through spigot PM
  1635. Critical startup error. Please update your plugin!
  1636. If the error persists after updating, contact Maximvdw through spigot PM
  1637. Critical startup error. Please update your plugin!
  1638. If the error persists after updating, contact Maximvdw through spigot PM
  1639. Critical startup error. Please update your plugin!
  1640. If the error persists after updating, contact Maximvdw through spigot PM
  1641. Critical startup error. Please update your plugin!
  1642. If the error persists after updating, contact Maximvdw through spigot PM
  1643. Critical startup error. Please update your plugin!
  1644. If the error persists after updating, contact Maximvdw through spigot PM
  1645. Critical startup error. Please update your plugin!
  1646. If the error persists after updating, contact Maximvdw through spigot PM
  1647. Critical startup error. Please update your plugin!
  1648. If the error persists after updating, contact Maximvdw through spigot PM
  1649. Critical startup error. Please update your plugin!
  1650. If the error persists after updating, contact Maximvdw through spigot PM
  1651. Critical startup error. Please update your plugin!
  1652. If the error persists after updating, contact Maximvdw through spigot PM
  1653. Critical startup error. Please update your plugin!
  1654. If the error persists after updating, contact Maximvdw through spigot PM
  1655. Critical startup error. Please update your plugin!
  1656. If the error persists after updating, contact Maximvdw through spigot PM
  1657. Critical startup error. Please update your plugin!
  1658. If the error persists after updating, contact Maximvdw through spigot PM
  1659. Critical startup error. Please update your plugin!
  1660. If the error persists after updating, contact Maximvdw through spigot PM
  1661. Critical startup error. Please update your plugin!
  1662. If the error persists after updating, contact Maximvdw through spigot PM
  1663. Critical startup error. Please update your plugin!
  1664. If the error persists after updating, contact Maximvdw through spigot PM
  1665. Critical startup error. Please update your plugin!
  1666. If the error persists after updating, contact Maximvdw through spigot PM
  1667. Critical startup error. Please update your plugin!
  1668. If the error persists after updating, contact Maximvdw through spigot PM
  1669. Critical startup error. Please update your plugin!
  1670. If the error persists after updating, contact Maximvdw through spigot PM
  1671. Critical startup error. Please update your plugin!
  1672. If the error persists after updating, contact Maximvdw through spigot PM
  1673. Critical startup error. Please update your plugin!
  1674. If the error persists after updating, contact Maximvdw through spigot PM
  1675. Critical startup error. Please update your plugin!
  1676. If the error persists after updating, contact Maximvdw through spigot PM
  1677. Critical startup error. Please update your plugin!
  1678. If the error persists after updating, contact Maximvdw through spigot PM
  1679. Critical startup error. Please update your plugin!
  1680. If the error persists after updating, contact Maximvdw through spigot PM
  1681. Critical startup error. Please update your plugin!
  1682. If the error persists after updating, contact Maximvdw through spigot PM
  1683. Critical startup error. Please update your plugin!
  1684. If the error persists after updating, contact Maximvdw through spigot PM
  1685. Critical startup error. Please update your plugin!
  1686. If the error persists after updating, contact Maximvdw through spigot PM
  1687. Critical startup error. Please update your plugin!
  1688. If the error persists after updating, contact Maximvdw through spigot PM
  1689. Critical startup error. Please update your plugin!
  1690. If the error persists after updating, contact Maximvdw through spigot PM
  1691. Critical startup error. Please update your plugin!
  1692. If the error persists after updating, contact Maximvdw through spigot PM
  1693. Critical startup error. Please update your plugin!
  1694. If the error persists after updating, contact Maximvdw through spigot PM
  1695. Critical startup error. Please update your plugin!
  1696. If the error persists after updating, contact Maximvdw through spigot PM
  1697. Critical startup error. Please update your plugin!
  1698. If the error persists after updating, contact Maximvdw through spigot PM
  1699. Critical startup error. Please update your plugin!
  1700. If the error persists after updating, contact Maximvdw through spigot PM
  1701. Critical startup error. Please update your plugin!
  1702. If the error persists after updating, contact Maximvdw through spigot PM
  1703. Critical startup error. Please update your plugin!
  1704. If the error persists after updating, contact Maximvdw through spigot PM
  1705. Critical startup error. Please update your plugin!
  1706. If the error persists after updating, contact Maximvdw through spigot PM
  1707. Critical startup error. Please update your plugin!
  1708. If the error persists after updating, contact Maximvdw through spigot PM
  1709. Critical startup error. Please update your plugin!
  1710. If the error persists after updating, contact Maximvdw through spigot PM
  1711. Critical startup error. Please update your plugin!
  1712. If the error persists after updating, contact Maximvdw through spigot PM
  1713. Critical startup error. Please update your plugin!
  1714. If the error persists after updating, contact Maximvdw through spigot PM
  1715. Critical startup error. Please update your plugin!
  1716. If the error persists after updating, contact Maximvdw through spigot PM
  1717. Critical startup error. Please update your plugin!
  1718. If the error persists after updating, contact Maximvdw through spigot PM
  1719. Critical startup error. Please update your plugin!
  1720. If the error persists after updating, contact Maximvdw through spigot PM
  1721. Critical startup error. Please update your plugin!
  1722. If the error persists after updating, contact Maximvdw through spigot PM
  1723. Critical startup error. Please update your plugin!
  1724. If the error persists after updating, contact Maximvdw through spigot PM
  1725. Critical startup error. Please update your plugin!
  1726. If the error persists after updating, contact Maximvdw through spigot PM
  1727. Critical startup error. Please update your plugin!
  1728. If the error persists after updating, contact Maximvdw through spigot PM
  1729. Critical startup error. Please update your plugin!
  1730. If the error persists after updating, contact Maximvdw through spigot PM
  1731. Critical startup error. Please update your plugin!
  1732. If the error persists after updating, contact Maximvdw through spigot PM
  1733. Critical startup error. Please update your plugin!
  1734. If the error persists after updating, contact Maximvdw through spigot PM
  1735. Critical startup error. Please update your plugin!
  1736. If the error persists after updating, contact Maximvdw through spigot PM
  1737. Critical startup error. Please update your plugin!
  1738. If the
  1739. [00:45:24] [Server thread/INFO]: error persists after updating, contact Maximvdw through spigot PM
  1740. Critical startup error. Please update your plugin!
  1741. If the error persists after updating, contact Maximvdw through spigot PM
  1742. Critical startup error. Please update your plugin!
  1743. If the error persists after updating, contact Maximvdw through spigot PM
  1744. Critical startup error. Please update your plugin!
  1745. If the error persists after updating, contact Maximvdw through spigot PM
  1746. Critical startup error. Please update your plugin!
  1747. If the error persists after updating, contact Maximvdw through spigot PM
  1748. Critical startup error. Please update your plugin!
  1749. If the error persists after updating, contact Maximvdw through spigot PM
  1750. Critical startup error. Please update your plugin!
  1751. If the error persists after updating, contact Maximvdw through spigot PM
  1752. Critical startup error. Please update your plugin!
  1753. If the error persists after updating, contact Maximvdw through spigot PM
  1754. Critical startup error. Please update your plugin!
  1755. If the error persists after updating, contact Maximvdw through spigot PM
  1756. Critical startup error. Please update your plugin!
  1757. If the error persists after updating, contact Maximvdw through spigot PM
  1758. Critical startup error. Please update your plugin!
  1759. If the error persists after updating, contact Maximvdw through spigot PM
  1760. Critical startup error. Please update your plugin!
  1761. If the error persists after updating, contact Maximvdw through spigot PM
  1762. Critical startup error. Please update your plugin!
  1763. If the error persists after updating, contact Maximvdw through spigot PM
  1764. Critical startup error. Please update your plugin!
  1765. If the error persists after updating, contact Maximvdw through spigot PM
  1766. Critical startup error. Please update your plugin!
  1767. If the error persists after updating, contact Maximvdw through spigot PM
  1768. Critical startup error. Please update your plugin!
  1769. If the error persists after updating, contact Maximvdw through spigot PM
  1770. Critical startup error. Please update your plugin!
  1771. If the error persists after updating, contact Maximvdw through spigot PM
  1772. Critical startup error. Please update your plugin!
  1773. If the error persists after updating, contact Maximvdw through spigot PM
  1774. Critical startup error. Please update your plugin!
  1775. If the error persists after updating, contact Maximvdw through spigot PM
  1776. Critical startup error. Please update your plugin!
  1777. If the error persists after updating, contact Maximvdw through spigot PM
  1778. Critical startup error. Please update your plugin!
  1779. If the error persists after updating, contact Maximvdw through spigot PM
  1780. Critical startup error. Please update your plugin!
  1781. If the error persists after updating, contact Maximvdw through spigot PM
  1782. Critical startup error. Please update your plugin!
  1783. If the error persists after updating, contact Maximvdw through spigot PM
  1784. Critical startup error. Please update your plugin!
  1785. If the error persists after updating, contact Maximvdw through spigot PM
  1786. Critical startup error. Please update your plugin!
  1787. If the error persists after updating, contact Maximvdw through spigot PM
  1788. Critical startup error. Please update your plugin!
  1789. If the error persists after updating, contact Maximvdw through spigot PM
  1790. Critical startup error. Please update your plugin!
  1791. If the error persists after updating, contact Maximvdw through spigot PM
  1792. Critical startup error. Please update your plugin!
  1793. If the error persists after updating, contact Maximvdw through spigot PM
  1794. Critical startup error. Please update your plugin!
  1795. If the error persists after updating, contact Maximvdw through spigot PM
  1796. Critical startup error. Please update your plugin!
  1797. If the error persists after updating, contact Maximvdw through spigot PM
  1798. Critical startup error. Please update your plugin!
  1799. If the error persists after updating, contact Maximvdw through spigot PM
  1800. Critical startup error. Please update your plugin!
  1801. If the error persists after updating, contact Maximvdw through spigot PM
  1802. Critical startup error. Please update your plugin!
  1803. If the error persists after updating, contact Maximvdw through spigot PM
  1804. Critical startup error. Please update your plugin!
  1805. If the error persists after updating, contact Maximvdw through spigot PM
  1806. Critical startup error. Please update your plugin!
  1807. If the error persists after updating, contact Maximvdw through spigot PM
  1808. Critical startup error. Please update your plugin!
  1809. If the error persists after updating, contact Maximvdw through spigot PM
  1810. Critical startup error. Please update your plugin!
  1811. If the error persists after updating, contact Maximvdw through spigot PM
  1812. Critical startup error. Please update your plugin!
  1813. If the error persists after updating, contact Maximvdw through spigot PM
  1814. Critical startup error. Please update your plugin!
  1815. If the error persists after updating, contact Maximvdw through spigot PM
  1816. Critical startup error. Please update your plugin!
  1817. If the error persists after updating, contact Maximvdw through spigot PM
  1818. Critical startup error. Please update your plugin!
  1819. If the error persists after updating, contact Maximvdw through spigot PM
  1820. Critical startup error. Please update your plugin!
  1821. If the error persists after updating, contact Maximvdw through spigot PM
  1822. Critical startup error. Please update your plugin!
  1823. If the error persists after updating, contact Maximvdw through spigot PM
  1824. Critical startup error. Please update your plugin!
  1825. If the error persists after updating, contact Maximvdw through spigot PM
  1826. Critical startup error. Please update your plugin!
  1827. If the error persists after updating, contact Maximvdw through spigot PM
  1828. Critical startup error. Please update your plugin!
  1829. If the error persists after updating, contact Maximvdw through spigot PM
  1830. Critical startup error. Please update your plugin!
  1831. If the error persists after updating, contact Maximvdw through spigot PM
  1832. Critical startup error. Please update your plugin!
  1833. If the error persists after updating, contact Maximvdw through spigot PM
  1834. Critical startup error. Please update your plugin!
  1835. If the error persists after updating, contact Maximvdw through spigot PM
  1836. Critical startup error. Please update your plugin!
  1837. If the error persists after updating, contact Maximvdw through spigot PM
  1838. Critical startup error. Please update your plugin!
  1839. If the error persists after updating, contact Maximvdw through spigot PM
  1840. Critical startup error. Please update your plugin!
  1841. If the error persists after updating, contact Maximvdw through spigot PM
  1842. Critical startup error. Please update your plugin!
  1843. If the error persists after updating, contact Maximvdw through spigot PM
  1844. Critical startup error. Please update your plugin!
  1845. If the error persists after updating, contact Maximvdw through spigot PM
  1846. Critical startup error. Please update your plugin!
  1847. If the error persists after updating, contact Maximvdw through spigot PM
  1848. Critical startup error. Please update your plugin!
  1849. If the error persists after updating, contact Maximvdw through spigot PM
  1850. Critical startup error. Please update your plugin!
  1851. If the error persists after updating, contact Maximvdw through spigot PM
  1852. Critical startup error. Please update your plugin!
  1853. If the error persists after updating, contact Maximvdw through spigot PM
  1854. Critical startup error. Please update your plugin!
  1855. If the error persists after updating, contact Maximvdw through spigot PM
  1856. Critical startup error. Please update your plugin!
  1857. If the error persists after updating, contact Maximvdw through spigot PM
  1858. Critical startup error. Please update your plugin!
  1859. If the error persists after updating, contact Maximvdw through spigot PM
  1860. Critical startup error. Please update your plugin!
  1861. If the error persists after updating, contact Maximvdw through spigot PM
  1862. Critical startup error. Please update your plugin!
  1863. If the error persists after updating, contact Maximvdw through spigot PM
  1864. Critical startup error. Please update your plugin!
  1865. If the error persists after updating, contact Maximvdw through spigot PM
  1866. Critical startup error. Please update your plugin!
  1867. If the error persists after updating, contact Maximvdw through spigot PM
  1868. Critical startup error. Please update your plugin!
  1869. If the error persists after updating, contact Maximvdw through spigot PM
  1870. Critical startup error. Please update your plugin!
  1871. If the error pe
  1872. [00:45:24] [Server thread/INFO]: rsists after updating, contact Maximvdw through spigot PM
  1873. Critical startup error. Please update your plugin!
  1874. If the error persists after updating, contact Maximvdw through spigot PM
  1875. Critical startup error. Please update your plugin!
  1876. If the error persists after updating, contact Maximvdw through spigot PM
  1877. Critical startup error. Please update your plugin!
  1878. If the error persists after updating, contact Maximvdw through spigot PM
  1879. Critical startup error. Please update your plugin!
  1880. If the error persists after updating, contact Maximvdw through spigot PM
  1881. Critical startup error. Please update your plugin!
  1882. If the error persists after updating, contact Maximvdw through spigot PM
  1883. Critical startup error. Please update your plugin!
  1884. If the error persists after updating, contact Maximvdw through spigot PM
  1885. Critical startup error. Please update your plugin!
  1886. If the error persists after updating, contact Maximvdw through spigot PM
  1887. Critical startup error. Please update your plugin!
  1888. If the error persists after updating, contact Maximvdw through spigot PM
  1889. Critical startup error. Please update your plugin!
  1890. If the error persists after updating, contact Maximvdw through spigot PM
  1891. Critical startup error. Please update your plugin!
  1892. If the error persists after updating, contact Maximvdw through spigot PM
  1893. Critical startup error. Please update your plugin!
  1894. If the error persists after updating, contact Maximvdw through spigot PM
  1895. Critical startup error. Please update your plugin!
  1896. If the error persists after updating, contact Maximvdw through spigot PM
  1897. Critical startup error. Please update your plugin!
  1898. If the error persists after updating, contact Maximvdw through spigot PM
  1899. Critical startup error. Please update your plugin!
  1900. If the error persists after updating, contact Maximvdw through spigot PM
  1901. Critical startup error. Please update your plugin!
  1902. If the error persists after updating, contact Maximvdw through spigot PM
  1903. Critical startup error. Please update your plugin!
  1904. If the error persists after updating, contact Maximvdw through spigot PM
  1905. Critical startup error. Please update your plugin!
  1906. If the error persists after updating, contact Maximvdw through spigot PM
  1907. Critical startup error. Please update your plugin!
  1908. If the error persists after updating, contact Maximvdw through spigot PM
  1909. Critical startup error. Please update your plugin!
  1910. If the error persists after updating, contact Maximvdw through spigot PM
  1911. Critical startup error. Please update your plugin!
  1912. If the error persists after updating, contact Maximvdw through spigot PM
  1913. Critical startup error. Please update your plugin!
  1914. If the error persists after updating, contact Maximvdw through spigot PM
  1915. Critical startup error. Please update your plugin!
  1916. If the error persists after updating, contact Maximvdw through spigot PM
  1917. Critical startup error. Please update your plugin!
  1918. If the error persists after updating, contact Maximvdw through spigot PM
  1919. Critical startup error. Please update your plugin!
  1920. If the error persists after updating, contact Maximvdw through spigot PM
  1921. Critical startup error. Please update your plugin!
  1922. If the error persists after updating, contact Maximvdw through spigot PM
  1923. Critical startup error. Please update your plugin!
  1924. If the error persists after updating, contact Maximvdw through spigot PM
  1925. Critical startup error. Please update your plugin!
  1926. If the error persists after updating, contact Maximvdw through spigot PM
  1927. Critical startup error. Please update your plugin!
  1928. If the error persists after updating, contact Maximvdw through spigot PM
  1929. Critical startup error. Please update your plugin!
  1930. If the error persists after updating, contact Maximvdw through spigot PM
  1931. Critical startup error. Please update your plugin!
  1932. If the error persists after updating, contact Maximvdw through spigot PM
  1933. Critical startup error. Please update your plugin!
  1934. If the error persists after updating, contact Maximvdw through spigot PM
  1935. Critical startup error. Please update your plugin!
  1936. If the error persists after updating, contact Maximvdw through spigot PM
  1937. Critical startup error. Please update your plugin!
  1938. If the error persists after updating, contact Maximvdw through spigot PM
  1939. Critical startup error. Please update your plugin!
  1940. If the error persists after updating, contact Maximvdw through spigot PM
  1941. Critical startup error. Please update your plugin!
  1942. If the error persists after updating, contact Maximvdw through spigot PM
  1943. Critical startup error. Please update your plugin!
  1944. If the error persists after updating, contact Maximvdw through spigot PM
  1945. Critical startup error. Please update your plugin!
  1946. If the error persists after updating, contact Maximvdw through spigot PM
  1947. Critical startup error. Please update your plugin!
  1948. If the error persists after updating, contact Maximvdw through spigot PM
  1949. Critical startup error. Please update your plugin!
  1950. If the error persists after updating, contact Maximvdw through spigot PM
  1951. Critical startup error. Please update your plugin!
  1952. If the error persists after updating, contact Maximvdw through spigot PM
  1953. Critical startup error. Please update your plugin!
  1954. If the error persists after updating, contact Maximvdw through spigot PM
  1955. Critical startup error. Please update your plugin!
  1956. If the error persists after updating, contact Maximvdw through spigot PM
  1957. Critical startup error. Please update your plugin!
  1958. If the error persists after updating, contact Maximvdw through spigot PM
  1959. Critical startup error. Please update your plugin!
  1960. If the error persists after updating, contact Maximvdw through spigot PM
  1961. Critical startup error. Please update your plugin!
  1962. If the error persists after updating, contact Maximvdw through spigot PM
  1963. Critical startup error. Please update your plugin!
  1964. If the error persists after updating, contact Maximvdw through spigot PM
  1965. Critical startup error. Please update your plugin!
  1966. If the error persists after updating, contact Maximvdw through spigot PM
  1967. Critical startup error. Please update your plugin!
  1968. If the error persists after updating, contact Maximvdw through spigot PM
  1969. Critical startup error. Please update your plugin!
  1970. If the error persists after updating, contact Maximvdw through spigot PM
  1971. Critical startup error. Please update your plugin!
  1972. If the error persists after updating, contact Maximvdw through spigot PM
  1973. Critical startup error. Please update your plugin!
  1974. If the error persists after updating, contact Maximvdw through spigot PM
  1975. Critical startup error. Please update your plugin!
  1976. If the error persists after updating, contact Maximvdw through spigot PM
  1977. Critical startup error. Please update your plugin!
  1978. If the error persists after updating, contact Maximvdw through spigot PM
  1979. Critical startup error. Please update your plugin!
  1980. If the error persists after updating, contact Maximvdw through spigot PM
  1981. Critical startup error. Please update your plugin!
  1982. If the error persists after updating, contact Maximvdw through spigot PM
  1983. Critical startup error. Please update your plugin!
  1984. If the error persists after updating, contact Maximvdw through spigot PM
  1985. Critical startup error. Please update your plugin!
  1986. If the error persists after updating, contact Maximvdw through spigot PM
  1987. Critical startup error. Please update your plugin!
  1988. If the error persists after updating, contact Maximvdw through spigot PM
  1989. Critical startup error. Please update your plugin!
  1990. If the error persists after updating, contact Maximvdw through spigot PM
  1991. Critical startup error. Please update your plugin!
  1992. If the error persists after updating, contact Maximvdw through spigot PM
  1993. Critical startup error. Please update your plugin!
  1994. If the error persists after updating, contact Maximvdw through spigot PM
  1995. Critical startup error. Please update your plugin!
  1996. If the error persists after updating, contact Maximvdw through spigot PM
  1997. Critical startup error. Please update your plugin!
  1998. If the error persists after updating, contact Maximvdw through spigot PM
  1999. Critical startup error. Please update your plugin!
  2000. If the error persists after updating, contact Maximvdw through spigot PM
  2001. Critical startup error. Please update your plugin!
  2002. If the error persists after updating, contact Maximvdw through spigot PM
  2003. Critical startup error. Please update your plugin!
  2004. If the error persists a
  2005. [00:45:24] [Server thread/INFO]: fter updating, contact Maximvdw through spigot PM
  2006. Critical startup error. Please update your plugin!
  2007. If the error persists after updating, contact Maximvdw through spigot PM
  2008. Critical startup error. Please update your plugin!
  2009. If the error persists after updating, contact Maximvdw through spigot PM
  2010. Critical startup error. Please update your plugin!
  2011. If the error persists after updating, contact Maximvdw through spigot PM
  2012. Critical startup error. Please update your plugin!
  2013. If the error persists after updating, contact Maximvdw through spigot PM
  2014. Critical startup error. Please update your plugin!
  2015. If the error persists after updating, contact Maximvdw through spigot PM
  2016. Critical startup error. Please update your plugin!
  2017. If the error persists after updating, contact Maximvdw through spigot PM
  2018. Critical startup error. Please update your plugin!
  2019. If the error persists after updating, contact Maximvdw through spigot PM
  2020. Critical startup error. Please update your plugin!
  2021. If the error persists after updating, contact Maximvdw through spigot PM
  2022. Critical startup error. Please update your plugin!
  2023. If the error persists after updating, contact Maximvdw through spigot PM
  2024. Critical startup error. Please update your plugin!
  2025. If the error persists after updating, contact Maximvdw through spigot PM
  2026. Critical startup error. Please update your plugin!
  2027. If the error persists after updating, contact Maximvdw through spigot PM
  2028. Critical startup error. Please update your plugin!
  2029. If the error persists after updating, contact Maximvdw through spigot PM
  2030. Critical startup error. Please update your plugin!
  2031. If the error persists after updating, contact Maximvdw through spigot PM
  2032. Critical startup error. Please update your plugin!
  2033. If the error persists after updating, contact Maximvdw through spigot PM
  2034. Critical startup error. Please update your plugin!
  2035. If the error persists after updating, contact Maximvdw through spigot PM
  2036. Critical startup error. Please update your plugin!
  2037. If the error persists after updating, contact Maximvdw through spigot PM
  2038. Critical startup error. Please update your plugin!
  2039. If the error persists after updating, contact Maximvdw through spigot PM
  2040. Critical startup error. Please update your plugin!
  2041. If the error persists after updating, contact Maximvdw through spigot PM
  2042. Critical startup error. Please update your plugin!
  2043. If the error persists after updating, contact Maximvdw through spigot PM
  2044. Critical startup error. Please update your plugin!
  2045. If the error persists after updating, contact Maximvdw through spigot PM
  2046. Critical startup error. Please update your plugin!
  2047. If the error persists after updating, contact Maximvdw through spigot PM
  2048. Critical startup error. Please update your plugin!
  2049. If the error persists after updating, contact Maximvdw through spigot PM
  2050. Critical startup error. Please update your plugin!
  2051. If the error persists after updating, contact Maximvdw through spigot PM
  2052. Critical startup error. Please update your plugin!
  2053. If the error persists after updating, contact Maximvdw through spigot PM
  2054. Critical startup error. Please update your plugin!
  2055. If the error persists after updating, contact Maximvdw through spigot PM
  2056. Critical startup error. Please update your plugin!
  2057. If the error persists after updating, contact Maximvdw through spigot PM
  2058. Critical startup error. Please update your plugin!
  2059. If the error persists after updating, contact Maximvdw through spigot PM
  2060. Critical startup error. Please update your plugin!
  2061. If the error persists after updating, contact Maximvdw through spigot PM
  2062. Critical startup error. Please update your plugin!
  2063. If the error persists after updating, contact Maximvdw through spigot PM
  2064. Critical startup error. Please update your plugin!
  2065. If the error persists after updating, contact Maximvdw through spigot PM
  2066. Critical startup error. Please update your plugin!
  2067. If the error persists after updating, contact Maximvdw through spigot PM
  2068. Critical startup error. Please update your plugin!
  2069. If the error persists after updating, contact Maximvdw through spigot PM
  2070. Critical startup error. Please update your plugin!
  2071. If the error persists after updating, contact Maximvdw through spigot PM
  2072. Critical startup error. Please update your plugin!
  2073. If the error persists after updating, contact Maximvdw through spigot PM
  2074. Critical startup error. Please update your plugin!
  2075. If the error persists after updating, contact Maximvdw through spigot PM
  2076. Critical startup error. Please update your plugin!
  2077. If the error persists after updating, contact Maximvdw through spigot PM
  2078. Critical startup error. Please update your plugin!
  2079. If the error persists after updating, contact Maximvdw through spigot PM
  2080. Critical startup error. Please update your plugin!
  2081. If the error persists after updating, contact Maximvdw through spigot PM
  2082. Critical startup error. Please update your plugin!
  2083. If the error persists after updating, contact Maximvdw through spigot PM
  2084. Critical startup error. Please update your plugin!
  2085. If the error persists after updating, contact Maximvdw through spigot PM
  2086. Critical startup error. Please update your plugin!
  2087. If the error persists after updating, contact Maximvdw through spigot PM
  2088. Critical startup error. Please update your plugin!
  2089. If the error persists after updating, contact Maximvdw through spigot PM
  2090. Critical startup error. Please update your plugin!
  2091. If the error persists after updating, contact Maximvdw through spigot PM
  2092. Critical startup error. Please update your plugin!
  2093. If the error persists after updating, contact Maximvdw through spigot PM
  2094. Critical startup error. Please update your plugin!
  2095. If the error persists after updating, contact Maximvdw through spigot PM
  2096. Critical startup error. Please update your plugin!
  2097. If the error persists after updating, contact Maximvdw through spigot PM
  2098. Critical startup error. Please update your plugin!
  2099. If the error persists after updating, contact Maximvdw through spigot PM
  2100. Critical startup error. Please update your plugin!
  2101. If the error persists after updating, contact Maximvdw through spigot PM
  2102. Critical startup error. Please update your plugin!
  2103. If the error persists after updating, contact Maximvdw through spigot PM
  2104. Critical startup error. Please update your plugin!
  2105. If the error persists after updating, contact Maximvdw through spigot PM
  2106. Critical startup error. Please update your plugin!
  2107. If the error persists after updating, contact Maximvdw through spigot PM
  2108. Critical startup error. Please update your plugin!
  2109. If the error persists after updating, contact Maximvdw through spigot PM
  2110. Critical startup error. Please update your plugin!
  2111. If the error persists after updating, contact Maximvdw through spigot PM
  2112. Critical startup error. Please update your plugin!
  2113. If the error persists after updating, contact Maximvdw through spigot PM
  2114. Critical startup error. Please update your plugin!
  2115. If the error persists after updating, contact Maximvdw through spigot PM
  2116. Critical startup error. Please update your plugin!
  2117. If the error persists after updating, contact Maximvdw through spigot PM
  2118. Critical startup error. Please update your plugin!
  2119. If the error persists after updating, contact Maximvdw through spigot PM
  2120. Critical startup error. Please update your plugin!
  2121. If the error persists after updating, contact Maximvdw through spigot PM
  2122. Critical startup error. Please update your plugin!
  2123. If the error persists after updating, contact Maximvdw through spigot PM
  2124. Critical startup error. Please update your plugin!
  2125. If the error persists after updating, contact Maximvdw through spigot PM
  2126. Critical startup error. Please update your plugin!
  2127. If the error persists after updating, contact Maximvdw through spigot PM
  2128. Critical startup error. Please update your plugin!
  2129. If the error persists after updating, contact Maximvdw through spigot PM
  2130. Critical startup error. Please update your plugin!
  2131. If the error persists after updating, contact Maximvdw through spigot PM
  2132. Critical startup error. Please update your plugin!
  2133. If the error persists after updating, contact Maximvdw through spigot PM
  2134. Critical startup error. Please update your plugin!
  2135. If the error persists after updating, contact Maximvdw through spigot PM
  2136. Critical startup error. Please update your plugin!
  2137. If the error persists after upd
  2138. [00:45:24] [Server thread/INFO]: ating, contact Maximvdw through spigot PM
  2139. Critical startup error. Please update your plugin!
  2140. If the error persists after updating, contact Maximvdw through spigot PM
  2141. Critical startup error. Please update your plugin!
  2142. If the error persists after updating, contact Maximvdw through spigot PM
  2143. Critical startup error. Please update your plugin!
  2144. If the error persists after updating, contact Maximvdw through spigot PM
  2145. Critical startup error. Please update your plugin!
  2146. If the error persists after updating, contact Maximvdw through spigot PM
  2147. Critical startup error. Please update your plugin!
  2148. If the error persists after updating, contact Maximvdw through spigot PM
  2149. Critical startup error. Please update your plugin!
  2150. If the error persists after updating, contact Maximvdw through spigot PM
  2151. Critical startup error. Please update your plugin!
  2152. If the error persists after updating, contact Maximvdw through spigot PM
  2153. Critical startup error. Please update your plugin!
  2154. If the error persists after updating, contact Maximvdw through spigot PM
  2155. Critical startup error. Please update your plugin!
  2156. If the error persists after updating, contact Maximvdw through spigot PM
  2157. Critical startup error. Please update your plugin!
  2158. If the error persists after updating, contact Maximvdw through spigot PM
  2159. Critical startup error. Please update your plugin!
  2160. If the error persists after updating, contact Maximvdw through spigot PM
  2161. Critical startup error. Please update your plugin!
  2162. If the error persists after updating, contact Maximvdw through spigot PM
  2163. Critical startup error. Please update your plugin!
  2164. If the error persists after updating, contact Maximvdw through spigot PM
  2165. Critical startup error. Please update your plugin!
  2166. If the error persists after updating, contact Maximvdw through spigot PM
  2167. Critical startup error. Please update your plugin!
  2168. If the error persists after updating, contact Maximvdw through spigot PM
  2169. Critical startup error. Please update your plugin!
  2170. If the error persists after updating, contact Maximvdw through spigot PM
  2171. Critical startup error. Please update your plugin!
  2172. If the error persists after updating, contact Maximvdw through spigot PM
  2173. Critical startup error. Please update your plugin!
  2174. If the error persists after updating, contact Maximvdw through spigot PM
  2175. Critical startup error. Please update your plugin!
  2176. If the error persists after updating, contact Maximvdw through spigot PM
  2177. Critical startup error. Please update your plugin!
  2178. If the error persists after updating, contact Maximvdw through spigot PM
  2179. Critical startup error. Please update your plugin!
  2180. If the error persists after updating, contact Maximvdw through spigot PM
  2181. Critical startup error. Please update your plugin!
  2182. If the error persists after updating, contact Maximvdw through spigot PM
  2183. Critical startup error. Please update your plugin!
  2184. If the error persists after updating, contact Maximvdw through spigot PM
  2185. Critical startup error. Please update your plugin!
  2186. If the error persists after updating, contact Maximvdw through spigot PM
  2187. Critical startup error. Please update your plugin!
  2188. If the error persists after updating, contact Maximvdw through spigot PM
  2189. Critical startup error. Please update your plugin!
  2190. If the error persists after updating, contact Maximvdw through spigot PM
  2191. Critical startup error. Please update your plugin!
  2192. If the error persists after updating, contact Maximvdw through spigot PM
  2193. Critical startup error. Please update your plugin!
  2194. If the error persists after updating, contact Maximvdw through spigot PM
  2195. Critical startup error. Please update your plugin!
  2196. If the error persists after updating, contact Maximvdw through spigot PM
  2197. Critical startup error. Please update your plugin!
  2198. If the error persists after updating, contact Maximvdw through spigot PM
  2199. Critical startup error. Please update your plugin!
  2200. If the error persists after updating, contact Maximvdw through spigot PM
  2201. Critical startup error. Please update your plugin!
  2202. If the error persists after updating, contact Maximvdw through spigot PM
  2203. Critical startup error. Please update your plugin!
  2204. If the error persists after updating, contact Maximvdw through spigot PM
  2205. Critical startup error. Please update your plugin!
  2206. If the error persists after updating, contact Maximvdw through spigot PM
  2207. Critical startup error. Please update your plugin!
  2208. If the error persists after updating, contact Maximvdw through spigot PM
  2209. Critical startup error. Please update your plugin!
  2210. If the error persists after updating, contact Maximvdw through spigot PM
  2211. Critical startup error. Please update your plugin!
  2212. If the error persists after updating, contact Maximvdw through spigot PM
  2213. Critical startup error. Please update your plugin!
  2214. If the error persists after updating, contact Maximvdw through spigot PM
  2215. Critical startup error. Please update your plugin!
  2216. If the error persists after updating, contact Maximvdw through spigot PM
  2217. Critical startup error. Please update your plugin!
  2218. If the error persists after updating, contact Maximvdw through spigot PM
  2219. Critical startup error. Please update your plugin!
  2220. If the error persists after updating, contact Maximvdw through spigot PM
  2221. Critical startup error. Please update your plugin!
  2222. If the error persists after updating, contact Maximvdw through spigot PM
  2223. Critical startup error. Please update your plugin!
  2224. If the error persists after updating, contact Maximvdw through spigot PM
  2225. Critical startup error. Please update your plugin!
  2226. If the error persists after updating, contact Maximvdw through spigot PM
  2227. Critical startup error. Please update your plugin!
  2228. If the error persists after updating, contact Maximvdw through spigot PM
  2229. Critical startup error. Please update your plugin!
  2230. If the error persists after updating, contact Maximvdw through spigot PM
  2231. Critical startup error. Please update your plugin!
  2232. If the error persists after updating, contact Maximvdw through spigot PM
  2233. Critical startup error. Please update your plugin!
  2234. If the error persists after updating, contact Maximvdw through spigot PM
  2235. Critical startup error. Please update your plugin!
  2236. If the error persists after updating, contact Maximvdw through spigot PM
  2237. Critical startup error. Please update your plugin!
  2238. If the error persists after updating, contact Maximvdw through spigot PM
  2239. Critical startup error. Please update your plugin!
  2240. If the error persists after updating, contact Maximvdw through spigot PM
  2241. Critical startup error. Please update your plugin!
  2242. If the error persists after updating, contact Maximvdw through spigot PM
  2243. Critical startup error. Please update your plugin!
  2244. If the error persists after updating, contact Maximvdw through spigot PM
  2245. Critical startup error. Please update your plugin!
  2246. If the error persists after updating, contact Maximvdw through spigot PM
  2247. Critical startup error. Please update your plugin!
  2248. If the error persists after updating, contact Maximvdw through spigot PM
  2249. Critical startup error. Please update your plugin!
  2250. If the error persists after updating, contact Maximvdw through spigot PM
  2251. Critical startup error. Please update your plugin!
  2252. If the error persists after updating, contact Maximvdw through spigot PM
  2253. Critical startup error. Please update your plugin!
  2254. If the error persists after updating, contact Maximvdw through spigot PM
  2255. Critical startup error. Please update your plugin!
  2256. If the error persists after updating, contact Maximvdw through spigot PM
  2257. Critical startup error. Please update your plugin!
  2258. If the error persists after updating, contact Maximvdw through spigot PM
  2259. Critical startup error. Please update your plugin!
  2260. If the error persists after updating, contact Maximvdw through spigot PM
  2261. Critical startup error. Please update your plugin!
  2262. If the error persists after updating, contact Maximvdw through spigot PM
  2263. Critical startup error. Please update your plugin!
  2264. If the error persists after updating, contact Maximvdw through spigot PM
  2265. Critical startup error. Please update your plugin!
  2266. If the error persists after updating, contact Maximvdw through spigot PM
  2267. Critical startup error. Please update your plugin!
  2268. If the error persists after updating, contact Maximvdw through spigot PM
  2269. Critical startup error. Please update your plugin!
  2270. If the error persists after updating, c
  2271. [00:45:24] [Server thread/INFO]: ontact Maximvdw through spigot PM
  2272. Critical startup error. Please update your plugin!
  2273. If the error persists after updating, contact Maximvdw through spigot PM
  2274. Critical startup error. Please update your plugin!
  2275. If the error persists after updating, contact Maximvdw through spigot PM
  2276. Critical startup error. Please update your plugin!
  2277. If the error persists after updating, contact Maximvdw through spigot PM
  2278. Critical startup error. Please update your plugin!
  2279. If the error persists after updating, contact Maximvdw through spigot PM
  2280. Critical startup error. Please update your plugin!
  2281. If the error persists after updating, contact Maximvdw through spigot PM
  2282. Critical startup error. Please update your plugin!
  2283. If the error persists after updating, contact Maximvdw through spigot PM
  2284. Critical startup error. Please update your plugin!
  2285. If the error persists after updating, contact Maximvdw through spigot PM
  2286. Critical startup error. Please update your plugin!
  2287. If the error persists after updating, contact Maximvdw through spigot PM
  2288. Critical startup error. Please update your plugin!
  2289. If the error persists after updating, contact Maximvdw through spigot PM
  2290. Critical startup error. Please update your plugin!
  2291. If the error persists after updating, contact Maximvdw through spigot PM
  2292. Critical startup error. Please update your plugin!
  2293. If the error persists after updating, contact Maximvdw through spigot PM
  2294. Critical startup error. Please update your plugin!
  2295. If the error persists after updating, contact Maximvdw through spigot PM
  2296. Critical startup error. Please update your plugin!
  2297. If the error persists after updating, contact Maximvdw through spigot PM
  2298. Critical startup error. Please update your plugin!
  2299. If the error persists after updating, contact Maximvdw through spigot PM
  2300. Critical startup error. Please update your plugin!
  2301. If the error persists after updating, contact Maximvdw through spigot PM
  2302. Critical startup error. Please update your plugin!
  2303. If the error persists after updating, contact Maximvdw through spigot PM
  2304. Critical startup error. Please update your plugin!
  2305. If the error persists after updating, contact Maximvdw through spigot PM
  2306. Critical startup error. Please update your plugin!
  2307. If the error persists after updating, contact Maximvdw through spigot PM
  2308. Critical startup error. Please update your plugin!
  2309. If the error persists after updating, contact Maximvdw through spigot PM
  2310. Critical startup error. Please update your plugin!
  2311. If the error persists after updating, contact Maximvdw through spigot PM
  2312. Critical startup error. Please update your plugin!
  2313. If the error persists after updating, contact Maximvdw through spigot PM
  2314. Critical startup error. Please update your plugin!
  2315. If the error persists after updating, contact Maximvdw through spigot PM
  2316. Critical startup error. Please update your plugin!
  2317. If the error persists after updating, contact Maximvdw through spigot PM
  2318. Critical startup error. Please update your plugin!
  2319. If the error persists after updating, contact Maximvdw through spigot PM
  2320. Critical startup error. Please update your plugin!
  2321. If the error persists after updating, contact Maximvdw through spigot PM
  2322. Critical startup error. Please update your plugin!
  2323. If the error persists after updating, contact Maximvdw through spigot PM
  2324. Critical startup error. Please update your plugin!
  2325. If the error persists after updating, contact Maximvdw through spigot PM
  2326. Critical startup error. Please update your plugin!
  2327. If the error persists after updating, contact Maximvdw through spigot PM
  2328. Critical startup error. Please update your plugin!
  2329. If the error persists after updating, contact Maximvdw through spigot PM
  2330. Critical startup error. Please update your plugin!
  2331. If the error persists after updating, contact Maximvdw through spigot PM
  2332. Critical startup error. Please update your plugin!
  2333. If the error persists after updating, contact Maximvdw through spigot PM
  2334. Critical startup error. Please update your plugin!
  2335. If the error persists after updating, contact Maximvdw through spigot PM
  2336. Critical startup error. Please update your plugin!
  2337. If the error persists after updating, contact Maximvdw through spigot PM
  2338. Critical startup error. Please update your plugin!
  2339. If the error persists after updating, contact Maximvdw through spigot PM
  2340. Critical startup error. Please update your plugin!
  2341. If the error persists after updating, contact Maximvdw through spigot PM
  2342. Critical startup error. Please update your plugin!
  2343. If the error persists after updating, contact Maximvdw through spigot PM
  2344. Critical startup error. Please update your plugin!
  2345. If the error persists after updating, contact Maximvdw through spigot PM
  2346. Critical startup error. Please update your plugin!
  2347. If the error persists after updating, contact Maximvdw through spigot PM
  2348. Critical startup error. Please update your plugin!
  2349. If the error persists after updating, contact Maximvdw through spigot PM
  2350. Critical startup error. Please update your plugin!
  2351. If the error persists after updating, contact Maximvdw through spigot PM
  2352. Critical startup error. Please update your plugin!
  2353. If the error persists after updating, contact Maximvdw through spigot PM
  2354. Critical startup error. Please update your plugin!
  2355. If the error persists after updating, contact Maximvdw through spigot PM
  2356. Critical startup error. Please update your plugin!
  2357. If the error persists after updating, contact Maximvdw through spigot PM
  2358. Critical startup error. Please update your plugin!
  2359. If the error persists after updating, contact Maximvdw through spigot PM
  2360. Critical startup error. Please update your plugin!
  2361. If the error persists after updating, contact Maximvdw through spigot PM
  2362. Critical startup error. Please update your plugin!
  2363. If the error persists after updating, contact Maximvdw through spigot PM
  2364. Critical startup error. Please update your plugin!
  2365. If the error persists after updating, contact Maximvdw through spigot PM
  2366. Critical startup error. Please update your plugin!
  2367. If the error persists after updating, contact Maximvdw through spigot PM
  2368. Critical startup error. Please update your plugin!
  2369. If the error persists after updating, contact Maximvdw through spigot PM
  2370. Critical startup error. Please update your plugin!
  2371. If the error persists after updating, contact Maximvdw through spigot PM
  2372. Critical startup error. Please update your plugin!
  2373. If the error persists after updating, contact Maximvdw through spigot PM
  2374. Critical startup error. Please update your plugin!
  2375. If the error persists after updating, contact Maximvdw through spigot PM
  2376. Critical startup error. Please update your plugin!
  2377. If the error persists after updating, contact Maximvdw through spigot PM
  2378. Critical startup error. Please update your plugin!
  2379. If the error persists after updating, contact Maximvdw through spigot PM
  2380. Critical startup error. Please update your plugin!
  2381. If the error persists after updating, contact Maximvdw through spigot PM
  2382. Critical startup error. Please update your plugin!
  2383. If the error persists after updating, contact Maximvdw through spigot PM
  2384. Critical startup error. Please update your plugin!
  2385. If the error persists after updating, contact Maximvdw through spigot PM
  2386. Critical startup error. Please update your plugin!
  2387. If the error persists after updating, contact Maximvdw through spigot PM
  2388. Critical startup error. Please update your plugin!
  2389. If the error persists after updating, contact Maximvdw through spigot PM
  2390. Critical startup error. Please update your plugin!
  2391. If the error persists after updating, contact Maximvdw through spigot PM
  2392. Critical startup error. Please update your plugin!
  2393. If the error persists after updating, contact Maximvdw through spigot PM
  2394. Critical startup error. Please update your plugin!
  2395. If the error persists after updating, contact Maximvdw through spigot PM
  2396. Critical startup error. Please update your plugin!
  2397. If the error persists after updating, contact Maximvdw through spigot PM
  2398. Critical startup error. Please update your plugin!
  2399. If the error persists after updating, contact Maximvdw through spigot PM
  2400. Critical startup error. Please update your plugin!
  2401. If the error persists after updating, contact Maximvdw through spigot PM
  2402. Critical startup error. Please update your plugin!
  2403. If the error persists after updating, contact M
  2404. [00:45:24] [Server thread/INFO]: aximvdw through spigot PM
  2405. Critical startup error. Please update your plugin!
  2406. If the error persists after updating, contact Maximvdw through spigot PM
  2407. Critical startup error. Please update your plugin!
  2408. If the error persists after updating, contact Maximvdw through spigot PM
  2409. Critical startup error. Please update your plugin!
  2410. If the error persists after updating, contact Maximvdw through spigot PM
  2411. Critical startup error. Please update your plugin!
  2412. If the error persists after updating, contact Maximvdw through spigot PM
  2413. Critical startup error. Please update your plugin!
  2414. If the error persists after updating, contact Maximvdw through spigot PM
  2415. Critical startup error. Please update your plugin!
  2416. If the error persists after updating, contact Maximvdw through spigot PM
  2417. Critical startup error. Please update your plugin!
  2418. If the error persists after updating, contact Maximvdw through spigot PM
  2419. Critical startup error. Please update your plugin!
  2420. If the error persists after updating, contact Maximvdw through spigot PM
  2421. Critical startup error. Please update your plugin!
  2422. If the error persists after updating, contact Maximvdw through spigot PM
  2423. Critical startup error. Please update your plugin!
  2424. If the error persists after updating, contact Maximvdw through spigot PM
  2425. Critical startup error. Please update your plugin!
  2426. If the error persists after updating, contact Maximvdw through spigot PM
  2427. Critical startup error. Please update your plugin!
  2428. If the error persists after updating, contact Maximvdw through spigot PM
  2429. Critical startup error. Please update your plugin!
  2430. If the error persists after updating, contact Maximvdw through spigot PM
  2431. Critical startup error. Please update your plugin!
  2432. If the error persists after updating, contact Maximvdw through spigot PM
  2433. Critical startup error. Please update your plugin!
  2434. If the error persists after updating, contact Maximvdw through spigot PM
  2435. Critical startup error. Please update your plugin!
  2436. If the error persists after updating, contact Maximvdw through spigot PM
  2437. Critical startup error. Please update your plugin!
  2438. If the error persists after updating, contact Maximvdw through spigot PM
  2439. Critical startup error. Please update your plugin!
  2440. If the error persists after updating, contact Maximvdw through spigot PM
  2441. Critical startup error. Please update your plugin!
  2442. If the error persists after updating, contact Maximvdw through spigot PM
  2443. Critical startup error. Please update your plugin!
  2444. If the error persists after updating, contact Maximvdw through spigot PM
  2445. Critical startup error. Please update your plugin!
  2446. If the error persists after updating, contact Maximvdw through spigot PM
  2447. Critical startup error. Please update your plugin!
  2448. If the error persists after updating, contact Maximvdw through spigot PM
  2449. Critical startup error. Please update your plugin!
  2450. If the error persists after updating, contact Maximvdw through spigot PM
  2451. Critical startup error. Please update your plugin!
  2452. If the error persists after updating, contact Maximvdw through spigot PM
  2453. Critical startup error. Please update your plugin!
  2454. If the error persists after updating, contact Maximvdw through spigot PM
  2455. Critical startup error. Please update your plugin!
  2456. If the error persists after updating, contact Maximvdw through spigot PM
  2457. Critical startup error. Please update your plugin!
  2458. If the error persists after updating, contact Maximvdw through spigot PM
  2459. Critical startup error. Please update your plugin!
  2460. If the error persists after updating, contact Maximvdw through spigot PM
  2461. Critical startup error. Please update your plugin!
  2462. If the error persists after updating, contact Maximvdw through spigot PM
  2463. Critical startup error. Please update your plugin!
  2464. If the error persists after updating, contact Maximvdw through spigot PM
  2465. Critical startup error. Please update your plugin!
  2466. If the error persists after updating, contact Maximvdw through spigot PM
  2467. Critical startup error. Please update your plugin!
  2468. If the error persists after updating, contact Maximvdw through spigot PM
  2469. Critical startup error. Please update your plugin!
  2470. If the error persists after updating, contact Maximvdw through spigot PM
  2471. [00:45:24] [Server thread/INFO]: [FeatherBoard] Adding command 'featherboard'
  2472. [00:45:24] [Server thread/INFO]: [AntiDisconnectSpam] Enabling AntiDisconnectSpam v1.0
  2473. [00:45:24] [Server thread/INFO]: [AntiDisconnectSpam] Starting...
  2474. [00:45:24] [Server thread/INFO]: [AntiDisconnectSpam] Started!
  2475. [00:45:24] [Server thread/INFO]: [ViaVersion] Enabling ViaVersion v2.1.2
  2476. [00:45:24] [Server thread/INFO]: [ViaVersion] Loading 1.12.2 -> 1.13 block mapping...
  2477. [00:45:24] [Server thread/INFO]: [ViaVersion] Loading 1.12.2 -> 1.13 item mapping...
  2478. [00:45:24] [Server thread/INFO]: [ViaVersion] Loading new 1.13 tags...
  2479. [00:45:24] [Server thread/INFO]: [ViaVersion] Loading 1.12.2 -> 1.13 enchantment mapping...
  2480. [00:45:24] [Server thread/INFO]: [ViaVersion] Loading 1.12.2 -> 1.13 sound mapping...
  2481. [00:45:24] [Server thread/INFO]: [ViaVersion] Loading translation mappping
  2482. [00:45:24] [Server thread/INFO]: [ViaVersion] Loading 1.13.2 -> 1.14 blockstate mapping...
  2483. [00:45:25] [Server thread/INFO]: [ViaVersion] Loading 1.13.2 -> 1.14 block mapping...
  2484. [00:45:25] [Server thread/INFO]: [ViaVersion] Loading 1.13.2 -> 1.14 item mapping...
  2485. [00:45:25] [Server thread/INFO]: [ViaVersion] Loading 1.13.2 -> 1.14 sound mapping...
  2486. [00:45:25] [Server thread/INFO]: [ViaVersion] Loading 1.14 blockstates...
  2487. [00:45:25] [Server thread/INFO]: [ViaVersion] Loading 1.14 heightmap data...
  2488. [00:45:25] [Server thread/INFO]: [SDTSpawner] Enabling SDTSpawner v1.1
  2489. [00:45:25] [Server thread/INFO]: [SDTSpawner] Plugin successfully enabled! Version: 1.1
  2490. [00:45:25] [Server thread/INFO]: [Tablist] Enabling Tablist v1.2.3.7
  2491. [00:45:25] [Server thread/INFO]: Tablist> Tablist v1.2.3.7 enabled!!
  2492. [00:45:25] [Server thread/INFO]: [ChestShop] Enabling ChestShop v3.8.12
  2493. [00:45:25] [Server thread/ERROR]: WARNING: you seem to not be using the Xerial SQLite driver. See ORMLite docs on SQLite: http://ormlite.com/docs/sqlite
  2494. [00:45:25] [Server thread/INFO]: creating table 'items'
  2495. [00:45:25] [Server thread/INFO]: executed create table statement changed 0 rows: CREATE TABLE IF NOT EXISTS `items` (`id` INTEGER PRIMARY KEY AUTOINCREMENT , `code` VARCHAR NOT NULL , UNIQUE (`code`))
  2496. [00:45:25] [Server thread/ERROR]: WARNING: you seem to not be using the Xerial SQLite driver. See ORMLite docs on SQLite: http://ormlite.com/docs/sqlite
  2497. [00:45:25] [Server thread/INFO]: creating table 'accounts'
  2498. [00:45:25] [Server thread/INFO]: creating index 'accounts_shortName_idx' for table 'accounts
  2499. [00:45:25] [Server thread/INFO]: executed create table statement changed 0 rows: CREATE TABLE IF NOT EXISTS `accounts` (`lastSeenName` VARCHAR NOT NULL , `name` VARCHAR NOT NULL , `shortName` VARCHAR NOT NULL , `uuid` VARCHAR NOT NULL , PRIMARY KEY (`name`) )
  2500. [00:45:25] [Server thread/INFO]: executed create table statement changed 0 rows: CREATE INDEX IF NOT EXISTS `accounts_shortName_idx` ON `accounts` ( `shortName` )
  2501. [00:45:25] [Server thread/INFO]: [ChestShop] Vault loaded! Found an economy plugin!
  2502. [00:45:25] [Server thread/INFO]: [Essentials] Enabling Essentials v2.17.0.0
  2503. [00:45:25] [Server thread/INFO]: Attempting to convert old kits in config.yml to new kits.yml
  2504. [00:45:25] [Server thread/INFO]: No kits found to migrate.
  2505. [00:45:25] [Server thread/INFO]: [Essentials] Using legacy item data provider as mob spawner provider.
  2506. [00:45:25] [Server thread/INFO]: [Essentials] Using legacy item data provider as spawn egg provider.
  2507. [00:45:25] [Server thread/INFO]: [Essentials] Using legacy potion meta provider as potion meta provider.
  2508. [00:45:25] [Server thread/INFO]: Loaded 852 items from items.csv.
  2509. [00:45:25] [Server thread/INFO]: Using locale pl
  2510. [00:45:25] [Server thread/INFO]: [Essentials] ServerListPingEvent: Spigot iterator API
  2511. [00:45:25] [Server thread/INFO]: [Essentials] Starting Metrics. Opt-out using the global bStats config.
  2512. [00:45:25] [Server thread/INFO]: [Vault][Economy] Essentials Economy hooked.
  2513. [00:45:25] [Server thread/INFO]: [Essentials] Using Vault based permissions (PermissionsEx)
  2514. [00:45:25] [Server thread/INFO]: [Essentials] Payment method found (Vault - Economy: iConomy 7 version: 1.5.3-b37)
  2515. [00:45:25] [Server thread/INFO]: [JoinMessagePlus] Enabling JoinMessagePlus v3.1
  2516. [00:45:25] [Server thread/INFO]: [JoinMessagePlus] [#]==========< JoinMessagePlus >==========[#]
  2517. [00:45:25] [Server thread/INFO]: [JoinMessagePlus] Version: 3.1
  2518. [00:45:25] [Server thread/INFO]: [JoinMessagePlus] Web: dev.bukkit.org/bukkit-plugins/join-message-plus/
  2519. [00:45:25] [Server thread/INFO]: [JoinMessagePlus] Mode: Standalone
  2520. [00:45:25] [Server thread/INFO]: [JoinMessagePlus] Plugin by AndyCraftz
  2521. [00:45:25] [Server thread/INFO]: [EssentialsChat] Enabling EssentialsChat v2.17.0.0
  2522. [00:45:25] [Server thread/INFO]: [UltimateCasino] Enabling UltimateCasino v1.4.0
  2523. [00:45:25] [Server thread/INFO]: Casino has been enabled!
  2524. [00:45:25] [Server thread/INFO]: [IslandBorder] Enabling IslandBorder vBuild 1
  2525. [00:45:25] [Server thread/INFO]: -------------------------------
  2526. [00:45:25] [Server thread/INFO]:
  2527. [00:45:25] [Server thread/INFO]: There is a new update available!
  2528. [00:45:25] [Server thread/INFO]:
  2529. [00:45:25] [Server thread/INFO]: Plugin version: Build 1
  2530. [00:45:25] [Server thread/INFO]: Update version: Build 2
  2531. [00:45:25] [Server thread/INFO]:
  2532. [00:45:25] [Server thread/INFO]: https://www.spigotmc.org/resources/56320/
  2533. [00:45:25] [Server thread/INFO]: -------------------------------
  2534. [00:45:26] [Server thread/INFO]: [EssentialsSpawn] Enabling EssentialsSpawn v2.17.0.0
  2535. [00:45:26] [Server thread/INFO]: [Multiverse-Core] Enabling Multiverse-Core v2.5-b665
  2536. [00:45:26] [Server thread/INFO]: [Multiverse-Core] [AllPay] - Version 13.0 - hooked into iConomy 6 for Multiverse-Core v2.5-b665
  2537. [00:45:26] [Server thread/INFO]: -------- World Settings For [ASkyBlock_nether] --------
  2538. [00:45:26] [Server thread/INFO]: Anti X-Ray: true
  2539. [00:45:26] [Server thread/INFO]: Engine Mode: 1
  2540. [00:45:26] [Server thread/INFO]: Hidden Blocks: [14, 15, 16, 21, 48, 49, 54, 56, 73, 74, 82, 129, 130]
  2541. [00:45:26] [Server thread/INFO]: Replace Blocks: [1, 5]
  2542. [00:45:26] [Server thread/INFO]: Mob Spawn Range: 3
  2543. [00:45:26] [Server thread/INFO]: Nerfing mobs spawned from spawners: true
  2544. [00:45:26] [Server thread/INFO]: Cactus Growth Modifier: 100%
  2545. [00:45:26] [Server thread/INFO]: Cane Growth Modifier: 100%
  2546. [00:45:26] [Server thread/INFO]: Melon Growth Modifier: 100%
  2547. [00:45:26] [Server thread/INFO]: Mushroom Growth Modifier: 100%
  2548. [00:45:26] [Server thread/INFO]: Pumpkin Growth Modifier: 100%
  2549. [00:45:26] [Server thread/INFO]: Sapling Growth Modifier: 100%
  2550. [00:45:26] [Server thread/INFO]: Wheat Growth Modifier: 100%
  2551. [00:45:26] [Server thread/INFO]: NetherWart Growth Modifier: 100%
  2552. [00:45:26] [Server thread/INFO]: Entity Activation Range: An 6 / Mo 16 / Mi 2
  2553. [00:45:26] [Server thread/INFO]: Entity Tracking Range: Pl 48 / An 48 / Mo 48 / Mi 32 / Other 64
  2554. [00:45:26] [Server thread/INFO]: Hopper Transfer: 24 Hopper Check: 24 Hopper Amount: 5
  2555. [00:45:26] [Server thread/INFO]: Random Lighting Updates: false
  2556. [00:45:26] [Server thread/INFO]: Structure Info Saving: true
  2557. [00:45:26] [Server thread/INFO]: Sending up to 10 chunks per packet
  2558. [00:45:26] [Server thread/INFO]: Max Entity Collisions: 2
  2559. [00:45:26] [Server thread/INFO]: Custom Map Seeds: Village: 10387312 Feature: 14357617
  2560. [00:45:26] [Server thread/INFO]: Max TNT Explosions: 100
  2561. [00:45:26] [Server thread/INFO]: Tile Max Tick Time: 20ms Entity max Tick Time: 20ms
  2562. [00:45:26] [Server thread/INFO]: Item Despawn Rate: 6000
  2563. [00:45:26] [Server thread/INFO]: Item Merge Radius: 3.5
  2564. [00:45:26] [Server thread/INFO]: Arrow Despawn Rate: 1200
  2565. [00:45:26] [Server thread/INFO]: Allow Zombie Pigmen to spawn from portal blocks: true
  2566. [00:45:26] [Server thread/INFO]: View Distance: 8
  2567. [00:45:26] [Server thread/INFO]: Zombie Aggressive Towards Villager: true
  2568. [00:45:26] [Server thread/INFO]: Chunks to Grow per Tick: 650
  2569. [00:45:26] [Server thread/INFO]: Clear tick list: false
  2570. [00:45:26] [Server thread/INFO]: Experience Merge Radius: 6.0
  2571. [00:45:26] [Server thread/INFO]: -------- World Settings For [ASkyBlock_nether] --------
  2572. [00:45:26] [Server thread/INFO]: Player blocking damage multiplier set to 0.5
  2573. [00:45:26] [Server thread/INFO]: Remove invalid mob spawner tile entities: true
  2574. [00:45:26] [Server thread/INFO]: Squids will spawn between Y: 45.0 and Y: 63.0
  2575. [00:45:26] [Server thread/INFO]: Max height for cactus growth 3. Max height for reed growth 3
  2576. [00:45:26] [Server thread/INFO]: Living Entity Despawn Ranges: Soft: 32 Hard: 128
  2577. [00:45:26] [Server thread/INFO]: Water over lava flow speed: 5
  2578. [00:45:26] [Server thread/INFO]: Fix TNT cannons: false
  2579. [00:45:26] [Server thread/INFO]: Allow undead horse types to be leashed: false
  2580. [00:45:26] [Server thread/INFO]: Keep spawn chunk loaded: true
  2581. [00:45:26] [Server thread/INFO]: World async lighting: false
  2582. [00:45:26] [Server thread/INFO]: WorldServer TickNextTick cap set at 10000
  2583. [00:45:26] [Server thread/INFO]: WorldServer TickNextTickList cap always processes redstone: false
  2584. [00:45:26] [Server thread/INFO]: Preparing start region for level 4 (Seed: -8205461886318484316)
  2585. [00:45:26] [Server thread/INFO]: [WorldGuard] (ASkyBlock_nether) TNT ignition is PERMITTED.
  2586. [00:45:26] [Server thread/INFO]: [WorldGuard] (ASkyBlock_nether) Lighters are PERMITTED.
  2587. [00:45:26] [Server thread/INFO]: [WorldGuard] (ASkyBlock_nether) Lava fire is blocked.
  2588. [00:45:26] [Server thread/INFO]: [WorldGuard] (ASkyBlock_nether) Fire spread is UNRESTRICTED.
  2589. [00:45:26] [Server thread/INFO]: [WorldGuard] Loaded configuration for world 'ASkyBlock_nether'
  2590. [00:45:26] [Server thread/INFO]: -------- World Settings For [spawnik] --------
  2591. [00:45:26] [Server thread/INFO]: Anti X-Ray: true
  2592. [00:45:26] [Server thread/INFO]: Engine Mode: 1
  2593. [00:45:26] [Server thread/INFO]: Hidden Blocks: [14, 15, 16, 21, 48, 49, 54, 56, 73, 74, 82, 129, 130]
  2594. [00:45:26] [Server thread/INFO]: Replace Blocks: [1, 5]
  2595. [00:45:26] [Server thread/INFO]: Mob Spawn Range: 3
  2596. [00:45:26] [Server thread/INFO]: Nerfing mobs spawned from spawners: true
  2597. [00:45:26] [Server thread/INFO]: Cactus Growth Modifier: 100%
  2598. [00:45:26] [Server thread/INFO]: Cane Growth Modifier: 100%
  2599. [00:45:26] [Server thread/INFO]: Melon Growth Modifier: 100%
  2600. [00:45:26] [Server thread/INFO]: Mushroom Growth Modifier: 100%
  2601. [00:45:26] [Server thread/INFO]: Pumpkin Growth Modifier: 100%
  2602. [00:45:26] [Server thread/INFO]: Sapling Growth Modifier: 100%
  2603. [00:45:26] [Server thread/INFO]: Wheat Growth Modifier: 100%
  2604. [00:45:26] [Server thread/INFO]: NetherWart Growth Modifier: 100%
  2605. [00:45:26] [Server thread/INFO]: Entity Activation Range: An 6 / Mo 16 / Mi 2
  2606. [00:45:26] [Server thread/INFO]: Entity Tracking Range: Pl 48 / An 48 / Mo 48 / Mi 32 / Other 64
  2607. [00:45:26] [Server thread/INFO]: Hopper Transfer: 24 Hopper Check: 24 Hopper Amount: 5
  2608. [00:45:26] [Server thread/INFO]: Random Lighting Updates: false
  2609. [00:45:26] [Server thread/INFO]: Structure Info Saving: true
  2610. [00:45:26] [Server thread/INFO]: Sending up to 10 chunks per packet
  2611. [00:45:26] [Server thread/INFO]: Max Entity Collisions: 2
  2612. [00:45:26] [Server thread/INFO]: Custom Map Seeds: Village: 10387312 Feature: 14357617
  2613. [00:45:26] [Server thread/INFO]: Max TNT Explosions: 100
  2614. [00:45:26] [Server thread/INFO]: Tile Max Tick Time: 20ms Entity max Tick Time: 20ms
  2615. [00:45:26] [Server thread/INFO]: Item Despawn Rate: 6000
  2616. [00:45:26] [Server thread/INFO]: Item Merge Radius: 3.5
  2617. [00:45:26] [Server thread/INFO]: Arrow Despawn Rate: 1200
  2618. [00:45:26] [Server thread/INFO]: Allow Zombie Pigmen to spawn from portal blocks: true
  2619. [00:45:26] [Server thread/INFO]: View Distance: 8
  2620. [00:45:26] [Server thread/INFO]: Zombie Aggressive Towards Villager: true
  2621. [00:45:26] [Server thread/INFO]: Chunks to Grow per Tick: 650
  2622. [00:45:26] [Server thread/INFO]: Clear tick list: false
  2623. [00:45:26] [Server thread/INFO]: Experience Merge Radius: 6.0
  2624. [00:45:26] [Server thread/INFO]: -------- World Settings For [spawnik] --------
  2625. [00:45:26] [Server thread/INFO]: Player blocking damage multiplier set to 0.5
  2626. [00:45:26] [Server thread/INFO]: Remove invalid mob spawner tile entities: true
  2627. [00:45:26] [Server thread/INFO]: Squids will spawn between Y: 45.0 and Y: 63.0
  2628. [00:45:26] [Server thread/INFO]: Max height for cactus growth 3. Max height for reed growth 3
  2629. [00:45:26] [Server thread/INFO]: Living Entity Despawn Ranges: Soft: 32 Hard: 128
  2630. [00:45:26] [Server thread/INFO]: Water over lava flow speed: 5
  2631. [00:45:26] [Server thread/INFO]: Fix TNT cannons: false
  2632. [00:45:26] [Server thread/INFO]: Allow undead horse types to be leashed: false
  2633. [00:45:26] [Server thread/INFO]: Keep spawn chunk loaded: true
  2634. [00:45:26] [Server thread/INFO]: World async lighting: false
  2635. [00:45:26] [Server thread/INFO]: WorldServer TickNextTick cap set at 10000
  2636. [00:45:26] [Server thread/INFO]: WorldServer TickNextTickList cap always processes redstone: false
  2637. [00:45:26] [Server thread/INFO]: Preparing start region for level 5 (Seed: 6142876165155285246)
  2638. [00:45:26] [Server thread/INFO]: [WorldGuard] (spawnik) TNT ignition is PERMITTED.
  2639. [00:45:26] [Server thread/INFO]: [WorldGuard] (spawnik) Lighters are PERMITTED.
  2640. [00:45:26] [Server thread/INFO]: [WorldGuard] (spawnik) Lava fire is blocked.
  2641. [00:45:26] [Server thread/INFO]: [WorldGuard] (spawnik) Fire spread is UNRESTRICTED.
  2642. [00:45:26] [Server thread/INFO]: [WorldGuard] Loaded configuration for world 'spawnik'
  2643. [00:45:26] [Server thread/INFO]: [Multiverse-Core] 6 - World(s) loaded.
  2644. [00:45:26] [Server thread/INFO]: [Multiverse-Core] Version 2.5-b665 (API v18) Enabled - By Rigby, fernferret, lithium3141 and main--
  2645. [00:45:26] [Server thread/INFO]: [AuthMe] Enabling AuthMe v3.4
  2646. [00:45:26] [Server thread/INFO]: [AuthMe] Loading Configuration File...
  2647. [00:45:26] [Server thread/INFO]: [AuthMe] Set Language: en
  2648. [00:45:26] [Server thread/INFO]: [AuthMe] Vault plugin detected, hook with PermissionsEx system
  2649. [00:45:26] [Server thread/INFO]: [AuthMe] Hook with Multiverse-Core for SpawnLocations
  2650. [00:45:26] [Server thread/INFO]: [AuthMe] Hook with Essentials plugin
  2651. [00:45:26] [Server thread/INFO]: [AuthMe] Hook with EssentialsSpawn plugin
  2652. [00:45:26] [Thread-13/INFO]: [AuthMe] MySQL driver loaded
  2653. [00:45:26] [Thread-13/INFO]: [AuthMe] Connection pool ready
  2654. [00:45:26] [Server thread/INFO]: [AuthMe] LICENSE : This product includes GeoLite data created by MaxMind, available from http://www.maxmind.com
  2655. [00:45:26] [Server thread/INFO]: [AuthMe] Authme 3.4 enabled
  2656. [00:45:26] [Server thread/INFO]: Server permissions file permissions.yml is empty, ignoring it
  2657. [00:45:26] [Server thread/INFO]: Done (6.140s)! For help, type "help" or "?"
  2658. [00:45:26] [Server thread/INFO]: Starting GS4 status listener
  2659. [00:45:26] [Query Listener #1/INFO]: Query running on 10.0.176.40:25565
  2660. [00:45:26] [Server thread/INFO]: Using epoll channel type
  2661. [00:45:26] [Server thread/INFO]: Timings Reset
  2662. [00:45:27] [Server thread/INFO]: [ViaVersion] ViaVersion detected server version: 1.8.x(47)
  2663. [00:45:27] [Craft Scheduler Thread - 3/INFO]: [Skript] Checking for the latest version of Skript...
  2664. [00:45:27] [Server thread/INFO]: [ViaVersion] Enabling Paper/TacoSpigot/Torch patch: Fixes block placement.
  2665. [00:45:27] [Craft Scheduler Thread - 9/INFO]: [FeatherBoard] Loaded '0' players from the database!
  2666. [00:45:27] [Server thread/WARN]: [Skript] Empty configuration section! You might want to indent one or more of the subsequent lines to make them belong to this section or remove the colon at the end of the line if you don't want this line to start a section. (MLECZUFAKECHAT.sk, line 11: loop 100 times:')
  2667. [00:45:27] [Server thread/WARN]: [Skript] Empty configuration section! You might want to indent one or more of the subsequent lines to make them belong to this section or remove the colon at the end of the line if you don't want this line to start a section. (MLECZUFAKECHAT.sk, line 25: loop 100 times:')
  2668. [00:45:27] [Craft Scheduler Thread - 8/INFO]: [SkinsRestorer] ----------------------------------------------
  2669. [00:45:27] [Craft Scheduler Thread - 8/INFO]: [SkinsRestorer] +===============+
  2670. [00:45:27] [Craft Scheduler Thread - 8/INFO]: [SkinsRestorer] | SkinsRestorer |
  2671. [00:45:27] [Craft Scheduler Thread - 8/INFO]: [SkinsRestorer] +===============+
  2672. [00:45:27] [Craft Scheduler Thread - 8/INFO]: [SkinsRestorer] ----------------------------------------------
  2673. [00:45:27] [Craft Scheduler Thread - 8/INFO]: [SkinsRestorer] Current version: 13.7.1
  2674. [00:45:27] [Craft Scheduler Thread - 8/INFO]: [SkinsRestorer] This is the latest version!
  2675. [00:45:27] [Craft Scheduler Thread - 8/INFO]: [SkinsRestorer] ----------------------------------------------
  2676. [00:45:27] [Skript update thread/INFO]: [Skript] You're currently running the latest stable version of Skript.
  2677. [00:45:27] [Server thread/WARN]: [Skript] Possible name conflict of variables {konkurs.znak1} and {konkurs.znak%loop-number%} (there might be more conflicts). (konkurs.sk, line 20: set {konkurs.kod} to "%{konkurs.znak1}%%{konkurs.znak2}%%{konkurs.znak3}%%{konkurs.znak4}%%{konkurs.znak5}%%{konkurs.znak6}%"')
  2678. [00:45:27] [Server thread/WARN]: [Skript] Possible name conflict of variables {konkurs.znak2} and {konkurs.znak%loop-number%} (there might be more conflicts). (konkurs.sk, line 20: set {konkurs.kod} to "%{konkurs.znak1}%%{konkurs.znak2}%%{konkurs.znak3}%%{konkurs.znak4}%%{konkurs.znak5}%%{konkurs.znak6}%"')
  2679. [00:45:27] [Server thread/WARN]: [Skript] Possible name conflict of variables {konkurs.znak3} and {konkurs.znak%loop-number%} (there might be more conflicts). (konkurs.sk, line 20: set {konkurs.kod} to "%{konkurs.znak1}%%{konkurs.znak2}%%{konkurs.znak3}%%{konkurs.znak4}%%{konkurs.znak5}%%{konkurs.znak6}%"')
  2680. [00:45:27] [Server thread/WARN]: [Skript] Possible name conflict of variables {konkurs.znak4} and {konkurs.znak%loop-number%} (there might be more conflicts). (konkurs.sk, line 20: set {konkurs.kod} to "%{konkurs.znak1}%%{konkurs.znak2}%%{konkurs.znak3}%%{konkurs.znak4}%%{konkurs.znak5}%%{konkurs.znak6}%"')
  2681. [00:45:27] [Server thread/WARN]: [Skript] Possible name conflict of variables {konkurs.znak5} and {konkurs.znak%loop-number%} (there might be more conflicts). (konkurs.sk, line 20: set {konkurs.kod} to "%{konkurs.znak1}%%{konkurs.znak2}%%{konkurs.znak3}%%{konkurs.znak4}%%{konkurs.znak5}%%{konkurs.znak6}%"')
  2682. [00:45:27] [Server thread/WARN]: [Skript] Possible name conflict of variables {konkurs.znak6} and {konkurs.znak%loop-number%} (there might be more conflicts). (konkurs.sk, line 20: set {konkurs.kod} to "%{konkurs.znak1}%%{konkurs.znak2}%%{konkurs.znak3}%%{konkurs.znak4}%%{konkurs.znak5}%%{konkurs.znak6}%"')
  2683. [00:45:28] [Server thread/ERROR]: [Skript] A command event cannot be cancelled (plugins.sk, line 187: cancel event')
  2684. [00:45:28] [Server thread/INFO]: [Skript] Loaded 4 scripts with a total of 34 triggers and 15 commands in 0.92 seconds
  2685. [00:45:28] [Server thread/INFO]: [Skript] Finished loading.
  2686. [00:45:28] [Server thread/INFO]: [ASkyBlock] Silencing command feedback for Ops...
  2687. [00:45:28] [Server thread/INFO]: Game rule has been updated
  2688. [00:45:28] [Server thread/INFO]: [ASkyBlock] If you do not want this, do /gamerule sendCommandFeedback true
  2689. [00:45:28] [Server thread/INFO]: [ASkyBlock] Checking for new updates...
  2690. [00:45:28] [Craft Scheduler Thread - 3/INFO]: [Vault] Checking for Updates ...
  2691. [00:45:28] [Server thread/INFO]: [ASkyBlock] Loading island grid...
  2692. [00:45:28] [Server thread/INFO]: [ASkyBlock] Loading islands.yml
  2693. [00:45:28] [Server thread/INFO]: [ASkyBlock] Loading warps...
  2694. [00:45:28] [Server thread/INFO]: [ASkyBlock] Loading warp panel...
  2695. [00:45:28] [Craft Scheduler Thread - 3/WARN]: [Vault] Stable Version: 1.7.2 is out! You are still running version: 1.5.3
  2696. [00:45:28] [Craft Scheduler Thread - 3/WARN]: [Vault] Update at: http://dev.bukkit.org/server-mods/vault
  2697. [00:45:28] [Server thread/INFO]: [ASkyBlock] Loading Top Ten
  2698. [00:45:28] [Server thread/WARN]: org.bukkit.configuration.InvalidConfigurationException: while scanning an anchor
  2699. in 'string', line 14, column 20:
  2700. description: &0&lWUNGIEL
  2701. ^
  2702. expected alphabetic or numeric character, but found &(38)
  2703. in 'string', line 14, column 22:
  2704. description: &0&lWUNGIEL
  2705. ^
  2706.  
  2707. [00:45:28] [Server thread/WARN]: at org.bukkit.configuration.file.YamlConfiguration.loadFromString(YamlConfiguration.java:57)
  2708. [00:45:28] [Server thread/WARN]: at org.bukkit.configuration.file.FileConfiguration.load(FileConfiguration.java:226)
  2709. [00:45:28] [Server thread/WARN]: at org.bukkit.configuration.file.FileConfiguration.load(FileConfiguration.java:169)
  2710. [00:45:28] [Server thread/WARN]: at com.wasteofplastic.askyblock.util.Util.loadYamlFile(Util.java:89)
  2711. [00:45:28] [Server thread/WARN]: at com.wasteofplastic.askyblock.panels.ControlPanel.loadShop(ControlPanel.java:97)
  2712. [00:45:28] [Server thread/WARN]: at com.wasteofplastic.askyblock.panels.ControlPanel.<init>(ControlPanel.java:66)
  2713. [00:45:28] [Server thread/WARN]: at com.wasteofplastic.askyblock.ASkyBlock$1.lambda$run$0(ASkyBlock.java:468)
  2714. [00:45:28] [Server thread/WARN]: at org.bukkit.craftbukkit.v1_8_R3.scheduler.CraftTask.run(CraftTask.java:59)
  2715. [00:45:28] [Server thread/WARN]: at org.bukkit.craftbukkit.v1_8_R3.scheduler.CraftScheduler.mainThreadHeartbeat(CraftScheduler.java:349)
  2716. [00:45:28] [Server thread/WARN]: at net.minecraft.server.v1_8_R3.MinecraftServer.B(MinecraftServer.java:783)
  2717. [00:45:28] [Server thread/WARN]: at net.minecraft.server.v1_8_R3.DedicatedServer.B(DedicatedServer.java:378)
  2718. [00:45:28] [Server thread/WARN]: at net.minecraft.server.v1_8_R3.MinecraftServer.A(MinecraftServer.java:713)
  2719. [00:45:28] [Server thread/WARN]: at net.minecraft.server.v1_8_R3.MinecraftServer.run(MinecraftServer.java:616)
  2720. [00:45:28] [Server thread/WARN]: at java.lang.Thread.run(Thread.java:748)
  2721. [00:45:28] [Server thread/WARN]: Caused by: while scanning an anchor
  2722. in 'string', line 14, column 20:
  2723. description: &0&lWUNGIEL
  2724. ^
  2725. expected alphabetic or numeric character, but found &(38)
  2726. in 'string', line 14, column 22:
  2727. description: &0&lWUNGIEL
  2728. ^
  2729.  
  2730. [00:45:28] [Server thread/WARN]: at org.yaml.snakeyaml.scanner.ScannerImpl.scanAnchor(ScannerImpl.java:1446)
  2731. [00:45:28] [Server thread/WARN]: at org.yaml.snakeyaml.scanner.ScannerImpl.fetchAnchor(ScannerImpl.java:939)
  2732. [00:45:28] [Server thread/WARN]: at org.yaml.snakeyaml.scanner.ScannerImpl.fetchMoreTokens(ScannerImpl.java:370)
  2733. [00:45:28] [Server thread/WARN]: at org.yaml.snakeyaml.scanner.ScannerImpl.checkToken(ScannerImpl.java:226)
  2734. [00:45:28] [Server thread/WARN]: at org.yaml.snakeyaml.parser.ParserImpl$ParseBlockMappingValue.produce(ParserImpl.java:586)
  2735. [00:45:28] [Server thread/WARN]: at org.yaml.snakeyaml.parser.ParserImpl.peekEvent(ParserImpl.java:158)
  2736. [00:45:28] [Server thread/WARN]: at org.yaml.snakeyaml.parser.ParserImpl.checkEvent(ParserImpl.java:143)
  2737. [00:45:28] [Server thread/WARN]: at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:132)
  2738. [00:45:28] [Server thread/WARN]: at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:229)
  2739. [00:45:28] [Server thread/WARN]: at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:155)
  2740. [00:45:28] [Server thread/WARN]: at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:229)
  2741. [00:45:28] [Server thread/WARN]: at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:155)
  2742. [00:45:28] [Server thread/WARN]: at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:229)
  2743. [00:45:28] [Server thread/WARN]: at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:155)
  2744. [00:45:28] [Server thread/WARN]: at org.yaml.snakeyaml.composer.Composer.composeDocument(Composer.java:122)
  2745. [00:45:28] [Server thread/WARN]: at org.yaml.snakeyaml.composer.Composer.getSingleNode(Composer.java:105)
  2746. [00:45:28] [Server thread/WARN]: at org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:120)
  2747. [00:45:28] [Server thread/WARN]: at org.yaml.snakeyaml.Yaml.loadFromReader(Yaml.java:450)
  2748. [00:45:28] [Server thread/WARN]: at org.yaml.snakeyaml.Yaml.load(Yaml.java:369)
  2749. [00:45:28] [Server thread/WARN]: at org.bukkit.configuration.file.YamlConfiguration.loadFromString(YamlConfiguration.java:55)
  2750. [00:45:28] [Server thread/WARN]: ... 13 more
  2751. [00:45:28] [Server thread/INFO]: [ASkyBlock] All files loaded. Ready to play...
  2752. [00:45:28] [Server thread/INFO]: [ASkyBlock] Metrics loaded.
  2753. [00:45:30] [Server thread/INFO]: [ASkyBlock] No update available.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!