Using Technical skills for Sabotage

[Savar]

[CRMcNeill]

That should translate into a bonus to Disguise.
_________________
"No set of rules can cover every situation. It's expected that you will make up new rules to suit the needs of your game." - The Star Wars Roleplaying Game, 2R&E, pg. 69, WEG, 1996.

The CRMcNeill Stat/Rule Index

[dic1]

Ah yes, the clipboard.
Walks up to guard "I have orders to give this report to the captain"
when the guard turns to call on com system hits him over the head with it.
Never underestimate the usefulness of the clipboard.

[Pel]

Bonus points for the clipboard idea. Always a classic.

I agree that this doesn't require complex game mechanics, just pick a difficulty number based on what the player (or nefarious NPC) wants to do. Might be a good idea to modify the number based on how obvious they want the sabotage to be, to cater to the sneaky players (and GMs!). I wouldn't require a separate Hide roll (unless maybe you're planting a bomb, but that's a completely different skill). Rather, just up the target number and roll the bones.
_________________
Aha!

[garhkal]

[Savar]

[dic1]

If i remember correctly R2 was told of the sabotage by cloud city's computer system.

In our game we describe what effect we are attempting with our sabotage and roll the appropriate repair skill, that is the difficulty to find and repair the damage.
Similar to disarming a booby trap, opposed demolitions rolls.

[Raven Redstar]

I do the same in my games, opposed repair rolls for finding and fixing sabotaged systems.
_________________
RR
________________________________________________________________

[Naaman]

Seems like some forms of techical sabotage could simplycome down to a basic hide roll.

For example, cutting a wire that is inside a panel, and then hiding that wire beneath/amidst a bunch of other wires.

Or simply disconnecting a component just enough so that it is not actually plugged in, but looks like it is (in some cases, components tht do certain things may be common knowldge, like a car battery or a light bulb, etc.).

Lastly, sometimes the sabotage can be "protectd" by obstacles. For example, a force user could use telekinesis to move a refridgerator and then unplug it, and the put it back in its place. Since refridgerators are hard to move, the ability to "repair" to sabotage is limited to the ability to move the refridgerator first.. so there is a lifting component there, even though the tecnical aspect wouldn't even require a roll.

[Error]

This may help!

Shouldn't "Slicing" be an available Technical skill? It's been in the SW universe nearly from the start; it was first given a name in the Thrawn Trilogy way back in the early 90's.

To me, Slicing has always meant "mischief with computers" so it would fit your needs if any computers are involved.

I could see a Slicing skill getting a results tree similar to others, and the good news is you can make it one roll.

Or has this already been done in a sourcebook somewhere?!?!
_________________
The only words of explanation you need for any concept in the entire Star Wars universe are the words Science Fiction and Space Opera.

[Savar]

[Error]

[Whill]

[CRMcNeill]

I had considered combining Droid Programming with Computer Programming, but then I started to wonder if programming a fully functional AI might be a tad more complex than programming a datapad.

If anything, I would think Slicing would be good as an Advanced Skill, with Computer Programming /Repair and Communications as pre-requisites.

However, I do think Droid Repair would be a better fit as Droid / Cybernetics Repair, focusing on the hardware of animated machinery, maybe with the ability to repair Power Armor, as well.
_________________
"No set of rules can cover every situation. It's expected that you will make up new rules to suit the needs of your game." - The Star Wars Roleplaying Game, 2R&E, pg. 69, WEG, 1996.

The CRMcNeill Stat/Rule Index

[Kytross]

Droid programming is focused on working with an AI and likely uses an entirely different programming languages than computer programming.

I keep droid repair as a separate skill because a droid is more complex than a backhoe, and has as little in common with programming. Droid repair means you have to be able to repair or replace repulsor lifts, wheeled drive systems, magnetic feet, walkers, multiple gripping arms, sensors, winches, jets, circular saws, vocabulators, databases, armor, blasters, shields, hydraulics, scomp links, comlinks, hands, arms feet, and probably more things I can't think of.

Computer repair tends to be much simpler. Plug and play, no moving parts, except fans. Sure, there are more difficult skill checks, like recovering a magnetized hard drive, but all-in-all I don't have a problem keeping computer programming/repair as one skill.