mirror of
https://github.com/hrydgard/ppsspp.git
synced 2026-10-22 02:39:05 +02:00
LunaMooandClaude Opus 5.5
3e175060dd
PSPAR code types run the way TempAR's cheat_apply_pspar() runs them: writes, 32-bit and masked 16-bit conditions with the D0 terminator stack, load/set/add/write offset, C0 loops with D1/D2, the Dx data register codes, patch (0x0E), memory copy (0x0F) and the safe data store (0xC4), which lets a cheat write over its own lines. PSPAR's button codes (type 9/A at 0x09F00000 and up) read the real pad, like TempAR's hijack option, as does TempAR's fake pad address 0x0A000000. TempAR's _N extensions aren't supported, and folder codes (0xCF) do nothing. Lines can now end in a # or // comment, a cheat can't mix _L and _M lines, and importing from cheat.db keeps _M lines. The unit test runs the PSPAR tests from TempAR's tests.db. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>