User:PowerfulBacon: Difference between revisions

From BeeStation Wiki
Jump to navigation Jump to search
No edit summary
(43 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{JobPageHeader
{{JobPageHeader
|headerbgcolor = #BE8700
|headerbgcolor = purple
|headerfontcolor = black
|headerfontcolor = white
|stafftype = ENEMY
|stafftype = HEAD
|imagebgcolor = #E6A500
|imagebgcolor = #cc9966
|img_generic =  
|img_generic = Generic_shaft.png
|img = servant_of_ratvar.png
|img = Lava_miner.png
|jobtitle = Servant of Ratvar
|jobtitle = Head Developer
|access = Maintenance
|access = Everything
|additional = Anywhere you can Warp or fabricate to
|difficulty = Extremely Hard
|difficulty = Medium to Hard
|superior = Project Lead/Host
|superior = Ratvar
|duties = Manage design direction, recruit maintainers, make sure the GitHub is running smoothly.
|duties = Forget to toggle your chameleon jumpsuit, don't set up any power generation, get crushed by an angry mech
|guides = [[Non-Admin Staff Conduct]]
|guides = This is the guide
|quote = Who the coded this like this.
|quote = "What's this lantern thi-" "QVR, URNGUR'A!!"
}}
}}


Although Nar-Sie is powerful in her own right, she has a mortal enemy: Ratvar, imprisoned ages ago in a conflict and endlessly seeking out freedom. Trapped in a place that none can enter or leave, Ratvar has enlisted the aid of (unwilling) servants such as yourself to free him.
Guide to being the Head-Developer, this is kind of where I try to right down things I learnt from experience in a guide, however I have to say almost everything learnt is through experience and is hard to convey in a document written in a few hours.
 
If you're one of these servants and you have no idea what to do, you've come to the right place.
 
== Introduction and Key Points ==
 
Despite the similar name, clockwork cult is nothing like the blood cult of Nar-Sie. While they both involve conversion (being cults) and both of their ultimate goals are to summon their respective gods, the similarities end there. While the blood cult is focused on sabotage, chaos, and stealth due to their status as normal crew, the servants of Ratvar need to worry about no such thing.
 
