You are looking at version 0.403.1. The latest is 0.437.0. This type no longer exists in 0.437.0.What changed in 0.403.1
Messageholoholo.rpc
FortDeployOutProto
| No. | Field | Type | Tag |
|---|---|---|---|
| 1 | result | FortDeployOutProto.Result | 08 |
| 2 | fort_details_out_proto | FortDetailsOutProto | 12 |
| 3 | egg_pokemon | PokemonProto | 1a |
| 4 | gym_state_proto | GymStateProto | 22 |
Nested types
Used in (0)
No message has a field of this type. That is usual for RPC requests and responses, which travel on their own.
.proto source
// holo_protos.proto · package holoholo.rpc message FortDeployOutProto { Result result = 1; FortDetailsOutProto fort_details_out_proto = 2; PokemonProto egg_pokemon = 3; GymStateProto gym_state_proto = 4; enum Result { RESULT_NO_RESULT_SET = 0; RESULT_SUCCESS = 1; RESULT_ERROR_ALREADY_HAS_POKEMON_ON_FORT = 2; RESULT_ERROR_OPPOSING_TEAM_OWNS_FORT = 3; RESULT_ERROR_FORT_IS_FULL = 4; RESULT_ERROR_NOT_IN_RANGE = 5; RESULT_ERROR_PLAYER_HAS_NO_TEAM = 6; RESULT_ERROR_POKEMON_NOT_FULL_HP = 7; RESULT_ERROR_PLAYER_BELOW_MINIMUM_LEVEL = 8; RESULT_ERROR_POKEMON_IS_BUDDY = 9; RESULT_ERROR_FORT_DEPLOY_LOCKOUT = 10; RESULT_ERROR_PLAYER_HAS_NO_NICKNAME = 11; RESULT_ERROR_POI_INACCESSIBLE = 12; RESULT_ERROR_LEGENDARY_POKEMON = 13; RESULT_ERROR_INVALID_POKEMON = 14; } }