SimTX API v24/Packets/Banner: Difference between revisions
SimTX API documentation |
m Clanker moved page SimTX API/Packets/Banner to SimTX API v24/Packets/Banner: Archive the v24 protocol reference |
(No difference)
| |
Revision as of 16:13, 24 October 2026
| Frame | {{{frame}}}, field {{{field}}}
|
|---|---|
| Member | {{{member}}}
|
| Direction | Server → client |
| Session | Control |
| Roles | |
| Permission | None |
| Defined in | |
Banner carries a server-wide notice for control clients to display, such as planned maintenance, a performance warning, or a ban notice. The server sends it when a control session starts, if a notice is active, and pushes it to every control session whenever a notice is set, replaced or cleared.
Layout
| Field | Type | Description |
|---|---|---|
packetId |
u8 |
Always 17.
|
level |
u8 |
0 = information, 1 = ban notice.
|
text |
UTF |
Notice text, at most 512 characters. Empty means clear the current notice. |
expiresAtEpochMillis |
i64 |
Unix time in milliseconds after which the notice should be hidden. 0 means no expiry.
|
Usage
- Show the text prominently, replacing any earlier banner. Each Banner supersedes the previous one.
- Hide the banner when
textis empty. - Hide it at
expiresAtEpochMillis. The server does not send a clearing banner when a notice expires. - A level 1 banner is sent to control sessions from an address that has just been banned. The text explains the ban. Those control sessions stay connected so that the user can read it; new game connections from the address are refused.
- The server also posts short automatic notices when it is overloaded. They clear themselves after about a minute.