Releases: ShugokiFable/SaintsRowForge
Release list
v0.2.2 — cold-start fixes
Fixes found by an independent cold-start audit that executed the README quickstart literally:
srforge mod patchnow self-extracts job files likemod build— the documented new → patch → diff → build order works with zero extra steps (was SRF-JOB-002).mod newcreates source/jobs/ out of the box, so the documented job-file location exists.
Asset = clean source archive of this tag.
ZIP SHA256: \744119b8c3105fd9dedd50b2d67df59fd3ad19beb5f0a6de9bcf7caab49e2e96
v0.2.1 — installer + docs refresh
Fixes since v0.2.0
- Install.ps1 / Update.ps1 now robocopy-/MIR code dirs — updates truly replace stale files (old Copy-Item merged), and knowledge/ + scripts/ now ship in installs
- README: 5-minute new-user quickstart (install → first mod → installing your mod → merging two mods)
- MCP:
sr_knowledge_searchtool (13 total) - Knowledge layer integrated (GPT pack, reviewed): format notes, SDK adapter recipes, upstream source map
Asset SHA256
\eabb113e29c18344e8ef72444637d6412ff599dfc5cbb84e80e95b4cd1a1e4e5
v0.2.0 — mod manager (cross-mod table merge) + knowledge layer
What's new
Mod manager: cross-mod table merge (srforge merge)
Saints Row mods ship full copies of shared tables, so installing two mods that both touch weapons.xtbl normally means last-one-wins data loss. Forge now three-way merges every shared .xtbl against vanilla:
- additions from any mod -> all survive
- distinct edits to the same record -> all applied
- same-field conflicts -> logged in
merge-report.json, later-listed mod wins, nothing silently lost - non-table collisions (
str2_pc,asm_pc) flagged, not merged
Validated end-to-end on real SRIV data: 4 edits applied, 2 record additions unioned, 1 true conflict correctly reported, package reopen-verified.
External knowledge layer (community pack, reviewed)
knowledge/: 10 reference docs +SOURCES.jsonupstream provenance map (Volition SDKs, ThomasJepp, Gibbed, SRZoneTools, SaintsRowMods)scripts/KnowledgeSearch.py: zero-dependency local searchscripts/Fetch-Upstream-References.ps1: optional source fetcher with SHA-256 manifests (kept out of executabletools_vault)- New MCP tool sr_knowledge_search - server is now 13 tools, wire-verified
Also: XTBL serializer fidelity fix (mixed-content text preserved), index-aware handling of repeated tags (Projectile_Info x2), CI badge green.
SHA256 of attached zip: \01fc4b3d327f07e7239e99982a1e046256b1be0d9fdd1aa263fe4fea6f5e5ea3
SaintsRowForge v0.1.0 — first public release
AI-operable Saints Row: The Third + Saints Row IV modding workbench.
Format engines (native, stdlib-only Python):
- VPP archives — SRIV v0x0A and SRTT v0x06, read + write, tolerant inflate
- STR2/ASM containers — parse + byte-perfect rebuild, container size sync
- XTBL tables — parse, semantic diff, edit
- le_strings files — parse + rebuild
Mod manager:
srforge merge— three-way cross-mod table merge against vanilla: additions unioned, distinct edits coexist, same-field conflicts reported (never silently lost), later-listed mod wins. Non-table collisions flagged.- Transactional mod pipeline: extract → patch → diff → build → reopen-verified package with sha256 receipts
Interfaces:
srforgeCLI with JSON output everywhere- Dependency-free MCP server (12 typed tools) for AI agent integration
- Capability registry that refuses to claim what isn't proven
Safety:
- Vanilla game files are never written; all output goes to workspace/release paths
- External tooling is user-acquired with pinned sha256 provenance, never redistributed
Requirements: Python 3.10+ (Windows; game installs auto-detected via Steam libraries)
Install: unzip, run powershell -File Install.ps1, then START-HERE.bat.
Tests: python tests/run_tests.py — 18 checks.
SHA256 of attached source zip: 6d2ee8adde10d31733c9c009503b183f6107f04d186d5376a9885fbd7ab72e92