Files

T

archvillainette dc93feb176 Topdata Migration (#2 )

Native topdata migration summary

- Replaced the legacy 2dabuilder runtime path with the native topdata builder.
- Native build, validate, compare, and convert flows now cover the canonical topdata pipeline.
- compare-topdata is now a native self-check; legacy reference-builder runtime usage was removed.
- Parts generation follows the native asset-scan contract and uses sow-assets via project asset resolution.
- Generated feat families, class-feat injects, masterfeat/successor expansion, and dataset-derived feat generation were brought to parity and regression-covered.
- Remaining mirrored datasets were migrated into native-owned canonical data while preserving lock IDs.
- normalize-topdata bridge behavior and migration-era ownership markers were removed.
- Documentation was rewritten around the native workflow and active contracts were cleaned up.
- Final hardening pass removed stale validator assumptions and cleaned ignored/generated artifacts for PR readiness.

Reviewed-on: https://gitea.westgate.pw/ShadowsOverWestgate/sow-tools/pulls/2
Co-authored-by: vickydotbat <vickydotbat@tutamail.com>
Co-committed-by: vickydotbat <vickydotbat@tutamail.com>

2026-04-09 07:14:01 +00:00

2.5 KiB

Raw Blame History

sow-tools

Shared NWN build tooling for Shadows Over Westgate.

This repository owns the Go-based sow-toolkit binary used by the separate module and assets repositories.

Build

Build the development binary into tools/sow-toolkit:

./build-tool.sh

Or run directly with Go:

GOCACHE="$PWD/.cache/go-build" go run ./cmd/nwn-tool --help

Repository Layout

cmd/nwn-tool/      CLI entrypoint
internal/app/      command wiring and console UX
internal/erf/      ERF/MOD/HAK reading and writing
internal/gff/      canonical GFF JSON and binary conversion
internal/pipeline/ build, extract, compare, and manifest workflows
internal/project/  config loading and repo scanning
internal/validator/validation and diagnostics
tools/             built development binary output

Intended Consumers

sow-module uses sow-toolkit for build-module, extract, validate, compare, and apply-hak-manifest
sow-assets uses sow-toolkit for build-haks and validation
- validation now fails early if duplicate asset resources would collide inside the same generated HAK
- duplicate resources split across different HAK groups remain warnings because later HAK order can still override earlier content at runtime
sow-module now also uses sow-toolkit for topdata:
- validate-topdata
- build-topdata
- compare-topdata
- convert-topdata

During development, sibling repositories can point at ../sow-tools/tools/sow-toolkit. For pinned releases, each consumer repo can instead carry its own copy at tools/sow-toolkit.

Release Automation

This repo publishes:

sow-toolkit-linux-amd64.tar.gz
sow-toolkit-windows-amd64.exe

Consumer repos can fetch those binaries into their local tools/ directory with:

install-tool.sh on Linux/macOS
install-tool.ps1 on Windows

TopData

The native topdata system is implemented in this repo and authored in sow-module.

High-level ownership split:

sow-tools
- owns the sow-toolkit implementation
- owns topdata validation, build, compare, conversion, and dataset-resolution logic
sow-module
- owns canonical topdata authored data under topdata/data/
- owns the user-facing topdata workflow scripts

For a human-readable front-to-back explanation of how the native topdata builder works and how to use it, see:

sow-module/topdata/README.md

Important topdata contracts still live here under internal/topdata/ because they are code-adjacent implementation contracts, not user workflow docs.

2.5 KiB Raw Blame History