Jump to content

SimTX API/Packets/CatalogDeleteResult: Difference between revisions

From SimTX Wiki
Clanker (talk | contribs)
Clanker moved page SimTX API/Packets/CatalogDeleteResult to SimTX API v24/Packets/CatalogDeleteResult: Archive the v24 protocol reference
Tag: New redirect
 
Clanker (talk | contribs)
Protocol v25 reference: CatalogDeleteResult
Tag: Removed redirect
Line 1: Line 1:
#REDIRECT [[SimTX API v24/Packets/CatalogDeleteResult]]
{{SimTX API navigation}}
{{SimTX packet
| name = CatalogDeleteResult
| frame = ServerFrame
| field = 39
| member = catalog_delete_result
| direction = s2c
| session = [[SimTX API/Extension catalog protocol|Control (catalog)]]
| roles = <code>ROLE_CONTROL</code>.
| permission = None
| answers = [[SimTX API/Packets/CatalogDelete|CatalogDelete]]
| group = catalog
| file = control.proto
}}
'''CatalogDeleteResult''' confirms that a [[SimTX API/Packets/CatalogDelete|CatalogDelete]] removed the entry. Refusals arrive as [[SimTX API/Packets/Error|Error]].
 
== Definition ==
<syntaxhighlight lang="protobuf">
message CatalogDeleteResult {
  reserved 2, 3;
  reserved "ok", "message";
  int64 request_id = 1;
  int32 entry_id = 4;
}
</syntaxhighlight>
 
== Fields ==
{| class="wikitable"
! # !! Field !! Type !! Description
|-
| 1 || <code>request_id</code> || <code>int64</code> || The request this answers.
|-
| 4 || <code>entry_id</code> || <code>int32</code> || The removed entry.
|}
 
Reserved, never reused: field numbers 2, 3 and the names <code>ok</code>, <code>message</code>.
 
== See also ==
* [[SimTX API/Packets/CatalogDelete|CatalogDelete]]
 
{{SimTX API navbox}}
[[Category:SimTX API]]

Revision as of 16:44, 24 October 2026

CatalogDeleteResult
Frame ServerFrame, field 39
Member catalog_delete_result
Direction Server → client
Session Control (catalog)
Roles ROLE_CONTROL.
Permission None
Answered by
Answers CatalogDelete
Defined in control.proto

CatalogDeleteResult confirms that a CatalogDelete removed the entry. Refusals arrive as Error.

Definition

message CatalogDeleteResult {
  reserved 2, 3;
  reserved "ok", "message";
  int64 request_id = 1;
  int32 entry_id = 4;
}

Fields

# Field Type Description
1 request_id int64 The request this answers.
4 entry_id int32 The removed entry.

Reserved, never reused: field numbers 2, 3 and the names ok, message.

See also

SimTX API reference (protocol v25)
Start OverviewQuick startFramingData typesPacket listSchemaLimits and errorsCompatibility and versioning
Account service OverviewDevice loginServer directoryStation endpointsGame ticketsPermissionsPublic endpoints
Game protocol Connection and handshakeSession statusReceiver sessionTransmitter sessionControl sessionCatalogModeration
Stations StationsSatellitesTracking and pointing
Connection ClientHelloPingServerHelloPongErrorBanner
Session AntennaPointingUpdateSessionStatus
Receiver ForwardedClientAddressReceiverStartReceiverRetuneIqStreamDescriptorIqBlock
Transmitter TransmitterStartSampleBlockTxUpdateTxModeInfoTxQueueTxAcceptTxTelemetryTxUpdateAck
Control ListStationsStartMonitorStopMonitorWeatherMapRequestServerHealthRequestCoverageMapRequestEphemerisRequestPassPredictionRequestStationListMonitorBlockMonitorEndWeatherMapResponseServerHealthReportCoverageMapResponseEphemerisResponsePassPredictionResponseMonitorAck
Catalog CatalogListRequestCatalogFetchCatalogUploadCatalogDeleteCatalogListCatalogEntryCatalogUploadResultCatalogDeleteResult
Moderation KickRequestIpModerationRequestBroadcastBannerKickResultIpModerationResultStationImpactList
Archive Protocol v24 reference