Skip to main content ↑ ↓
Topic: Lists are trimmed to 500 caches after a while (Read 4059 times) previous topic - next topic

Lists are trimmed to 500 caches after a while

I'm not exactly sure what triggers this, but it's been happening to me constantly lately. I'll create a list of all caches within a certain radius of a point (with no limit on the number of caches), and invariably it'll be trimmed down to the 500 closest caches after some time has passed. This persists through refresh, so I actually have to delete the list to fix it.

Added a picture of what I mean. These are the same list, but more than half the caches are gone.

Re: Lists are trimmed to 500 caches after a while

Reply #2 –
Even 1000 is fairly usable on my S21 Ultra. I'd prefer if setting maximum geocaches to 0 on a list was uncapped (maybe with a warning?). That's what I think the behavior has been like before I think. Can't recall having seen the trimming in the past.

Re: Lists are trimmed to 500 caches after a while

Reply #3 –
The trimming code was always there, but due to another issue it wasn't triggered properly until I "fixed" it. I'll look into a setting so you can adjust it higher. I've had complaints before about the time to render map markers so a cap curbs it for more novice users.