Sources & freshness

What this reference is built from, pinned to an exact commit so it can be updated and audited.

Pinned commit

Repository: Meshiest/wirescript
Commit: 96601070f02585f7375f2271e90ac4fb839d8f63
Commit date: 2026-10-23
Commit message: feat: loop continue keyword, v2.3.0
Fetched: 2026-10-27

Files used

Primary — gate inventory. crates/wirescript-ir/data/logic_gate_inventory.simple.json. 423 entries: brick asset, display name, summary, component class, category, kind, inputs, outputs, and config. This drives everything on the site and provides the in-game display names.
Supplementary — gate docs. crates/wirescript/gate_docs.json. Class-keyed descriptions and port tooltips. Used only to fill blanks, always labeled gate_docs, never overriding the inventory. In practice it filled 1 of the 2180 blank port tooltips — its port names don't cleanly map.
Reference — builtins. docs/src/builtins.md. The Wirescript language's built-in functions. Linked for depth, not merged into gate data. Note Wirescript names can differ from the in-game UI (its docs used Cycle for what the game now calls Counter).
Official release notes for cross-checking: EA3, EA3.1, EA3.2.

This is community data, not an official API spec. The inventory was extracted around EA3.2 (it includes Stopwatch and Function Call), but the exact game build and compatibility with the latest hotfix are not verified. Behavior, persistence, defaults, timing, and reset semantics are documented or silent — not independently tested. Verify in-game before relying on anything.

Updating the data

The site regenerates from JSON, so refreshing it is two commands:

# pull the latest sources (prints the new commit) and rebuild data
npm run update-sources   # or: node scripts/update-sources.mjs <commit-sha>
# then paste the printed commit into SOURCE_META in scripts/build-data.mjs
npm run data
npm run build