0 Fork 0

Files

T

zwitschi 4d27109668 refactor(tools): group the sixty scripts by what they talk to

One directory with sixty scripts stopped being navigable, and the grouping is also the sandbox boundary:

  Tools/unreal/    commandlets and the two map builders, with ue_common.py and ue_placement.py as the
                   shared imports (they need the engine)
  Tools/blender/   builders, exporters, the FBX preset, the MPFB character pipeline, blender_screenshots
                   (they need the Blender Flatpak)
  Tools/review/    the visual loop: render_screenshots.sh, judge_screenshot.py, hero_compare.py,
                   build_comparison_md.py, e2e_asset_check.py, hero_iterate.sh, visual_loop.py,
                   visual_targets.json
  Tools/gen/       image and texture generation: the ComfyUI driver, deterministic texture writers,
                   reference fetching
  Tools/input/     OS-level input injection
  root             _common.py, check-lfs.sh, addon_compat_probe.py, sibling_asset_audit.py, tests/

Every moved script now resolves the repository root as ../.. and puts the tools root plus its siblings on
sys.path, so 'import ue_common' still works from unreal/. The test suite bootstrap does the same for the five
folders. render_screenshots.sh takes the folder as a third argument to run_cmdlet, and the e2e driver,
hero_iterate.sh and the comparison generator were repointed.

51 README rows now link to their new location, the README gains a Layout section naming each folder's
sandbox, and the architecture notes and Blender README follow the moves.

Verified: 108 tests pass, prettier is clean, judge_screenshot.py and hero_compare.py run from their new
homes, and the e2e run was aborted mid-way (it had been rebuilding an empty DemoMap for 15 minutes) and is
being rerun against the new layout.

2026-11-10 12:40:30 +01:00

blender

refactor(tools): group the sixty scripts by what they talk to

2026-11-10 12:40:30 +01:00

characters/blueprints

fix(clothing): close the coverage holes, and bind materials without crashing

2026-11-09 13:50:21 +01:00

props

refs: survey the sibling project and recalibrate the hero facade

2026-11-07 12:20:41 +01:00

textures/generated

feat(hero): generate the stone albedo with the new texture tool, import it, wire it into the material

2026-11-10 11:58:39 +01:00

README.md

chore: keep reference photography local and out of the repository

2026-11-06 22:04:37 +01:00

README.md

Art

Editable sources and original textures. Exported, game-ready output goes to Game/Content/.

Layout (as content arrives)

Path	Contents
`Art/blender/`	`.blend` sources, one file per building or asset family
`Art/textures/`	Original texture sources before baking or compression
`Art/reference/`	Reference photography, local only, gitignored — never committed. Fetch with `Tools/commons_fetch.py`; what it is evidence for goes in `Docs/reference-notes-hollywood.md`

Rules

Every .blend saves with a real-world metric scene scale. No exceptions; scale drift is the main source of import defects.
Named export presets only. Record the preset name and its settings next to the asset that used it.
Textures enter as a documented source (author, licence, source URL) and are listed in ../THIRD_PARTY_NOTICES.md.
Reference photography is never committed and never shipped. It is evidence, not content. Licensing is not a gate for local private development, but anything that would derive from a reference in a shipped asset needs a licensing decision before release.
.blend files are LFS-tracked and lockable; pull before editing.