> For the complete documentation index, see [llms.txt](https://8bitmods.gitbook.io/manuals/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://8bitmods.gitbook.io/manuals/gameid/ps2.md).

# PS2 GameID

## MMCE-aware loaders

OPL and Neutrino talk to the device directly and send the game ID before launching. This is the most reliable method and needs no extra setup beyond enabling MMCE support in the loader. See [OPL and Neutrino setup](/manuals/mmce/loaders.md).

## Launch history

When no loader sends an ID, the device watches the mounted card for the PS2's launch history file, which the console updates every time a disc or executable is started. The device reads the last launched title from it and switches card.

This works with retail discs and with any loader that lets the PS2 write its history file. Because the history is written after the game has started, the first save of a session may land on the previous card if the game saves immediately on boot.

## Card switching from the loader

Loaders can also ask the device to mount a specific card and channel, or return to the boot card, without a game ID. OPL's **IGR boot card** option uses this.

## uLaunchELF and wLaunchELF

The device delays acknowledging the card for a moment after switching so that file managers notice the change and re-read the card.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://8bitmods.gitbook.io/manuals/gameid/ps2.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.