mirror of
https://github.com/luckeyfaraday/bo3-workshop-ps4.git
synced 2026-10-17 18:02:40 +02:00
luckeyfaradayandClaude Opus 5.5
3353d9688d
bo3ps4.py: SteamCMD download -> convert -> check -> FTP upload, GoldHEN plugin setup, PS4 zone pull, language zones, compatibility list. patches/: FFPorter (PS4-BO3-Customs v1.50) fixes so conversions work without Sony's shader compiler, using shaders from the console's own zones; plus GSC table fixes. scripts/build-ffport.ps1 builds it. Tested: LEVIATHAN, Minecraft v1.2 and Cheese Cube play on an EU PS4. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
886 B
886 B
Contributing
The most useful thing right now is testing maps. Port one, play it, and open a Map report issue, or add a row to COMPATIBILITY.md in a PR.
Fixing a map usually means fixing the converter. Converter changes live in patches/ffporter-fixes.diff, against
PS4-BO3-Customs v1.50:
scripts\build-ffport.ps1clones and patches the source intoupstream\src.- Edit it there, rebuild (
dotnet publishas in the script), and test on the map. - Regenerate the diff from
upstream\src(git -C upstream\src diff -- Tool/src/*.cs > patches\ffporter-fixes.diff) and include the map that made you do it in the PR.
Changes to the t7_gsc data tables go in patches/apply-data-fixes.py.
Ground rules: never commit game files (fastfiles, xpaks, sound banks, executables or dumps of them), converted maps, or logs with account names in them.