Troubleshooting

I'm getting a "Device is not functioning error" with USB-Botbase

Reboot to payload, then ensure libusbK drivers are installed with Zadig and filters are applied via the libusb filter wizard. Can require multiple driver and filter installations depending on how your computer recognizes the device.

I'm running multiple instances of SysBot on multiple Switches and it keeps adding the same bot!

Libusb goes through all connected USB devices in a list in order and stops on the first one. If adding bots on multiple instances, add all available devices, then remove duplicate ones. Or run your bots on a single instance for simplicity.

My Switch suddenly has a WinUSB driver again!

Re-do the steps for installing the libusbK driver via Zadig, then re-apply a libusb filter. Windows likes to reassign drivers the first few times when reconnecting the cable or rebooting the console.

My Switch is losing charge!

A Switch needs at least 1.5A of current provided to it over a USB port to charge faster than it discharges. If your computer does not have a USB-C port, you may need to invest into a powered USB hub that can supply 1.5A (7.5W) through a data port.

TradeCord doesn't apply user-set trainer info!

Enable "AllowTrainerDataOverride" in SysBot settings under "Legality".