Sybrespace Host - Revision history

Purkinje at 00:56, 13 March 2020

2020-03-13T00:56:55Z

← Older revision		Revision as of 00:56, 13 March 2020
Line 26:		Line 26:
	When your SIN is cleared to enter the club, you are invited to claim a mark on the club host and enter. To the average club-goer, it serves as a way of protecting their identities from nagging spouses or people on the streets while giving them access to hot deals, decor, and the full suite of AR sim experiences the club has to offer. In VR, it looks like a digital-chic representation of itself, full of saturated colors and heavy synth beats. Clubbers are ''required'' to be in the host while they are at the club. Think of it like how you're required to transmit SIN info in Downtown. The kind of person who visits Sybrespace doesn't usually have a problem with this, embracing the matrix easily. Because their persona icons have entered the host, they are not visible to people on the outside; similarly, the host is able to run all the ARO pleasures they want with its excellent data processing capabilities. A win-win, right? Well, you trade one form of anonymity for another, because the host’s patrol IC is constantly swimming around to keep an eye on you. It’ll check to see if you’re doing any hacking or if you’ve got any contraband slaved to your commlink, such as a smartgun that wasn’t caught on the handheld MAD-scanner when you entered.		When your SIN is cleared to enter the club, you are invited to claim a mark on the club host and enter. To the average club-goer, it serves as a way of protecting their identities from nagging spouses or people on the streets while giving them access to hot deals, decor, and the full suite of AR sim experiences the club has to offer. In VR, it looks like a digital-chic representation of itself, full of saturated colors and heavy synth beats. Clubbers are ''required'' to be in the host while they are at the club. Think of it like how you're required to transmit SIN info in Downtown. The kind of person who visits Sybrespace doesn't usually have a problem with this, embracing the matrix easily. Because their persona icons have entered the host, they are not visible to people on the outside; similarly, the host is able to run all the ARO pleasures they want with its excellent data processing capabilities. A win-win, right? Well, you trade one form of anonymity for another, because the host’s patrol IC is constantly swimming around to keep an eye on you. It’ll check to see if you’re doing any hacking or if you’ve got any contraband slaved to your commlink, such as a smartgun that wasn’t caught on the handheld MAD-scanner when you entered.

	==== IC Behavior ====		====IC Behavior====
	Patrol is always deployed, with the other three in reserve. IC behave normally.		Patrol is always deployed, with the other three in reserve. IC behave normally.

	==== Devices ====		====Devices====
	Any device a clubber would have physical access to is slaved to this host, such as simsense or condom vending machines. After all, if you're inside, you already have a mark on the host, right? Right?		Any device a clubber would have physical access to is slaved to this host, such as simsense or condom vending machines. After all, if you're inside, you already have a mark on the host, right? Right?

	==== Spiders ====		====Spiders====
	There are no spiders active in this host under normal circumstances, though security staff who interact with patrons will have their persona icons here.		There are no spiders active in this host under normal circumstances, though security staff who interact with patrons will have their persona icons here.

Line 56:		Line 56:
	Of course, the only things you’ll find in the public-facing host are what the owners want you to see - AROs designed to take your money and draw your attention away from security features, all under the guise of having a good time. You won’t get very far unless all you needed was to hack a club-goer’s commlink. No, the real good stuff is all slaved to the security host, which is running silent inside the club host. Any important business files are going to be stored here, such as financial information or employee data. Only recent transactions can be found, with previous records archived. The host's sculpt is plain, looking like an overlay of the club sculpt and any parts of the club that would only be accessible to staff.		Of course, the only things you’ll find in the public-facing host are what the owners want you to see - AROs designed to take your money and draw your attention away from security features, all under the guise of having a good time. You won’t get very far unless all you needed was to hack a club-goer’s commlink. No, the real good stuff is all slaved to the security host, which is running silent inside the club host. Any important business files are going to be stored here, such as financial information or employee data. Only recent transactions can be found, with previous records archived. The host's sculpt is plain, looking like an overlay of the club sculpt and any parts of the club that would only be accessible to staff.

	==== IC Behavior ====		====IC Behavior====
	Patrol is always deployed, with the other three in reserve. IC behave normally.		Patrol is always deployed, with the other three in reserve. IC behave normally.

	==== Devices ====		====Devices====
	This host contains devices that clubbers would ''not'' have physical access to, such as the sound system, lights, and credstick readers behind bar counters.		This host contains devices that clubbers would ''not'' have physical access to, such as the sound system, lights, and credstick readers behind bar counters.

	==== Spiders ====		====Spiders====
	The club's spider resides here. They aren't terribly well equipped or skilled, or else they'd be working for the corps or against them. It is worth noting that users marked as owners of the host can simultaneously see the security node and club node, so the spider will respond to any situations outside this host. They do have to leave it first, though.		The club's spider resides here. They aren't terribly well equipped or skilled, or else they'd be working for the corps or against them. It is worth noting that users marked as owners of the host can simultaneously see the security node and club node, so the spider will respond to any situations outside this host. They do have to leave it first, though.