As a servant, you start on a z-level entirely separate from the station, called the City of Cogs (or Reebe, if you prefer.) This place can't normally be accessed by the station crew until a certain point, and comes outfitted with facilities for spying on, listening to, and getting onto the station, as well as disguises, spare materials, and an infirmary for healing yourself and fellow servants. Most importantly, it houses the '''Ark of the Clockwork Justiciar''', which you will need to defend.
 
From the start of the round, the Ark has a countdown timer between 30 and 35 minutes. Once this time is up, the crew will be made aware of your presence, and all servants will be transported to and prevented from leaving Reebe; then, after a five-minute grace period, portals will open up on the station and allow the crew access to Reebe, from an area in the south that no servants can access. ''As a servant, your goal is to build defenses and sabotage the station to protect the Ark until it activates.''
 
While such a task seems very daunting, rest easy! As a servant, you have a wide variety of tools at your disposal to make defending the Ark as painless as possible.
 
=== The Clockwork Slab [[File:clockwork_slab.gif]] ===
 
If you have experience with the blood cult, you can think of the clockwork slab as your version of a tome. It is the essential servant tool; it contains all of your special abilities as a servant, and you should have it on your person at all times.
 
The clockwork slab has several functions:
* '''Recital''' lets you recite ''scripture,'' the clockwork cult's special powers and abilities. Most structures come from scripture.
* '''Recollection''' displays an in-game guide for being a servant. You can toggle freely between this and Recital.
* '''Up to Five Quickbind action buttons''' allow you to recite scripture without opening the slab interface. You can bind a scripture by clicking the Quickbind button next to its "Recite" button.
 
Clockwork slabs also generate a very small amount of power every second. ''Every human servant should have a slab!'' They're the key to any cult's success and you should have one at all times.
 
=== Your HUD [[File:Clockinfo.png|32px]] [[File:Hierophant_network.png|32px]] ===
 
As a servant, you'll have several elements on your HUD that are all very important.
 
[[File:Clockinfo.png|32px]] The '''global records display''' can be found in the top-right corner. Hovering over it will give you a short rundown of the status of the entire cult, including number of servants, stored power, and the Ark time left for its current phase. You should refer to this often to get a feeling for the state of your cult.
 
 
 
[[File:Hierophant_network.png|32px]] The '''Hierophant Network''' is '''''INCREDIBLY IMPORTANT!''''' Using it will allow you to send messages to all other servants, regardless of distance. Use this often to stay coordinated. Note that using it will make you whisper, so don't use it next to anyone who shouldn't be hearing you.
 
=== Power ===
 
Servants don't use their own blood to power their magic like Nar-Sie's cult. Instead, they use power, measured in Watts like normal electricity. Just any power doesn't work for servants' tools, though. Power can be generated in various ways through different items and structures. Ensuring that you have a healthy supply of power is both easy to do and critically important to succeed as a servant.
 
Power is used by many structures, and it is used to power all scripture. Additionally, reaching certain power thresholds will unlock new tiers of scripture!
'''50 kW''' unlocks the Script tier.
'''100 kW''' unlocks the Application tier,
 
=== The Eminence ===
 
The Eminence is your leader. Elected by the servants through the Eminence spire, they are not a normal servant; instead, they are invisible, incorporeal, and can only interact in very limited ways. Anything they say is relayed to all servants in large text, and their goal is to serve as overwatch, coordinator, and leader.
 
The Eminence can travel between the station and Reebe at will, and can move freely as an all-seeing eye. Holy water will block its path, and it cannot enter the Chapel, but it is otherwise unrestricted. Note that it can't understand anything said stationside unless war is declared, meaning that while it can see movements and planning, it cannot overhear what people are discussing.
 
The Eminence can left click on certain objects to have a special interaction with them. Click on a door to open it for your cultist buddies, or click on a servant to access a variety of different abilities.
 
{| class="wikitable" border="3" cellspacing="0" cellpadding="5"
! style='background-color:#E6A500;' width='32px'|Icon
! style='background-color:#E6A500;' width='80px'|Name
! style='background-color:#E6A500;' width='659px'|Description
! style='background-color:#E6A500;' width='70px'|Cooldown
|- style="text-align: center;"
![[File:Abscond.png]]
|'''Linked Abscond'''
|Returns the targetted servant to Reebe. Anything the mob is dragging will be recalled too. The target does not require a slab, but needs to stand still for 7 seconds. Has an extremely log cooldown, but can get servants out of a pinch.
|600 seconds
|- style="text-align: center;"
![[File:MendingMantra.png]]
|'''Purge Reagents'''
|Removes all chemicals from the target's bloodstream. Useful for clearing holy water from servants being deconverted.
|30 seconds
|}
 
Finally, once per round, the Eminence can activate a mass recall. After a ten-second windup, coupled with a sound that all crew (servant or not) can hear, every living servant will be pulled directly to the Ark chamber.
 
== The City of Cogs and the Ark ==
 
Here is a map of the City of Cogs:
 
[[File:CityOfCogs.png|thumb]]
 
* '''The <span style='color:#FF0000'>red</span> room contains the Ark, which you need to defend.'''
* '''The <span style='color:#00FF00'>green</span> room contains the observation post. This is extremely important as the camera consoles can be used to access the station. They can be used by both servants and cogscarabs, however the cogscarabs will be extremely obvious on the station and are very weak.'''
* The <span style='color:#FF6A00'>orange</span> room contains a listening outpost, containing Rat'varian intercoms and a hierophant relay. In practise this room will be of little use to you since most of the time you will be out converting or building defences.
* The <span style='color:#00FFFF'>cyan</span> room contains a medical area, containing 4 sleepers which can inject any chemical into servants, as well as 2 standard medkits. There is a magic mirror on the northeastern wall of the medical room, which can be used to change your race to fit in better with the crew (or become a plasma-man and burn to death immediately).
* The <span style='color:#0094FF'>blue</span> room contains the storage area. There are a few clockwork slabs as spares here as well as 2 replica fabricators which can be used to summon brass for constructing defences.
 
=== The Ark ===
 
The Ark spawns at roundstart at the northernmost point in Reebe. As a servant, your ultimate goal is to defend it until activation (which occurs automatically when you convert enough servants or can be opened by having a set amount of servants stand around it while summoning 'Ark Invigoration'.) ''Defend the Ark with your life'' - if the Ark is destroyed, ''the round ends instantly with a cult loss.'' If it completes its summoning, however, it will result in a cult win and a brief period of revelation during which the cult and its servants are made unstoppable by the presence of Ratvar.
 
The Ark has five "phases", listed below. In each phase check your global info alert to see the remaining time until its activation.
 
{| class="wikitable" border="3" cellspacing="0" cellpadding="5"
! style='background-color:#E6A500;' width='96px'|Appearance
! style='background-color:#E6A500;' width='150px'|Duration(s)
! style='background-color:#E6A500;' width='400px'|Description
|- style="text-align: center;"
![[File:Arkhalted.png]]
Build Phase<br>
Prep Phase
|As long as it takes you to convert enough servants (charge-up)<br>5 minutes (grace period)
|The Ark starts in this state, during which it is silent. This entire phase marks the time during which the servants should build fortifications and actively prepare to defend the Ark. After the first phase passes, there is a 30-second warning for all servants to get back to Reebe. Once this time is up, ''all servants will become marked and visible to all non-servants, and a station-wide announcement will inform the crew of the Ark's presence.'' There is then a five-minute grace period during which neither side can attack, for servants to finalize preparations and the crew to get ready for the assault.
|- style="text-align: center;"
![[File:Arkopening.gif]]
Defense Phase
|4 minutes
|When this phase begins, portals to Reebe will open up everywhere across the station in nearly every room over a one-minute timespan. Crew can enter these portals to emerge in one of the three spawn rooms, and cannot return to the station. This phase consists of the crew's first massive assault on Reebe, and is generally the hardest phase as the crew is at full strength.
|- style="text-align: center;"
![[File:Arkactive.gif]]
Assault Phase
|4 minutes
|This timespan marks the middle of the crew's attack period. Any stragglers from the station have likely ended up on Reebe by this point (as well as anyone who took extra time to arm themselves) and will be actively trying to kill you. If you managed to fend off the initial assault, the worst should be over, but always keep an eye out for one-man armies.
|- style="text-align: center;"
![[File:Arkclosing.gif]]
Cleanup Phase
|2 minutes
|If you've made it to this point, congratulations; your victory is almost certainly assured by now. At this point, the crew has likely been butchered, converted, or both, and there is little to no resistance remaining to attempt to stop the Ark. During this lull, you should heal or revive any dead or dying servants, destroy any enemy corpses with vitality matrices, repair structures, and ensure nobody sneaks up on the Ark.
|}
 
== Scriptures ==
 
Scripture are the unique powers that clockwork cultists possess. They cost power to consume and vary widely in effects; from healing allies to creating power generators to building defenses, they are one of your most vital tools as a servant, and secondary only to teamwork in ensuring your victory. To recite scripture, use your clockwork slab and make sure you have the Recital tab open.
 
Scripture is divided into three different groups: Servitude, Preservation and Structures. To use scriptures of any tier, you must first unlock it using 'cogs' - A currency unlocked by placing integration cogs into APCs. Placing an integration cog into an APC that has not previously had an integration cog installed will grant you a point for unlocking new scriptures, and will also have the added benefit of generating power.
 
=== Servitude ===
These scriptures are dedicated to the advancement of the cult, whether it be opening the gateway; converting new people or for generating power. These scruptures are the most important ones you have, and without using these it will be impossible to win.
 
{| class="wikitable" border="3" cellspacing="0" cellpadding="5"
! style='background-color:#E6A500;' width='32px'|Icon
! style='background-color:#E6A500;' width='80px'|Name
! style='background-color:#E6A500;' width='140px'|Power Cost
! style='background-color:#E6A500;' width='659px'|Description
! style='background-color:#E6A500;' width='70px'|Invocation Time
! style='background-color:#E6A500;' width='150px'|Invokers Required
! style='background-color:#E6A500;' width='50px'|Unlock Cost
|- style="text-align: center;"
![[File:Abscond.png]]
|'''Abscond'''
|5 W
|Returns you to Reebe. If you're dragging a mob behind you, they will be transported too.
|5 seconds
|1
|0 Cogs
|- style="text-align: center;"
![[File:Kindle.png]]
|'''Kindle'''
|125 W
|Stuns and mutes a target from a short-range. Will not work on the chaplain, cultists and will only have a limited effect on those with mindshields (Silencing them, but not paralyzing them).
|3 seconds + 15 seconds to use it
|1
|1 Cog
|- style="text-align: center;"
![[File:Hatefulmanacles.png]]
|'''Hateful Manacles'''
|25 W
|Applies cuffs to an adjacent target.
|1.5 seconds + 5 seconds to cuff
|1
|1 Cog
|- style="text-align: center;"
![[File:Spatialgateway.png]]
|'''Dimensional Breach'''
|5 W
|Activates the Ark, alerting the crew of the presence of the cult
|5 seconds
|6 + 1 for every 12 crew members above 18 (7 for 30 crew, 8 for 42 crew)
|0 Cogs
|- style="text-align: center;"
![[File:Sigilsubmission.png]]
|'''Sigil of Submission'''
|250 W
|Summons a sigil of submission, which will convert anyone placed on top of it to the faith of Rat'var. The sigil requires that a victim is held on top of it for 8 seconds, and will not work on mindshielded or magic-proof crew.
|5 seconds
|1
|1 Cogs
|- style="text-align: center;"
![[File:Sigilvitality.png]]
|'''Vitality Matrix'''
|400 W
|Summons a vitality matrix, which drains the life force of non-servants, and can be used to heal or revive servants. The matrix only drains the health of people that cannot be converted but is useful when combined with traps such as the spike trap, which stuns those caught by it. It will heal 5 of all damage types every 2 seconds for 5 vitality, or can revive dead servants for a vitality cost 20 + the damage the body has.
|5 seconds
|1
|2 Cogs
|}
 
=== Preservation ===
Scriptures that are dedicated to keeping you and your fellow servants alive, mainly used during the combat phase once the Ark has opened.
 
{| class="wikitable" border="3" cellspacing="0" cellpadding="5"
! style='background-color:#E6A500;' width='32px'|Icon
! style='background-color:#E6A500;' width='80px'|Name
! style='background-color:#E6A500;' width='140px'|Power Cost
! style='background-color:#E6A500;' width='659px'|Description
! style='background-color:#E6A500;' width='70px'|Invocation Time
! style='background-color:#E6A500;' width='50px'|Invokers Required
! style='background-color:#E6A500;' width='50px'|Unlock Cost
|- style="text-align: center;"
![[File:Brassspear.png]]
|'''Clockwork Armaments'''
|250 W
|Summons a set of clockwork armour and weapons. Upon invocation, you will be given an option to whether you want a spear, battle-hammer or sword. The spear has insanely high throw damage and armour penetration, the battle-hammer will push enemies back on hitting them and the sword will emit an electromagnetic pulse with a 30-second cooldown upon hitting an enemy, making it a useful tool against those with stun batons and borgs.
|2 seconds
|1
|1 Cogs
|- style="text-align: center;"
![[File:Cogscarab.png]]
|'''Summon Cogscarab'''
|500W
|Summon a Cogscarab shell, a weak drone shell useful for constructing defences while the servants convert and sabotage the crew. Cogscarabs have a 40% speed increase on all actions such as construction.
|12 seconds
|1
|5 Cogs
|- style="text-align: center;"
![[File:Clockworkmarauder.gif]]
|'''Summon Clockwork Marauder'''
|8kW
|Summons a Clockwork Marauder, a powerful warrior that can deflect ranged attacks.
|30 seconds
|1
|6 Cogs
|- style="text-align: center;"
![[File:Sentinelscompromise.png]]
|'''Sentinel's Compromise'''
|80 W
|Heals all damage loss on a target converting it back as 50% toxin loss to the invoker. Additionally heals all holy water from a target, sets their nutritional level to full, cures them of blindness, dizziness and blurriness cures nearsightedness, removes hallucinations and cures husks.
|1 seconds + 8 seconds to use
|1
|1 Cog
|- style="text-align: center;"
![[File:Vanguard.png]]
|'''Vanguard'''
|150 W
|Provides the user with 30 seconds of stun immunity, but half of the stun absorbed will be applied at once, knocking you unconscious if you receive more than 15 seconds of stuns.
|1 seconds + 30 seconds of use
|1
|1 Cog
|}
 
