Compare a stealthy matrix action with a stealthy physical action:
Very helpful analogy.
If someone successfully shoot you then you will automatically be aware that you were attacked and if the attacker is not trying to hide then you will also automatically spot him (to spot an attacker that is trying to hide require an opposed perception test). If someone fail to hit you then you will not even be aware that you were attacked in the first place... OK, maybe not best of examples but you get the idea :-)
See that's the baffling part to me, I feel like I surely
would notice. Pew goes the bullet past my head, thunk goes the knife into the wall near me. Would my Firewall not also say "hey buddy, I just stopped an attack"? Today, I believe most malicious stuff gets logged. Seems like your system should have that basic ability.
shrugIf someone successfully land a data spike then you will be automatically aware that you were attacked and if the attacker is not trying to hide then you will automatically spot it (to spot an attacker that is trying to hide require an opposed matrix perception test). If someone fail to land a data spike then you will not even be aware that you were attacked in the first place.
Seems like the corps are overlooking some old school functionality there. The best logical I can conjure is that systems get swiped at so often, the corps don't care to follow up on failed attempts. Script kiddies and bots might be the bulk of such efforts, so they just ignore it? Seems like a decker would not want to do that though.
Note that the above relates to SR5. In this edition it depend on the action you are taking if the sleaze action will be noticed or not. Probe, for example, will not be noticed on a failed attempt (unless perhaps the hacker glitch) while Backdoor Entry will always not only be detected on a failed attempt, the backdoor will also be deleted and hacker need to start over with a new Probe attempt.
And that makes sense enough, for sure.
And also that in this edition
Yep, all that I gleaned. Nicer way to go, really.
Not sure about the "next to the icon" part since distance in the matrix is a bit funky, but yes, if you are obviously attacked by a PAN then you can attack back. Unless perhaps if the PAN is currently running silent, in which case you first need to take an opposed matrix perception test to spot the PAN.
I'm thinking of it as a GM here. If the hacker is on overwatch, what do they "see" in VR when they would detect a hack? Would it reasonably look like an icon materializing out of nowhere? If so, that icon needs a position relative to the target icon. So, I assume "next to me from my perspective" would be the relative position, since they are attempting to interact with the network I am defending. If they are not detectable to me at first, and use some sort of attack action, I see the attack animation, but not their icon. When I roll well enough spot them, the icon sort of shimmers into visibility in VR or something I suppose (?).
If your target is trying to hide then you resolve it with an opposed matrix perception test, otherwise you don't. If you also wish to know the physical location you first need to gain admin access and then take an Electronics test to get the real life location....
That is what I was gathering. Makes sense enough.
Reason target don't notice is because the Probe action explicitly state that: Probing a device does not raise an alarm automatically. Even if your attempt initially fails, it will not trigger an alarm unless major mistakes are made.
Target will also not notice a successful Backdoor Entry attempt.
"raise an alarm" brings up another point. That's not a ideal choice of wording to describe it, since "alarms" are not a thing by the rules as such. This line introduces a new term that doesn't connect to anything specific in the rest of the text. It should probably simply read "does not alert the target to the attempt".
However(!) on a failed Backdoor Entry attempt the hacker will be detected. But this have also nothing to do with running silent or not. Reason why target notice is because the Backdoor Entry action explicitly state that: If this test fails, the backdoor you have made was detected and removed, and you cannot attempt Backdoor Entry again with the same host until a new backdoor is made through the Probe Action.
I'm talking about becoming aware of the hacker's icon due to the hack attempt itself, vs becoming aware of just the hack action.
You spend a major action on full matrix defense. If you are attacked before it is your turn to act again then you add firewall to your defense. Repeat until you need to use your actions on your turn on something other than full matrix defense. Not really more complicated than that.
Seems like it is more complicated though. So each round you are using a Major action, fine. Not clearly written, but there's no other precedent in the book that suggests actions carry over longer than one turn unless they are Extended tests. That's fine.
However, it also says you are prevented from attacking. I feel like most games have any sort of Full Defense preclude making attacks, so it would make sense. However, Full Defense has no such limitation. Is that an oversight or intentionally different?
Also, it seems like it should be an Anytime action, like FD is. I don't see any other Matrix actions that seem like candidates for that, so I think that would be the only one. The rest would be Initiative actions, I assume. If there's supposed to be parity, there isn't currently, and Matrix actions aren't tagged either way.
I hope at the least this helps for further FAQ or errata. Looks like I have a choice to make as the GM to either treat FD and MFD differently (closer to RAW) or go more traditional and treat them equally (picking one or the other to use for the baseline - Initiative Action with no attack or Anytime Action and allow attacks). At least until some errata is ever dropped.
Would one "break the game" more than another to choose? Seems like allowing the parity with FD is the more favorable option, but I can't conjure any downstream effects that would be an issue.