Robots of the Imperial Army

[Carlobrand]

Historically, the Imperial Army does not tend to use warbots. There are a variety of reasons for this, but the major one is practicality: warbots with the intelligence to function effectively in combat are expensive. A civilian robot lasts long enough for the payments on it to be less than the monthly wage of the worker it replaces; a warbot's lifespan on the battlefield is a great deal shorter. Even allowing for repair - if the robot can be recovered, and if the weapon that hit the robot was not too destructive - it is frankly cheaper to train a human (or other suitable sapient) than to field an effective warbot. There is no shortage of humans willing to join the military, whether to escape their past lives or in pursuit of adventure and a better future for themselves.

That being said, there are roles for which the robot is ideally suited, roles that free soldiers up for combat, roles that bring capabilities to the unit that could otherwise only be delivered by a vehicle, and roles in which for whatever reason the robot is more effective. In this thread, we will present a number of robots possibly used by the Imperial Army and Marines.

 

[Carlobrand]

Pony

A160D-82-EG112-SF51(1)
Cr197,469
750-liter Box/Wedge; Chassis dimensions: 144 cm tall/long by 72 cm by 72 cm
Armor, Striker: TL 15 Bonded Superdense, Armor 18
1 head (8%)
2 heavy arms;
TL 9 UH Grav Mod; Speed: 4 (24 kph; 400 meters per minute ground. 24 kph/667 meters per minute roads. 24 kph top speed in flight.
Power: 4x Type G Fuel Cell; available excess power: 6.5Kw
Fuel: 237.7 liters, 148.56 hours
Batteries: 0 KWh; Duration: 0 hours
Designed Cargo Capacity: 600 kg.
Mass: 1144.81 kg unloaded, 2884.81 kg loaded
Inoperable: 150; Destroyed: 375

Programs
TL9 High Data: Commands must be explicit. Can analyze and learn from data, gains experience.
Basic Command: Full vocabulary but limited to basic verb-adjective-object commands, must be clearly spoken, cannot understand accents.
Cargo Handling-2, Active; Engineering-1, Storage;

Chassis
Radiation Sensors
Master Unit; Radio, Distant (5 km); Power Interface; Program Interface;
4x 5km Laser Communicator; TL15 Battle Computer; 30x foxhole covers; 3x CR-a;

Head #1
Basic Sensor Package (Includes 2 visual, 2 audio, 1 olfactory); +1 Light Intensifying;
Voder (speech synthesizer);

Appendage #1: TL 5 Arm, heavy (no installed items)
Appendage #2: TL 5 Arm, heavy (no installed items)

The pony is an Imperial military bot intended to provide cargo support at the platoon level. The bot's body, at 1.44 meters length by 72 cm (28.35”) width and height, is about the size of the torso of a small pony and can fit in most vehicles. The bot is a basic grav-lift cargo bot with a capacity of over 1800 kg. It's primary purpose is to carry and place the platoon's foxhole covers, armored plates on stands intended to provide overhead protection to troops in foxholes. In addition, it carries 5 100 kg (46 cm cube) cargo containers for the troops' food and munitions and a 100-liter water container, and it typically carries a battle computer and four 5 km range laser communicators for control of its three subsidiary CR-a's and secure mobile communication with the company HQ, as well as carrying the CR-a's themselves between uses. When the bot is not carrying foxhole covers, up to eight cargo containers can be attached at attachment points around the chassis perimeter (three either side, 1 fore, 1 aft) and another 9 can be stacked on back.

The bot can alternately carry up to 6 troops, two seated on its back, four in foldaway seats on either side, to assist with crossing rivers or scaling steep surfaces. It can also be used as a stretcher bearer, with a stretcher mounted on its back and/or to either side. Collapsible stretchers and slings for the purpose are stored in a storage bin within the bot.

A master program allows the bot to control three CR-a's for distribution of cargo to the platoon's squads, with the battery-powered CR-a's plugging into the pony for recharge between trips; the pony can control the SR units when needed but lacks programming to control their weapons. With 6.5 Kw excess power available, the bot can also be used to recharge other batteries or to power some equipment.

The bot is armored equivalent to combat armor to survive on the battlefield but is unarmed in keeping with Imperial policies on use of robots. The bot has a basic engineering program and carries an oversize pick and shovel suitable to its strength for basic digging, allowing it to dig its own trench or to help dig other field fortifications. An engineering variant mounts a 500 kg. backhoe on the back for trench digging; another variant mounts a 500 kg crane for heavy lifting of up to 1 ton. Engineering variants are held at the company level for use where needed.

 

[Carlobrand]

Cargo Remote Alfa (CR-a)
01x0B-N2-00xx0-0330(0)
Cr10,919
5-liter Box/Wedge; Chassis dimensions: 28 cm tall/long by 14 cm by 14 cm
Armor, Striker: TL 15 Bonded Superdense, Armor 18
1 head (40%)
Tracks; Speed: 1 (6 kph; 100 meters per minute), 1 (6 kph; 100 meters per minute) in rough terrain
Power: Battery powered
Fuel: N/A
Batteries: 5.4 KWh; Duration: 0.59 hours
Designed Cargo Capacity: 83 kg.
Mass: 16.89 kg unloaded, 99.89 kg loaded
Inoperable: 1; Destroyed: 3

Programs
No data program: Slave unit, controlled remotely by a master robot or a human with a control unit.
No command program (Slaved): No command program; unit is controlled remotely by a master robot or a human with a control unit.

Chassis
Slave Unit; Acoustical Speaker; Radio, Distant (5 km); Power Interface;
1x 5km Laser Communicator;

Head #1
1 Visual Sensor; +1 Light Intensifying; 1 Audio Sensor;

The Cargo Remote alfa (CR-a) is a battery-powered Imperial military bot intended to provide cargo support at the platoon level, primarily to deliver ammunition and other essentials over short ranges to troops under fire. The bot's body at 28 cm length and width by 7 cm height is the smallest producible, about the size of a large square dinner plate, and is optimized for carrying small loads. Standard battery duration is 34 minutes with a TL12 battery, sufficient for a range of 3000 meters in rough terrain, but the bot's typical run is less than a hundred yards and back.

The bot can carry up to 83 kg, but over rough ground the load is generally limited to about 30 kg to minimize the risk of tipping. Its low profile greatly reduces the risk of being hit by stray fire. Lacking arms, the bot is loaded or unloaded by troops or the platoon's pony. The bot has a single visual sensor with light intensification, a single audio sensor, and no brain; it is remotely operated by a master robot, typically the platoon pony, to shuttle cargo between the pony and the platoon's squads, with one CR-a available for each squad. If the platoon pony is damaged, the bot can also be moved by humans using a backup hand-held controller, though care must be taken to find a source of power to recharge from.

The bot has a short-range laser communicator (5 km range, 2 kg., Cr2000) mounted externally, allowing the master unit to maintain control even in the face of battlefield radio jamming; with the laser comm and its on-board speaker, the bot can also serve as an improvised communications link, provided it is plugged into a power source or the use does not exceed the battery life.

 

[rancke]

I can't think of a single adventure or world writeup that mentions the routine employment of robots as substitutes for human workers. Apparently there is some reason why they are not economically sound¹. Perhaps the economic details for robots should be revised?

¹ IMTU terrorists and 'humaniti first' activists enjoy hacking robots so much that safeguards and mandatory insurance payments make them more expensive than human workers in most cases.​

Hans

 

[Carlobrand]

Cargo Remote sierra

2100B-J2-00xx0-1330(0)
Cr12,183
20-liter Box/Wedge; Chassis dimensions: 44 cm tall/long by 22 cm by 22 cm
Armor, Striker: TL 15 Bonded Superdense, Armor 18
1 head (18%)
Tracks; Speed: 1 (6 kph; 100 meters per minute), 1 (6 kph; 100 meters per minute) in rough terrain
Power: 1x Type A Fuel Cell; available excess power: 0Kw
Fuel: 1.9 liters, 19 hours
Batteries: 0 KWh; Duration: 0 hours
Designed Cargo Capacity: 64 kg.
Mass: 35.39 kg unloaded, 99.39 kg loaded
Inoperable: 4; Destroyed: 10

Programs
No data program: Slave unit, controlled remotely by a master robot or a human with a control unit.
No command program (Slaved): No command program; unit is controlled remotely by a master robot or a human with a control unit.

Chassis
Slave Unit; Acoustical Speaker; Radio, Distant (5 km); Power Interface;
1x 5km Laser Communicator;

Head #1
2 Visual Sensors; +1 Light Intensifying; 1 Audio Sensor;

The Cargo Remote sierra (CR-s) is an Imperial military bot intended to provide cargo support at the company level. Unlike the CR-a, the CR-s is self-powered, with a fuel cell and fuel for up to 19 hours of operation. The bot's body, at 44 cm length and width by 11 cm height, is optimized for carrying small loads, and the bot can carry up to 64 kg. The bot must be loaded or unloaded by troops or a pony; it does not have arms.

The bot has a pair of visual sensors with light intensification and an audio sensor. The bot has no brain; it is remotely operated by a master robot, typically the company pony, to shuttle cargo between the pony and the company's platoons, with one CR-c available for each platoon. If the pony controlling it is damaged, the bot can also be moved by humans using a backup hand-held controller. The bot has a short-range laser communicator (5 km range) mounted externally, allowing the master unit to maintain control even in the face of battlefield radio jamming; with the laser comm and its on-board speaker, the bot can also serve as an improvised communications link.

 

[Carlobrand]

Remote Visual Sensor alfa

01x0B-N2-00xx0-0930(0)
Cr21,319
5-liter Box/Wedge; Chassis dimensions: 28 cm tall/long by 14 cm by 14 cm
Armor, Striker: TL 15 Bonded Superdense, Armor 18
1 head (40%)
2 very light arms;
Tracks; Speed: 2 (12 kph; 200 meters per minute), 1 (6 kph; 100 meters per minute) in rough terrain
Power: Battery powered
Fuel: N/A
Batteries: 3.4 KWh; Duration: 0.18 hours
Designed Cargo Capacity: 53 kg.
Mass: 46.39 kg unloaded, 99.39 kg loaded
Inoperable: 1; Destroyed: 3

Programs
No data program: Slave unit, controlled remotely by a master robot or a human with a control unit.
No command program (Slaved): No command program; unit is controlled remotely by a master robot or a human with a control unit.

Chassis
Slave Unit; Radio, Distant (5 km); Power Interface;
Laser Carbine (self-powered); RAM Auto Grenade Launcher (self-powered);
1x 5km Laser Communicator;

Head #1 (no installed items)

Appendage #1: TL 8 Arm, very light
1 Visual Sensor; +1 Light Intensifying; 1 Audio Sensor;
Appendage #2: TL 8 Arm, very light
1 Visual Sensor; +1 Passive Infrared;

The Remote Visual Sensor alfa (RVS-a) is an Imperial military bot intended to provide observation at the squad level. The bot's body, at 28 cm length by 14 cm width and height, is the smallest producible, a bit smaller than a shoebox. One very light arm carries a visual sensor with light intensification augmentation and an audio sensor, and a second carries a visual sensor with passive infrared augmentation, permitting the bot to see and hear above ground cover, around corners, etc.

The bot has no brain; it is remotely operated by a human controller using a control box, feeding audio and visual input back to the controlling unit. It is typically controlled and powered by wire but can also be operated on battery by radio. Standard battery duration is 20 minutes with a TL12 battery, sufficient for a radio-controlled return to origin over a range of 2000 meters in rough terrain if the wire is cut, or to continue function while another bot comes out with a replacement wire; the bot has a radio communicator, and a short-range laser communicator is mounted externally to allow the unit to continue secure communication and control if the wire is cut. It is possible but not cost-effective to use a more powerful battery; the larger RVS-I is more often used for roles requiring extended operation on independent power.

The RVS-c is used in the picket role, positioned in concealment around a perimeter to provide observation and early warning of attack. It is well armored to endure all but a direct hit in an artillery barrage, though the power/communication wire represents a point of vulnerability. The bot is typically armed with a chassis-mounted laser carbine for laser designation, allowing the human controller to tag a target without putting himself at risk, and a RAM auto-grenade launcher for attacks of opportunity; the use of these weapons when the power line is cut reduces battery life to 11 minutes. The RVS-a track carriage has a hypothetical load-bearing weight of up to 53 kg. above the unit's weight of 46 kg., though the unit's small size makes it impractical to carry more than a few kilograms without tipping over.

 

[Carlobrand]

Remote Visual Sensor I

3130B-N2-00xx0-C730(0)
Cr56,821
50-liter Box/Wedge; Chassis dimensions: 58 cm tall/long by 29 cm by 29 cm
Armor, Striker: TL 15 Bonded Superdense, Armor 18
1 head (40%)
2 light arms;
Tracks; Speed: 2 (12 kph; 200 meters per minute), 1 (6 kph; 100 meters per minute) in rough terrain
Power: 1x Type D Fuel Cell; available excess power: 1.9Kw
Fuel: 6.8 liters, 27.2 hours
Batteries: 0 KWh; Duration: 0 hours
Designed Cargo Capacity: 37 kg.
Mass: 162.95 kg unloaded, 199.95 kg loaded
Inoperable: 10; Destroyed: 25

Programs
No data program: Slave unit, controlled remotely by a master robot or a human with a control unit.
No command program (Slaved): No command program; unit is controlled remotely by a master robot or a human with a control unit.

Chassis
Slave Unit; Radio, Distant (5 km); Power Interface; Obscuration Device; Extensive ECM;
Laser Carbine (self-powered); RAM Auto Grenade Launcher (self-powered);
1x 5km Laser Communicator; Chemical mine sniffer; Infantry trenching tool;

Head #1
1 Visual Sensor; +1 Light Intensifying; 1 Audio Sensor;

Appendage #1: TL 7 Arm, light
2 Visual Sensors; +1 Telescopic; +1 Light Intensifying; +1 Passive Infrared; 2 Audio Sensors;
Appendage #2: TL 7 Arm, light (no installed items)

The Remote Visual Sensor I (RVS-I) is an Imperial military bot intended to provide observation and fire support at the squad level. Unlike the smaller RVS-a, the bot is self-powered, with a fuel cell and 27 hour fuel supply. The bot's body, at 58 cm length by 29 cm width and height, is still quite small. The bot has two light arms, permitting it to carry standard infantry weapons or other items up to 20 kg.; one light arm has a pair of visual sensors with light intensification, passive infrared and telescopic augmentation, and a pair of audio sensors, permitting the bot to see and hear above ground cover, around corners, etc. The head carries a visual sensor with light intensification and an audio sensor, permitting it to maneuver and look in one direction while the arm looks in another.

The bot has no brain; it is remotely operated by a human controller using a control box, feeding audio and visual input back to the controlling unit. The paired arm sensors allow a human controller using a visor interface or helmet feeds to get a 3-dimensional experience, but there must be a second controller to take advantage of both the arm and head sensors, or the operator is obliged to switch back and forth or to operate in a split-screen mode, dividing his attention. The bot has a short-range laser communicator mounted externally, allowing it to communicate with a controller through a secure laser link without risk of jamming or detection.

The bot is equipped with a chassis-mounted laser carbine and RAM grenade launcher; lacking a brain or programming, the bot cannot use the weapon independently, but the human controller can use the laser as a laser designator and use the grenade launcher to fire on observed enemy units. The bot is used for reconnaissance patrols, to “man” isolated observation posts (either alone or in support of a small team), or to provide fire support from concealed flanking positions, allowing the squad to deliver flanking fire without putting a man in an isolated position.

The chassis also mounts a chemical mine sniffer, allowing the unit to function as a mine detector; in that role, it often takes point for an advancing squad, with one member of the squad operating the controller (typically without the visor interface). The RVS-I carries a standard infantry trenching tool, allowing the operator to dig entrenchments for the unit. The unit can carry up to 37 kg. additional weight but is rarely used for cargo transport.

 

[Carlobrand]

Point Defense Bot

8260D-L2-GL113-PF52(2)
Cr330,874
350-liter Cylinder/Cone; Suggested chassis dimensions: 121 cm tall/long by 61 cm diameter
Armor, Striker: TL 15 Bonded Superdense, Armor 18
1 head (23%)
2 medium arms;
TL 9 UH Grav Mod; Speed: 4 (24 kph; 400 meters per minute ground. 24 kph/667 meters per minute roads. 24 kph top speed in flight.
Power: 3x Type G Fuel Cell; available excess power: 8Kw
Fuel: 35.3 liters, 29.41 hours
Batteries: 0 KWh; Duration: 0 hours
Designed Cargo Capacity: 496 kg.
Mass: 1436.91 kg unloaded, 1932.91 kg loaded
Inoperable: 70; Destroyed: 175

Programs
TL9 High Data: Commands must be explicit. Can analyze and learn from data, gains experience.
Basic Command: Full vocabulary but limited to basic verb-adjective-object commands, must be clearly spoken, cannot understand accents.
Weapon Handling-2, Active; Engineering-1, Storage; Cargo Handling-1, Storage;

Chassis
1 Visual Sensor; +1 Light Intensifying; 1 Audio Sensor;
Voder (speech synthesizer); Radiation Sensors
Radio, Distant (5 km); Power Interface; Program Interface; Obscuration Device; Extensive ECM;
1x 5km Laser Communicator; TL9 Point Defense Fire Control; 2x 5000 rd. hopper (8 bursts);

Head #1
Basic Sensor Package (Includes 2 visual, 2 audio, 1 olfactory); 2 Visual Sensors; +1 Light Intensifying; +1 Passive Infrared;

Appendage #1: TL 6 Arm, medium (no installed items)
Appendage #2: TL 6 Arm, medium (no installed items)

One of the few combat-rated bots in the Imperial inventory, the Point Defense bot is an Imperial military bot intended to provide point defense for an infantry unit at the platoon level. The exception is permitted by Imperial authorities because the bot's mission is to attack munitions only, its weapon lacking the power to be a significant threat except to unarmored troops, and because the only other way to provide for the need is with vehicles. The bot provides point defense capability at a much lower cost than could be achieved with comparably armored vehicles, and it can fit in most vehicles alongside accompanied troops.

The bot is a 61 cm (26”) diameter, 1.2 meter tall grav-propelled barrel containing a TL9 point defense fire control and surmounted by a head mounting a 5.5mm gatling gun; it has the capacity to destroy from 2 to 6 inbound direct fire rounds or 4D6 artillery rounds per gatling burst over a 300 meter radius. Two head-mounted optical sensors with light intensification and passive IR augmentation provide binary vision for ranging while a third and fourth 120 degrees to left and right of the front pair ensure 360 degree visual monitoring; an additional auditory sensor and visual sensor with light intensification are mounted on the chassis to provide sensor function in event of damage to the head. Two 5000-round hoppers provide ammunition for 8 bursts.

The bot can fit through doorways to follow troops into bunkers and vehicles and can enter a typical foxhole to take a hull-down profile; in hull-down profile, the typical direct-fire hit will destroy the gatling and sensor systems while leaving the bot as a whole intact. The bot is armored equivalent to combat armor, carries extensive ECM against thermal and radar detection and mounts smoke projectors.

The bot has a brain with a "high-data" logic program, adequate for its role as a point defense platform since it doesn't have to discriminate between targets or make tactical decisions. In addition to its weapons program, the bot has a basic engineering program and two medium strength arms; it carries a pick and shovel suitable to its strength for basic digging, allowing it to dig its own foxhole or to help dig a trench.

The bot can carry up to 500 kg. load in addition to its normal loadout, sufficient for 8 additional hoppers. However, its design is not optimal for cargo. Attachment points permit attachment of additional hoppers for reload while keeping the firing arc unblocked, and the bot can remove empty hoppers and connect carried hoppers to the loading port independently, but more than two additional containers may interfere with arm operation or require the bot to unload itself to fit through doorways. The bot therefore typically carries cargo only during non-combat movement

 

[Timerover51]

Explosive Ordnance Disposal and Improvised Explosive Device Detector would likely be two immediate areas of use. Loss rate for humans would be sufficiently high to discourage volunteers, and not the easiest job to draft someone too.

 

[Carlobrand]

I can't think of a single adventure or world writeup that mentions the routine employment of robots as substitutes for human workers. Apparently there is some reason why they are not economically sound¹. Perhaps the economic details for robots should be revised? ...

Duly noted. In your TU, Book 8 canon does not apply.

Robots feature in Research Station Gamma, a canon adventure that features the routine employment of robots as substitutes for human workers. They include a security robot armed with a laser. They also feature in Secret of the Ancients, but that's a special case, as are those chips in Signal GK. I can't speak for other sources as my library is rather limited.

I know of no canon sources that speak of robots over TL12 being "not economically sound," and I wouldn't support rewriting canon to reflect one person's preferred TU. However, I'm not so wedded to bots that I would raise a major objection if you want to try such a campaign. My personal opinion is they're rarely seen because Imperials - at least the ones that fly the spaceways - simply prefer to deal with humans. Rich folk today seem to get great pleasure out of having people serve them, and I suspect that will not change in the future. I also suspect there's a certain resistance to having bots take peoples' jobs, but that's not going to stop bots from being built or large corporations from using them; it just means you're less likely to see bots in highly visible roles unless it's doing something a person can't do. That still leaves plenty of room in the background for cargo bots capable of lifting 200 kg loads, repair bots small enough to scamper through small accessways to repair machinery, bot-brained vehicles following a driver's commands and the other kinds of background roles that aren't going to grab attention but in which bots might be preferable.

At any rate, the thread's about military bots. These bots fill roles that would otherwise require a larger and much more expensive vehicle or that extend the capabilities of the soldier without adding unnecessary risk. I have very deliberately chosen roles where the bot would supplement rather than supplant the soldier; in several cases, the bots are in fact remotes operated by the soldier. I would be very pleased to have you comment on them in that vein rather than on some speculative basis. And, since I understand the Ship's Locker to be about introducing new ideas, I'd ask that the fact these haven't been seen before not be used as an indictment against them.

Meanwhile, back at the ranch:

 

[Carlobrand]

Robotic Grav Scooter

6150D-N2-7B001-7F31(1)
Cr19,989
150-liter Box/Wedge; Chassis dimensions: 84 cm tall/long by 42 cm by 42 cm
Armor, Striker: TL 15 Bonded Superdense, Armor 18
1 head (40%)
TL 9 UH Grav Mod; Speed: 4 (24 kph; 400 meters per minute ground. 24 kph/667 meters per minute roads. 24 kph top speed in flight.
Power: 2x Type F Fuel Cell; available excess power: 16.5Kw
Fuel: 23.1 liters, 33 hours
Batteries: 0 KWh; Duration: 0 hours
Designed Cargo Capacity: 600 kg.
Mass: 355.15 kg unloaded, 955.15 kg loaded
Inoperable: 30; Destroyed: 75

Programs
TL8 Low Data: Commands must be explicit. Cannot analyze/learn from sensor data.
Limited Basic Command: Limited 100 word vocabulary, must be clearly spoken, cannot understand accents.
Pilot-1, Active;

Chassis
Voder (speech synthesizer);
Slave Unit; Radio, Distant (5 km);
5 km laser communicator;

Head #1
2 Visual Sensors; +1 Light Intensifying; 2 Audio Sensors;

The Robotic Grav Scooter (RGS) is an Imperial military bot intended to provide inexpensive grav transportation for a four man combat team. 1.68 meters long by 21 cm wide and 42 cm tall, the bot carries up to 4 passengers, with the driver immediately behind the head, one passenger behind the driver, and the two rearmost passengers riding in side seats to either side of the chassis.

The bot has a slave unit for control by a human controller riding it, but it also has a simple brain and pilot program allowing the driver to fly the unit on autopilot; the bot brain will fly a straight course, avoiding obstacles, and will ascend, descend or stop on command, but it lacks capacity for more complex independent flight. Unless over-ridden, the bot's brain will avoid obstacles even while under control of a human controller, allowing the scooter to be flown by someone with no skill. The head mounts a pair of visual sensors augmented by light intensification and a pair of audio sensors.

The bot has a maximum lift capacity of 600 kg over its own weight, allowing it to be used for cargo transport in addition to passenger transport; two 100 kg. cargo boxes can be mounted, one to either side of the chassis under each rear passenger seat; the bot lacks a cargo handling program and must be loaded and unloaded by others, and the loads must be balanced. Usual ground speed is 24 kph (about twice as fast as a running man), allowing the bot to be flown by a person with little or no skill, but with 4 passengers and no additional cargo the bot can reach 40 kph over roads in the hands of a driver with appropriate skill; the robotic brain cannot function in autopilot mode at speeds over 24 KPH and must be overriden to achieve this speed, resulting in loss of the obstacle-avoidance function. In flight mode (above 10 meters altitude) with 4 passengers and no additional cargo, the bot can reach up to 360 KPH; however, the bot lacks radar or ladar systems for high-speed flight, so piloting is entirely visual. The bot has a 33 hour fuel supply.

The RGS is intended for non-combat transport; the seating arrangement provides little room for the passengers to use weapons. The team will typically take the bot to a secure point, dismount, and move forward on foot with the bot falling back to the company motor pool until recalled. The bot can function as an ambulance, with stretchers replacing the side seats and either ridden by a medic/driver or operated remotely in slave mode by a bot or person at the company casualty station.

 

[rancke]

Duly noted. In your TU, Book 8 canon does not apply.

That's not of import. What is of import is that there's no sign that it applies to the OTU either.

Robots feature in Research Station Gamma, a canon adventure that features the routine employment of robots as substitutes for human workers.

Not so much. The scientist involved has made a special effort to get rid of any other human on the research station. I don't think that counts as routine employment of robots for human workers since there a strong ulterior motive involved.

I know of no canon sources that speak of robots over TL12 being "not economically sound," and I wouldn't support rewriting canon to reflect one person's preferred TU.

Nor do I. What I said was that since robots do not seem to be routinely employed, there has to be an explanation for that.

However, I'm not so wedded to bots that I would raise a major objection if you want to try such a campaign.

Well, that would please me no end if I needed your permission to run such a campaign.

My personal opinion is they're rarely seen because Imperials - at least the ones that fly the spaceways - simply prefer to deal with humans. Rich folk today seem to get great pleasure out of having people serve them, and I suspect that will not change in the future. I also suspect there's a certain resistance to having bots take peoples' jobs, but that's not going to stop bots from being built or large corporations from using them; it just means you're less likely to see bots in highly visible roles unless it's doing something a person can't do. That still leaves plenty of room in the background for cargo bots capable of lifting 200 kg loads, repair bots small enough to scamper through small accessways to repair machinery, bot-brained vehicles following a driver's commands and the other kinds of background roles that aren't going to grab attention but in which bots might be preferable.

Except we don't see any of those either.

At any rate, the thread's about military bots.

I was responding to a statement you made that explicitly applied to civilian robots.

And, since I understand the Ship's Locker to be about introducing new ideas, I'd ask that the fact these haven't been seen before not be used as an indictment against them.

Absence of evidence is not proof of absence, but it IS evidence of it. How strong is a matter of opinion. If my opinion inclines me towards a particular conclusion, I feel entitled to express that opinion.

But if you prefer I don't pursue that line of thought, I'll drop it if you will drop it.


Hans

(Talking about evidence of absence, does the Army career provide skill in robot operation¹? :devil

¹ Not a serious indictment. Merely a suggestion that if someone decides to use your no doubt excellent and useful robots in a ATU, they should consider changing the Army skill tables.​

 

[Carlobrand]

That's not of import. What is of import is that there's no sign that it applies to the OTU either. ... But if you prefer I don't pursue that line of thought, I'll drop it if you will drop it. ...

Well done. Either I divert my thread to an argument about bots in the OTU or you win the last word on the subject. Well then, inasmuch as I'd prefer that this particular thread remain on topic, I'll drop it.

 

[aramis]

That's not of import. What is of import is that there's no sign that it applies to the OTU either. ... But if you prefer I don't pursue that line of thought, I'll drop it if you will drop it. ...

Well done. Either I divert my thread to an argument about bots in the OTU or you win the last word on the subject. Well then, inasmuch as I'd prefer that this particular thread remain on topic, I'll drop it.

[m;]The above quoted exchange is on the border of trolling.[/m;]

On both sides.

consider this a public warning.

 

[sabredog]

I can't think of a single adventure or world writeup that mentions the routine employment of robots as substitutes for human workers. Apparently there is some reason why they are not economically sound¹. Perhaps the economic details for robots should be revised?

¹ IMTU terrorists and 'humaniti first' activists enjoy hacking robots so much that safeguards and mandatory insurance payments make them more expensive than human workers in most cases.​

Hans

I don't know if it was something I read in a JTAS or elsewhere, or maybe just something of my own that I came up with to justify the lack of robots IMTU given the surprising lack in the early early days of Traveller (like around 77-80), but I thought it had something to do with Zhodani using them or the like. Like the strange persecution of psionics having something to do with the Zhodani, people felt the same about robots.

Or wasn't there some society that felt robots, like cybernetics, were heretical? I might be waaaay off - nowadays I confuse my house rules with official ones, and official ones with some article I read thirty years ago in Different Worlds and added to my campaign.

For what its worth, I prefer not to use them very much (other than the really stupid ones for helping in construction work and loading ships while directed by a living being with the required skill) is that I try to make sure anything that happens in the game that affects the players is done by a player instead of a magic robot expert.

The closest I have in common types of robots are remote gunbots for security work - mainly colony security. Colonists use them for perimeter defense a lot because they are cheap, easy to maintain, and actual manpower can then be put to better uses in the colony growing yams or something.

 

[rancke]

[m;]The above quoted exchange is on the border of trolling.[/m;]

On both sides.

consider this a public warning.

I don't think that's fair. Both of you are overlooking the option of starting a new thread. I'm perfectly willing to continue the discussion, in this thread or another. I'm perfectly willing to drop the discussion. What I didn't and don't see any justice in was Carlo responding to me, then declaring the debate closed. And I resent being publically accused of devious or trollish behavior on that account.


Hans

 

[Travellerspud]

In this thread, we will present a number of robots possibly used by the Imperial Army and Marines.

Love these Robots and their purposes....thanks for sharing. This fits perfectly with my version of Imperial Infantry (lots of toys).

I have also envisioned Imperial Infantry at the company level using a "dumb" robotic heavy weapon carrier with remote aiming interface (gunner stays hidden) and a 'dumb" robotic mortar carrier (IMTU the Marines don't have this stuff typically, relying instead on orbital fire support and/or air support...unless in a garrison role)

 

[mike wightman]

Very useful design there Carlo - thanks for sharing them.

As to the robots in the Imperium discussion it would make an excellent topic for another thread..

 

[sabredog]

In Gene Wolfe's short story, The HORARS Of War, he describes a small unit action on some hellworld that even he admitted was a thinly disguised incident from his Vietnam experience. Its a pretty good little story but the part that relates here is that one of the "members" of the fireteam is a semi-autonomous weapons carrier the rest of the soldiers named "Pinocchio". It carried a autocannon or recoilless rifle - I forget which, but it is a pretty low tech bunch in the story - and is assigned its own fighting pit on the perimeter. The characters refer to it with some degree of affection or concern as if it was a real soldier.

Of course, the soldiers being HORARS are not exactly real humans, either, so some of that affinity with "Pinocchio" is understandable.

Nowadays there is that "Big Dog" robot being tested by the Marines, and no doubt many other will show up soon around the world. The use the Marines are figuring on for the Big Dog - casualty clearing and resupply carrier in combat zones - is pretty much how I've always figured combat robots to be used for. They seem perfect for that sort of thing since it doesn't require much in the way of command and control.

IMTU I have a couple of drone designs that operate similarly. The Nightingale evacs wounded personnel in battle dress, and the Hornet. While classed as "drones" I've found the line between drone vs robot is pretty fine and most of the time just semantics.



“Nightingale” Casualty Recovery Drone TL-15

The “Nightingale” is a 6 ton drone designed to recover combat casualties even if they are wearing battledress from an active battlefield. The drone is armored to the equivalent of Combat Armor+7, has smoke and anti-laser aerosol dispensers, Advanced ECM, and the “B” models are also beginning to be equipped with the Hydra Point Defense Weapons System to protect it from incoming projectiles. The “Nightingales” also have 2 active ECM “Screamers” (about the size of a rocket-powered beer keg and amazingly shaped like one to no end of amusement to the troops) that are decoys which the drone will deploy when operating in an especially “active” combat zone.

The drone has room on board for 4 casualties in full battledress which it grapples and loads into a rotating drum inside the center of the drone. The drone’s onboard medical systems then plug into the trauma maintenance systems of the battledress (or combat armor) to stabilize the patient. If the condition of the patient is dire enough the drone will then induce cold sleep so the patient can be stabilized until arriving at a casualty clearing station for triage evaluation.

The drones are grav vehicles capable of a 12 hour range at a maximum speed of 360kph, and a nap op earth speed of 200kph.


“Hornet” Hunter-Killer Drone TL-15

Kemmer-Lansing GmbH has developed the “Hornet” hunter-killer drone to provide close support to front line combat troops under a wide variety of conditions. The primary user of the drone are the Imperial Drop Troops and Scout Reconnaissance Regiments assigned to Imperial Line Marine Regiments during wartime.

The 9 ton, grav drone is armored to the equivalent of Combat+9 and capable of speeds of up to 400kph / 250 at nap of earth with a combat range of 6 hours. The drone is semi-autonomous with an active controller monitoring it as it cruises the battlefield in whatever pre-programmed pattern the operator selects, and when encountering an enemy target the operator then selects a response. In case of the operator losing contact with the drone the drone then follows a series of pre-set patrol and combat patterns until it runs low on power and returns to base. During this time active control of the drone can be achieved by any personnel who are equipped to so and are within the drone’s communications range of up to 500km. Friendly personnel are equipped with IFF (Identify Friend or Foe) beacons in their armor so the drone will not engage them as hostiles.

The “Hornet” has Advanced active ECM, anti-laser aerosols, and Hydra PDWS for incoming projectile protection. It also has active chameleon aromr that mimics background colors and patterns to aid in hiding the drone when it is set in "ambush" mode by an operator - lying grounded or nearly so in cover until sent an attack order, or enemy units pass by. The Hornet's offensive capabilities are a primary weapon of either a VRF Gauss Gun w/ a 60 shot (bursts) magazine or a 3cm hyper-velocity autocannon. The autocannon has a magazine loaded with 30 shots (bursts) each of HE, KEAP, and KEAPER ammunition which is selected by either the operator, or if designated to do so by the operator, automatically by the drone itself. The magazine for the autocannon also includes 20 rounds of 30mm, .002kt collapsing rounds fired in single or 4 round bursts.

 

[Carlobrand]

[m;]The above quoted exchange is on the border of trolling.[/m;]

On both sides.

consider this a public warning.

Well, I'll own that I was getting pretty irritated and in consequence getting personal, which is a rule violation by itself, and maybe just a wee little bit sarcastic. Maybe just a bit more than that, in fact. Well, maybe a lot. Apologies to the group, and apologies to Rancke. I'm perfectly willing to take up the Robots in the Imperium question or the question of "last word etiquette" elsewhere, if anyone wishes. Lord knows I'm an opinionated sumgun, and I am occasionally blinded by my brilliance and incapable of seeing my own flaws.

Love these Robots and their purposes....thanks for sharing. This fits perfectly with my version of Imperial Infantry (lots of toys).

I have also envisioned Imperial Infantry at the company level using a "dumb" robotic heavy weapon carrier with remote aiming interface (gunner stays hidden) and a 'dumb" robotic mortar carrier (IMTU the Marines don't have this stuff typically, relying instead on orbital fire support and/or air support...unless in a garrison role)

I was working on models of that type, a bot that basically replaces the carriage on what would otherwise be a towed field weapon, permitting the weapons team greater freedom to move and the ability to fire the weapon remotely from covered positions, and a bot that acts as a missile carrier, allowing an infantry missile team to field heavier missiles than they ordinarily would and - again - giving them the ability to fire missiles remotely.

In the case of the missiles, I'm wondering if it might not be better just to have a pony to carry and place field-mount tube launchers and then go hide with the missile team. That way only the launcher buys it.

...IMTU I have a couple of drone designs that operate similarly. The Nightingale evacs wounded personnel in battle dress, and the Hornet. While classed as "drones" I've found the line between drone vs robot is pretty fine and most of the time just semantics. ...

I like these. Have you considered putting a couple of small slave bots aboard the ambulance drone, to act as stretcher bearers to get the wounded into the vehicle?

I'd like more details on those ECM screamers. High power Radio/radar jammers? Do you put a bot brain in them so they can go evasive and get an evasion DM?