Condottiere
Emperor Mongoose
Dazzle camouflage.
Potentially.
Possibly, the only time you shoot (low powered) laser beams at yourself.
Potentially.
Possibly, the only time you shoot (low powered) laser beams at yourself.
Yeah, but that changed in the Starship Operator's Manual. There's a whole section on how you can do "ongoing maintenance" instead of parking at the starport for 2 weeks.Annual maintenance is still a thing, the cost is just amortised over the year:
No specified down time though.
Pity, those two weeks are a great opportunity for the Travellers toYeah, but that changed in the Starship Operator's Manual. There's a whole section on how you can do "ongoing maintenance" instead of parking at the starport for 2 weeks.
Those rules are only an issue if you have that book (and it was way down on my priority list)Yeah, but that changed in the Starship Operator's Manual. There's a whole section on how you can do "ongoing maintenance" instead of parking at the starport for 2 weeks.
I am sure you can have a bundle of fun with just the $1 starter editions. Even with the supplements there are rules that I just don't agree with and house rule out.The same is true of all the robot stuff people argue should be affecting how everything is done. *shrugs*
AI software is a spectrum and any software is only as good as the idiot that wrote it. These days people are lazy and use code generators rather than employ software engineers who actually understand the implications of adding that Class you found on the internet into your core systems. The time spent testing used to be equal to the time spent developing. With "minimum viable product" philosophy it is out the door before the requirements have been tested, let alone the implementation. It's OK because the consumer will test it"Once you realise that TL12 computer is tiny and cheap (which is exactly how it should be)"
They run AI software now too...
"In the Third Imperium and other regions of Charted Space, AI is a useful tool but one that is highly regimented and controlled. For various reasons – some quite valid – sophonts keep the lid on tightly when it comes to AI. For Humaniti, this means establishing stringent design limitations, and creating multiple fail-safes to prevent disasters from happening. AI is not allowed to operate independently; it is only allowed to think within very specific confines and only to achieve tightly defined goals. AI innovators can create brilliant computer minds but they must also create tools and safeguards to keep them in check."
Okay. I don't see what any of that has to do with anything.I am sure you can have a bundle of fun with just the $1 starter editions. Even with the supplements there are rules that I just don't agree with and house rule out.
I try not to argue against rules that I don't have the supplement for and try to cite references so people can come to their own conclusions. It is irritating to have someone argue that a rule is X and then discover they are misquoting or citing a previous edition without identifying it. I now have most editions, but some are too arcane to read cross from or use such a different baseline ruleset that extrapolation is a fools errand.
Once you have the Robot handbook it is hard not to find ways to replace virtually everything with a Robot. Once you realise that TL12 computer is tiny and cheap (which is exactly how it should be) then it is hard not to envisage Travellers festooned with computers steering their every action (much like society today).
When I was playing in the 80's and we first saw how big ships computers and hand comps were "in the future" we laughed derisively. Sadly the designers got that badly wrong and trying to recapture that "golden age" is just going to make it seem a bit silly to a modern audience. It is a way to play Traveller but it is not the "Right" way to play traveller. The "Right" way is whatever works for you.
Sigh.Yeah, but that changed in the Starship Operator's Manual. There's a whole section on how you can do "ongoing maintenance" instead of parking at the starport for 2 weeks.
I thought I was agreeing with you.Okay. I don't see what any of that has to do with anything.
I pointed out that rules change over time. Another person said that a particular rule I mentioned hadn't changed. I pointed out where it had changed. You made a flippant comment that the rules don't count if you don't own them. I merely pointed out that this is true of a wide range of materials, using the Robot handbook as an example because you (or another poster) mentioned droids earlier.
I don't care what rules you use. I certainly don't use all the rules as written. And, in fact, earlier in this thread I said "use whichever rules you like".
I gather the intent is to allow ships that are operating on long range exploration, out in the wilds where there's no reliable A/B starports, criminal ships who want to avoid the more sophisticated ports, and so on to have a way of maintaining the ship. A fair bit of discussion of the complexities of doing various sorts of maintenance in less than ideal environments.Sigh.
Thanks, I'll check that out.
Well, it's not new, it was in JTAS#24.I gather the intent is to allow ships that are operating on long range exploration, out in the wilds where there's no reliable A/B starports, criminal ships who want to avoid the more sophisticated ports, and so on to have a way of maintaining the ship. A fair bit of discussion of the complexities of doing various sorts of maintenance in less than ideal environments.
Just like there was a "Special exception" in Deepnight because it was a 20 year mission into the beyond.
As an alternate to this a GM might allow the extra rolls to result in one of the larger scout craft from the Adventure Class ships book. Ones with more jump fuel, jump range etc. Might include more restrictions of course.Geir, you're not hallucinating. However, the emphasized (in red) phrase is not the only significant portion of the quoted text:
"If you roll this Benefit more than once, re-roll the result."
I’m not sure it is an inconsistency. The WBH talks about maintenance which is not the same as refueling and supplies. Seems to me it’s like this you get fuel and other standard supplies but repairs are done at cost.Good catches by both @boggo2300 and @Limpin Legin
This kind of inconsistency really needs to be taken care of during the writing and development process. This is a prime example of what I mean whenever I complain of this kind of thing.
Mongoose needs a database person, even an unpaid volunteer/intern, to enter information from each Traveller canon book into a database that writers can check whenever they want to write about a particular subject or person, place, or thing for a new Traveller product.
I'm tempted to do it on my own, just to learn about databases and SQL, like set up the community version of MySQL. I'd learn some SQL, get familiarized the MySQL databases, and read Traveller books!
Maybe Mongoose has something like this already.
Edit:
I mean, here I am criticizing after the fact with no knowledge of the difficulties, production schedules, costs, and trade-offs that Mongoose has to make to bring a Traveller product to market. My own post reminds me of how Bethesda's Skyrim developers got irritated with the modding community complaining about problems with the game, and the devs commented unofficially that production schedules and cost cycles make the kind of quality control the modding community wanted almost impossible, and that modders have the freedom to work at their own pace to bring fixes and mods to the community.
Still this kind of inconsistency fragments the OTU even more along with all the other inconsistencies, obscurities, etc.