A controller for the second player

Connecting a controller for the second player in the right order, checking that the browser sees it, and when to give up on it.

If there is an old controller in a drawer somewhere, it is the best way to keep the second player out of your half of the keyboard. But a controller only works when three conditions meet: the operating system sees the device, the browser can read it, and the game has code to handle it. Miss one and the controller sits on the desk with its light on and does nothing.

Plug the controller in before opening the page, not after. Many games check the device list once at startup, so a controller connected later stays invisible until the page is reloaded. That is the most common fault and the easiest to fix: close the tab, connect the controller, open the tab again. The same applies after a browser update, which sometimes clears the list of devices the page is allowed to see.

Once it is connected, press any button on it. On Windows this wakes the device and forces the system to register it as a game controller rather than as a spare keyboard. If the light does not come on, try a different USB port before assuming the hardware is dead, because plenty of laptop ports supply only enough power for a mouse or a memory stick. A controller that draws too much current from one port will often work perfectly from another.

To check whether the browser can read the controller, open a gamepad tester page and press a few buttons. That page shows the device name and the live state of every button. If the name appears and the buttons react, the browser has found the controller and anything still broken sits on the game side. If the page shows nothing at all, the problem is the operating system or the cable.

Inside a browser, remember that only the tab holding focus can read a controller. If you click into another window to look something up, the controller goes quiet until you come back and click once inside the game frame. This is why people conclude the controller is broken when in fact the tab is simply behind another one. Closing other windows helps as well, since a background tab does not receive controller input at all.

Not every game accepts a controller, even a two-player one. Read the key line under the cover: if it lists keyboard keys and never mentions a controller, there is a good chance no controller code exists inside. In that case the fastest route is still the right half of the keyboard for the second player, plus a second USB keyboard if the keys start to fight. The cover text is the fastest place to find out, and it is written by whoever built the game.

With a wireless controller, charge it before you start. A pad sitting at twenty percent will drop its connection in the third round, and the browser loses the device while you are playing. Playing with the cable attached is the safest option, since a wired connection is far steadier and never needs pairing in the middle of a match. A cheap long cable is a better investment than a wireless pad for this kind of evening.

If there is exactly one controller, give it to the person on the right. A controller placed in the middle of the desk invites both people to reach for it, and the left player still needs both hands for W A S D. Put the controller in front of the right-hand player and route the cable behind the monitor so it does not catch the hands of the left player.

Last, play one short round to see whether the two input styles can live together. If the game allows mixing keyboard and controller, both people will be far more comfortable than when they are crowded onto one keyboard. If it does not, drop the controller and go back to splitting the keyboard, because stability matters more than a nice piece of hardware. A controller is a convenience, not a requirement, and the keyboard halves work on any machine.