just in case confirmation helps embolden, this is how cheat codes 2 works – when you flip on the MIDI control, the script actively changes modes (eg. the pattern recording + arps look for MIDI notes from the source specified). if you connect a Midi Fighter Twister and boot the script, the script will auto-configure all settings to match. there’s on-screen feedback to confirm the connected hardware, as well 
additional thoughts on script design
what you bring up is really interesting, though, and it’s a necessary accommodation for commercial products (eg. nearly all industry-standard connections are facilitated by norns) – but scripts are community expressions, built from a contributor’s needs and further shaped by their ability/availability to accommodate community feedback. adding full support for additional hardware requires reimagining performance gestures for interfaces that the contributor might not need or even have access to.
from a design perspective, the grid is such an open canvas that it often deeply inspires how the script functions – cheat codes 1 began as “i want to play this type of interface: vertical orientation, three 4x4 banks of pads, right-angle multi-finger area)” + “i want it to be able to make these sounds (@brin’s loose leaf ).”
this seems true of many grid-centric scripts – the 128 becomes such a deep component of the script’s DNA. adding new methods of control can require re-design of the fundamental interactions. i’m really glad i spent the time adding these to cheat codes 2, but i also think it’s a tough proposition for folks with limited resources to make what are functionally different versions of their scripts for each of these paradigms.
one of the central goals of norns is to allow folks to collaborate on code, to modify + remix, to customize small snippets to play a role in a larger collection of tools. what i’ve learned is that building scripts as collections of functions allows people to roll their own controls – but when we get to the scope of scripts like Takt / cheat codes / arcologies / etc, where you’re looking at full composition environments, it becomes very hard to do this (esp. for novice-yet-spirited folks like myself).
all to say, i do feel that there are a lot of opportunities for monome to help facilitate examples for easy integration of additional hardware in the scripting process. Midi Fighter Twister, for example, is a really solid stand-in for arc control, but it took me a while to wrap my head around how to integrate it into the script. the parameters menu is a really good place to focus some brainstorming – https://github.com/monome/norns/issues/1248. thank you for the dialogue!
this could be cool! i’ll add it to the backlog 
@hypnosapien, thank you!! this is super rad and really helpful 
