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.

This build

Built in GitHub Actions from jgwoolley/vintage-story-wiki on branch main.

Commit: bc7e4fc — Now uses npm workspaces + has vscode extension (James W)

CI run: https://github.com/jgwoolley/vintage-story-wiki/actions/runs/38740964021

Generated 2026-10-15T13:15:38.728Z ago (2026-10-15T13:15:38.728Z 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 3.2s, finished 2026-10-15T13:14:24.899Z 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	775 ms
nf3ttranslocatorrepair	skipped-present	143 ms
nf3ttranslocatorfindercmd	skipped-present	147 ms
nf3ttranslocatornavigator	skipped-present	141 ms
nf3tblueprintcopy	skipped-present	144 ms
nf3tsponge	skipped-present	143 ms
chiseltools	skipped-present	512 ms
treetapredux	skipped-present	143 ms

2. Ingest (`npm run ingest`)

Took 1m 11s, finished 2026-10-15T13:15:37.538Z UTC.

Step	Took
Resolving mods	908 ms
Building asset sources	1 ms
Indexing schematic files (headers only, voxel data stays unparsed)	8 ms
Loading assets (JSON5)	16.8s
Applying patches	34 ms
Extracting recipes	19 ms
Extracting loot	15.7s
Extracting schematics + structures	400 ms
Compressing schematics for the in-browser viewer	3.4s
Extracting decor catalog (paintings/tapestries/clothing)	126 ms
Cross-referencing decor items against structure schematics	185 ms
Extracting lore books	7 ms
Locating lore books in structure schematics	2.0s
Resolving tapestry/wallcarving instances in worldgen schematics	4.5s
Resolving clutter types (ShapeFromAttributes) in worldgen schematics	8.1s
Extracting ore/gem/rock deposits	1 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)	0 ms
Extracting help guides	3 ms
Extracting trader buy/sell lists	0 ms
Extracting NPC dialogue	156 ms
Cross-referencing trader specializations against trader entity variants	4 ms
Extracting player traits and starting classes	6 ms
Building item index	838 ms
Extracting weapon/tool stats	772 ms
Cross-referencing items against structure schematics	191 ms
Attaching item descriptions + C# class references	2.1s
Extracting block display names (schematic viewer legend)	15.0s
Writing generated data	140 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.

Not available — the site hasn't been built via apps/vs-wiki/scripts/build-site.ts yet (e.g. a bare npx eleventy invocation was used instead, or this is the very first build in this checkout).