CT Only: JTas Robots charts.

[infojunky]

Well did one of those odd turns tonight, looking at the original Robots articles noticed the charts where out of order. So spent the evening putting them in the order of the checklist.

Now the question is what to add to that base?

 

[Spinward Flow]

Well did one of those odd turns tonight, looking at the original Robots articles noticed the charts where out of order. So spent the evening putting them in the order of the checklist.

Less than optimal layout in JTAS?
This is my shocked face.

However, I'm pretty sure that LBB8 Robots was written and published later, consolidating everything from JTAS into a better (not optimal, just better) presentation format.

 

[infojunky]

The hardest part is avoiding making changes.

 

[Spinward Flow]

The hardest part is avoiding making changes.

One of the changes I would want to make is allowing (robot) batteries to exist prior to TL=12.
I figure porting over batteries from Striker and converting their megawatt-seconds to kilowatt-hours ought to do the trick.

Without a "batteries only" option prior to TL=12, you can't have robots that are "all electric" tapping power from the ship's power bus systems which place no demands on the life support systems of a starship (O₂ for a fuel cell's consumption, for example) and would thus be able to operate in a vacuum under null-g conditions using a zero-g maneuver module that only needs H₂ gas (1 liter equals 100 combat rounds) if the ship is in a combat and/or damaged.

 

[infojunky]

Honestly I reset the starting point of robots to tech level ten or so.
with drones earlier no brain just a slave unit.

 

[kilemall]

Honestly I reset the starting point of robots to tech level ten or so.
with drones earlier no brain just a slave unit.

My standard is a Ship’s Robot, static brain, and lots of slave drones. Big money into essentially a robot server and then plenty of little disposable units.

Interesting question is whether to direct link that brain to the Ship’s Computer.

 

[Spinward Flow]

Interesting question is whether to direct link that brain to the Ship’s Computer.

Direct link ... maybe not.
Firewalled link ... undoubtedly.
You want the crew to be able interface with the robot brain from anywhere there's a computer access terminal (with sufficient authorizations, of course). That way you can issue commands to the engineering droids from your bridge workstation (for example). That kind of remote command and control interface, not to mention video/trideo recording playback from starship control panels would be valuable in all kinds of damage control/casualty situations, rather than being limited to "in person" access at the brain box only (which can then be blocked by damage control/casualty situations restricting physical access to the brain box (decompression, doors jammed/locked, plasma fires, hull rupture, etc.).

For exceptionally high security protocols, however, preventing the brain box from having access to the ship's computer becomes necessary, but I wouldn't expect such arrangements to be a default standard for everyone but more of an exception depending on use case.