mirror of
https://github.com/DorkSquadRR/DorkNet.git
synced 2026-10-25 23:18:44 -07:00
fix: open the sign-in page instead of creating a new account on a fresh client
With no remembered account, the 2023 title screen creates a brand-new account (grant_type create_account). On a server with sign-ups off that fails and the title screen retries forever. PC (ClientMod) and Quest now open the sign-in page instead, so players log into their existing DorkNet account. AutoCreateAccount = true keeps Rec Room's behaviour. Also replaces a literal NUL byte in the Quest config loader with '\0'.
This commit is contained in:
@@ -55,6 +55,17 @@ an account, never matched by the cached-login lookup
|
||||
players are keyed by `deviceId` alone, exactly like the PC Steam-emulator path.
|
||||
A real Meta platform id (the Meta build) still tags and lists normally.
|
||||
|
||||
Because the placeholder never lists a remembered account, the title screen
|
||||
would normally create a new account on every fresh headset. With
|
||||
`AutoCreateAccount = false` (the default) the hook library opens the sign-in
|
||||
page instead, so players log into their existing DorkNet account; set it to
|
||||
`true` only on a server that allows sign-ups.
|
||||
|
||||
On a headset that reaches Meta, the Oculus platform also refuses the
|
||||
"logged-in user" request for the renamed app ("Unable to load Oculus user
|
||||
account"). The no-Meta build passes that refusal and hands the game the same
|
||||
placeholder user id `1`.
|
||||
|
||||
Thanks to [RecFlare](https://github.com/recflare) for documenting this
|
||||
pitfall in their Quest client notes.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user