Line 71:		Line 71:

	==Foundation==		==Foundation==
	~~Use this section to describe a host’s~~ foundation~~, if it has one. The only static, unchanging feature~~ of a host ~~foundation~~ is ~~its logic map: a set of seven specific nodes and the data trails connecting them with the requirement each node be connected~~ to ~~the rest~~. ~~If the host’s foundation paradigm has been locked down for some reason (such as a persistent portal anchor)~~, ~~you may describe it as well~~. ~~This is~~ a ~~rare occurrence~~, ~~as keeping~~ the ~~paradigm randomized helps the host’s owners recognize when~~ the ~~portal node has been anchored by an unauthorized user~~.		The foundation of the Sybrespace host is relatively easy to navigate. It is not anchored under normal circumstances, so there's no telling what to expect inside. The archive node will have business records older than a week inside, and troublemakers might enjoy playing with the scaffolding node to vandalize the place.

	<br />		[[File:Stuffershack15496foundation.png]]<br />
	[[Category:Hosts]]		[[Category:Hosts]]

Purkinje at 00:54, 13 March 2020

2020-03-13T00:54:22Z

Show changes

Purkinje: Created page with "==Description== Use this section to give a brief description of the network’s intended purpose and general situations you might see it used in play. This should give the rea..."

2020-03-13T00:17:27Z

Created page with "==Description== Use this section to give a brief description of the network’s intended purpose and general situations you might see it used in play. This should give the rea..."

New page

==Description==
Use this section to give a brief description of the network’s intended purpose and general situations you might see it used in play. This should give the reader a broad idea of whether they want to use this host in their level design.

==Scaffolding==
[[File:Sample_host_map.png|alt=|The website [https://www.draw.io/ draw.io] is a free resource you can use to create host flowcharts. The colors here don't really mesh with the wiki, but you get the idea. It's really easy to use.|frame]]
This section outlines the structure of the host’s scaffolding. It should contain a subsection for each node in the host if there’s more than one. Each subsection should include the node’s properties (Type, Rating, Attack, Sleaze, Data Processing, and Firewall), IC Tray (the load order of all IC the node is capable of deploying), sculpt (a description of what a character in the node experiences), files (can be broad, be sure to include any file storage and retrieval protocols), devices (include operating procedures), and notable users (including spiders and their equipment and behavior).<br>

===Example Entry Node===
{| class="wikitable"
|+insertorganizationhere.mtx
!Type
!Rating
!Attack
!Sleaze
!Data Processing
!Firewall
!IC Tray
|-
|Destination
|4
|4
|2
|7
|9
|Patrol, Blaster, Probe, Track
|}
This node serves as the public face of Insert Organization Here. It is the first node you enter when you access the host. It looks like a normal office building with a friendly receptionist to give you a tour, and its IC look like staff. Its files contain public contact information and press releases. No devices are slaved to this node. A spider is in charge of the security, but they are normally in the nested security node and so will take a turn or two to respond to an alert.

===Example Security Node===
{| class="wikitable"
|+intranet.insertorganizationhere.mtx
!Type
!Rating
!Attack
!Sleaze
!Data Processing
!Firewall
!IC Tray
|-
|Data
|4
|6
|4
|5
|7
|Patrol, Killer, Marker, Binder
|}
This node contains Insert Organization Here's client and employee records. It looks like a series of rooms filled with book cases and filing cabinets. Client and employee files are labeled with anonymous ID numbers known only to the clients and employees themselves, though an offline ID lookup database exists. The files of former employees or clients who have not used Insert Organization Here's services in X months are stored in the host's archive; otherwise, they are accessible to users in the node. Each file is protected by a databomb with a password known only to the client and employees handling the client's case. There are no devices slaved to this node. This node is closed to the general public, primarily used by employees as a data repository. The host's spider normally spends time here, so expect faster responses to alerts.

==Physical Integration==
Some hosts correspond with physical locations. They may act as a WAN to manage devices in a building, protect the personas of a business’ clientele from prying eyes, or serve as a data repository for staff reference. A few rare, outdated hosts have physical hardware they run on. Use this section to describe how the host is integrated with meatspace, if at all. Remember that because direct connections to slaved devices are a backdoor into a host’s firewall, slaved devices will be physically protected. It is better to have an easily accessible device not be slaved to a host at all than to have it compromise your network security. Whether a given host’s owners subscribe to that philosophy is up to you.

Insert Organization Here has a modest building protected by a cheap private security force. It's in an old building with wired, offline electronics, so security devices are placed in a cavalier fashion. The spider's office on the third floor contains an offline terminal they can use to match employee/client names with ID numbers when needed.

==Foundation==
Use this section to describe a host’s foundation, if it has one. The only static, unchanging feature of a host foundation is its logic map: a set of seven specific nodes and the data trails connecting them with the requirement each node be connected to the rest. If the host’s foundation paradigm has been locked down for some reason (such as a persistent portal anchor), you may describe it as well. This is a rare occurrence, as keeping the paradigm randomized helps the host’s owners recognize when the portal node has been anchored by an unauthorized user.

[[File:Sample_foundation_map.png]]

<br />
[[Category:Hosts]]