== Structures, Sigils, Objects, Constructs, and Cyborgs ==
 
This is a listing of the various structures and constructs available to the Servants of Ratvar.
 
=== Structures ===
 
Clockwork structures with effects become up to 50% less effective (at 25% of maximum health) as they lose health.
 
All structures can be unsecured from the floor with a wrench.<br>
This only applies to actual structures; brass windows, tables, and doors all have their own deconstruction/unsecuring steps.
 
{| class="wikitable" border="3" cellspacing="0" cellpadding="5"
! style='background-color:#E6A500;' width='32px'|Image
! style='background-color:#E6A500;' width='73px'|Name
! style='background-color:#E6A500;' width='40px'|Health
! style='background-color:#E6A500;' width='560px'|Description
! style='background-color:#E6A500;' width='280px'|Usage Tip
! style='background-color:#E6A500;' width='280px'|Deconstruction
|- style="text-align: center;"
![[File:Clockfloor.png]]
|Clockwork Floor
|N/A
|A clockwork floor produced by brass or a replica fabricator. Reebe is covered in an indestructible variety.<br>
Replica fabricators can swap between these and clockwork walls at a power cost.<br>
|Servants standing on clockwork floors heal 2 toxin damage per second.
|Can not be deconstructed.
|- style="text-align: center;"
![[File:Brass window single.png]]
|Brass Window
|80
|A window produced with brass or by a replica fabricator.
|Provides a very small amount of CV and is a reasonable barrier.
|Use a screwdriver to unfasten the window from the floor. Use a wrench to disassemble the brass window.
|- style="text-align: center;"
![[File:Brass window.png]]
|Brass Window
|120
|A full-tile window produced with brass or by a replica fabricator.
|Provides a small amount of CV and is a reasonable barrier.
|Use a screwdriver to unfasten the window from the floor. Use a wrench to disassemble the brass window.
|- style="text-align: center;"
![[File:Brass table.png]]
|Brass Table
|200
|A brass table produced with brass or by a replica fabricator.<br>
Brass Tables can be removed by welding them, then wrenching or screwdrivering them.
|Provides a small amount of CV and a place to store items.
|Use a crowbar to weaken the table. Use a welding tool to deconstruct the table.
|- style="text-align: center;"
![[File:Wallgear.png]]
|Wall Gear
|100
|A gear produced with brass, by a replica fabricator, or by breaking down a clockwork wall.<br>
Wall gears can be climbed like tables, unwrenched from the floor, and, if unsecured, deconstructed with a screwdriver.
|Wall gears are essentially clockwork girders, can be plated with brass to construct a clockwork wall.
|Use a wrench to detach the gear from the floor. Use a screwdriver to deconstruct the gear.
|- style="text-align: center;"
![[File:Brass windoor.png]]
|Brass Windoor
|200
|A windoor produced with brass or by a replica fabricator.
|Brass windoors only allow servants to pass.
|Use a screwdriver to open the maintenance panel. Use a crowbar to deconstruct.
|- style="text-align: center;"
![[File:Clockwall.png]]
|Clockwork Wall
|N/A
|A clockwork wall produced with brass or by a replica fabricator.<br>
Replica Fabricators can deconstruct clockwork walls for a refund of 1 kW power.
|Serves as a durable barrier. Can be superheated by the Eminence to prevent mechs from destroying them.
|Use a welder to weld the plating off of the wall. Afterwards, use a wrench on the resulting wall gear to detach it from the floor before using a screwdriver to deconstruct the gear.
|- style="text-align: center;"
![[File:Pinion airlock.png]]
|Pinion Airlock
|240
|A Pinion airlock produced with brass or by a replica fabricator.<br>
Pinion airlocks can be removed by wrenching them, then crowbarring the gear off.
|Pinion Airlocks are difficult to remove and only allow servants to pass.
|Use a wrench to loosen the airlock's cogwheel, then use a crowbar to deconstruct the door.
|- style="text-align: center;"
![[File:Ocularwarden.png]]
|Ocular Warden
|60
|Ocular Wardens will automatically damage a target non-servant that can see it within 3 tiles of it.<br>
If the target has x-ray vision, it will attack them through walls. If the target is carrying a bible, it will target the bible first.<br>
It deals 15 damage per second, reduced by 5% for each tile between the target and warden, and 10% for each dense object.
|Ocular wardens, while lethal and powerful, are very easily smashed. Placing them behind barricades will make them more durable, but less damaging.
|Hit it with melee weapons as they have a strong resistance to ranged fire.
|- style="text-align: center;"
![[File:Clockworkobelisk.png]]
|Abstraction Crystal
|100
|Abstraction Crystals are powerful defensive tools, allowing 2 of them to link together on-demand, allowing the user to manifest a holoform at the other.<br>
Once manifested at the other, the manifestation will be able to attack, repair and do all normal actions a human can do, even if the person who manifested at the crystal was previously a cyborg or the Eminence.<br>
Manifestations share a health pool with the abstraction crystal they are linked to, and if either die, the other will be destroyed too.<br>
When the crystal or manifestation take damage, 40% of the damage taken will be received in the form of brute damage on the user, which can be easily healed using sleepers, brute kits or Sentinel's compromise.
|Abstraction crystals are extremely powerful defensive tools, and allow servants to fight on the front lines while only taking a small amount of damage themselves. Keep the abstraction crystal protected behind some pinion airlocks, since they are particularly fragile.
|Kill the active hologram or destroy the crystal by smashing it.
|- style="text-align: center;"
![[File:Prolongingprism.png]]
|Prosperity Prism
|150
|Rapidly heals toxin damage from servants within 4 unit range of it, at a rate of 10 toxin damage per second, and will also remove all stamina damage from nearby servants every second.
|Put these near the front lines to make fellow servants resistant to stun based weapons.
|Smash it with a toolbox of +3 robusting.
|- style="text-align: center;"
![[File:Interdictionlens.png]]
|Interdiction Lens
|150
|Forces nearby non-servants within 3 tiles to walk and slows them down by 50%.<br>
Projectiles entering the field will be weakened if not fired from a servant.<br>
Mechs within range will take 25 damage per second and be drained of 1kW per second.
|Use to destroy mechs and slow down attackers. Works through walls and doesn't require direct line of sight.
|Smash it with a toolbox of +3 robusting.
|- style="text-align: center;"
![[File:Stargazer.png]]
|Stargazer
|100
|Applies a random effect to a weapon placed on top of it.<br>
* <b>Tightened</b>: You can no longer drop the item.<br>
* <b>Sharpened</b>: The item recieves +6 force.<br>
* <b>Small</b>: The weapons weight class is changed to tiny, allowing it to fit in pockets.<br>
* <b>Glow</b>: The item glows. (There is no lighting on Reebe, so this only affects the item when on the station!)<br>
* <b>Heat</b>: Item now does burn damage and has +2 force.<br>
* <b>Unbreakable</b>: The item can no longer be destroyed by normal means.<br>
* <b>Sentient</b>: The item is possessed by a ghost and can talk.<br>
* <b>Blunt</b>: The item loses 4 damage.<br>
* <b>Anti Magic</b>: The item now protects you from magic.<br>
* <b>Shungite</b>: The item protects you from EMPs and magic.
|Put a weapon on it randomly, get it stuck to your hand and be unable to drop it, cry.
|Smash it with a cakehat of +1 robusting or any other robust item.
|-
|}
 
