Changelog

This page records only changes that alter project boundaries. Small wording edits, scattered copy fixes, and temporary experiments do not belong here.

2026-04-04

Permanent Documentation Formalization

The permanent documentation surfaces went through a full consolidation pass on this date. The important part was not page count. The important part was moving rules that had been scattered across temporary planning files, showcase-style writing, and local notes back into permanent pages.

The main pages consolidated in this pass include:

• the home page and top-level catalogue pages,
• the main-loop, pseudo-instance, civilization-shell, and catalogue pages under Design,
• the survey, activation, site-runtime, resonance, and recovery design and implementation pages under ModdingDeveloping,
• the catalogue or rule pages under Developing, Grouping, Modpacking, and Contribute.

Documentation Rules Locked

This date also locked the current documentation standard:

1. Headings use explicit English anchors.
2. Mermaid no longer uses <div> or showcase-style line-break tricks.
3. Body text focuses on objects, phases, data structures, and boundaries instead of showing thought process.
4. ModdingDeveloping is Forge-side runtime only; pack work, KubeJS, and datapacks belong in Modpacking.
5. The docs keep a direct project voice instead of presentation-copy phrasing.

First-Version Direction Clarified

By this point, the first-version direction was fixed as follows:

• the main loop is early discovery, formal survey, activation, site runtime, resonance, and recovery,
• the site model stays with a local pseudo-instance instead of a separate dungeon dimension,
• activation is centered on ActivationService rather than a single hard-coded right-click path,
• resonance performs evaluation only, and tooltip layers read saved snapshots only,
• TaCZ and its current extension stack remain the shared firearm base instead of splitting into multiple weapon systems.

2026-04-03

Documentation Foundation

The project established the current documentation tree on this date:

• Developing
• Grouping
• Modpacking
• ModdingDeveloping
• Design
• Contribute
• Changelog

That split separated showcase, development, integration, runtime, and contributor rules into fixed subtrees.

Core Loop Consolidation

The project main line was also reduced to one explicit chain on the same day:

• archaeology brings the player into a ruin,
• the local pseudo-instance creates the site scene,
• resonance shapes how the site is handled,
• recovery and identification leave the long-term result behind.

From this date onward, archaeology stopped carrying the full encounter expression by itself, and resonance stopped being treated as a side system.