logprot.toml config either does not work or has no effect
Cleista opened this issue · 3 comments
Modpack Version
Enigmatica 6 1.2.1
Describe your issue.
I set logprot.toml to the following:
[Login-settings]
#Time in ticks the logging player is invulnerable, 20 ticks = 1sec. Default is 50secs = 1000 ticks
#Range: 0 ~ 50000
invulnerabilityTime = 12000
#Max distance in blocks(2d) the invulnerability lasts, default: 10
#Range: 1 ~ 200
maxDistance = 2
[debug]
#Wether to enable debug log outputs, default: false
debugLog = falseHowever, users continue to die while loading, sometimes immediately upon login. This is far less than the 10 minutes of invulnerability expected.
logprot is in fact loaded as the following is visible in latest.log
[11May2022 21:21:19.121] [modloading-worker-23/INFO] [com.logprot.Logprot/]: Shields up!
Relevant section of log during player death, occurring ~40 seconds after initial connect:
[11May2022 21:39:08.707] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer/]: TTomoego joined the game
[11May2022 21:39:08.766] [Server thread/INFO] [KubeJS Server/]: server_scripts:enigmatica/kubejs/packmode.js:4: setting mode for player: TTomoego
[11May2022 21:39:08.766] [Server thread/INFO] [KubeJS Server/]: server_scripts:enigmatica/kubejs/packmode.js:7: set mode to expert for player: TTomoego
[11May2022 21:39:08.767] [Server thread/INFO] [se.mickelus.tetra.data.DataManager/]: Sending data to client: TTomoego
[11May2022 21:39:09.405] [Netty Epoll Server IO #21/ERROR] [net.minecraft.command.arguments.ArgumentTypes/]: Could not serialize dev.maxneedssnacks.interactio.command.RegistryArgument@2c0861d0 (class dev.maxneedssnacks.interactio.command.RegistryArgument) - will not be sent to client!
[11May2022 21:39:09.989] [Netty Epoll Server IO #21/ERROR] [net.minecraft.command.arguments.ArgumentTypes/]: Could not serialize dev.maxneedssnacks.interactio.command.RegistryArgument@2c0861d0 (class dev.maxneedssnacks.interactio.command.RegistryArgument) - will not be sent to client!
[11May2022 21:39:10.929] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer/]: <Xyphyria> o/
[11May2022 21:39:51.061] [Server thread/INFO] [dev.quarris.enigmaticgraves.EnigmaticGraves/]: Preparing grave for TTomoego
[11May2022 21:39:51.061] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer/]: TTomoego was slain by Zombie
[11May2022 21:39:51.063] [Server thread/INFO] [dev.quarris.enigmaticgraves.EnigmaticGraves/]: Spawned grave for TTomoego at BlockPos{x=305, y=79, z=13}
[11May2022 21:39:51.063] [Server thread/INFO] [dev.quarris.enigmaticgraves.EnigmaticGraves/]: Added grave entry to player TTomoego
[11May2022 21:39:53.944] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer/]: <Xyphyria> F
[11May2022 21:40:04.385] [JDA MainWS-ReadThread/INFO] [net.minecraft.server.dedicated.DedicatedServer/]: <Tomoego> bruh im in loading
Additional context on the Enigmatica Discord here.
Crash Report
No response
Latest Log
No response
Have you modified the modpack?
No
User Modifications
No response
Did the issue happen in singleplayer or on a server?
Server
Another instance of this occurring, with logprot debug output set to true.
[12May2022 10:00:15.697] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer/]: heawen joined the game
[12May2022 10:00:15.740] [Server thread/INFO] [KubeJS Server/]: server_scripts:enigmatica/kubejs/packmode.js:4: setting mode for player: heawen
[12May2022 10:00:15.740] [Server thread/INFO] [KubeJS Server/]: server_scripts:enigmatica/kubejs/packmode.js:7: set mode to expert for player: heawen
[12May2022 10:00:15.740] [Server thread/INFO] [com.logprot.Logprot/]: Player:heawen now has login protection for 5000 ticks
[12May2022 10:00:15.741] [Server thread/INFO] [se.mickelus.tetra.data.DataManager/]: Sending data to client: heawen
[12May2022 10:00:30.710] [Server thread/INFO] [com.logprot.Logprot/]: Player:heawen got his login protection removed
[12May2022 10:01:06.984] [Server thread/INFO] [dev.quarris.enigmaticgraves.EnigmaticGraves/]: Preparing grave for heawen
[12May2022 10:01:06.984] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer/]: heawen was burnt to a crisp whilst fighting Blaze
[12May2022 10:01:06.987] [Server thread/INFO] [dev.quarris.enigmaticgraves.EnigmaticGraves/]: Spawned grave for heawen at BlockPos{x=299, y=68, z=225}
[12May2022 10:01:06.987] [Server thread/INFO] [dev.quarris.enigmaticgraves.EnigmaticGraves/]: Added grave entry to player heawen
[12May2022 10:01:10.603] [JDA MainWS-ReadThread/INFO] [net.minecraft.server.dedicated.DedicatedServer/]: <Crimson> WHAT
[12May2022 10:01:11.923] [JDA MainWS-ReadThread/INFO] [net.minecraft.server.dedicated.DedicatedServer/]: <Crimson> HOW
[12May2022 10:01:15.875] [JDA MainWS-ReadThread/INFO] [net.minecraft.server.dedicated.DedicatedServer/]: <Crimson> IM LOADING IN
Note that the above player logged in with entity id 30951 at (299.23750001192093, 68.0, 225.31105237035575) and died at the same location, so login protection was not removed due to movement.
