Episode 045: Data Trails

This is Critical Glitch, a Shadowrun Podcast Episode 045

Your host, The Most Dangerous Man in Gaming – Tim Patrick

Co-Host: Bob “Dr. Meatgrinder” Loper

In this episode we take a deeper look into Data Trails the “Core Matrix Hanbook”

Both Bob and myself found the book to be light on rules, and some of the rules that where included should have been moved to a dedicated e-pub to make room for more core concepts.  For a Matrix Core Handbook there was little to nothing for Technomancers absolutely nothing on their sprites.

We both found the book to be better then Run & Gun and Street Grimoire but not as polished as Run Faster. The lack of an index and intuitive chapter names still plagues the line for these reasons we both placed the book at around a C+ grade. Definitely worth getting in PDF, and you won’t feel like you wasted your money if you buy the hardback.

God Speaks – Intro fiction by CZ Wright of the Arcology podcast

The World in your Pocket – some setting info and examples of Grids

True Hackers, Lusers & Dirtballs – Hacker Groups & Technomancer Tribes

On the Bleeding edge – Positive & Negative Qualities

Born to Hack – Lifepaths

Killer Apps & Razor forms – Programs, Complex Forms, Echoes

The Guts of the Matrix – Upgrades for Commlinks & Cyberdecks

The All-Seeing Eye of God – Corp hosts, IC, sample Spiders, and Demi God

Corporate Sponsorship – Fiction by Jason Andrew

The Perfect Host – Host info & examples, Host cyber combat example p. 87 (Flawed), more Spiders

Deeper and Deeper – Foundation (You got your WoD in our SR)

Body Hunt – fiction by Scott Scheltz

Principles of Insanity – AI, Resonance Realms, Dissonants

Mastering the Matrix – GM overview of the Matrix, Matrix examples, Matrix Actions

Never hesitate to contact us with your questions or comments:

E-mail us at: criticalglitchpodcast@gmail.com

Follow us on Twitter: @CriticalGlitch1
Like us on Facebook

Help support us by making a pledge to our Patreon


5 thoughts on “Episode 045: Data Trails

  1. Hoi, Chummers!

    So, I dug back into my PDF copy of the first printing of the SR5 core rulebook and could not find anything on page 233 (under PANs and WANs) that indicated a mark on a master gives you a mark on a slave. The explicitly state that the reverse is true — even if you hack the slave with a direct connection.

    I also looked in the subsection about marks and the section about Hosts (to see if they had a special rule relating to master/slave relationships). The only thing about hosts that seem different is that when you’re connected to a host you have what is considered a direct connection to all devices slaved to that host (i.e. all devices in its wide-area network) in the second-to-last paragraph under PAns and WANs (p. 233, SR5). This implies that you still need to get marks on the devices even after you’ve marked the host.

    Did you all go back and find the reference that says marked masters also count as marks on slaves? This isn’t just me pulling a rules-lawyer on you, I’m honestly curious since the only reason my players tend to hack hosts is to avoid grid convergence since host convergence is a little less problematic if you can GTFO fast enough.

    • The more I dig through the mess that is the Matrix rules, I have to agree with your findings. There is spoof after all that specifically says I do not need a mark on the device just on the owner and in the case of a slaved door to a host I think t’s safe to say the host owns the door.

      This just makes hacking a lot harder I smell a lot more conversions now.

      Another place they errored in the example as they said they had to get a mark on the last door before they could issue the spoof command to open the door.

      • I’ve actually not run it that the host is the owner. For Spoofing, my characters tend to get a mark on security personnel (who would have the access rights to open doors, manipulate cameras and camera data, etc.) and as long as they keep their mark on that NPC’s system, they can Spoof around to their heart’s content.

        I find it interesting that you all thing the Matrix rules are a mess. I’ve found them to be very intuitive, personally. The hardest part is remembering dice pools for actions, but I just made a cheat sheet for that. Different strokes, ‘eh?

      • Whoops! The reason to have marks on the host, in the case of a Spoof, is to gain the virutalized direct connection to the devices so that you can target it using it’s own device rating and not the host’s ratings backing it up.

  2. Hoi, as someone who worked on the book I wanted to say thanks for your feedback. Some of the items you mentioned are slated for clarification/revision (like MMRI, for example). Melting a few snowflakes, as it were. I’ll take the blame for plugging the new Matrix actions into a somewhat strange chapter. I wrote them and figured there would be a bunch of other new Matrix actions, but that didn’t happen, so I plugged them into one of the less thematically-constrained chapters. Garbage In/Garbage Out is there as stealth TM love. I expect the TM pdf will be more love.

Leave a Reply