@Grover-c13 did you design this? maybe you can speak a little towards it?

it was redesigned by someone, cant remember who. Basically from what i understand you can force a fresh copy from the server by setting the parameter to true

looks like it may have issues, will look into it on weekend.

@Grover-c13 for what i have see, there are multiple problems

1. the cache object it's not returned (so the cache it's not working)
2. if the cache object it's returned, the object on it won't update after 'user' action ie:
   -- i catch a pokemon, it should disappear from list of catchable (it should disappear after the encounter i think)
   -- i loot a fort, he should have looted expires
   -- pokestop should be invariant objects? using their ids has hashcode to update them?

Ive reworked the cache in the PR #386, people wont have a choice anymore and must use the retained object for at least 5 seconds (this is part of the server throttling), the next request after 5 seconds will always be a fresh request and always sends 0 as the timestamp (the game doesnt seem to send last update just 0).

I agree we need to remove them from the list if caught, makes sense will look at it some time.