Hoi chummer!

So you got this drek hot C-space emulator Icetoaster put on the net. If you've found this, you've probably already had some deckers try cracking some of your homemade LTGs. I guess they'll know better now than to just charge in, right?

But how about some REAL networking experience? After all, C-space is an infinite playground for deckers to manipulate. So here's your chance. Link your deck up from that vidphone in the back of your local bar, connect to the RTG and fly anywhere you smell paydata.

Go burn their frames, chummer!

Framefreezer

Author's note:

This archive consists of four subdirectories that you can simply extract into the LTG directory of the cyberspace program. It contains a fully linked grid of LTGs of part of the Seattle matrix. Have a player decker connect to one LTG (s)he uses as logon point and from there on you can fly across all LTGs and RTGs that are part of the Seattle grid. Connections to new parts will be done automatically by the cyberspace program. This grid does not contain satellites.

As I used the security codes provided by FASA's sourcebooks, you will find that a standard archetype decker will fly through most LTGs without any problems. Of course, he's supposed to and most such easy LTGs don't contain anything worth going after. As the unique buildings described in the sourcebook will probably be somewhat different in each campaign, I provided the linking nodes for them, but without the actual links or LTG files. You'll have to make them yourself. There is plenty of unused (or disconnected, as I called them) links to add your own LTGs, and it is fairly easy to add new RTGs as well.

All RTGs contain but numeric references to the LTGs they connect to. See here they value of accurate information on LTG addresses or your decker will be spending way too too much valuable time searching for the right address.

Two warnings:

1. Keep a backup of this archive and all grids you link up to it. As the decker leaves a system, it will be saved AS IT IS at that moment, including damaged ice, alert status and changed data. If you go back there, even after a long time, that status will be loaded again. Chances are though that the corp will have fixed the problem by then, so you should replace it with a standard or properly adjusted file. Personally I found it very useful to turn on the GM log file for just this purpose.
2. The cyberspace program is not too happy about not having links to the external matrix (MAT). I have tried various contructions to go around this problem but none are really elegant. Stick to one rule of thumb: put your MAT links at standard locations, so deckers will know what to expect and may avoid them, or at least get back in easily.

The contents of the archive:

std\

contains the LTG archetypes for each of the location archetypes described in Sprawl Sites. This book only gave general security codes, and I wrote the corresponding LTG archetypes myself. You might want to twist some of them to reflect your own campaign.

rtg\

contains the seattle RTG files. It is set up to contain links to all other UCAS RTGs, all major international RTGs and all Seattle district RTGs. Only Downtown Seattle and Tacoma are added so far. Note that Downtown Seattle had so many systems linked to it that it required three RTG nodes to cover them all.

downtown\

contains all LTGs of Downtown Seattle that are one of the Location Archetypes, as listed in the Seattle Sourcebook. It has nodes allocated for the unique buildings that are described as well, but those are not connected to LTG files.

tacoma\

contains similar LTGs for the Tacoma district.

DISCLAIMER:

FASA, Shadowrun, and Matrix are trademarks of the FASA Corporation. The Shadowrun Sourcebook and Sprawl Sites are copyright by the FASA Corporation. The Cyberspace Emulation programs are all copyright by Stefan Markgraf.

Enjoy the Seattle grid!

Bart Savenije