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.

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

In 1.0.0.130–1.0.0.140

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

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

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).

A client names no one in Pause or Resume.

A server holds the match with Paused.

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

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

In 1.0.0.140–3.1.0.0

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.

In 1.0.0.140–3.1.0.0

A client announces in chat who resumed the match.

In 1.0.0.140

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 1.0.0.130–1.0.0.140

A client sends ClientFinished every time GameEnded arrives in play, while playing a replay too.

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

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

In 1.0.0.140–3.1.0.0

A client moves no neutral unit for VictoryDance.

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.

A client also leaves as one abandoning as its player declines to reconnect or cancels a reconnection under way, and as its player dismisses the notice that it was dropped for being away.

In 1.0.0.140–3.1.0.0

The action of BotKick that means leave is 4.

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

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.

In 1.0.0.130–1.0.0.140

A client sends ReconnectedInMatch on every connection it makes, the first included, with a byte that is 0 where the match is in play and 1 otherwise.

Reconnected announces that a player came back. A client shows it in chat for any other player, ally or enemy.

In 1.0.0.140–3.1.0.0

A client dropped during play connects again at once by itself, for any reason but the one that means its player was away, and shows its player that it is reconnecting while it does. Where its settings turn this off, it asks its player for the reason 0 whether to connect again, and for any other shows that the reconnection failed.

A client sends ReconnectedInMatch as the connection is made, without waiting for the registration answer.

Staying connected

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.

Where its last Camera goes unacknowledged, a client sends it again without its view moving, once more than twice the round trip has passed.

In 1.0.0.140–3.1.0.0

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

In 1.0.0.140–3.1.0.0

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

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
1.0.0.132–1.0.0.134	202
1.0.0.135	204
1.0.0.136–1.0.0.137	202
1.0.0.138	204
1.0.0.139–1.0.0.140	203
1.0.0.141–1.0.0.143	205
1.0.0.144–1.0.0.149	193
1.0.0.150–3.1.0.0	190

Field	Type	What it is
value	u32	The client id the sender holds, as it sends in clientId in Camera and CameraLock.
serverSaid	f32	What the server last said the clock stood at, in seconds.
clientSaid	f32	What the client’s own clock reads, in seconds, just after it set itself from that statement: elapsed plus its smoothed estimate of the delay.
check	bytes, 32	Thirty-two bytes every client of this build sends alike; a server ignores them.

Field	Type	What it is
clientId	u32	A client writes 4294967295, the client id of no client.
timeLeft	i32	A client leaves it unwritten; its bytes carry no meaning.
how	1-byte bits
how.tournament	bit 0	A client sends it clear.
how.unused	bit 1 to 7	A client leaves these bits unwritten; they carry no meaning.

Builds	Command
1.0.0.132–1.0.0.134	170
1.0.0.135	172
1.0.0.136–1.0.0.137	170
1.0.0.138	172

Keyboard shortcuts

Trueshot Season 2