Skill · Version 1.0.0

Nakama sessions and reconnection

Restores online play by treating login, socket connection and match participation separately. It handles expired credentials and bounded retries, then reloads server state without accumulating listeners or duplicate actions.

nakama-sessions-reconnect

See how it helps

When is it useful?

Use it when network switches or expired credentials interrupt play and socket reconnection alone is insufficient.

What does it help you do?

Separates authentication sessions, sockets and match presence.
Defines token expiration, reconnect and explicit match rejoining.
Restores server state with bounded retries and no duplicate listeners.

Try asking this

Disconnect our cooperative player after their login session expires but while the client still shows a match. Reauthenticate through the existing flow, reconnect the socket and rejoin explicitly. Restore the current world, prevent old queued attacks from replaying blindly and verify one listener per event.

Detailed documentation

Read the skill’s original instructions, examples and checks in their authored language.

Details…Show less

Nakama — sessions reconnect

Use when implementing Nakama sessions, sockets, presence loss or rejoin behavior.

Version and project gate

Inspect Nakama server and client SDK versions, chosen Go/TypeScript/Lua runtime, compiled module deployment, database topology, match handlers, RPC registrations, auth/session handling, storage collections and permission rules. Never turn a task into an engine upgrade without the user’s intent. Read the version-matching official reference when an API decision depends on it.

Work

Separate refreshable authentication sessions from socket and match presence. Define reconnect/rejoin and expired-session outcomes using the installed SDK. Rehydrate authoritative state rather than trusting cached client progress. Bound retries and prevent duplicated subscriptions; never log session tokens.

Deliver

A session/socket/match transition table and client recovery path. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.

Failure to prevent

A reconnected socket does not prove the player rejoined the same match or recovered missed events.

Acceptance scenario

Expire a session, switch networks, reconnect repeatedly and rejoin a running match without duplicate listeners or player records. Follow the project’s execution and verification permissions. If execution or a target device is unavailable, provide the reproduction steps and name the remaining uncertainty; do not mark it passed.

Scope and sources

This skill belongs to Kairo. Agent selection is restricted by Orqestria’s assigned-agent policy, including forced skill selection; instruction text alone is not an access control. These are original task workflows researched from official documentation, not a copied or endorsed vendor skill.

Task-specific official references

Included files 1

SKILL.md