ForceSpawnLocOnJoin ignored when SaveQuitLocation is true after full Quit (re-join) #274
Description
What behaviour is observed?
When a player fully disconnects (Quit) and joins back, AuthMe restores their last position on the Arena world after login. The ForceSpawnLocOnJoin feature seems to be ignored or overridden by SaveQuitLocation during a fresh session join. Interestingly, the feature works perfectly fine when using the /logout command without leaving the server.
Expected behaviour
Even when SaveQuitLocation is set to true, the ForceSpawnLocOnJoin feature should take priority when a player logs in on a blacklisted world.
If a player joins and authenticates on a world listed in ForceSpawnLocOnJoin.worlds, they should be forced to the spawn point regardless of whether they fully disconnected or just used /logout.
To Reproduce
Steps to reproduce the behavior:
Set SaveQuitLocation: true and teleportUnAuthedToSpawn: true in AuthMe config.
Add world Arena to the ForceSpawnLocOnJoin worlds list.
Log in to the server and go to the Arena world.
Use the /logout command — observe that you are correctly moved to spawn.
Log back in while still on the server — observe that you are correctly kept at spawn (correct behavior).
Go back to the Arena world and fully disconnect from the server (Quit game).
Reconnect to the server and log in.
See error: Instead of being forced to spawn, the player is restored to their last position on the Arena world.
Plugin list
Server Implementation
Standalone(Spigot)
Database Implementation
SQLite
AuthMe Version
AuthMe-5.7.0 build: 2642
Error log (if applicable)
Paper version 1.21.10-129-ver