Engineering

From LegendWiki
Revision as of 23:12, 5 August 2017 by Vicerious (talk | contribs) (Created page with "==Engineering (Int)== Engineering covers buildings, structures, and mechanical technology. ===Identification=== Creatures with the {{Bracket|Construct}} type. ===Structural...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Engineering (Int)

Engineering covers buildings, structures, and mechanical technology.

Identification

Creatures with the [Construct] type.

Structural Repair

You can repair a fault in a structure or device; or, if it's a particularly large structure or device that would require more than one person's work, you can at least figure out how to repair the fault and explain to others how to fix it. The DC is equal to the DC for identifying the fault +2.

Structural Design

You can design a new mechanical device or advanced structure. Any implementation of your design requires GM approval. The DC is equal to identifying faults in a similar device +5.

Identify Fault

You can identify faulty structural or mechanical engineering. If you examine an [Average] or smaller device for 5 minutes, you can identify faults or sabotage in the device. A [Large] device must be examined for 15 minutes, and a [Huge] or larger device must be examined for an hour. DCs are outlined below.

  • DC 10: You can identify faults in a basic mechanical device, such as a horse-drawn wagon. Structurally, you can identify faults in a livestock barn. 
  • DC 15: You can identify faults in a more complex mechanical device, such as a well-built crossbow or (if your setting has them) a double-action revolver.
  • DC 20: You can identify faults in a highly complex mechanical device, such as a pocket watch or a self-propelling ship. Structurally, you can identify faults in a suspension bridge. 
  • DC 25: You can identify faults in the body parts of a golem or other [Construct]. Structurally, you can identify faults in large or particularly mobile structures, such as a submarine.
  • DC 30: You can identify faults in the decision-making cortex of a golem or information terminal. You can identify faults in programmable or autonomous structures, such as a hovercar.
  • DC 35: You can identify faults in truly massive or complex systems, such as a flying city.