=== Traps ===
 
Traps are useful objects produced with brass sheets. There are two types of trap: '''sender''' and '''receiver.'''<br>
'''Senders''' are objects like levers and pressure sensors. They detect certain conditions and, when those are met, send a signal to all receivers they're linked to.<br>
'''Receivers''' are the traps themselves, like brass skewers, that cause various things to occur when they receive a signal from a sender.<br>
Senders and receivers can be linked by attacking them with a clockwork slab. The Eminence can also trigger traps by clicking on them.<br>
Traps are built from brass sheets, and can be instantly deconstructed with a wrench.
 
{| class="wikitable" border="3" cellspacing="0" cellpadding="5"
! style='background-color:#E6A500;' width='32px'|Image
! style='background-color:#E6A500;' width='73px'|Name
! style='background-color:#E6A500;' width='40px'|Health
! style='background-color:#E6A500;' width='560px'|Description
! style='background-color:#E6A500;' width='280px'|Usage Tip
|- style="text-align: center;"
![[File:Brass lever.png]]
|Sender - Lever
|75
|The most simple sender. Activates when clicked.
|It's a lever. There's nothing else to it.
|- style="text-align: center;"
![[File:Pressure sensor.png]]
|Sender - Pressure Sensor
|5
|Pressure sensors trigger when a non-servant walks over them. They are mostly translucent in-game.<br>
|When built, pressure sensors will link with any receivers they're built on top of, to save time.
|- style="text-align: center;"
![[File:Brass repeater.png]]
|Sender - Repeater
|15
|Repeaters can be toggled on and off. When active, they will send a signal once every second.
|Useful for traps that perform well when they receive signals at constant intervals.
|- style="text-align: center;"
![[File:Brass skewer.png]]
|Receiver - Brass Skewer
|40
|A deadly spear trap. When not extended, it's difficult to see, appearing only a small, dark circle on the floor.<br>
When activated, it will become dense and block passage. If someone is standing on it, it will impale them, dealing heavy damage and hoisting them into the air.<br>
People impaled on skewers can use items and weapons, but not destroy the spear. They can resist to pull themselves off after 30 seconds, but can be helped off by another person after 6.<br>
Cyborgs will not be impaled, but will take massive damage.<br>
There must be a gap of one tile between any two skewers.
|Combines well with pressure sensors, for obvious reasons.
|- style="text-align: center;"
![[File:Steam vent.png]]
|Receiver - Steam Vent
|100
|A vent that taps into the machinery of Reebe and vents excess steam when toggled.<br>
While venting steam, the vent cannot be seen past, and slightly wets anyone walking over it. It has no other effects.<br>
Steam vents cannot be placed directly adjacent to each other on cardinal directions; diagonally adjacent is fine.
|Especially powerful when combined with wraith spectacles!
|-
|}
 
