So, obviously, our first priority once we hit Early Access was stability and game-breaking bugs.
However, we’re now at the point where I have my weekends back again, and I have begun buying components to make another, brand-new console both for testing purposes and so I have one that isn’t a huge wooden thing designed for expos.
This is something I’ll be doing on my own time, but in the process I’ve decided I’m going to, rather than use my own old hacked-together Arduino sketches, use Arduinos in Space.
This also means I will be spending some time cleaning up, expanding and even overhauling parts of the Arduino-exposed interface.
That being the case, especially once I begun, I was hoping people who’re doing console construction could send me some features they’d like.
Things I am already planning to do include:
I am going to slightly alter how commands are coded in the game, which will allow more detailed parameter-based commands into Arduinos (so, for instance PWR_DISCONNECT_BATT:1 instead of PWR_DISCONNECT_BATT1)
In the process of doing this, beyond giving a bit more options for console makers, I will also have the game automatically generate full and updated command lists, to be put in a text file with each build.
That way anyone wanting to have a constantly up-to-date reference for the inputs and outputs can find it easily. (At the moment, the average update has added 2-3 new checks and a similar number of new interface commands, and while most won’t be important for consoles, I want them all to be documented in a sane way.)
So, those are the two main things I plan in the next while.
Are there other features console-builders are after? I can’t guarantee they’ll be doable of course, but I’d love to know what people are currently finding the biggest limitations of the serial protocol.