-
Notifications
You must be signed in to change notification settings - Fork 278
Incense Encounters Don't Work #69
Comments
encounter_id for the encounter message needs to be int64...even though the encounter_id on the incensePokemon message is fixed64. I had the same issue, but I got it working by reverting the encounter message back to int64. |
@prorook thanks, I will give it a try. What's the correct way to transform a fixed64 to an int64 in python? I ask cause I get errors thrown if I don't do a conversion (perhaps because I use an older version of protobuf). |
Thank you, got it working after fixing the GetIncensePokemonResponse to PokemonId enum, rather than int32 |
* little fixes * Seems to be right like in AeonLucid/POGOProtos#69 mentioned
Actually, it still fails at times... for large encounter_id type-casting to python's int() doesn't work at times. I just got two encounter_ids (1 worked, 1 didn't) |
How are incense encounters caught without a spawn_point_id? |
@RyanHope they are not, you get one from GetIncencePokemon response. |
@RyanHope it's called "encounter_location" |
This is about to be fixed with |
Using latest commits for protos
I can do: UseIncense -> GetIncensePokemon() -> IncenseEncounter() and here it complaints and throws "INCENSE_ENCOUNTER_NOT_AVAILABLE"
GetIncensePokemon() returns "INCENSE ENCOUNTER AVAILABLE". I then invoke IncenseEncounter with the fixed64 encounter_id and string encounter_location, but get the INCENSE_ENCOUNTER_NOT_AVAILABLE return.
I did modify my proto for IncenseEncounterMessage to be fixed64 for encounter_id to match the GetIncensePokemon response.
Still doesn't work unfortunately.
The text was updated successfully, but these errors were encountered: