- summary: The account's permission flags for this session, as an opaque block of booleans (five; four from 3.7.1.0).
- area: Game.Account
The account's permission flags for this session, as an opaque block of booleans (five; four from 3.7.1.0).
Kind event · Area Game.Account
Pushed during account setup. You receive it, record it, and never reply - nothing in the protocol is gated on having processed it.
THE FLAGS ARE NOT INDIVIDUALLY RECOVERED and are deliberately left unnamed.
There are five of them up to 3.6.12.16 and four from 3.7.1.0. Every line of evidence that names things elsewhere in this catalogue
fails here: the unobfuscated reference build has no account-rights type in the
game protocol, the early 3.x name map has none either, and the client's handlers
branch only on the BLOCK's presence, never on an individual flag. Read them
positionally as opaque flags, or ignore them - see Rights.
UP TO 3.6.12.16 THE DECLARATION CARRIES TWO FIELDS OF THE SAME NESTED TYPE and only one is ever read. Five consumers across two services all read the same member and never touch the other, which is what makes the named one the real one. From 3.7.1.0 the second copy is gone and a repeated string sits beside the block instead; no consumer loads it, so ignore it.
This record describes the current build. Earlier builds either lack the message or carry a different shape.
When you may send it
- Requires
authenticatedobserved
Related messages
- Unsolicited - nothing you send causes this inferred — no client writer constructs it in any dumped build and there is no matching request message
Fields
| # | Field | Type | Meaning | You set it |
|---|---|---|---|---|
| 2 | rights | Rights | The account's permission-flag block. See Rights. The only member any client consumer reads.The declaration carries a second field of the identical type that nothing reads. Name ours: no build names this field (the type-name table names types only). | never |