[v3] fix: fall back to login when the AuthMe reconnect prompt never arrives by monikon22 · Pull Request #60 · Drownek/plugwright

monikon22 · 2026-08-28T11:52:15Z

Closes#57.

A pool account reconnecting sometimes gets no login/register prompt at all — AuthMe stays silent, and the plugin burned its full 15s timeout waiting for something that was never coming. One missed prompt failed the whole connection, and on v3-dev that stranded the bot online, so the next test got kicked with "already playing" and the failure cascaded through the rest of the run.

The plugin now catches that timeout and assumes login (never registration — a silent reconnect can only happen to an account that already exists), then sends /login anyway. successPattern and authenticatedPattern already match "already logged in" as a substring, so if AuthMe considers the session still active, the extra command just gets accepted instead of leaving the bot stuck.

Root cause of the missing prompt itself is still open — this only stops it from taking the rest of the run down with it.

Verified on both stands (example_plugin, feat/53-serial-identity → this branch):

plugwrightTestLocal: 50/50 pass
plugwrightTestStand (hand-started server, same as [v3] AuthMe login prompt sometimes never arrives when a pool account reconnects #57's repro): 44/44 pass, 6 skip — 0 fail, vs. 2 failed in the run that surfaced [v3] AuthMe login prompt sometimes never arrives when a pool account reconnects #57

AuthMe sometimes sends no login/register prompt at all when a pool account reconnects, so the plugin waited out its full timeout and failed the whole test even though the server would have accepted a plain /login. Catch that timeout and assume login (never registration -- a silent reconnect can only happen to an account that already exists). The existing success/authenticated patterns already match "already logged in", so a stale session on the server just costs one extra command instead of stranding the bot online for the rest of the run. ClosesDrownek#57

monikon22 · 2026-08-28T11:52:15Z

Closes#57.

A pool account reconnecting sometimes gets no login/register prompt at all — AuthMe stays silent, and the plugin burned its full 15s timeout waiting for something that was never coming. One missed prompt failed the whole connection, and on v3-dev that stranded the bot online, so the next test got kicked with "already playing" and the failure cascaded through the rest of the run.

The plugin now catches that timeout and assumes login (never registration — a silent reconnect can only happen to an account that already exists), then sends /login anyway. successPattern and authenticatedPattern already match "already logged in" as a substring, so if AuthMe considers the session still active, the extra command just gets accepted instead of leaving the bot stuck.

Root cause of the missing prompt itself is still open — this only stops it from taking the rest of the run down with it.

Verified on both stands (example_plugin, feat/53-serial-identity → this branch):

plugwrightTestLocal: 50/50 pass
plugwrightTestStand (hand-started server, same as [v3] AuthMe login prompt sometimes never arrives when a pool account reconnects #57's repro): 44/44 pass, 6 skip — 0 fail, vs. 2 failed in the run that surfaced [v3] AuthMe login prompt sometimes never arrives when a pool account reconnects #57

AuthMe sometimes sends no login/register prompt at all when a pool account reconnects, so the plugin waited out its full timeout and failed the whole test even though the server would have accepted a plain /login. Catch that timeout and assume login (never registration -- a silent reconnect can only happen to an account that already exists). The existing success/authenticated patterns already match "already logged in", so a stale session on the server just costs one extra command instead of stranding the bot online for the rest of the run. ClosesDrownek#57

monikon22 · 2026-08-28T11:52:15Z

Closes#57.

A pool account reconnecting sometimes gets no login/register prompt at all — AuthMe stays silent, and the plugin burned its full 15s timeout waiting for something that was never coming. One missed prompt failed the whole connection, and on v3-dev that stranded the bot online, so the next test got kicked with "already playing" and the failure cascaded through the rest of the run.

The plugin now catches that timeout and assumes login (never registration — a silent reconnect can only happen to an account that already exists), then sends /login anyway. successPattern and authenticatedPattern already match "already logged in" as a substring, so if AuthMe considers the session still active, the extra command just gets accepted instead of leaving the bot stuck.

Root cause of the missing prompt itself is still open — this only stops it from taking the rest of the run down with it.

Verified on both stands (example_plugin, feat/53-serial-identity → this branch):

plugwrightTestLocal: 50/50 pass
plugwrightTestStand (hand-started server, same as [v3] AuthMe login prompt sometimes never arrives when a pool account reconnects #57's repro): 44/44 pass, 6 skip — 0 fail, vs. 2 failed in the run that surfaced [v3] AuthMe login prompt sometimes never arrives when a pool account reconnects #57

AuthMe sometimes sends no login/register prompt at all when a pool account reconnects, so the plugin waited out its full timeout and failed the whole test even though the server would have accepted a plain /login. Catch that timeout and assume login (never registration -- a silent reconnect can only happen to an account that already exists). The existing success/authenticated patterns already match "already logged in", so a stale session on the server just costs one extra command instead of stranding the bot online for the rest of the run. ClosesDrownek#57

monikon22 · 2026-08-28T11:52:15Z

Closes#57.

A pool account reconnecting sometimes gets no login/register prompt at all — AuthMe stays silent, and the plugin burned its full 15s timeout waiting for something that was never coming. One missed prompt failed the whole connection, and on v3-dev that stranded the bot online, so the next test got kicked with "already playing" and the failure cascaded through the rest of the run.

The plugin now catches that timeout and assumes login (never registration — a silent reconnect can only happen to an account that already exists), then sends /login anyway. successPattern and authenticatedPattern already match "already logged in" as a substring, so if AuthMe considers the session still active, the extra command just gets accepted instead of leaving the bot stuck.

Root cause of the missing prompt itself is still open — this only stops it from taking the rest of the run down with it.

Verified on both stands (example_plugin, feat/53-serial-identity → this branch):

plugwrightTestLocal: 50/50 pass
plugwrightTestStand (hand-started server, same as [v3] AuthMe login prompt sometimes never arrives when a pool account reconnects #57's repro): 44/44 pass, 6 skip — 0 fail, vs. 2 failed in the run that surfaced [v3] AuthMe login prompt sometimes never arrives when a pool account reconnects #57

AuthMe sometimes sends no login/register prompt at all when a pool account reconnects, so the plugin waited out its full timeout and failed the whole test even though the server would have accepted a plain /login. Catch that timeout and assume login (never registration -- a silent reconnect can only happen to an account that already exists). The existing success/authenticated patterns already match "already logged in", so a stale session on the server just costs one extra command instead of stranding the bot online for the rest of the run. ClosesDrownek#57

monikon22 · 2026-08-28T11:52:15Z

Closes#57.

A pool account reconnecting sometimes gets no login/register prompt at all — AuthMe stays silent, and the plugin burned its full 15s timeout waiting for something that was never coming. One missed prompt failed the whole connection, and on v3-dev that stranded the bot online, so the next test got kicked with "already playing" and the failure cascaded through the rest of the run.

The plugin now catches that timeout and assumes login (never registration — a silent reconnect can only happen to an account that already exists), then sends /login anyway. successPattern and authenticatedPattern already match "already logged in" as a substring, so if AuthMe considers the session still active, the extra command just gets accepted instead of leaving the bot stuck.

Root cause of the missing prompt itself is still open — this only stops it from taking the rest of the run down with it.

Verified on both stands (example_plugin, feat/53-serial-identity → this branch):

plugwrightTestLocal: 50/50 pass
plugwrightTestStand (hand-started server, same as [v3] AuthMe login prompt sometimes never arrives when a pool account reconnects #57's repro): 44/44 pass, 6 skip — 0 fail, vs. 2 failed in the run that surfaced [v3] AuthMe login prompt sometimes never arrives when a pool account reconnects #57

AuthMe sometimes sends no login/register prompt at all when a pool account reconnects, so the plugin waited out its full timeout and failed the whole test even though the server would have accepted a plain /login. Catch that timeout and assume login (never registration -- a silent reconnect can only happen to an account that already exists). The existing success/authenticated patterns already match "already logged in", so a stale session on the server just costs one extra command instead of stranding the bot online for the rest of the run. ClosesDrownek#57

monikon22 · 2026-08-28T11:52:15Z

Closes#57.

A pool account reconnecting sometimes gets no login/register prompt at all — AuthMe stays silent, and the plugin burned its full 15s timeout waiting for something that was never coming. One missed prompt failed the whole connection, and on v3-dev that stranded the bot online, so the next test got kicked with "already playing" and the failure cascaded through the rest of the run.

The plugin now catches that timeout and assumes login (never registration — a silent reconnect can only happen to an account that already exists), then sends /login anyway. successPattern and authenticatedPattern already match "already logged in" as a substring, so if AuthMe considers the session still active, the extra command just gets accepted instead of leaving the bot stuck.

Root cause of the missing prompt itself is still open — this only stops it from taking the rest of the run down with it.

Verified on both stands (example_plugin, feat/53-serial-identity → this branch):

plugwrightTestLocal: 50/50 pass
plugwrightTestStand (hand-started server, same as [v3] AuthMe login prompt sometimes never arrives when a pool account reconnects #57's repro): 44/44 pass, 6 skip — 0 fail, vs. 2 failed in the run that surfaced [v3] AuthMe login prompt sometimes never arrives when a pool account reconnects #57

AuthMe sometimes sends no login/register prompt at all when a pool account reconnects, so the plugin waited out its full timeout and failed the whole test even though the server would have accepted a plain /login. Catch that timeout and assume login (never registration -- a silent reconnect can only happen to an account that already exists). The existing success/authenticated patterns already match "already logged in", so a stale session on the server just costs one extra command instead of stranding the bot online for the rest of the run. ClosesDrownek#57

monikon22 · 2026-08-28T11:52:15Z

Closes#57.

A pool account reconnecting sometimes gets no login/register prompt at all — AuthMe stays silent, and the plugin burned its full 15s timeout waiting for something that was never coming. One missed prompt failed the whole connection, and on v3-dev that stranded the bot online, so the next test got kicked with "already playing" and the failure cascaded through the rest of the run.

The plugin now catches that timeout and assumes login (never registration — a silent reconnect can only happen to an account that already exists), then sends /login anyway. successPattern and authenticatedPattern already match "already logged in" as a substring, so if AuthMe considers the session still active, the extra command just gets accepted instead of leaving the bot stuck.

Root cause of the missing prompt itself is still open — this only stops it from taking the rest of the run down with it.

Verified on both stands (example_plugin, feat/53-serial-identity → this branch):

plugwrightTestLocal: 50/50 pass
plugwrightTestStand (hand-started server, same as [v3] AuthMe login prompt sometimes never arrives when a pool account reconnects #57's repro): 44/44 pass, 6 skip — 0 fail, vs. 2 failed in the run that surfaced [v3] AuthMe login prompt sometimes never arrives when a pool account reconnects #57

AuthMe sometimes sends no login/register prompt at all when a pool account reconnects, so the plugin waited out its full timeout and failed the whole test even though the server would have accepted a plain /login. Catch that timeout and assume login (never registration -- a silent reconnect can only happen to an account that already exists). The existing success/authenticated patterns already match "already logged in", so a stale session on the server just costs one extra command instead of stranding the bot online for the rest of the run. ClosesDrownek#57

monikon22 · 2026-08-28T11:52:15Z

Closes#57.

A pool account reconnecting sometimes gets no login/register prompt at all — AuthMe stays silent, and the plugin burned its full 15s timeout waiting for something that was never coming. One missed prompt failed the whole connection, and on v3-dev that stranded the bot online, so the next test got kicked with "already playing" and the failure cascaded through the rest of the run.

The plugin now catches that timeout and assumes login (never registration — a silent reconnect can only happen to an account that already exists), then sends /login anyway. successPattern and authenticatedPattern already match "already logged in" as a substring, so if AuthMe considers the session still active, the extra command just gets accepted instead of leaving the bot stuck.

Root cause of the missing prompt itself is still open — this only stops it from taking the rest of the run down with it.

Verified on both stands (example_plugin, feat/53-serial-identity → this branch):

plugwrightTestLocal: 50/50 pass
plugwrightTestStand (hand-started server, same as [v3] AuthMe login prompt sometimes never arrives when a pool account reconnects #57's repro): 44/44 pass, 6 skip — 0 fail, vs. 2 failed in the run that surfaced [v3] AuthMe login prompt sometimes never arrives when a pool account reconnects #57

AuthMe sometimes sends no login/register prompt at all when a pool account reconnects, so the plugin waited out its full timeout and failed the whole test even though the server would have accepted a plain /login. Catch that timeout and assume login (never registration -- a silent reconnect can only happen to an account that already exists). The existing success/authenticated patterns already match "already logged in", so a stale session on the server just costs one extra command instead of stranding the bot online for the rest of the run. ClosesDrownek#57