Premium User keeping getting detected as Offline.

[Len-Github]

Environment

• Minecraft Version: 1.21.1[cite: 1]
• Mod Loader: NeoForge (21.1.235)[cite: 1]
• TrueUUID Version: 1.2.0[cite: 1]
• Server Setup: online-mode=false with TrueUUID enabled on both server and client.

Issue Description

A legitimate premium Minecraft player (mybloodyvalentie) is consistently detected as non-premium and forced into offline fallback mode upon joining the server.

While other premium users authenticate fine, this specific player receives the following message in chat immediately upon joining:
[TrueUUID] Offline fallback accepted. This account was not premium-verified.

Key Log Findings

1. Client launches with an official Microsoft account, passing valid profile UUID (62377299e4d94510a84078f70943295b)[cite: 1].
2. Discord server relay/skin bots successfully fetch and display the player's official Mojang skin.
3. Player can successfully connect to strict online-mode=true servers without issues.
4. On our server, TrueUUID does not wait for a timeout (~30s); the offline fallback triggers within ~10 seconds of connection[cite: 1].
5. Noticeable config warning in client log during startup:
   [WARN] [com.iafenvoy.jupiter.Jupiter/]: Cannot find suitable entry for key=timeoutMs, type=java.lang.Long in config=trueuuid:COMMON[cite: 1]

Troubleshooting Attempted (Unsuccessful)

• Verified matching trueuuid-1.2.0-neoforge-1.21.1.jar is installed in client mods folder[cite: 1].
• Refreshed Microsoft/CurseForge launcher credentials (logged out & back in).
• Checked Windows hosts file for Mojang domain redirects (none found).
• Purged player entries from server usercache.json and ran /trueuuid cleanupuuid while server was stopped.
• Deleted local client trueuuid-common.toml config to force regeneration.
• Verified Windows system clock synchronization.

Attached Logs

(Attach sanitized latest.log file here)

latest.txt

[Len-Github]

Please keep in mind this only happens to that specified player, no other premium user has this problem

[F1xGOD]

interesting... did you try different premium account on same launcher and version?

[F1xGOD]

also this log does not look complete, and i preferably need both, server and client logs

[F1xGOD]

i am not against AI, but i would like to have a complete valid log, thanks

[F1xGOD]

Also, the timeoutMs warning you quoted is not in this file

[F1xGOD]

i've looked through, however this seems to be a client side issue, not a real code regression that can be fixed, id be happy to investigate further if you provide complete server and client logs (you can use self test local premium client, contained sh script in repo)