Kicking Players with Java Error (0.2.16) #261
Comments
|
Thank you for the report, I will investigate the issue. |
|
I would like the full latest.log please, debug.log if you have it, and latest.log from one client that was kicked. |
|
Client Log logs.zip |
|
The client log indicates that they are missing mods. Are they on the same version as the server? |
|
Yes both on 0.2.16 |
|
debug-3.log.gz |
|
Does it only happen to some, or all players? |
|
Happened to 4 out of the 5 that were online. The other player wasn’t near our base. The 4 players kicked were all in the same base. Usually happened when a player was interacting with AE2. When it started kicking a lot one player would log on and it immediately kicked closest player.
|
|
Interesting. In a bad way ^^' |
|
Server Logs: |
|
Client |
|
Logged in with my Alt and received same error once more of my base-mates logged in. |
|
Do you happen to have an Enderman spawner at the base? |
|
We do. It is redstone controlable. Will remove it ASAP |
|
Will test tonight (in roughly 12 hours). |
|
No luck. Will try to pick up all spawners. |
|
No luck. |
|
Dammit, I'll dig deeper through the logs tomorrow :) |
|
my small group has that too. it is influenced by where the players are and where they spawn in. It seems to kick out the player in the same chunk, or close to the chunk where the new one spawns in. You may need a world copy to reproduce. |
|
I see fixed in 16.3, do we know the culprit? |
|
Nope not at all, not sure what to do here tbh. |
|
we're near 100% certain its related to the apothesis spawners - after a fresh server restart we only started having issues after using a lever to control spawners that also have the ignore players tag. I do notice that the spawners record a xyz location for redstone control in the NBT, may also impact usability. Curiously though we have one player who is consistently not part of the impacted group, even though they have interacted with spawners and are part of the allies group for the claimed areas. update: we performed a soft restart and that did not resolve the problem once it set in. |
we also began experiencing this once players began moving between dimensions using Mekanism portals, It seems specific to some sort of load check when players enter/spawn into the area. In your world Mike, was it specific to an area, or any areas where certain players loaded? |
|
Yes, close to the chunk that had the storage and ME and mekanism machines
(connected to ME). All this is in just 2 or 3 chunks.
…On Tue, Sep 22, 2020, 1:54 PM corhean ***@***.***> wrote:
my small group has that too. it is influenced by where the players are and
where they spawn in. It seems to kick out the player in the same chunk, or
close to the chunk where the new one spawns in.
It also seem to be related to block updates.
You may need a world copy to reproduce.
we also began experiencing this once players began moving between
dimensions using Mekanism portals, It seems specific to some sort of load
check when players enter/spawn into the area.
In your world Mike, was it specific to an area, or any areas where certain
players loaded?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#261 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABZH5SALQUK3BT3CVGAWGQTSHDQFLANCNFSM4Q7FG7BQ>
.
|
|
I think 0.3.0 will fix this, I can't know for sure though since I can't reproduce it ^^' |
Modpack version
Enigmatica 6 0.2.16
Issue
Kicking users with this error: "[INFO] username lost connection: Internal Exception: io.netty.handler.codec.EncoderException: java.lang.IllegalStateException: LazyOptional is empty or otherwise returned null from getValue() unexpectedly"
Started since 0.2.16 update
Logs
latest.log
The text was updated successfully, but these errors were encountered: