◆ Interactive demo. Visual only, no devices are accessed. Open in a new tab
This is a faithful, non-functional replica of the Lattice Weaver companion app. Click the navigation, switch themes in Settings → Theme, run the guided Setup and Calibrate mouse walkthroughs. Nothing here touches real hardware. Open the compact dashboard teaser →
Lattice Weaver
LATTICE
Access Elevated
PRO
Capture
Player slots
Settings
Games
Setup Doctor
last run 21:52:37
TOOLS
Help
Lattice Weaver v2.0.0
build 995614d+ · 2026-10-15 · debug
Local cooperative play in which each player uses their own keyboard and mouse in their own instance.
Links & Support
Modrinth Lattice Polar
GitHub Email Donate
How routing works
Lattice claims each additional mouse and keyboard so that Windows no longer sees them, then routes their input into that player's game window. The host (P0) keeps its own devices. Your device bindings are never released automatically. Pausing routing or closing Lattice leaves every binding in place; a peripheral stays bound until you release it yourself.
Common problems
Routing is Paused and no input is being routed. Routing never resumes on its own; please select Resume, or the Capture button. This is deliberate, so that a reconnecting device cannot silently take your input.
A device is Missing and has dropped. Please reconnect it, then select Repair on the slot's card. If it has moved to another port, select Reassign instead.
Two identical devices are Ambiguous and cannot be told apart. Please run Verify in the Setup Doctor, then operate the device you intend to use. Selection is always by physical input, never from a raw list.
A player has no input in their game. Each additional player requires its own game window, one instance per player, and that window must be linked. Please confirm that the slot shows an active instance.
The application reports that administrator access is required. Applying device locks requires elevation. Please use the Access control in the header to relaunch; Windows will present a User Account Control prompt.
Your own mouse or keyboard appears to have been claimed. The host (P0) is never claimed. If a native device was moved to a player slot, please open Reassign and release it back to native. The host always retains its own devices.
Tip: each extra player needs their own mouse and keyboard.
Event log
Quiet. Nothing to report.
Demo navigator: jump to any screen or play a walkthrough