简体中文
EnglishWhat Input Methods Can You Use to Play Games in Eclipse?
Updated
Eclipse supports three input methods: touch, keyboard, and controller. You can use any of them to play the supported systems (Game Boy, Game Boy Color, Game Boy Advance, NES, SNES, Sega Master System, and Sega Game Gear), and if the default bindings don't suit you, you can edit them in settings. The one hard limit is controller support: it depends on the JavaScript Gamepad API, so a controller your browser or operating system doesn't recognize won't work in Eclipse at all.
The Three Supported Input Methods
Touch
On phones and tablets, including iOS and iPadOS, Eclipse presents on-screen controls you tap to play. This is the default way to play on a touchscreen device and requires no setup.
Keyboard
On a desktop or laptop, you can play with your keyboard. Eclipse ships with default key bindings, so you can start playing without configuring anything first.
Controller
Eclipse accepts game controllers through the JavaScript Gamepad API. Two conditions decide whether your controller works:
- The browser must expose it through the Gamepad API. Eclipse reads controllers through this API, not through any separate driver of its own.
- Your operating system must recognize it. If the OS doesn't see the controller, the browser can't pass it to Eclipse.
If either condition fails, the controller "will not be recognized" — this is a limitation of the API and OS, not a setting you can toggle inside Eclipse. A controller that pairs and works in other browser-based tools is a good sign it will work here.
Changing the Default Bindings
Eclipse states that if you don't like the default bindings, you can easily edit them in settings. This applies to the input methods you use — so if a keyboard layout feels awkward or a controller button mapping doesn't match your habits, adjust it there rather than adapting your play style. The site doesn't publish a step-by-step mapping guide, so treat the settings area as the place to look and test each change by pressing the button in a game.
Choosing an Input Method
| Situation | Recommended input | Why |
|---|---|---|
| Playing on iPhone/iPad | Touch | No revokes to worry about; on-screen controls are built in |
| Playing on a laptop or desktop | Keyboard | Default bindings work immediately; no extra hardware |
| Prefer a console-style feel | Controller | Supported via the Gamepad API, with editable bindings |
| Controller not detected | Keyboard or touch | The API/OS didn't recognize the device; Eclipse can't override that |
Practical Notes
- Test your controller before committing to it. Load a game and press a button; if nothing registers, the device isn't being exposed through the Gamepad API on your setup.
- Offline play doesn't change input support. When you play offline using games from your local files instead of the Library, touch, keyboard, and controller all remain available.
- Bindings are worth revisiting per game. Some titles lean on buttons that feel unnatural on a given layout; a quick remap in settings is faster than fighting the default.
In short: pick touch on mobile, keyboard on desktop, and a controller if you want a more tactile feel — but confirm your controller is recognized by your browser and OS first, since that's the one input path Eclipse can't work around.