console-controller

Controller Mapper. Hooks the game up to any controller: DualSense, Xbox, Switch Pro, keyboard or touch, remapped how you like. Reads a mapping in console/controls.json (a layout preset plus per-button overrides, radial deadzone, invert Y, stick swap, analog trigger threshold, keyboard keys, two players, Android touch zones) and writes console/ps2_pad.cpp, a drop-in replacement for PS2Recomp's ps2xRuntime/src/lib/ps2_pad.cpp with the same class, signature and DualShock 2 report. Optional input replay and recording for scripted test runs. Backs up the stock file before installing and only touches the PS2Recomp checkout you name. Use when the user says "my controller doesn't work", "remap the buttons", "use my Xbox pad", "Switch Pro buttons are swapped", "invert the camera", "keyboard controls", "two players", "touch controls on Android", or when /console-tester needs scripted input.

Jump to install Review files

Repository: Jakeschincariol/console-skill
Last source activity: October 22, 2026 at 14:14
Detected SKILL.md language: English
Stars: 288
Forks: 37

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with an AI assistant

Copy this prompt into the AI assistant you're using.

Follow https://skillsmp.com/skill-install/prompt.md to install only the Agent Skill at https://github.com/Jakeschincariol/console-skill/tree/main/console-controller.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/Jakeschincariol/console-skill --skill console-controller

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

5 files

SKILL.md

Source instructions · Read-only preview

name: console-controller
description: Controller Mapper. Hooks the game up to any controller: DualSense, Xbox, Switch Pro, keyboard or touch, remapped how you like. Reads a mapping in console/controls.json (a layout preset plus per-button overrides, radial deadzone, invert Y, stick swap, analog trigger threshold, keyboard keys, two players, Android touch zones) and writes console/ps2_pad.cpp, a drop-in replacement for PS2Recomp's ps2xRuntime/src/lib/ps2_pad.cpp with the same class, signature and DualShock 2 report. Optional input replay and recording for scripted test runs. Backs up the stock file before installing and only touches the PS2Recomp checkout you name. Use when the user says "my controller doesn't work", "remap the buttons", "use my Xbox pad", "Switch Pro buttons are swapped", "invert the camera", "keyboard controls", "two players", "touch controls on Android", or when /console-tester needs scripted input.
argument-hint: init|check|gen|install|restore|presets|table [flags]

