Build info
Full detail behind the "generated X ago" note in the footer of every page: exactly which commit/branch/CI run produced this build, and how long each of the three pipeline phases (download, ingest, site build) took to run.
Production wiki: https://jgwoolley.github.io/vintage-story-wiki/
This build
Built in GitHub Actions from
jgwoolley/vintage-story-wiki
on branch main.
Commit:
465cc46
— Now vintagestory-wiki.nf3t.com
(James W)
CI run: https://github.com/jgwoolley/vintage-story-wiki/actions/runs/39876421660
Generated
ago
(2026-10-23T00:12:20.331Z UTC).
Pipeline timings
Each phase below runs as its own process (in CI, three separate workflow steps, possibly
minutes apart) and persists its own timing to a small JSON file under
site/_data/generated/ that this page reads — see
apps/vs-wiki/src/ingest/types.ts's DownloadTiming/IngestTiming/
EleventyBuildTiming for the exact shape of each.
1. Download (npm run download)
Took 2.7s, finished 2026-10-23T00:10:12.817Z UTC.
already present everything was cached from a previous run (skip-checked, not re-fetched) — a small duration here is expected, not a bug.
| What | Outcome | Took |
|---|---|---|
| Vintage Story server | skipped-present | 1 ms |
| betterruins | skipped-present | 1.0s |
| stonequarry | skipped-present | 550 ms |
| nf3ttranslocatorrepair | skipped-present | 143 ms |
| nf3ttranslocatorfindercmd | skipped-present | 138 ms |
| nf3ttranslocatornavigator | skipped-present | 144 ms |
| nf3tblueprintcopy | skipped-present | 136 ms |
| nf3tsponge | skipped-present | 142 ms |
| chiseltools | skipped-present | 278 ms |
| treetapredux | skipped-present | 143 ms |
2. Ingest (npm run ingest)
Took 2m 03s, finished 2026-10-23T00:12:18.860Z UTC.
| Step | Took |
|---|---|
| Resolving mods | 1.3s |
| Building asset sources | 0 ms |
| Indexing schematic files (headers only, voxel data stays unparsed) | 8 ms |
| Loading assets (JSON5) | 25.2s |
| Applying patches | 48 ms |
| Extracting recipes | 27 ms |
| Extracting loot | 30.7s |
| Extracting schematics + structures | 602 ms |
| Compressing schematics for the in-browser viewer | 5.9s |
| Extracting decor catalog (paintings/tapestries/clothing) | 237 ms |
| Cross-referencing decor items against structure schematics | 294 ms |
| Extracting lore books | 9 ms |
| Locating lore books in structure schematics | 4.0s |
| Resolving tapestry/wallcarving instances in worldgen schematics | 5.6s |
| Resolving clutter types (ShapeFromAttributes) in worldgen schematics | 11.2s |
| Extracting ore/gem/rock deposits | 2 ms |
| Extracting crop/flower/mushroom/etc. spawn patches | 2 ms |
| Extracting tree/shrub species spawn data | 4 ms |
| Extracting fruit tree variety spawn data | 0 ms |
| Extracting rock strata (base rock-type placement) | 1 ms |
| Extracting help guides | 3 ms |
| Extracting trader buy/sell lists | 1 ms |
| Extracting NPC dialogue | 259 ms |
| Cross-referencing trader specializations against trader entity variants | 7 ms |
| Extracting player traits and starting classes | 10 ms |
| Building item index | 1.6s |
| Extracting weapon/tool stats | 221 ms |
| Extracting food nutrition | 1.3s |
| Cross-referencing items against structure schematics | 292 ms |
| Attaching item descriptions + C# class references | 3.7s |
| Extracting block display names (schematic viewer legend) | 30.1s |
| Writing generated data | 203 ms |
3. Site build (Eleventy)
Eleventy can't report its own total duration to its own templates — the number isn't
known until the process is already exiting, after every page (including this one) has already
rendered. apps/vs-wiki/scripts/build-site.ts wraps the real eleventy CLI, times the
whole child process, and writes eleventyBuildTiming.json only after it exits. That
means the figure below is always one full build run stale: it describes the
previous successful build, not the one that produced this page. It is shown here labeled as
such rather than silently presented as a live number.
Previous build took 2m 23s, finished
2026-10-20T01:51:36.434Z UTC.