> For the complete documentation index, see [llms.txt](https://wiki.retrobat.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.retrobat.org/controllers/supported-controllers/gamepads/special-controllers.md). # Special controllers For some systems, RetroBat recognises controllers that reproduce the original console pad (N64 controllers, Genesis/Saturn-style pads, GameCube adapters…) and maps them **button for button**, so that each button does exactly what it did on the original console. These mappings are stored in `.json` files. RetroBat already provides mappings for the controllers listed on this page, and you can add your own. {% hint style="info" %} When a special controller is detected, the mapping you configured in RetroBat (CONTROLLER SETTINGS) is ignored for this controller: the mapping from the `.json` file is used instead. {% endhint %} ## How it works RetroBat identifies the controller by its **GUID** (and, for RetroArch, by the input driver in use). Two cases exist:

Case	Behaviour
Automatic	Controllers with a unique identifier (adapters, 8BitDo pads in D-input mode, Nintendo Switch Online N64 controller…). The special mapping is applied as soon as the controller is connected.
Needs activation	Controllers that share their identifier with standard pads (for example an 8BitDo M30 in X-input mode is seen as an Xbox 360 controller). The special mapping is only applied if you enable the matching option in the system's advanced configuration, CONTROLS submenu.

{% hint style="warning" %} Only enable the **USE xxx-LIKE CONTROLLER** options when you actually play with one of the controllers listed below. Otherwise, a standard Xbox or Switch controller may receive the special mapping and its buttons will be wrong. {% endhint %} To check that a special mapping was applied, open `emulationstation\emulatorLauncher.log` after launching a game and look for a line like `Performing specific … mapping for `. ## Mapping files The files are located in `system\resources\inputmapping`:

File	Systems
`n64Controllers.json`	Nintendo 64
`mdControllers.json`	Mega Drive / Genesis, Mega-CD / Sega CD, 32X
`saturnControllers.json`	Saturn
`GCControllers.json`	GameCube
`3doControllers.json`	3DO
`arcade_sticks.json`	Custom arcade stick mapping (RetroArch)
`kbpads\*.yml`	Arcade sticks recognised as a keyboard (I-PAC2, X-Arcade Tankstick)

{% hint style="info" %} If you modify a file, copy it to `user\inputmapping` (`user\inputmapping\kbpads` for `.yml` files) and edit the copy. RetroBat reads this folder first, and it is not overwritten by updates. {% endhint %} ## Nintendo 64

Controller	RetroArch	Ares	BizHawk	RMG	Simple64	Ship ports
Nintendo Switch Online N64 Controller	Auto	Auto	Auto	Auto	Auto	Auto
8BitDo N64 Controller	Auto	Auto	Auto	Auto	Auto	–
Mayflash N64 adapter	Auto	Auto	Auto	Auto	Auto	Auto
Raphnet N64 adapter	Auto	Auto	Auto	Auto	Auto	Auto
SWITCH CO.LTD. USB Controller (D-input/SDL)	Auto	–	Auto	–	–	–
SWITCH CO.LTD. USB Controller (X-input)	Option	Option	Option	Option	Option	–

* **RetroArch**: Mupen64Plus-Next and ParaLLEl N64 cores. * **BizHawk**: Ares64 and Mupen64Plus cores. * **RMG**: Rosalie's Mupen GUI (Mupen64Plus). * **Ship ports**: Ship of Harkinian, 2 Ship 2 Harkinian, Ghostship. * **Option**: **USE N64-LIKE CONTROLLER** (system advanced configuration > CONTROLS). ### N64 TRIGGER INVERT On controllers with two triggers (Nintendo Switch Online N64 controller, 8BitDo N64 controller), the **Z** button is mapped to the left trigger by default. Enable **N64 TRIGGER INVERT** to use the right trigger instead. This is a global option: **GAME SETTINGS > CONTROLS > SPECIAL CONTROLLERS > N64 TRIGGER INVERT**. It works with RetroArch, Ares, BizHawk, RMG and Simple64.

## Mega Drive / Genesis (and Mega-CD, 32X) Supported controller: **8BitDo M30** (the mode depends on how it is connected and switched on; see the [Gamepads](/controllers/supported-controllers/gamepads.md) page).

M30 mode	Activation
X-input	Option
Switch	Option
D-input	Auto
2.4G receiver	Auto

* **Emulators**: RetroArch (Genesis Plus GX, Genesis Plus GX Wide, Genesis Plus GX Expanded and PicoDrive cores), Ares, BizHawk (Genplus-gx, PicoDrive), BlastEm, Jgenesis, Kega Fusion, Mednafen. * **Option**: **USE GENESIS-LIKE CONTROLLER** (system advanced configuration > CONTROLS). In Kega Fusion, the option lets you choose **YES (DPAD)** or **YES (ANALOG)**.

## Saturn Supported controller: **8BitDo M30**.

M30 mode	RetroArch	BizHawk	Mednafen	Kronos	SSF	YabaSanshiro	Ymir
X-input	Option	Option	Option	Option	Option	Option	Option
Switch	Option	Option	–	Option	Option	Option	Option
D-input	Auto	Auto	Auto	Option	Auto	Option	Option
2.4G receiver	Auto	Auto	Auto	Auto	Not supported	Auto	Not supported

* **RetroArch**: Beetle Saturn, Kronos, YabaSanshiro, Yabause and Ymir cores. * **BizHawk**: Saturnus core. * **Option**: **USE SATURN-LIKE CONTROLLER** (system advanced configuration > CONTROLS). In Kronos, SSF and YabaSanshiro, choose **YES (DPAD)** or **YES (ANALOG)**.

## GameCube Special mappings for GameCube controllers are only available with **Dolphin** (standalone), for the GameCube and Triforce systems. | Adapter | Activation | | ---------------------------------------------- | ---------- | | Mayflash GameCube Controller Adapter (PC mode) | Auto | | raphnet Dual GameCube to USB adapter | Auto | The **USE GAMECUBE-LIKE CONTROLLER** option is available for entries that need activation (none in the provided file at the moment). ### Wii U GameCube adapter (official or Mayflash in Wii U mode) Dolphin can use this adapter directly (rumble supported, all 4 ports): 1. Install the WinUSB driver for the adapter with [Zadig](https://zadig.akeo.ie/), as explained in the [Dolphin guide](https://dolphin-emu.org/docs/guides/how-use-official-gc-controller-adapter-wii-u/). 2. In the GameCube system advanced configuration > CONTROLS, set **PLAYER 1 CONTROLLER TYPE** (and players 2 to 4 if needed) to **GAMECUBE ADAPTER**. ## 3DO Supported controller: **8BitDo M30**, with the **RetroArch Opera** core.

M30 mode	Activation
X-input	Option
Switch	Option
D-input	Auto
2.4G receiver	Auto

**Option**: **USE 3DO-LIKE CONTROLLER** (system advanced configuration > CONTROLS). ## Wiimotes (Wii) With **Dolphin** (standalone), the **WIIMOTE TYPE** option (Wii system advanced configuration > CONTROLS) defines how Wii controllers are handled:

Value	Behaviour
REAL (default)	Real Wiimotes, connected via Bluetooth or with a Mayflash DolphinBar in mode 4.
EMULATED	Your gamepads act as Wiimotes. Choose the emulated device (Wiimote, sideways Wiimote, Nunchuk, Classic Controller…) with EMULATED DEVICES.
REAL AS EMULATED / (NUNCHUK) / (CC)	A real Wiimote is used through Dolphin's emulated Wiimote, without extension, with a Nunchuk or with a Classic Controller.

Other useful options: * **NUMBER OF WIIMOTES**: forces the number of Wiimotes the game detects (set it to 1 for games that switch to multiplayer as soon as several controllers are connected). * **USE GAMECUBE CONTROLLERS**: also configures your gamepads as GameCube controllers, for Wii games that support them. * **DISABLE WIIMOTE CONTINUOUS SCANNING**: RetroBat automatically disables continuous scanning when a DolphinBar is detected, when Wiimotes are emulated, and for GameCube games. Set this option to force the behaviour. To use a Wiimote as a lightgun, see the [Wiimote and DolphinBar](/controllers/supported-controllers/lightguns/wiimoteandbar.md) page. ## Arcade sticks recognised as a keyboard (I-PAC2, X-Arcade Tankstick) Some arcade sticks and encoders are seen by Windows as a **keyboard** (Ultimarc I-PAC2, X-Arcade Tankstick…). Their keys follow the MAME defaults (player 1: arrows, Left Ctrl, Left Alt, Space…, Start `1`, Coin `5`; player 2: `R`/`F`/`D`/`G`, `A`, `S`…, Start `2`, Coin `6`).

Emulator	How to configure
RetroArch	GAME SETTINGS > RETROARCH OPTIONS > CONTROLS > CONFIGURE SPECIAL KEYBOARD STICK: choose IPAC2 or X-ARCADE TANKSTICK. Applies to all RetroArch games.
MAME (standalone, GroovyMAME and HBMame)	System advanced configuration > CONTROLS > CONTROLLER PROFILE: choose IPAC2 or X-ARCADE. The profiles are located in `saves\mame\ctrlr`; you can also create your own profiles (CUSTOM 1 to 6) or one profile per game (GAME SPECIFIC, file named after the rom).
PCSX2x6 (Namco System 246/256)	System advanced configuration > CONTROLS > CONFIGURE SPECIAL KEYBOARD STICK.

The RetroArch and PCSX2x6 mappings come from `kbpads\libretro_.yml` and `kbpads\pcsx2x6_.yml`. Each file has a `default` block, and you can add blocks named after a **system**, a **core** (RetroArch only) or a **rom** (file name without extension). They are applied in this order: `default` → system → core → game, and you only need to list what changes. Example (`user\inputmapping\kbpads\libretro_ipac2.yml`): ```yaml default: input_player1_a: ctrl input_player1_b: alt # ... snes: input_player1_a: alt input_player1_b: ctrl ``` ## Custom arcade stick mapping (RetroArch) For an arcade stick recognised as a **gamepad**, you can define a dedicated RetroArch mapping: 1. Copy `system\resources\inputmapping\arcade_sticks.json` to `user\inputmapping`. 2. Replace the example entry (`Arcade Stick Test`) with the GUID of your stick and your mapping. 3. Enable **GAME SETTINGS > RETROARCH OPTIONS > CONTROLS > USE CUSTOM ARCADE STICK MAPPING**. ## Adding your own controller 1. Copy the `.json` file of the system to `user\inputmapping`. 2. Find the GUID of your controller: it is the `deviceGUID` value in `emulationstation\.emulationstation\es_input.cfg`. 3. Duplicate an existing entry **for the same emulator** (the mapping format differs for each emulator) and change `Name`, `Guid` and `Mapping`. Main fields:

Field	Description
`Emulator`	Emulator the entry applies to (`libretro`, `ares`, `bizhawk`, `mupen64`, `dolphin`…).
`Guid`	Controller GUID; several GUIDs can be separated with commas.
`Driver`	RetroArch only: input driver (`xinput`, `dinput`, `sdl2`). Leave empty if not needed.
`Mapping`	Button mapping, in the emulator's format.
`HotKeyMapping`	RetroArch only: hotkeys for player 1 with this controller.
`ControllerInfo`	Extra settings: `needActivationSwitch: "true"` makes the mapping depend on the USE xxx-LIKE CONTROLLER option; `switch_trigger` is the button used by N64 TRIGGER INVERT.

4. Launch a game and check `emulationstation\emulatorLauncher.log`. {% hint style="success" %} Your mapping works? Share it on the RetroBat Discord or on GitHub so it can be added to RetroBat! {% endhint %} --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://wiki.retrobat.org/controllers/supported-controllers/gamepads/special-controllers.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.