Website/rules.html at main · hogstation/Website · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
<!DOCTYPE html>

<html lang="en">
	<head>
		<meta http-equiv="content-type" content="text/html; charset=UTF-8">
		<title>HogStation | Rules</title>
		<link rel="stylesheet" href="rules.css">
	</head>
	<body>
		<center><h1>Rules</h1></center>
		<button type="button" class="non-expandable"><h2>General</h2></button>
		<button type="button" class="expandable">01. Don't be a jerk.</button>
			<div class="content">
				<button type="button" class="non-expandable">This is an intentionally wide-reaching rule. We enforce this rule slightly more strictly than our predecessor, Yogstation, enforced <a href="https://forums.yogstation.net/help/rules/#rule-0_0">their 0.0 rule.</a></button>
				<button type="button" class="non-expandable">A. Don't intentionally or recklessly lessen others' happiness or fun.</button>
				<button type="button" class="non-expandable">B. Don't use slurs.</button>
				<button type="button" class="non-expandable">C. Don't attack others based on race, color, ethnicity, religion, gender, sexual orientation, birthplace, or any immutable characteristic.</button>
			</div>
		<button type="button" class="expandable">02. Don't engage in ERP.</button>
			<div class="content">
				<p>
					<b>ERP</b> = <b>E</b>rotic <b>R</b>ole-<b>P</b>lay<br><br>
					Keep it in your pants, simple as.
				</p>
			</div>
		<button type="button" class="expandable">03. Don't mix IC with OOC.</button>
			<div class="content">
				<button type="button" class="expandable">A. Don't use information you gained playing the current round (<b>I</b>n <b>C</b>haracter or <b>"IC"</b>) through any <b>O</b>ut <b>O</b>f <b>C</b>haracter communications channels.</button>
					<div class="content">
						<p>
							<b>OOC</b> communication channels include but are not limited to the BYOND OOC command, Discord, Signal, Lemmy, forums, smoke signals, etc. You may discuss IC events in LOOC, but use it sparingly because the message recipient(s) may not be as good as you at preventing that OOC from affecting their IC behavior. If you disclose something in LOOC that someone else uses IC, you may both be held accountable for metacommunication.
						</p>
					</div>
				<button type="button" class="expandable">B. Conversely, your character should not know everything you do OOC, e.g. metagaming, metacommunication, information obtained while a ghost, etc.</button>
					<div class="content">
						<button type="button" class="non-expandable">
							Metagaming: The use of OOC knowledge to benefit your character by supplementing their limited knowledge.
						</button>
						<button type="button" class="non-expandable">
							Metacommunication: The use of non-IC communication to coordinate or disseminate IC matters.
						</button>
					</div>
				<button type="button" class="non-expandable">C. Information you learn while a ghost is to be used in deadchat ("say" while dead) only.</button>
				<button type="button" class="expandable">D. A cloned person has no memory of the current shift (<b>C</b>lone <b>M</b>emory-loss <b>D</b>isorder). A revived person has no memory of how they died or who killed them (<b>D</b>eath <b>M</b>emory-loss <b>D</b>isorder).</button>
					<div class="content">
						<p>Following this rule after cloning/revival ensures your killer has no incentive to destroy your body, ending your round permanently.</p>
					</div>
				<button type="button" class="non-expandable">E. If you choose a ghost role, you lose all memories of the round prior to the moment you spawned as said ghost role.</button>
			</div>
		<button type="button" class="expandable">04. Don't multikey.</button>
			<div class="content">
				<p>
					Multikeying: An individual's use of more than one account (i.e. CKey) on a server (i.e. "alt accounts").
				</p>
			</div>
		<button type="button" class="expandable">05. Don't spam.</button>
			<div class="content">
				<p>
					Spam: Unauthorized repeat or promotional messages.
				</p>
			</div>
		<button type="button" class="non-expandable">06. Don't abuse bugs; let us know about them so we can fix them: <a href=https://github.com/hogstation/Hogstation/issues>https://github.com/hogstation/Hogstation/issues</a>.</button>
		<button type="button" class="expandable">07. Don't grief, greytide, powergame, or validhunt.</button>
			<div class="content">
				<button type="button" class="expandable">A. Griefing: Ruining the server, station, or someone's round (e.g. kidnapping, killing, spacing) without a relevant objective (e.g. murderboning).</button>
					<div class="content">
						<button type="button" class="expandable">01. Murderboning: Antagonists intentionally killing someone without it relating to an objective.</button>
							<div class="content">
								<button type="button" class="non-expandable">You may kill a non-objective as long as you can link it to the completion of your objective ("There can be no witnesses if there's no one on station to witness it" does not count). Nuclear teams, wizards, blobs, traitors with hijack, ascended heretics, and ascended darkspawn are exempt from this rule provided they leave arrivals alone.</button>
							</div>
					</div>
				<button type="button" class="non-expandable">B. Greytiding: Non-antagonists committing <a href="https://web.archive.org/web/20250514061637/https://wiki.yogstation.net/wiki/Official:Space_Law#majorcrimes">moderate or higher crimes</a> without an emergency forcing their hand.</button>

				<button type="button" class="expandable">C. Powergaming: Taking steps to proactively thwart potential attack vectors on yourself or the station before a threat presents itself</button>
					<div class="content">
						<button type="button" class="non-expandable">Examples include collecting or creating powerful things just because they're powerful and you could theoretically be attacked, cutting cameras or forcing the AI to state its laws at round start because you "don't trust computers," etc.</button>
						<button type="button" class="non-expandable">Janitors are not secretly Delta SEAL Ranger Space Marines just praying for an excuse to whip out their "Space Cleaner" bottle full of flesh melting chemicals. You shouldn't even have that kind of thing on you at Green or Blue Alert, same as IRL janitors don't keep sawed-off shotguns stuffed down their pants while mopping cafeterias because they "know" a deadly threat is going to present itself today.</button>
					</div>

				<button type="button" class="expandable">D. Validhunting: Prioritizing pursuit of antagonists over other duties because you know OOC they are antagonists.</button>
					<div class="content">
						<button type="button" class="non-expandable">Security/Command are the protagonists of this story, so don't go looking for trouble if you aren't one of them; your primary goal if you aren't is to do your job when safe and Run>Hide>Fight (in priority order) if it isn't. Gamma Alerts or similar events (e.g. confirmed wizards, nuke ops) are an imminent threat to all and render your job irrelevant until resolved, but remember the only John Rambos aboard are Security; as such, if you want to be Rambo, join the round as Security. Otherwise, law enforcement isn't any of your business apart from reporting the crime unless you are called upon or security is out of the picture permanently. Your employer (NT) would prefer you report crime but otherwise attend to your job rather than be a vigilante.</button>
						<button type="button" class="non-expandable">For Security, validhunting includes ignoring minor crimes as well as keeping an OOC IC watchful eye on someone who has only committed a minor crime because you have spotted a metashielded item that you know you aren't allowed to use as evidence they are an antagonist. Remember: your employer does not know what "Red Texts" or "Green Texts" are, they only require you enforce <a href="https://web.archive.org/web/20250514061637/https://wiki.yogstation.net/wiki/Official:Space_Law">Space Law</a> to the best of your ability.</button>
					</div>
			</div>
		<button type="button" class="expandable">08. Don't abandon a role because you forgot to set your preferences properly.</button>
			<div class="content">
				<button type="button" class="non-expandable">"I've been converted/spawned into a role I don't want to be" is not a valid reason for cryoing/disconnecting/AFKing.</button>
				<button type="button" class="non-expandable">If there's an HoP available, request reassignment.</button>
				<button type="button" class="non-expandable">For antagonists, reach out to us via ahelp and we'll try to fix it if reasonable and prudent.</button>
				<button type="button" class="non-expandable">With that said, <b>you may still have to ride out your mistake to not ruin other players' rounds, as they may have taken great risks just to convert someone who forgot to indicate that they refuse to play that role</b>.</button>
			</div>
		<button type="button" class="expandable">09. Use English.</button>
			<div class="content">
				<button type="button" class="non-expandable">
					This goes for both IC (i.e. "Common" is English) and OOC, purely because we do not have an on-hand team of linguists to live translate everything.
				</button>
			</div>
		<button type="button" class="expandable">10. Role-play.</button>
			<div class="content">
				<button type="button" class="expandable">A. Choose a reasonable, RP name for the character you are playing.</button>
					<div class="content">
						<button type="button" class="non-expandable">Every race has a <a href="https://web.archive.org/web/20250515093727/https://wiki.yogstation.net/wiki/Naming_Rules">naming pattern</a>; do your best to follow it, but ahelp if you can't figure it out.</button>
						<button type="button" class="non-expandable">Don't choose obscene names or attempt to mimic famous individuals; a good rule of thumb is if they have a <a href="https://www.wikipedia.org/">Wikipedia</a> page, they're famous.</button>
						<button type="button" class="non-expandable">No honorifics in your name with the exception of Clowns, Mimes, and antagonists.</button>
					</div>
				<button type="button" class="expandable">B. Crew are employees of a cutting edge research facility without suspicion of imminent disaster.</button>

			</div>

		<button type="button" class="expandable">11. Listen to the admins.</button>
			<div class="content">
				<p>
					We're reasonable people. If you disagree with a ticket, bring it to our attention after the round.
				</p>
			</div>


		<button type="button" class="expandable"><h2>Antagonists</h2></button>
			<div class="content">
				<p>01. Work towards your objectives; do not abandon them in favor of being friendly or AFK.</p>
				<p>02. If a team antagonist, listen to your leader (e.g. head revoluntionary, head gangster, whoever brainwashed you). They are the authority on what is and what is not working towards your objectives.</p>
				<p>03. Don't quit the round because you don't like the antagonist role; that's on you for not setting your antagonist preferences properly. In the meantime, ahelp if you accidentally left something on and are now stuck so we can try to figure something out for you.</p>
			</div>

		<button type="button" class="expandable"><h2>Heads of Staff</h2></button>
			<div class="content">
				<button type="button" class="non-expandable">01. The (acting) Captain or a reasonable designee must take possession of the Nuclear Authorization Disk in order to protect it.</button>
				<button type="button" class="non-expandable">02. Don't leave the station without permission from the admins (or CentCom).</button>
				<button type="button" class="expandable">03. You must be minimally competent at managing your subordinates as well as technical proficiency in your department; you are charged with ensuring your department pursues (and ideally, achieves) its basic function and goals.</button>
					<div class="content">
						<button type="button" class="non-expandable">Managing your subordinates includes helping them where requested or in emergencies as well as evaluating their competencies to best assign them to tasks or evaluating the lack thereof in order to consider them for termination; NanoTrasen does not want to pay someone to be an Engineer if they haven't touched anything power or atmoshperics related because they want to go get drunk at the Bar.</button>
						<button type="button" class="non-expandable">Know how to do every job in the department you are the head of, at least a basic level. As an example, the Chief Medical Officer doesn't need to (and ideally, shouldn't) be the best surgeon on shift, but they should know basic anatomy and how to use a Medical Scanner.</button>
						<button type="button" class="non-expandable">Don't compromise the function of the station or your department without good reason.</button>
					</div>
				<button type="button" class="expandable">04. Follow the <a href="https://web.archive.org/web/20250514061637/https://wiki.yogstation.net/wiki/Official:Space_Law#Alert_Procedures">Alert Procedures</a>.</button>
					<div class="content">
						<p>Setting an alert level too high is unfair to antagonists if you're essentially forcing people to metagame by over-estimating the threat level.</p>
						<p>An alert level too low is <b>not</b> a violation of this rule as it is an IC issue (less assistance from crew and CentCom).</p>
					</div>
				<button type="button" class="non-expandable">05. With a Captain above them, the Head of Personnel should not involve themselves in Security.</button>
			</div>
		<button type="button" class="expandable"><h2>Silicons</h2></button>
			<div class="content">
				<p>Follow <a href="https://web.archive.org/web/20250514060305/https://wiki.yogstation.net/wiki/Official:Silicon_Policy">Silicon Policy</a>.</p>
			</div>

		<button type="button" class="expandable"><h2>Security</h2></button>
			<div class="content">
				<button type="button" class="non-expandable">01. Follow <b>and apply</b> <a href="https://web.archive.org/web/20250514061637/https://wiki.yogstation.net/wiki/Official:Space_Law">Space Law</a> regardless of suspected antagonist status.</button>
				<button type="button" class="expandable">02. Confiscated or contraband items MUST be placed in the contraband, armory, or evidence locker as soon as possible.</button>
					<div class="content">
						<p>CentCom does not want you to be a high priority target to attack and loot for potential Syndicate or similar equipment, not to mention needing the evidence handy and not in your pocket somewhere if and when a trial commences.</p>
					</div>
				<button type="button" class="non-expandable">03. Don't use confiscated or contraband items outside of an emergency while securing them after you have exhausted other options.</button>
				<button type="button" class="non-expandable">04. Undercover security forfeit security protections, i.e. you cannot charge someone with Assault of an Officer if they did not know you were an Officer.</button>
			</div>
		<button type="button" class="expandable"><h2>Engineering</h2></button>
			<div class="content">
				<button type="button" class="expandable">01. Do not start an engine without having read instructions first or working with someone who has.</button>
					<div class="content">
						<p>Causing catastrophic (i.e. station-ruining) engine failures because you were lazy and decided to wing it may be held against you as grief.</p>
					</div>
				<button type="button" class="expandable">02. Don't abuse telecommunications.</button>
					<div class="content">
						<p>Don't disrupt communications or upload confusing/harmful/obscene scripts. If communications remain easily readable, it's ok.</p>
					</div>
				<button type="button" class="expandable">03. Don't impede the AI's control over systems without a valid reason.</button>
					<div class="content">
						<p>At the start of the round, you have no reason to suspect the AI could secretly be plotting to kill you. Much like you wouldn't yank your ethernet cord because your computer beeped, don't cut cameras or disable/replace remotely accessible systems just because the AI didn't open the airlock for you when you asked, or worse yet, because you "don't trust computers."</p>
					</div>
			</div>
		<button type="button" class="expandable"><h2>Chemistry</h2></button>
			<div class="content">
				<button type="button" class="expandable">01. Don't negligently or maliciously distribute harmful chemicals.</button>
					<div class="content">
						<p>Label drugs properly and don't hand them out in amounts that cause overdose.</p>
					</div>
			</div>
		<button type="button" class="expandable"><h2>Ghost Roles</h2></button>
			<div class="content">
				<button type="button" class="expandable">01. Act in the interests of your team if you have one.</button>
					<div class="content">
						<p>An example of a team-based ghost role would be Ashwalkers, who must protect their own, kill outsiders, and return bodies to their tendril.</p>
						<p>An example of a plural but not team-based ghost role would be Prisoners.</p>
					</div>
				<button type="button" class="non-expandable">Podpeople, Free Golems, Hotel staff, Vets, and Beach Bums are examples of non-antagonist ghost roles. When in doubt, assume you are not an antagonist or ahelp before taking antagonistic action.</button>
			</div>
		<button type="button" class="expandable"><h2>Creatures</h2></button>
			<div class="content">
				<p>Creatures are not antagonists unless victims of a spell from a Staff of Change or Wand of Polymorph, who must answer to their creator.</p>
				<p>Slimes from pyroclastic anomalies are antagonists, as they must kill to feed.</p>
				<p><b>General</b> rules still apply to creatures, including but not limited to grief i.e. station damage and murderboning.</p>
			</div>
	<script src="./rules.js"></script>
	</body>

</html>