# console-controller The recompiled game asks the runtime for the pad state many times a second through `PSPadBackend::readState(int port, int slot, uint8_t *data, size_t size)` in `ps2xRuntime/src/lib/ps2_pad.cpp`. The stock file maps raylib's gamepad 0 and a fixed keyboard layout onto the 32-byte DualShock 2 report. This skill replaces that one file with a generated one built from your `console/controls.json`, so any controller raylib can see becomes a DualShock 2, mapped your way. Nothing else in the runtime changes, so the rebuild is incremental. Honest limits: rumble is not wired in the runtime, pressure-sensitive buttons are reported as fully pressed or not pressed, and touch zones on Android are invisible (the runtime draws no overlay). `${CLAUDE_SKILL_DIR}` below is this skill's folder (where this SKILL.md lives). ```bash python3 "${CLAUDE_SKILL_DIR}/padmap.py" init --layout xbox # writes console/controls.json python3 "${CLAUDE_SKILL_DIR}/padmap.py" check # every DS2 button bound, no clashes python3 "${CLAUDE_SKILL_DIR}/padmap.py" gen --replay # writes console/ps2_pad.cpp python3 "${CLAUDE_SKILL_DIR}/padmap.py" install --repo ~/PS2Recomp # backs up, then copies it in python3 "${CLAUDE_SKILL_DIR}/padmap.py" restore --repo ~/PS2Recomp # puts the stock file back python3 "${CLAUDE_SKILL_DIR}/padmap.py" presets switch-labels # playstation xbox switch switch-labels keyboard python3 "${CLAUDE_SKILL_DIR}/padmap.py" table # the DS2 bit table python3 "${CLAUDE_SKILL_DIR}/padmap.py" check --script console/inputs/menu.txt # validate a replay script ``` Flags: `--config FILE` (default `console/controls.json`; the preset alone is used if it is missing), `--layout NAME`, `--out FILE` (`-` for stdout), `--json`, `--strict` (warnings fail `check`), `--backups DIR` (default `console/backups`). Exit codes: 0 ok, 1 `check` found a problem, 2 bad input. ## What it reads and writes | file | what | | --- | --- | | `console/controls.json` | your mapping: `layout` + overrides. Full format: [reference/controls-json.md](reference/controls-json.md) | | `console/ps2_pad.cpp` | the generated drop-in pad file (from `gen`) | | `<PS2Recomp>/ps2xRuntime/src/lib/ps2_pad.cpp` | replaced by `install`, only when you pass `--repo` | | `console/backups/ps2_pad.cpp.orig` | the stock file, saved once and never overwritten; later installs also keep a timestamped copy | | `templates/menu-walk.txt` | an example input replay script to copy and edit | ## The DualShock 2 report the file fills `data[0] = 0x01`, `data[1] = 0x73` (analog), buttons ACTIVE-LOW in `data[2]` (low byte) and `data[3]` (high byte), so `0xFFFF` means nothing pressed. Sticks: `data[4]` RX, `data[5]` RY, `data[6]` LX, `data[7]` LY, `0x80` centre, `0x00` full left or up. Bits: SELECT 0x0001, L3 0x0002, R3 0x0004, START 0x0008, UP 0x0010, RIGHT 0x0020, DOWN 0x0040, LEFT 0x0080, L2 0x0100, R2 0x0200, L1 0x0400, R1 0x0800, TRIANGLE 0x1000, CIRCLE 0x2000, CROSS 0x4000, SQUARE 0x8000. `Kernel/Stubs/Pad.cpp` copies bytes 2 to 7 into the game's pad buffer, sets the mode byte itself (digital 0x41 until the game switches the pad to analog) and fills the pressure bytes as 0xFF or 0. ## Method 1. **Find out what they play with.** Controller model, how it connects (USB or Bluetooth), which OS, one or two players, and whether they want keyboard or touch. If a button already lands in the wrong place, ask which physical button they pressed and what the game did. 2. **Start from a preset.** `init --layout playstation|xbox|switch|switch-labels|keyboard`. raylib reports pads by POSITION: the bottom face button is Cross on every pad (Xbox A, Nintendo B). `switch-labels` matches Nintendo's printed letters instead (A, on the right, is Cross). Details and why some Switch Pro setups arrive already swapped: [reference/controllers.md](reference/controllers.md). 3. **Apply the user's changes** in `controls.json`: `buttons` overrides, `keyboard` keys, `deadzone` (radial, default 0.15), `invert_y` (`true` means the right stick, the camera in most games), `stick_swap`, `trigger_threshold` (reads L2/R2 from the analog trigger axes), `players: 2` (port 2 gets the second pad), `touch` zones for Android. Keep it a mapping, never game code. 4. **Check.** `padmap.py check`. Fix every ERROR. Read the warnings out: Escape quits the game (raylib's default exit key; the runtime never changes it) and F1 opens the debug panel on desktop builds with the debug UI. 5. **Generate.** `padmap.py gen` (add `--replay` when /console-tester will drive scripted runs). 6. **Install.** `padmap.py install --repo <their PS2Recomp checkout>` backs the stock file up to `console/backups/ps2_pad.cpp.orig` and copies the new one in. Then the normal incremental build (`cmake --build <build dir>`, the same command recorded in `console/STATE.md`). One `.cpp` changes and no header does, so it is quick. Never clean the build for this. 7. **Test with the controller in hand.** Run the port, press every button once in a menu that reacts to all of them (or a game's controller test screen). If one is wrong, change `controls.json`, `gen`, `install`, rebuild. Log the result in `console/STATE.md`. 8. **Scripted input for tests** (with `--replay`): set `PS2X_INPUT_RECORD=console/inputs/run1.txt`, play the bit you want to repeat, quit; that file replays with `PS2X_INPUT_SCRIPT` (which `/console-tester`'s `run.py --input` sets for you). The format is in [reference/controls-json.md](reference/controls-json.md). Frame numbers count the game's reads of pad port 0, so a script stays in step with the game, not with the wall clock. ## Rumble, pressure, analog, touch | feature | status in this PS2Recomp checkout | | --- | --- | | Rumble | not wired: `scePadSetActDirect` and `scePadSetActAlign` in `Kernel/Stubs/Pad.cpp` return 1 and do nothing (`scePadInfoAct` reports two motors). Adding it is runtime C++ work for /console-backend, not a mapping | | Pressure-sensitive buttons | digital: when a game turns pressure mode on, `Pad.cpp` reports 0xFF for a pressed button and 0 otherwise | | Analog mode | the game switches it (`scePadSetMainMode`); sticks are always sent and the game ignores them in digital mode | | Touch (Android) | `ps2_android_runtime.cpp` is only a TODO for an on-screen overlay, so the stock port has no touch controls. `touch` zones work as invisible areas; a Bluetooth controller is the better answer | | Two players | the stock file feeds the same pad to both ports; the generated one gives port 2 its own pad with `players: 2`, or a released pad otherwise | ## Guard rails - **Bring your own game.** Only games you own, dumped from your own disc. Never download ISOs, ELFs or BIOS files, never help find them. PS2Recomp needs no BIOS. - **Nothing from the game gets published.** The disc, ELF, IRX modules, assets and the recompiled `runner/*.cpp` stay on your machine. A `controls.json`, a generated `ps2_pad.cpp` and replay scripts you wrote are yours to share. - **Not affiliated with Sony.** PlayStation and DualShock are trademarks of Sony Interactive Entertainment. DualSense, Xbox and Nintendo Switch belong to their owners. - **Back up, then replace one file.** `install` refuses a source it did not generate, never overwrites the `.orig` backup, and touches only the checkout you name. Never edit headers (`ps2_pad.h` included: a header change rebuilds every generated file) and never clean the build. ## Hands off to - `/console-tester` to run the port with a replay script (`run.py boot --input ...`). - `/console-anywhere` to build for the device the controller is for (Steam Deck, Android, Vita). - `/console-backend` if the game needs rumble or a pad call the runtime does not implement yet.

