This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| augments:network_siphon [2020-06-19 10:21] – turtlingherd | augments:network_siphon [2020-06-19 10:26] (current) – turtlingherd | ||
|---|---|---|---|
| Line 7: | Line 7: | ||
| ====== Strategy ====== | ====== Strategy ====== | ||
| - | If we assume one [[:alarm level]] passes every 4 turns (because it makes the math easy), its power output per turn is: | + | If we assume one [[:alarm level]] passes every 4 turns (because it makes the math easy, and it's sort of realistic, assuming an average of one mistake per alarm level), its power output per turn is: |
| ^ Alarm level ^ Total [[:PWR]] gained ^ Total turns ^ Average efficiency | ^ Alarm level ^ Total [[:PWR]] gained ^ Total turns ^ Average efficiency | ||
| Line 20: | Line 20: | ||
| *not a real alarm level, but Network Siphon still works every 5 ticks after alarm level 6 | *not a real alarm level, but Network Siphon still works every 5 ticks after alarm level 6 | ||
| - | As such, Network Siphon can be strong when you're able to get a lot of utility out of power spent when the [[:alarm level|alarm tracker]] is already very advanced, such as challenge campaigns where the alarm tracker moves at faster-than usual speed, or in an agency making heavy use of an [[: | + | As such, Network Siphon can be strong when you're able to get a lot of utility out of power spent when the [[:alarm level|alarm tracker]] is already very advanced, such as challenge campaigns where the alarm tracker moves at faster-than usual speed, or in an agency making heavy use of an [[: |