
this is beta software which is not yet fully documented, but is 90% working as intended. I’m hoping that a few folks who have watched the last two streams and are comfortable with the first version of cheat codes will be willing to test the system for the next week or so, as I ready an August 30th public release documentation for a mid-September release.
please back up your dust > code > cheat_codes folder if you wish to retain any saved work from cheat codes 1. at this point, collections are not compatible across the two versions and if you save a cheat codes 2 collection over where you saved a cheat codes 1 collection, the data will not be recoverable.
for reference, here’s the video of the new features stream from three weeks ago. that will be your best guide for testing – i’d recommend going through and testing each of the features as they’re discussed. and then the video from today’s stream will remain up on twitch for delay testing! eeee!
the only thing that's DEFINITELY different is the grid arp workflow.
- the arp button is the button to the left of the 2nd zilchmo row
- press it one to turn on the arpeggiator (doesn’t matter what screen you’re on)
- hold some grid keys down and they’ll arpeggiate
- release them and they’ll stop
- hold some grid keys and press the arp button again
- release them and they’ll hold
- press the arp button again and the arp will pause
- press the arp button again and the arp will play
- hold alt (either local or global) and press the arp button to clear the arp
since beta issues are going to be ephemeral, i’d love for this process to take place on the cheat codes 2 github repo: https://github.com/dndrks/cheat_codes2-beta. i definitely don’t have docs in place yet, but for folks who have watched the last two streams, you should be in a totally good zone to explore and start getting a sense for what seems fun / weird / wrong. if that’s totally inaccessible, let me know and we can start a thread – but i think it’d be awesome to centralize the convo in a code-focused space, so for now let’s assume that we’ll chat there! 
when submitting an issue, please feel free to use any combo of the labels depending on the situation.
i super appreciate everybody’s positivity and energy, but please don’t feel pressured to jump onto the testing train if you aren’t totally comfortable with this process. the public release is super soon 
i legitimately never thought this would happen. i cannot thank y’all enough 