Okay. I've been thinking about this whole limpet controller situation, and I think I have a good idea that gives commanders a lot of flexibility, that should be fairly easy for developers to implement, and wouldn't allow any commander to just run any limpet all the time. It's reasonably well balanced, all all the user interfaces it uses are interfaces which are used elsewhere in the game.
Super short summary: A limpet controller can only run one limpet program at a time.
First off, a limpet controller would now work much like a fighter bay or an SRV bay. You buy the controller, and then it has its own child-slots.
In each of these child-slots, you could purchase programs. These programs would give the functionality that all the existing limpet controllers provide.
So, you could buy a class 1 limpet controller, then purchase, for it, two programs. One for collector limpets, one for repair limpets.
The "class/grade" that a program runs at is determined entirely by the controller on which it is loaded.
Now, the limpet controller starts out powered-off.
When you power-up the limpet controller, you get an additional UI dialog box that asks you which program you would like to load on the limpet, and are given a list of the programs you have purchased for that controller.
Upon choosing a program to load, the limpet controller boots up and from that point on acts exactly like a current limpet controller. For instance, if you chose collector limpets, the controller would now be listed as "Limpet Controller: Collector" and you would just bind it to a fire key as usual and use it as normal.
Now, when you want to use repair limpets, instead, you just go to your power panel, shut the controller off, and turn it back on. It will then ask you which program to load. You select "Repair Limpet" and now it shows up as "Limpet Controller: Repair" and is used just like a regular repair limpet controller.
With this setup, there still is an occasional need/desire to have more than one controller, so you can run two types simultaneously. But it allows commanders to be a little bit more flexible.
For instance, a pirate could get by with one, with a little bit of management. Pop some hatch breakers, then reboot the controller while you're waiting for the cargo to drop.
I miner might really desire two controllers.
Super short summary: A limpet controller can only run one limpet program at a time.
First off, a limpet controller would now work much like a fighter bay or an SRV bay. You buy the controller, and then it has its own child-slots.
In each of these child-slots, you could purchase programs. These programs would give the functionality that all the existing limpet controllers provide.
So, you could buy a class 1 limpet controller, then purchase, for it, two programs. One for collector limpets, one for repair limpets.
The "class/grade" that a program runs at is determined entirely by the controller on which it is loaded.
Now, the limpet controller starts out powered-off.
When you power-up the limpet controller, you get an additional UI dialog box that asks you which program you would like to load on the limpet, and are given a list of the programs you have purchased for that controller.
Upon choosing a program to load, the limpet controller boots up and from that point on acts exactly like a current limpet controller. For instance, if you chose collector limpets, the controller would now be listed as "Limpet Controller: Collector" and you would just bind it to a fire key as usual and use it as normal.
Now, when you want to use repair limpets, instead, you just go to your power panel, shut the controller off, and turn it back on. It will then ask you which program to load. You select "Repair Limpet" and now it shows up as "Limpet Controller: Repair" and is used just like a regular repair limpet controller.
With this setup, there still is an occasional need/desire to have more than one controller, so you can run two types simultaneously. But it allows commanders to be a little bit more flexible.
For instance, a pirate could get by with one, with a little bit of management. Pop some hatch breakers, then reboot the controller while you're waiting for the cargo to drop.
I miner might really desire two controllers.