Skip to content

v6.18.0

Choose a tag to compare

@github-actions github-actions released this 14 Oct 23:51
· 20 commits to main since this release

[6.18.0] — 2026-10-14 — Painted tiles are dealt at random and kept; bakes choose their quality and export the map; hex.bakeMap and the tile pool join the hex API

Added

  • A bake says what it weighs, before and after. The Bake Map Background dialog now reports both sides of the change: what the scene's tiles load today — the distinct texture files, counted, with their total bytes measured by HEAD requests and cached across sessions — and what the bake will replace them with, estimated from measured flattens (0.25 bytes per pixel at quality 0.9 tracks the Western Reaches map's real 12.3–13.0 MB bakes within a few percent). The completion notification then reports the file's actual size. A host that answers no content-length gets the file count alone — the dialog never guesses a total.
  • A running bake shows its steps. While Bake Map Background works — a minute or more on large maps — a small progress card tracks it: the current step in words (loading textures, rendering, encoding, saving to the server, replacing the tiles, per piece), a bar that advances as each real step finishes, live texture-loading counts ("214 of 387 texture files loaded"), and a ticking elapsed clock. The browser reports no progress for its own webp encode, so the card never fakes a crawl — it shows what is happening and that it is still happening, in place of a silent minute that reads as a freeze.
  • The hex background bake can trade size for detail — and asks which you want. Bake Map Background offers Low, Medium, High and Max right in its confirm dialog, each priced before you pick: the bake's dimensions, its scale against the full map and the estimated file size — and the pick is remembered as the next dialog's default. Low, Medium (the previous fixed cap) and High are one image with the longest side bounded at 4096, 8192 or 12288 px (the renderer's 16384 px texture limit can bound High further), never past full size, so a map already under the chosen cap bakes at native resolution. Max is full resolution, split into pieces: a single image cannot exceed what the browsers' webp encoders actually survive (150 MP — measured: Firefox refuses a 201 MP canvas-to-webp outright while a loaded tab under Chromium ground for minutes and produced nothing) or the renderer's 16384 px texture side, so Max bakes a map as however many image tiles both walls require — the Western Reaches map bakes as two 14262×9536 images, locked so canvas drags cannot nudge them out of place — and Restore takes the pieces away again. The progress and completion notifications state the size, piece count and actual file size of the bake, so nothing about a large map's output is discovered only on the canvas. Everything else about the bake and its Restore is unchanged.
  • The map can be exported as an image file, for looking at outside Foundry — at full light, whatever the time of day. An Export Map Image button beside Bake Map Background renders the scene's map to webp and delivers it two ways: saved under map-exports/ in the user data folder, and downloaded to the browser, so a hosted world exports onto the user's own machine too. Nothing about the scene changes — no tiles, no background, no flags — which also makes it the safe way to see what a bake would produce before running one. It asks the same priced quality question as a bake (Max splits a large map into pieces exactly the same way), exports a flattened scene's existing files instead of re-rendering, and both it and a bake draw the art as fully lit: the environment overlays — darkness, coloration, illumination — are excluded from the capture, so a night scene does not export as a night picture.

Changed

  • A painted hex's tile is dealt at random and kept, not worked out from its position. Each hex draws from its terrain's pool, never the tile of a hex that touches it (when the pool has another), the least-used tiles first, and the draw is saved on the scene. The old place-based formula was a poor scatter and the same on every map: with a pool of 17 the whole of a row came out as one tile (Salt Flats), and pools of 6, 8 and 12 repeated along a diagonal (jungle, lava, swamp). Now every map gets its own picture, and it stays put: repaintHexTiles leaves a hex on its saved tile while its terrain still draws it, and takes another when the terrain moves or the hex entry says reshuffle: true; buildHexcrawl over a scene of the same name carries the replaced scene's deal, takes an explicit layout (from the new hex.getPaintLayout(sceneId)), or reshuffle: true for a fresh deal. Scenes painted before this have no saved deal and keep every tile until a hex is repainted.

  • hex.bakeMap(sceneId) bakes a painted map without the sidebar menu. "Bake map for play" only appears while Tile Flatten is on, so a world that keeps Tile Flatten off could not reach the bake from the interface. The call runs the same bake and returns the new scene's id and name; it needs the GM's own client (a GPU), and takes about a minute.

  • A hex's tile can be chosen, and the choices of a terrain read. hex.getTilePool(terrain) lists the tiles a terrain is dealt, and a repaintHexTiles entry may carry tile: that exact catalogue tile, kept as ground (so a bake still draws it as terrain, which art would not) and saved in the deal. A tile from another terrain's pool is pinned and survives a repaint of the same terrain until the hex's terrain moves or the entry says reshuffle: true. This is what a hex-by-hex tile picker is built on.

Fixed

  • A terrain rule no longer paints another location's own picture. The volcano rule matched 657_Extinct_Volcano.webp, which is hex 657's keyed illustration, because it shares a word with the rule. Terrain and settlement rules now draw only from the Specials folder's unnumbered tiles.
  • Baking right after Restore Hexagons no longer captures blank tiles. Restored tiles' textures resolve asynchronously, and a bake that rendered before they landed wrote a flat, empty background. The bake now preloads the scene's distinct tile texture sources — one load per file, through the same cache the sprites use — before it renders.
  • A baked map no longer shows every keyed location from the first turn when Shadowdark Enhancer runs the hex fog. The baked copy asked only Extras' own fog whether to show a keyed location, and Extras stands down on a map the Enhancer owns, so players saw all of them before the party had been anywhere. The art now follows the Enhancer's own disclosure: a location appears once the party has been to the hex or the GM has revealed it, the same moment its map pin does, and stays hidden if the Enhancer cannot say. The GM still sees every location, faded for hexes the viewed party has not visited. A map the Enhancer does not own is unchanged. The Enhancer fires a hook when its fog redraws (shadowdark-enhancer#490); until that ships, the map refreshes from the Enhancer's own record updates.
  • Clicking an NPC feature's name on the NPC sheet posts its card again. On Shadowdark 4.0.6 the click ran the feature's macros and activities but posted nothing to chat, so a feature with no macro appeared to do nothing. NPC Special Attacks with no attack bonus and the token toolbar's NPC button went through the same path and were silent too. The card is now posted first, then the macros and activities run. Introduced in 6.10.28.
  • Salt Flats and Lava Fields art is no longer filed under the wrong terrain. Foundry's FilePicker lists a folder's name percent-encoded, so those two folders arrived as Salt%20Flats and Lava%20Fields and matched no terrain pool. Their tiles spilled into the shared pool that other terrains draw from at random, and the terrain's own rule found nothing of its own and always fell back. The folder name is now decoded when the tree is scanned, and again when a cached catalogue is read, so a world that has already scanned those folders is repaired without waiting for the catalogue to be invalidated. Hexes already painted keep what the old code gave them until they are repainted: fallback art stays, and a hex painted from one of these folders keeps its encoded terrain label (Salt%20flats).

Read the Shadowdark Extras Wiki