=== Sigils ===
 
Sigils, while effective as unexpected traps, are incredibly fragile and can be easily removed by any non-servant hitting them with an item or simply striking them with an open hand.
 
You can stack multiple sigils of different types on a single tile, which allows you to create conversion traps, damage traps, or damaging conversion traps.
 
{| class="wikitable" border="3" cellspacing="0" cellpadding="5"
! style='background-color:#E6A500;' width='32px'|Image
! style='background-color:#E6A500;' width='80px'|Name
! style='background-color:#E6A500;' width='605px'|Description
! style='background-color:#E6A500;' width='274px'|Usage Tip
|- style="text-align: center;"
![[File:Sigiloftransgression.png]]
|Sigil of Transgression
|Sigils of Transgression are nearly invisible, and, when crossed by a non-Servant, will lock that non-Servant in place for about 7 seconds while emitting a bright flash that will temporarily blind non-servants lacking eye protection.<br>
The Sigil does not mute the target, and is immediately consumed when stunning a target.
|Try stacking a Sigil of Submission and a Sigil of Transgression for a conversion trap.
|- style="text-align: center;"
![[File:Vitalitymatrix.png]]
|Vitality Matrix
|Vitality Matrices, when crossed by a non-Servant, will drain them of health, which fills all Matrices with Vitality, after a brief delay.<br>
When crossed by a Servant, however, it will use drained Vitality to rapidly heal them of all damage until it runs out of Vitality. It cannot do both at once.<br>
The Vitality Matrix can also revive dead Servants at a cost of 20 Vitality plus all of that Servant's non-oxygen damage in Vitality, in addition to consuming the Matrix.
|Use the Vitality Matrix to heal usually difficult-to-remove damage such as cloneloss.
|- style="text-align: center;"
![[File:Sigil of submission.png]]
|Sigil of Submission
|Sigils of Submission, when crossed by a non-Servant, will attempt to convert them after 8 seconds if they remain on the Sigil for that time.<br>
|Both successful and unsuccessful conversion attempts will stun and mute the target and send an announcement over the Hierophant Network.
|- style="text-align: center;"
![[File:Sigiloftransmission.png]]
|Sigil of Transmission
|Sigils of Transmission can be activated to drain power from the nearby area and will power Clockwork Structures within 2 tiles.<br>
While active, it will drain power from APCs, SMES units, non-Servant cyborgs, and mechs occupied by non-Servants.<br>
The Sigil can be charged with Brass Sheets at a rate of '''250W''' per sheet.<br>
Using a Replica Fabricator on it will rapidly charge that Fabricator.
|When crossed by a Servant cyborg, it will attempt to recharge that cyborg.
|-
|}
 
=== Constructs ===
 
{| class="wikitable" border="3" cellspacing="0" cellpadding="5"
! style='background-color:#E6A500;' width='32px'|Image
! style='background-color:#E6A500;' width='73px'|Name
! style='background-color:#E6A500;' width='40px'|Health
! style='background-color:#E6A500;' width='520px'|Description
! style='background-color:#E6A500;' width='320px'|Playstyle Tips
|- style="text-align: center;"
![[File:Clockworkmarauder.gif]]
|Clockwork Marauder
|120
|Clockwork marauders are created by the scripture of the same name, and are well-rounded defensive constructs.<br>
They have a unique mechanic, called ''shield health.'' Using their shield, marauders can block projectiles.<br>
Each projectile the marauder is hit by has a 100% chance to be blocked, and will consume one shield health, regardless of damage.<br>
Once shield health expires, the shield shatters, and projectiles will damage it normally.<br>
Marauders regain one shield health every 20 seconds.
|As a marauder, you are the front line. Try to prioritize protecting your fellow servants. Don't be afraid to give your life.
|- style="text-align: center;"
![[File:Scarab.png]]
|Cogscarab
|50
|Cogscarabs are friendly helper drones that cannot leave Reebe. Two shells spawn in the camera room at the start of the round, and can be activated by any ghost. You cannot obtain cogscarabs in any other way, meaning these two are the only two.<br>
Scarabs are outfitted with a full set of tools and a replica fabricator. Their primary goal is to build defenses, and they are physically incapable of leaving the City of Cogs.<br>
They can wield and use any kind of weapon, but can't fire guns, move slowly, and die fast.<br>
Activating a cogscarab shell during a non-clockwork cult round will allow you infinite power and the ability to recite scripture. This is for players to learn the ins and outs of the gamemode in a safe environment!
|Your entire purpose is to build. If power generation is insufficient, make do by cannibalizing unnecessary structures for brass.
|-
|}
 
=== Cyborgs ===
 
