@JoargTheBard the control block seems to set them to js0 and 1 by default. I have had problems with my Bluetooth / and systems like daphne because of it. I know only use the control block as a power block with the power block script. It only shuts down and powers up the system with a led indicator but that's fine because I went to the Bluetooth controllers anyways
The main documentation for the ControlBlock can be found here. The sources of the ControlBlock driver are hosted at Github. Currently, the ControlBlock driver does not support N64 controllers and certainly would need to be added to the driver, if you want to connect N64 controllers to the ControlBlock.
I hope this points you into a helpful direction.
Switch is fine. Checked and double checked. When I get a chance this Summer I'll examine the code and see if I can figure out what is going on with the service and hardware. Any suggestions on where to start?
If you are interested in working on the ControlBlock sources, a place to add that functionality would be https://github.com/petrockblog/ControlBlockService2/blob/master/src/controlblock/SNESGamepad.cpp. You could take a look at https://github.com/petrockblog/ControlBlockService2/blob/master/src/controlblock/MAMEGamepad.cpp, where a simulated keyboard is already implemented.
The ControlBlock emulates two individual gamepads on your system. If you connect any additional USB controller it will simply show as another controller that is attached to your system.
So, there is no problem with having arcade controls together with any additional USB controller.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.