You are looking at version 0.403.1. The latest is 0.437.0. See it in 0.437.0What changed in 0.403.1
Messageholoholo.rpc
JoinBreadLobbyProto
Request of RPC method JOIN_BREAD_LOBBY (ID 2450). The response is JoinBreadLobbyOutProto.
| No. | Field | Type | Tag |
|---|---|---|---|
| 1 | bread_battle_seed | int64 | 08 |
| 2 | station_id | string | 12 |
| 3 | station_lat_degrees | double | 19 |
| 4 | station_lng_degrees | double | 21 |
| 5 | bread_battle_entry_point | BreadBattleEntryPoint | 28 |
| 6 | use_power_crystal | bool | 30 |
| 7 | bread_lobby_id | int64 | 38 |
| 8 | is_battle_assist | bool | 40 |
| 9 | use_remote_pass | bool | 48 |
| 10 | inviter_id | string | 52 |
| 11 | is_self_invite | bool | 58 |
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 JoinBreadLobbyProto { int64 bread_battle_seed = 1; string station_id = 2; double station_lat_degrees = 3; double station_lng_degrees = 4; BreadBattleEntryPoint bread_battle_entry_point = 5; bool use_power_crystal = 6; int64 bread_lobby_id = 7; bool is_battle_assist = 8; bool use_remote_pass = 9; string inviter_id = 10; bool is_self_invite = 11; }