NEWS

Running Silent

  • 22 Replies
  • 1198 Views

Xenon

  • *
  • Prime Runner
  • *****
  • Posts: 6267
« Reply #15 on: <08-03-21/1157:06> »
Also clarifies how to handle silent running for me and my crew
Note that searching for random silent running icons in the vicinity is one way to get aware of their presence  (determine that they are present).

The intent here is that there might also be other ways to also become aware (or determine that they are present). If you (or any of your team members) for example physically see a specific device then you would also be considered aware of it  (you already determined that it is present) and can take a matrix perception test to spot the device icon of this specific device (in this case there is no need to randomly check all other 2000 silent running devices in the vicinity. since you are aware of this device you just attempt to spot the device icon of this specific device directly).



Example;

You see a vehicle parked further down the street (among other parked vehicles).

Matrix perception to spot the device icon of this specific vehicle.
If it is running silent then it get to oppose the test
If it is not running silent and within 100 meters then spotting of its icon is automatic.


Example 2;

The team run into a door locked with a maglock (in a facility that have many other locked doors).

Matrix perception to spot the device icon of this specific maglock.
If it is running silent then it get to oppose the test
If it is not running silent and within 100 meters then spotting of its icon is automatic.
« Last Edit: <08-03-21/1159:32> by Xenon »

RickDeckard

  • *
  • Chummer
  • **
  • Posts: 154
  • It can't rain all the time.
« Reply #16 on: <08-04-21/0651:51> »
Yeah, that's how I gathered it would work. If you suspect there's a silent running device that's enough to search specifically for that one.

In the example with the maglock you'd probably just jack directly into its jackpoint tho.

Xenon

  • *
  • Prime Runner
  • *****
  • Posts: 6267
« Reply #17 on: <08-04-21/1426:40> »
In the example with the maglock you'd probably just jack directly into its jackpoint tho.
If the decker is physically with the team, yes, and in that case he would be considered directly connected to the device. He would also be considered directly connected to the maglock if the maglock was slaved to the host his matrix persona is currently inside of (no matter distance).

But if he is hacking the maglock remotely over the grids (for example if he is hiding in the rigger van) then he would typically have to take a matrix perception test in order to first spot the icon.

(note that we are still only discussing SR5, spotting is treated differently in SR6).

RickDeckard

  • *
  • Chummer
  • **
  • Posts: 154
  • It can't rain all the time.
« Reply #18 on: <08-05-21/0545:55> »
In the example with the maglock you'd probably just jack directly into its jackpoint tho.
If the decker is physically with the team, yes, and in that case he would be considered directly connected to the device. He would also be considered directly connected to the maglock if the maglock was slaved to the host his matrix persona is currently inside of (no matter distance).

I was not aware of this! So if you're hacked into a host, all slaved devices are handled as if you're directly connected? Do you remember where this is referenced?

Xenon

  • *
  • Prime Runner
  • *****
  • Posts: 6267
« Reply #19 on: <08-05-21/1400:57> »
In the example with the maglock you'd probably just jack directly into its jackpoint tho.
If the decker is physically with the team, yes, and in that case he would be considered directly connected to the device. He would also be considered directly connected to the maglock if the maglock was slaved to the host his matrix persona is currently inside of (no matter distance).
I was not aware of this! So if you're hacked into a host, all slaved devices are handled as if you're directly connected? Do you remember where this is referenced?
SR5 p. 233 PANs and WANs
If you are in a host that has a WAN, you are considered directly connected to all devices in the WAN.

RickDeckard

  • *
  • Chummer
  • **
  • Posts: 154
  • It can't rain all the time.
« Reply #20 on: <08-07-21/1055:13> »
In the example with the maglock you'd probably just jack directly into its jackpoint tho.
If the decker is physically with the team, yes, and in that case he would be considered directly connected to the device. He would also be considered directly connected to the maglock if the maglock was slaved to the host his matrix persona is currently inside of (no matter distance).
I was not aware of this! So if you're hacked into a host, all slaved devices are handled as if you're directly connected? Do you remember where this is referenced?
SR5 p. 233 PANs and WANs
If you are in a host that has a WAN, you are considered directly connected to all devices in the WAN.

Our decker is gonna have it both easier and harder at the same time now =)

Xenon

  • *
  • Prime Runner
  • *****
  • Posts: 6267
« Reply #21 on: <08-07-21/1744:49> »
Also, Aaron (one of the authors of the Matrix chapter for this edition) clarified that devices (in this edition) are never actually inside a host. They are (always) out on the grid. You can always hack a wireless device directly from the matrix (where noise due to distance is a thing), without first 'entering' the Host it is slaved to. Just that if they are in a Wide Area Network (slaved to a Host) then you would be considered directly connected to the device (even though it is out on the grid) if you were to enter the host. Think of it as having a 'window' from the Host directly to the device out on the grid. No matter where in the world the device is located. The intent was that this is an exception to the rule that you cannot interact with devices outside of a host.

If your decker attack the device directly out on the grid, without entering the host, then it get to defend with host ratings and he need to worry about noise due to distance (but while doing this he probably doesn't have to worry that much about physical patrols, spiders or IC).

If your decker establish a physical direct connection, then your decker get to ignore host ratings (and noise) when attacking the device (but typically must watch out for patrols and drones etc).

If your decker hack and enter the host, then your decker also get to ignore host ratings (and noise) when attacking devices slaved to the host (but typically must watch out for spiders and IC).


A good plan here is to combine them by first establish a physical direct connection with a device slaved to the host in order to ignore host ratings while hacking the device. And since the device is slaved to the host the hacker also gain a mark on the host (without fighting host ratings). Once the hacker have a mark on the host the hacker can basically walk out to the rigger van (or join the team while hacking from AR) while using the mark on the host to enter the host. Getting directly connected with all other devices slaved to the Host (again, ignoring host ratings while attacking them).
« Last Edit: <08-07-21/1747:04> by Xenon »

RickDeckard

  • *
  • Chummer
  • **
  • Posts: 154
  • It can't rain all the time.
« Reply #22 on: <08-08-21/1334:19> »
Also, Aaron (one of the authors of the Matrix chapter for this edition) clarified that devices (in this edition) are never actually inside a host. They are (always) out on the grid. You can always hack a wireless device directly from the matrix (where noise due to distance is a thing), without first 'entering' the Host it is slaved to. Just that if they are in a Wide Area Network (slaved to a Host) then you would be considered directly connected to the device (even though it is out on the grid) if you were to enter the host. Think of it as having a 'window' from the Host directly to the device out on the grid. No matter where in the world the device is located. The intent was that this is an exception to the rule that you cannot interact with devices outside of a host.

If your decker attack the device directly out on the grid, without entering the host, then it get to defend with host ratings and he need to worry about noise due to distance (but while doing this he probably doesn't have to worry that much about physical patrols, spiders or IC).

If your decker establish a physical direct connection, then your decker get to ignore host ratings (and noise) when attacking the device (but typically must watch out for patrols and drones etc).

If your decker hack and enter the host, then your decker also get to ignore host ratings (and noise) when attacking devices slaved to the host (but typically must watch out for spiders and IC).


A good plan here is to combine them by first establish a physical direct connection with a device slaved to the host in order to ignore host ratings while hacking the device. And since the device is slaved to the host the hacker also gain a mark on the host (without fighting host ratings). Once the hacker have a mark on the host the hacker can basically walk out to the rigger van (or join the team while hacking from AR) while using the mark on the host to enter the host. Getting directly connected with all other devices slaved to the Host (again, ignoring host ratings while attacking them).

Good insights, chummer. Much karma.