{| class="wikitable" border="3" cellspacing="0" cellpadding="5"
! style='background-color:#E6A500;' width='32px'|Image
! style='background-color:#E6A500;' width='73px'|Module
! style='background-color:#E6A500;' width='280px'|Scripture
! style='background-color:#E6A500;' width='120px'|Other Tools
! style='background-color:#E6A500;' width='480px'|Playstyle Tips
|- style="text-align: center;"
![[File:RatvarStandard.png]]
|Standard
|Judicial Marker, Linked Vanguard
|Ratvarian Spear, Cyborg Fabricator
|Your main strength is in combat; Linked Vanguard allows you to charge at enemies that would normally disable you and attack them with your spear and judicial markers. However, you also have the basic construction and crit-stabilising abilities that come with your module.
|- style="text-align: center;"
![[File:RatvarEngineering.png]]
|Engineering
|Replicant, Sigil of Transmission
|Cyborg Fabricator
|As you have only relatively basic tools, your use is to, more or less, create 5 layers of clockwork walls around the clockcult's base.<br>
In addition, you are capable of producing power for clockwork structures and other cyborgs.
|- style="text-align: center;"
![[File:RatvarJanitor.png]]
|Janitor
|Replicant, Sigil of Transgression, Ocular Warden, Mania Motor
|Cyborg Fabricator
|As a Janitor cyborg, you use is similar to an Engineering cyborg, except you create active defenses instead of passive ones.<br>
Use all of your tools to reinforce a clockcult base in conjunction with an Engineering cyborg or a helpful human Servant.
|- style="text-align: center;"
![[File:RatvarMedical.png]]
|Medical
|Linked Vanguard, Sentinel's Compromise, Vitality Matrix, Mending Mantra, Fellowship Armory
|Ratvarian Spear
|As a Medical cyborg, you exist to heal and defend other Servants; with Sentinel's Compromise you are extremely able to revive allies during combat.<br>
You're a combat medic; with Linked Vanguard and Sentinel's Compromise, you are very difficult to kill or disable while attacking with your spear.
|- style="text-align: center;"
![[File:RatvarPeacekeeper.png]]
|Peacekeeper
|Belligerent, Judicial Marker
|Ratvarian Spear
|You exist to fucking murder any enemies of Ratvar; with your combination of scripture, you are extremely suited to disabling and killing large numbers of enemies.
|- style="text-align: center;"
![[File:RatvarService.png]]
|Service
|Replicant, Tinkerer's Cache, Spatial Gateway, Fellowship Armory, Clockwork Obelisk
|Truesight Lens
|As a Service borg, you exist to assist other Servants; you can hand out slabs, make caches, equip allies with armor, and create gateways to allies or obelisks.<br>
Your biggest strength is probably communication; with a Clockwork Obelisk, you can talk in extremely large text, which is wonderful for coordinating Servants.
|- style="text-align: center;"
![[File:RatvarMiner.png]]
|Miner
|Linked Vanguard, Spatial Gateway
|Ratvarian Spear, Truesight Lens
|As a Miner cyborg, you're mostly defensive combat-based; you're able to avoid stuns with Linked Vanguard and your own kinetic accelerator.<br>
With your Truesight Lens, you can spot people assembling outside a clockcult base, or notice people with the Chameleon mutation fading out, allowing you to attack them before they realize you know they're there.
|-
|}
 
== Cult Strategy ==
 
The primary threats in the defensive phase are the advanced weapons in the armory, cargo, and science, Genetics monsters, and RCD's. One of your primary objectives should be to disrupt the production of such devices before the five minute grace period. The armory can be easily looted with an accomplice to eliminate the security robot, genetics and cargo can be subverted or destroyed, Research can be wiped with a screwdriver and teleports to three rooms, and recovery of these assets can be prevented with a trip to engineering storage.  Your teleport is basically free, abuse this as often as possible.  armory weapons are much more powerful and concealable then anything you get early in the round. Giving a taser to a convert and setting them on their friends isn't the worst way to round up more converts.


A cultist or so should spend some time building walls, defenses, and traps from the top down for when the crew attempts to invade. Each room and set of defenses and traps will serve as means to divide up the invading crew, and create advantages for those defending. At times it might be more advantageous to, when trapping a crewmember during the invasion, to attempt to convert them to the cult instead. If you're unlucky you wasted time converting someone with a mindshield implant, otherwise your numbers just grew by one, and theirs down by one!
If you don't read any of this, then remember this: '''Do not create a negative environment for coders, avoid grudges at all cost even if someone writes code that causes lots of bugs. Give them pointers for how to improve, if something doesn't fit into the game then say in the PR that it doesn't fit in the game and don't just leave it for  4 months with no review until the coder gives up and goes somewhere else.'''.


You can teleport into areas without the crew knowing by warping into airlocks. Extra points if you have kindle prepared beforehand for an instant warp-->stun. The airlock actually hides the animation of you shifting in, allowing for you to ambush and nab the HOP/HOS/Capt/whatever important target.
For some reason in Space Station 13, the Head-Developer usually is the person in charge of design and that will typically be more important than development for you, so you must be ready to take on the heavy workload and mental torment that comes with understanding the design of Space Station 13. Once you reach the point where you realise that nothing in the game works at a design level, and that all of the jobs encourage isolationism; then you are at the point where you are starting to truly understand SS13 design.


== Threats to the Enlightened ==
The true role of the head-developer is to make themselves entirely expendible. If you were to leave at any moment, then if you are doing a good job that should have very little impact on the codebase.


Although the servants of Ratvar are gifted with great power, they are still threatened by many things on the station. This can range from enemy cultists to things as simple as hard vacuum.
== Design ==
You are in charge of setting out the design precidents that will lead the server in the right direction. You aren't setting the direction that the server should go in, and shouldn't be trying to change that; the direction of the server overall is something that needs to be agreed on by all the project heads.


=== [[Blood Cult|Nar-Sian Dogs]] [[File:Cultist.png]] ===
=== Design Principles ===


The one thing that Ratvar hates more than people telling him that he has a bad name are the followers of his nemesis, Nar-Sie. Not only are Ratvar's servants incapable of converting them, but they endeavor to do the very thing that Ratvar wants to prevent: Nar-Sie's arrival into the mortal plane. The two cults are enemies of one another, serving rival gods with rival goals. As such, Ratvarian magic will be more effective against Nar-Sian cultists. The opposite is also true; much of Nar-Sie's magic is more effective against Ratvar's servants.
Here are a few things that you should try to keep in mind when designing for SS13:
* Every single change has positives and negatives. Even trivial changes that seem universally good can have long term consequences and slow mentality shifts over time which lead to undesirable states. For example, completely solving powergaming would also completely kill any form of improvisation for antagonists; completely removing all forms of cheap ways to kill people may make it more challenging for new players to play as an antagonist.
* The Head-Admins and Head-Developers are solving the same problem. They should both be talking about what the other party is doing and the Head-Developer should give input into, and understand, the rules.
* Good rules go hand-in-hand with the mechanics of the game. Bad rules go against what the mechanics encourage you to do. If there is a rule, or a proposed rule, that goes against how the players are being encouraged to play then something probably needs changing to emphasise the rule in the game. I like to think of this as the rules being 'diagetic', part of the game-world as players shouldn't be caught off-guard when they do something wrong; the rules exist to remove the bad-actors from the game, if there is something that people are regularly doing despite not being bad actors then perhaps something needs to change.
* Try to play like a normal player would and try to keep the mentality of a normal player. Don't design everything around the requirement that everyone using a system must be a perfect player who always roleplays no-matter what.
* The server wants to be a roleplay server. This doesn't mean roleplay is the only thing that you should care about, gameplay and fun are also very important and without variation and some amount of chaos in what happens in the round, there are no events that are actually worth roleplaying.
* Changes in the game will have slow psychological effects on the playerbase, which may not have an immediate impact but may cause a shift in player mentality over time.
* Everyone who actively participates in the forums/discord will be an experienced player, remember to consider the experience of the newer player as well when it comes to balancing/changing things.
* If you are making a poll, text answers are by far the most useful fo getting any meaningful data out. If you are trying to analyse a testmerge, most of the time its better to just observe players and see how they are playing rather than to use a poll however.
* On that note, make sure you observe and watch people frequently! When you play, you may feel that something is unfair but are heavily biased and will not consider how the other player was feeling. You ```must``` observe players regularly and watch them die to things that seem unfair, when you see this happening, then you know that changes might need to be made in that area. It is specifically useful when you are watching inexperienced antagonists who get their round ruined by a player who was unprepared simply because that player had experienced with some obscure or novel mechanic.
* Learn how to communicate that your change is good. If you think/know a change will be good for the game, explain why it will be good for the game so that someone who has absolutely no understanding about that feature will also think it is good. Some people will be biased against certain changes and always hate on them, but still make sure to look out for genuine feedback.
* Players may not be good designers, however they know when there is something that they don't like in the game. If people do not like a certain feature, it isn't because they don't understand it, it is because it is poorly designed. Solutions may be suggested that may have obvious flaws, however the simple act of someone suggesting a solution to something indicates that there is a problem with the underlying mechanic that they are referencing. Don't ignore people if they have valid concerns about a particular system.


=== [[Security]] and the [[Chaplain]] [[File:Generic_hos.png]][[File:Generic_chaplain.png]] ===
== GitHub ==


Nar-Sie's cult is generally absent on the stations that Ratvar's servants are present, but the watchful eye of [[Security]] and [[Chaplain|heretical priests]] is ever-present. A tactical security assault can demolish the most well-prepared servant defences, and the [[Chaplain#Null_Rod|chaplain's holy weapon]] weakens the Justiciar's magic; a holy weapon makes the user totally immune to the affects of sigils, for instance, and [[Chaplain#GET_BEHIND_ME_NAR-NAR_RATVAR|holy water]] will purge the light of Ratvar from even the most powerful servant's mind, given time.
* There isn't really much to say here tbh.
* Don't upset Crossed or the other heads, don't do anything that would impact them as a host/headmin without their knowledge.


It should be one of the servants' top priorities to [[Guide to toxins|damage]] and [[Armory|hamper]] Security. The [[Warden]] and the [[Head of Security]] can issue powerful weapons to loyal crew, which will make your time defending a whole lot harder if the crew is armed with e-guns and laser guns rather than spears. Keep in mind that servants cannot normaly convert security officers due to their [[Security_items#Mindshield_Implant|mindshield implants]], though. If you feel like going the extra mile, you can abduct an officer (or, even better, the HoS), and teleport them to [[Operating Theater|Surgery]] with a friend to [[Beyond the impossible|surgically remove the implant in order to convert them]]. As for the chaplain? Well, Ratvar says "Suffer not a heretic to live", so the answer should be self-evident.
== Coding ==
As the Head-Developer, you may find yourself coding significantly less than prior to being the Head-Developer. This is natural since you have other responsibilities that are far more important, and naturally should be trying to organise other developers in the right direction rather than doing everything yourself.


== Ratvar ==
== Tips ==


<center>
* Don't worry if another maintainer is coding more than you. It is not a competition and your job isn't to be the most active coder on GitHub. Coding is the least important part of the role.
[[File:Ratvar.gif]]
* Don't ignore #github. Look at every single merged change when you wake up in the morning and constantly keep an idea about the state of the game.
* Many changes have extremely indirect consequences that are almost impossible to see, even with experience. Make sure to keep tabs on what is and what isn't improving the game.


Once you've defended the Ark for enough time, Ratvar will come forth.
== Unsorted.dm ==


His destructive power is unmatched, turning the minds of the unenlightened and twisting the very walls to suit his image.
=== Things from experience ===


Few things are capable of challenging Ratvar's sheer power.
* The bi-weekly developer meetings are pretty cool, although they should have been 50/50 talking about what we want from the design, and contrbutors having a chance to give input into the design.


One of them is Nar-Sie.
=== Things that I think Beestation should aim towards in the future ===


If Ratvar and Nar-Sie encounter one another,
* Easier and more consistent ways to get back into the round. This will lessen the annoyance of being dead and will allow us to have a more relaxed community view on traitors who kill players.
* In-character goals (Antagonists acting antagonistically out of their nature) instead of Out-of-character goals (Strict objectives that must be completed no matter what, limiting roleplay variance)
* More control over what antagonists are allowed to do in-character, progressive traitors/a reputation system is a good step, although try to avoid the very gamey approach that progressive traitors encourage (If completing objectives is the way to make money, players will optimise completing objectives as much as possible and have a gamey approach. Try to make it so that the focus of antagonists is something relating to their character).


Th̗̮̪̹́ͅe̘n̺ ̤̣͟ơ͙͈̻n̵̘̦l̫̬̀ͅyͅ ̲ò̮̤n̼̻̼̖̭̪͠ͅe̬͚͕̲̻̰ ҉͚̞͙̞̭̼s̡͖h̜̻̞̣̩̟ͅa̴͉͍̯̟͎̠l̳̝̖̫͞ḷ͔̘̞͞ ̯̞̥̱̲͙̕ͅe̛̙m̦̻̗̹̝̹͘e͈r̫g͕͉̠e͢ ̮͎̗̮̭̭̝a̱͍͍ͅl͙̗͔̹̻̗͈i͕͕̣̫̳̞v̗͈͍͝e.̛̟
=== Other things that I think ===
</center>


* Everyone talks about economy (insert any major system) changes that magically fix the game, however you need to think: How will this actually impact the game. If the economy isn't tied into literally every part of the game, then making a good economy is literally useless. Remember why you are making a change and keep that in mind when you are designing something: You want to make changes that have an impact on how people player the game, not changes that are just a good isolated system.




{{Jobs}}
{{Jobs}}
{{Game modes}}
[[Category: Jobs]]
[[Category: Jobs]] [[Category:Game Modes]]

Revision as of 10:17, 14 January 2024

HEAD STAFF

Head Developer
Access: Everything
Difficulty: Extremely Hard
Supervisors: Project Lead/Host
Duties: Manage design direction, recruit maintainers, make sure the GitHub is running smoothly.
Guides: Non-Admin Staff Conduct
Quote: Who the coded this like this.


Guide to being the Head-Developer, this is kind of where I try to right down things I learnt from experience in a guide, however I have to say almost everything learnt is through experience and is hard to convey in a document written in a few hours.

If you don't read any of this, then remember this: Do not create a negative environment for coders, avoid grudges at all cost even if someone writes code that causes lots of bugs. Give them pointers for how to improve, if something doesn't fit into the game then say in the PR that it doesn't fit in the game and don't just leave it for 4 months with no review until the coder gives up and goes somewhere else..

For some reason in Space Station 13, the Head-Developer usually is the person in charge of design and that will typically be more important than development for you, so you must be ready to take on the heavy workload and mental torment that comes with understanding the design of Space Station 13. Once you reach the point where you realise that nothing in the game works at a design level, and that all of the jobs encourage isolationism; then you are at the point where you are starting to truly understand SS13 design.

The true role of the head-developer is to make themselves entirely expendible. If you were to leave at any moment, then if you are doing a good job that should have very little impact on the codebase.

Design

You are in charge of setting out the design precidents that will lead the server in the right direction. You aren't setting the direction that the server should go in, and shouldn't be trying to change that; the direction of the server overall is something that needs to be agreed on by all the project heads.

Design Principles

Here are a few things that you should try to keep in mind when designing for SS13:

  • Every single change has positives and negatives. Even trivial changes that seem universally good can have long term consequences and slow mentality shifts over time which lead to undesirable states. For example, completely solving powergaming would also completely kill any form of improvisation for antagonists; completely removing all forms of cheap ways to kill people may make it more challenging for new players to play as an antagonist.
  • The Head-Admins and Head-Developers are solving the same problem. They should both be talking about what the other party is doing and the Head-Developer should give input into, and understand, the rules.
  • Good rules go hand-in-hand with the mechanics of the game. Bad rules go against what the mechanics encourage you to do. If there is a rule, or a proposed rule, that goes against how the players are being encouraged to play then something probably needs changing to emphasise the rule in the game. I like to think of this as the rules being 'diagetic', part of the game-world as players shouldn't be caught off-guard when they do something wrong; the rules exist to remove the bad-actors from the game, if there is something that people are regularly doing despite not being bad actors then perhaps something needs to change.
  • Try to play like a normal player would and try to keep the mentality of a normal player. Don't design everything around the requirement that everyone using a system must be a perfect player who always roleplays no-matter what.
  • The server wants to be a roleplay server. This doesn't mean roleplay is the only thing that you should care about, gameplay and fun are also very important and without variation and some amount of chaos in what happens in the round, there are no events that are actually worth roleplaying.
  • Changes in the game will have slow psychological effects on the playerbase, which may not have an immediate impact but may cause a shift in player mentality over time.
  • Everyone who actively participates in the forums/discord will be an experienced player, remember to consider the experience of the newer player as well when it comes to balancing/changing things.
  • If you are making a poll, text answers are by far the most useful fo getting any meaningful data out. If you are trying to analyse a testmerge, most of the time its better to just observe players and see how they are playing rather than to use a poll however.
  • On that note, make sure you observe and watch people frequently! When you play, you may feel that something is unfair but are heavily biased and will not consider how the other player was feeling. You ```must``` observe players regularly and watch them die to things that seem unfair, when you see this happening, then you know that changes might need to be made in that area. It is specifically useful when you are watching inexperienced antagonists who get their round ruined by a player who was unprepared simply because that player had experienced with some obscure or novel mechanic.
  • Learn how to communicate that your change is good. If you think/know a change will be good for the game, explain why it will be good for the game so that someone who has absolutely no understanding about that feature will also think it is good. Some people will be biased against certain changes and always hate on them, but still make sure to look out for genuine feedback.
  • Players may not be good designers, however they know when there is something that they don't like in the game. If people do not like a certain feature, it isn't because they don't understand it, it is because it is poorly designed. Solutions may be suggested that may have obvious flaws, however the simple act of someone suggesting a solution to something indicates that there is a problem with the underlying mechanic that they are referencing. Don't ignore people if they have valid concerns about a particular system.

GitHub

  • There isn't really much to say here tbh.
  • Don't upset Crossed or the other heads, don't do anything that would impact them as a host/headmin without their knowledge.

Coding

As the Head-Developer, you may find yourself coding significantly less than prior to being the Head-Developer. This is natural since you have other responsibilities that are far more important, and naturally should be trying to organise other developers in the right direction rather than doing everything yourself.

Tips

  • Don't worry if another maintainer is coding more than you. It is not a competition and your job isn't to be the most active coder on GitHub. Coding is the least important part of the role.
  • Don't ignore #github. Look at every single merged change when you wake up in the morning and constantly keep an idea about the state of the game.
  • Many changes have extremely indirect consequences that are almost impossible to see, even with experience. Make sure to keep tabs on what is and what isn't improving the game.

Unsorted.dm

Things from experience

  • The bi-weekly developer meetings are pretty cool, although they should have been 50/50 talking about what we want from the design, and contrbutors having a chance to give input into the design.

Things that I think Beestation should aim towards in the future

  • Easier and more consistent ways to get back into the round. This will lessen the annoyance of being dead and will allow us to have a more relaxed community view on traitors who kill players.
  • In-character goals (Antagonists acting antagonistically out of their nature) instead of Out-of-character goals (Strict objectives that must be completed no matter what, limiting roleplay variance)
  • More control over what antagonists are allowed to do in-character, progressive traitors/a reputation system is a good step, although try to avoid the very gamey approach that progressive traitors encourage (If completing objectives is the way to make money, players will optimise completing objectives as much as possible and have a gamey approach. Try to make it so that the focus of antagonists is something relating to their character).

Other things that I think

  • Everyone talks about economy (insert any major system) changes that magically fix the game, however you need to think: How will this actually impact the game. If the economy isn't tied into literally every part of the game, then making a good economy is literally useless. Remember why you are making a change and keep that in mind when you are designing something: You want to make changes that have an impact on how people player the game, not changes that are just a good isolated system.


Jobs on Beestation

Command Captain, Head of Personnel
Security Head of Security, Security Officer, Warden, Detective
Engineering Chief Engineer, Station Engineer, Atmospheric Technician
Science Research Director, Scientist, Roboticist, Exploration Crew
Medical Chief Medical Officer, Medical Doctor, Brig Physician, Chemist, Geneticist, Virologist
Service Janitor, Bartender, Cook, Botanist, Clown, Mime
Civilian Assistant, Lawyer, Chaplain, Curator, Gimmick
Cargo Quartermaster, Cargo Technician, Shaft Miner
Non-human AI, Cyborg, Positronic Brain, Drone, Personal AI, Construct, Ghost
Antagonists Traitor, Malfunctioning AI, Changeling, Nuclear Operative, Blood Cultist, Clockwork Cultist, Revolutionary, Wizard, Blob, Abductor, Holoparasite, Xenomorph, Spider, Swarmers, Revenant, Morph, Nightmare, Space Ninja, Slaughter Demon, Pirate, Creep, Fugitives, Hunters, Heretics, Space Dragon
Special CentCom Official, Death Squad Officer, Emergency Response Officer, Chrono Legionnaire, Highlander, Ian, Lavaland Role