"Double Clutch" and what follows
The rigger supplement “Double Clutch” was the book that made me quit Genesis.
“Double Clutch” featured modifications that not only had a rating to chose, but had dynamic costs/stats depending on the kind of vehicle it was added to.
In Genesis we “solved” this by hardcoding the formula for mod slots in the code, whereas other formulas were left to the users discretion (see max. “Rating”):
Commlink is playing its strengths here, but adapting everything to the new model took a lot of time. While we did, we did not find the time to fix reported bugs - and there are quite a few:
Where do we go from here?
Immediate focus will be on bugfixing what we just released, including having a look at the recently reported bugs. I guess one or two more releases of 0.12 will be necessary.
And than we have the following areas of work to choose from:
Companion: PACKS
You already can select PACKs during character creation, but the way it is implemented is not really satisfying.Companion: SURGE collectives
Currently you cannot select a SURGE collective, but need to fallback to buying individual mutations - which means that they count against your 6 qualities limit and you also won’t be able to make use of the sometimes reduced Karma cost of a collective. And we do have very cool illustrations we want to show.Companion: Infected
Similiar to the SURGE collectives, support is currently missing (but without an alternative to fallback to)Companion: Lifemodule generation system
Work is already on the way to enter all module data, but the generator with an user interface to use it has not been started.Companion: Extended Contact Rules
Has been prepared, but no logic has been implemented yet.Companion: Extended Lifestyle Rules
Same here. Will likely follow later with support for the extra lifestyle PDF.Lofwyr’s Legions: Drakes!
Data has already been entered, the work on the user interface has been started.Cloud Synchronization
The whole cloud account creation and password recovery has been done already, but code for synchronization is still missing. This feature is my internal marker 1 for leaving the Alpha test.Auto-Updater
The ability of Commlink to update itself is my second important feature I want to have, before I officially release the application
I think we will take care if 1., 2., 8. and 9. since work has already started and/or they are quick to accomplish. If we do manage to get 8. and 9. done, the next version will be the official release version 1.0.