- Update dependencies
- Use blocking queue for Tick.asyncTasksQueue
- Do not call removed method Thread#stop in Tick#waitAndKillThreads
- Use virtual threads for ClientConnection
- Add build action
Signed-off-by: Joshua Castle <26531652+Kas-tle@users.noreply.github.com>
Addresses comments from https://github.com/LOOHP/Limbo/pull/57#issuecomment-1304543589
In particular:
* Functionality now matches other server types
* only enforce the allowlist if a new "enforce-allowlist"
boolean in server.properties is set to true
* Loads and process the allowlist only once when the server starts (or
the reload command is executed), instead of every time a user connects.
* Add a new command & associated permissions "allowlist reload"
to reload the allowlist
"Incorrect Payload Received in KeepAlive packet for player"
The problem is that in my setup (described in the issue linked above)
the loohp-limbo server is receiving an unsolicited PacketInKeepAlive
message prior to sending any out. This causes the payload validation
check to fail, resulting in the connection then being closed.
This commit changes the PacketInKeepAlive handler to ignore (other than
logging) unsolicited KeepAlive messages rather than act on them.
Possibly the logging is a bad idea unless it's limited to being
suppressed via a debug flag...