SplitScript reference / PS2
PS2
state provider
state PS2
Attaches to a supported PlayStation 2 emulator.
The provider discovers the emulator's main RAM mapping and exposes original PS2 addresses through the read-only ps2 value of type PS2Emulator. PCSX2 and 64-bit RetroArch using pcsx2_libretro.dll are supported. Declare guest addresses directly instead of recreating emulator-specific DeepPointer mappings.
Examples
Read PS2 memory
state PS2 {
health: u16 at 0x00123456
}
Value type
| Member | Description | Available through |
|---|---|---|
| PS2Emulator | Retains a discovered PlayStation 2 emulator memory mapping. |
Readable guest memory
0x00100000..<0x02000000(exclusive upper bound)
A read must fit entirely inside one range. Literal addresses are checked during compilation; computed addresses remain fallible and are checked at runtime.
Mapping lifecycle
The provider validates its private memory mapping before each state poll. If that mapping disappears while the host process remains open, the current logical attachment ends: attachment-scoped state and pending continuations are cleared, and onDetach runs if onAttach had completed. Discovery then continues cooperatively against the same host process. A replacement mapping starts a new attachment, runs onAttach again, and establishes a fresh old / current baseline.