https://wiki.fulp.gg/api.php?action=feedcontributions&feedformat=atom&user=AnetteraFulpstation - User contributions [en-gb]2026-04-23T17:30:35ZUser contributionsMediaWiki 1.44.0https://wiki.fulp.gg/index.php?title=MediaWiki:Sidebar&diff=71MediaWiki:Sidebar2025-11-09T10:34:15Z<p>Anettera: </p>
<hr />
<div><br />
* navigation<br />
** mainpage|mainpage-description<br />
** Server_Rules|Server Rules<br />
** Discord_rules|Discord/Forum Rules<br />
** recentchanges-url|recentchanges<br />
** helppage|help-mediawiki<br />
** specialpages-url|specialpages<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Anetterahttps://wiki.fulp.gg/index.php?title=Discord_rules&diff=70Discord rules2025-11-09T10:33:30Z<p>Anettera: Created page with "==The Forums, Discord, and everywhere else outside of the server== # All core rules apply to communications between players outside of the SS13 server. Core rules 3 and 4 (prohibiting sexual or discriminatory content) will be strictly enforced. Core rules 2-4 still apply the #shitposting channel. Sending inappropriate content to other players via direct messages on Discord will result in a ban if it is brought to an admin’s attention. # Discussing the current round an..."</p>
<hr />
<div>==The Forums, Discord, and everywhere else outside of the server==<br />
# All core rules apply to communications between players outside of the SS13 server. Core rules 3 and 4 (prohibiting sexual or discriminatory content) will be strictly enforced. Core rules 2-4 still apply the #shitposting channel. Sending inappropriate content to other players via direct messages on Discord will result in a ban if it is brought to an admin’s attention. <br />
# Discussing the current round anywhere but in-round Dead chat is prohibited. Please wait until the round-end screen to discuss a round or file a report on the forums to avoid disclosing vital round information. See “Metacomming” in the Rules Glossary.<br />
# All ban appeals and staff reports must be made in the Fulpstation forums. Sending direct messages to admins regarding reports is not acceptable.<br />
# Forum comments on appeals and grief reports should only be made by involved parties. If you weren’t named in the thread or witness to the event, you probably shouldn’t comment. These threads are not the place to discuss whether you think someone else’s ban was applied properly or discuss server policies. Such comments are subject to deletion and making these comments repeatedly is a bannable offense. Players are welcome to discuss appeals and reports in the Discord as long as it’s done in a way that is not harassing to players or staff.<br />
# Do not ping staff members on the Discord without reason. Pinging mentors, reboot gang, and active administration as well as individual staff members should only be done once to get their attention. Spam pinging roles or players will result in a mute/ shed time. Please see the pinned message in #public-chat for a full list of pingable roles.<br />
# Verified players do not need to be mentors to answer questions in #Mentor-Help; however, please only do so if you are certain of the answer to avoid sending misinformation.<br />
# The criticisms channel should not be used to gang up on or harass other players. Keep in mind that we are a beginner-friendly server. Mistakes and bad judgment calls will happen from time to time. Try to focus your criticisms in a constructive way rather than using this as an excuse to insult others.<br />
# Images, links, and memes should be posted in the appropriate misc channel. This is to avoid clogging up public chat with large images that impede conversations. <br />
# Raiding or intentionally griefing other servers is a bannable offense. If administrators from other servers contact us about bad behavior from Fulp players, your ban on their server may be applied to ours as well.<br />
# Sending direct messages (DMs) to staff via Discord to complain about staff rulings is not acceptable. If you think a staff member made a mistake, you can file a staff report here: https://forms.gle/AxKRrcXJChn9GTKbA</div>Anetterahttps://wiki.fulp.gg/index.php?title=Old_guide_to_contributing&diff=69Old guide to contributing2025-11-09T10:27:32Z<p>Anettera: </p>
<hr />
<div>== Tools ==<br />
* Dream Maker - comes installed with Byond. NOT RECOMMENDED!<br />
* [https://code.visualstudio.com/ Visual Studio Code] - Modern lightweight code editor. Recommended! <br />
**Use in combination with extensions to improve experience. You'll be prompted to install recommended extensions - you 100% should do that. Also, check the extension marketplace!<br />
**To compile, use Ctrl + Shift + P and type “build”.<br />
**You can debug the project by running the “Launch Dreamseeker” command in the debug menu. This allows you to view variables while executing the code. You can place a breakpoint (forces the system to wait for you to resume it so you can inspect variables)<br />
*[https://git-scm.com/ Git] - This is how professionals keep track of changes in code. I highly suggest you get familiar with the git command line, but there are also numerous applications you can use if you're intimidated. Popular applications in the community for interacting with git are Gitkraken, Github Desktop, and Tortoise Git. VS Code also has a pretty solid git client.<br />
**Please! Read up on how git works. It's something you MUST work with if you want to contribute on your own. There are tons of resources for this. Here's a decent one I'm familiar with: https://learngitbranching.js.org/. If you're having issues with git, please check the [https://git-scm.com/docs git docs] or [https://google.com your choice] of [https://stackoverflow.com/ god] for assistance.<br />
*For sprites: [https://www.aseprite.org/ Aseprite], [https://www.gimp.org/ Gimp], or any other pixel art tool. You will need to convert the files from .dmi to .png if you are using something besides Dream Maker's built-in tool for sprites. Additionally, Aseprite is available for free [https://github.com/aseprite/aseprite here] but requires more set up than buying it from the website or Steam.<br />
<br />
== Getting Started ==<br />
Now that you have the tools, there's a little more setup we need to do if you want to contribute to the repository.<br />
<br />
If you haven't already, make a github account. Next, you'll want to make a fork of [https://github.com/fulpstation/fulpstation github.com/fulpstation/fulpstation] (click the fork button in the top right).<br />
<br />
Once your fork is ready, you need to pull the code down into your machine. Make a folder somewhere and clone the repo into it (if you're using git via commandline or gitbash, the syntax for this is <code>git clone github.com/<yourname>/fulpstation</code>. <br />
<br />
To keep things clean, you should never make changes in your master branch. That's where you want to fork from, and your goal is to make merging code into the upstream as easy as possible. The best way to do this is to keep your master branch as close to the upstream master branch as possible. You'll want to make branches any time you make changes. <br />
<br />
Making a branch is easy. <code>git branch <name></code> followed by <code>git checkout <name></code> will make and change your active branch to <name>. <br />
Or you can use <code>git checkout -b <name></code>. Same outcome. Git has a lot of nifty shortcuts and functions. Seriously, read the docs! <br />
<br />
==Code!==<br />
Byond, the game engine, uses Dream Maker, which is a language made custom for the engine. <br />
<br />
Dream Maker is object oriented. There is a clearly defined hierarchy. There are 5 main objects.<br />
<br />
*ATOM (You should never use this, forget I said it exists)<br />
**Area - used to define groups of turfs<br />
**Turf - represents a single cell on the map. Everything on the turf could be said to belong to the turf.<br />
**Obj - used to define things that aren't turfs, areas, or mobs<br />
**Mob - used to define mobile objects.<br />
Everything in the game is derived from those 4 main objects. <br />
<br />
Let's talk about some of my own code:<br />
<br />
<pre>/obj/effect/spawner/random_mob<br />
icon = 'fulp_modules/mob_spawners/icons/landmark_static.dmi'<br />
icon_state = "exclamation"<br />
name = "custom mob spawner"<br />
var/list/valid_mobs<br />
<br />
/obj/effect/spawner/random_mob/Initialize(mapload)<br />
..()<br />
if(valid_mobs?.len)<br />
var/mobspawndata = pick_random_item_and_count(valid_mobs)<br />
if(mobspawndata)<br />
var/mobX = mobspawndata[1]<br />
for(var/i = 0, i < mobspawndata[2], i++)<br />
new mobX(loc)<br />
return INITIALIZE_HINT_QDEL<br />
<br />
/obj/effect/spawner/random_mob/maintenance<br />
name = "maintenance mob spawner"<br />
valid_mobs = list(<br />
/mob/living/simple_animal/hostile/viscerator = list(1,2,4),<br />
/mob/living/simple_animal/cow = list(1,1,2),<br />
/mob/living/simple_animal/hostile/hivebot = list(1,1,3),<br />
/mob/living/simple_animal/hostile/skeleton = list(1,1,2),<br />
/mob/living/simple_animal/bot/medbot = list(1,1,1),<br />
/mob/living/simple_animal/crab = list(1,1,3),<br />
/mob/living/simple_animal/hostile/rat = list(1,1,2),<br />
/mob/living/simple_animal/chicken = list(1,1,3),<br />
/mob/living/simple_animal/hostile/killertomato = list(1,1,2)<br />
)</pre><br />
There's a lot going on here so lets take it one step at a time.<br />
<br />
<code>/obj/effect/spawner/random_mob</code> This means I am defining <code>random_mob</code>. It is a subtype of spawner, which is a subtype of effect, which is a subtype of object. This one line actually does a lot of work, because <code>random_mob</code> now has inherited the procedures and variables of its ancestors. In fact, lines 2-4 are actually just me overriding the defaults on the spawner object! On line 8, <code>var/list/valid_mobs</code>, I am creating an empty list called valid mobs. I am leaving it empty on purpose because I wanted this object to be a skeleton that mostly defines variables and behaviors so that objects that inherit from it get access to those variables and behaviors. <br />
<br />
Lines 10-18 I am overriding the Initialize proc. This procedure gets called when something is made real in the game. What I defined on line one does not make it spawn - Initialize does that. <br />
<br />
<code>..()</code> is the king of overriding. This nifty 4 characters calls the proc of the same name on the parent object. In this case, it is calling the version of Initialize() defined in <code>spawner</code>. The engine will wait for that version to finish running before resuming. <br />
<br />
<code>if(valid_mobs?.len)</code>. This basically means “If <code>valid_mobs</code>” exists and has a length (remember, <code>valid_mobs</code> is a list), we continue to the next line. If it does not exist, we skip to line 18. <br />
<br />
<code>var/mobspawndata = pick_random_item_and_count(valid_mobs)</code> We define a variable called mobspawndata because we want to hold something for use later. <code>var/mobspawndata</code> is set to the return of <code>pick_random_item_and_count(valid_mobs)</code>, which is a proc that is defined elsewhere. <br />
<br />
Now is an excellent time to tell you my favorite feature of VS Code: Right click! By using Go To Definition, you can easily jump to where something is defined! This means you can view this weird proc and find out what it does yourself! So don't ask me. <br />
[[File:Vscodegotodefinition.png|frame|alt=Go to definition (F12)|De-spaghettify your life]]<br />
<br />
I'm tired and don't feel like explaining the rest thoroughly so figure it out yourself. Basically the rest of the procedure is used to spawn X amount of Y monster which was picked by the proc. <br />
<br />
<code>/obj/effect/spawner/random_mob/maintenance</code> The definition of this object gives it a special name and a list. The list contains other mobs. Each mob in the list has its own list of 3 integers. Pick weight, minimum count, and maximum count. The proc randomly picks a single mob and an appropriate number for the mob.<br />
<br />
Test often, commit often, and maybe you'll figure it out. Good luck.<br />
<br />
Use git commit to tell git to hold onto your changes. Use git push to send them to github. Open github and open pull requests. ehhh thats all for today, figure it out lmao</div>Anetterahttps://wiki.fulp.gg/index.php?title=Old_guide_to_contributing&diff=68Old guide to contributing2025-11-09T10:20:36Z<p>Anettera: Created page with "== Tools == * Dream Maker - comes installed with Byond. NOT RECOMMENDED! * Visual Studio Code - Modern lightweight code editor. Recommended! **Use in combination with extensions to improve experience. You'll be prompted to install recommended extensions - you 100% should do that. Also, check the extension marketplace! **To compile, use Ctrl + Shift + P and type “build”. **You can debug the project by running the “Launch Dreamseeker” command in the debug menu. T..."</p>
<hr />
<div>== Tools ==<br />
* Dream Maker - comes installed with Byond. NOT RECOMMENDED!<br />
* Visual Studio Code - Modern lightweight code editor. Recommended! <br />
**Use in combination with extensions to improve experience. You'll be prompted to install recommended extensions - you 100% should do that. Also, check the extension marketplace!<br />
**To compile, use Ctrl + Shift + P and type “build”.<br />
**You can debug the project by running the “Launch Dreamseeker” command in the debug menu. This allows you to view variables while executing the code. You can place a breakpoint (forces the system to wait for you to resume it so you can inspect variables)<br />
*Git - This is how professionals keep track of changes in code. I highly suggest you get familiar with the git command line, but there are also numerous applications you can use if you're intimidated. Popular applications in the community for interacting with git are Gitkraken, Github Desktop, and Tortoise Git. VS Code also has a pretty solid git client.<br />
**Please! Read up on how git works. It's something you MUST work with if you want to contribute on your own. There are tons of resources for this. Here's a decent one I'm familiar with: https://learngitbranching.js.org/. If you're having issues with git, please check the git docs or your choice of god for assistance.<br />
*For sprites: Aseprite, Gimp, or any other pixel art tool. You will need to convert the files from .dmi to .png if you are using something besides Dream Maker's built-in tool for sprites. Additionally, Aseprite is available for free here but requires more set up than buying it from the website or Steam.<br />
<br />
== Getting Started ==<br />
Now that you have the tools, there's a little more setup we need to do if you want to contribute to the repository.<br />
<br />
If you haven't already, make a github account. Next, you'll want to make a fork of [https://github.com/fulpstation/fulpstation github.com/fulpstation/fulpstation] (click the fork button in the top right).<br />
<br />
Once your fork is ready, you need to pull the code down into your machine. Make a folder somewhere and clone the repo into it (if you're using git via commandline or gitbash, the syntax for this is <code>git clone github.com/<yourname>/fulpstation</code>. <br />
<br />
To keep things clean, you should never make changes in your master branch. That's where you want to fork from, and your goal is to make merging code into the upstream as easy as possible. The best way to do this is to keep your master branch as close to the upstream master branch as possible. You'll want to make branches any time you make changes. <br />
<br />
Making a branch is easy. <code>git branch <name></code> followed by <code>git checkout <name></code> will make and change your active branch to <name>. <br />
Or you can use <code>git checkout -b <name></code>. Same outcome. Git has a lot of nifty shortcuts and functions. Seriously, read the docs! <br />
<br />
==Code!==<br />
Byond, the game engine, uses Dream Maker, which is a language made custom for the engine. <br />
<br />
Dream Maker is object oriented. There is a clearly defined hierarchy. There are 5 main objects.<br />
<br />
*ATOM (You should never use this, forget I said it exists)<br />
**Area - used to define groups of turfs<br />
**Turf - represents a single cell on the map. Everything on the turf could be said to belong to the turf.<br />
**Obj - used to define things that aren't turfs, areas, or mobs<br />
**Mob - used to define mobile objects.<br />
Everything in the game is derived from those 4 main objects. <br />
<br />
Let's talk about some of my own code:<br />
<br />
<pre>/obj/effect/spawner/random_mob<br />
icon = 'fulp_modules/mob_spawners/icons/landmark_static.dmi'<br />
icon_state = "exclamation"<br />
name = "custom mob spawner"<br />
var/list/valid_mobs<br />
<br />
/obj/effect/spawner/random_mob/Initialize(mapload)<br />
..()<br />
if(valid_mobs?.len)<br />
var/mobspawndata = pick_random_item_and_count(valid_mobs)<br />
if(mobspawndata)<br />
var/mobX = mobspawndata[1]<br />
for(var/i = 0, i < mobspawndata[2], i++)<br />
new mobX(loc)<br />
return INITIALIZE_HINT_QDEL<br />
<br />
/obj/effect/spawner/random_mob/maintenance<br />
name = "maintenance mob spawner"<br />
valid_mobs = list(<br />
/mob/living/simple_animal/hostile/viscerator = list(1,2,4),<br />
/mob/living/simple_animal/cow = list(1,1,2),<br />
/mob/living/simple_animal/hostile/hivebot = list(1,1,3),<br />
/mob/living/simple_animal/hostile/skeleton = list(1,1,2),<br />
/mob/living/simple_animal/bot/medbot = list(1,1,1),<br />
/mob/living/simple_animal/crab = list(1,1,3),<br />
/mob/living/simple_animal/hostile/rat = list(1,1,2),<br />
/mob/living/simple_animal/chicken = list(1,1,3),<br />
/mob/living/simple_animal/hostile/killertomato = list(1,1,2)<br />
)</pre><br />
There's a lot going on here so lets take it one step at a time.<br />
<br />
<code>/obj/effect/spawner/random_mob</code> This means I am defining <code>random_mob</code>. It is a subtype of spawner, which is a subtype of effect, which is a subtype of object. This one line actually does a lot of work, because <code>random_mob</code> now has inherited the procedures and variables of its ancestors. In fact, lines 2-4 are actually just me overriding the defaults on the spawner object! On line 8, <code>var/list/valid_mobs</code>, I am creating an empty list called valid mobs. I am leaving it empty on purpose because I wanted this object to be a skeleton that mostly defines variables and behaviors so that objects that inherit from it get access to those variables and behaviors. <br />
<br />
Lines 10-18 I am overriding the Initialize proc. This procedure gets called when something is made real in the game. What I defined on line one does not make it spawn - Initialize does that. <br />
<br />
<code>..()</code> is the king of overriding. This nifty 4 characters calls the proc of the same name on the parent object. In this case, it is calling the version of Initialize() defined in <code>spawner</code>. The engine will wait for that version to finish running before resuming. <br />
<br />
<code>if(valid_mobs?.len)</code>. This basically means “If <code>valid_mobs</code>” exists and has a length (remember, <code>valid_mobs</code> is a list), we continue to the next line. If it does not exist, we skip to line 18. <br />
<br />
<code>var/mobspawndata = pick_random_item_and_count(valid_mobs)</code> We define a variable called mobspawndata because we want to hold something for use later. <code>var/mobspawndata</code> is set to the return of <code>pick_random_item_and_count(valid_mobs)</code>, which is a proc that is defined elsewhere. <br />
<br />
Now is an excellent time to tell you my favorite feature of VS Code: Right click! By using Go To Definition, you can easily jump to where something is defined! This means you can view this weird proc and find out what it does yourself! So don't ask me. <br />
[[File:Vscodegotodefinition.png|frame|alt=Go to definition (F12)|De-spaghettify your life]]<br />
<br />
I'm tired and don't feel like explaining the rest thoroughly so figure it out yourself. Basically the rest of the procedure is used to spawn X amount of Y monster which was picked by the proc. <br />
<br />
<code>/obj/effect/spawner/random_mob/maintenance</code> The definition of this object gives it a special name and a list. The list contains other mobs. Each mob in the list has its own list of 3 integers. Pick weight, minimum count, and maximum count. The proc randomly picks a single mob and an appropriate number for the mob.<br />
<br />
Test often, commit often, and maybe you'll figure it out. Good luck.<br />
<br />
Use git commit to tell git to hold onto your changes. Use git push to send them to github. Open github and open pull requests. ehhh thats all for today, figure it out lmao</div>Anetterahttps://wiki.fulp.gg/index.php?title=File:Vscodegotodefinition.png&diff=67File:Vscodegotodefinition.png2025-11-09T10:18:05Z<p>Anettera: </p>
<hr />
<div>go to definition (f12)</div>Anetterahttps://wiki.fulp.gg/index.php?title=Chems&diff=66Chems2025-11-08T20:26:23Z<p>Anettera: </p>
<hr />
<div>{| class="wikitable sortable" style="width:100%; text-align:left; border: 3px solid ; cellspacing=0; cellpadding=2; "<br />
! scope="col" style='width:150px; '|Name<br />
! scope="col" class="unsortable" '|Formula<br />
! scope="col" class="unsortable" style='width:170px;'|Reaction conditions<br />
! scope="col" class="unsortable" style=''|Description<br />
! scope="col" class="unsortable" style=''|Chemical properties<br />
|-<br />
<br />
!style=''|{{anchor|Spaceacillin}}Spaceacillin<span style="color:#E1F2E6;background-color:white">▮</span><br />
<br>Inverse: [[#Sepsisillin|Sepsisillin]] <30%<br />
<br>pH: 8.1<span style="color:#23b36e;background-color:white">▮</span><br />
|{{RecursiveChem/Spaceacillin}}<br />
|<b>Min temp:</b> 100K<br />
<br><b>Overheat:</b> 900K<br />
<br><b>Optimal pH:</b> 5 to 10<br />
<br><b>Unstable purity:</b> <10%<br />
<br>Weakly Exothermic<br />
<br>H+ producing<br />
|Spaceacillin will provide limited resistance against disease and parasites. Also reduces infection in serious burns.<br />
|<b>Rate:</b> 0.04u/tick<br />
<br><b>Unreacted purity:</b> 100%<br />
|-<br />
<br />
!|{{anchor|Epinephrine}}Epinephrine<span style="color:#D2FFFA;background-color:white">▮</span><br />
<br>Inverse: [[#Toxic Monomers|Toxic Monomers]] <25%<br />
<br>pH: 10.2<span style="color:#3f93cf;background-color:white">▮</span><br />
|{{RecursiveChem/Epinephrine}}<br />
|<b>Min temp:</b> 100K<br />
<br><b>Overheat:</b> 900K<br />
<br><b>Optimal pH:</b> 5 to 10<br />
<br><b>Unstable purity:</b> <10%<br />
<br>Weakly Exothermic<br />
<br>H+ consuming<br />
|Very minor boost to stun resistance. Slowly heals damage if a patient is in critical condition, as well as regulating oxygen loss. Overdose causes weakness and toxin damage.<br />
|<b>Rate:</b> 0.1u/tick<br />
<br><b>Unreacted purity:</b> 100%<br />
<br><b>OD:</b> 30u<br />
|-<br />
!|{{anchor|Diethylamine}}Diethylamine<span style="color:#604030;background-color:white">▮</span><br />
<br>Inverse: [[#Toxic Monomers|Toxic Monomers]] <25%<br />
<br>pH: 12<span style="color:#5a51a2;background-color:white">▮</span><br />
|{{RecursiveChem/Diethylamine}}<br />
|<b>Min temp:</b> 100K<br />
<br><b>Overheat:</b> 900K<br />
<br><b>Optimal pH:</b> 5 to 9<br />
<br><b>Unstable purity:</b> <15%<br />
<br>Weakly Exothermic<br />
<br>H+ consuming<br />
|A secondary amine, mildly corrosive.<br />
|<b>Rate:</b> 0.4u/tick<br />
<br><b>Unreacted purity:</b> 100%<br />
|-<br />
!|{{anchor|Cryptobiolin}}Cryptobiolin<span style="color:#ADB5DB;background-color:white">▮</span><br />
<br>Inverse: [[#Toxic Monomers|Toxic Monomers]] <25%<br />
<br>pH: 11.9<span style="color:#3853a4;background-color:white">▮</span><br />
|{{RecursiveChem/Cryptobiolin}}<br />
|<b>Min temp:</b> 100K<br />
<br><b>Overheat:</b> 900K<br />
<br><b>Optimal pH:</b> 5 to 9<br />
<br><b>Unstable purity:</b> <15%<br />
<br>Weakly Exothermic<br />
<br>H+ consuming<br />
|Cryptobiolin causes confusion and dizziness.<br />
|<b>Rate:</b> 0.6u/tick<br />
<br><b>Unreacted purity:</b> 100%<br />
|-<br />
!|{{anchor|Acetone}}Acetone<span style="color:#AF14B7;background-color:white">▮</span><br />
<br>Inverse: [[#Toxic Monomers|Toxic Monomers]] <25%<br />
<br>pH: 7<span style="color:#3aa651;background-color:white">▮</span><br />
|{{RecursiveChem/Acetone}}<br />
|<b>Min temp:</b> 100K<br />
<br><b>Overheat:</b> 900K<br />
<br><b>Optimal pH:</b> 5 to 9<br />
<br><b>Unstable purity:</b> <15%<br />
<br>Weakly Exothermic<br />
<br>H+ consuming<br />
|A slick, slightly carcinogenic liquid. Has a multitude of mundane uses in everyday life.<br />
|<b>Rate:</b> 0.4u/tick<br />
<br><b>Unreacted purity:</b> 100%<br />
|-<br />
!|{{anchor|Phenol}}Phenol<span style="color:#E7EA91;background-color:white">▮</span><br />
<br>Inverse: [[#Toxic Monomers|Toxic Monomers]] <25%<br />
<br>pH: 5.5<span style="color:#b5d335;background-color:white">▮</span><br />
|{{RecursiveChem/Phenol}}<br />
|<b>Min temp:</b> 100K<br />
<br><b>Overheat:</b> 900K<br />
<br><b>Optimal pH:</b> 5 to 9<br />
<br><b>Unstable purity:</b> <15%<br />
<br>Weakly Exothermic<br />
<br>H+ producing<br />
|An aromatic ring of carbon with a hydroxyl group. A useful precursor to some medicines, but has no healing properties on its own.<br />
|<b>Rate:</b> 0.4u/tick<br />
<br><b>Unreacted purity:</b> 100%<br />
|-<br />
!|{{anchor|Oil}}Oil<span style="color:#2D2D2D;background-color:white">▮</span><br />
<br>Inverse: [[#Toxic Monomers|Toxic Monomers]] <25%<br />
<br>pH: 4<span style="color:#f7ec1e;background-color:white">▮</span><br />
|{{RecursiveChem/Oil}}<br />
|<b>Min temp:</b> 100K<br />
<br><b>Overheat:</b> 900K<br />
<br><b>Optimal pH:</b> 5 to 9<br />
<br><b>Unstable purity:</b> <15%<br />
<br>Weakly Exothermic<br />
<br>H+ consuming<br />
|Burns in a small smoky fire, can be used to get Ash.<br />
|<b>Rate:</b> 0.4u/tick<br />
<br><b>Unreacted purity:</b> 100%<br />
|-<br />
!|{{anchor|Ammonia}}Ammonia<span style="color:#404030;background-color:white">▮</span><br />
<br>Inverse: [[#Toxic Monomers|Toxic Monomers]] <25%<br />
<br>pH: 11.6<span style="color:#3853a4;background-color:white">▮</span><br />
|{{RecursiveChem/Ammonia}}<br />
|<b>Min temp:</b> 500K<br />
<br><b>Overheat:</b> 980K<br />
<br><b>Optimal pH:</b> 5 to 10<br />
<br><b>Unstable purity:</b> <10%<br />
<br>Exothermic<br />
<br>H+ consuming<br />
|A caustic substance commonly used in fertilizer or household cleaners.<br />
|<b>Rate:</b> 0.4u/tick<br />
<br><b>Unreacted purity:</b> 100%<br />
|-<br />
|}</div>Anetterahttps://wiki.fulp.gg/index.php?title=Chems&diff=65Chems2025-11-08T20:24:43Z<p>Anettera: </p>
<hr />
<div>{| class="wikitable sortable" style="width:100%; text-align:left; border: 3px solid ; cellspacing=0; cellpadding=2; "<br />
! scope="col" style='width:150px; '|Name<br />
! scope="col" class="unsortable" '|Formula<br />
! scope="col" class="unsortable" style='width:170px;'|Reaction conditions<br />
! scope="col" class="unsortable" style=''|Description<br />
! scope="col" class="unsortable" style=''|Chemical properties<br />
|-<br />
<br />
!style=''|{{anchor|Spaceacillin}}Spaceacillin<span style="color:#E1F2E6;background-color:white">▮</span><br />
<br>Inverse: [[#Sepsisillin|Sepsisillin]] <30%<br />
<br>pH: 8.1<span style="color:#23b36e;background-color:white">▮</span><br />
|{{RecursiveChem/Spaceacillin}}<br />
|<b>Min temp:</b> 100K<br />
<br><b>Overheat:</b> 900K<br />
<br><b>Optimal pH:</b> 5 to 10<br />
<br><b>Unstable purity:</b> <10%<br />
<br>Weakly Exothermic<br />
<br>H+ producing<br />
|Spaceacillin will provide limited resistance against disease and parasites. Also reduces infection in serious burns.<br />
|<b>Rate:</b> 0.04u/tick<br />
<br><b>Unreacted purity:</b> 100%<br />
|-<br />
<br />
!|{{anchor|Epinephrine}}Epinephrine<span style="color:#D2FFFA;background-color:white">▮</span><br />
<br>Inverse: [[#Toxic Monomers|Toxic Monomers]] <25%<br />
<br>pH: 10.2<span style="color:#3f93cf;background-color:white">▮</span><br />
|{{RecursiveChem/Epinephrine}}<br />
|<b>Min temp:</b> 100K<br />
<br><b>Overheat:</b> 900K<br />
<br><b>Optimal pH:</b> 5 to 10<br />
<br><b>Unstable purity:</b> <10%<br />
<br>Weakly Exothermic<br />
<br>H+ consuming<br />
|Very minor boost to stun resistance. Slowly heals damage if a patient is in critical condition, as well as regulating oxygen loss. Overdose causes weakness and toxin damage.<br />
|<b>Rate:</b> 0.1u/tick<br />
<br><b>Unreacted purity:</b> 100%<br />
<br><b>OD:</b> 30u<br />
|-<br />
!|{{anchor|Epinephrine}}Epinephrine<span style="color:#D2FFFA;background-color:white">▮</span><br />
<br>Inverse: [[#Toxic Monomers|Toxic Monomers]] <25%<br />
<br>pH: 10.2<span style="color:#3f93cf;background-color:white">▮</span><br />
|{{RecursiveChem/Epinephrine}}<br />
|<b>Min temp:</b> 100K<br />
<br><b>Overheat:</b> 900K<br />
<br><b>Optimal pH:</b> 5 to 9<br />
<br><b>Unstable purity:</b> <15%<br />
<br>Weakly Exothermic<br />
<br>H+ consuming<br />
<br>grey slime extract<br />
|Very minor boost to stun resistance. Slowly heals damage if a patient is in critical condition, as well as regulating oxygen loss. Overdose causes weakness and toxin damage.<br />
|<b>Rate:</b> 0.1u/tick<br />
<br><b>Unreacted purity:</b> 100%<br />
<br><b>OD:</b> 30u<br />
|-<br />
!|{{anchor|Cryptobiolin}}Cryptobiolin<span style="color:#ADB5DB;background-color:white">▮</span><br />
<br>Inverse: [[#Toxic Monomers|Toxic Monomers]] <25%<br />
<br>pH: 11.9<span style="color:#3853a4;background-color:white">▮</span><br />
|{{RecursiveChem/Cryptobiolin}}<br />
|<b>Min temp:</b> 100K<br />
<br><b>Overheat:</b> 900K<br />
<br><b>Optimal pH:</b> 5 to 9<br />
<br><b>Unstable purity:</b> <15%<br />
<br>Weakly Exothermic<br />
<br>H+ consuming<br />
|Cryptobiolin causes confusion and dizziness.<br />
|<b>Rate:</b> 0.6u/tick<br />
<br><b>Unreacted purity:</b> 100%<br />
|-<br />
!|{{anchor|Acetone}}Acetone<span style="color:#AF14B7;background-color:white">▮</span><br />
<br>Inverse: [[#Toxic Monomers|Toxic Monomers]] <25%<br />
<br>pH: 7<span style="color:#3aa651;background-color:white">▮</span><br />
|{{RecursiveChem/Acetone}}<br />
|<b>Min temp:</b> 100K<br />
<br><b>Overheat:</b> 900K<br />
<br><b>Optimal pH:</b> 5 to 9<br />
<br><b>Unstable purity:</b> <15%<br />
<br>Weakly Exothermic<br />
<br>H+ consuming<br />
|A slick, slightly carcinogenic liquid. Has a multitude of mundane uses in everyday life.<br />
|<b>Rate:</b> 0.4u/tick<br />
<br><b>Unreacted purity:</b> 100%<br />
|-<br />
!|{{anchor|Phenol}}Phenol<span style="color:#E7EA91;background-color:white">▮</span><br />
<br>Inverse: [[#Toxic Monomers|Toxic Monomers]] <25%<br />
<br>pH: 5.5<span style="color:#b5d335;background-color:white">▮</span><br />
|{{RecursiveChem/Phenol}}<br />
|<b>Min temp:</b> 100K<br />
<br><b>Overheat:</b> 900K<br />
<br><b>Optimal pH:</b> 5 to 9<br />
<br><b>Unstable purity:</b> <15%<br />
<br>Weakly Exothermic<br />
<br>H+ producing<br />
|An aromatic ring of carbon with a hydroxyl group. A useful precursor to some medicines, but has no healing properties on its own.<br />
|<b>Rate:</b> 0.4u/tick<br />
<br><b>Unreacted purity:</b> 100%<br />
|-<br />
!|{{anchor|Oil}}Oil<span style="color:#2D2D2D;background-color:white">▮</span><br />
<br>Inverse: [[#Toxic Monomers|Toxic Monomers]] <25%<br />
<br>pH: 4<span style="color:#f7ec1e;background-color:white">▮</span><br />
|{{RecursiveChem/Oil}}<br />
|<b>Min temp:</b> 100K<br />
<br><b>Overheat:</b> 900K<br />
<br><b>Optimal pH:</b> 5 to 9<br />
<br><b>Unstable purity:</b> <15%<br />
<br>Weakly Exothermic<br />
<br>H+ consuming<br />
|Burns in a small smoky fire, can be used to get Ash.<br />
|<b>Rate:</b> 0.4u/tick<br />
<br><b>Unreacted purity:</b> 100%<br />
|-<br />
!|{{anchor|Ammonia}}Ammonia<span style="color:#404030;background-color:white">▮</span><br />
<br>Inverse: [[#Toxic Monomers|Toxic Monomers]] <25%<br />
<br>pH: 11.6<span style="color:#3853a4;background-color:white">▮</span><br />
|{{RecursiveChem/Ammonia}}<br />
|<b>Min temp:</b> 500K<br />
<br><b>Overheat:</b> 980K<br />
<br><b>Optimal pH:</b> 5 to 10<br />
<br><b>Unstable purity:</b> <10%<br />
<br>Exothermic<br />
<br>H+ consuming<br />
|A caustic substance commonly used in fertilizer or household cleaners.<br />
|<b>Rate:</b> 0.4u/tick<br />
<br><b>Unreacted purity:</b> 100%<br />
|-<br />
|}</div>Anetterahttps://wiki.fulp.gg/index.php?title=Chems&diff=64Chems2025-11-08T20:20:59Z<p>Anettera: </p>
<hr />
<div>{| class="wikitable sortable" style="width:100%; text-align:left; border: 3px solid ; cellspacing=0; cellpadding=2; "<br />
! scope="col" style='width:150px; '|Name<br />
! scope="col" class="unsortable" '|Formula<br />
! scope="col" class="unsortable" style='width:170px;'|Reaction conditions<br />
! scope="col" class="unsortable" style=''|Description<br />
! scope="col" class="unsortable" style=''|Chemical properties<br />
|-<br />
<br />
!style=''|{{anchor|Spaceacillin}}Spaceacillin<span style="color:#E1F2E6;background-color:white">▮</span><br />
<br>Inverse: [[#Sepsisillin|Sepsisillin]] <30%<br />
<br>pH: 8.1<span style="color:#23b36e;background-color:white">▮</span><br />
|{{RecursiveChem/Spaceacillin}}<br />
|<b>Min temp:</b> 100K<br />
<br><b>Overheat:</b> 900K<br />
<br><b>Optimal pH:</b> 5 to 10<br />
<br><b>Unstable purity:</b> <10%<br />
<br>Weakly Exothermic<br />
<br>H+ producing<br />
|Spaceacillin will provide limited resistance against disease and parasites. Also reduces infection in serious burns.<br />
|<b>Rate:</b> 0.04u/tick<br />
<br><b>Unreacted purity:</b> 100%<br />
|-<br />
|}</div>Anetterahttps://wiki.fulp.gg/index.php?title=Chems&diff=63Chems2025-11-08T20:20:41Z<p>Anettera: </p>
<hr />
<div><gallery><br />
Beefman.png<br />
Beefmanstanding.png<br />
</gallery><br />
<br />
{| class="wikitable sortable" style="width:100%; text-align:left; border: 3px solid ; cellspacing=0; cellpadding=2; "<br />
! scope="col" style='width:150px; '|Name<br />
! scope="col" class="unsortable" '|Formula<br />
! scope="col" class="unsortable" style='width:170px;'|Reaction conditions<br />
! scope="col" class="unsortable" style=''|Description<br />
! scope="col" class="unsortable" style=''|Chemical properties<br />
|-<br />
<br />
!style=''|{{anchor|Spaceacillin}}Spaceacillin<span style="color:#E1F2E6;background-color:white">▮</span><br />
<br>Inverse: [[#Sepsisillin|Sepsisillin]] <30%<br />
<br>pH: 8.1<span style="color:#23b36e;background-color:white">▮</span><br />
|{{RecursiveChem/Spaceacillin}}<br />
|<b>Min temp:</b> 100K<br />
<br><b>Overheat:</b> 900K<br />
<br><b>Optimal pH:</b> 5 to 10<br />
<br><b>Unstable purity:</b> <10%<br />
<br>Weakly Exothermic<br />
<br>H+ producing<br />
|Spaceacillin will provide limited resistance against disease and parasites. Also reduces infection in serious burns.<br />
|<b>Rate:</b> 0.04u/tick<br />
<br><b>Unreacted purity:</b> 100%<br />
|-<br />
|}</div>Anetterahttps://wiki.fulp.gg/index.php?title=Chem&diff=62Chem2025-11-08T20:17:42Z<p>Anettera: Redirected page to Chems</p>
<hr />
<div>#REDIRECT [[Chems]]</div>Anetterahttps://wiki.fulp.gg/index.php?title=Main_Page&diff=61Main Page2025-11-08T20:17:04Z<p>Anettera: </p>
<hr />
<div>This is the wiki for Fulpstation, a custom fork of the /tg/station flavoured fork of Space Station 13.<br />
<br />
<big>'''This wiki is new and under heavy construction. Anything can change at any time, and you should expect issues.'''</big> <br />
<br />
<br />
Most things listed here are Fulpstation-Unique, and the tgstation wiki should be used for everything else.<br />
<br />
* Play! [byond://fulp.gg:1338 fulp.gg:1338]<br />
* Our Repository: https://github.com/fulpstation/fulpstation<br />
* tgstation's Repository: https://github.com/tgstation/tgstation<br />
* Forum: https://forum.fulp.gg<br />
* Discord: https://discord.gg/dSw5nqgDye<br />
* tgstation's Wiki: https://wiki.tgstation13.org<br />
* Map viewer: https://webmap.affectedarc07.co.uk<br />
<br />
Space Station 13 is a paranoia-laden round-based roleplaying game set against the backdrop of a nonsensical, metal death trap masquerading as a space station, with charming spritework designed to represent the sci-fi setting and its dangerous undertones. Have fun, and survive!</div>Anetterahttps://wiki.fulp.gg/index.php?title=MediaWiki:Common.css&diff=59MediaWiki:Common.css2025-11-08T16:34:31Z<p>Anettera: </p>
<hr />
<div>/* CSS placed here will be applied to all skins */<br />
.tooltiptext {<br />
position: absolute;<br />
display: block;<br />
z-index: 2;<br />
width: 250px;<br />
padding: 10px;<br />
visibility: hidden;<br />
opacity: 0;<br />
white-space: normal;<br />
text-align: left;<br />
transition: all 0.2s;<br />
border: 1px solid #aaa;<br />
background-color: var(--background-color-neutral, #eaecf0);<br />
}<br />
<br />
.tooltip {<br />
position: relative;<br />
}<br />
<br />
.tooltip:hover>.tooltiptext {<br />
visibility: visible;<br />
opacity: 1;<br />
}<br />
<br />
.vector-main-menu-action-opt-out {<br />
display:none;<br />
}<br />
<br />
.vector-toc .vector-toc-link {<br />
word-break: normal; <br />
}</div>Anetterahttps://wiki.fulp.gg/index.php?title=MediaWiki:Common.css&diff=58MediaWiki:Common.css2025-11-08T16:34:13Z<p>Anettera: </p>
<hr />
<div>/* CSS placed here will be applied to all skins */<br />
.tooltiptext {<br />
position: absolute;<br />
display: block;<br />
z-index: 2;<br />
width: 250px;<br />
padding: 10px;<br />
visibility: hidden;<br />
opacity: 0;<br />
white-space: normal;<br />
text-align: left;<br />
transition: all 0.2s;<br />
border: 1px solid #aaa;<br />
background-color: var(--background-color-neutral, #eaecf0);<br />
}<br />
<br />
.tooltip {<br />
position: relative;<br />
}<br />
<br />
.tooltip:hover>.tooltiptext {<br />
visibility: visible;<br />
opacity: 1;<br />
}<br />
<br />
.vector-main-menu-action-opt-out {<br />
display:none;<br />
}<br />
<br />
.vector-toc .vector-toc-link {<br />
word-break: normal; <br />
}<br />
}</div>Anetterahttps://wiki.fulp.gg/index.php?title=MediaWiki:Common.css&diff=46MediaWiki:Common.css2025-11-08T16:16:52Z<p>Anettera: </p>
<hr />
<div>/* CSS placed here will be applied to all skins */<br />
.tooltiptext {<br />
position: absolute;<br />
display: block;<br />
z-index: 2;<br />
width: 250px;<br />
padding: 10px;<br />
visibility: hidden;<br />
opacity: 0;<br />
white-space: normal;<br />
text-align: left;<br />
transition: all 0.2s;<br />
border: 1px solid #aaa;<br />
background-color: var(--background-color-neutral, #eaecf0);<br />
}<br />
<br />
.tooltip {<br />
position: relative;<br />
}<br />
<br />
.tooltip:hover>.tooltiptext {<br />
visibility: visible;<br />
opacity: 1;<br />
}<br />
<br />
.vector-main-menu-action-opt-out {<br />
display:none;<br />
}</div>Anetterahttps://wiki.fulp.gg/index.php?title=MediaWiki:Common.css&diff=45MediaWiki:Common.css2025-11-08T16:15:41Z<p>Anettera: </p>
<hr />
<div>/* CSS placed here will be applied to all skins */<br />
.tooltiptext {<br />
position: absolute;<br />
display: block;<br />
z-index: 2;<br />
width: 250px;<br />
padding: 10px;<br />
visibility: hidden;<br />
opacity: 0;<br />
white-space: normal;<br />
text-align: left;<br />
transition: all 0.2s;<br />
border: 1px solid #aaa;<br />
background-color: inherit;<br />
}<br />
<br />
.tooltip {<br />
position: relative;<br />
}<br />
<br />
.tooltip:hover>.tooltiptext {<br />
visibility: visible;<br />
opacity: 1;<br />
}<br />
<br />
.vector-main-menu-action-opt-out {<br />
display:none;<br />
}</div>Anetterahttps://wiki.fulp.gg/index.php?title=MediaWiki:Common.css&diff=44MediaWiki:Common.css2025-11-08T16:14:55Z<p>Anettera: </p>
<hr />
<div>/* CSS placed here will be applied to all skins */<br />
.tooltiptext {<br />
position: absolute;<br />
display: block;<br />
z-index: 2;<br />
width: 250px;<br />
padding: 10px;<br />
visibility: hidden;<br />
opacity: 0;<br />
white-space: normal;<br />
text-align: left;<br />
transition: all 0.2s;<br />
border: 1px solid #aaa;;<br />
}<br />
<br />
.tooltip {<br />
position: relative;<br />
}<br />
<br />
.tooltip:hover>.tooltiptext {<br />
visibility: visible;<br />
opacity: 1;<br />
}<br />
<br />
.vector-main-menu-action-opt-out {<br />
display:none;<br />
}</div>Anetterahttps://wiki.fulp.gg/index.php?title=Chems&diff=43Chems2025-11-08T16:14:16Z<p>Anettera: </p>
<hr />
<div>{| class="wikitable sortable" style="width:100%; text-align:left; border: 3px solid ; cellspacing=0; cellpadding=2; "<br />
! scope="col" style='width:150px; '|Name<br />
! scope="col" class="unsortable" '|Formula<br />
! scope="col" class="unsortable" style='width:170px;'|Reaction conditions<br />
! scope="col" class="unsortable" style=''|Description<br />
! scope="col" class="unsortable" style=''|Chemical properties<br />
|-<br />
<br />
!style=''|{{anchor|Spaceacillin}}Spaceacillin<span style="color:#E1F2E6;background-color:white">▮</span><br />
<br>Inverse: [[#Sepsisillin|Sepsisillin]] <30%<br />
<br>pH: 8.1<span style="color:#23b36e;background-color:white">▮</span><br />
|{{RecursiveChem/Spaceacillin}}<br />
|<b>Min temp:</b> 100K<br />
<br><b>Overheat:</b> 900K<br />
<br><b>Optimal pH:</b> 5 to 10<br />
<br><b>Unstable purity:</b> <10%<br />
<br>Weakly Exothermic<br />
<br>H+ producing<br />
|Spaceacillin will provide limited resistance against disease and parasites. Also reduces infection in serious burns.<br />
|<b>Rate:</b> 0.04u/tick<br />
<br><b>Unreacted purity:</b> 100%<br />
|-<br />
|}</div>Anetterahttps://wiki.fulp.gg/index.php?title=MediaWiki:Common.css&diff=38MediaWiki:Common.css2025-11-08T15:29:51Z<p>Anettera: </p>
<hr />
<div>/* CSS placed here will be applied to all skins */<br />
.tooltiptext {<br />
position: absolute;<br />
display: block;<br />
z-index: 2;<br />
width: 250px;<br />
padding: 10px;<br />
visibility: hidden;<br />
opacity: 0;<br />
white-space: normal;<br />
text-align: left;<br />
transition: all 0.2s;<br />
border: 1px solid #aaa;<br />
background-color: #ffdd66;<br />
}<br />
<br />
.tooltip {<br />
position: relative;<br />
}<br />
<br />
.tooltip:hover>.tooltiptext {<br />
visibility: visible;<br />
opacity: 1;<br />
}<br />
<br />
.vector-main-menu-action-opt-out {<br />
display:none;<br />
}</div>Anetterahttps://wiki.fulp.gg/index.php?title=Template:RecursiveChem/Cryptobiolin&diff=37Template:RecursiveChem/Cryptobiolin2025-11-08T15:25:17Z<p>Anettera: Created page with "1 part Oxygen<br> 1 part Potassium<br> 1 part Sugar"</p>
<hr />
<div>1 part Oxygen<br><br />
1 part Potassium<br><br />
1 part Sugar</div>Anetterahttps://wiki.fulp.gg/index.php?title=Template:RecursiveChem/Phenol&diff=36Template:RecursiveChem/Phenol2025-11-08T15:24:47Z<p>Anettera: Created page with "1 part {{Tooltip|Oil|{{RecursiveChem/Oil}}}}<br> 1 part Chlorine<br> 1 part Water"</p>
<hr />
<div>1 part {{Tooltip|[[#Oil|Oil]]|{{RecursiveChem/Oil}}}}<br><br />
1 part Chlorine<br><br />
1 part Water</div>Anetterahttps://wiki.fulp.gg/index.php?title=Template:RecursiveChem/Ammonia&diff=35Template:RecursiveChem/Ammonia2025-11-08T15:24:21Z<p>Anettera: Created page with "3 parts Hydrogen<br> 1 part Nitrogen"</p>
<hr />
<div>3 parts Hydrogen<br><br />
1 part Nitrogen</div>Anetterahttps://wiki.fulp.gg/index.php?title=Template:RecursiveChem/Diethylamine&diff=34Template:RecursiveChem/Diethylamine2025-11-08T15:24:12Z<p>Anettera: Created page with "1 part {{Tooltip|Ammonia|{{RecursiveChem/Ammonia}}}}<br> 1 part Ethanol"</p>
<hr />
<div>1 part {{Tooltip|[[#Ammonia|Ammonia]]|{{RecursiveChem/Ammonia}}}}<br><br />
1 part Ethanol</div>Anetterahttps://wiki.fulp.gg/index.php?title=Template:RecursiveChem/Oil&diff=33Template:RecursiveChem/Oil2025-11-08T15:23:56Z<p>Anettera: Created page with "1 part Welding Fuel<br> 1 part Carbon<br> 1 part Hydrogen"</p>
<hr />
<div>1 part Welding Fuel<br><br />
1 part Carbon<br><br />
1 part Hydrogen</div>Anetterahttps://wiki.fulp.gg/index.php?title=Template:RecursiveChem/Acetone&diff=32Template:RecursiveChem/Acetone2025-11-08T15:23:44Z<p>Anettera: Created page with "1 part {{Tooltip|Oil|{{RecursiveChem/Oil}}}}<br> 1 part Welding Fuel<br> 1 part Oxygen"</p>
<hr />
<div>1 part {{Tooltip|[[#Oil|Oil]]|{{RecursiveChem/Oil}}}}<br><br />
1 part Welding Fuel<br><br />
1 part Oxygen</div>Anetterahttps://wiki.fulp.gg/index.php?title=Template:RecursiveChem/Epinephrine&diff=31Template:RecursiveChem/Epinephrine2025-11-08T15:23:29Z<p>Anettera: Created page with "1 part {{Tooltip|Acetone|{{RecursiveChem/Acetone}}}}<br> 1 part {{Tooltip|Diethylamine|{{RecursiveChem/Diethylamine}}}}<br> 1 part {{Tooltip|Phenol|{{RecursiveChem/Phenol}}}}<br> 1 part Chlorine<br> 1 part Hydrogen<br> 1 part Oxygen"</p>
<hr />
<div>1 part {{Tooltip|[[#Acetone|Acetone]]|{{RecursiveChem/Acetone}}}}<br><br />
1 part {{Tooltip|[[#Diethylamine|Diethylamine]]|{{RecursiveChem/Diethylamine}}}}<br><br />
1 part {{Tooltip|[[#Phenol|Phenol]]|{{RecursiveChem/Phenol}}}}<br><br />
1 part Chlorine<br><br />
1 part Hydrogen<br><br />
1 part Oxygen</div>Anetterahttps://wiki.fulp.gg/index.php?title=MediaWiki:Common.css&diff=30MediaWiki:Common.css2025-11-08T15:22:22Z<p>Anettera: </p>
<hr />
<div>/* CSS placed here will be applied to all skins */<br />
.tooltiptext {<br />
position: absolute;<br />
display: block;<br />
z-index: 2;<br />
width: 250px;<br />
padding: 10px;<br />
visibility: hidden;<br />
opacity: 0;<br />
white-space: normal;<br />
text-align: left;<br />
transition: all 0.2s;<br />
border: 1px solid #aaa;<br />
background-color: #ffdd66;<br />
}<br />
<br />
.tooltip {<br />
position: relative;<br />
}<br />
<br />
.tooltip:hover>.tooltiptext {<br />
visibility: visible;<br />
opacity: 1;<br />
}</div>Anetterahttps://wiki.fulp.gg/index.php?title=MediaWiki:Common.css&diff=29MediaWiki:Common.css2025-11-08T15:20:17Z<p>Anettera: Created page with "/* CSS placed here will be applied to all skins */ .tooltiptext { position: absolute; display: block; z-index: 2; width: 250px; padding: 10px; visibility: hidden; opacity: 0; white-space: normal; text-align: left; transition: all 0.2s; border: 1px solid #aaa; background-color: #ffdd66; } .tooltip { position: relative; }"</p>
<hr />
<div>/* CSS placed here will be applied to all skins */<br />
.tooltiptext {<br />
position: absolute;<br />
display: block;<br />
z-index: 2;<br />
width: 250px;<br />
padding: 10px;<br />
visibility: hidden;<br />
opacity: 0;<br />
white-space: normal;<br />
text-align: left;<br />
transition: all 0.2s;<br />
border: 1px solid #aaa;<br />
background-color: #ffdd66;<br />
}<br />
<br />
.tooltip {<br />
position: relative;<br />
}</div>Anetterahttps://wiki.fulp.gg/index.php?title=Template:Tooltip&diff=28Template:Tooltip2025-11-08T15:16:22Z<p>Anettera: Created page with "<span class='tooltip'>{{{1}}}<div class='tooltiptext'>{{{2}}}</div></span><noinclude>Category:Templates</noinclude>"</p>
<hr />
<div><span class='tooltip'>{{{1}}}<div class='tooltiptext'>{{{2}}}</div></span><noinclude>[[Category:Templates]]</noinclude></div>Anetterahttps://wiki.fulp.gg/index.php?title=Template:RecursiveChem/Spaceacillin&diff=27Template:RecursiveChem/Spaceacillin2025-11-08T15:16:05Z<p>Anettera: Created page with "1 part {{Tooltip|Epinephrine|{{RecursiveChem/Epinephrine}}}}<br> 1 part {{Tooltip|Cryptobiolin|{{RecursiveChem/Cryptobiolin}}}}"</p>
<hr />
<div>1 part {{Tooltip|[[#Epinephrine|Epinephrine]]|{{RecursiveChem/Epinephrine}}}}<br><br />
1 part {{Tooltip|[[#Cryptobiolin|Cryptobiolin]]|{{RecursiveChem/Cryptobiolin}}}}</div>Anetterahttps://wiki.fulp.gg/index.php?title=Template:Anchor&diff=26Template:Anchor2025-11-08T14:49:48Z<p>Anettera: </p>
<hr />
<div><onlyinclude><br />
{{#if:{{{1|}}}|<span id="{{{1}}}"></span>}}<br />
</onlyinclude><br />
<noinclude><br />
== How to use ==<br />
<pre><br />
<nowiki>{{anchor|Firesuit}}</nowiki><br />
</pre><br />
The anchor template works for making internal links to specific parts of pages. For example, linking to [[Engineering_items#Firesuit]] (Assuming you already have the anchor on the engineering items page to direct the link) will load the page focused on the firesuit. This is useful when you don't have a <nowiki>===header===</nowiki> for the item in the page.<br />
<br />
Important note though; If the page already has a header with the same name as an anchor, a link to anchored item will go to whichever is first. so if the anchor is higher than the header, it will go to the anchor and vice versa. Alternatively, you can just make the anchor have a slightly different name to fix this.<br />
<br />
[[category:templates]]<br />
</noinclude></div>Anetterahttps://wiki.fulp.gg/index.php?title=Template:Anchor&diff=25Template:Anchor2025-11-08T14:19:47Z<p>Anettera: </p>
<hr />
<div><onlyinclude>{{safesubst:<noinclude/>#invoke:Loops|forNumArgs<!--<br />
-->| template = ²{safesubst:#if:$1¦<span class="anchor" id="²{safesubst:anchorencode:$1}²"></span>}²<!--<br />
-->}}</onlyinclude><br />
<noinclude><br />
== How to use ==<br />
<pre><br />
<nowiki>{{anchor|Firesuit}}</nowiki><br />
</pre><br />
The anchor template works for making internal links to specific parts of pages. For example, linking to [[Engineering_items#Firesuit]] (Assuming you already have the anchor on the engineering items page to direct the link) will load the page focused on the firesuit. This is useful when you don't have a <nowiki>===header===</nowiki> for the item in the page.<br />
<br />
Important note though; If the page already has a header with the same name as an anchor, a link to anchored item will go to whichever is first. so if the anchor is higher than the header, it will go to the anchor and vice versa. Alternatively, you can just make the anchor have a slightly different name to fix this.<br />
<br />
[[category:templates]]<br />
</noinclude></div>Anetterahttps://wiki.fulp.gg/index.php?title=Template:Anchor&diff=24Template:Anchor2025-11-08T14:12:54Z<p>Anettera: Undo revision 23 by Anettera (talk)</p>
<hr />
<div><includeonly>{{Sandbox other||<br />
<!-- Categories below this line; interwikis at Wikidata --><br />
[[Category:Templates{{#translation:}}]]<br />
}}</includeonly><br />
<noinclude><br />
== How to use ==<br />
<pre><br />
<nowiki>{{anchor|Firesuit}}</nowiki><br />
</pre><br />
The anchor template works for making internal links to specific parts of pages. For example, linking to [[Engineering_items#Firesuit]] (Assuming you already have the anchor on the engineering items page to direct the link) will load the page focused on the firesuit. This is useful when you don't have a <nowiki>===header===</nowiki> for the item in the page.<br />
<br />
Important note though; If the page already has a header with the same name as an anchor, a link to anchored item will go to whichever is first. so if the anchor is higher than the header, it will go to the anchor and vice versa. Alternatively, you can just make the anchor have a slightly different name to fix this.<br />
<br />
[[category:templates]]<br />
</noinclude></div>Anetterahttps://wiki.fulp.gg/index.php?title=Template:Anchor&diff=23Template:Anchor2025-11-08T14:11:56Z<p>Anettera: </p>
<hr />
<div><includeonly>{{Sandbox other||<br />
<!-- Categories below this line; interwikis at Wikidata --><br />
[[Category:Templates{{#translation:}}]]<br />
}}</includeonly><br />
<br />
== How to use ==<br />
<pre><br />
<nowiki>{{anchor|Firesuit}}</nowiki><br />
</pre><br />
The anchor template works for making internal links to specific parts of pages. For example, linking to [[Engineering_items#Firesuit]] (Assuming you already have the anchor on the engineering items page to direct the link) will load the page focused on the firesuit. This is useful when you don't have a <nowiki>===header===</nowiki> for the item in the page.<br />
<br />
Important note though; If the page already has a header with the same name as an anchor, a link to anchored item will go to whichever is first. so if the anchor is higher than the header, it will go to the anchor and vice versa. Alternatively, you can just make the anchor have a slightly different name to fix this.<br />
<br />
[[category:templates]]</div>Anetterahttps://wiki.fulp.gg/index.php?title=Guide_to_food&diff=22Guide to food2025-11-07T22:57:37Z<p>Anettera: </p>
<hr />
<div>[[tgstation:Guide_to_food|Guide to food on tgstation wiki]]<br />
<br />
[[tgstation:Guide_to_food#Icecream_Vat|Guide to ice cream on tgstation wiki]]</div>Anetterahttps://wiki.fulp.gg/index.php?title=Guide_to_food&diff=21Guide to food2025-11-07T22:55:29Z<p>Anettera: Created page with "Guide to food on tgstation wiki"</p>
<hr />
<div>[[tgstation:Guide_to_food|Guide to food on tgstation wiki]]</div>Anetterahttps://wiki.fulp.gg/index.php?title=Main_Page&diff=20Main Page2025-11-07T20:14:38Z<p>Anettera: </p>
<hr />
<div>This is the wiki for Fulpstation, a custom fork of the /tg/station flavoured fork of Space Station 13.<br />
<br />
<big>'''This wiki is new and under heavy construction. Anything can change at any time, and you should expect issues.'''</big> <br />
<br />
<br />
Most things listed here are Fulpstation-Unique, and the tgstation wiki should be used for everything else.<br />
<br />
* Our Repository: https://github.com/fulpstation/fulpstation<br />
* tgstation's Repository: https://github.com/tgstation/tgstation<br />
* Forum: https://forum.fulp.gg<br />
* Discord: https://discord.gg/dSw5nqgDye<br />
* tgstation's Wiki: https://wiki.tgstation13.org<br />
* Map viewer: https://webmap.affectedarc07.co.uk<br />
<br />
Space Station 13 is a paranoia-laden round-based roleplaying game set against the backdrop of a nonsensical, metal death trap masquerading as a space station, with charming spritework designed to represent the sci-fi setting and its dangerous undertones. Have fun, and survive!</div>Anetterahttps://wiki.fulp.gg/index.php?title=Server_Rules&diff=19Server Rules2025-11-07T19:54:04Z<p>Anettera: </p>
<hr />
<div>For more in-depth explanations of rules and FAQ, please read the Rule precedents document<br />
<br />
== Core Rules ==<br />
# Take these rules as they are to be intended and not as they are written literally.<br />
## Rule skirting, lawyering, and/or being a dick for the sake of ruining others' experiences can become a bannable offense if occurring regularly.<br />
# Fulpstation is a Medium Roleplay server. We define this as performing your assigned duties. This is a ‘do your job’ server. This means it is important to do what is expected out of your department and not what would be expected out of other departments.<br />
## If you want to build mechs, play roboticists. If you want to hunt for antags and uphold space law, play security. This is to ensure all players can have a fun shift and have a role to fill. This is not intended to limit what is possible on the server but to provide structure for everyone.<br />
## Opt-in for roles you intend to play or seek an IC way to change your job. Failure to attempt to do the most basic of duties for your role may result in a job ban. [A list of basic duties can be found here]. While transferring to another department and doing another job is acceptable, being a know it all for multiple departments is not.<br />
## If you do not wish to be a role or antag, ensure you set it to never in your occupation preferences and/or request a ban from said role or antag. Changing your job preference settings to “return to lobby if preferences unavailable” will prevent you from being assigned a random position.<br />
## Players' knowledge of the game is not limited by their job. However, using knowledge of antags and round types without IC justification is considered metagaming. For example, it is acceptable for a clown to know how to build a conveyor belt for a prank. It is not acceptable for a clown to know that xenomorphs are weak to fire and rush to make a flamethrower.<br />
# Malicious acts like griefing, metagaming, killbaiting, banbaiting, powergaming, self-antagging, greytiding, validhunting (along with calling people and silicons valid without proper cause), and exploiting can become bannable offenses if occurring regularly or if the infraction is serious enough.[See the glossary here].<br />
## Multi keying, ban evasion, cheating, blatant intent to grief, and RDMing are all permanent ban offenses.<br />
## If playing with someone that is at the same location as you, alert us so we may take note of it. Otherwise, we may assume they are you.<br />
## Antag rolling, or round-start suicides that appear to be antag rolling, may result in an antag ban if occurring frequently enough<br />
# Sexual content is strictly prohibited. This includes content like photos/websites/Erotic Role Play (ERP) and applies to the server, Discord, and forums. Sending unsolicited sexual content to another player via direct messages will also result in a ban.<br />
# Hate speech is strictly forbidden. Using the Discord, the SS13 server, or the forums to threaten a group of people or to propagate racial and otherwise prejudiced slurs or stereotypes is a bannable offense. We take this seriously and want to create a server that is welcoming to all people. This includes variations or misspellings of slurs. SS13 is your character’s workplace; if you would get fired for saying it in a modern-day office setting, you shouldn’t be saying it on the server.<br />
# Discrimination towards in-game sub-species and silicons is acceptable in moderation, but attacking them or otherwise preventing them from playing the round is not. Additionally, terms that are based on real-life slurs are not allowed.<br />
# Do not spam, advertise, or paste lengthy and/or inappropriate copypastas.<br />
# Keep IC content in IC, and OOC content in OOC. This means no IC in OOC (ick ock) and vice versa.<br />
# Revealing information about the current round in OOC, Discord, or the forums (metacomming) is strictly prohibited. Wait until after the Round End screen to discuss the round or file a report.<br />
# Avoid antagonizing players and staff via the Discord, Forums, or through OOC/deadchat. While expressing frustration about in-round events is acceptable, ganging up on fellow players is not.<br />
## IC insults are fine within reason, but harassing other players repeatedly throughout the round or using OOC insults IC is not.<br />
# Each round exists independently of all other rounds. While friendships persisting through rounds is okay, using experiences from other rounds to give an advantage or disadvantage to other players is not permitted.<br />
<br />
== Returning From The Afterlife ==<br />
# Do not use information obtained while dead or from a previous life upon returning to the land of the living.<br />
# Cyborgs and other creatures that are created with a character’s organic brain (i.e. not a positronic brain) retain all knowledge of events that happened before the procedure while they were living. Rule 1 still applies to information obtained while dead.<br />
## Antagonists who undergo forced cyborgization retain their antag status and objectives but must prioritize their law set. This prevents borgs from attempting to be unborged in most circumstances.<br />
== SSD/AFK Player Interactions ==<br />
Note: SSD characters are players who are disconnected or AFK. It is possible for players to return to SSD bodies. Players become catatonic when they take a ghost spawner role or commit suicide. Players are NOT able to return to these bodies without admin intervention.<br />
# Do your best not to interact negatively with SSD/AFK players. Moving them to safety is acceptable, but killing, looting, or otherwise griefing them while they are away is not.<br />
## If the player in question is an antag’s target or they are being secured by security, interactions to finish what is required of your duties/objectives are always acceptable.<br />
## Ahelping about an SSD/AFK player may grant an exception to this rule.<br />
# Rule 1 does not apply to players that are catatonic. Although needlessly killing or harming catatonic players is discouraged (and will probably get you hunted by security), harvesting their organs to save another player is acceptable.<br />
<br />
== Escalation Clause ==<br />
# Escalation resulting in murder is only acceptable within reason. If your life is in danger, you can always fight back lethally, or if a conflict with the other player has lasted throughout the round with multiple fights. In most cases, fights end when one party enters critical condition or is otherwise incapacitated. Theft, break-ins, demotions, destruction of property, getting pranked and other inconveniences are not reasons to murder another player or put them into a life or death situation. Ask what a rational person would do and act accordingly.<br />
## Expect to receive the same kind of treatment and escalation that you give out.<br />
## If the other party during an altercation dies or is seriously injured, work to get them healed or revived.<br />
# If you act like an antagonist, expect to be treated like one and be held liable for your actions both IC and by admins.<br />
# Over-escalation of fights is also unacceptable. Over-escalation is, in short, doing more damage to someone than is required to resolve an issue or using violence instead of words to solve an issue. <br>Examples: <br />
##Killing someone during a dangerous fight when they could be placed into crit and healed or ignoring the opportunity to use non-lethal force when available.<br />
##Placing someone someplace they will surely die, like disposals when crit, space, in shuttle landing zones, or other gibbers.<br />
##Delimbing someone for doing minimal damage to you.<br />
##Breaking into a department and attacking someone when they try to remove you from the department instead of asking for what is needed.<br />
# While using lethal force is allowed in some cases of self-defense, actions that jeopardize the lives of other players or could cause massive damage to the station (e.g. max caps) is considered over escalation, and you will be held accountable for deaths that occur due to negligent behavior. This rule applies when committing acts that will likely cause mass casualties to eliminate antagonists.<br />
<br />
== Command/Security/Silicon Responsibilities ==<br />
# The following jobs: Captain, HOP, HOS, CE, RD, CMO, QM, and AI should ahelp when they need to leave. This is to ensure a replacement can be installed (Your body will be offered to ghosts or your character will be deleted and the job slot reopened) for continuity of the round. Your intent to leave should also be made known to other command staff if possible. If no staff are available to offer your body to ghosts, you should designate another player as your replacement after ahelping.<br />
## These roles must exhibit some competency. Lack of this can result in a job ban. Command roles are designed to lead and manage departments first and do second. They are not intended to become do-it-all members of their departments.<br />
## Crew promoted to acting heads of staff must step down when an official head of staff arrives at the station. This is to prevent confusion with the chain of command when the new player arrives.<br />
# In the absence of a captain and CentCom appointed acting captain, the Head of Personnel or Head of Security must serve as acting captain or split the duties of the captain between themselves. In the absence of a captain and CentCom appointed acting captain, HoP, and HoS, the other command staff have equal standing in determining a new acting captain among themselves.<br />
## Only command staff may serve as acting captain. Acting departmental heads and regular crew may not serve as acting captain.<br />
## The only item acting heads may take from the head’s office is the command headset. Unless there is a dire emergency, no other items should be removed by non-antags.<br />
## An acting captain may fill in for decisions that require the captain’s authorization, but may not run the station and its departments, nor are they privy to the captain's equipment or access outside of the command headset and nuke disk. The captain’s spare ID can be used to run the HoP line in the case of a non-HoP acting captain but should not leave the bridge.<br />
# Heads of staff, acting heads of staff, and security should not abandon the station without permission from CentCom. This includes going to Lavaland, space exploration, bitrunning, and entering the gateway.<br />
# We adhere to our own version of [space law].<br />
## While the majority of this is a guideline, we expect things to be applied reasonably. Giving someone a ten-minute brig timer for slipping the captain is an example of things not being applied reasonably.<br />
## Abusing crew as security is never acceptable.<br />
## Authorization for permanent punishments (including executions) should only be followed if the authorization was given by the correct authority. For example, a sec officer should not comply with execution orders given by an HoS when a captain is abroad the station.<br />
## Security must use nonlethal force unless there is reasonable suspicion that the other party is armed (e.g. breaking into the armory), lethal force is used upon them, or the use of nonlethal force is impossible (e.g. Hulks). See “Use of Deadly Force” under Space Law for more information.<br />
## Ensuring prisoners receive timely revival and proper medical care is the responsibility of everyone in the security team. Unless an execution was authorized by the captain, this applies to any player killed by security. Detaining players who are dead or will likely die from injuries without attempting to provide medical care (e.g. throwing a prisoner in critical condition in a cell) is a violation of 4.2. See “Prisoner Medical Care” in Space law for more information. Repeated negligent deaths may result in a role ban.<br />
# We adhere to our own version of [silicon and drone] policy.<br />
## Those that upload laws to silicons are responsible for what said law causes.<br />
## Ordering silicons to commit suicide or any actions that would be considered grief as a non-antag is strictly prohibited. Silicons who are given such orders should ahelp before carrying them out; however, the person giving the command will still be held responsible.<br />
# We now adhere to our own [standard operating procedure] policy.<br />
## Calling the shuttle on red alert to end the round faster despite there being no significant threats to the station will likely result in it being recalled.<br />
== Antagonist/Lavaland/Ghost Policy ==<br />
# Antagonists exist to move the round forward and make things interesting and fun for everyone involved. Excessively recalling the shuttle to prevent the natural end of the round in order to do your objectives should be avoided and may result in moderator intervention. If you complete your objectives, you may pray to be given additional objectives.<br />
## Do not needlessly kill those you do not need to outside of your objectives and simply because you can. This includes destroying silicons. Things like covering up evidence, dealing with pursuing security officers, ‘Good Samaritans’ on your tail, and removing a witness, are always acceptable examples. Ahelping ideas for gimmicks may grant an exception to this.<br />
## Killing players outside of rule 1.1 must directly further your goal, and you cannot permanently remove these players from the round. For example, killing an engineer to gain departmental access with the objective to steal the CE’s blueprints is acceptable. Killing an engineer for her insulated gloves or access to the prolathe without an objective in that department is not.<br />
## Do not spawn camp or prevent others from entering the round safely.<br />
## Do what is needed for your goals. Destroying half the station when you only need to steal research is an example of going extremely overboard. Causing chaos in a department with a bomb is okay but destroying half the station is not<br />
## Team antag objectives take precedent over solo antag objectives.<br />
# If you become an antagonist and do not wish to be one, ahelp so that we may set you up with another role and/or give your antagonist status to another player.<br />
# Creatures and those turned into creatures maintain their antag status from their previous form. See the “Returning from the Afterlife” section for more information.<br />
# Ghost spawner roles must follow their flavor text upon taking said role. These roles are meant to allow players to return to the game, and their slots are usually limited. Intentionally wasting spawner slots (e.g. repeatedly suiciding as spawner roles during one round) may result in a ghost role ban.<br />
# Sentient animals, critters, and creatures are not valid to be killed by the crew simply for existing -- they are players too. However, if they are causing trouble, this protection is waived.<br />
# Lavaland spawner roles (such as Ashwalkers and Free Golems) are meant to allow players to return to the game and are only considered valid if aggressive toward crewmembers. See the “Guide on acceptable killing” section at the end of this document.<br />
## Lavaland spawners who enter the station must be peaceful and are held to stricter standards for escalation and roleplay than when on Lavaland. Spawners may not use meta knowledge to seek out the Lavaland mining base and may only enter if invited by crew members. Spawners who are hostile/ willingly impede the station are subject to a ghost role ban.<br />
## Spawner roles must follow their flavor text and treat their spawn location (e.g. Charlie station) with the same regard as the main station. Intentionally destroying your spawn location without sufficient IC reason prevents players from rejoining the game and will result in a ghost role ban.<br />
# Rules 6 and 6.1 do NOT apply to any Syndicate spawners. These roles are permitted to kill Nanotrasen crew members on sight and similarly may be killed by NT crew. <br />
## Spawners at the Syndicate base in Lavaland are never permitted to leave their base.<br />
## Spawners at the Syndicate ship are allowed to leave their base but must not seek out the Nanotrasen station. These spawners are never permitted to intentionally approach or board the NT station. If you accidentally find the NT station you are expected to leave immediately.<br />
# If you disconnect as an antagonist, we will be forced to offer your body to ghosted players after ten minutes without reconnecting. Members of team antagonists (e.g. nuclear/clown operatives, blood brothers, head revolutionaries) must notify admins that they are leaving through ahelps.<br />
<br />
== Admin Interactions ==<br />
# Our staff is composed entirely of volunteers who work to make Fulp a welcoming community to all players. While it’s okay to express frustration with admin interactions, doing so in a way that is aggressive or harassing will result in a mute or a ban. If you harass staff, expect consequences to come as a result of your actions or your issue to be discarded.<br />
## Do not send unsolicited Direct Messages to staff via Byond. If you need to contact staff, verify on Discord and use the #ask-mods channel or the forums. Sending unsolicited DMs via Byond may result in a permaban.<br />
# Ahelp as soon as possible. Waiting can make things harder or even impossible to look into. We do not know what we do not see. The moderation team exists to help. Ahelping can bring things to our attention we may miss.<br />
# Provide as many details as possible. Generally, your ahelp should include the name of the offending character and a brief description of what happened. This makes it easier for us to figure out an issue.<br>Bad ahelp: Sec arrested me for no reason<br>Good ahelp: Sec officer John Smith put me in a cell with no timer for trespassing into science, and I’ve been here for 5 minutes already.<br />
# While players are encouraged to ahelp problems they have in-round, misusing ahelps (e.g. complaining about round or asking to be an antag) is not acceptable. If your ticket is rejected or marked IC and you wish to have it reviewed, file a staff report on the forums as additional tickets regarding the same issue will be ignored. Misusing ahelps clutters tickets, and repeatedly doing so may result in notes or a ban.<br />
# Do not lie in ahelps as we can verify any claims made via player logs. If you are unsure of how an event transpired, you are encouraged to look through your logs for verification. Lying in ahelps will result in a ban.<br />
# Respond to Admin PMs as soon as possible so we know you aren’t ignoring the ticket. Even a ‘one moment’ will suffice.<br />
# In-character communication with admins should be done through the prayer option under the IC tab. Prayer can be used to obtain in-game items at the admin’s discretion. This includes TC trades. Ahelps should not be used in place of prayers for IC issues. Praying does not guarantee a response and may result in being smited. Spamming prayers may result in a mute/smiting. Do not ahelp if your prayer is not answered.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Admin interaction !! Event<br />
|-<br />
| Ahelp || Other players breaking the rules (e.g. suspected self-antag, IC in OOC, hate speech, theft of dept equipment, etc.), reporting a bug/ glitches, leaving as a dept head, asking for antag status to be removed, confirming rules about large-scale antag actions<br />
|-<br />
| Mhelp || Asking about game mechanics<br />
|-<br />
| Prayer || TC trades, requesting items, asking for antag status when not already an antag, asking for additional objectives<br />
|-<br />
| Forum Post || Reporting other players when no admins are online, ban appeals<br />
|}<br />
<br />
== Glossary of Malicious Acts and Examples ==<br />
Ban Baiting: Actions/communication that bait staff into banning others. <br />
<br />
This also applies to tricking other players into doing things that would get them banned e.g. telling a new chemist to make a potassium water bomb<br />
<br />
Griefing: Deliberate actions that interfere with/antagonize other players or will take serious effort and time from other players to fix and/or repair.<br />
<br />
Stacking numerous small acts also applies here. <br />
<br />
If the combination of all that you are going to do will take more than ten minutes to repair or replace, you probably should not do it regardless of if it's ‘just a prank’. This includes things like infinite disposals loops.<br />
<br />
Obvious things like floor pills, conveyor belts leading out an airlock, mazes, and other inconveniences do not count as grief, as long as their intentions are not mislabeled or hidden. Like dangerous floor pills being labeled, ‘brute damage pill’.<br />
<br />
Losing is part of the game and does not always equal being griefed. Excessive complaints about IC deaths may result in a deadchat/ OOC mute.<br />
<br />
Examples of grief include:<br />
<br />
Dismantling important machinery like Cryo Tubes or disabling the gravity generator.<br />
Trapping other players in lockers/rooms while stealing their ID and other unique items.<br />
Removing other players limbs, drugging, or poisoning them needlessly, or removal of unique items like heirlooms.<br />
Venting the station to space or blocking off areas of the station.<br />
Pushing players out of the airlocks on the shuttle<br />
Greytiding: Consistent and deliberate low-level IC crimes used for personal advantages or gimmicks that spark conflict with others.<br />
<br />
Stealing items or equipment from departments.<br />
Hacking/trespassing into places that you do not have access.<br />
Starting/joining fights that you have no reason to.<br />
<br />
Kill Baiting: Baiting others into harming or killing you to escalate an issue, or baiting them into escalation so that you may kill them.<br />
<br />
This counts as an over-escalation of an issue. Fights and normally escalated fights are fine however.<br />
<br />
Meta Gaming/ Meta Knowledge: The use of out of character knowledge or game mechanics to have an advantage in-game. <br />
<br />
Examples of this could be:<br />
<br />
Knowing about stealth traitor uplink gear (e.g. sleepy pens) as a non-antag.<br />
This rule does not apply to non-stealth items such as e-swords<br />
Hiding traitor objective items and other sensitive materials at round start without confirmation of antagonists on the station looking for these items.<br />
Noticing a character is acting differently than normal and acting on it as them being an antag.<br />
Metagrudging against players and meta communicating.<br />
Using discovered knowledge of round type to assume the existence of additional antagonists, this includes expecting exact numbers of antags.<br />
Going into maint and checking for maint walls to check for Bloodsucker lairs when you aren't security.<br />
Changing the access of doors or bunkering departments without sufficient IC reasons. This includes building vault doors or turrets.<br />
Multi Keying: Using multiple accounts/clients to play the game during the course of a round. This will result in the newer account(s) being permanently banned and any and all notes being transferred to the older account.<br />
<br />
Power Gaming: Obtaining items/power or doing things outside of the scope of your department or skill range to have a greater advantage. More often than not this is playing to ‘win’, whether it be at a certain mechanic, game mode or anything else. This includes giving others no room or ability to act or ‘win’ themselves. These rules are relaxed for players with antag status.<br />
<br />
Examples of this are: <br />
<br />
Breaking in and taking your head of staff’s gear.<br />
A Head of Personnel giving themselves security access.<br />
Replacing the brig windows with walls at round start.<br />
Building an exosuit fabricator as an engineer to make yourself a mech.<br />
Circumventing access restrictions via hacking or using stolen/looted IDs.<br />
Removing your mindshield or asking others to remove your mindshield.<br />
RDMing (Random Death Match): Killing or attempting to kill multiple other players without proper cause or reason.<br />
<br />
Self Antagging: Acting as an enemy of the station when not one, i.e. making yourself ‘valid’. More often than not, these are capital crimes. If it's something only an antag would reasonably do- like bombing a department - don’t do it.<br />
<br />
Valid Hunting: Searching for / preparing for / dealing with antagonists and criminals without a need or duty to do so. This includes having the intention of eliminating them as a threat to the station. Note that this refers specifically to the illegitimate targeting of antags and does not include scenarios listed as acceptable in the Guide of Acceptable Antag Killing (e.g. you can’t validhunt a nukie because they are always an acceptable target for all crewmembers).<br />
<br />
Being a vigilante within reason is acceptable here such as helping someone getting attacked by another player. If it involves going out of your way to do so though, it's probably going too far.<br />
<br />
Examples of this are:<br />
<br />
As an engineer, creating a tesla death trap for those that may break-in.<br />
As an assistant, stealing a baton and wandering maint because they expect antagonists to be there.<br />
As a miner, attacking a suspected changeling who is not actively harming anyone.<br />
Attacking or ‘jumping at’ a fellow player simply for having an item an antag would. An example being a chaplain/scientist having a dark blessing/a xeno-biology arm blade or a known space explorer having contraband.<br />
<br />
== Guides on acceptable killing ==<br />
Note: While this guide applies for most scenarios, there is some flexibility on who you can kill so long as it directly furthers your objectives. However, it is generally advised that you ahelp before killing a player that does not fall under these categories. Rule lawyering kills based on the flexibility of this rule will result in your argument being disregarded.<br />
<br />
Highlighted entries denote roles that may cause large scale damage to the station WITHOUT admin approval. For all others, please refer to Antag rule 1.4 <br />
<br />
{| class="wikitable"<br />
|-<br />
! Role !! Who you can kill !! Who you can permanently remove<br />
|-<br />
| Any antag with hijack objective || Anyone once the shuttle has been called at any alert level || Anyone once the shuttle has been called at any alert level<br />
|-<br />
| Abductor || Self-defense only || None<br />
|-<br />
| Ashwalkers || Any non-ashwalker at lavaland wastes || Any non-ashwalker at lavaland wastes<br />
|-<br />
| Bloodsucker || Pursuing security officers, witnesses, valid hunters, anyone if it is in line with objectives (e.g. blood consumption, hearts)*<br />
<br />
''Note: Plasma men do not have blood and should not be killed for feedings'' <br />
|| None<br />
|-<br />
| Blood Brother/ Traitor WITHOUT hijack, other round-ending objectives die a glorious death, or round-ending final objectives || Your target, pursuing security officers, witnesses, valid hunters, people protecting items for steal objectives(e.g. killing the captain for the nuke disk) || Your target(s)<br />
|-<br />
| Changeling|| Your target, pursuing security officers, witnesses, valid hunters, anyone if it's in line with objectives (e.g. killing other lings to obtain the most DNA points)* || Your target(s)<br />
|-<br />
| Cultist || Mindshielded crew, self-defense || Mindshielded crew<br />
|-<br />
| Die a glorious death objective || Anyone as long as you die as a result. If you are planning something impactful, ahelp to let the admins know ahead of time (e.g. clown car into sm is fine while murdering unarmed crew members is not) || Anyone as long as you die as a result<br />
|-<br />
| Heretic || <br />
* Before ascension: Sacrifice/ objective targets, pursuing security officers, witnesses, valid hunters<br />
* After ascension: Anyone <br />
|| <br />
* Before ascension: None<br />
* After ascension: Anyone<br />
|-<br />
| (Syndicate) Infiltrator || Before full completion: Your target, pursuing security officers, witnesses, valid hunters, people protecting items for steal objectives.<br />
<br />
After last objective: See Die a glorious death or Hijack acceptable killing depending on which one you receive. <br />
|| Before full completion: Your target(s)<br />
<br />
After last objective: See Die a glorious death or Hijack acceptable killing depending on which one you receive.<br />
|-<br />
| Malf AI WITH hijack objectives || Anyone except borgs slaved to you || Anyone except borgs slaved to you<br />
|-<br />
| Malf AI WITHOUT hijack objectives || Your target(s), anyone breaking into your satellite to card you || Your target(s). A malf AI should not use Doomsday without an appropriate objective.<br />
|-<br />
| Miners || Megafauna, aggressive ashwalkers, self-defense <br />
<br />
Lavaland gear should NOT be used on the station to validhunt or as a non-antag <br />
|| None<br />
|-<br />
| Monster Hunter || Targets, Self-defense <br />
|| Before ascension: Targets<br />
After ascension: Anyone<br />
|-<br />
| Nightmare || Anyone || Anyone<br />
|-<br />
| Ninja || Anyone as long as it is in line with objectives || Anyone as long as it is in line with objectives<br />
|-<br />
| Nuclear or Clown Operatives || Anyone except other operatives || Anyone except other operatives<br />
|-<br />
| Obsessed || Your targets, pursuing security members, witnesses, valid hunters || Your target(s)<br />
|-<br />
| Paradox Clone || Your target, witnesses, pursuing security members || Your target<br />
|-<br />
| Prisoner || Self-defense only. Prisoners are not antags on Fulp || None<br />
|-<br />
| Pirate || Security, self-defense || None<br />
|-<br />
| Revenant || Anyone for soul consumption || Anyone for soul consumption<br />
|-<br />
| Revolutionary || Department heads, Mindshielded crew (including security), self-defense || Department heads, security<br />
|-<br />
| Security || Self-defense, nuclear/clown operatives, criminals who have committed capital crimes AFTER captain approval or a trial, criminals that are too dangerous to detain non lethally || Nuclear/clown operatives, Criminals who have committed capital crimes AFTER captain approval or a trial<br />
|-<br />
| Sentient Disease || Anyone || Anyone<br />
|-<br />
| Sentience Spawns/ Slaved Golems || Anyone you are instructed to kill by your creator; otherwise, regular escalation rules apply || Anyone you are instructed to kill by your creator<br />
|-<br />
| Slaughter/ Laughter demon || Anyone || Anyone <br />
|-<br />
| Space Dragon || Anyone || Anyone <br />
|-<br />
| Spy || Your target, pursuing security officers, witnesses, valid hunters, people protecting items for steal objectives(e.g. killing the captain for the nuke disk) || Targets<br />
<br />
Mass destruction (even when it results in round removal of non-targets) is acceptable within the scope of your objective (not spy bounties). Starting a plasma fire in medbay would be acceptable for the objective “Ensure medbay is engulfed in flames”, but starting a station-wide plasma fire would not.<br />
|-<br />
| Wizard || Anyone || Anyone <br />
|-<br />
| Xenomorphs|| Anyone || Anyone <br />
|}<br />
* Rules on killbaiting and RDM still apply for these roles. Going out of your way to kill or round remove players without sufficient reason will still result in an antag ban<br />
<br />
<br />
== Guide on acceptable antag killing ==<br />
Note: This guide applies to most scenarios, and very few situations exist where crew members aside from security (as well as silicons and chaplains with proper IC justification) should intentionally seek out antags. This guide is not meant as a replacement of the above rules. Self-defense and other justifications still apply. If you have any questions in-round you are encouraged to ahelp before taking action<br />
<br />
{| class="wikitable"<br />
|-<br />
! Antag type !! Can the crew kill it?<br />
|-<br />
| Any antag attempting to hijack the shuttle || Yes<br />
|-<br />
| Abductor || No<br />
|-<br />
| Blob || Yes<br />
|-<br />
| Bloodsucker || Crew should not actively seek out or prepare for bloodsuckers, but confirmed bloodsuckers can be round removed by crew if caught while behaving aggressively<br />
|-<br />
| Changeling || Crew should not actively seek out or prepare for changelings but confirmed changelings can be round removed by crew if caught while behaving aggressively<br />
|-<br />
| Cultist || Only AFTER the cult has been revealed (Pentagrams appear above cultists’ heads or ritual has begun)<br />
|-<br />
| Escaped prisoners || No (prisoners are not valid on Fulp)<br />
|-<br />
| Heretics || <br />
* Before ascension: No<br />
* After ascension: Yes<br />
|-<br />
| Malf AI/ Traitor/ Blood Brother WITHOUT hijack objectives || No<br />
|-<br />
| Malf AI/ Traitor/ Blood Brother WITH hijack or other round-ending objective || Only AFTER they start acting on this objective<br />
|-<br />
| Monster Hunter || Before ascension: No<br />
After ascension: Yes<br />
|-<br />
| Nightmare|| Yes<br />
|-<br />
| Ninja || Yes<br />
|-<br />
| Nuclear/ Clown Operatives || Yes<br />
|-<br />
| Obsessed || No<br />
|-<br />
| Pirate || Yes<br />
|-<br />
| Paradox Clone || No (except the cloning target)<br />
|-<br />
| Revenant || Yes<br />
|-<br />
| Revolutionary || No<br />
|-<br />
| Slaughter/ Laughter demon || Yes<br />
|-<br />
| Spy || No, unless immediately engaged in something that would reasonably cause mass destruction (e.g., bombing a department)<br />
|-<br />
| Wizard || Yes<br />
|-<br />
| Xenomorph|| Yes<br />
|}</div>Anetterahttps://wiki.fulp.gg/index.php?title=Template:Anchor&diff=18Template:Anchor2025-11-07T18:30:26Z<p>Anettera: Created page with "{{#if:{{{1|}}}|<span id="{{{1|}}}"></span>}}<noinclude> == How to use == <pre> <nowiki>{{anchor|Firesuit}}</nowiki> </pre> The anchor template works for making internal links to specific parts of pages. For example, linking to Engineering_items#Firesuit (Assuming you already have the anchor on the engineering items page to direct the link) will load the page focused on the firesuit. This is useful when you don't have a <nowiki>===header===</nowiki> for the item in th..."</p>
<hr />
<div>{{#if:{{{1|}}}|<span id="{{{1|}}}"></span>}}<noinclude><br />
== How to use ==<br />
<pre><br />
<nowiki>{{anchor|Firesuit}}</nowiki><br />
</pre><br />
The anchor template works for making internal links to specific parts of pages. For example, linking to [[Engineering_items#Firesuit]] (Assuming you already have the anchor on the engineering items page to direct the link) will load the page focused on the firesuit. This is useful when you don't have a <nowiki>===header===</nowiki> for the item in the page.<br />
<br />
Important note though; If the page already has a header with the same name as an anchor, a link to anchored item will go to whichever is first. so if the anchor is higher than the header, it will go to the anchor and vice versa. Alternatively, you can just make the anchor have a slightly different name to fix this.<br />
<br />
[[category:templates]]<br />
</noinclude></div>Anetterahttps://wiki.fulp.gg/index.php?title=Chems&diff=17Chems2025-11-07T18:24:08Z<p>Anettera: Created page with "{| class="wikitable sortable" style="width:100%; text-align:left; border: 3px solid #FFDD66; cellspacing=0; cellpadding=2; background-color:white;" ! scope="col" style='width:150px; background-color:#FFDD66;'|Name ! scope="col" class="unsortable" style='background-color:#FFDD66;'|Formula ! scope="col" class="unsortable" style='background-color:#FFDD66; width:170px;'|Reaction conditions ! scope="col" class="unsortable" style='background-color:#FFDD66;'|Description ! scope..."</p>
<hr />
<div>{| class="wikitable sortable" style="width:100%; text-align:left; border: 3px solid #FFDD66; cellspacing=0; cellpadding=2; background-color:white;"<br />
! scope="col" style='width:150px; background-color:#FFDD66;'|Name<br />
! scope="col" class="unsortable" style='background-color:#FFDD66;'|Formula<br />
! scope="col" class="unsortable" style='background-color:#FFDD66; width:170px;'|Reaction conditions<br />
! scope="col" class="unsortable" style='background-color:#FFDD66;'|Description<br />
! scope="col" class="unsortable" style='background-color:#FFDD66;'|Chemical properties<br />
|-<br />
<br />
!style='background-color:#FFEE88;'|{{anchor|Spaceacillin}}Spaceacillin<span style="color:#E1F2E6;background-color:white">▮</span><br />
<br>Inverse: [[#Sepsisillin|Sepsisillin]] <30%<br />
<br>pH: 8.1<span style="color:#23b36e;background-color:white">▮</span><br />
|{{RecursiveChem/Spaceacillin}}<br />
|<b>Min temp:</b> 100K<br />
<br><b>Overheat:</b> 900K<br />
<br><b>Optimal pH:</b> 5 to 10<br />
<br><b>Unstable purity:</b> <10%<br />
<br>Weakly Exothermic<br />
<br>H+ producing<br />
|Spaceacillin will provide limited resistance against disease and parasites. Also reduces infection in serious burns.<br />
|<b>Rate:</b> 0.04u/tick<br />
<br><b>Unreacted purity:</b> 100%<br />
|-<br />
|}</div>Anetterahttps://wiki.fulp.gg/index.php?title=Main_Page&diff=16Main Page2025-11-07T17:52:38Z<p>Anettera: </p>
<hr />
<div>This is the wiki for Fulpstation, a custom fork of the /tg/station flavoured fork of Space Station 13.<br />
<br />
<big>'''This wiki is new and under heavy construction. Anything can change at any time, and you should expect issues.'''</big> <br />
<br />
<br />
Most things listed here are Fulpstation-Unique, and the TGstation wiki should be used for everything else.<br />
<br />
* Our Repository: https://github.com/fulpstation/fulpstation<br />
* tgstation's Repository: https://github.com/tgstation/tgstation<br />
* Forum: https://forum.fulp.gg<br />
* Discord: https://discord.gg/dSw5nqgDye<br />
* tgstation's Wiki: https://wiki.tgstation13.org<br />
* Map viewer: https://webmap.affectedarc07.co.uk<br />
<br />
Space Station 13 is a paranoia-laden round-based roleplaying game set against the backdrop of a nonsensical, metal death trap masquerading as a space station, with charming spritework designed to represent the sci-fi setting and its dangerous undertones. Have fun, and survive!</div>Anetterahttps://wiki.fulp.gg/index.php?title=Main_Page&diff=15Main Page2025-11-07T17:52:03Z<p>Anettera: </p>
<hr />
<div>This is the wiki for Fulpstation, a custom fork of the /tg/station flavoured fork of Space Station 13.<br />
<br />
=== '''This wiki is new and under heavy construction. Anything can change at any time, and you should expect issues.''' ===<br />
<br />
<br />
Most things listed here are Fulpstation-Unique, and the TGstation wiki should be used for everything else.<br />
<br />
* Our Repository: https://github.com/fulpstation/fulpstation<br />
* tgstation's Repository: https://github.com/tgstation/tgstation<br />
* Forum: https://forum.fulp.gg<br />
* Discord: https://discord.gg/dSw5nqgDye<br />
* tgstation's Wiki: https://wiki.tgstation13.org<br />
* Map viewer: https://webmap.affectedarc07.co.uk<br />
<br />
Space Station 13 is a paranoia-laden round-based roleplaying game set against the backdrop of a nonsensical, metal death trap masquerading as a space station, with charming spritework designed to represent the sci-fi setting and its dangerous undertones. Have fun, and survive!</div>Anetterahttps://wiki.fulp.gg/index.php?title=Main_Page&diff=14Main Page2025-11-07T17:51:25Z<p>Anettera: </p>
<hr />
<div>This is the wiki for Fulpstation, a custom fork of the /tg/station flavoured fork of Space Station 13.<br />
This wiki is new and under heavy construction. Anything can change at any time, and you should expect issues.<br />
<br />
Most things listed here are Fulpstation-Unique, and the TGstation wiki should be used for everything else.<br />
<br />
* Our Repository: https://github.com/fulpstation/fulpstation<br />
* tgstation's Repository: https://github.com/tgstation/tgstation<br />
* Forum: https://forum.fulp.gg<br />
* Discord: https://discord.gg/dSw5nqgDye<br />
* tgstation's Wiki: https://wiki.tgstation13.org<br />
* Map viewer: https://webmap.affectedarc07.co.uk<br />
<br />
Space Station 13 is a paranoia-laden round-based roleplaying game set against the backdrop of a nonsensical, metal death trap masquerading as a space station, with charming spritework designed to represent the sci-fi setting and its dangerous undertones. Have fun, and survive!</div>Anetterahttps://wiki.fulp.gg/index.php?title=File:Beefmanfavicon.png&diff=13File:Beefmanfavicon.png2025-11-07T15:20:34Z<p>Anettera: tiny beefman</p>
<hr />
<div>== Summary ==<br />
tiny beefman</div>Anetterahttps://wiki.fulp.gg/index.php?title=Server_Rules&diff=12Server Rules2025-11-07T14:19:45Z<p>Anettera: </p>
<hr />
<div>For more in-depth explanations of rules and FAQ, please read the Rule precedents document<br />
<br />
== Core Rules ==<br />
0). Take these rules as they are to be intended and not as they are written literally.<br />
0.1. Rule skirting, lawyering, and/or being a dick for the sake of ruining others' experiences can become a bannable offense if occurring regularly.<br />
<br />
1). Fulpstation is a Medium Roleplay server. We define this as performing your assigned duties. This is a ‘do your job’ server. This means it is important to do what is expected out of your department and not what would be expected out of other departments.<br />
<br />
1.1. If you want to build mechs, play roboticists. If you want to hunt for antags and uphold space law, play security. This is to ensure all players can have a fun shift and have a role to fill. This is not intended to limit what is possible on the server but to provide structure for everyone.<br />
1.2. Opt-in for roles you intend to play or seek an IC way to change your job. Failure to attempt to do the most basic of duties for your role may result in a job ban. [A list of basic duties can be found here]. While transferring to another department and doing another job is acceptable, being a know it all for multiple departments is not.<br />
1.3. If you do not wish to be a role or antag, ensure you set it to never in your occupation preferences and/or request a ban from said role or antag. Changing your job preference settings to “return to lobby if preferences unavailable” will prevent you from being assigned a random position.<br />
1.4. Players' knowledge of the game is not limited by their job. However, using knowledge of antags and round types without IC justification is considered metagaming. For example, it is acceptable for a clown to know how to build a conveyor belt for a prank. It is not acceptable for a clown to know that xenomorphs are weak to fire and rush to make a flamethrower.<br />
<br />
2). Malicious acts like griefing, metagaming, killbaiting, banbaiting, powergaming, self-antagging, greytiding, validhunting (along with calling people and silicons valid without proper cause), and exploiting can become bannable offenses if occurring regularly or if the infraction is serious enough.[See the glossary here].<br />
<br />
2.1. Multi keying, ban evasion, cheating, blatant intent to grief, and RDMing are all permanent ban offenses.<br />
2.2. If playing with someone that is at the same location as you, alert us so we may take note of it. Otherwise, we may assume they are you.<br />
2.3. Antag rolling, or round-start suicides that appear to be antag rolling, may result in an antag ban if occurring frequently enough<br />
3). Sexual content is strictly prohibited. This includes content like photos/websites/Erotic Role Play (ERP) and applies to the server, Discord, and forums. Sending unsolicited sexual content to another player via direct messages will also result in a ban.<br />
<br />
4). Hate speech is strictly forbidden. Using the Discord, the SS13 server, or the forums to threaten a group of people or to propagate racial and otherwise prejudiced slurs or stereotypes is a bannable offense. We take this seriously and want to create a server that is welcoming to all people. This includes variations or misspellings of slurs. SS13 is your character’s workplace; if you would get fired for saying it in a modern-day office setting, you shouldn’t be saying it on the server.<br />
<br />
5). Discrimination towards in-game sub-species and silicons is acceptable in moderation, but attacking them or otherwise preventing them from playing the round is not. Additionally, terms that are based on real-life slurs are not allowed.<br />
<br />
6). Do not spam, advertise, or paste lengthy and/or inappropriate copypastas.<br />
<br />
7). Keep IC content in IC, and OOC content in OOC. This means no IC in OOC (ick ock) and vice versa.<br />
<br />
8). Revealing information about the current round in OOC, Discord, or the forums (metacomming) is strictly prohibited. Wait until after the Round End screen to discuss the round or file a report.<br />
<br />
9). Avoid antagonizing players and staff via the Discord, Forums, or through OOC/deadchat. While expressing frustration about in-round events is acceptable, ganging up on fellow players is not.<br />
<br />
9.1 - IC insults are fine within reason, but harassing other players repeatedly throughout the round or using OOC insults IC is not.<br />
10). Each round exists independently of all other rounds. While friendships persisting through rounds is okay, using experiences from other rounds to give an advantage or disadvantage to other players is not permitted.<br />
<br />
== Returning From The Afterlife ==<br />
1). Do not use information obtained while dead or from a previous life upon returning to the land of the living.<br />
<br />
2). Cyborgs and other creatures that are created with a character’s organic brain (i.e. not a positronic brain) retain all knowledge of events that happened before the procedure while they were living. Rule 1 still applies to information obtained while dead.<br />
<br />
2.1. Antagonists who undergo forced cyborgization retain their antag status and objectives but must prioritize their law set. This prevents borgs from attempting to be unborged in most circumstances.<br />
SSD/AFK Player Interactions<br />
Note: SSD characters are players who are disconnected or AFK. It is possible for players to return to SSD bodies. Players become catatonic when they take a ghost spawner role or commit suicide. Players are NOT able to return to these bodies without admin intervention.<br />
<br />
1). Do your best not to interact negatively with SSD/AFK players. Moving them to safety is acceptable, but killing, looting, or otherwise griefing them while they are away is not.<br />
<br />
1.1. If the player in question is an antag’s target or they are being secured by security, interactions to finish what is required of your duties/objectives are always acceptable.<br />
1.2. Ahelping about an SSD/AFK player may grant an exception to this rule.<br />
2). Rule 1 does not apply to players that are catatonic. Although needlessly killing or harming catatonic players is discouraged (and will probably get you hunted by security), harvesting their organs to save another player is acceptable.<br />
<br />
== Escalation Clause ==<br />
1). Escalation resulting in murder is only acceptable within reason. If your life is in danger, you can always fight back lethally, or if a conflict with the other player has lasted throughout the round with multiple fights. In most cases, fights end when one party enters critical condition or is otherwise incapacitated. Theft, break-ins, demotions, destruction of property, getting pranked and other inconveniences are not reasons to murder another player or put them into a life or death situation. Ask what a rational person would do and act accordingly.<br />
<br />
1.1. Expect to receive the same kind of treatment and escalation that you give out.<br />
1.2. If the other party during an altercation dies or is seriously injured, work to get them healed or revived.<br />
2). If you act like an antagonist, expect to be treated like one and be held liable for your actions both IC and by admins.<br />
<br />
3). Over-escalation of fights is also unacceptable. Over-escalation is, in short, doing more damage to someone than is required to resolve an issue or using violence instead of words to solve an issue. <br />
<br />
Examples being: <br />
<br />
Killing someone during a dangerous fight when they could be placed into crit and healed or ignoring the opportunity to use non-lethal force when available.<br />
Placing someone someplace they will surely die, like disposals when crit, space, in shuttle landing zones, or other gibbers.<br />
Delimbing someone for doing minimal damage to you.<br />
Breaking into a department and attacking someone when they try to remove you from the department instead of asking for what is needed.<br />
3.1). While using lethal force is allowed in some cases of self-defense, actions that jeopardize the lives of other players or could cause massive damage to the station (e.g. max caps) is considered over escalation, and you will be held accountable for deaths that occur due to negligent behavior. This rule applies when committing acts that will likely cause mass casualties to eliminate antagonists.<br />
<br />
Command/Security/Silicon Responsibilities<br />
1). The following jobs: Captain, HOP, HOS, CE, RD, CMO, QM, and AI should ahelp when they need to leave. This is to ensure a replacement can be installed (Your body will be offered to ghosts or your character will be deleted and the job slot reopened) for continuity of the round. Your intent to leave should also be made known to other command staff if possible. If no staff are available to offer your body to ghosts, you should designate another player as your replacement after ahelping.<br />
<br />
1.1. These roles must exhibit some competency. Lack of this can result in a job ban. Command roles are designed to lead and manage departments first and do second. They are not intended to become do-it-all members of their departments.<br />
1.2. Crew promoted to acting heads of staff must step down when an official head of staff arrives at the station. This is to prevent confusion with the chain of command when the new player arrives.<br />
2). In the absence of a captain and CentCom appointed acting captain, the Head of Personnel or Head of Security must serve as acting captain or split the duties of the captain between themselves. In the absence of a captain and CentCom appointed acting captain, HoP, and HoS, the other command staff have equal standing in determining a new acting captain among themselves.<br />
<br />
2.1. Only command staff may serve as acting captain. Acting departmental heads and regular crew may not serve as acting captain.<br />
2.2. The only item acting heads may take from the head’s office is the command headset. Unless there is a dire emergency, no other items should be removed by non-antags.<br />
2.3. An acting captain may fill in for decisions that require the captain’s authorization, but may not run the station and its departments, nor are they privy to the captain's equipment or access outside of the command headset and nuke disk. The captain’s spare ID can be used to run the HoP line in the case of a non-HoP acting captain but should not leave the bridge.<br />
3). Heads of staff, acting heads of staff, and security should not abandon the station without permission from CentCom. This includes going to Lavaland, space exploration, bitrunning, and entering the gateway.<br />
<br />
4). We adhere to our own version of [space law].<br />
<br />
4.1. While the majority of this is a guideline, we expect things to be applied reasonably. Giving someone a ten-minute brig timer for slipping the captain is an example of things not being applied reasonably.<br />
4.2. Abusing crew as security is never acceptable.<br />
4.3. Authorization for permanent punishments (including executions) should only be followed if the authorization was given by the correct authority. For example, a sec officer should not comply with execution orders given by an HoS when a captain is abroad the station.<br />
4.4. Security must use nonlethal force unless there is reasonable suspicion that the other party is armed (e.g. breaking into the armory), lethal force is used upon them, or the use of nonlethal force is impossible (e.g. Hulks). See “Use of Deadly Force” under Space Law for more information.<br />
4.5 Ensuring prisoners receive timely revival and proper medical care is the responsibility of everyone in the security team. Unless an execution was authorized by the captain, this applies to any player killed by security. Detaining players who are dead or will likely die from injuries without attempting to provide medical care (e.g. throwing a prisoner in critical condition in a cell) is a violation of 4.2. See “Prisoner Medical Care” in Space law for more information. Repeated negligent deaths may result in a role ban.<br />
5). We adhere to our own version of [silicon and drone] policy.<br />
<br />
5.1 Those that upload laws to silicons are responsible for what said law causes.<br />
5.2 Ordering silicons to commit suicide or any actions that would be considered grief as a non-antag is strictly prohibited. Silicons who are given such orders should ahelp before carrying them out; however, the person giving the command will still be held responsible.<br />
6). We now adhere to our own [standard operating procedure] policy.<br />
<br />
6.1 Calling the shuttle on red alert to end the round faster despite there being no significant threats to the station will likely result in it being recalled.<br />
Antagonist/Lavaland/Ghost Policy<br />
1). Antagonists exist to move the round forward and make things interesting and fun for everyone involved. Excessively recalling the shuttle to prevent the natural end of the round in order to do your objectives should be avoided and may result in moderator intervention. If you complete your objectives, you may pray to be given additional objectives.<br />
<br />
1.1. Do not needlessly kill those you do not need to outside of your objectives and simply because you can. This includes destroying silicons. Things like covering up evidence, dealing with pursuing security officers, ‘Good Samaritans’ on your tail, and removing a witness, are always acceptable examples. Ahelping ideas for gimmicks may grant an exception to this.<br />
1.2. Killing players outside of rule 1.1 must directly further your goal, and you cannot permanently remove these players from the round. For example, killing an engineer to gain departmental access with the objective to steal the CE’s blueprints is acceptable. Killing an engineer for her insulated gloves or access to the prolathe without an objective in that department is not.<br />
1.3. Do not spawn camp or prevent others from entering the round safely.<br />
1.4. Do what is needed for your goals. Destroying half the station when you only need to steal research is an example of going extremely overboard. Causing chaos in a department with a bomb is okay but destroying half the station is not<br />
1.5 Team antag objectives take precedent over solo antag objectives.<br />
2). If you become an antagonist and do not wish to be one, ahelp so that we may set you up with another role and/or give your antagonist status to another player.<br />
<br />
3). Creatures and those turned into creatures maintain their antag status from their previous form. See the “Returning from the Afterlife” section for more information.<br />
<br />
4). Ghost spawner roles must follow their flavor text upon taking said role. These roles are meant to allow players to return to the game, and their slots are usually limited. Intentionally wasting spawner slots (e.g. repeatedly suiciding as spawner roles during one round) may result in a ghost role ban.<br />
<br />
5). Sentient animals, critters, and creatures are not valid to be killed by the crew simply for existing -- they are players too. However, if they are causing trouble, this protection is waived.<br />
<br />
6). Lavaland spawner roles (such as Ashwalkers and Free Golems) are meant to allow players to return to the game and are only considered valid if aggressive toward crewmembers. See the “Guide on acceptable killing” section at the end of this document.<br />
<br />
6.1. Lavaland spawners who enter the station must be peaceful and are held to stricter standards for escalation and roleplay than when on Lavaland. Spawners may not use meta knowledge to seek out the Lavaland mining base and may only enter if invited by crew members. Spawners who are hostile/ willingly impede the station are subject to a ghost role ban.<br />
6.2 Spawner roles must follow their flavor text and treat their spawn location (e.g. Charlie station) with the same regard as the main station. Intentionally destroying your spawn location without sufficient IC reason prevents players from rejoining the game and will result in a ghost role ban.<br />
7). Rules 6 and 6.1 do NOT apply to any Syndicate spawners. These roles are permitted to kill Nanotrasen crew members on sight and similarly may be killed by NT crew. <br />
<br />
7.1 Spawners at the Syndicate base in Lavaland are never permitted to leave their base.<br />
7.2 Spawners at the Syndicate ship are allowed to leave their base but must not seek out the Nanotrasen station. These spawners are never permitted to intentionally approach or board the NT station. If you accidentally find the NT station you are expected to leave immediately.<br />
8). If you disconnect as an antagonist, we will be forced to offer your body to ghosted players after ten minutes without reconnecting. Members of team antagonists (e.g. nuclear/clown operatives, blood brothers, head revolutionaries) must notify admins that they are leaving through ahelps.<br />
<br />
== Admin Interactions ==<br />
0). Our staff is composed entirely of volunteers who work to make Fulp a welcoming community to all players. While it’s okay to express frustration with admin interactions, doing so in a way that is aggressive or harassing will result in a mute or a ban. If you harass staff, expect consequences to come as a result of your actions or your issue to be discarded.<br />
<br />
0.1). Do not send unsolicited Direct Messages to staff via Byond. If you need to contact staff, verify on Discord and use the #ask-mods channel or the forums. Sending unsolicited DMs via Byond may result in a permaban.<br />
<br />
1). Ahelp as soon as possible. Waiting can make things harder or even impossible to look into. We do not know what we do not see. The moderation team exists to help. Ahelping can bring things to our attention we may miss.<br />
<br />
2). Provide as many details as possible. Generally, your ahelp should include the name of the offending character and a brief description of what happened. This makes it easier for us to figure out an issue.<br />
Bad ahelp: Sec arrested me for no reason<br />
Good ahelp: Sec officer John Smith put me in a cell with no timer for trespassing into science, and I’ve been here for 5 minutes already.<br />
<br />
3). While players are encouraged to ahelp problems they have in-round, misusing ahelps (e.g. complaining about round or asking to be an antag) is not acceptable. If your ticket is rejected or marked IC and you wish to have it reviewed, file a staff report on the forums as additional tickets regarding the same issue will be ignored. Misusing ahelps clutters tickets, and repeatedly doing so may result in notes or a ban.<br />
<br />
4). Do not lie in ahelps as we can verify any claims made via player logs. If you are unsure of how an event transpired, you are encouraged to look through your logs for verification. Lying in ahelps will result in a ban.<br />
<br />
5). Respond to Admin PMs as soon as possible so we know you aren’t ignoring the ticket. Even a ‘one moment’ will suffice.<br />
<br />
6). In-character communication with admins should be done through the prayer option under the IC tab. Prayer can be used to obtain in-game items at the admin’s discretion. This includes TC trades. Ahelps should not be used in place of prayers for IC issues. Praying does not guarantee a response and may result in being smited. Spamming prayers may result in a mute/smiting. Do not ahelp if your prayer is not answered.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Admin interaction !! Event<br />
|-<br />
| Ahelp || Other players breaking the rules (e.g. suspected self-antag, IC in OOC, hate speech, theft of dept equipment, etc.), reporting a bug/ glitches, leaving as a dept head, asking for antag status to be removed, confirming rules about large-scale antag actions<br />
|-<br />
| Mhelp || Asking about game mechanics<br />
|-<br />
| Prayer || TC trades, requesting items, asking for antag status when not already an antag, asking for additional objectives<br />
|-<br />
| Forum Post || Reporting other players when no admins are online, ban appeals<br />
|}<br />
<br />
== Glossary of Malicious Acts and Examples ==<br />
Ban Baiting: Actions/communication that bait staff into banning others. <br />
<br />
This also applies to tricking other players into doing things that would get them banned e.g. telling a new chemist to make a potassium water bomb<br />
<br />
Griefing: Deliberate actions that interfere with/antagonize other players or will take serious effort and time from other players to fix and/or repair.<br />
<br />
Stacking numerous small acts also applies here. <br />
<br />
If the combination of all that you are going to do will take more than ten minutes to repair or replace, you probably should not do it regardless of if it's ‘just a prank’. This includes things like infinite disposals loops.<br />
<br />
Obvious things like floor pills, conveyor belts leading out an airlock, mazes, and other inconveniences do not count as grief, as long as their intentions are not mislabeled or hidden. Like dangerous floor pills being labeled, ‘brute damage pill’.<br />
<br />
Losing is part of the game and does not always equal being griefed. Excessive complaints about IC deaths may result in a deadchat/ OOC mute.<br />
<br />
Examples of grief include:<br />
<br />
Dismantling important machinery like Cryo Tubes or disabling the gravity generator.<br />
Trapping other players in lockers/rooms while stealing their ID and other unique items.<br />
Removing other players limbs, drugging, or poisoning them needlessly, or removal of unique items like heirlooms.<br />
Venting the station to space or blocking off areas of the station.<br />
Pushing players out of the airlocks on the shuttle<br />
Greytiding: Consistent and deliberate low-level IC crimes used for personal advantages or gimmicks that spark conflict with others.<br />
<br />
Stealing items or equipment from departments.<br />
Hacking/trespassing into places that you do not have access.<br />
Starting/joining fights that you have no reason to.<br />
<br />
Kill Baiting: Baiting others into harming or killing you to escalate an issue, or baiting them into escalation so that you may kill them.<br />
<br />
This counts as an over-escalation of an issue. Fights and normally escalated fights are fine however.<br />
<br />
Meta Gaming/ Meta Knowledge: The use of out of character knowledge or game mechanics to have an advantage in-game. <br />
<br />
Examples of this could be:<br />
<br />
Knowing about stealth traitor uplink gear (e.g. sleepy pens) as a non-antag.<br />
This rule does not apply to non-stealth items such as e-swords<br />
Hiding traitor objective items and other sensitive materials at round start without confirmation of antagonists on the station looking for these items.<br />
Noticing a character is acting differently than normal and acting on it as them being an antag.<br />
Metagrudging against players and meta communicating.<br />
Using discovered knowledge of round type to assume the existence of additional antagonists, this includes expecting exact numbers of antags.<br />
Going into maint and checking for maint walls to check for Bloodsucker lairs when you aren't security.<br />
Changing the access of doors or bunkering departments without sufficient IC reasons. This includes building vault doors or turrets.<br />
Multi Keying: Using multiple accounts/clients to play the game during the course of a round. This will result in the newer account(s) being permanently banned and any and all notes being transferred to the older account.<br />
<br />
Power Gaming: Obtaining items/power or doing things outside of the scope of your department or skill range to have a greater advantage. More often than not this is playing to ‘win’, whether it be at a certain mechanic, game mode or anything else. This includes giving others no room or ability to act or ‘win’ themselves. These rules are relaxed for players with antag status.<br />
<br />
Examples of this are: <br />
<br />
Breaking in and taking your head of staff’s gear.<br />
A Head of Personnel giving themselves security access.<br />
Replacing the brig windows with walls at round start.<br />
Building an exosuit fabricator as an engineer to make yourself a mech.<br />
Circumventing access restrictions via hacking or using stolen/looted IDs.<br />
Removing your mindshield or asking others to remove your mindshield.<br />
RDMing (Random Death Match): Killing or attempting to kill multiple other players without proper cause or reason.<br />
<br />
Self Antagging: Acting as an enemy of the station when not one, i.e. making yourself ‘valid’. More often than not, these are capital crimes. If it's something only an antag would reasonably do- like bombing a department - don’t do it.<br />
<br />
Valid Hunting: Searching for / preparing for / dealing with antagonists and criminals without a need or duty to do so. This includes having the intention of eliminating them as a threat to the station. Note that this refers specifically to the illegitimate targeting of antags and does not include scenarios listed as acceptable in the Guide of Acceptable Antag Killing (e.g. you can’t validhunt a nukie because they are always an acceptable target for all crewmembers).<br />
<br />
Being a vigilante within reason is acceptable here such as helping someone getting attacked by another player. If it involves going out of your way to do so though, it's probably going too far.<br />
<br />
Examples of this are:<br />
<br />
As an engineer, creating a tesla death trap for those that may break-in.<br />
As an assistant, stealing a baton and wandering maint because they expect antagonists to be there.<br />
As a miner, attacking a suspected changeling who is not actively harming anyone.<br />
Attacking or ‘jumping at’ a fellow player simply for having an item an antag would. An example being a chaplain/scientist having a dark blessing/a xeno-biology arm blade or a known space explorer having contraband.<br />
<br />
== Guides on acceptable killing ==<br />
Note: While this guide applies for most scenarios, there is some flexibility on who you can kill so long as it directly furthers your objectives. However, it is generally advised that you ahelp before killing a player that does not fall under these categories. Rule lawyering kills based on the flexibility of this rule will result in your argument being disregarded.<br />
<br />
Highlighted entries denote roles that may cause large scale damage to the station WITHOUT admin approval. For all others, please refer to Antag rule 1.4 <br />
<br />
{| class="wikitable"<br />
|-<br />
! Role !! Who you can kill !! Who you can permanently remove<br />
|-<br />
| Any antag with hijack objective || Anyone once the shuttle has been called at any alert level || Anyone once the shuttle has been called at any alert level<br />
|-<br />
| Abductor || Self-defense only || None<br />
|-<br />
| Ashwalkers || Any non-ashwalker at lavaland wastes || Any non-ashwalker at lavaland wastes<br />
|-<br />
| Bloodsucker || Pursuing security officers, witnesses, valid hunters, anyone if it is in line with objectives (e.g. blood consumption, hearts)*<br />
<br />
''Note: Plasma men do not have blood and should not be killed for feedings'' <br />
|| None<br />
|-<br />
| Blood Brother/ Traitor WITHOUT hijack, other round-ending objectives die a glorious death, or round-ending final objectives || Your target, pursuing security officers, witnesses, valid hunters, people protecting items for steal objectives(e.g. killing the captain for the nuke disk) || Your target(s)<br />
|-<br />
| Changeling|| Your target, pursuing security officers, witnesses, valid hunters, anyone if it's in line with objectives (e.g. killing other lings to obtain the most DNA points)* || Your target(s)<br />
|-<br />
| Cultist || Mindshielded crew, self-defense || Mindshielded crew<br />
|-<br />
| Die a glorious death objective || Anyone as long as you die as a result. If you are planning something impactful, ahelp to let the admins know ahead of time (e.g. clown car into sm is fine while murdering unarmed crew members is not) || Anyone as long as you die as a result<br />
|-<br />
| Heretic || <br />
* Before ascension: Sacrifice/ objective targets, pursuing security officers, witnesses, valid hunters<br />
* After ascension: Anyone <br />
|| <br />
* Before ascension: None<br />
* After ascension: Anyone<br />
|-<br />
| (Syndicate) Infiltrator || Before full completion: Your target, pursuing security officers, witnesses, valid hunters, people protecting items for steal objectives.<br />
<br />
After last objective: See Die a glorious death or Hijack acceptable killing depending on which one you receive. <br />
|| Before full completion: Your target(s)<br />
<br />
After last objective: See Die a glorious death or Hijack acceptable killing depending on which one you receive.<br />
|-<br />
| Malf AI WITH hijack objectives || Anyone except borgs slaved to you || Anyone except borgs slaved to you<br />
|-<br />
| Malf AI WITHOUT hijack objectives || Your target(s), anyone breaking into your satellite to card you || Your target(s). A malf AI should not use Doomsday without an appropriate objective.<br />
|-<br />
| Miners || Megafauna, aggressive ashwalkers, self-defense <br />
<br />
Lavaland gear should NOT be used on the station to validhunt or as a non-antag <br />
|| None<br />
|-<br />
| Monster Hunter || Targets, Self-defense <br />
|| Before ascension: Targets<br />
After ascension: Anyone<br />
|-<br />
| Nightmare || Anyone || Anyone<br />
|-<br />
| Ninja || Anyone as long as it is in line with objectives || Anyone as long as it is in line with objectives<br />
|-<br />
| Nuclear or Clown Operatives || Anyone except other operatives || Anyone except other operatives<br />
|-<br />
| Obsessed || Your targets, pursuing security members, witnesses, valid hunters || Your target(s)<br />
|-<br />
| Paradox Clone || Your target, witnesses, pursuing security members || Your target<br />
|-<br />
| Prisoner || Self-defense only. Prisoners are not antags on Fulp || None<br />
|-<br />
| Pirate || Security, self-defense || None<br />
|-<br />
| Revenant || Anyone for soul consumption || Anyone for soul consumption<br />
|-<br />
| Revolutionary || Department heads, Mindshielded crew (including security), self-defense || Department heads, security<br />
|-<br />
| Security || Self-defense, nuclear/clown operatives, criminals who have committed capital crimes AFTER captain approval or a trial, criminals that are too dangerous to detain non lethally || Nuclear/clown operatives, Criminals who have committed capital crimes AFTER captain approval or a trial<br />
|-<br />
| Sentient Disease || Anyone || Anyone<br />
|-<br />
| Sentience Spawns/ Slaved Golems || Anyone you are instructed to kill by your creator; otherwise, regular escalation rules apply || Anyone you are instructed to kill by your creator<br />
|-<br />
| Slaughter/ Laughter demon || Anyone || Anyone <br />
|-<br />
| Space Dragon || Anyone || Anyone <br />
|-<br />
| Spy || Your target, pursuing security officers, witnesses, valid hunters, people protecting items for steal objectives(e.g. killing the captain for the nuke disk) || Targets<br />
<br />
Mass destruction (even when it results in round removal of non-targets) is acceptable within the scope of your objective (not spy bounties). Starting a plasma fire in medbay would be acceptable for the objective “Ensure medbay is engulfed in flames”, but starting a station-wide plasma fire would not.<br />
|-<br />
| Wizard || Anyone || Anyone <br />
|-<br />
| Xenomorphs|| Anyone || Anyone <br />
|}<br />
* Rules on killbaiting and RDM still apply for these roles. Going out of your way to kill or round remove players without sufficient reason will still result in an antag ban<br />
<br />
<br />
== Guide on acceptable antag killing ==<br />
Note: This guide applies to most scenarios, and very few situations exist where crew members aside from security (as well as silicons and chaplains with proper IC justification) should intentionally seek out antags. This guide is not meant as a replacement of the above rules. Self-defense and other justifications still apply. If you have any questions in-round you are encouraged to ahelp before taking action<br />
<br />
{| class="wikitable"<br />
|-<br />
! Antag type !! Can the crew kill it?<br />
|-<br />
| Any antag attempting to hijack the shuttle || Yes<br />
|-<br />
| Abductor || No<br />
|-<br />
| Blob || Yes<br />
|-<br />
| Bloodsucker || Crew should not actively seek out or prepare for bloodsuckers, but confirmed bloodsuckers can be round removed by crew if caught while behaving aggressively<br />
|-<br />
| Changeling || Crew should not actively seek out or prepare for changelings but confirmed changelings can be round removed by crew if caught while behaving aggressively<br />
|-<br />
| Cultist || Only AFTER the cult has been revealed (Pentagrams appear above cultists’ heads or ritual has begun)<br />
|-<br />
| Escaped prisoners || No (prisoners are not valid on Fulp)<br />
|-<br />
| Heretics || <br />
* Before ascension: No<br />
* After ascension: Yes<br />
|-<br />
| Malf AI/ Traitor/ Blood Brother WITHOUT hijack objectives || No<br />
|-<br />
| Malf AI/ Traitor/ Blood Brother WITH hijack or other round-ending objective || Only AFTER they start acting on this objective<br />
|-<br />
| Monster Hunter || Before ascension: No<br />
After ascension: Yes<br />
|-<br />
| Nightmare|| Yes<br />
|-<br />
| Ninja || Yes<br />
|-<br />
| Nuclear/ Clown Operatives || Yes<br />
|-<br />
| Obsessed || No<br />
|-<br />
| Pirate || Yes<br />
|-<br />
| Paradox Clone || No (except the cloning target)<br />
|-<br />
| Revenant || Yes<br />
|-<br />
| Revolutionary || No<br />
|-<br />
| Slaughter/ Laughter demon || Yes<br />
|-<br />
| Spy || No, unless immediately engaged in something that would reasonably cause mass destruction (e.g., bombing a department)<br />
|-<br />
| Wizard || Yes<br />
|-<br />
| Xenomorph|| Yes<br />
|}</div>Anetterahttps://wiki.fulp.gg/index.php?title=MediaWiki:Sidebar&diff=11MediaWiki:Sidebar2025-11-07T13:25:58Z<p>Anettera: </p>
<hr />
<div><br />
* navigation<br />
** mainpage|mainpage-description<br />
** Server_Rules|Server Rules<br />
** recentchanges-url|recentchanges<br />
** helppage|help-mediawiki<br />
** specialpages-url|specialpages<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Anetterahttps://wiki.fulp.gg/index.php?title=MediaWiki:Sidebar&diff=10MediaWiki:Sidebar2025-11-07T13:25:23Z<p>Anettera: </p>
<hr />
<div><br />
* navigation<br />
** mainpage|mainpage-description<br />
** [[Server Rules]]|Server Rules<br />
** recentchanges-url|recentchanges<br />
** helppage|help-mediawiki<br />
** specialpages-url|specialpages<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Anetterahttps://wiki.fulp.gg/index.php?title=MediaWiki:Sidebar&diff=9MediaWiki:Sidebar2025-11-07T13:22:33Z<p>Anettera: Created page with " * navigation ** mainpage|mainpage-description ** recentchanges-url|recentchanges ** helppage|help-mediawiki ** specialpages-url|specialpages * SEARCH * TOOLBOX * LANGUAGES"</p>
<hr />
<div><br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** helppage|help-mediawiki<br />
** specialpages-url|specialpages<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Anetterahttps://wiki.fulp.gg/index.php?title=Main_Page&diff=8Main Page2025-11-07T13:19:42Z<p>Anettera: </p>
<hr />
<div>This is the wiki for Fulpstation, a custom fork of the /tg/station flavoured fork of Space Station 13.<br />
<br />
Most things listed here are Fulpstation-Unique, and the TGstation wiki should be used for everything else.<br />
<br />
* Our Repository: https://github.com/fulpstation/fulpstation<br />
* tgstation's Repository: https://github.com/tgstation/tgstation<br />
* Forum: https://forum.fulp.gg<br />
* Discord: https://discord.gg/dSw5nqgDye<br />
* tgstation's Wiki: https://wiki.tgstation13.org<br />
* Map viewer: https://webmap.affectedarc07.co.uk<br />
<br />
Space Station 13 is a paranoia-laden round-based roleplaying game set against the backdrop of a nonsensical, metal death trap masquerading as a space station, with charming spritework designed to represent the sci-fi setting and its dangerous undertones. Have fun, and survive!</div>Anetterahttps://wiki.fulp.gg/index.php?title=Server_Rules&diff=7Server Rules2025-11-07T12:45:27Z<p>Anettera: </p>
<hr />
<div>For more in-depth explanations of rules and FAQ, please read the Rule precedents document<br />
<br />
== Core Rules ==<br />
0). Take these rules as they are to be intended and not as they are written literally.<br />
0.1. Rule skirting, lawyering, and/or being a dick for the sake of ruining others' experiences can become a bannable offense if occurring regularly.<br />
<br />
1). Fulpstation is a Medium Roleplay server. We define this as performing your assigned duties. This is a ‘do your job’ server. This means it is important to do what is expected out of your department and not what would be expected out of other departments.<br />
<br />
1.1. If you want to build mechs, play roboticists. If you want to hunt for antags and uphold space law, play security. This is to ensure all players can have a fun shift and have a role to fill. This is not intended to limit what is possible on the server but to provide structure for everyone.<br />
1.2. Opt-in for roles you intend to play or seek an IC way to change your job. Failure to attempt to do the most basic of duties for your role may result in a job ban. [A list of basic duties can be found here]. While transferring to another department and doing another job is acceptable, being a know it all for multiple departments is not.<br />
1.3. If you do not wish to be a role or antag, ensure you set it to never in your occupation preferences and/or request a ban from said role or antag. Changing your job preference settings to “return to lobby if preferences unavailable” will prevent you from being assigned a random position.<br />
1.4. Players' knowledge of the game is not limited by their job. However, using knowledge of antags and round types without IC justification is considered metagaming. For example, it is acceptable for a clown to know how to build a conveyor belt for a prank. It is not acceptable for a clown to know that xenomorphs are weak to fire and rush to make a flamethrower.<br />
<br />
2). Malicious acts like griefing, metagaming, killbaiting, banbaiting, powergaming, self-antagging, greytiding, validhunting (along with calling people and silicons valid without proper cause), and exploiting can become bannable offenses if occurring regularly or if the infraction is serious enough.[See the glossary here].<br />
<br />
2.1. Multi keying, ban evasion, cheating, blatant intent to grief, and RDMing are all permanent ban offenses.<br />
2.2. If playing with someone that is at the same location as you, alert us so we may take note of it. Otherwise, we may assume they are you.<br />
2.3. Antag rolling, or round-start suicides that appear to be antag rolling, may result in an antag ban if occurring frequently enough<br />
3). Sexual content is strictly prohibited. This includes content like photos/websites/Erotic Role Play (ERP) and applies to the server, Discord, and forums. Sending unsolicited sexual content to another player via direct messages will also result in a ban.<br />
<br />
4). Hate speech is strictly forbidden. Using the Discord, the SS13 server, or the forums to threaten a group of people or to propagate racial and otherwise prejudiced slurs or stereotypes is a bannable offense. We take this seriously and want to create a server that is welcoming to all people. This includes variations or misspellings of slurs. SS13 is your character’s workplace; if you would get fired for saying it in a modern-day office setting, you shouldn’t be saying it on the server.<br />
<br />
5). Discrimination towards in-game sub-species and silicons is acceptable in moderation, but attacking them or otherwise preventing them from playing the round is not. Additionally, terms that are based on real-life slurs are not allowed.<br />
<br />
6). Do not spam, advertise, or paste lengthy and/or inappropriate copypastas.<br />
<br />
7). Keep IC content in IC, and OOC content in OOC. This means no IC in OOC (ick ock) and vice versa.<br />
<br />
8). Revealing information about the current round in OOC, Discord, or the forums (metacomming) is strictly prohibited. Wait until after the Round End screen to discuss the round or file a report.<br />
<br />
9). Avoid antagonizing players and staff via the Discord, Forums, or through OOC/deadchat. While expressing frustration about in-round events is acceptable, ganging up on fellow players is not.<br />
<br />
9.1 - IC insults are fine within reason, but harassing other players repeatedly throughout the round or using OOC insults IC is not.<br />
10). Each round exists independently of all other rounds. While friendships persisting through rounds is okay, using experiences from other rounds to give an advantage or disadvantage to other players is not permitted.<br />
<br />
== Returning From The Afterlife ==<br />
1). Do not use information obtained while dead or from a previous life upon returning to the land of the living.<br />
<br />
2). Cyborgs and other creatures that are created with a character’s organic brain (i.e. not a positronic brain) retain all knowledge of events that happened before the procedure while they were living. Rule 1 still applies to information obtained while dead.<br />
<br />
2.1. Antagonists who undergo forced cyborgization retain their antag status and objectives but must prioritize their law set. This prevents borgs from attempting to be unborged in most circumstances.<br />
SSD/AFK Player Interactions<br />
Note: SSD characters are players who are disconnected or AFK. It is possible for players to return to SSD bodies. Players become catatonic when they take a ghost spawner role or commit suicide. Players are NOT able to return to these bodies without admin intervention.<br />
<br />
1). Do your best not to interact negatively with SSD/AFK players. Moving them to safety is acceptable, but killing, looting, or otherwise griefing them while they are away is not.<br />
<br />
1.1. If the player in question is an antag’s target or they are being secured by security, interactions to finish what is required of your duties/objectives are always acceptable.<br />
1.2. Ahelping about an SSD/AFK player may grant an exception to this rule.<br />
2). Rule 1 does not apply to players that are catatonic. Although needlessly killing or harming catatonic players is discouraged (and will probably get you hunted by security), harvesting their organs to save another player is acceptable.<br />
<br />
== Escalation Clause ==<br />
1). Escalation resulting in murder is only acceptable within reason. If your life is in danger, you can always fight back lethally, or if a conflict with the other player has lasted throughout the round with multiple fights. In most cases, fights end when one party enters critical condition or is otherwise incapacitated. Theft, break-ins, demotions, destruction of property, getting pranked and other inconveniences are not reasons to murder another player or put them into a life or death situation. Ask what a rational person would do and act accordingly.<br />
<br />
1.1. Expect to receive the same kind of treatment and escalation that you give out.<br />
1.2. If the other party during an altercation dies or is seriously injured, work to get them healed or revived.<br />
2). If you act like an antagonist, expect to be treated like one and be held liable for your actions both IC and by admins.<br />
<br />
3). Over-escalation of fights is also unacceptable. Over-escalation is, in short, doing more damage to someone than is required to resolve an issue or using violence instead of words to solve an issue. <br />
<br />
Examples being: <br />
<br />
Killing someone during a dangerous fight when they could be placed into crit and healed or ignoring the opportunity to use non-lethal force when available.<br />
Placing someone someplace they will surely die, like disposals when crit, space, in shuttle landing zones, or other gibbers.<br />
Delimbing someone for doing minimal damage to you.<br />
Breaking into a department and attacking someone when they try to remove you from the department instead of asking for what is needed.<br />
3.1). While using lethal force is allowed in some cases of self-defense, actions that jeopardize the lives of other players or could cause massive damage to the station (e.g. max caps) is considered over escalation, and you will be held accountable for deaths that occur due to negligent behavior. This rule applies when committing acts that will likely cause mass casualties to eliminate antagonists.<br />
<br />
Command/Security/Silicon Responsibilities<br />
1). The following jobs: Captain, HOP, HOS, CE, RD, CMO, QM, and AI should ahelp when they need to leave. This is to ensure a replacement can be installed (Your body will be offered to ghosts or your character will be deleted and the job slot reopened) for continuity of the round. Your intent to leave should also be made known to other command staff if possible. If no staff are available to offer your body to ghosts, you should designate another player as your replacement after ahelping.<br />
<br />
1.1. These roles must exhibit some competency. Lack of this can result in a job ban. Command roles are designed to lead and manage departments first and do second. They are not intended to become do-it-all members of their departments.<br />
1.2. Crew promoted to acting heads of staff must step down when an official head of staff arrives at the station. This is to prevent confusion with the chain of command when the new player arrives.<br />
2). In the absence of a captain and CentCom appointed acting captain, the Head of Personnel or Head of Security must serve as acting captain or split the duties of the captain between themselves. In the absence of a captain and CentCom appointed acting captain, HoP, and HoS, the other command staff have equal standing in determining a new acting captain among themselves.<br />
<br />
2.1. Only command staff may serve as acting captain. Acting departmental heads and regular crew may not serve as acting captain.<br />
2.2. The only item acting heads may take from the head’s office is the command headset. Unless there is a dire emergency, no other items should be removed by non-antags.<br />
2.3. An acting captain may fill in for decisions that require the captain’s authorization, but may not run the station and its departments, nor are they privy to the captain's equipment or access outside of the command headset and nuke disk. The captain’s spare ID can be used to run the HoP line in the case of a non-HoP acting captain but should not leave the bridge.<br />
3). Heads of staff, acting heads of staff, and security should not abandon the station without permission from CentCom. This includes going to Lavaland, space exploration, bitrunning, and entering the gateway.<br />
<br />
4). We adhere to our own version of [space law].<br />
<br />
4.1. While the majority of this is a guideline, we expect things to be applied reasonably. Giving someone a ten-minute brig timer for slipping the captain is an example of things not being applied reasonably.<br />
4.2. Abusing crew as security is never acceptable.<br />
4.3. Authorization for permanent punishments (including executions) should only be followed if the authorization was given by the correct authority. For example, a sec officer should not comply with execution orders given by an HoS when a captain is abroad the station.<br />
4.4. Security must use nonlethal force unless there is reasonable suspicion that the other party is armed (e.g. breaking into the armory), lethal force is used upon them, or the use of nonlethal force is impossible (e.g. Hulks). See “Use of Deadly Force” under Space Law for more information.<br />
4.5 Ensuring prisoners receive timely revival and proper medical care is the responsibility of everyone in the security team. Unless an execution was authorized by the captain, this applies to any player killed by security. Detaining players who are dead or will likely die from injuries without attempting to provide medical care (e.g. throwing a prisoner in critical condition in a cell) is a violation of 4.2. See “Prisoner Medical Care” in Space law for more information. Repeated negligent deaths may result in a role ban.<br />
5). We adhere to our own version of [silicon and drone] policy.<br />
<br />
5.1 Those that upload laws to silicons are responsible for what said law causes.<br />
5.2 Ordering silicons to commit suicide or any actions that would be considered grief as a non-antag is strictly prohibited. Silicons who are given such orders should ahelp before carrying them out; however, the person giving the command will still be held responsible.<br />
6). We now adhere to our own [standard operating procedure] policy.<br />
<br />
6.1 Calling the shuttle on red alert to end the round faster despite there being no significant threats to the station will likely result in it being recalled.<br />
Antagonist/Lavaland/Ghost Policy<br />
1). Antagonists exist to move the round forward and make things interesting and fun for everyone involved. Excessively recalling the shuttle to prevent the natural end of the round in order to do your objectives should be avoided and may result in moderator intervention. If you complete your objectives, you may pray to be given additional objectives.<br />
<br />
1.1. Do not needlessly kill those you do not need to outside of your objectives and simply because you can. This includes destroying silicons. Things like covering up evidence, dealing with pursuing security officers, ‘Good Samaritans’ on your tail, and removing a witness, are always acceptable examples. Ahelping ideas for gimmicks may grant an exception to this.<br />
1.2. Killing players outside of rule 1.1 must directly further your goal, and you cannot permanently remove these players from the round. For example, killing an engineer to gain departmental access with the objective to steal the CE’s blueprints is acceptable. Killing an engineer for her insulated gloves or access to the prolathe without an objective in that department is not.<br />
1.3. Do not spawn camp or prevent others from entering the round safely.<br />
1.4. Do what is needed for your goals. Destroying half the station when you only need to steal research is an example of going extremely overboard. Causing chaos in a department with a bomb is okay but destroying half the station is not<br />
1.5 Team antag objectives take precedent over solo antag objectives.<br />
2). If you become an antagonist and do not wish to be one, ahelp so that we may set you up with another role and/or give your antagonist status to another player.<br />
<br />
3). Creatures and those turned into creatures maintain their antag status from their previous form. See the “Returning from the Afterlife” section for more information.<br />
<br />
4). Ghost spawner roles must follow their flavor text upon taking said role. These roles are meant to allow players to return to the game, and their slots are usually limited. Intentionally wasting spawner slots (e.g. repeatedly suiciding as spawner roles during one round) may result in a ghost role ban.<br />
<br />
5). Sentient animals, critters, and creatures are not valid to be killed by the crew simply for existing -- they are players too. However, if they are causing trouble, this protection is waived.<br />
<br />
6). Lavaland spawner roles (such as Ashwalkers and Free Golems) are meant to allow players to return to the game and are only considered valid if aggressive toward crewmembers. See the “Guide on acceptable killing” section at the end of this document.<br />
<br />
6.1. Lavaland spawners who enter the station must be peaceful and are held to stricter standards for escalation and roleplay than when on Lavaland. Spawners may not use meta knowledge to seek out the Lavaland mining base and may only enter if invited by crew members. Spawners who are hostile/ willingly impede the station are subject to a ghost role ban.<br />
6.2 Spawner roles must follow their flavor text and treat their spawn location (e.g. Charlie station) with the same regard as the main station. Intentionally destroying your spawn location without sufficient IC reason prevents players from rejoining the game and will result in a ghost role ban.<br />
7). Rules 6 and 6.1 do NOT apply to any Syndicate spawners. These roles are permitted to kill Nanotrasen crew members on sight and similarly may be killed by NT crew. <br />
<br />
7.1 Spawners at the Syndicate base in Lavaland are never permitted to leave their base.<br />
7.2 Spawners at the Syndicate ship are allowed to leave their base but must not seek out the Nanotrasen station. These spawners are never permitted to intentionally approach or board the NT station. If you accidentally find the NT station you are expected to leave immediately.<br />
8). If you disconnect as an antagonist, we will be forced to offer your body to ghosted players after ten minutes without reconnecting. Members of team antagonists (e.g. nuclear/clown operatives, blood brothers, head revolutionaries) must notify admins that they are leaving through ahelps.<br />
<br />
== Admin Interactions ==<br />
0). Our staff is composed entirely of volunteers who work to make Fulp a welcoming community to all players. While it’s okay to express frustration with admin interactions, doing so in a way that is aggressive or harassing will result in a mute or a ban. If you harass staff, expect consequences to come as a result of your actions or your issue to be discarded.<br />
<br />
0.1). Do not send unsolicited Direct Messages to staff via Byond. If you need to contact staff, verify on Discord and use the #ask-mods channel or the forums. Sending unsolicited DMs via Byond may result in a permaban.<br />
<br />
1). Ahelp as soon as possible. Waiting can make things harder or even impossible to look into. We do not know what we do not see. The moderation team exists to help. Ahelping can bring things to our attention we may miss.<br />
<br />
2). Provide as many details as possible. Generally, your ahelp should include the name of the offending character and a brief description of what happened. This makes it easier for us to figure out an issue.<br />
Bad ahelp: Sec arrested me for no reason<br />
Good ahelp: Sec officer John Smith put me in a cell with no timer for trespassing into science, and I’ve been here for 5 minutes already.<br />
<br />
3). While players are encouraged to ahelp problems they have in-round, misusing ahelps (e.g. complaining about round or asking to be an antag) is not acceptable. If your ticket is rejected or marked IC and you wish to have it reviewed, file a staff report on the forums as additional tickets regarding the same issue will be ignored. Misusing ahelps clutters tickets, and repeatedly doing so may result in notes or a ban.<br />
<br />
4). Do not lie in ahelps as we can verify any claims made via player logs. If you are unsure of how an event transpired, you are encouraged to look through your logs for verification. Lying in ahelps will result in a ban.<br />
<br />
5). Respond to Admin PMs as soon as possible so we know you aren’t ignoring the ticket. Even a ‘one moment’ will suffice.<br />
<br />
6). In-character communication with admins should be done through the prayer option under the IC tab. Prayer can be used to obtain in-game items at the admin’s discretion. This includes TC trades. Ahelps should not be used in place of prayers for IC issues. Praying does not guarantee a response and may result in being smited. Spamming prayers may result in a mute/smiting. Do not ahelp if your prayer is not answered.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Admin interaction !! Event<br />
|-<br />
| Ahelp || Other players breaking the rules (e.g. suspected self-antag, IC in OOC, hate speech, theft of dept equipment, etc.), reporting a bug/ glitches, leaving as a dept head, asking for antag status to be removed, confirming rules about large-scale antag actions<br />
|-<br />
| Mhelp || Asking about game mechanics<br />
|-<br />
| Prayer || TC trades, requesting items, asking for antag status when not already an antag, asking for additional objectives<br />
|-<br />
| Forum Post || Reporting other players when no admins are online, ban appeals<br />
|}</div>Anetterahttps://wiki.fulp.gg/index.php?title=Server_Rules&diff=6Server Rules2025-11-07T12:42:55Z<p>Anettera: Created page with "For more in-depth explanations of rules and FAQ, please read the Rule precedents document Core Rules 0). Take these rules as they are to be intended and not as they are written literally. 0.1. Rule skirting, lawyering, and/or being a dick for the sake of ruining others' experiences can become a bannable offense if occurring regularly. 1). Fulpstation is a Medium Roleplay server. We define this as performing your assigned duties. This is a ‘do your job’ server. This..."</p>
<hr />
<div>For more in-depth explanations of rules and FAQ, please read the Rule precedents document<br />
<br />
Core Rules<br />
0). Take these rules as they are to be intended and not as they are written literally.<br />
0.1. Rule skirting, lawyering, and/or being a dick for the sake of ruining others' experiences can become a bannable offense if occurring regularly.<br />
<br />
1). Fulpstation is a Medium Roleplay server. We define this as performing your assigned duties. This is a ‘do your job’ server. This means it is important to do what is expected out of your department and not what would be expected out of other departments.<br />
<br />
1.1. If you want to build mechs, play roboticists. If you want to hunt for antags and uphold space law, play security. This is to ensure all players can have a fun shift and have a role to fill. This is not intended to limit what is possible on the server but to provide structure for everyone.<br />
1.2. Opt-in for roles you intend to play or seek an IC way to change your job. Failure to attempt to do the most basic of duties for your role may result in a job ban. [A list of basic duties can be found here]. While transferring to another department and doing another job is acceptable, being a know it all for multiple departments is not.<br />
1.3. If you do not wish to be a role or antag, ensure you set it to never in your occupation preferences and/or request a ban from said role or antag. Changing your job preference settings to “return to lobby if preferences unavailable” will prevent you from being assigned a random position.<br />
1.4. Players' knowledge of the game is not limited by their job. However, using knowledge of antags and round types without IC justification is considered metagaming. For example, it is acceptable for a clown to know how to build a conveyor belt for a prank. It is not acceptable for a clown to know that xenomorphs are weak to fire and rush to make a flamethrower.<br />
<br />
2). Malicious acts like griefing, metagaming, killbaiting, banbaiting, powergaming, self-antagging, greytiding, validhunting (along with calling people and silicons valid without proper cause), and exploiting can become bannable offenses if occurring regularly or if the infraction is serious enough.[See the glossary here].<br />
<br />
2.1. Multi keying, ban evasion, cheating, blatant intent to grief, and RDMing are all permanent ban offenses.<br />
2.2. If playing with someone that is at the same location as you, alert us so we may take note of it. Otherwise, we may assume they are you.<br />
2.3. Antag rolling, or round-start suicides that appear to be antag rolling, may result in an antag ban if occurring frequently enough<br />
3). Sexual content is strictly prohibited. This includes content like photos/websites/Erotic Role Play (ERP) and applies to the server, Discord, and forums. Sending unsolicited sexual content to another player via direct messages will also result in a ban.<br />
<br />
4). Hate speech is strictly forbidden. Using the Discord, the SS13 server, or the forums to threaten a group of people or to propagate racial and otherwise prejudiced slurs or stereotypes is a bannable offense. We take this seriously and want to create a server that is welcoming to all people. This includes variations or misspellings of slurs. SS13 is your character’s workplace; if you would get fired for saying it in a modern-day office setting, you shouldn’t be saying it on the server.<br />
<br />
5). Discrimination towards in-game sub-species and silicons is acceptable in moderation, but attacking them or otherwise preventing them from playing the round is not. Additionally, terms that are based on real-life slurs are not allowed.<br />
<br />
6). Do not spam, advertise, or paste lengthy and/or inappropriate copypastas.<br />
<br />
7). Keep IC content in IC, and OOC content in OOC. This means no IC in OOC (ick ock) and vice versa.<br />
<br />
8). Revealing information about the current round in OOC, Discord, or the forums (metacomming) is strictly prohibited. Wait until after the Round End screen to discuss the round or file a report.<br />
<br />
9). Avoid antagonizing players and staff via the Discord, Forums, or through OOC/deadchat. While expressing frustration about in-round events is acceptable, ganging up on fellow players is not.<br />
<br />
9.1 - IC insults are fine within reason, but harassing other players repeatedly throughout the round or using OOC insults IC is not.<br />
10). Each round exists independently of all other rounds. While friendships persisting through rounds is okay, using experiences from other rounds to give an advantage or disadvantage to other players is not permitted.<br />
<br />
Returning From The Afterlife<br />
1). Do not use information obtained while dead or from a previous life upon returning to the land of the living.<br />
<br />
2). Cyborgs and other creatures that are created with a character’s organic brain (i.e. not a positronic brain) retain all knowledge of events that happened before the procedure while they were living. Rule 1 still applies to information obtained while dead.<br />
<br />
2.1. Antagonists who undergo forced cyborgization retain their antag status and objectives but must prioritize their law set. This prevents borgs from attempting to be unborged in most circumstances.<br />
SSD/AFK Player Interactions<br />
Note: SSD characters are players who are disconnected or AFK. It is possible for players to return to SSD bodies. Players become catatonic when they take a ghost spawner role or commit suicide. Players are NOT able to return to these bodies without admin intervention.<br />
<br />
1). Do your best not to interact negatively with SSD/AFK players. Moving them to safety is acceptable, but killing, looting, or otherwise griefing them while they are away is not.<br />
<br />
1.1. If the player in question is an antag’s target or they are being secured by security, interactions to finish what is required of your duties/objectives are always acceptable.<br />
1.2. Ahelping about an SSD/AFK player may grant an exception to this rule.<br />
2). Rule 1 does not apply to players that are catatonic. Although needlessly killing or harming catatonic players is discouraged (and will probably get you hunted by security), harvesting their organs to save another player is acceptable.<br />
<br />
Escalation Clause<br />
1). Escalation resulting in murder is only acceptable within reason. If your life is in danger, you can always fight back lethally, or if a conflict with the other player has lasted throughout the round with multiple fights. In most cases, fights end when one party enters critical condition or is otherwise incapacitated. Theft, break-ins, demotions, destruction of property, getting pranked and other inconveniences are not reasons to murder another player or put them into a life or death situation. Ask what a rational person would do and act accordingly.<br />
<br />
1.1. Expect to receive the same kind of treatment and escalation that you give out.<br />
1.2. If the other party during an altercation dies or is seriously injured, work to get them healed or revived.<br />
2). If you act like an antagonist, expect to be treated like one and be held liable for your actions both IC and by admins.<br />
<br />
3). Over-escalation of fights is also unacceptable. Over-escalation is, in short, doing more damage to someone than is required to resolve an issue or using violence instead of words to solve an issue. <br />
<br />
Examples being: <br />
<br />
Killing someone during a dangerous fight when they could be placed into crit and healed or ignoring the opportunity to use non-lethal force when available.<br />
Placing someone someplace they will surely die, like disposals when crit, space, in shuttle landing zones, or other gibbers.<br />
Delimbing someone for doing minimal damage to you.<br />
Breaking into a department and attacking someone when they try to remove you from the department instead of asking for what is needed.<br />
3.1). While using lethal force is allowed in some cases of self-defense, actions that jeopardize the lives of other players or could cause massive damage to the station (e.g. max caps) is considered over escalation, and you will be held accountable for deaths that occur due to negligent behavior. This rule applies when committing acts that will likely cause mass casualties to eliminate antagonists.<br />
<br />
Command/Security/Silicon Responsibilities<br />
1). The following jobs: Captain, HOP, HOS, CE, RD, CMO, QM, and AI should ahelp when they need to leave. This is to ensure a replacement can be installed (Your body will be offered to ghosts or your character will be deleted and the job slot reopened) for continuity of the round. Your intent to leave should also be made known to other command staff if possible. If no staff are available to offer your body to ghosts, you should designate another player as your replacement after ahelping.<br />
<br />
1.1. These roles must exhibit some competency. Lack of this can result in a job ban. Command roles are designed to lead and manage departments first and do second. They are not intended to become do-it-all members of their departments.<br />
1.2. Crew promoted to acting heads of staff must step down when an official head of staff arrives at the station. This is to prevent confusion with the chain of command when the new player arrives.<br />
2). In the absence of a captain and CentCom appointed acting captain, the Head of Personnel or Head of Security must serve as acting captain or split the duties of the captain between themselves. In the absence of a captain and CentCom appointed acting captain, HoP, and HoS, the other command staff have equal standing in determining a new acting captain among themselves.<br />
<br />
2.1. Only command staff may serve as acting captain. Acting departmental heads and regular crew may not serve as acting captain.<br />
2.2. The only item acting heads may take from the head’s office is the command headset. Unless there is a dire emergency, no other items should be removed by non-antags.<br />
2.3. An acting captain may fill in for decisions that require the captain’s authorization, but may not run the station and its departments, nor are they privy to the captain's equipment or access outside of the command headset and nuke disk. The captain’s spare ID can be used to run the HoP line in the case of a non-HoP acting captain but should not leave the bridge.<br />
3). Heads of staff, acting heads of staff, and security should not abandon the station without permission from CentCom. This includes going to Lavaland, space exploration, bitrunning, and entering the gateway.<br />
<br />
4). We adhere to our own version of [space law].<br />
<br />
4.1. While the majority of this is a guideline, we expect things to be applied reasonably. Giving someone a ten-minute brig timer for slipping the captain is an example of things not being applied reasonably.<br />
4.2. Abusing crew as security is never acceptable.<br />
4.3. Authorization for permanent punishments (including executions) should only be followed if the authorization was given by the correct authority. For example, a sec officer should not comply with execution orders given by an HoS when a captain is abroad the station.<br />
4.4. Security must use nonlethal force unless there is reasonable suspicion that the other party is armed (e.g. breaking into the armory), lethal force is used upon them, or the use of nonlethal force is impossible (e.g. Hulks). See “Use of Deadly Force” under Space Law for more information.<br />
4.5 Ensuring prisoners receive timely revival and proper medical care is the responsibility of everyone in the security team. Unless an execution was authorized by the captain, this applies to any player killed by security. Detaining players who are dead or will likely die from injuries without attempting to provide medical care (e.g. throwing a prisoner in critical condition in a cell) is a violation of 4.2. See “Prisoner Medical Care” in Space law for more information. Repeated negligent deaths may result in a role ban.<br />
5). We adhere to our own version of [silicon and drone] policy.<br />
<br />
5.1 Those that upload laws to silicons are responsible for what said law causes.<br />
5.2 Ordering silicons to commit suicide or any actions that would be considered grief as a non-antag is strictly prohibited. Silicons who are given such orders should ahelp before carrying them out; however, the person giving the command will still be held responsible.<br />
6). We now adhere to our own [standard operating procedure] policy.<br />
<br />
6.1 Calling the shuttle on red alert to end the round faster despite there being no significant threats to the station will likely result in it being recalled.<br />
Antagonist/Lavaland/Ghost Policy<br />
1). Antagonists exist to move the round forward and make things interesting and fun for everyone involved. Excessively recalling the shuttle to prevent the natural end of the round in order to do your objectives should be avoided and may result in moderator intervention. If you complete your objectives, you may pray to be given additional objectives.<br />
<br />
1.1. Do not needlessly kill those you do not need to outside of your objectives and simply because you can. This includes destroying silicons. Things like covering up evidence, dealing with pursuing security officers, ‘Good Samaritans’ on your tail, and removing a witness, are always acceptable examples. Ahelping ideas for gimmicks may grant an exception to this.<br />
1.2. Killing players outside of rule 1.1 must directly further your goal, and you cannot permanently remove these players from the round. For example, killing an engineer to gain departmental access with the objective to steal the CE’s blueprints is acceptable. Killing an engineer for her insulated gloves or access to the prolathe without an objective in that department is not.<br />
1.3. Do not spawn camp or prevent others from entering the round safely.<br />
1.4. Do what is needed for your goals. Destroying half the station when you only need to steal research is an example of going extremely overboard. Causing chaos in a department with a bomb is okay but destroying half the station is not<br />
1.5 Team antag objectives take precedent over solo antag objectives.<br />
2). If you become an antagonist and do not wish to be one, ahelp so that we may set you up with another role and/or give your antagonist status to another player.<br />
<br />
3). Creatures and those turned into creatures maintain their antag status from their previous form. See the “Returning from the Afterlife” section for more information.<br />
<br />
4). Ghost spawner roles must follow their flavor text upon taking said role. These roles are meant to allow players to return to the game, and their slots are usually limited. Intentionally wasting spawner slots (e.g. repeatedly suiciding as spawner roles during one round) may result in a ghost role ban.<br />
<br />
5). Sentient animals, critters, and creatures are not valid to be killed by the crew simply for existing -- they are players too. However, if they are causing trouble, this protection is waived.<br />
<br />
6). Lavaland spawner roles (such as Ashwalkers and Free Golems) are meant to allow players to return to the game and are only considered valid if aggressive toward crewmembers. See the “Guide on acceptable killing” section at the end of this document.<br />
<br />
6.1. Lavaland spawners who enter the station must be peaceful and are held to stricter standards for escalation and roleplay than when on Lavaland. Spawners may not use meta knowledge to seek out the Lavaland mining base and may only enter if invited by crew members. Spawners who are hostile/ willingly impede the station are subject to a ghost role ban.<br />
6.2 Spawner roles must follow their flavor text and treat their spawn location (e.g. Charlie station) with the same regard as the main station. Intentionally destroying your spawn location without sufficient IC reason prevents players from rejoining the game and will result in a ghost role ban.<br />
7). Rules 6 and 6.1 do NOT apply to any Syndicate spawners. These roles are permitted to kill Nanotrasen crew members on sight and similarly may be killed by NT crew. <br />
<br />
7.1 Spawners at the Syndicate base in Lavaland are never permitted to leave their base.<br />
7.2 Spawners at the Syndicate ship are allowed to leave their base but must not seek out the Nanotrasen station. These spawners are never permitted to intentionally approach or board the NT station. If you accidentally find the NT station you are expected to leave immediately.<br />
8). If you disconnect as an antagonist, we will be forced to offer your body to ghosted players after ten minutes without reconnecting. Members of team antagonists (e.g. nuclear/clown operatives, blood brothers, head revolutionaries) must notify admins that they are leaving through ahelps.<br />
<br />
Admin Interactions<br />
0). Our staff is composed entirely of volunteers who work to make Fulp a welcoming community to all players. While it’s okay to express frustration with admin interactions, doing so in a way that is aggressive or harassing will result in a mute or a ban. If you harass staff, expect consequences to come as a result of your actions or your issue to be discarded.<br />
<br />
0.1). Do not send unsolicited Direct Messages to staff via Byond. If you need to contact staff, verify on Discord and use the #ask-mods channel or the forums. Sending unsolicited DMs via Byond may result in a permaban.<br />
<br />
1). Ahelp as soon as possible. Waiting can make things harder or even impossible to look into. We do not know what we do not see. The moderation team exists to help. Ahelping can bring things to our attention we may miss.<br />
<br />
2). Provide as many details as possible. Generally, your ahelp should include the name of the offending character and a brief description of what happened. This makes it easier for us to figure out an issue.<br />
Bad ahelp: Sec arrested me for no reason<br />
Good ahelp: Sec officer John Smith put me in a cell with no timer for trespassing into science, and I’ve been here for 5 minutes already.<br />
<br />
3). While players are encouraged to ahelp problems they have in-round, misusing ahelps (e.g. complaining about round or asking to be an antag) is not acceptable. If your ticket is rejected or marked IC and you wish to have it reviewed, file a staff report on the forums as additional tickets regarding the same issue will be ignored. Misusing ahelps clutters tickets, and repeatedly doing so may result in notes or a ban.<br />
<br />
4). Do not lie in ahelps as we can verify any claims made via player logs. If you are unsure of how an event transpired, you are encouraged to look through your logs for verification. Lying in ahelps will result in a ban.<br />
<br />
5). Respond to Admin PMs as soon as possible so we know you aren’t ignoring the ticket. Even a ‘one moment’ will suffice.<br />
<br />
6). In-character communication with admins should be done through the prayer option under the IC tab. Prayer can be used to obtain in-game items at the admin’s discretion. This includes TC trades. Ahelps should not be used in place of prayers for IC issues. Praying does not guarantee a response and may result in being smited. Spamming prayers may result in a mute/smiting. Do not ahelp if your prayer is not answered.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Admin interaction !! Event<br />
|-<br />
| Ahelp || Other players breaking the rules (e.g. suspected self-antag, IC in OOC, hate speech, theft of dept equipment, etc.), reporting a bug/ glitches, leaving as a dept head, asking for antag status to be removed, confirming rules about large-scale antag actions<br />
|-<br />
| Mhelp || Asking about game mechanics<br />
|-<br />
| Prayer || TC trades, requesting items, asking for antag status when not already an antag, asking for additional objectives<br />
|-<br />
| Forum Post || Reporting other players when no admins are online, ban appeals<br />
|}</div>Anettera