Proneutron
SOC-13
Back to the OP, it can be simpler.
Yours way is MORE complex than my one dimensional chart, not simpler.
Last edited:
Back to the OP, it can be simpler.
A character with good computer skills should be able to easily reverse-engineer the generate algorithms and write new interface code.
Your way is MORE complex than my one dimensional chart, not simpler.
But that's the problem -- if the intent is to provide pricing even vaguely resembling economic constraints,
A character with good computer skills should be able to easily reverse-engineer the generate algorithms and write new interface code. This would probably violate various copyright or patent standards. A programmer could use the reverse engineered code as a test engine to certify the output of new code. While this could be legally dicey it wouldn't be easy to prove once the testing is complete and the questionable code is disposed.
A group of characters with high computer skills, PhDs in astrogation, and related fields should be able to make an open source generate pgm. A group of independent starship owners could form a risk retention group and certify the open source version after suitable testing. Membership in the risk group for a tenth the cost of Generate would gain access to the code.
It's based on ship cost for a ship that would deliver cargo in one jump that many parsecs. Or so the originator stated. In Traveller you stay in space for a ~1 week per jump. Since that chart is per Jump it doesn't require the additional dimension variable of TIME.
That is, most of the available cargo will pay the cheapest rate and doesn't care how long it might take. Meanwhile, a small portion of the available cargo will pay whatever it takes to get there in one week if they can.*
As an example, the rate to 5 parsecs would probably be based on the costs of a Jump-3 ship doing two jumps (J3, then J2) or a Jump-2 ship doing three jumps (J2, J2, J1). Some cargoes would pay extra to do it in one week,
...<snip>
*This would call for a change to the cargo rules. Instead of declaring a destination and rolling to see how much cargo is going there, you'd roll cargo for all destinations within 6 (or so) parsecs and then break each world's cargo down into the normal and time-sensitive categories.
back when I was working on my trade program, that's what I did, though only out to the ship's jump range. Think I was using the T5 rules for that part of things. You had a list of cargos (rolled once per week) for all destinations in reach. Same for passengers.
You are assuming that thousands of years from now you can view the code and it doesn't come in encrypted H/W computing modules you cannot access...
Also, if it is open source then you cannot charge for it...
Like all of those folks that have been reverse engineering data and duplicating interfaces for the past 50 years?
That's why Canoncial (makers of Ubuntu) is a $110M/yr company.
I would go with the open source software in this case being the same as a home written piece of software. A 5.5% probability (assuming I read the table correctly) each time you jump. Eventually it will catch up with you.
I don't know. What has more errors, MS Office or LibreOffice? What is more Secure, Windows or Linux?
but for the game in question, that rule in book 2 stands regardless of current software, for the future software we are talking about. So for that case, less secure by the rules.
I understand what you are saying but, this was written before Marc knew about OSS. So I don't think that rule would exist if he wrote Traveller today. Just as Jump "tapes" are not the mag tapes of my mini-computer days but some thumbnail sized atomic crystal lattice device.
I still blow on the connector for my jump tapes as they seem to work better that way![]()