Mensagemholoholo.rpc
BelugaTransactionCompleteOutProto
Resposta do método RPC BELUGA_TRANSACTION_COMPLETE (ID 820). O pedido é BelugaTransactionCompleteProto.
| Nº | Campo | Tipo | Tag |
|---|---|---|---|
| 1 | status | BelugaTransactionCompleteOutProto.Status | 08 |
| 2 | candy_awarded | int32 | 10 |
| 3 | loot_awarded | LootProto | 1a |
| 4 | beluga_finalize_response | BelugaBleFinalizeTransfer | 22 |
| 5 | buckets_until_weekly_award | int32 | 28 |
| 6 | xl_candy_awarded_per_id | map<int32, int32> | 32 |
Tipos aninhados
Usado em (0)
Nenhuma mensagem tem um campo deste tipo. Costuma ser o caso dos pedidos e respostas de RPC, que circulam sozinhos.
Código .proto
// holo_protos.proto · package holoholo.rpc message BelugaTransactionCompleteOutProto { Status status = 1; int32 candy_awarded = 2; LootProto loot_awarded = 3; BelugaBleFinalizeTransfer beluga_finalize_response = 4; int32 buckets_until_weekly_award = 5; map<int32, int32> xl_candy_awarded_per_id = 6; enum Status { STATUS_UNSET = 0; STATUS_SUCCESS = 1; STATUS_FAILED = 2; STATUS_ERROR_INVALID_POKEMON_ID = 3; STATUS_ERROR_POKEMON_DEPLOYED = 4; STATUS_ERROR_POKEMON_NOT_ALLOWED = 5; STATUS_ERROR_POKEMON_IS_BUDDY = 6; STATUS_ERROR_INVALID_TRANSACTION_ID = 7; STATUS_ERROR_MISSING_TRANSACTION_ID = 8; STATUS_ERROR_FUSION_POKEMON = 9; STATUS_ERROR_FUSION_COMPONENT_POKEMON = 10; } }