The match

How a match runs once play has begun, apart from the field: its clock, holds, its end, and players leaving and coming back.

The clock

A server states how long the match has run with ClockSync, and a client answers on the clock channel with ClockReply. Time says how the match clock is kept, and which clock each time on the wire is measured against.

GameSpeed sets how fast the match runs. StatTick hands every unit a span of seconds.

In 4.1–4.19

A client shows the speed GameSpeed sets over its champion. A client changes nothing it shows for StatTick.

In 4.1–4.19

Sent during a hold, GameSpeed takes effect as the match resumes.

StatTick asks every unit’s stats to advance by that span.

Holding and resuming

A client asks to hold the match with Pause, and to resume it with Resume. A server MUST attribute each to the connection it arrived on (see Objects and identifiers).

In 4.1–4.17

A client names no one in Pause or Resume.

In 4.18–4.19

A client puts 0 in the client id of Pause and Resume, the same id as the first seat’s, so a server takes no seat from that field.

A server holds the match with Paused.

Paused carries how long the hold can last, in seconds.

In 4.1–4.19

A client begins a hold only where the time Paused carries is above zero and the match is not already held.

In 4.1–4.19

A client shows a tournament’s hold, crediting the seat that asked, where the message says it is one.

A server ends the hold with Resumed.

Resumed ends the hold either at once or after a countdown the client shows, during which the match stays held.

A client announces in chat who resumed the match.

Input stays locked during the countdown.

The end

A server ends the match with GameEnded, saying which side won, and takes the interface down with HudDisabled. A client shows the win or loss for its player’s side and sends ClientFinished.

In 4.1–4.19

A client that receives GameEnded while still loading leaves at once.

A client sends ClientFinished once, and not while playing a replay.

VictoryDance sets units moving as winners or losers do. It ends nothing.

VictoryDance moves every unit.

Leaving and coming back

A client leaving as one abandoning the match sends Exit: as its player quits or closes the window, as a reconnection fails, or on a server’s Shutdown, which has it leave at once. A client also leaves at once on BotKick with the action that means leave.

In 4.1–4.17

The action of BotKick that means leave is 4.

In 4.18–4.20

The action of BotKick that means leave is 5.

A server tells the others that a player’s client dropped with PlayerDisconnected.

In 4.1–4.19

A client shows a notice in chat for PlayerDisconnected.

SoftReconnect rebuilds a client’s world without a new connection, as Objects and identifiers describes.

A client started again for a match in progress knows nothing of it, and joins as at the start: a server takes it through Joining a match from registering to StartGame, with a spawn run that states the field as it stands, and a ClockSync.

A client the server drops with the reason that means its player was away shows that, and does not connect again.

A server MUST NOT send SpawnStart to a client coming back from a drop: it returns the client to spawning, from which only another StartGame brings it back into play.

In 4.1–4.19

Reconnected announces that another player came back. A client shows it for an ally, or for anyone while it watches the match, and only notes it where it names its own client.

A client dropped during play connects again by itself, registers again, and sends ReconnectedInMatch right after the registration answer; one dropped while loading leaves instead.

A client dropped during play connects again to the same address and port, and shows its player that it is reconnecting until it is back. It goes on where it was: it asks for no status and no version, loads nothing, and keeps every seat, name and identifier it held. A server answers with SoftReconnect, sending between its two stages a message creating each unit the client is to hold.

Staying connected

In 4.1–4.19

A client’s view report, Camera, goes out as its view moves at least 200 units, at most every tenth of a second, and never while its view is locked.

Once loading is done, a client gives up on a connection where a reliable message it sent goes unacknowledged for 15 seconds.

In 4.1–4.19

Before loading is done, a client waits 60 seconds for an acknowledgement rather than 15.

Where it has heard nothing for 5 seconds in play, a client shows its player that it is trying to reconnect, and clears the notice as soon as anything arrives.

In 4.1–4.19

In play a client sends nothing on its own to show it is still there: what it sends answers what it is sent (ClockReply, TransientAck, WaypointAck) or follows from its player, and Camera goes out only as its view moves.

Messages

Each message of this system in this book, with each layout it has across the book’s patches and every note its definition carries. A layout is the message’s body, after the header its channel’s family puts in front (see Messages).

`ClockSync`

What a server sends to set a client’s idea of how long the match has run. The header names no object: a server writes zero.

Builds	Command
4.1–4.10	192
4.11–4.20	193

Field	Type	What it is
serverSaid	f32	What the server last said the clock stood at, in seconds.
clientSaid	f32	What the client’s own clock stood at when that statement arrived, in seconds.

Builds	Command
4.1–4.10	160
4.11–4.17	161

Field	Type	What it is
clientId	u32	A client writes 4294967295, the client id of no client.
timeLeft	i32	A client sends zero.
how	1-byte bits
how.tournament	bit 0	A client sends it clear.
how.unused	bit 1 to 7	Unused; a client writes zero.

Keyboard shortcuts

Trueshot Season 4