Difference between revisions of "SR5:Matrix:Complex Forms"
(Merge Kill Code forms into alphabetical listing) |
m (→Cleaner) |
||
(5 intermediate revisions by the same user not shown) | |||
Line 2: | Line 2: | ||
{{SR5:Matrix Rules Navigation}} | {{SR5:Matrix Rules Navigation}} | ||
− | ==Arc Feedback== | + | ==All Streams== |
+ | |||
+ | ===Arc Feedback=== | ||
;Target:Icon | ;Target:Icon | ||
;Duration:S | ;Duration:S | ||
Line 24: | Line 26: | ||
;Source:Kill Code | ;Source:Kill Code | ||
− | ==Bootleg Program== | + | ===Bootleg Program=== |
;Target:Device | ;Target:Device | ||
;Duration:I | ;Duration:I | ||
Line 42: | Line 44: | ||
;Source:Kill Code | ;Source:Kill Code | ||
− | ==Cleaner== | + | ===Cleaner=== |
;Target:Persona | ;Target:Persona | ||
− | ;Duration: | + | ;Duration:P |
;Fading:L-2 | ;Fading:L-2 | ||
Line 54: | Line 56: | ||
;Source:Core | ;Source:Core | ||
− | ==Coriolis== | + | ===Coriolis=== |
;Target:Persona | ;Target:Persona | ||
;Duration:E (5, 24 hours) | ;Duration:E (5, 24 hours) | ||
Line 60: | Line 62: | ||
;Source:Chrome Flesh | ;Source:Chrome Flesh | ||
− | ==Derezz== | + | ===Derezz=== |
;Target:Persona | ;Target:Persona | ||
;Duration:I | ;Duration:I | ||
Line 76: | Line 78: | ||
;Source:Data Trails | ;Source:Data Trails | ||
− | ==Diffusion of [Matrix Attribute]== | + | ===Diffusion of [Matrix Attribute]=== |
;Target:Device | ;Target:Device | ||
;Duration:S | ;Duration:S | ||
Line 89: | Line 91: | ||
;Source:Core | ;Source:Core | ||
− | ==Editor== | + | ===Editor=== |
;Target:File | ;Target:File | ||
;Duration:P | ;Duration:P | ||
Line 103: | Line 105: | ||
;Source:Core | ;Source:Core | ||
− | ==FAQ== | + | ===FAQ=== |
;Target:Device | ;Target:Device | ||
;Duration:P | ;Duration:P | ||
Line 121: | Line 123: | ||
;Source:Data Trails | ;Source:Data Trails | ||
− | ==Host Emulator== | + | ===Host Emulator=== |
;Target:Self | ;Target:Self | ||
;Duration:P | ;Duration:P | ||
Line 154: | Line 156: | ||
;Source:Kill Code | ;Source:Kill Code | ||
− | ==IC Tray== | + | ===IC Tray=== |
;Target:Host | ;Target:Host | ||
;Duration:I | ;Duration:I | ||
Line 166: | Line 168: | ||
;Source:Data Trails | ;Source:Data Trails | ||
− | ==Infusion of [Matrix Attribute]== | + | ===Infusion of [Matrix Attribute]=== |
;Target:Device | ;Target:Device | ||
;Duration:S | ;Duration:S | ||
Line 185: | Line 187: | ||
;Source:Core | ;Source:Core | ||
− | ==Mirrored Persona== | + | ===Mirrored Persona=== |
;Target:Self | ;Target:Self | ||
;Duration:I | ;Duration:I | ||
Line 202: | Line 204: | ||
;Source:Kill Code | ;Source:Kill Code | ||
− | ==Misread Marks== | + | ===Misread Marks=== |
;Target:IC | ;Target:IC | ||
;Duration:P | ;Duration:P | ||
Line 220: | Line 222: | ||
;Source:Data Trails | ;Source:Data Trails | ||
− | ==Pinch== | + | ===Pinch=== |
;Target:Self | ;Target:Self | ||
;Duration:S | ;Duration:S | ||
Line 239: | Line 241: | ||
;Source:Kill Code | ;Source:Kill Code | ||
− | ==Primed Charge== | + | ===Primed Charge=== |
;Target:Self | ;Target:Self | ||
;Duration:I | ;Duration:I | ||
Line 252: | Line 254: | ||
;Source:Kill Code | ;Source:Kill Code | ||
− | ==Pulse Storm== | + | ===Pulse Storm=== |
;Target:Persona | ;Target:Persona | ||
;Duration:I | ;Duration:I | ||
Line 264: | Line 266: | ||
;Source:Core | ;Source:Core | ||
− | ==Puppeteer== | + | ===Puppeteer=== |
;Target:Device | ;Target:Device | ||
;Duration:I | ;Duration:I | ||
Line 281: | Line 283: | ||
;Source:Core | ;Source:Core | ||
− | ==Redundancy== | + | ===Redundancy=== |
;Target:Device | ;Target:Device | ||
;Duration:S | ;Duration:S | ||
Line 296: | Line 298: | ||
;Source:Data Trails | ;Source:Data Trails | ||
− | ==Resonance Bind== | + | ===Resonance Bind=== |
;Target:Persona | ;Target:Persona | ||
;Duration:S | ;Duration:S | ||
Line 316: | Line 318: | ||
;Source:Kill Code | ;Source:Kill Code | ||
− | ==Resonance Cache== | + | ===Resonance Cache=== |
;Target:IC | ;Target:IC | ||
;Duration:I | ;Duration:I | ||
Line 330: | Line 332: | ||
;Source:Kill Code | ;Source:Kill Code | ||
− | ==Resonance Channel== | + | ===Resonance Channel=== |
;Target:Device | ;Target:Device | ||
;Duration:S | ;Duration:S | ||
Line 342: | Line 344: | ||
;Source:Core | ;Source:Core | ||
− | ==Resonance Spike== | + | ===Resonance Spike=== |
;Target:Device | ;Target:Device | ||
;Duration:I | ;Duration:I | ||
Line 355: | Line 357: | ||
;Source:Core | ;Source:Core | ||
− | ==Resonance Veil== | + | ===Resonance Veil=== |
;Target:Device | ;Target:Device | ||
;Duration:S | ;Duration:S | ||
Line 370: | Line 372: | ||
;Source:Core | ;Source:Core | ||
− | ==Search History== | + | ===Search History=== |
;Target:Device | ;Target:Device | ||
;Duration:I | ;Duration:I | ||
Line 383: | Line 385: | ||
;Source:Kill Code | ;Source:Kill Code | ||
− | ==Static Bomb== | + | ===Static Bomb=== |
;Target:Self | ;Target:Self | ||
;Duration:I | ;Duration:I | ||
Line 398: | Line 400: | ||
;Source:Core | ;Source:Core | ||
− | ==Static Veil== | + | ===Static Veil=== |
;Target:Persona | ;Target:Persona | ||
;Duration:S | ;Duration:S | ||
Line 413: | Line 415: | ||
;Source:Core | ;Source:Core | ||
− | ==Stitches== | + | ===Stitches=== |
;Target:Sprite | ;Target:Sprite | ||
;Duration:P | ;Duration:P | ||
Line 424: | Line 426: | ||
;Source:Core | ;Source:Core | ||
− | ==Weaken Data Bomb== | + | ===Weaken Data Bomb=== |
;Target:File | ;Target:File | ||
;Duration:I | ;Duration:I | ||
Line 437: | Line 439: | ||
;Source:Kill Code | ;Source:Kill Code | ||
− | ==Weaken Encryption== | + | ===Weaken Encryption=== |
;Target:File | ;Target:File | ||
;Duration:I | ;Duration:I | ||
Line 450: | Line 452: | ||
;Source:Kill Code | ;Source:Kill Code | ||
− | ==Tattletale== | + | ===Tattletale=== |
;Target:Persona | ;Target:Persona | ||
;Duration:P | ;Duration:P | ||
Line 463: | Line 465: | ||
;Source:Core | ;Source:Core | ||
− | ==Transcendent Grid== | + | ===Transcendent Grid=== |
;Target:Self | ;Target:Self | ||
;Duration:I | ;Duration:I | ||
Line 478: | Line 480: | ||
;Source:Core | ;Source:Core | ||
+ | |||
+ | ==Stream Specific== | ||
+ | ===Overdrive=== | ||
+ | ;Stream: Cyberadept | ||
+ | ;Target: Cyberware | ||
+ | ;Duration: S | ||
+ | ;FV: L+1 | ||
+ | |||
+ | Like the power of the same name used by great | ||
+ | form machine sprites, the Cyberadept can put a single | ||
+ | piece of their cyberware into Overdrive. This power can | ||
+ | only be used on cyberware that is currently installed | ||
+ | in the Cyberadept. The Cyberadept rolls a Software + Resonance [Level] Test. | ||
+ | Half the net hits (rounded up) | ||
+ | are added to the effective rating of the cyberware. | ||
+ | This can—and often will—push a piece of cyberware | ||
+ | way past its intended limits. When this complex form | ||
+ | is no longer sustained, the cyberware takes a number | ||
+ | of boxes of Matrix damage equal to the level of the | ||
+ | complex form. This damage cannot be resisted. On a | ||
+ | glitch, the cyberware is bricked, filling its Matrix Condition Monitor. | ||
+ | On a critical glitch, the damage is physical, | ||
+ | rather than Matrix. The rules for repairing Matrix | ||
+ | Damage appear on p. 228, SR5. The rules for repairing | ||
+ | Physical Damage to gear appear on p. 143, Run & Gun. | ||
+ | |||
+ | ===LOTO=== | ||
+ | ;Stream: Machinist | ||
+ | ;Target: Device | ||
+ | ;Duration: I | ||
+ | ;FV: L-1 | ||
+ | |||
+ | Using this ability, a Machinist can disrupt the | ||
+ | signals going to and from a machine, separating it | ||
+ | from its master(s). This power can be used on any | ||
+ | device. When using it, the Machinist rolls a | ||
+ | Software + Resonance [Level] v. Willpower + Firewall | ||
+ | Opposed Test. The device is completely disabled | ||
+ | for a number of Combat Turns equal to the net hits on the test. | ||
+ | In the case of something that has a Pilot rating, the Pilot loses functionality as well. | ||
+ | |||
+ | ===Hyperthreading=== | ||
+ | ;Stream: Sourceror | ||
+ | ;Target: Complex form | ||
+ | ;Duration: Varies | ||
+ | ;FV: Varies | ||
+ | |||
+ | The Sourceror can merge multiple complex | ||
+ | forms into a single form, making multiple results | ||
+ | in a single action. Doing so has its limits; | ||
+ | the target and level for the Hyperthreaded Form must be | ||
+ | the same for all merged complex forms. Resolve | ||
+ | effects with a single Software + Resonance [Level] Test, | ||
+ | the results of which are used for all the merged complex forms. | ||
+ | The Fading Value is determined by taking the highest Fading Value of all the | ||
+ | merged complex forms, and then adding 1 point | ||
+ | for each complex form added after the first; | ||
+ | the -2 bonus for being a Sourceror is applied at the end. | ||
+ | |||
+ | ===Sprite Pet=== | ||
+ | ;Stream: Technoshaman | ||
+ | ;Target: Sprite | ||
+ | ;Duration: P | ||
+ | ;FV: L+0 | ||
+ | |||
+ | This complex form allows a technomancer to | ||
+ | convince a registered sprite to become his “pet” and | ||
+ | stick around even when other sprites are around. It | ||
+ | can only be used on a single sprite at a time. | ||
+ | Because this complex form takes several hours to | ||
+ | complete, it can be considered a sort of “digital ritual.” | ||
+ | The Technoshaman spends a number of hours | ||
+ | equal to the sprite’s level attuning himself to the | ||
+ | sprite. At the end of this time, the Technoshaman | ||
+ | pits his Software + Resonance [Level] against the | ||
+ | Level x 2 of the sprite. If the Technoshaman gets | ||
+ | more hits, he feeds the sprite a number of Karma | ||
+ | equal to the sprite’s level. If this is done, the sprite | ||
+ | becomes a sprite pet. This means that the sprite no | ||
+ | longer has a limit on favors and tasks and can be | ||
+ | active at the same time as any other sprite. It also | ||
+ | no longer counts against the Technoshaman’s limit | ||
+ | on registered sprites. This can only be done on | ||
+ | one sprite at any given time. If the sprite pet is destroyed, | ||
+ | it will return to its home Resonance Realm, | ||
+ | and the Karma spent is lost. |
Latest revision as of 18:56, 19 May 2022
5th Edition Rules |
---|
Basics // Combat // Magic // Matrix // Driving // Character Creation |
Basics | Skills/Attributes | Actions | Jargon | Cyberdecks | Programs | How To | Complex Forms | Echoes | Sprites | Sprite Powers | IC |
---|
All Streams
Arc Feedback
- Target
- Icon
- Duration
- S
- Fading
- L-2
Arc Feedback grants the technomancer the ability to catch some of the energy of a successful attack against them and send it back toward the attacker. While a technomancer is sustaining this form, every time they receive Matrix damage — that is to say, damage remaining after any and all resistance rolls — they roll Software + Resonance [Level] v. Willpower + Firewall of the attacker. If the test succeeds, the damage the technomancer was not able to resist is reflected back to the attacker at a ratio of 1 point of damage for every 2 inflicted on the technomancer. Net hits on the test increase the damage, and the total damage must be resisted by the original attacker. Damage reflected back on the attacker does not reduce the damage taken by the technomancer.
- Source
- Kill Code
Bootleg Program
- Target
- Device
- Duration
- I
- Fading
- L-2
Target a device and make an opposed Software + Resonance [Level] vs. Willpower + Firewall test. On a successful test, the technomancer may copy the effects of one program currently running on the device for a number of combat turns equal to the number of net hits. This complex form may not copy an agent or a program the technomancer already knows as a Resonance [program] echo (p. 258, SR5). A technomancer may only benefir from one Bootleg Program at a time; threading a new Bootleg Program complex form cancels any remaing effects of the previous one.
- Source
- Kill Code
Cleaner
- Target
- Persona
- Duration
- P
- Fading
- L-2
Illegal actions leave traces in the Matrix, but the Resonance can erase a few of them. Make a Simple Software + Resonance [Level] test. For each hit, reduce the target’s Overwatch Score by 1.
- Source
- Core
Coriolis
- Target
- Persona
- Duration
- E (5, 24 hours)
- Source
- Chrome Flesh
Derezz
- Target
- Persona
- Duration
- I
- Fading
- L-1
A stiletto or ice pick as opposed to the typical superheated sledgehammers, the Resonance energy from this form slides into the cracks and holes in the target’s armor and strips it away slightly. Make a Software + Resonance [Level] v. Willpower + Firewall test, doing 1 box of Matrix damage per net hit, and dropping the target’s Firewall attribute by 1 until the device has rebooted. Additional successful Derezz attacks do not stack the Firewall adjustment, even if they are from two separate technomancers.
- Source
- Data Trails
Diffusion of [Matrix Attribute]
- Target
- Device
- Duration
- S
- Fading
- L-2
This complex form entry is shorthand for four different complex forms, one for each Matrix attribute. Make an Opposed Software + Resonance [Level] v. Willpower + Firewall test. If you win, the target’s attribute is reduced by your net hits. You can’t reduce an attribute to less than 1.
- Source
- Core
Editor
- Target
- File
- Duration
- P
- Fading
- L-1
You infuse a file with Resonance long enough to manipulate its contents. Make a Software + Resonance [Level] test against the Intuition + Data Processing of the file’s owner. You can make the same amount of changes to the file that you would be able to make with your net hits in Edit File actions.
- Source
- Core
FAQ
- Target
- Device
- Duration
- P
- Fading
- L-3
Scanning the very darkest depths of the Matrix to find out exactly what has been going on with the device they physically have or the host they are current inside of, the technomancer is able to delve into the very deepest questions to find out the true purpose of it. Make an immediate Computer + Intuition [Level] Test with Level / 2 (rounded up) dice added to the pool from the complex form. Gamemasters should provide information to the player based on the number of hits this test generates, with truly obscure or long-forgotten bytes of information requiring 6 hits.
- Source
- Data Trails
Host Emulator
- Target
- Self
- Duration
- P
- Fading
- L
Sometimes the target needs to believe that they’re in a regular host doing typical things when a runner needs that target to be doing anything but that. And sometimes a little illusion is all you need to log a target’s keystrokes or get their banking PINs. Whatever it is, it’s always better to have a host emulator in your back pocket, just in case. When threading the Host Emulator complex form, a technomancer makes a Software + Resonance [Level] simple test. They create a host that looks legitimate, but is not, though the pseudo-host does appear to have been created through official channels. This pseudo-host seems functional but does not store any data and cannot make or run IC. The technomancer may attempt to make the pseudo-host appear to be a host that already exists, if they have at least one mark on that host when this complex form is threaded. Anyone entering it may realize it’s not a real host by performing a Matrix Perception test, with a threshold equal to the number of hits rolled when threading this complex form. In the event that someone attempts to hack the host, treat the pseudo-host’s rating as (2 x number of hits on the threading test). If the hack is successful, the hacker gets marks on the technomancer and sees through the illusion.This complex form may be dismissed by the technomancer as a Simple Action.
- Source
- Kill Code
IC Tray
- Target
- Host
- Duration
- I
- Fading
- L-5
This form scans the host the technomancer is currently residing in and displays a list of the IC it is currently equipped to deploy, up to the number of hits scored on an Opposed Software + Resonance [Level] vs. Host Rating + Sleaze Test.
- Source
- Data Trails
Infusion of [Matrix Attribute]
- Target
- Device
- Duration
- S
- Fading
- L-2
This complex form entry is shorthand for four different complex forms, one for each Matrix attribute. Resonance floods the target device, boosting the specified attribute. The Level of the complex form must equal or exceed the value of the attribute being affected. The attribute is increased by the number of hits scored, up to twice the target’s normal rating (any hits that would increase the at- tribute beyond this maximum are ignored). Each attribute can only be affected by a single Infusion at a time. If an attribute boosted by this complex form is swapped in a Reconfigure action, this complex form ends.
- Source
- Core
Mirrored Persona
- Target
- Self
- Duration
- I
- Fading
- L-2
You can create a proxy persona that looks and acts identical to you in the Matrix. To differentiate between the technomancer and the proxy, opponents must succeed on a Matrix Perception test with a threshold of the number of hits rolled when threading this form. If they fail to notice, opponents target the proxy with a Matrix Action. The player rolls a defense test as normal. If they succeed, the proxy disappears, and technomancer character takes no negative effect.
- Source
- Kill Code
Misread Marks
- Target
- IC
- Duration
- P
- Fading
- L-1
A nasty little thing that will manipulate how IC perceives the Matrix, and who exactly is friend or foe. Temporarily tricks a targeted IC into thinking your marks are its intended targets, similar to the way someone might mistakenly attack a magic-user’s illusion. This lasts for for a number of actions (including Simple or Complex, but not Free) equal to the hits scored on a Simple Software + Resonance [Level] Test. If you have multiple marks in the same host, the mark that is attacked is selected randomly.
- Source
- Data Trails
Pinch
- Target
- Self
- Duration
- S
- Fading
- L + 2
When you’re caught in the crossfire, sometimes the only thing to do is burn down everything around you. If a technomancer is sustaining this form when their Matrix condition monitor becomes full or when they are otherwise forcibly removed from the Matrix, all icons the technomancer has marks on and all icons that have marks on the technomancer take Matrix damage equal to the level of the complex form. This damage may be resisted. If a technomancer is removed by the fade damage from threading this form, the form fizzles and returns to the fabric of the Resonance before it can take effect.
- Source
- Kill Code
Primed Charge
- Target
- Self
- Duration
- I
- Fading
- L
When a technomancer harnesses the raw power of the Resonance, it can make any obstacle that gets in their way regret its choices. Make a Software + Resonance [Level] test. The next Matrix action you perform gains a dice pool bonus equal to the number of hits on this test.
- Source
- Kill Code
Pulse Storm
- Target
- Persona
- Duration
- I
- Fading
- L-3
You pull signals out of the Resonance and surround the target with them. Make a Software + Resonance [Level] v. Logic + Data Processing test. For each net hit you get, the target’s noise is increased by 1.
- Source
- Core
Puppeteer
- Target
- Device
- Duration
- I
- Fading
- L+1
You push Resonance commands into a target, forcing it to perform a Matrix action. Pick a target and a Matrix action for it to perform. Make a Software + Resonance [Level] v. Willpower + Firewall test with a threshold based on the type of action: 1 for a Free Action, 2 for Simple, and 3 for Complex. If you succeed, the target performs that Matrix action as its next available action.
- Source
- Core
Redundancy
- Target
- Device
- Duration
- S
- Fading
- L-3
This form works with Resonance threads to better allow for secondary and tertiary connections, making the device slightly tougher for a limited amount of time. Redundancy grants additional, temporary boxes to the Matrix Damage Track to one device, giving a number of boxes equal to the hits acquired on a Simple Software + Resonance [Level] Test.
- Source
- Data Trails
Resonance Bind
- Target
- Persona
- Duration
- S
- Fading
- L-2
Need to slow the opposition down? Snag them in a Resonance Bind that hinders all actions in the Matrix. Make a Software + Resonance [Level] v. Intuition + Data Processing opposed test. On a successful attack, each net hit reduces the target’s Initiative Score by 2. If you sustain the complex form, the target loses the same amount from their Initiative Score at the beginning of each combat turn. A target caught in Resonance Bind may attempt to break free of the binding by making a Cybercombat + Logic [Attack/Sleaze] v. the complex form’s Level x 2 opposed test. Success only means that they stop future Initiative Score loss; they do not regain any points of Initiative Score in the present Combat Turn.
- Source
- Kill Code
Resonance Cache
- Target
- IC
- Duration
- I
- Fading
- L-2
The technomancer pushes a single IC into a stream of Resonance that isolates it, effectively locking it away. Make a Software + Resonance [Level] v. Host Rating x 2 opposed test. On a successful test, the IC is locked in a Resonance fold for a number of combat turns equal to the complex form’s level.
- Source
- Kill Code
Resonance Channel
- Target
- Device
- Duration
- S
- Fading
- L-4
Instead of using Matrix channels, you communicate through a Resonance channel. Make a Simple Software + Resonance [Level] test. For each net hit, reduce the noise due to distance from the target device by 1.
- Source
- Core
Resonance Spike
- Target
- Device
- Duration
- I
- Fading
- L-3
You send a spike of raw destructive Resonance into the target, causing errors and mayhem. Make a Software + Resonance [Level] v. Willpower + Firewall test. Your target takes 1 box of Matrix damage per net hit, with no chance to resist.
- Source
- Core
Resonance Veil
- Target
- Device
- Duration
- S
- Fading
- L-4
This complex form lets you make the target believe something has happened in the Matrix. It’s a convincing illusion if you can succeed in a Software + Resonance [Level] v. Intuition + Data Processing test. Even if the target has reason to believe what it’s seeing is fake, it needs to make a Matrix Perception Test with a threshold equal to your net hits to see through the illusion.
- Source
- Core
Search History
- Target
- Device
- Duration
- I
- Fading
- L-2
Target a device and make a Software + Resonance [Level] v. Device Rating x 2 opposed test. On a successful test, the technomancer has a full record of the device’s Matrix history over a number of days past equal to the number of net hits.
- Source
- Kill Code
Static Bomb
- Target
- Self
- Duration
- I
- Fading
- L-1
Make a Software + Resonance [Level] v. Intuition + Data Processing test against all icons that have spotted you. If there’s more than one, compare your hits to each of theirs separately. Each icon you beat loses you, and you’re no longer spotted by those icons. Any icon that has a mark on you doesn’t lose you, of course.
- Source
- Core
Static Veil
- Target
- Persona
- Duration
- S
- Fading
- L-4
Resonance energy coils around you, hiding you from GOD. Make a Simple Software + Resonance [Level] test with a threshold of 1 if the target is on the public grid and 2 on any other grid. As long as you sustain this complex form and the target doesn’t hop to another grid, the veiled persona’s Overwatch Score doesn’t increase due to time (p. 231). It still increases as a result of the target’s illegal actions, though.
- Source
- Core
Stitches
- Target
- Sprite
- Duration
- P
- Fading
- L-5
You knit the Resonance patterns in a sprite back together. Make a Simple Software + Resonance [Level] test. For each hit, remove 1 box of Matrix damage from the target sprite.
- Source
- Core
Weaken Data Bomb
- Target
- File
- Duration
- I
- Fading
- L-2
Make a Software + Resonance [Level] v. Data Bomb Rating x 2 opposed test. On a successful test, the form lowers the rating of a data bomb by the number of net hits (to a minimum of 1).
- Source
- Kill Code
Weaken Encryption
- Target
- File
- Duration
- I
- Fading
- L-3
Make a Software v. Resonance [Level] v. Protection Rating x 2 opposed test. On a successful test, the form lowers the rating of the file’s protection (see Edit File, p. 249, SR5) by the number of net hits (to a minimum of 1).
- Source
- Kill Code
Tattletale
- Target
- Persona
- Duration
- P
- Fading
- L-5
The Resonance can be used to mimic the telltale signs of illegal activity in the Matrix — to your target’s sorrow. Make a Simple Software + Resonance [Level] test. For each hit, increase the target’s Overwatch Score by 1. This only works if your target has an Overwatch Score.
- Source
- Core
Transcendent Grid
- Target
- Self
- Duration
- I
- Fading
- L-6
You broaden your connection to the Matrix and connect to all grids at once. You take no penalty for acting across grids (because you’re on all of them), but neither do others targeting you. You also don’t take a penalty from the public grid. Make a Simple Software + Resonance [Level] Test. The effect persists for one minute for every hit you get. When you run out of hits, the complex form ends.
- Source
- Core
Stream Specific
Overdrive
- Stream
- Cyberadept
- Target
- Cyberware
- Duration
- S
- FV
- L+1
Like the power of the same name used by great form machine sprites, the Cyberadept can put a single piece of their cyberware into Overdrive. This power can only be used on cyberware that is currently installed in the Cyberadept. The Cyberadept rolls a Software + Resonance [Level] Test. Half the net hits (rounded up) are added to the effective rating of the cyberware. This can—and often will—push a piece of cyberware way past its intended limits. When this complex form is no longer sustained, the cyberware takes a number of boxes of Matrix damage equal to the level of the complex form. This damage cannot be resisted. On a glitch, the cyberware is bricked, filling its Matrix Condition Monitor. On a critical glitch, the damage is physical, rather than Matrix. The rules for repairing Matrix Damage appear on p. 228, SR5. The rules for repairing Physical Damage to gear appear on p. 143, Run & Gun.
LOTO
- Stream
- Machinist
- Target
- Device
- Duration
- I
- FV
- L-1
Using this ability, a Machinist can disrupt the signals going to and from a machine, separating it from its master(s). This power can be used on any device. When using it, the Machinist rolls a Software + Resonance [Level] v. Willpower + Firewall Opposed Test. The device is completely disabled for a number of Combat Turns equal to the net hits on the test. In the case of something that has a Pilot rating, the Pilot loses functionality as well.
Hyperthreading
- Stream
- Sourceror
- Target
- Complex form
- Duration
- Varies
- FV
- Varies
The Sourceror can merge multiple complex forms into a single form, making multiple results in a single action. Doing so has its limits; the target and level for the Hyperthreaded Form must be the same for all merged complex forms. Resolve effects with a single Software + Resonance [Level] Test, the results of which are used for all the merged complex forms. The Fading Value is determined by taking the highest Fading Value of all the merged complex forms, and then adding 1 point for each complex form added after the first; the -2 bonus for being a Sourceror is applied at the end.
Sprite Pet
- Stream
- Technoshaman
- Target
- Sprite
- Duration
- P
- FV
- L+0
This complex form allows a technomancer to convince a registered sprite to become his “pet” and stick around even when other sprites are around. It can only be used on a single sprite at a time. Because this complex form takes several hours to complete, it can be considered a sort of “digital ritual.” The Technoshaman spends a number of hours equal to the sprite’s level attuning himself to the sprite. At the end of this time, the Technoshaman pits his Software + Resonance [Level] against the Level x 2 of the sprite. If the Technoshaman gets more hits, he feeds the sprite a number of Karma equal to the sprite’s level. If this is done, the sprite becomes a sprite pet. This means that the sprite no longer has a limit on favors and tasks and can be active at the same time as any other sprite. It also no longer counts against the Technoshaman’s limit on registered sprites. This can only be done on one sprite at any given time. If the sprite pet is destroyed, it will return to its home Resonance Realm, and the Karma spent is lost.