protos/pogo0.437.0

You are looking at version 0.435.2. The latest is 0.437.0. See it in 0.437.0What changed in 0.435.2

Enumholoholo.rpcInvasionAvailabilitySettingsProto

InvasionAvailabilitySettingsId

holoholo.rpc.InvasionAvailabilitySettingsProto.InvasionAvailabilitySettingsIdFile: holo_protos.proto8 valuesSince 0.403.1

ValueName
0INVASION_AVAILABILITY_SETTINGS_ID_INVASION_AVAILABILITY_SETTINGS_UNSET
1INVASION_AVAILABILITY_SETTINGS_ID_INVASION_AVAILABILITY_SETTINGS_MONDAY
2INVASION_AVAILABILITY_SETTINGS_ID_INVASION_AVAILABILITY_SETTINGS_TUESDAY
3INVASION_AVAILABILITY_SETTINGS_ID_INVASION_AVAILABILITY_SETTINGS_WEDNESDAY
4INVASION_AVAILABILITY_SETTINGS_ID_INVASION_AVAILABILITY_SETTINGS_THURSDAY
5INVASION_AVAILABILITY_SETTINGS_ID_INVASION_AVAILABILITY_SETTINGS_FRIDAY
6INVASION_AVAILABILITY_SETTINGS_ID_INVASION_AVAILABILITY_SETTINGS_SATURDAY
7INVASION_AVAILABILITY_SETTINGS_ID_INVASION_AVAILABILITY_SETTINGS_SUNDAY

Used in (0)

No message has a field of this type.

.proto source
// holo_protos.proto · package holoholo.rpc
enum InvasionAvailabilitySettingsId {
  INVASION_AVAILABILITY_SETTINGS_ID_INVASION_AVAILABILITY_SETTINGS_UNSET = 0;
  INVASION_AVAILABILITY_SETTINGS_ID_INVASION_AVAILABILITY_SETTINGS_MONDAY = 1;
  INVASION_AVAILABILITY_SETTINGS_ID_INVASION_AVAILABILITY_SETTINGS_TUESDAY = 2;
  INVASION_AVAILABILITY_SETTINGS_ID_INVASION_AVAILABILITY_SETTINGS_WEDNESDAY = 3;
  INVASION_AVAILABILITY_SETTINGS_ID_INVASION_AVAILABILITY_SETTINGS_THURSDAY = 4;
  INVASION_AVAILABILITY_SETTINGS_ID_INVASION_AVAILABILITY_SETTINGS_FRIDAY = 5;
  INVASION_AVAILABILITY_SETTINGS_ID_INVASION_AVAILABILITY_SETTINGS_SATURDAY = 6;
  INVASION_AVAILABILITY_SETTINGS_ID_INVASION_AVAILABILITY_SETTINGS_SUNDAY = 7;
}