Data hosted with ♥ by Pastebin.com - Download Raw - See Original
  1. [18:15:13] [main/INFO] [LaunchWrapper]: Loading tweak class name net.minecraftforge.fml.common.launcher.FMLServerTweaker
  2. [18:15:13] [main/INFO] [LaunchWrapper]: Using primary tweak class name net.minecraftforge.fml.common.launcher.FMLServerTweaker
  3. [18:15:13] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.common.launcher.FMLServerTweaker
  4. [18:15:13] [main/INFO] [FML]: Forge Mod Loader version 14.23.5.2838 for Minecraft 1.12.2 loading
  5. [18:15:13] [main/INFO] [FML]: Java is Java HotSpot(TM) 64-Bit Server VM, version 1.8.0_191, running on Windows 10:amd64:10.0, installed at C:\Program Files\Java\jre1.8.0_191
  6. [18:15:13] [main/INFO] [FML]: Searching C:\Users\User\Desktop\SERVER\.\mods for mods
  7. [18:15:13] [main/WARN] [FML]: Found FMLCorePluginContainsFMLMod marker in mw-1.11.7.5_mc1.12.2.jar. This is not recommended, @Mods should be in a separate jar from the coremod.
  8. [18:15:13] [main/WARN] [FML]: The coremod weaponlib (com.vicmatskiv.weaponlib.core.WeaponlibCorePlugin) is not signed!
  9. [18:15:13] [main/WARN] [FML]: The coremod ObfuscatePlugin (com.mrcrayfish.obfuscate.asm.ObfuscatePlugin) is not signed!
  10. [18:15:13] [main/INFO] [FML]: Loading tweaker org.spongepowered.asm.launch.MixinTweaker from spongeforge-1.12.2-2825-7.1.6.jar
  11. [18:15:13] [main/INFO] [FML]: Loading tweaker org.spongepowered.asm.launch.MixinTweaker from phosphor-1.12.2-0.2.2+build43-universal.jar
  12. [18:15:13] [main/INFO] [LaunchWrapper]: Loading tweak class name net.minecraftforge.fml.common.launcher.FMLInjectionAndSortingTweaker
  13. [18:15:13] [main/INFO] [LaunchWrapper]: Loading tweak class name org.spongepowered.asm.launch.MixinTweaker
  14. [18:15:13] [main/INFO] [mixin]: SpongePowered MIXIN Subsystem Version=0.7.11 Source=file:/C:/Users/User/Desktop/SERVER/./mods/spongeforge-1.12.2-2825-7.1.6.jar Service=LaunchWrapper Env=SERVER
  15. [18:15:13] [main/WARN] [FML]: The coremod SpongeCoremod (org.spongepowered.mod.SpongeCoremod) is not signed!
  16. [18:15:13] [main/INFO] [mixin]: Compatibility level set to JAVA_8
  17. [18:15:13] [main/INFO] [mixin]: Adding new token provider org.spongepowered.mod.SpongeCoremod$TokenProvider to MixinEnvironment[DEFAULT]
  18. [18:15:13] [main/INFO] [mixin]: Adding new token provider org.spongepowered.mod.SpongeCoremod$TokenProvider to MixinEnvironment[PREINIT]
  19. [18:15:13] [main/INFO] [mixin]: Adding new token provider org.spongepowered.mod.SpongeCoremod$TokenProvider to MixinEnvironment[INIT]
  20. [18:15:13] [main/WARN] [LaunchWrapper]: Tweak class name org.spongepowered.asm.launch.MixinTweaker has already been visited -- skipping
  21. [18:15:13] [main/INFO] [LaunchWrapper]: Loading tweak class name net.minecraftforge.fml.common.launcher.FMLDeobfTweaker
  22. [18:15:13] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.common.launcher.FMLInjectionAndSortingTweaker
  23. [18:15:13] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.common.launcher.FMLInjectionAndSortingTweaker
  24. [18:15:13] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.relauncher.CoreModManager$FMLPluginWrapper
  25. [18:15:14] [main/INFO] [FML]: Found valid fingerprint for Minecraft Forge. Certificate fingerprint e3c3d50c7c986df74c645c0ac54639741c90a557
  26. [18:15:14] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.relauncher.CoreModManager$FMLPluginWrapper
  27. [18:15:14] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.relauncher.CoreModManager$FMLPluginWrapper
  28. [18:15:14] [main/INFO] [LaunchWrapper]: Calling tweak class org.spongepowered.asm.launch.MixinTweaker
  29. [18:15:14] [main/INFO] [mixin]: Initialised Mixin FML Remapper Adapter with net.minecraftforge.fml.common.asm.transformers.deobf.FMLDeobfuscatingRemapper@383f1975
  30. [18:15:14] [main/INFO] [Phosphor Forge Core]: Phosphor has been hooked by Forge, setting up Mixin and plugins
  31. [18:15:14] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.common.launcher.FMLDeobfTweaker
  32. [18:15:15] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.relauncher.CoreModManager$FMLPluginWrapper
  33. [18:15:15] [main/INFO] [LaunchWrapper]: Loading tweak class name net.minecraftforge.fml.common.launcher.TerminalTweaker
  34. [18:15:15] [main/INFO] [LaunchWrapper]: Loading tweak class name org.spongepowered.asm.mixin.EnvironmentStateTweaker
  35. [18:15:15] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.common.launcher.TerminalTweaker
  36. [18:15:15] [main/INFO] [LaunchWrapper]: Calling tweak class org.spongepowered.asm.mixin.EnvironmentStateTweaker
  37. [18:15:15] [main/INFO] [Phosphor Plugin]: Loading configuration
  38. [18:15:15] [main/INFO] [Phosphor Plugin]: Sponge has been detected on the classpath! Sponge mixins will be used.
  39. [18:15:15] [main/WARN] [Phosphor Plugin]: Please keep in mind that Sponge support is **experimental** (although supported). We cannot currentlydetect if you are using Sponge's async lighting feature, so please disable it if you have not already.
  40. [18:15:18] [main/INFO] [Phosphor Plugin]: Disabled mixin 'me.jellysquid.mods.phosphor.mixins.lighting.common.MixinChunk$Vanilla' as we are in a Sponge environment
  41. [18:15:19] [main/WARN] [mixin]: Static binding violation: PRIVATE overwrite method initializeConnectionToPlayer in mixins.common.core.json:server.MixinPlayerList cannot reduce visibiliy of PUBLIC target method, visibility will be upgraded.
  42. [18:15:19] [main/INFO] [LaunchWrapper]: Launching wrapped minecraft {net.minecraft.server.MinecraftServer}
  43. [18:15:24] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: Starting minecraft server version 1.12.2
  44. [18:15:24] [Server thread/INFO] [FML]: MinecraftForge v14.23.5.2838 Initialized
  45. [18:15:24] [Server thread/INFO] [FML]: Starts to replace vanilla recipe ingredients with ore ingredients.
  46. [18:15:24] [Server thread/INFO] [FML]: Invalid recipe found with multiple oredict ingredients in the same ingredient...
  47. [18:15:24] [Server thread/INFO] [FML]: Replaced 1227 ore ingredients
  48. [18:15:24] [Server thread/INFO] [Sponge]: Found mcmod.info at jar:file:/C:/Users/User/Desktop/SERVER/./mods/spongeforge-1.12.2-2825-7.1.6.jar!/mcmod.info
  49. [18:15:24] [Server thread/INFO] [Sponge]: Creating injector in stage 'PRODUCTION'
  50. [18:15:27] [Server thread/INFO] [FML]: Searching C:\Users\User\Desktop\SERVER\.\mods for mods
  51. [18:15:27] [Server thread/INFO] [FML]: Forge Mod Loader has identified 18 mods to load
  52. [18:15:27] [Server thread/WARN] [FML]: Missing English translation for FML: assets/fml/lang/en_us.lang
  53. [18:15:27] [Server thread/WARN] [FML]: Missing English translation for spongeapi: assets/spongeapi/lang/en_us.lang
  54. [18:15:27] [Server thread/WARN] [FML]: Missing English translation for spongeforge: assets/spongeforge/lang/en_us.lang
  55. [18:15:27] [Server thread/WARN] [FML]: Missing English translation for chestrefill: assets/chestrefill/lang/en_us.lang
  56. [18:15:27] [Server thread/WARN] [FML]: Missing English translation for snowvariants: assets/snowvariants/lang/en_us.lang
  57. [18:15:27] [Server thread/WARN] [FML]: Missing English translation for worldedit: assets/worldedit/lang/en_us.lang
  58. [18:15:27] [Server thread/WARN] [FML]: Missing English translation for phosphor-lighting: assets/phosphor-lighting/lang/en_us.lang
  59. [18:15:27] [Server thread/WARN] [Sponge]: The mod spongeforge was designed for forge 1.12.2-14.23.5.2825 but version 14.23.5.2838 is in use. It may not work properly.
  60. [18:15:27] [Server thread/WARN] [Sponge]: The mod spongeforge was designed for forge 1.12.2-14.23.5.2825 but version 14.23.5.2838 is in use. It may not work properly.
  61. [18:15:28] [Server thread/INFO] [FML]: Attempting connection with missing mods [minecraft, mcp, FML, forge, spongeapi, sponge, spongeforge, obfuscate, chestrefill, cfm, mw, nzsmod, snowvariants, toughasnails, vehicle, gvc, worldedit, phosphor-lighting] at CLIENT
  62. [18:15:28] [Server thread/INFO] [FML]: Attempting connection with missing mods [minecraft, mcp, FML, forge, spongeapi, sponge, spongeforge, obfuscate, chestrefill, cfm, mw, nzsmod, snowvariants, toughasnails, vehicle, gvc, worldedit, phosphor-lighting] at SERVER
  63. [18:15:28] [Server thread/WARN] [Sponge]: There's no certificate fingerprint available
  64. [18:15:28] [Server thread/INFO] [FML]: Processing ObjectHolder annotations
  65. [18:15:28] [Server thread/INFO] [FML]: Found 1199 ObjectHolder annotations
  66. [18:15:28] [Server thread/INFO] [FML]: Identifying ItemStackHolder annotations
  67. [18:15:28] [Server thread/INFO] [FML]: Found 0 ItemStackHolder annotations
  68. [18:15:28] [Server thread/INFO] [FML]: Configured a dormant chunk cache size of 0
  69. [18:15:28] [Forge Version Check/INFO] [forge.VersionCheck]: [spongeforge] Starting version check at https://files.minecraftforge.net/maven/org/spongepowered/spongeforge/promotions_slim.json
  70. [18:15:29] [Forge Version Check/INFO] [forge.VersionCheck]: [spongeforge] Found status: OUTDATED Target: 7.1.2
  71. [18:15:29] [Forge Version Check/INFO] [forge.VersionCheck]: [forge] Starting version check at http://files.minecraftforge.net/maven/net/minecraftforge/forge/promotions_slim.json
  72. [18:15:30] [Forge Version Check/INFO] [forge.VersionCheck]: [forge] Found status: AHEAD Target: null
  73. [18:15:30] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment M6Gscope
  74. [18:15:30] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment MA5Dcover
  75. [18:15:30] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment Maxim9cover
  76. [18:15:30] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment DMRscope
  77. [18:15:30] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment BR55scope
  78. [18:15:30] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment G36Scope
  79. [18:15:30] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment AUGScope
  80. [18:15:30] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment SRS99S5scope
  81. [18:15:30] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment PythonClip
  82. [18:15:31] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment MA37Mag
  83. [18:15:31] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment MA5Dmag
  84. [18:15:31] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment BR55mag
  85. [18:15:31] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment M395Bmag
  86. [18:15:31] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment SRS99S5mag
  87. [18:15:31] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment M6Gmag
  88. [18:15:33] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.Weapon$Builder:build:735]: !!!No recipe defined for weapon MA37
  89. [18:15:33] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.Weapon$Builder:build:735]: !!!No recipe defined for weapon MA5D
  90. [18:15:33] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.Weapon$Builder:build:735]: !!!No recipe defined for weapon M395B
  91. [18:15:33] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.Weapon$Builder:build:735]: !!!No recipe defined for weapon SRS99S5
  92. [18:15:33] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.Weapon$Builder:build:735]: !!!No recipe defined for weapon BR55
  93. [18:15:33] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `temperature_spread`, expected `toughasnails`. This could be a intended override, but in most cases indicates a broken mod.
  94. [18:15:33] [Server thread/WARN] [net.minecraft.network.datasync.EntityDataManager]: defineId called for: class net.minecraft.entity.player.EntityPlayer from class com.mrcrayfish.vehicle.common.CommonEvents
  95. [18:15:33] [Server thread/WARN] [net.minecraft.network.datasync.EntityDataManager]: defineId called for: class net.minecraft.entity.player.EntityPlayer from class com.mrcrayfish.vehicle.common.CommonEvents
  96. [18:15:33] [Server thread/WARN] [net.minecraft.network.datasync.EntityDataManager]: defineId called for: class net.minecraft.entity.player.EntityPlayer from class com.mrcrayfish.vehicle.common.CommonEvents
  97. [18:15:34] [Server thread/WARN] [Sponge]: Could not find pipe_down owning class, assigning fallback id: vehicle:block_fluid_pipe_pipe_down
  98. [18:15:34] [Server thread/WARN] [Sponge]: Could not find pipe_east owning class, assigning fallback id: vehicle:block_fluid_pipe_pipe_east
  99. [18:15:34] [Server thread/WARN] [Sponge]: Could not find pipe_north owning class, assigning fallback id: vehicle:block_fluid_pipe_pipe_north
  100. [18:15:34] [Server thread/WARN] [Sponge]: Could not find pipe_south owning class, assigning fallback id: vehicle:block_fluid_pipe_pipe_south
  101. [18:15:34] [Server thread/WARN] [Sponge]: Could not find pipe_up owning class, assigning fallback id: vehicle:block_fluid_pipe_pipe_up
  102. [18:15:34] [Server thread/WARN] [Sponge]: Could not find pipe_west owning class, assigning fallback id: vehicle:block_fluid_pipe_pipe_west
  103. [18:15:34] [Server thread/INFO] [FML]: Applying holder lookups
  104. [18:15:34] [Server thread/INFO] [FML]: Holder lookups applied
  105. [18:15:34] [Server thread/INFO] [FML]: Applying holder lookups
  106. [18:15:34] [Server thread/INFO] [FML]: Holder lookups applied
  107. [18:15:34] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `sponge` for name `human`, expected `spongeforge`. This could be a intended override, but in most cases indicates a broken mod.
  108. [18:15:34] [Server thread/INFO] [FML]: Applying holder lookups
  109. [18:15:34] [Server thread/INFO] [FML]: Holder lookups applied
  110. [18:15:34] [Server thread/INFO] [FML]: Applying holder lookups
  111. [18:15:34] [Server thread/INFO] [FML]: Holder lookups applied
  112. [18:15:34] [Server thread/INFO] [FML]: Injecting itemstacks
  113. [18:15:34] [Server thread/INFO] [FML]: Itemstack injection complete
  114. [18:15:34] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: Loading properties
  115. [18:15:34] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: Default game type: SURVIVAL
  116. [18:15:34] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: Generating keypair
  117. [18:15:34] [pool-4-thread-1/INFO] [Gliby's Voice Chat Mod]: Mod is up-to-date.
  118. [18:15:34] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: Starting Minecraft server on *:25565
  119. [18:15:34] [Server thread/INFO] [net.minecraft.network.NetworkSystem]: Using default channel type
  120. [18:15:34] [Server thread/WARN] [net.minecraft.server.dedicated.DedicatedServer]: **** SERVER IS RUNNING IN OFFLINE/INSECURE MODE!
  121. [18:15:34] [Server thread/WARN] [net.minecraft.server.dedicated.DedicatedServer]: The server will make no attempt to authenticate usernames. Beware.
  122. [18:15:34] [Server thread/WARN] [net.minecraft.server.dedicated.DedicatedServer]: 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.
  123. [18:15:34] [Server thread/WARN] [net.minecraft.server.dedicated.DedicatedServer]: To change this, set "online-mode" to "true" in the server.properties file.
  124. [18:15:34] [Server thread/INFO] [FML]: Applying holder lookups
  125. [18:15:34] [Server thread/INFO] [FML]: Holder lookups applied
  126. [18:15:34] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: [CR] Chest Refill is loading... :D
  127. [18:15:34] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: [CR] Initializing commands...
  128. [18:15:34] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: [CR] Initializing listeners...
  129. [18:15:34] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: [CR] Chest Refill is ready!
  130. [18:15:35] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: [CR] You are using the latest version!
  131. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmoven`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  132. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmfridge`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  133. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmcabinet`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  134. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmfreezer`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  135. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmbedsidecabinet`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  136. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmmailbox`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  137. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmcomputer`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  138. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmprinter`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  139. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmstereo`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  140. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmpresent`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  141. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmbin`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  142. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmwallcabinet`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  143. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmbath`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  144. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmshowerhead`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  145. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmplate`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  146. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmcouch`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  147. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmtoaster`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  148. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmchoppingboard`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  149. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmblender`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  150. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmmicrowave`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  151. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmwashingmachine`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  152. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmdishwasher`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  153. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmcabinetkitchen`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  154. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmcup`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  155. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmcookiejar`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  156. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmtree`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  157. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmmirror`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  158. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmgrill`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  159. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmeski`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  160. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmdoormat`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  161. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmcrate`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  162. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmlightswitch`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  163. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmceilingfan`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  164. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmdeskcabinet`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  165. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmmodernslidingdoor`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  166. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmdigitalclock`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  167. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmtv`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  168. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmkitchencounter`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  169. [18:15:35] [Server thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `cfmkitchencounterdrawer`, expected `cfm`. This could be a intended override, but in most cases indicates a broken mod.
  170. [18:15:35] [Server thread/INFO] [FML]: Injecting itemstacks
  171. [18:15:35] [Server thread/INFO] [FML]: Itemstack injection complete
  172. [18:15:36] [Server thread/INFO] [worldedit]: WorldEdit for Forge (version 6.1.8) is loaded
  173. [18:15:36] [Server thread/INFO] [FML]: Forge Mod Loader has successfully loaded 18 mods
  174. [18:15:36] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: Preparing level "world"
  175. [18:15:36] [Server thread/INFO] [Sponge]: Checking for worlds that need to be migrated...
  176. [18:15:36] [Server thread/INFO] [Sponge]: No worlds were found in need of migration.
  177. [18:15:36] [Server thread/INFO] [FML]: Injecting existing registry data into this server instance
  178. [18:15:36] [Server thread/INFO] [FML]: Registry Block: Found a missing id from the world props:blockfake
  179. [18:15:36] [Server thread/INFO] [FML]: Registry Block: Found a missing id from the world props:blockprops
  180. [18:15:36] [Server thread/INFO] [FML]: Applying holder lookups
  181. [18:15:36] [Server thread/INFO] [FML]: Holder lookups applied
  182. [18:15:37] [Server thread/INFO] [net.minecraft.advancements.AdvancementList]: Loaded 513 advancements
  183. [18:15:37] [Server thread/INFO] [net.minecraft.advancements.AdvancementList]: Loaded 7 advancement trees
  184. [18:15:37] [Server thread/INFO] [net.minecraft.server.MinecraftServer]: Preparing start region for level 0 (world)
  185. [18:15:37] [Server thread/WARN] [net.minecraft.network.datasync.EntityDataManager]: defineId called for: class com.mrcrayfish.vehicle.entity.EntityPoweredVehicle from class com.mrcrayfish.vehicle.entity.EntityLandVehicle
  186. [18:15:38] [Server thread/INFO] [Sponge]: Loading world [world] (minecraft:overworld/0)
  187. [18:15:38] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: Done (2,036s)! For help, type "help" or "?"
  188. [18:15:38] [Voice Server Process/WARN] [Gliby's Voice Chat Mod]: Minecraft Networking is not recommended and is consider very slow, please setup UDP.
  189. [18:15:38] [Voice Server Process/INFO] [Gliby's Voice Chat Mod]: Started [Minecraft] Server.
  190. [18:16:20] [Netty Server IO #1/INFO] [FML]: Client protocol version 2
  191. [18:16:20] [Netty Server IO #1/INFO] [FML]: Client attempting to join with 16 mods : minecraft@1.12.2,toughasnails@3.1.0.139,ptrmodellib@1.0.3,FML@8.0.99.99,obfuscate@0.2.6,worldedit@6.1.8,mw@1.11.7.5,cfm@6.3.0,snowvariants@1.0.0,vehicle@0.35.0,gvc@@VERSION@,forge@14.23.5.2768,nzsmod@1,phosphor-lighting@1.12.2-0.2.2,mcp@9.42,mobends@0.25
  192. [18:16:20] [Netty Server IO #1/INFO] [FML]: Attempting connection with missing mods [spongeapi, sponge, spongeforge, chestrefill] at CLIENT
  193. [18:16:21] [Server thread/INFO] [FML]: [Server thread] Server side modded connection established
  194. [18:16:21] [Server thread/INFO] [net.minecraft.server.management.PlayerList]: meroxx[/95.83.77.75:57986] logged in with entity id 2 in world(0) at (-485.5, 32.025, -553.5)
  195. [18:16:22] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: meroxx joined the game
  196. [18:16:22] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  197. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  198. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  199. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  200. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  201. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  202. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  203. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  204. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  205. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  206. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  207. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  208. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  209. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  210. [18:16:22] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  211. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  212. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  213. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  214. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  215. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  216. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  217. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  218. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  219. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  220. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  221. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  222. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  223. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  224. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  225. [18:16:22] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  226. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  227. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  228. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  229. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  230. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  231. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  232. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  233. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  234. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  235. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  236. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  237. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  238. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  239. [18:16:22] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  240. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  241. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  242. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  243. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  244. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  245. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  246. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  247. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  248. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  249. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  250. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  251. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  252. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  253. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  254. [18:16:22] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  255. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  256. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  257. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  258. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  259. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  260. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  261. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  262. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  263. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  264. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  265. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  266. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  267. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  268. [18:16:23] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  269. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  270. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  271. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  272. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  273. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  274. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  275. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  276. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  277. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  278. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  279. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  280. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  281. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  282. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  283. [18:16:24] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  284. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  285. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  286. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  287. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  288. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  289. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  290. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  291. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  292. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  293. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  294. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  295. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  296. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  297. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  298. [18:16:24] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  299. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  300. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  301. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  302. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  303. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  304. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  305. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  306. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  307. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  308. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  309. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  310. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  311. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  312. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  313. [18:16:24] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  314. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  315. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  316. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  317. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  318. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  319. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  320. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  321. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  322. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  323. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  324. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  325. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  326. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  327. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  328. [18:16:24] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  329. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  330. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  331. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  332. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  333. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  334. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  335. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  336. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  337. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  338. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  339. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  340. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  341. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  342. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  343. [18:16:25] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  344. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  345. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  346. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  347. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  348. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  349. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  350. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  351. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  352. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  353. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  354. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  355. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  356. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  357. [18:16:25] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  358. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  359. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  360. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  361. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  362. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  363. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  364. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  365. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  366. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  367. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  368. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  369. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  370. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  371. [18:16:26] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  372. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  373. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  374. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  375. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  376. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  377. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  378. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  379. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  380. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  381. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  382. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  383. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  384. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  385. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  386. [18:16:26] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  387. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  388. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  389. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  390. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  391. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  392. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  393. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  394. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  395. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  396. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  397. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  398. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  399. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  400. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  401. [18:16:26] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  402. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  403. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  404. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  405. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  406. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  407. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  408. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  409. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  410. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  411. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  412. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  413. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  414. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  415. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  416. [18:16:27] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  417. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  418. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  419. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  420. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  421. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  422. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  423. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  424. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  425. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  426. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  427. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  428. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  429. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  430. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  431. [18:16:28] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  432. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  433. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  434. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  435. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  436. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  437. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  438. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  439. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  440. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  441. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  442. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  443. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  444. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  445. [18:16:29] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  446. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  447. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  448. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  449. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  450. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  451. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  452. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  453. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  454. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  455. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  456. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  457. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  458. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  459. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  460. [18:16:30] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  461. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  462. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  463. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  464. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  465. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  466. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  467. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  468. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  469. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  470. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  471. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  472. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  473. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  474. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  475. [18:16:30] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  476. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  477. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  478. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  479. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  480. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  481. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  482. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  483. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  484. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  485. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  486. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  487. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  488. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  489. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  490. [18:16:30] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  491. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  492. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  493. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  494. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  495. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  496. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  497. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  498. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  499. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  500. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  501. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  502. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  503. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  504. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  505. [18:16:31] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  506. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  507. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  508. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  509. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  510. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  511. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  512. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  513. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  514. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  515. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  516. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  517. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  518. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  519. [18:16:32] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  520. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  521. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  522. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  523. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  524. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  525. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  526. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  527. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  528. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  529. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  530. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  531. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  532. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  533. [18:16:33] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  534. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  535. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  536. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  537. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  538. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  539. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  540. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  541. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  542. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  543. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  544. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  545. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  546. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  547. [18:16:34] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  548. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  549. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  550. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  551. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  552. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  553. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  554. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  555. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  556. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  557. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  558. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  559. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  560. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  561. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  562. [18:16:34] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  563. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  564. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  565. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  566. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  567. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  568. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  569. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  570. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  571. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  572. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  573. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  574. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  575. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  576. [18:16:36] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  577. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  578. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  579. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  580. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  581. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  582. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  583. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  584. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  585. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  586. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  587. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  588. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  589. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  590. [18:16:39] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  591. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  592. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  593. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  594. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  595. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  596. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  597. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  598. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  599. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  600. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  601. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  602. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  603. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  604. [18:16:39] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  605. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  606. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  607. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  608. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  609. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  610. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  611. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  612. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  613. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  614. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  615. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  616. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  617. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  618. [18:16:39] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  619. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  620. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  621. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  622. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  623. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  624. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  625. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  626. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  627. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  628. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  629. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  630. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  631. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  632. [18:16:40] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  633. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  634. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  635. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  636. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  637. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  638. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  639. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  640. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  641. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  642. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  643. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  644. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  645. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  646. [18:16:40] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  647. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  648. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  649. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  650. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  651. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  652. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  653. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  654. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  655. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  656. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  657. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  658. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  659. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  660. [18:16:40] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  661. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  662. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  663. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  664. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  665. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  666. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  667. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  668. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  669. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  670. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  671. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  672. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  673. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  674. [18:16:41] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  675. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  676. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  677. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  678. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  679. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  680. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  681. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  682. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  683. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  684. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  685. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  686. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  687. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  688. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  689. [18:16:42] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  690. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  691. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  692. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  693. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  694. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  695. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  696. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  697. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  698. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  699. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  700. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  701. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  702. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  703. [18:16:42] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  704. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  705. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  706. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  707. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  708. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  709. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  710. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  711. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  712. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  713. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  714. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  715. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  716. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  717. [18:16:42] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  718. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  719. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  720. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  721. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  722. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  723. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  724. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  725. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  726. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  727. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  728. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  729. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  730. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  731. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  732. [18:16:43] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  733. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  734. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  735. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  736. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  737. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  738. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  739. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  740. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  741. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  742. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  743. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  744. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  745. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  746. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  747. [18:16:43] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  748. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  749. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  750. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  751. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  752. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  753. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  754. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  755. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  756. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  757. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  758. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  759. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  760. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  761. [18:16:43] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  762. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  763. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  764. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  765. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  766. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  767. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  768. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  769. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  770. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  771. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  772. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  773. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  774. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  775. [18:16:44] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  776. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  777. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  778. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  779. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  780. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  781. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  782. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  783. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  784. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  785. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  786. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  787. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  788. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  789. [18:16:44] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  790. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  791. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  792. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  793. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  794. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  795. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  796. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  797. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  798. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  799. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  800. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  801. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  802. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  803. [18:16:44] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  804. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  805. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  806. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  807. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  808. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  809. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  810. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  811. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  812. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  813. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  814. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  815. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  816. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  817. [18:16:44] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  818. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  819. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  820. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  821. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  822. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  823. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  824. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  825. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  826. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  827. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  828. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  829. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  830. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  831. [18:16:44] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  832. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  833. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  834. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  835. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  836. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  837. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  838. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  839. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  840. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  841. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  842. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  843. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  844. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  845. [18:16:45] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  846. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  847. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  848. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  849. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  850. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  851. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  852. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  853. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  854. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  855. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  856. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  857. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  858. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  859. [18:16:45] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  860. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  861. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  862. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  863. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  864. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  865. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  866. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  867. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  868. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  869. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  870. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  871. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  872. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  873. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  874. [18:16:46] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  875. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  876. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  877. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  878. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  879. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  880. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  881. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  882. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  883. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  884. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  885. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  886. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  887. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  888. [18:16:47] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  889. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  890. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  891. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  892. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  893. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  894. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  895. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  896. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  897. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  898. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  899. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  900. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  901. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  902. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  903. [18:16:47] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  904. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  905. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  906. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  907. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  908. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  909. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  910. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  911. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  912. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  913. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  914. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  915. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  916. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  917. [18:16:47] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  918. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  919. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  920. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  921. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  922. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  923. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  924. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  925. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  926. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  927. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  928. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  929. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  930. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  931. [18:16:47] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  932. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  933. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  934. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  935. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  936. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  937. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  938. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  939. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  940. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  941. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  942. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  943. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  944. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  945. [18:16:48] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  946. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  947. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  948. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  949. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  950. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  951. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  952. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  953. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  954. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  955. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  956. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  957. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  958. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  959. [18:16:48] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  960. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  961. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  962. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  963. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  964. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  965. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  966. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  967. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  968. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  969. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  970. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  971. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  972. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  973. [18:16:48] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  974. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  975. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  976. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  977. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  978. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  979. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  980. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  981. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  982. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  983. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  984. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  985. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  986. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  987. [18:16:48] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  988. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  989. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  990. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  991. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  992. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  993. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  994. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  995. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  996. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  997. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  998. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  999. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1000. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1001. [18:16:48] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1002. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1003. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1004. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1005. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1006. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1007. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1008. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1009. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1010. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1011. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1012. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1013. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1014. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1015. [18:16:49] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1016. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1017. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1018. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1019. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1020. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1021. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1022. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1023. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1024. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1025. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1026. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1027. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1028. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1029. [18:16:49] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1030. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1031. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1032. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1033. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1034. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1035. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1036. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1037. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1038. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1039. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1040. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1041. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1042. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1043. [18:16:49] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1044. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1045. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1046. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1047. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1048. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1049. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1050. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1051. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1052. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1053. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1054. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1055. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1056. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1057. [18:16:49] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1058. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1059. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1060. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1061. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1062. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1063. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1064. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1065. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1066. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1067. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1068. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1069. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1070. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1071. [18:16:49] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1072. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1073. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1074. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1075. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1076. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1077. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1078. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1079. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1080. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1081. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1082. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1083. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1084. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1085. [18:16:49] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1086. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1087. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1088. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1089. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1090. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1091. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1092. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1093. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1094. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1095. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1096. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1097. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1098. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1099. [18:16:49] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1100. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1101. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1102. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1103. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1104. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1105. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1106. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1107. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1108. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1109. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1110. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1111. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1112. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1113. [18:16:49] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1114. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1115. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1116. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1117. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1118. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1119. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1120. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1121. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1122. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1123. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1124. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1125. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1126. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1127. [18:16:49] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1128. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1129. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1130. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1131. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1132. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1133. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1134. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1135. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1136. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1137. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1138. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1139. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1140. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1141. [18:16:50] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1142. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1143. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1144. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1145. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1146. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1147. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1148. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1149. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1150. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1151. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1152. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1153. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1154. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1155. [18:16:50] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1156. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1157. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1158. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1159. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1160. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1161. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1162. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1163. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1164. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1165. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1166. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1167. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1168. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1169. [18:16:50] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1170. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1171. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1172. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1173. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1174. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1175. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1176. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1177. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1178. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1179. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1180. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1181. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1182. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1183. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1184. [18:16:50] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1185. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1186. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1187. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1188. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1189. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1190. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1191. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1192. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1193. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1194. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1195. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1196. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1197. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1198. [18:16:50] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1199. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1200. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1201. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1202. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1203. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1204. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1205. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1206. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1207. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1208. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1209. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1210. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1211. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1212. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1213. [18:16:50] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1214. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1215. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1216. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1217. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1218. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1219. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1220. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1221. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1222. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1223. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1224. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1225. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1226. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1227. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1228. [18:16:50] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1229. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1230. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1231. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1232. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1233. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1234. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1235. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1236. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1237. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1238. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1239. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1240. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1241. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1242. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1243. [18:16:51] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1244. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1245. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1246. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1247. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1248. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1249. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1250. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1251. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1252. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1253. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1254. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1255. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1256. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1257. [18:16:51] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1258. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1259. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1260. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1261. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1262. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1263. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1264. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1265. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1266. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1267. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1268. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1269. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1270. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1271. [18:16:51] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1272. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1273. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1274. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1275. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1276. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1277. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1278. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1279. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1280. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1281. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1282. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1283. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1284. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1285. [18:16:51] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1286. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1287. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1288. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1289. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1290. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1291. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1292. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1293. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1294. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1295. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1296. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1297. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1298. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1299. [18:16:53] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1300. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1301. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1302. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1303. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1304. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1305. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1306. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1307. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1308. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1309. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1310. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1311. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1312. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1313. [18:16:53] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1314. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1315. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1316. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1317. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1318. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1319. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1320. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1321. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1322. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1323. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1324. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1325. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1326. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1327. [18:16:55] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1328. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1329. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1330. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1331. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1332. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1333. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1334. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1335. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1336. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1337. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1338. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1339. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1340. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1341. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1342. [18:16:56] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1343. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1344. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1345. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1346. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1347. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1348. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1349. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1350. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1351. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1352. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1353. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1354. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1355. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1356. [18:16:57] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1357. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1358. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1359. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1360. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1361. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1362. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1363. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1364. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1365. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1366. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1367. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1368. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1369. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1370. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1371. [18:16:57] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1372. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1373. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1374. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1375. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1376. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1377. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1378. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1379. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1380. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1381. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1382. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1383. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1384. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1385. [18:16:57] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1386. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1387. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1388. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1389. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1390. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1391. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1392. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1393. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1394. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1395. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1396. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1397. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1398. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1399. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1400. [18:16:57] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1401. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1402. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1403. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1404. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1405. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1406. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1407. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1408. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1409. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1410. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1411. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1412. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1413. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1414. [18:16:58] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1415. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1416. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1417. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1418. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1419. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1420. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1421. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1422. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1423. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1424. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1425. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1426. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1427. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1428. [18:16:58] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1429. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1430. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1431. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1432. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1433. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1434. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1435. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1436. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1437. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1438. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1439. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1440. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1441. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1442. [18:16:58] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1443. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1444. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1445. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1446. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1447. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1448. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1449. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1450. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1451. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1452. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1453. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1454. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1455. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1456. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1457. [18:16:59] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1458. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1459. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1460. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1461. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1462. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1463. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1464. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1465. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1466. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1467. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1468. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1469. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1470. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1471. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1472. [18:16:59] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1473. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1474. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1475. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1476. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1477. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1478. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1479. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1480. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1481. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1482. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1483. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1484. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1485. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1486. [18:16:59] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1487. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1488. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1489. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1490. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1491. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1492. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1493. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1494. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1495. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1496. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1497. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1498. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1499. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1500. [18:16:59] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1501. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1502. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1503. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1504. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1505. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1506. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1507. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1508. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1509. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1510. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1511. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1512. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1513. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1514. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1515. [18:16:59] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1516. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1517. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1518. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1519. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1520. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1521. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1522. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1523. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1524. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1525. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1526. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1527. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1528. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1529. [18:16:59] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1530. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1531. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1532. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1533. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1534. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1535. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1536. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1537. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1538. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1539. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1540. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1541. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1542. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1543. [18:16:59] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1544. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1545. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1546. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1547. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1548. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1549. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1550. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1551. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1552. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1553. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1554. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1555. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1556. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1557. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1558. [18:17:00] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1559. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1560. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1561. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1562. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1563. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1564. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1565. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1566. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1567. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1568. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1569. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1570. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1571. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1572. [18:17:00] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1573. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1574. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1575. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1576. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1577. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1578. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1579. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1580. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1581. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1582. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1583. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1584. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1585. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1586. [18:17:02] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1587. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1588. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1589. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1590. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1591. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1592. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1593. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1594. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1595. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1596. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1597. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1598. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1599. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1600. [18:17:03] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1601. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1602. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1603. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1604. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1605. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1606. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1607. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1608. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1609. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1610. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1611. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1612. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1613. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1614. [18:17:03] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1615. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1616. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1617. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1618. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1619. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1620. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1621. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1622. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1623. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1624. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1625. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1626. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1627. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1628. [18:17:03] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1629. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1630. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1631. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1632. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1633. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1634. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1635. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1636. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1637. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1638. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1639. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1640. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1641. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1642. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1643. [18:17:03] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1644. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1645. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1646. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1647. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1648. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1649. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1650. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1651. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1652. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1653. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1654. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1655. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1656. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1657. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1658. [18:17:03] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1659. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1660. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1661. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1662. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1663. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1664. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1665. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1666. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1667. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1668. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1669. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1670. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1671. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1672. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1673. [18:17:04] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1674. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1675. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1676. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1677. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1678. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1679. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1680. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1681. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1682. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1683. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1684. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1685. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1686. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1687. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1688. [18:17:04] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1689. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1690. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1691. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1692. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1693. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1694. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1695. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1696. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1697. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1698. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1699. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1700. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1701. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1702. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1703. [18:17:05] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1704. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1705. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1706. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1707. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1708. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1709. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1710. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1711. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1712. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1713. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1714. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1715. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1716. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1717. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1718. [18:17:05] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1719. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1720. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1721. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1722. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1723. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1724. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1725. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1726. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1727. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1728. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1729. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1730. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1731. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1732. [18:17:06] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1733. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1734. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1735. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1736. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1737. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1738. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1739. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1740. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1741. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1742. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1743. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1744. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1745. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1746. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1747. [18:17:06] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1748. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1749. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1750. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1751. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1752. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1753. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1754. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1755. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1756. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1757. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1758. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1759. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1760. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1761. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1762. [18:17:06] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1763. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1764. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1765. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1766. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1767. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1768. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1769. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1770. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1771. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1772. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1773. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1774. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1775. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1776. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1777. [18:17:06] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1778. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1779. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1780. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1781. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1782. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1783. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1784. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1785. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1786. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1787. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1788. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1789. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1790. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1791. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1792. [18:17:06] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1793. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1794. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1795. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1796. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1797. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1798. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1799. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1800. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1801. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1802. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1803. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1804. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1805. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1806. [18:17:07] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1807. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1808. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1809. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1810. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1811. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1812. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1813. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1814. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1815. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1816. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1817. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1818. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1819. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1820. [18:17:08] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1821. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1822. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1823. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1824. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1825. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1826. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1827. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1828. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1829. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1830. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1831. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1832. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1833. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1834. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1835. [18:17:09] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1836. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1837. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1838. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1839. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1840. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1841. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1842. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1843. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1844. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1845. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1846. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1847. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1848. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1849. [18:17:09] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1850. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1851. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1852. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1853. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1854. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1855. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1856. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1857. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1858. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1859. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1860. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1861. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1862. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1863. [18:17:10] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1864. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1865. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1866. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1867. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1868. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1869. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1870. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1871. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1872. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1873. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1874. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1875. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1876. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1877. [18:17:10] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1878. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1879. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1880. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1881. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1882. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1883. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1884. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1885. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1886. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1887. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1888. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1889. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1890. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1891. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1892. [18:17:11] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1893. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1894. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1895. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1896. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1897. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1898. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1899. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1900. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1901. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1902. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1903. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1904. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1905. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1906. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1907. [18:17:11] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1908. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1909. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1910. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1911. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1912. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1913. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1914. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1915. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1916. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1917. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1918. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1919. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1920. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1921. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1922. [18:17:11] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1923. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1924. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1925. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1926. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1927. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1928. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1929. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1930. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1931. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1932. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1933. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1934. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1935. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1936. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1937. [18:17:12] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1938. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1939. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1940. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1941. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  1942. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1943. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1944. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1945. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1946. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1947. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1948. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1949. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1950. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1951. [18:17:12] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1952. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1953. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1954. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1955. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1956. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1957. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1958. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1959. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1960. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1961. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1962. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1963. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1964. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1965. [18:17:13] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1966. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1967. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1968. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1969. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1970. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1971. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1972. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1973. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1974. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
  1975. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1976. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1977. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1978. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1979. [18:17:14] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1980. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1981. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1982. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1983. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1984. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  1985. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  1986. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  1987. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  1988. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  1989. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  1990. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  1991. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  1992. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  1993. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  1994. [18:17:14] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  1995. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  1996. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  1997. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  1998. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  1999. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  2000. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  2001. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  2002. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  2003. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  2004. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  2005. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  2006. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  2007. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  2008. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  2009. [18:17:15] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  2010. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  2011. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  2012. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  2013. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
  2014. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  2015. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  2016. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  2017. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  2018. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  2019. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  2020. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  2021. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  2022. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  2023. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  2024. [18:17:15] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  2025. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  2026. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  2027. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  2028. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  2029. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  2030. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  2031. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  2032. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  2033. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  2034. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  2035. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  2036. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
  2037. at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
  2038. at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
  2039. [18:17:16] [Sponge - Async Light Thread/WARN] [Phosphor]: Something (likely another mod) has attempted to modify the world's state from the wrong thread!
  2040. This is *bad practice* and can cause severe issues in your game. Phosphor has done as best as it can to mitigate this violation, but it may negatively impact performance or introduce stalls.
  2041. In a future release, this violation may result in a hard crash instead of the current soft warning. You should report this issue to our issue tracker with the following stacktrace information.
  2042. (If you are aware you have misbehaving mods and cannot resolve this issue, you can safely disable this warning by setting `enable_illegal_thread_access_warnings` to `false` in Phosphor's configuration file for the time being.)
  2043. java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
  2044. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
  2045. at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
  2046. at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
  2047. at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
  2048. at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
  2049. at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
  2050. at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
  2051. at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]