[Trigger Lynx]

For the sake of slaving devices to your PAN for the Firewall protection, can you consider cyberware as a device? If so, is any chrome fair game, or only cyberware with a device rating? And if not, doesn't that make your 'ware far more of a liabilty than any gun or gizmo you carry with you? I just flipped through the Matrix section again and I didn't see an answer (maybe I overlooked it), so I figured I'd ask the forums.

[Stainless Steel Devil Rat]

Everything that's a manufactured object is a "device" as far as the matrix rules are concerned.  Your shoelaces, your can of energy drink, and etc can all be hacked. Most things won't matter if they're hacked or bricked, but you'll absolutely care if your cyberware gets hacked or bricked.

[Trigger Lynx]

Everything that's a manufactured object is a "device" as far as the matrix rules are concerned.  Your shoelaces, your can of energy drink, and etc can all be hacked. Most things won't matter if they're hacked or bricked, but you'll absolutely care if your cyberware gets hacked or bricked.

Soka, omae.  Thank you for the quick reply. And just for clarification:  what Devices in your PAN that are slaved (covered by your link/deck Firewall) can be changed with a Switch Mode action, correct?

[Stainless Steel Devil Rat]

Everything that's a manufactured object is a "device" as far as the matrix rules are concerned.  Your shoelaces, your can of energy drink, and etc can all be hacked. Most things won't matter if they're hacked or bricked, but you'll absolutely care if your cyberware gets hacked or bricked.

Soka, omae.  Thank you for the quick reply. And just for clarification:  what Devices in your PAN that are slaved (covered by your link/deck Firewall) can be changed with a Switch Mode action, correct?

Personally, I'd call it an alternate function of the Reconfigure Matrix Attribute action, but either way those are both a minor action.  So the technical difference is probably pedantic.

Also note that the matrix rules designer's own preference is to simply not have a limit on the number of devices.  Just allow everyone to put as many devices as they want in their PAN... it makes everything so much simpler.

[Trigger Lynx]

Personally, I'd call it an alternate function of the Reconfigure Matrix Attribute action, but either way those are both a minor action.  So the technical difference is probably pedantic.

Also note that the matrix rules designer's own preference is to simply not have a limit on the number of devices.  Just allow everyone to put as many devices as they want in their PAN... it makes everything so much simpler.

Indeed. While I always try to run my first session with RAW, I may very well just house rule that straight out of the gate.  With the Rating 6 commlink having just D3/F1, that's a lot of juggling slaved devices between action rounds to fit the situation.

[Banshee]

Personally, I'd call it an alternate function of the Reconfigure Matrix Attribute action, but either way those are both a minor action.  So the technical difference is probably pedantic.

Also note that the matrix rules designer's own preference is to simply not have a limit on the number of devices.  Just allow everyone to put as many devices as they want in their PAN... it makes everything so much simpler.

Indeed. While I always try to run my first session with RAW, I may very well just house rule that straight out of the gate.  With the Rating 6 commlink having just D3/F1, that's a lot of juggling slaved devices between action rounds to fit the situation.

As SSDR stated I fully support that. My original version had much higher device limits for commlinks especially. You are not going to break anything I wrote by saying each PC can slave everything they own (as long as they aren't getting ridiculous with it) to their commlink for minimal protection and then daisy chain slave to the team hacker for full support. This is the way I run things at home.