Bringing this thread from Reddit, I'm going to be starting a player and redditor-based discussion on Rigger rules and issues people have with them. I'll be breaking these both into Shadowrun Core Rulebook and Rigger 5.0 for clarification, and citing page sources. Please do the same when contributing to the thread to make it easier on everyone working hard here. To start here, I'll post a short, to-the-point list of general concerns and discussions that will be followed in more detail:
- Sensor rules confusion
- Vehicle repair rules
- Speed and ramming
- Vehicle weight, shape and visuals
- Restricted to who? Forbidden outside of which groups?
- Which stats are used where?
- Errata cheat sheets for actions
I Sense a Disturbance in the ForceSensors and sensor operations covered under Electronic Warfare are a major part of what makes Riggers good at what they do. Fly Spies, helmet-equipped sensors, handheld, all of those are incredibly handy and work very well for us. The following is from page 445 SR5:
Sensors need to be placed in a housing or case of some sort, or built into another device. Sensors can record data themselves or forward it wirelessly in real-time or as files to other devices. Sensors are available in seven ratings (2–8) and two types: single and array. When you use the sensor array for Perception Tests, you may use your Electronic Warfare skill in place of your Perception skill, and you may use the sensor’s Rating as your limit. Sensor array: This sensor package includes up to eight functions listed under Sensor Functions. Single sensor: This is a sensor that can do only one function listed under Sensor Functions.
Sensors can be put into devices that have capacity. Most vehicles and drones come factory-equipped with a sensor array (at a rating listed with their stats). What you can put your sensor in is limited by the Rating of the sensor (see Sensor Housings table).Two instances of 'may', implying choice on whichever is better. Perfect. Another issue brought up is that this implies vehicles and drones need to choose Sensor Functions from the table, up to their Sensor rating. Some clarification if there's any "freebies" would be good, or how they will function without cameras. Most come with a Rating 2, which means Camera and Microphone would be appropriate fits.
This is from page 199 SR5:
Sensor is a rating representing the suite of information-gathering or detection devices that are built into every vehicle in the Sixth World. Sensor acts as the limit for Perception and other detection tests using the vehicle’s systemsThis is from page 269 SR5:
A drone observes its surroundings with a Pilot + Clearsight [Sensor] Test. If you’re jumped into the drone, you make a Perception + Intuition [Sensor] Test. Either way, you get to use the drone’s entire sensor suite, if it has one.Three conflicting sides here. The original sensor and sensor array says you can use whichever stat or limit you prefer. It also goes on to say that the same type of sensors are placed in vehicles and drones, which then follow Perception [Sensor] rules. Vehicles imply Electronic Warfare with "other detection tests" and drones simply apply Perception. I'm under the impression that following the baseline Electronic Warfare [Mental] is legal, as the section makes it clear that it is an intended mechanic. Perception could also get knocked down a peg or two for something else to take it's place when equipment is used.
Coming from Rigger 5.0, we have the wonderful Target Device Action:
Pick a wireless-enabled device you’ve spotted on the Matrix. You can target that device and feed targeting data to any pilot program or person with a Sensor rating or smartlink that is slaved to your RCC. For the rest of the Combat Turn, the slaved attackers receive a dice pool bonus equal to your net hits when targeting the device you’re tracking for them. Your RCC’s Noise Reduction rating is added as a dice pool bonus for this action.This clearly implies drones and vehicles as great targets for bonus dice. "Wireless-enabled device" is a broad category, and my first though was adding bonuses to Called Shots or normal attacks on wireless-enabled armor. Just looking to get some clarification in the action's description on what's allowed and not.
You Kicked My Drone! You Fragging Guy!Ahh, good ol' repair rules for Riggers, the eternal discussion. As it stands, Riggers are just as equipment dependent as Deckers, but have a risk so high that they fit into their own category. Drones and vehicles are expensive and hard to replace with Shadowrun games. Losing a car can mean multiple runs of nothing but eaten costs, not to mention the fact that you're down a critical component of your character. Some would say this is a balancing factor, some would say this is just too punishing. I subscribe to the belief that if the Rigger isn't a dick, the GM shouldn't be a dick. Riggers straight out of chargen can bull some pretty ridiculous moves with slaved drones, but stealing the show and breaking the game isn't (usually) fun for everyone else. I don't blame the GM that pulls out the rocket launcher to destroy the swarm of Assault Rifle Rotodrones that just crashed through the windows of the office building.
SR5 Page 270:
Drones have two damage tracks, Physical and Matrix. Fill up either one and it’s bye-bye birdie as the drone is either irreparably destroyed and joins the spare parts collections, or it gets bricked and it’s time to completely rewire its guts. But up until that final box is filled, damage done to a drone can be repaired. Repairing Physical damage follows the rules for building and repair on p. 145. To repair Matrix damage, check out Repairing Matrix Damage, p. 228. If the chassis and the electronics of your drone get trashed, it will probably cost you more to fix it than buy a new one. But if it has sentimental value, ain’t it worth it?That's pretty harsh, and the rules for repairing weren't terribly fleshed out, however we have this little nugget from Run Faster Page 221:
A garage is a large covered area with enough space to park and maintain a single vehicle. With the purchase of a Shop (p. 443, SR5) related to the vehicle, 1 box of damage to the vehicle can be repaired per week without additional financial cost, as the cost is absorbed by the lifestyle. Purchasing a Facility increases the repair rate to 2 boxes of damage. Use the Build and Repair rules for quicker repairs (p.145, SR5, and p. 143, Run & Gun). This asset can be purchased more than once so that multiple vehicles can be serviced at the same time. The points cost, monthly nuyen cost, and minimum lifestyle depend on the nature of the vehicle, as listed in the table.Awesome. This is quite sensible. It doesn't clarify if you can do it to drones of the appropriate Garage type, but I'd assume so. Hell, given small drones, I'd say it's fair game to give them more boxes back, since vehicles are a larger job and bigger cost.
Thankfully, there's some clarification from Rigger 5.0 Page 29:
To repair a vehicle or drone, you need to have the parts on hand. These can be purchased from any shop, hardware store, or junk yard for five percent of the cost of the vehicle or drone per box of damage on the Condition Monitor that needs to be repaired. You can also scavenge parts off of similar vehicles—more about that later on. If you don’t have sufficient parts for your repair, you’ll take a penalty to the Extended Technical Skill Test, depending on how short you are: Increase the interval to one day, and for every box worth of parts you lack, you take a –4 dice pool penalty.
You can tear parts out of a working vehicle or drone (the target) for use in the repair of a similar vehicle or drone (your gamemaster will tell you if your scavenging victim is similar if you’re not sure). First, decide how much damage you’re willing to inflict on the target, in Condition Monitor boxes. Then the target takes that damage (with no chance to resist) and you make an appropriate Mechanic skill + Logic [damage inflicted] Test. For every two hits, you scavenge one box worth of parts for your repair job.Awesome, the scavenging part makes perfect sense and adds another layer of depth to rigging. The 5% per box rule is very strange, because it doesn't scale properly with how the damage box system works. We also have a number of reasons why the damage box system is already confusing and doesn't work properly with vehicles and drones. It was designed for meat bodies, and has no problems there. Vehicles may take a ton of damage from an Assault Rifle, shredding the cab and killing the occupants three times over, but that doesn't translate properly to "The vehicle is now broken, unusable, and can never be repaired). The following is a Reddit thread I started ages ago that has some good discussions detailing the issues with it:
https://www.reddit.com/r/Shadowrun/comments/4fjpmq/rigger_vehicledrone_damage_houserule_ideas/Differentiating between superficial, component, and structural damage would go a long way for vehicles. Unfortunately due to varying drone / vehicle size, weapon types and such, I don't have a good solution for what would be a relatively simple way to define what type of damage each is. Requiring Called Shots on vehicles with certain weapons may be a viable solution as well.
Perhaps today is a good day to die! PREPARE FOR RAMMING SPEED!I can't speak for anyone else, but sometimes the most brainless, crude and brutish options are the best. I am of course talking about ramming. And with ramming, we have to talk about speed. I'll just link this one Reddit thread because the math is so well-known to be silly:
https://www.reddit.com/r/Shadowrun/comments/3bw7fg/vehicle_speeds/Decent vehicles with Control Rigs or even Speed upgrades can hit hundreds or thousands of km/h easily. For the most part this isn't really a big deal as any GM would houserule "You're not going to break the speed of sound in your stupid motorbike and survive". Adding in the optional rule of extra defense dice per level of speed gets pretty funny too. That guy moving at 300 km/h is only getting a few dice penalties instead of being essentially impossible to hit?
Switching over to ramming, we have the ramming chart on SR5 Page 203:
If a driver wants to ram something (or someone) with the vehicle, treat it as a melee attack. The target must be within the vehicle’s Walking or Running Rate (a –3 dice modifier applies if the driver has to resort to running). The driver rolls Vehicle skill + Reaction to attack. The target rolls Reaction + Intuition if a pedestrian, or Reaction + Intuition [Handling] if driving another vehicle. Pedestrians may use the Full Defense (p. 191) or Dodge (p. 191) Interrupt Action but not Block or Parry. If the driver gets more hits, he rams the target. Make the Damage Resistance Test as normal. The base Damage Value of the attack is determined by the ramming vehicle’s Body and speed, as noted on the Ramming Damage Table. The ramming vehicle must resist only half that amount (round up). Characters resist ramming damage with Body + Armor – 6 AP.
1-10 Body / 2
11-50 Body
51-200 Body x 2
201-300 Body x 3
301-500 Body x 5
501+ Body x 10The funny part here is that the damage is only based upon the ramming vehicle, not his target. Taking the Ares Roadmaster (Body 18 and Armor 18), an excellent ramming vehicle, this is what the chart ends up looking like:
Less than 15k/h = Half Body (9P -6)
15km/h - 65km/h = Body (18P -6). This sounds about right for killing a pedestrian with a big vehicle
66km/h - 250km/h = Body x2 (36P -6). Note that the Roadmaster has 18 Armor and can't take damage from this.
250 km/h - 350 km/h = Body x3 (54P -6). Goddamn, hope you didn't like whoever got hit by that. With this, the Roadmaster is taking a 27P hit. The question of vehicle Hardened Armor comes in to play (Hero Lab agrees it's hardened and it makes sense. Should it work for crashes and hits?) and either way, the vehicle is realistically surviving this hit without much damage.
Let's take a look at a Hyundai Shin-Hyung, a little more sensible vehicle. Body 10 Armor 6.
Less than 15k/h = Half Body (5P -6)
15km/h - 65km/h = Body (10P -6). No damage at this point with 6 Hardened Armor, or rolling 16 to beat 5P, so probably zero damage.
66km/h - 250km/h = Body x2 (20P -6). Only has to resist 10 damage with 16 Boxes (Or 7 with Hardened Armor benefits).
250 km/h - 350 km/h = Body x3 (30P -6). 17 Physical Damage boxes and the MAXIMUM damage that can be done here is 15. Realistically that car's still driving away after crashing at around 300 km/h. Safety standards to make anyone proud.
Not much else to say. Definitely needs to be looked at, and to consider the ramming target. Rigger 5.0 Page 176 has some more clarification upon ramming, but it still has the same general issues. At least it covers head-on collisions.
"I'm not making that out too well. What is it, Hudson"?
"You tell me, man. I only work here."This issue I've had isn't a gamebreaker, but it's probably added some confusion at more tables than just mine. Many of the vehicles and drones are given pictures and comparable real-life counterparts. Unfortunately, 'most' does not mean 'all', and it gets especially tricky when dealing with drones and equipment that is unfamiliar to most laymen. Adding a few more fluff stats to the equipment would go a long way to helping alleviate some of this confusion. Weights, dimensions, pictures and comparison to an average human would be awesome.
Licenses and LegaleseThis falls a little more into general Shadowrun concerns, but it definitely hits Riggers because of their variety of equipment. Whether an item is Restricted or Forbidden, it's not made clear who is actually legally allowed to use it. In regards to Restricted for players, or possibly Forbidden and Con shenanigans, it would be nice to see a descriptor for what kind of license and job would be fair game for who can have a license for the item. A number of vehicles and drones are clearly intended for law enforcement, emergency response, military, private investigator use, and so on. Not a huge issue, but it comes up.
Crunchy! Soft! Crunchy! Soft!The question of which stats are appropriate to use for jumped in and not jumped in.
Manual ControlPilot Vehicle - Reaction
Gunnery - Agility
Sensors - Questionable
Stealth - Reaction vs. Sensors (SR5 Page 184), Intuition vs. Lifeforms (SR5 Page 270)
Remote ControlPilot Vehicle - Reaction
Gunnery - Logic
Sensors - Questionable
Stealth - Reaction vs, Sensors, Intuition vs. Lifeforms
Jumped InPilot Vehicle - Questionable
Gunnery - Logic
Sensors - Questionable
Stealth - Reaction vs. Sensors, Intuition vs. Lifeforms
Sensors remain questionable because of the original Sensor topic posted early on. SR5 Page 270 clearly states that Jumped In Stealth is Intuition. SR5 Page 205 says that Vehicle Defense tests are Reaction + Intuition, nothing to do with piloting. The debate concerning Reaction vs. Intuition boils down to not using meat stats while jumped in, where Reaction is kind of in a funny position of being half and half. Then there is the concern of splitting a fundamentally critical skill for Riggers into separate stats based upon the situation. What's balanced? What's sensible? It could go either way, just hoping for clarification.
The very last thing I would like to mention is an official cheat sheet detailing these charts for easy access instead of ripping through the book every time. Thank you all for your hard work, I hope we've helped with our feedback and playtesting.