What Was Changed:
- A scheduled task that attempted to check if a player was online after a delay (in onPlayerQuit) was causing a NullPointerException because the player object could become null after disconnecting.
How It Was Fixed:
- The logic was updated to safely handle the case when the player is no longer online or has already been fully removed from the server.
- Specifically, before checking whether the player is online, it now verifies that the player object is not null.
Why It Matters:
- Prevents a crash that occurs when calling methods on a null reference.
- Improves overall plugin stability during delayed session cleanup routines.
- Aligns with safe practices when working with Bukkit’s player API, especially in asynchronous or delayed environments.
