1) Find The Drone. There are multiple ways to do it.
The easiest is to use Sc
I do have a
matrix crib sheet (from
here), but its
far from complete.The first step is to find the drone's network:
The easiest way to do this is with a wifi
scan. (If you haven't taken a look at the matrix section list of programs and also the list of actions do so now).
Using an
Intercept Traffic command on its controlling rigger, and waiting for one to communicate to the other would let you eavesdrop on which command is being sent where, and snag its access id that way. (such as if the rigger sends a command, or the drone makes a 'wtf do i do test' and contacts its owner)
A
Trace User might be faster than waiting, and is also handy for finding out generally where a signal is (per the list of information analyze can give you, the precise location of a traced user may be available under the 'other relevant information' option. I prefer using telematics infrastructure for my triangulation needs)
You could also use the access log to snag an AccessID to a connected drone, but that's more advanced stuffin unwired.
Next you have to get in
mutual signal range, though you CAN use relays to accomplish this, if you're more of a remote hacker.
You gotta
break the encryption before you do anything - including trying to intercept traffic (its been my experience that some GM's just forget that this program exists and that its common use, so cheap and everyone should have it.) If you
have the encryption key already, its a simple action to decrypt something, I believe.
Then you can try to log into the node. You have some options in this. You can
Probe or
Hack on the Fly. If you have an account already, such as from pre-hacking, or managing to steal someone elses login info/id, then you could use it too. You're probably hacking, thoush and should
decide what type of account you want to hack for
Then there is the
Loading step. Its not actually in an official list of things, but there is a lot of stuff that happens at once when you cross the firewall to get inside a node, so its a good habit to start doing the Loading/Rendering step all at once.
Defending node may make a firewall test, depending on the method of entry. (Probe rolls once when you Log In, HotF rolls every time you roll)
Your Reality Filter rolls now, if you have one running.
If your analyzer program is in automatic(and it should be!) it will make automatic tests against things.
If there are any defending or Patrolling IC, they will probably make analyze tests to notice the Log On.
If the defenders also have automatic-analyzer settings, it may roll to see you when you try to make changes on the node too.
And once you're inside, you can make Analyze tests to spot things, Data Searches to find pay data, Edit Tests to make accounts, run your programs on things - whether its crashing, attacking, medic, tracing a user, or whatever. (i'm fond of finding controls and important things that would hinder the defenders, and Encrypting them).
There is also the mechanics behind the story
Game, Set, Match. that gives a MUCH more in practical look to the matrix and how it works in a hack-off. The story starts on Anniversary Edition page 212, and I recommend reading them side by side.
However, I was hesitant to link it first because there
are a few dev errors in the example- either it was written for 4th ed(not anniversary), or before Unwired, or possibly a brainfart.(the math for slammo getting nuked was off). Still, it is FANTASTIC for getting people in the mindset of thinking about what you can do with the matrix, and the dice pools you need to have available in response to actions.
Speaking of Unwired, you should read the Security Examples starting on page 79 or so, whether or not you're using the book in your game.
Happy hacking.