Repository navigation
Development
English | Русский
Known issue in alpha 0.19.328: 27 producer prefab names differ in letter case from the native registry. This is not fixed in the issued package; review missing parts on import. The correction and successful 251/502-part catalogue checks belong only to the internal 0.19.329 candidate. Eight bounded native data checks are accepted for that candidate. Four direct producer-profile checks (.blueprint/.vbuild) have passed independent review. Acceptance of 2.17 covers codec/profile data only in the internal 0.19.329 candidate. Gameplay sections 3–13 and multiplayer remain open.
Updated 31 October 2026. Issued private alpha: 0.19.328. This is not a public beta or a Thunderstore package. Version and limits.
The internal 0.19.329 candidate has passed eight bounded native data checks. Four direct producer-profile checks (.blueprint/.vbuild) have passed independent review. Acceptance of 2.17 covers codec/profile data only in the internal 0.19.329 candidate. Strict player-state endpoints differ; the cause is not established. Inventory, source files and catalogue content hashes were preserved; the ordinary-save comparison covered metadata only. This run does not establish UI, world construction, new visual frames, networking or a cold-process test. The next requirement is 2.18; the 2.16 HOLD is unchanged. The .280 examples and 23 October captures describe their historical version; they do not validate 0.19.328 or the 0.19.329 candidate.
137 stable IDs:34 scoped accepted/103 open, all 14 sections.Section 1 and2.1–2.15 are accepted within their stated limits; 2.17 is accepted for codec/profile data only in internal 0.19.329; next is 2.18, followed by 2.19–2.23, with2.16required before release.5.7/5.8 are partial. All IDs and future milestones. Assemblies/guides/adaptive pieces/EarthWorks remain planned and do not replace the current module.
These are roadmap directions, not first-release commitments or dates. The priority is the standalone blueprint workflow and durable paid construction with a board, cancellation, refunds, and in-game validation. Broader building contents and shared use follow.
Ordinary Array/Contour already creates copies. Future work preserves repetition parameters so you can change count/spacing and align/distribute pieces without changing their size. Linked instances with an explicit make-independent action come later. Editing a stored Array operation is not currently promised.
The direction is straight A/B → polyline → arc → Bezier curve. A guide supplies position/orientation for parts or assemblies; ordinary pieces remain rigid. Manual placement, repetition, spacing, and orientation still need agreement. Existing temporary A/B points are not that persistent path editor.
BuildWorks-owned pieces could change shape through parameters/guides with matching textures, collision, and snap data. This is separate future geometry work, not a promise to deform arbitrary third-party prefabs.
Both mods remain independent: BuildWorks owns the building, EarthWorks owns terrain preparation/changes. Preparation may be planned for a selected house; the agreed direction is one board and one material store. Appearance, actions, access, accounting, and the technical contract remain under discussion. Cancelling a building never restores terrain. The current board chapter does not describe an implemented cross-mod integration.
For a newly available feature, add a Markdown chapter and Home/sidebar links. Explain purpose, starting state, steps, result, limits, and a common failure. Update evidence, media provenance, and the capture plan. Move a feature from this page into a guide only after identifying its version and proof; source code alone does not verify multiplayer or visual acceptance.