View on GitHub

Back to search Back to installation

console-anywhere

Play Anywhere. Builds the port for Windows, Mac, Linux, Steam Deck, Android and PS Vita and packages it without any game files inside. doctor checks this machine's tools for a target and prints the exact install command for anything missing; plan prints the build steps taken from PS2Recomp's own README, android/README.md and vita scripts; package makes a player folder in console/dist/ (the runner, its libraries, an empty game/ folder, PLAYERS.md, a launch script, .recomp.json) and refuses outright if a disc image, PS2 ELF, IRX module, recompiled runner source or other game data is inside; guard runs that check on any folder; recomp-json writes the project's optional .recomp.json. Use when the user says "put it on my Steam Deck", "build it for Android", "play it on my phone", "on my TV", "Vita build", "Mac build", "package it", "make a release folder", "is it safe to zip this", or after the port plays on the machine it was built on.

2026-10-22

console-backend

Backend Engineer. Builds the engine room the recompiled game runs on: syscalls, kernel stubs, file and disc I/O, the IOP. Reads PS2Recomp runtime logs and turns every "Unimplemented PS2 stub", "[Syscall TODO]", missing function, unhandled IOP RPC, failed disc read and untranslated instruction into a ranked fix list: count, first PC and RA, and the exact fix tool (a TOML binding, the runtime .cpp file to implement it in, an entry point and a recompile, or a game override). With the user's PS2Recomp checkout it reads the real handler names and syscall numbers. Writes nothing into the checkout; prints a table for console/STATE.md. Use when the user says "unimplemented stub", "syscall TODO", "it crashes at boot", "fix the backend", "it can't find a file", "the IOP", "what is syscall 0x3C", or after /console-tester reports a stop.

2026-10-22

console-graphics

Graphics Artist. Rebuilds the graphics: dumps every texture, lets you repaint or replace them with your own art, finds the widescreen fix. Converts PS2 TIM2 textures (.tm2, 32/24/16-bit and 8/4-bit indexed) from the user's own extracted disc to PNG, rebuilds them from edited PNGs at the same size and format (GS registers kept, palettes refit or quantised), finds TIM2 blobs inside archives and puts edited ones back, and lists the 4:3 aspect and FOV constants in the ELF with 16:9 pnach lines to try in PCSX2. Reads the packets the game sends the GS from a RAM dump (DMA chains, VIF codes, GIF tags, every register write) and flags what breaks rendering. Writes to console/textures/ and console/patches/, never into the disc image. Use when the user says "dump the textures", "repaint", "replace this texture", "my own art", "HD textures", "make it widescreen", "16:9", "the picture is stretched", "black screen", "garbage textures", "nothing draws", or "how does the port draw".

2026-10-22

View all from this repository

console-controller

Source facts

Install options

Install with an AI assistant

Review the source files

More from this repository

Install with an AI assistant

More from this repository