What is the problem with White Noise and Repeater? Even if they were both NFB, the hacker is only using one skill with NFB trait (that is White Noise). Repeater is not used by the hacker, he does't even have it...
NFB on White Noise isn't a major issue for Reverend Links: Order 1: Custodier casts White Noise, Order 2: Moira HMG shoot through it vs a Trooper with MSV1, say helo to -9 MODs As @tox points out: the [Moira] is only using one skill with NFB trait (that is [ODD]). [White Noise] is not used by the [Moira], [she ] does't even have it... NFB on White Noise IS an issue for solo Custodiers: Custodier wants to use ODD and White Noise themselves... can't due NFB. Custodier wants to use Cybermask and White Noise... can't due NFB. So if the interaction between White Noise's NFB and a potential Repeater NFB is what's causing the worry, then remove NFB from White Noise. But mostly, CB should remove NFB from White Noise because all it does is add an anti-synergy to HD+s and specifically screw Custodiers for - as far as I can tell - no good reason. OTOH *looks meaningfully at Pi-well, Vostoks and Bulleteers* there's other issues with giving Repeaters NFB. Easier by far to either accept that the Repeater covered by Cybermask remains available for both player's to use OR to write a specific rule that deals with them (ie. using a Marker-state Repeater drops them from the Marker-state as per N3).
You have to consider that the problem is not only in one way. Because with that clause you only solve when you attack trough a repeater in camo, but the repeater works in two ways, so I couldnt use an enemy repeater in a camo state. we are going to update the rules, because we want to have that living rules
@inane.imp Yeah, that was kinda dumb. I only realised after posting that the only benefit would be to shoot with Custodier (which would only be a good option if you run her solo) otherwise you can already do it now.
Thank you, that makes sense now. I look forward to resolution of a couple of other not-fully-clear moments stated in other threads (ehm ehm BS attack without LoF declaration). But what's most important, while you're here, thank you and the team for the amazing job with N4. Me and my friends started with N3, and it did feel really overwhelming in a lot of cases, so we did not get much play time. With N4 launch, we started to play often, and we unanimously agree N4 is a huge improvement, and much more newbie-friendly. Also, most of my group are game developers (just not tabletop, huh), and from the professional PoV, almost everything in the game got better as well - game flow, complexity/depth balance, balance between troop types, etc. So here's to the long and successful life of N4, cheers!
I can understand that the various options are a significant problem. perhaps the cleanest solution that I can think of is the answer that n3 had? 1) repeaters being used reveal themselves in a marker state 2) troopers do not gain an aro from a hackable trooper through an enemy repeater if it is in a marker state (there is certainly a cleaner way to word this part). this allows the problem of a Moran camo repeater or a cyber mask + repeater from being impossible to deal with, and yet it does mean walking near that prior camo'ing Moran to be a risky venture with something important. and once it is revealed, go nuts on that killer hacker or what have you. The second bullet point is to just handle the problem of "did you technically have an aro against the Interventor through the camo'ing moran and not elect to use it, to bad, spotlight". because if the Intenventor idles with the Moran nearby, the friendly angus has no aro due to 2nd bullet point. as soon as he gets spotlighted, then he gets an aro as the moran is no longer camo'd and he is being comms attacked and can spotlight back or reset or cry (the last is assumed).