Technetium 98
Banded Mongoose
Ah, missed that bit. Cheers!
To be clear (actually to be clear to Cassie so she fixes it) the sentence needs to be added to page 13.Ah, missed that bit. Cheers!
Is that in addition to the base 25% requirement (so, 35%), which is then rounded up, or is it after the initial rounding? So the Size 1 robot I keep talking about, would that be 1 slot for base speed and all associated increases, or 1 slot for base, then 2 for the first increase, 3 for the second, and so on?... The robot's rate of movement may be increased by one Speed Band at the expense of an additional 10% of slots...
1) Sure, why not.Ok, three more things:
1) does p.62 mean that I can install an autobar in my battledress? Sweet!
(Or the slightly more serious autochef for tasty meals in the field)
2) Some bots, for example the battle mule and medium Zhodani warbot, have a listed speed of ‘-‘ along with a speed band trait. Does this mean they are only capable of moving at vehicle speed, or are they assumed to also have the default movement of 5 m per move action? This would also affect duration.
3) Mining drones. Been meaning to ask about them for quite some time, and since they’re presented here in greater detail than ever before, I might as well do it here.
How many drones can one operator handle, and how closely must they be controlled? Is it enough to just tap the screen and say ‘dig here’ or is direct input needed for each maneuver?
With its impressive INT of 0 it feels like they need some help, but the control interface might be smart enough to handle much of it? And come to think of it, perhaps a swarm controller is assumed to be part of the package, so a single drone operator can give broad instructions to all the drones and then when needed assume direct control over one of them for detailed work?
It's a bigger engine, so yes, that's intended. Imagine a big truck idling its giant engine vs. a small car with a V4 engine. If the robot had a secondary locomotion mode, then it could use that instead. They could both be grav, or the secondary could be, well, anything.Apologies, I was too vague above. If bots with vehicle speed movement and regular movement ‘-‘ always move in ‘vehicle mode’ then they would always reduce their endurance to a quarter, regardless of how fast they actually move, assuming I interpret this correctly:
p.23:
Vehicle speed movement reduces a robot’s endurance by a factor of four when in use. Each further movement enhancement halves the robot remaining endurance.
Assuming vehicle mode is their only form of locomotion their endurance is drastically lowered, except when standing still. Whereas if they had a regular movement as well, they could move slowly/tactically without running out of juice too quickly.
Is that correct, and if so, is it intended?
Okay, I take all that back "when in use" is the key, and perhaps a split "5 / - " might be more appropriate.It's a bigger engine, so yes, that's intended. Imagine a big truck idling its giant engine vs. a small car with a V4 engine. If the robot had a secondary locomotion mode, then it could use that instead. They could both be grav, or the secondary could be, well, anything.
Nah, we're just nattering about edge cases, here. For just about everything you're going to make, the rules work fine. It's well worth the money.I want to buy this, but holy moly the amount of errors being raised in this thread! Mongoose being Mongoose I guess, which isn't a good thing. Mongoose needs to overhaul their editing and reviewing process at a corporate level.
And add dates and versions to all PDF and hard copies of their products.
Nah, we're just nattering about edge cases, here. For just about everything you're going to make, the rules work fine. It's well worth the money.
... Editing could use an overhaul, though. And dates/versions would be appreciated.
That is one of the reasons I like buying the PDF early, then I can help catch mistakes before the send it to the printers.I wish that were the case, but missing a whole table of data isn't nattering about edge cases. And this isn't the first time Mongoose dropped a table in their editing/reviewing. Fortunately it sounds like this instance has been caught in time for fixing the hard copies. My concern (as always with Mongoose) is if something that drastic can be messed up, then what else is there that won't be caught in time for the printers?
To be fair, that table was mostly fluff, I get why it was cut.I wish that were the case, but missing a whole table of data isn't nattering about edge cases. And this isn't the first time Mongoose dropped a table in their editing/reviewing. Fortunately it sounds like this instance has been caught in time for fixing the hard copies. My concern (as always with Mongoose) is if something that drastic can be messed up, then what else is there that won't be caught in time for the printers?
1. Not 5 o'clock where I am yet, so no drinking, unfortunately.One more thing- I'm probably just ignorant of what's going on under the hood, but some paragraph breaks between the details on the Offensive, TDX, and Nuclear systems would improve readability. I think there's room, but again, ignorance.
- Cheers!
- Fair enough, though I feel like packing an Offensive self-destruct option comes with an expectation of at least some damage. On that subject, what's your take on the D3 ruling?
- Pretty sure? Armour doesn't factor into Blast in Offensive or Defensive. It also depends on TL, not Size, so I'm not sure how the maths changes.
- Yeah, but the current table wraps awkwardly as well. I think the change fits it in. That, and the brackets. The lack of them tripped me up in the first read-through.
You'll get a notice when it gets fixed. The pdf is out early so the stuff that snuck through can get fixed before the printed version. People are in a rush combing it to clarify and get the fixes in time.I want to buy this, but holy moly the amount of errors being raised in this thread! Mongoose being Mongoose I guess, which isn't a good thing. Mongoose needs to overhaul their editing and reviewing process at a corporate level.
And add dates and versions to all PDF and hard copies of their products.
While this is a really good idea, and probably necessary, it doesn't fix the issue of Mongoose's processes (in my opinion).I still think a team of volunteers before anything is even released on pdf would go a long way