KMBox, MAKCU, Teensy and Arduino: the devices that actually move the cursor on the gaming PC.
Reading memory cannot move your mouse, so a separate device has to present itself to the gaming PC as an ordinary USB mouse. These pages compare the five common options and show how to wire each one up. They also explain why the descriptor that each device sends to the gaming PC matters.
10 guidesBeginner 3Intermediate 5Advanced 2
All five act as an ordinary USB mouse on the game PC and inject movement from the second PC. KMBox Net is the easiest and costliest, B+ its cheaper serial version, MAKCU the open middle ground, and Teensy 4.1 or Arduino the DIY end.
Solder a 5-pin header to the host pads of the 600 MHz Teensy 4.1, then flash passthrough firmware with the Teensy Loader. Plug the mouse into the host port and the device port into the game PC, then drive the board over serial.
MAKCU is a mouse passthrough device built on the open MAKCM design: two ESP32-S3 microcontrollers and a CH343 USB-to-UART bridge. Install the CH343 driver, force its COM port below 10, match the cheat's baud rate, and connect the mouse and the game PC.
An Arduino Leonardo with a USB Host Shield is the cheapest working mouse passthrough: the shield's MAX3421E reads your mouse and the ATmega32u4 presents it. It is also the fiddliest: most shields expect Uno pin mapping and need SPI jumpered to the ICSP header.
Both KMBoxes do the same job, but the B+ talks to the second PC over USB serial at 115200 baud. The Net presents a USB Ethernet adapter addressed by IP, port and UUID, which tolerates distance and sustains far more commands per second.
A USB HID descriptor is how a device describes itself when plugged in: its vendor ID, product ID, strings and report format. Descriptor cloning means the input device presents the identity of the real mouse attached to it instead of its own generic one.
First prove that your own mouse moves the cursor through the device, then prove the second PC can open the link. Most input faults come from the wrong socket, a missing serial driver, a mismatched COM port or baud rate, or a charge-only cable.
The mouse goes into the input device's host port, the device into the game PC, and the second PC into the device's control port. Never cable the game PC directly to the second PC: the only link between them should be a mouse.
When you need a KMBox, how to wire a KMBox Net, and how to prove the ethernet path before you touch the game software.
USB serial KMBox B+ Pro: CH340 drivers, the PC and COM ports, and a cursor test before the loader.