Private
_heartbeatReadonly
adapterPrivate
Readonly
cReadonly
hostPrivate
nextReadonly
portReadonly
sendReadonly
useSSLStatic
Readonly
DefaultStatic
Readonly
DefaultStatic
Readonly
DefaultJoin the matchmaker pool and search for opponents on the server.
Optional
string_properties: Record<string, string>Optional
numeric_properties: Record<string, number>Begin matchmaking as a party.
Optional
string_properties: Record<string, string>Optional
numeric_properties: Record<string, number>Request a list of pending join requests for a party.
Receive channel presence updates.
An application-level heartbeat timeout that fires after the client does not receive a pong from the server after the heartbeat interval.
Most browsers maintain an internal heartbeat, in which case its unlikely you'll need to use this callback. However, Chrome does not implement an internal heartbeat.
We fire this separately from onclose
because heartbeats fail when there's no connectivity, and many browsers don't fire onclose
until the closing handshake either succeeds or fails.
In any case, be aware that onclose
will still fire if there is a heartbeat timeout in a potentially delayed manner.
Receive matchmaking results.
Receive a matchmaker ticket.
Receive match presence updates.
Receive notifications from the socket.
Receive party join requests, if party leader.
Receive announcements of a new party leader.
Receive matchmaking results.
Receive a presence update for a party.
Receive status presence updates.
Receive stream data.
Receive stream presence updates.
Private
pingPromote a new party leader.
Remove a chat message from a chat channel on the server.
When no presences are supplied the new match state will be sent to all presences.
Optional
presences: Presence[]Optional
reliable: booleanUpdate a chat message on a chat channel in the server.
Send a chat message to a chat channel on the server.
Generated using TypeDoc
A socket connection to Nakama server implemented with the DOM's WebSocket API.