v1.5.2.1

A fix release for GMs whose Foundry is hosted somewhere that keeps uploaded files outside the world's data folder (The Forge is the case this was reported on). Self-hosted worlds are unaffected by everything below and need not hurry.

The People gallery was empty on a world that had all the art

If you imported your book art on a hosted server, the gallery of "People of Stonetop" portraits could come up empty even though every picture was on disk and visible in your asset library. The same blank could affect treasure art and the GM playbook diagrams.

The system asks the server which pictures are present. On a hosted setup your uploads are redirected into an asset library, so the folder the system asked about was empty while the real one, a little further away, was full. The server answered "no files" rather than "no such folder", and there is no way to tell that apart from a folder you emptied on purpose, so the system dutifully recorded that you had no art and did so again on every load.

It now asks a second time, in the place the server itself said your art was served from, and only when the first answer came back empty. Nothing about a self-hosted world changes: there is no second question to ask, so it is never asked.

Your gallery should refill by itself the next time you load the world. No re-import, no settings to touch.

Re-importing on a hosted server no longer redoes everything

The importer had the same blind spot when it checked what was already on disk. It could not see your existing art, so "skip what is already there" never skipped: every re-import re-extracted and re-uploaded all 545 pictures. It also meant that importing one book could drop art belonging to a book you did not supply that run.

The two Book II regional maps that timed out

On a slower machine, The Vicinity and The World's End could fail with "timed out after 60s" while every other picture imported fine.

Those maps are the only two pages in the rulebooks that get rasterised whole rather than lifted, because their location labels are text printed over the artwork. At 300 dpi that is 8.4 megapixels of dense map, which is legitimately minutes of work, and it was being judged by a stopwatch meant for catching something that had frozen. The time allowed is now based on how big the page actually is. A render that still runs over is stopped rather than left running in the background slowing down everything after it.

If an import times out on a machine that ought to cope, check whether you left the browser tab in the background. Browsers throttle drawing in hidden tabs, and the clock keeps running.

One case this cannot fix by itself

If you last imported your art on version 1.4.x or earlier and you are on a hosted server, the system has no record of where that server keeps your files and no way to work it out. You will notice this as book illustrations showing as broken images throughout, not just as an empty gallery. Re-run Import Book Art once and everything reconnects, including the gallery.

Also

• When the system clears its record of what art is on disk, it now says so in the console instead of doing it silently. That silence is what made this take two rounds to find.
• Full details, including how it was diagnosed, are in the commit message.

Installing: use the manifest URL below, or update from Foundry's package browser.

https://github.com/PrinceWitherdick/stonetop-pwd/releases/latest/download/system.json

Full Changelog: 1.5.2...1.5.2.1