Skip to content

Disk (lure) encounter cache no longer needed #283

@jfberry

Description

@jfberry

The disk cache was put in place because the GMO was needed to find the fort id (and lat/lon of the pokemon).
This could be avoided entirely by processing the request.
In fact, it probably means that all GMO processing of lures and the whole disk cache could be removed

message DiskEncounterOutProto {
	enum Result {
		UNKNOWN = 0;
		SUCCESS = 1;
		NOT_AVAILABLE = 2;
		NOT_IN_RANGE = 3;
		ENCOUNTER_ALREADY_FINISHED = 4;
		POKEMON_INVENTORY_FULL = 5;
	}

	Result result = 1;
	PokemonProto pokemon = 2;
	CaptureProbabilityProto capture_probability = 3;
	Item active_item = 4;
	int32 arplus_attempts_until_flee = 5;
}

message DiskEncounterProto {
	int64 encounter_id = 1;
	string fort_id = 2;
	double player_lat_degrees = 3;
	double player_lng_degrees = 4;
	double gym_lat_degrees = 5;
	double gym_lng_degrees = 6;
	Item disk_item_id = 7;
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions