I'll probably join the discord shortly after this post, though I probably won't be active until some time tomorrow-ish, because training has been kicking my ass a bit. But first this post here, and then stuff there.<br/><br/>Going from when-ish I remember being the top that I can weigh in on and going down:<br/><br/>The hotel would hopefully have a low level (possibly not even 3) host just for that one hotel. It would mean that any ranged hacking, even technomantic, on contained/slaved devices would first have to gain entrance to the host through it's minimum double Host Rating defense pool first and anything not on a slaved device would also have that same pool to resist. Add in noise penalties and I'd need to go into Hot-Sim or get closer to do the initial hack whether by sprite or Nadia's own persona. And Hosts are somewhat protected from basal technomantic shenanigans.<br/><br/><br/>One of the less stupid decisions made about hacking, all kinds, is that bricking a device is never more dangerous than not having that device but is always showy as fuck. On the other hand, I have access to Machine Sprites and from close-ish distance they can cause glitches, the exact nature of which would be up to the GM but normally look like just bad luck. And I can certainly send a sprite to go and wreck stuff while doing other stuff or even hack in the hotel's host but that would instantly get rid of it if I wasn't in there too. Of course, the main advantage of doing things technomantically is that it's near invisible on the matrix  other than the results. So for helping out planning, I can essentially do file editing invisibly and probably without the usual caveats, and make machines do things 'without reason' (but only that they could do).<br/><br/>So Nadia's probably better on the hacking team, but if needed I can try and whistle up a sprite or two to semi-invisibly mess with some of those bikes or even boosting the team that's dealing with the go-gangers. Choose one piece of kit and I can hand out a small dice bonus while using it.<br/><br/>Now what I don't currently have is a good way of dealing with the potential chips and trackers at the moment that doesn't involve at least a little bit of normal work and one of the deeply stupid bits of the Matrix rules. But the good news is that disabling the reporting, at least, will be easy enough and they can eventually all be rooted out and dealt with.