Editing SimTX API v24/Game tickets (section)

=== Roles ===
The ticket is bound to one role. The role string in the request must correspond to the role byte later sent in the handshake.

{| class="wikitable"
! Ticket <code>role</code> !! Handshake role byte !! Permission required to obtain the ticket
|-
| <code>receiver</code> || 1 <code>RECEIVER</code> || None
|-
| <code>tx-audio</code> || 2 <code>TX_AUDIO</code> || <code>game.transmit</code>
|-
| <code>tx-generated</code> || 3 <code>TX_GENERATED</code> || <code>game.transmit</code>
|-
| <code>control</code> || 4 <code>CONTROL</code> || <code>catalog.publish</code>
|-
| <code>moderation</code> || 5 <code>MODERATION</code> || <code>moderation.manage</code>
|}

There is no ticket role for <code>TIMESTAMPED_RECEIVER</code> (role 6). That role is anonymous only.

An authenticated <code>control</code> connection is only needed to publish to or delete from the [[SimTX API v24/Extension catalog protocol|extension catalog]]. Reading the station list, maps and the catalog works anonymously.

The permission check uses the intersection of the credential's scopes and the account's effective permissions on that server. A credential created with scope <code>catalog.publish</code> cannot obtain a <code>tx-audio</code> ticket, even if the account itself may transmit.