Skip to content

[v3] fix: make AuthMe's Microsoft login-wall skip opt-in - #68

Open
monikon22 wants to merge 2 commits into
Drownek:v3-devfrom
monikon22:fix/65-authme-microsoft-login-wall
Open

[v3] fix: make AuthMe's Microsoft login-wall skip opt-in#68
monikon22 wants to merge 2 commits into
Drownek:v3-devfrom
monikon22:fix/65-authme-microsoft-login-wall

Conversation

@monikon22

Copy link
Copy Markdown
Contributor

Related to #65.

onPlayerCreate had if (account.auth === 'microsoft') return;, skipping the login/register handshake for every Microsoft account unconditionally. That assumed AuthMe never gates a premium account — a server-config decision, not something derivable from account.auth. #65's log shows the opposite: a microsoft account got prompted to /register like any offline one, and the plugin never answered it because it had already returned.

Added skipOnMicrosoftAccount (default false). With it off, Microsoft accounts now go through the same register/login/session-resumed poll as any other account, which means they need a password too — accounts { microsoft { ... } } never carries one (mineflayer authenticates the account itself; AuthMe is a separate wall). Set the plugin's password option for that, or skipOnMicrosoftAccount = true once you've confirmed a given server really does let premium accounts through without one.

Also updated README.md and the docs/plugins.mdx example — both stated the old assumption as fact.

account.auth === 'microsoft' unconditionally skipped the login/register
handshake, assuming AuthMe never prompts premium accounts. That's a
server-config decision, not something derivable from the account type
(issue Drownek#65: a microsoft account got prompted to /register like any
other). Add skipOnMicrosoftAccount (default false) to opt back into the
old shortcut once you've confirmed your server doesn't gate premium
accounts.
README and the plugins.mdx example both stated it as fact; document
skipOnMicrosoftAccount instead and fix the example hook.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant