Step 1: the Salty project, two modules, tests and the gym

Salty.uproject (UE 5.8) from the Third Person template with class redirects, the SaltyCore and Salty modules,
the three build targets, USaltyAssetManager calling InitGlobalData, Config/Tags with the 23 root namespaces,
Scripts/run-tests.sh, build.sh and Authoring/create_gym.py, L_Gym, Git LFS attributes and the placeholder test.
Template variants kept as reference (D-41). The four Fab packs stay out of the repository for now (~10 GB).
The editor serves the engine MCP plugin on 127.0.0.1:8000 through DefaultEditorPerProjectUserSettings.ini.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
Rainer Leit
2026-09-16 20:10:43 +03:00
co-authored by Claude Fable 5.1
parent 0e61a77346
commit 4f2c55cd2a
1434 changed files with 11358 additions and 27 deletions
+6 -6
View File
@@ -4,7 +4,7 @@ An Unreal Engine 5 project that builds three things in order and proves each one
built around it: a movement controller, fighting, and crafting. Server-authoritative from the first line, C++
first, data-driven, telemetry from step 2, and worked as a ladder of small proofs rather than a roadmap.
Nothing is built yet. The repository currently holds the documentation set.
Step 1 is built: `Salty.uproject` on Unreal Engine 5.8, two modules, the headless test runner and the gym. Step 2 (telemetry) is next.
## Read
@@ -22,16 +22,16 @@ UnrealEnginePrototyping/
├── CLAUDE.md Instructions for an AI agent: conventions, layout, commands, upkeep.
├── README.md This file.
├── Docs/ Design, steps, ideas, decisions, worklog, and Spec/ with one document per system.
├── <Project>.uproject Created in step 1, at the root, which is what the .gitignore assumes.
├── Source/ <Project>Core (rules, no actors) and <Project> (gameplay).
├── Content/ Assets, one folder per feature; Maps/L_Gym; Tests/.
├── Salty.uproject Unreal Engine 5.8. At the root, which is what the .gitignore assumes.
├── Source/ SaltyCore (rules, no actors) and Salty (gameplay). Variant_* is template reference.
├── Content/ Assets, one folder per feature; Maps/L_Gym; Tests/; the Fab packs.
├── Config/ Engine and game config; Tags/ holds the gameplay tag sources.
└── Scripts/ Test and build scripts run by hand; Authoring/ for editor Python.
```
## Getting started
After step 1: open `<Project>.uproject` with the pinned engine version, run `Scripts/run-tests.sh`, and press Play
in `L_Gym` with two clients and "Run Dedicated Server" on. Until then there is nothing to run.
Open `Salty.uproject` with Unreal Engine 5.8, run `Scripts/run-tests.sh`, and press Play in `L_Gym` with two
clients and "Run Dedicated Server" on. `Scripts/Authoring/create_gym.py` rebuilds the gym.
Binary assets go through Git LFS; run `git lfs install` once per machine.