Hi.
When we upload an image into the game maps, it gives the file an identifier based on the game and group numbers. Our browsers cache the image so they don't have to reload it every single time we open the file.
Bandwidth saved. Yay!

... except when a map gets updated. Since the browser doesn't realize the image file for the group has changed, it relies on the old, cached version of the file and doesn't bother to download the new map. Which means that you can't see the new version of the map, and since the browser doesn't realize the map has changed, it has no way to tell you you're looking at an old version of the map. So, even if you knew somehow that the map HAD changed, you'd have to empty the page's cache so your browser would know to download the new version of the image file.

So.
Would it be possible to add a version number or timestamp or the version's filename to the image filename so the web browser wouldn't just use its cache every time it hits the Maps page? Or if there's a good way to force a reload, that might work... although performance would also suffer on large maps, so... not an ideal solution.

Thanks for your hard work!

I believe that the use of the cache is controlled by the browser settings.

For Firefox (my weapon of choice), you can manually change the setting by following the instructions below (in a nutshell, you need to go to about:config and then search for and modify the browser.cache.check_doc_frequency value):

https://support.mozilla.org/en-US/questions/1203480

Or you can just press CTRL+F5 to force a page refresh and reload images from scratch.

There'll undoubtedly be similar settings in Edge/Chrome etc.

In reply to Skald (msg # 2):

Yeah. I don't actually want my browser to stop caching all images as I use a hotspot for connection sometimes, and I haven't found a way yet to convince my browser to not store caches on a per-site basis... although, frankly, that sounds like an awesome plug-in I should probably go ahead and write. lol
CTRL+F5, of course, is a solution as long as you know the cache is out of date...

Eh, it's fine. I'll just write a browser extension for it. Thanks anyway! :)