![]() |
![]() |
![]()
Post
#1
|
|
Target ![]() Group: Members Posts: 40 Joined: 26-February 02 Member No.: 629 ![]() |
Sorry if this topic's been covered, but I didn't see anything similar in the thread index when I scanned through. Lock if necessary.
Our group's gotten back together after many years away from the game, and we upgraded to 4th edition along with the game. We're just all pretty confused about the 2070 Matrix--implementing the rules, and implementing the omnipresence of AR. So maybe you folks can help? Here's the two main concerns we have: 1) Where's the limit, as far as using the Matrix/AR? How much can you really do? Anything you can think of? Can every mechanical device with a wireless connection to the Matrix be hacked? Every person's commlink, every place of business's Matrix node? Every vehicle and wirelessly accessible kitchen appliance? Where do you draw the line in your sessions, or do you? On the same note, how much Matrix interconnectivity do you allow your players to have, in the heat of a run? The 4th ed. sourcebook makes it seem like everyone with even a simple commlink and some AR glasses can have live textual communication, live-updated tacmaps, and the kitchen sink. Where you draw the line here, if at all? 2) As far as implementing the rules for hacking, how many dice rolls should it take for your hacker character to accomplish something meaningful? One dice roll to access a desired node, and one to search for juicy data, and that's it? I'm sure our group is missing some important steps, but we've been away from the game for a long time, the Matrix is totally different in fourth edition, and we were never incredibly familiar with the Matrix in 2nd or 3rd ed. either. In your sessions, how do you resolve a typical hacking excursion? For example, if the hacker character is armed with a license plate number, how difficult do you make it for him to find out who owns the vehicle, and from that, everything interesting about that person? My group is anxious to get comfortable with the 4th ed. Matrix, because it's just cool, but we don't feel like we really have a grasp on how to incorporate it into our sessions. Hopefully you guys can share your experiences. |
|
|
![]() |
![]()
Post
#2
|
|||
Shooting Target ![]() ![]() ![]() ![]() Group: Members Posts: 1,706 Joined: 30-June 06 From: Fort Wayne, IN Member No.: 8,814 ![]() |
1) Honestly, that is all up to you, as the GM. I've had buildings all run off one node and other buildings run off a node for each floor. I've done runs where there was a dedicated node for security access (doors, elevators, temperature controls) and a separate node for data storage. I like to keep changing things for my players so they don't always do the same things in every matix run. Sometimes I might make a node only accessible from a certain location or force the hacker to directly access it via wires...so really, those choices are all up to you and the specific system. I'd recommend keeping it changing just so you are not boring the players or yourself with every matrix run. 2) Again, I think this is all individual, to both the GM and the system. Realize, that with any type of access, a hacker can do anything, its just a matter of whether it is a legitimate action that won't cause the system to think twice or an illegimate action that may cause the system to take actions. Most of the time, if I put a system into a run, I know ahead of time the types of information that I will allow/disallow for certain access types. The rest of the time, I just judge based on my own reasoning. You never have to worry about admin, as they have access to the entire system (granted, that doesn't mean every node can do EVERYTHING, so there could be limitations on a node and no matter what access, the hacker just can't do something). So really, you are just wanting to decide what the difference is between normal and security users. Sometimes one or both of them will not even be available...again, it comes down to how you want to handle it and will differ in each system/node, so there really isn't a wrong answer! 3) Personally, I start everything as a rating 3...programs, IC, everything. If I have a special node for a specific run and pre-plan everything, then I will vary things, but for most on the fly hack jobs my group will throw at me, I just stick to 3s across the board. If I feel the node is really insignificant, with little to no paydata, I'll drop it to 1. And if its something that I think is important, then I will up it to a 4, 5 or 6, but the vast majority, unless I have something specific planned, I stick it at 3. |
||
|
|||
![]() ![]() |
![]() |
Lo-Fi Version | Time is now: 13th May 2025 - 09:02 PM |
Topps, Inc has sole ownership of the names, logo, artwork, marks, photographs, sounds, audio, video and/or any proprietary material used in connection with the game Shadowrun. Topps, Inc has granted permission to the Dumpshock Forums to use such names, logos, artwork, marks and/or any proprietary materials for promotional and informational purposes on its website but does not endorse, and is not affiliated with the Dumpshock Forums in any official capacity whatsoever.