[18:15:13] [main/INFO] [LaunchWrapper]: Loading tweak class name net.minecraftforge.fml.common.launcher.FMLServerTweaker
[18:15:13] [main/INFO] [LaunchWrapper]: Using primary tweak class name net.minecraftforge.fml.common.launcher.FMLServerTweaker
[18:15:13] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.common.launcher.FMLServerTweaker
[18:15:13] [main/INFO] [FML]: Forge Mod Loader version 14.23.5.2838 for Minecraft 1.12.2 loading
[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
[18:15:13] [main/INFO] [FML]: Searching C:\Users\User\Desktop\SERVER\.\mods for mods
[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.
[18:15:13] [main/WARN] [FML]: The coremod weaponlib (com.vicmatskiv.weaponlib.core.WeaponlibCorePlugin) is not signed!
[18:15:13] [main/WARN] [FML]: The coremod ObfuscatePlugin (com.mrcrayfish.obfuscate.asm.ObfuscatePlugin) is not signed!
[18:15:13] [main/INFO] [FML]: Loading tweaker org.spongepowered.asm.launch.MixinTweaker from spongeforge-1.12.2-2825-7.1.6.jar
[18:15:13] [main/INFO] [FML]: Loading tweaker org.spongepowered.asm.launch.MixinTweaker from phosphor-1.12.2-0.2.2+build43-universal.jar
[18:15:13] [main/INFO] [LaunchWrapper]: Loading tweak class name net.minecraftforge.fml.common.launcher.FMLInjectionAndSortingTweaker
[18:15:13] [main/INFO] [LaunchWrapper]: Loading tweak class name org.spongepowered.asm.launch.MixinTweaker
[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
[18:15:13] [main/WARN] [FML]: The coremod SpongeCoremod (org.spongepowered.mod.SpongeCoremod) is not signed!
[18:15:13] [main/INFO] [mixin]: Compatibility level set to JAVA_8
[18:15:13] [main/INFO] [mixin]: Adding new token provider org.spongepowered.mod.SpongeCoremod$TokenProvider to MixinEnvironment[DEFAULT]
[18:15:13] [main/INFO] [mixin]: Adding new token provider org.spongepowered.mod.SpongeCoremod$TokenProvider to MixinEnvironment[PREINIT]
[18:15:13] [main/INFO] [mixin]: Adding new token provider org.spongepowered.mod.SpongeCoremod$TokenProvider to MixinEnvironment[INIT]
[18:15:13] [main/WARN] [LaunchWrapper]: Tweak class name org.spongepowered.asm.launch.MixinTweaker has already been visited -- skipping
[18:15:13] [main/INFO] [LaunchWrapper]: Loading tweak class name net.minecraftforge.fml.common.launcher.FMLDeobfTweaker
[18:15:13] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.common.launcher.FMLInjectionAndSortingTweaker
[18:15:13] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.common.launcher.FMLInjectionAndSortingTweaker
[18:15:13] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.relauncher.CoreModManager$FMLPluginWrapper
[18:15:14] [main/INFO] [FML]: Found valid fingerprint for Minecraft Forge. Certificate fingerprint e3c3d50c7c986df74c645c0ac54639741c90a557
[18:15:14] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.relauncher.CoreModManager$FMLPluginWrapper
[18:15:14] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.relauncher.CoreModManager$FMLPluginWrapper
[18:15:14] [main/INFO] [LaunchWrapper]: Calling tweak class org.spongepowered.asm.launch.MixinTweaker
[18:15:14] [main/INFO] [mixin]: Initialised Mixin FML Remapper Adapter with net.minecraftforge.fml.common.asm.transformers.deobf.FMLDeobfuscatingRemapper@383f1975
[18:15:14] [main/INFO] [Phosphor Forge Core]: Phosphor has been hooked by Forge, setting up Mixin and plugins
[18:15:14] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.common.launcher.FMLDeobfTweaker
[18:15:15] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.relauncher.CoreModManager$FMLPluginWrapper
[18:15:15] [main/INFO] [LaunchWrapper]: Loading tweak class name net.minecraftforge.fml.common.launcher.TerminalTweaker
[18:15:15] [main/INFO] [LaunchWrapper]: Loading tweak class name org.spongepowered.asm.mixin.EnvironmentStateTweaker
[18:15:15] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.common.launcher.TerminalTweaker
[18:15:15] [main/INFO] [LaunchWrapper]: Calling tweak class org.spongepowered.asm.mixin.EnvironmentStateTweaker
[18:15:15] [main/INFO] [Phosphor Plugin]: Loading configuration
[18:15:15] [main/INFO] [Phosphor Plugin]: Sponge has been detected on the classpath! Sponge mixins will be used.
[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.
[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
[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.
[18:15:19] [main/INFO] [LaunchWrapper]: Launching wrapped minecraft {net.minecraft.server.MinecraftServer}
[18:15:24] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: Starting minecraft server version 1.12.2
[18:15:24] [Server thread/INFO] [FML]: MinecraftForge v14.23.5.2838 Initialized
[18:15:24] [Server thread/INFO] [FML]: Starts to replace vanilla recipe ingredients with ore ingredients.
[18:15:24] [Server thread/INFO] [FML]: Invalid recipe found with multiple oredict ingredients in the same ingredient...
[18:15:24] [Server thread/INFO] [FML]: Replaced 1227 ore ingredients
[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
[18:15:24] [Server thread/INFO] [Sponge]: Creating injector in stage 'PRODUCTION'
[18:15:27] [Server thread/INFO] [FML]: Searching C:\Users\User\Desktop\SERVER\.\mods for mods
[18:15:27] [Server thread/INFO] [FML]: Forge Mod Loader has identified 18 mods to load
[18:15:27] [Server thread/WARN] [FML]: Missing English translation for FML: assets/fml/lang/en_us.lang
[18:15:27] [Server thread/WARN] [FML]: Missing English translation for spongeapi: assets/spongeapi/lang/en_us.lang
[18:15:27] [Server thread/WARN] [FML]: Missing English translation for spongeforge: assets/spongeforge/lang/en_us.lang
[18:15:27] [Server thread/WARN] [FML]: Missing English translation for chestrefill: assets/chestrefill/lang/en_us.lang
[18:15:27] [Server thread/WARN] [FML]: Missing English translation for snowvariants: assets/snowvariants/lang/en_us.lang
[18:15:27] [Server thread/WARN] [FML]: Missing English translation for worldedit: assets/worldedit/lang/en_us.lang
[18:15:27] [Server thread/WARN] [FML]: Missing English translation for phosphor-lighting: assets/phosphor-lighting/lang/en_us.lang
[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.
[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.
[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
[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
[18:15:28] [Server thread/WARN] [Sponge]: There's no certificate fingerprint available
[18:15:28] [Server thread/INFO] [FML]: Processing ObjectHolder annotations
[18:15:28] [Server thread/INFO] [FML]: Found 1199 ObjectHolder annotations
[18:15:28] [Server thread/INFO] [FML]: Identifying ItemStackHolder annotations
[18:15:28] [Server thread/INFO] [FML]: Found 0 ItemStackHolder annotations
[18:15:28] [Server thread/INFO] [FML]: Configured a dormant chunk cache size of 0
[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
[18:15:29] [Forge Version Check/INFO] [forge.VersionCheck]: [spongeforge] Found status: OUTDATED Target: 7.1.2
[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
[18:15:30] [Forge Version Check/INFO] [forge.VersionCheck]: [forge] Found status: AHEAD Target: null
[18:15:30] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment M6Gscope
[18:15:30] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment MA5Dcover
[18:15:30] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment Maxim9cover
[18:15:30] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment DMRscope
[18:15:30] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment BR55scope
[18:15:30] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment G36Scope
[18:15:30] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment AUGScope
[18:15:30] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment SRS99S5scope
[18:15:30] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment PythonClip
[18:15:31] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment MA37Mag
[18:15:31] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment MA5Dmag
[18:15:31] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment BR55mag
[18:15:31] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment M395Bmag
[18:15:31] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment SRS99S5mag
[18:15:31] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.AttachmentBuilder:build:298]: !!!No recipe defined for attachment M6Gmag
[18:15:33] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.Weapon$Builder:build:735]: !!!No recipe defined for weapon MA37
[18:15:33] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.Weapon$Builder:build:735]: !!!No recipe defined for weapon MA5D
[18:15:33] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.Weapon$Builder:build:735]: !!!No recipe defined for weapon M395B
[18:15:33] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.Weapon$Builder:build:735]: !!!No recipe defined for weapon SRS99S5
[18:15:33] [Server thread/INFO] [STDERR]: [com.vicmatskiv.weaponlib.Weapon$Builder:build:735]: !!!No recipe defined for weapon BR55
[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.
[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
[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
[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
[18:15:34] [Server thread/WARN] [Sponge]: Could not find pipe_down owning class, assigning fallback id: vehicle:block_fluid_pipe_pipe_down
[18:15:34] [Server thread/WARN] [Sponge]: Could not find pipe_east owning class, assigning fallback id: vehicle:block_fluid_pipe_pipe_east
[18:15:34] [Server thread/WARN] [Sponge]: Could not find pipe_north owning class, assigning fallback id: vehicle:block_fluid_pipe_pipe_north
[18:15:34] [Server thread/WARN] [Sponge]: Could not find pipe_south owning class, assigning fallback id: vehicle:block_fluid_pipe_pipe_south
[18:15:34] [Server thread/WARN] [Sponge]: Could not find pipe_up owning class, assigning fallback id: vehicle:block_fluid_pipe_pipe_up
[18:15:34] [Server thread/WARN] [Sponge]: Could not find pipe_west owning class, assigning fallback id: vehicle:block_fluid_pipe_pipe_west
[18:15:34] [Server thread/INFO] [FML]: Applying holder lookups
[18:15:34] [Server thread/INFO] [FML]: Holder lookups applied
[18:15:34] [Server thread/INFO] [FML]: Applying holder lookups
[18:15:34] [Server thread/INFO] [FML]: Holder lookups applied
[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.
[18:15:34] [Server thread/INFO] [FML]: Applying holder lookups
[18:15:34] [Server thread/INFO] [FML]: Holder lookups applied
[18:15:34] [Server thread/INFO] [FML]: Applying holder lookups
[18:15:34] [Server thread/INFO] [FML]: Holder lookups applied
[18:15:34] [Server thread/INFO] [FML]: Injecting itemstacks
[18:15:34] [Server thread/INFO] [FML]: Itemstack injection complete
[18:15:34] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: Loading properties
[18:15:34] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: Default game type: SURVIVAL
[18:15:34] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: Generating keypair
[18:15:34] [pool-4-thread-1/INFO] [Gliby's Voice Chat Mod]: Mod is up-to-date.
[18:15:34] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: Starting Minecraft server on *:25565
[18:15:34] [Server thread/INFO] [net.minecraft.network.NetworkSystem]: Using default channel type
[18:15:34] [Server thread/WARN] [net.minecraft.server.dedicated.DedicatedServer]: **** SERVER IS RUNNING IN OFFLINE/INSECURE MODE!
[18:15:34] [Server thread/WARN] [net.minecraft.server.dedicated.DedicatedServer]: The server will make no attempt to authenticate usernames. Beware.
[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.
[18:15:34] [Server thread/WARN] [net.minecraft.server.dedicated.DedicatedServer]: To change this, set "online-mode" to "true" in the server.properties file.
[18:15:34] [Server thread/INFO] [FML]: Applying holder lookups
[18:15:34] [Server thread/INFO] [FML]: Holder lookups applied
[18:15:34] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: [CR] Chest Refill is loading... :D
[18:15:34] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: [CR] Initializing commands...
[18:15:34] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: [CR] Initializing listeners...
[18:15:34] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: [CR] Chest Refill is ready!
[18:15:35] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: [CR] You are using the latest version!
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[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.
[18:15:35] [Server thread/INFO] [FML]: Injecting itemstacks
[18:15:35] [Server thread/INFO] [FML]: Itemstack injection complete
[18:15:36] [Server thread/INFO] [worldedit]: WorldEdit for Forge (version 6.1.8) is loaded
[18:15:36] [Server thread/INFO] [FML]: Forge Mod Loader has successfully loaded 18 mods
[18:15:36] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: Preparing level "world"
[18:15:36] [Server thread/INFO] [Sponge]: Checking for worlds that need to be migrated...
[18:15:36] [Server thread/INFO] [Sponge]: No worlds were found in need of migration.
[18:15:36] [Server thread/INFO] [FML]: Injecting existing registry data into this server instance
[18:15:36] [Server thread/INFO] [FML]: Registry Block: Found a missing id from the world props:blockfake
[18:15:36] [Server thread/INFO] [FML]: Registry Block: Found a missing id from the world props:blockprops
[18:15:36] [Server thread/INFO] [FML]: Applying holder lookups
[18:15:36] [Server thread/INFO] [FML]: Holder lookups applied
[18:15:37] [Server thread/INFO] [net.minecraft.advancements.AdvancementList]: Loaded 513 advancements
[18:15:37] [Server thread/INFO] [net.minecraft.advancements.AdvancementList]: Loaded 7 advancement trees
[18:15:37] [Server thread/INFO] [net.minecraft.server.MinecraftServer]: Preparing start region for level 0 (world)
[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
[18:15:38] [Server thread/INFO] [Sponge]: Loading world [world] (minecraft:overworld/0)
[18:15:38] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: Done (2,036s)! For help, type "help" or "?"
[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.
[18:15:38] [Voice Server Process/INFO] [Gliby's Voice Chat Mod]: Started [Minecraft] Server.
[18:16:20] [Netty Server IO #1/INFO] [FML]: Client protocol version 2
[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
[18:16:20] [Netty Server IO #1/INFO] [FML]: Attempting connection with missing mods [spongeapi, sponge, spongeforge, chestrefill] at CLIENT
[18:16:21] [Server thread/INFO] [FML]: [Server thread] Server side modded connection established
[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)
[18:16:22] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: meroxx joined the game
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4805) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 60)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_191]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_191]
[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!
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.
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.
(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.)
java.lang.IllegalAccessException: World is owned by 'Server thread' (ID: 21), but was accessed from thread 'Sponge - Async Light Thread' (ID: 61)
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.acquireLock(LightingEngine.java:201) ~[LightingEngine.class:?]
at me.jellysquid.mods.phosphor.mod.world.lighting.LightingEngine.processLightUpdatesForType(LightingEngine.java:180) ~[LightingEngine.class:?]
at net.minecraft.world.chunk.Chunk.func_177413_a(Chunk.java:4800) ~[axw.class:?]
at net.minecraft.world.WorldServer.getLightForAsync(WorldServer.java:5038) ~[oo.class:?]
at net.minecraft.world.WorldServer.getRawBlockLightAsync(WorldServer.java:5069) ~[oo.class:?]
at net.minecraft.world.WorldServer.checkLightAsync(WorldServer.java:4806) ~[oo.class:?]
at net.minecraft.world.WorldServer.lambda$updateLightAsync$0(WorldServer.java:4990) ~[oo.class:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_191]