Spawns (& attributes) change depending on weather.

[tokar86a]

It seems like some spawnpoint change there time depending on the weather. It starting to be more and more time that's is not correct. So i suspect that the spawpoints spawn time change depending on what type of weather it is when it spawn.

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce (for bugs)

Context

Your Environment

• Version used:
• Environment name and version (e.g. Python 2.7):
• Operating System and version (desktop or mobile):

[dongemus]

To me, this seems to be a Suspected Niantic bug where the species changes, not a bad timer. It seems to be happening serverside at Niantic. We had one person encounter species A, then on the catch screen it turn to species B. That doesn't seem to be something that Rocketmap is doing, unfortunately.

[dpegasusm]

I have also seen this happen before my eyes, where a spawn point will change mid timer to something else. The IV will change and the mon will change as well. after experimenting with a point like this near my house, if you catch the first mon reported you will never see the second mon. so it looks like a new kind of spawn point where the mon is actually changing at the point mid timer, not that the timer itself is incorrect. There seems to be consistency here too in the time of change. At the point near me the change will always happen 13 minutes into the spawn, which is not the top of an hour and not weather affected.

[blsmit5728]

Just had this happen as well. The map showed a Jigglypuff spawned from 59:12 to 29:12 someone was at the point at 07:00 and it was a dragonite. Weather at both times was cloudy.

[sebastienvercammen]

Everyone has been tracking this issue for a while now, so I'm commenting to keep GitHub up to date.

Since Niantic introduced weather and weather changes, Pokémon spawns have been found to be affected in all kinds of ways:

• Spawn disappears before the spawn timer is over.
• Spawn changes into something else.
• Pokémon attributes change (e.g. Update gender on encounter. #2513).

In the short term, we can only apply small QoL updates to make it easier to detect where a change could have occurred. In the long term, we hope to identify the specifics of the changes and implement updates that can handle the spawn changes.