In addition, there are support and software market aspects to the pricing model.
For Astronics, a large part of the fee is a 'lifetime' support contract- physical damage replacement still has to be paid for, but there will be upgrades and updates installed for free during yearly maintenance, support for software working with new OR old replacement equipment the computer must interface with, etc.
At the merc/bulk freighter level there would be either a support contract imposed at 5% of the value of the computers and software per year to get the astronic support level, or per service/consultant fee, which should be structured to be punitive enough to make the support contract look good, and ultimately failure of certification if the software isn't updated after X years.
At the small craft level the support contracts are available at 10% or fees as per above, with a lot of the oldest or newest starship hardware being very difficult to get easy functionality with. Most of the time it will be easier and cheaper to just buy a new version of the program.
At the desperate level, you are likely going to have to write everything, contract for it, share programs of dubious value merit or safety on software netsites, or do without. Every replacement of a piece of starship electronics that interfaces with the computer will be a major repair/configuration exercise.
Another aspect is commercial availability of the software on the list.
Astronic level software has everything on the list for sale due to their high profitability and subsequent capacity to QA and hire the best programmers and subject matter experts for their programs.
But at the bulk/merc level, any program that requires a 4 or greater expertise to make is not commercially available. It's just not worth it to incur the extra cost for the more meager rewards.
This means even the ECM and Generate programs will need to be programmed by the players or contracted/negotiated for, and otherwise the self-erasing jump programs will have to be used.
At the small craft level, any program that requires a 3 or greater expertise to make is not commercially available.
At the desperate level, any program that requires a 2 or greater expertise to make is not commercially available. Desperate computing does not even have target/weapons programs, all that will have to be programmed, with the resulting risks- and good luck finding a pilot-6 on the frontier willing to hold still for a few weeks while the program is being created! Favors will need to be called in....
For ships that sport multiple computers for damage control purposes, failover must be to computers of the same basic level, too many incompatibilities between levels of computers to mix and match. Between incompatible levels, computer techs effectively have to switch over as though it were a new install with interface issues to every piece of starship equipment the computer communicates with.
So no you do not get a sub-100K backup system (although I do have virtual machine rules for those clever enough to inquire).
For Astronics, a large part of the fee is a 'lifetime' support contract- physical damage replacement still has to be paid for, but there will be upgrades and updates installed for free during yearly maintenance, support for software working with new OR old replacement equipment the computer must interface with, etc.
At the merc/bulk freighter level there would be either a support contract imposed at 5% of the value of the computers and software per year to get the astronic support level, or per service/consultant fee, which should be structured to be punitive enough to make the support contract look good, and ultimately failure of certification if the software isn't updated after X years.
At the small craft level the support contracts are available at 10% or fees as per above, with a lot of the oldest or newest starship hardware being very difficult to get easy functionality with. Most of the time it will be easier and cheaper to just buy a new version of the program.
At the desperate level, you are likely going to have to write everything, contract for it, share programs of dubious value merit or safety on software netsites, or do without. Every replacement of a piece of starship electronics that interfaces with the computer will be a major repair/configuration exercise.
Another aspect is commercial availability of the software on the list.
Astronic level software has everything on the list for sale due to their high profitability and subsequent capacity to QA and hire the best programmers and subject matter experts for their programs.
But at the bulk/merc level, any program that requires a 4 or greater expertise to make is not commercially available. It's just not worth it to incur the extra cost for the more meager rewards.
This means even the ECM and Generate programs will need to be programmed by the players or contracted/negotiated for, and otherwise the self-erasing jump programs will have to be used.
At the small craft level, any program that requires a 3 or greater expertise to make is not commercially available.
At the desperate level, any program that requires a 2 or greater expertise to make is not commercially available. Desperate computing does not even have target/weapons programs, all that will have to be programmed, with the resulting risks- and good luck finding a pilot-6 on the frontier willing to hold still for a few weeks while the program is being created! Favors will need to be called in....
For ships that sport multiple computers for damage control purposes, failover must be to computers of the same basic level, too many incompatibilities between levels of computers to mix and match. Between incompatible levels, computer techs effectively have to switch over as though it were a new install with interface issues to every piece of starship equipment the computer communicates with.
So no you do not get a sub-100K backup system (although I do have virtual machine rules for those clever enough to inquire).
Last edited: