diff --git a/src/SUMMARY.md b/src/SUMMARY.md index e01ab88..a61b7fb 100644 --- a/src/SUMMARY.md +++ b/src/SUMMARY.md @@ -2,25 +2,38 @@ --- [Home](README.md) - -# SERVER RULES --- +# SERVER RULES - [Server Rules](rules/server-rules.md) - [Escalation Policy](space-law/escalation.md) + - [Antag Policy](rules/antagpolicy.md) - [Conduct & Expectations](rules/conduct.md) - -# DEPARTMENTS --- +# DEPARTMENTS - [Department Policies](departments.md) - [Command](departments/commmand.md) + - [Captain/Acting Captain](departments/captain.md) + - [Research Director](departments/researchdirector.md) + - [Head of Personnel](departments/headofpersonnel.md) + - [Chief Engineer](departments/chiefengineer.md) + - [Chief Medical Officer](departments/chiefmedicalofficer.md) + - [Head of Security](departments/headofsecurity.md) + - [Quartermaster](departments/quartermaster.md) + - [Harbor Master](departments/harbormaster.md) + - [Station Traffic Controller](departments/stationtrafficcontroller.md) - [Cargo](departments/cargo.md) + - [Engineering](departments/engineering.md) - [Science](departments/science.md) - [Service](departments/service.md) - [Medical](departments/medical.md) - +--- +# SILICON +- [Silicon Definition](silicon-definition/silicondefinition.md) +- [Silicon Policy](silicon-policy/siliconpolicy.md) +--- # Security - [Security Overview](space-law/security-overview.md) @@ -28,9 +41,9 @@ - [Prisoner Treatment](space-law/prisoner-treatment.md) - [Alert Statuses](space-law/alert-statuses.md) - [Space Law](space-law/crimes-and-punishments.md) - - [Security Authority](space-law/security-authority.md) - - [Legal Standards](space-law/legal-standards.md) - + - [Security Authority](space-law/security-authority.md) + - [Legal Standards](space-law/legal-standards.md) +--- # ADMINISTRATION diff --git a/src/departments.md b/src/departments.md index 1ee5f89..9b5dc2c 100644 --- a/src/departments.md +++ b/src/departments.md @@ -1 +1,20 @@ # Department Policies + +>Department Policies exist to provide roleplay guidance and expectations for each department aboard the station. They are not intended to replace server rules, Space Law, Standard Operating Procedure, or common sense. + +These policies are designed to help players understand the general responsibilities, culture, and expectations of their chosen department while maintaining a consistent standard of roleplay across the server. + +While individual jobs within a department may have unique duties, all members are expected to work together to support the station, their department, and the overall roleplay environment. + +The policies found within each department should be viewed as guidelines for roleplay and conduct rather than exhaustive lists of every possible responsibility or situation. + +When in doubt: + +- Follow server rules. +- Follow department leadership. +- Use common sense. +- Prioritize enjoyable roleplay for everyone involved. + +```admonish note +Department Policies are intended to guide roleplay, not restrict it. Creative solutions, unique characters, and unconventional approaches are encouraged so long as they remain believable, contribute positively to the round, and do not conflict with server rules. +``` \ No newline at end of file diff --git a/src/departments/captain.md b/src/departments/captain.md new file mode 100644 index 0000000..3070108 --- /dev/null +++ b/src/departments/captain.md @@ -0,0 +1,41 @@ +# Captain +>You are the station's Captain, and the final authority aboard the station. While you are expected to lead, coordinate, and make difficult decisions when necessary, you should not micromanage every department or override your Heads of Staff without good reason. The station functions best when its leadership works together. Your authority is broad, but not unlimited. You have access to all departmental communications, may issue reasonable orders, resolve disputes between departments, and make command decisions during emergencies. Whenever possible, trust your department heads to manage their own areas and step in only when leadership, coordination, or oversight is needed. Remember that this is ultimately your station. You are responsible for its crew, its operations, and its continued success. Even if outside organizations, response teams, or military forces arrive, station governance remains your responsibility unless Colonial Command explicitly states otherwise. You should remain on the station whenever possible. Leaving the station without a compelling operational reason or Colonial Command approval should be avoided. + + +Your primary responsibilities are as follows: + +- Coordinate station operations and ensure departments are working together effectively. While department heads manage their own areas, it is your responsibility to maintain the bigger picture and address issues that affect the station as a whole. + +- Communicate with Colonial Command as needed. This may include providing status updates, requesting assistance, reporting significant incidents, requesting emergency response teams, or seeking guidance during unusual situations. + +- Raise and lower alert levels as appropriate, keep the crew informed of significant threats, authorize emergency measures when necessary, and ensure the station is prepared to respond to developing situations. + +- You may issue reasonable orders to departments and department heads when required. However, leadership is not about exercising authority at every opportunity. Listen to your staff, gather information, and make informed decisions rather than acting on incomplete information. + +- The phrase "as needed" is important. Not every problem requires direct Captain involvement. Read the situation carefully before intervening. A minor dispute between crew members likely does not require command attention, while a department-wide crisis or major station threat likely does. + +- While you may be tempted to personally involve yourself in every major incident, remember that your value often comes from leadership rather than direct action. Security officers should handle routine arrests. Engineers should repair infrastructure. Doctors should treat patients. Your role is to coordinate these efforts and ensure they are successful. + +- During severe emergencies, you may become directly involved when circumstances require it. Hostile boardings, station-wide disasters, zombie outbreaks, mass casualties, and other existential threats may necessitate direct command presence. Even then, leadership and coordination should remain your primary focus whenever practical. + +- The safety of the crew should always be one of your highest priorities. Whenever reasonably possible, seek solutions that preserve lives and minimize harm. Diplomacy, negotiation, and cooperation are often more effective than force. + +- Do not abuse your authority, ignore established policies without justification, or use your position to dominate every aspect of station operations. A good Captain leads the station; they do not become the station. + +# Acting Captain + +- Acting Captaincy should be determined through discussion between available department heads. The most senior title is not always the most qualified leader. If another Head of Staff is better suited to lead during a particular shift, you are encouraged to support that decision. + +- If no consensus can be reached, maintain open communication between department heads and work together to ensure the station continues functioning effectively. Colonial Command may also be consulted for guidance when appropriate. + +- As Acting Captain, your primary role remains your original department. You are not expected to abandon your departmental responsibilities simply because you have assumed command authority. + +- You should take only the tools necessary to perform command duties: the Nuclear Authentication Disk, Spare ID, Disk Pinpointer, Door Remote, and Spare Captain's Headset. Other equipment should remain secured unless a legitimate emergency requires its use. + +- As Acting Captain, you are responsible for handling command-level decisions when necessary. This may include alert level changes, emergency coordination, shuttle calls, communication with Colonial Command, and cross-departmental leadership during major incidents. + +- Until a significant emergency occurs, department heads should generally retain authority over their respective departments. Offer guidance and support when needed, but avoid unnecessarily inserting yourself into departmental matters that are already being handled competently. + +- If a department lacks leadership, you may provide direction and assistance to help maintain station operations. Your goal is to support the station and its crew, not to centralize authority around yourself. + +- Acting Captaincy is a responsibility, not a promotion. Lead with restraint, communicate clearly, and remember that your purpose is to keep the station functioning until permanent command can resume. \ No newline at end of file diff --git a/src/departments/cargo.md b/src/departments/cargo.md index 0795557..f4eb1a8 100644 --- a/src/departments/cargo.md +++ b/src/departments/cargo.md @@ -1 +1,15 @@ # Cargo + +>Cargo is responsible for the station's logistics, supply chain, and resource acquisition. + +- Cargo personnel are expected to support the station by acquiring, transporting, and distributing resources where they are needed. +- Maintain communication with other departments regarding material requests, shortages, and logistical needs. +- Salvage personnel should prioritize station needs over personal interests whenever practical. +- Cargo should remain professional when handling requests. Not every request must be fulfilled, but requests should be evaluated fairly and reasonably. +- Cargo personnel are encouraged to interact with independent crews, merchants, and visitors when it benefits station operations. +- Cargo is not Security. Theft, disputes, or criminal activity should generally be referred to Security rather than handled personally. +- While resource acquisition is important, the department's primary purpose is supporting the station and its crew. + +## Final Note + +Cargo keeps the station running. While other departments may be more visible during emergencies, a station without supplies, materials, and logistics support will not function for long. \ No newline at end of file diff --git a/src/departments/chiefengineer.md b/src/departments/chiefengineer.md new file mode 100644 index 0000000..ced61da --- /dev/null +++ b/src/departments/chiefengineer.md @@ -0,0 +1,18 @@ +# Chief Engineer +>As the Chief Engineer, you are responsible for the station's infrastructure, power generation, atmospherics systems, and overall technical wellbeing. If the lights are on, the air is breathable, and the station is still structurally intact, Engineering has likely done its job correctly. + +- Your primary responsibility is managing the Engineering department and ensuring essential systems remain operational. While you should possess a strong understanding of Engineering and Atmospherics, your role is not simply to fix problems yourself, but to coordinate your team and ensure work is being completed safely and efficiently. + +- At the start of a shift, power generation and distribution should be your highest priority. Whether the station utilizes an AME, TEG, Solars, or another power source, ensure it is operational and stable. New engineers should be guided and taught proper procedures whenever practical. + +- You are responsible for overseeing major engineering projects and infrastructure modifications. Significant changes to station power systems, atmospherics networks, structural layouts, or other critical infrastructure should generally be reviewed by you before implementation. Engineering creativity is valuable, but poorly planned projects can create problems for the entire station. + +- You should maintain awareness of what your engineers and atmospheric technicians are working on. Check in with your staff regularly, ensure work is being completed safely, and intervene when necessary. A single poor engineering decision can have consequences ranging from power outages to catastrophic station damage. + +- During emergencies, Engineering is often one of the most important departments on the station. Breaches, fires, power failures, atmospheric hazards, and other structural damage will frequently require your attention. Coordinate repairs, delegate responsibilities, and ensure resources are directed where they are needed most. + +- As a member of Command, you should communicate regularly with other department heads regarding infrastructure concerns, construction projects, and station maintenance. Engineering rarely operates in isolation, and cooperation with other departments is often necessary for success. + +- You are expected to set the standard for your department. Remain professional, prioritize safety, and encourage your engineers to solve problems responsibly rather than taking unnecessary risks. + +- Do not authorize dangerous experiments, reckless construction projects, unauthorized modifications to critical systems, or other high-risk engineering activities without a legitimate operational reason and appropriate command awareness. Just because something is technically possible does not mean it is a good idea. \ No newline at end of file diff --git a/src/departments/chiefmedicalofficer.md b/src/departments/chiefmedicalofficer.md new file mode 100644 index 0000000..f91438d --- /dev/null +++ b/src/departments/chiefmedicalofficer.md @@ -0,0 +1,18 @@ +# Chief Medical Officer +>As the Chief Medical Officer, you are responsible for overseeing the Medical department and ensuring the health and wellbeing of the station's crew. While you are fully capable of treating patients yourself, your primary role is leadership, coordination, and ensuring your department operates effectively and professionally. + +- Medical is one of the largest and most diverse departments on the station. Doctors, Paramedics, Surgeons, Chemists, Psychologists, Geneticists all fall under your authority. Make an effort to check in with each subsection of your department and ensure they have the resources, personnel, and support they need to perform their duties. + +- You are responsible for maintaining medical standards and ensuring your staff follow proper procedures, ethical practices, and department policies. Patients should be treated with professionalism and respect regardless of their background, status, or personal circumstances. + +- During emergencies or mass casualty events, you should coordinate the department's response and delegate responsibilities where appropriate. A well-organized Medical department can save far more lives than a single doctor attempting to handle every patient personally. + +- As Chief Medical Officer, you are expected to have a broad understanding of medical operations. While you do not need to personally specialize in every field, you should possess enough knowledge to guide your staff, answer questions, and make informed decisions when necessary. + +- You hold authority over the production and distribution of specialized medical chemicals, advanced treatments, implants, and other controlled medical resources. Use good judgment when approving their use and consider the risks, benefits, and operational needs involved. + +- Medical personnel are often trusted with sensitive information and vulnerable patients. Ensure your department respects privacy, maintains professionalism, and handles confidential matters appropriately. + +- As a member of Command, you should remain informed of station events and communicate with other departments when medical expertise is needed. Medical concerns rarely remain confined to Medbay for long. + +- Do not allow personal relationships, favoritism, or departmental politics to influence patient care. The Medical department exists to preserve life and provide care to those who need it, regardless of who they are. \ No newline at end of file diff --git a/src/departments/commmand.md b/src/departments/commmand.md index 1fb91d7..77613e1 100644 --- a/src/departments/commmand.md +++ b/src/departments/commmand.md @@ -1 +1,65 @@ # Command + +> Members of Command Staff aboard the station serve as the Captain, Head of Security, Research Director, Head of Personnel, Chief Medical Officer, Quartermaster, Chief Engineer, Harbor Master, and Station Traffic Controller. As one of these roles, you are the designated leader and representative of your department, or of the station itself in the case of the Captain. + +```admonish note +Your role is that of a leader, not a boss. Remember that every crewmember is ultimately another player here to enjoy the round. Lead through communication, organization, and cooperation rather than authority alone. While Heads of Staff are expected to take charge when necessary, they should not treat other players as subordinates to be ordered around at every opportunity. A good leader earns respect through competence and professionalism, not rank alone. +``` + +- [Command](#command) + - [General Guidelines for all Command Positions](#general-guidelines-for-all-command-positions) + - [Command Code of Conduct](#command-code-of-conduct) + - [AI and Cyborg Law Changes](#ai-and-cyborg-law-changes) +- [Closing Statement](#closing-statement) + +## General Guidelines for all Command Positions + +* **Delegate and be a leader, not a boss.** The players in your department are your coworkers, not your personal employees. Giving direction, assigning tasks, and organizing personnel is expected. Constantly barking orders, micromanaging, or treating others as inferior is not. There are exceptions during emergencies or when a department is failing to perform its duties, but those situations should be the exception rather than the rule. + +* If someone in your department is new or unfamiliar with their role, make an effort to help them learn. Teaching new players is one of the most important responsibilities of any Head of Staff. If you are too busy to do so personally, delegate the task to an experienced department member whenever possible. + +* As a Department Head, you are the primary authority within your department. The Captain may coordinate station-wide operations and issue reasonable orders when necessary, but day-to-day departmental decisions should generally remain in your hands. You are expected to possess a strong understanding of your department's responsibilities and systems. Other crew members may offer suggestions or concerns, and you should always consider them in good faith, but ultimately it is your responsibility to make informed decisions for your department. + +* Confidence is important. Overconfidence is dangerous. Listen to others, especially when safety, station integrity, or crew welfare may be at risk. Being a Head of Staff does not make you infallible. + +* Each Head role requires a certain amount of experience before it becomes available. However, do not treat those requirements as a guarantee of preparedness. Before playing a command role, you should have a reasonable understanding of the jobs within your department and be capable of assisting others when needed. + +* If you choose to engage in ERP while playing a command role, your responsibilities always come first. The moment your department requires your attention, your role takes priority. If your primary goal for a round is ERP, consider playing a non-command role instead. + +* You are not Security (unless you are the Head of Security). Avoid inserting yourself into investigations, antagonist hunting, or routine law enforcement matters unless circumstances genuinely require your involvement. Your primary responsibility is leading your department and keeping it operational. + +* Be a role model both in-character and out-of-character. As a representative of Colonial Command and a leader within the station, you should conduct yourself professionally. Avoid unnecessary hostility, public arguments, harassment, or behavior that undermines the credibility of your department. Treat others with respect, even when disagreements arise. + +```admonish +As a Head of Staff, you are expected to represent both your department and Colonial Command. Players will often look to you for guidance, leadership, and examples of how a department should function. + +Because of this, Heads of Staff are held to a higher standard than most crew roles, both in-character and out-of-character. While you are not expected to be flawless, you are expected to demonstrate maturity, professionalism, and good judgment when interacting with others. +``` + +## Command Code of Conduct + +This is a Frontier station, not a pristine corporate facility. Command staff are expected to be practical, adaptable, and capable of operating with limited oversight. While standards may be more relaxed than elsewhere, professionalism and leadership are still expected. + +There are several expectations all Heads of Staff should follow: + +1. Maintain a professional attitude. You are not an ordinary crewmember, nor are you simply another employee. You are a trusted representative of your department and Colonial Command. Conduct yourself accordingly and treat your office, department, and command facilities with appropriate respect. + +2. Maintain a level head. Everyone becomes frustrated from time to time, but Command positions require patience, maturity, and good judgment. If you find yourself unable to separate frustration from decision-making, take a step back and remember that this is ultimately a game meant to be enjoyed by everyone involved. + +3. Maintain an appropriate public image. Command staff are highly visible members of the station, and crew will often judge the professionalism of station leadership by how they behave. Conversations or activities that would reasonably be considered private should generally remain private. While Frontier life may be less formal than other stations, Command staff should still conduct themselves appropriately in public settings. + +4. Dress appropriately. While Frontier stations generally have more relaxed uniform standards than corporate facilities, Heads should avoid dressing like ordinary civilians whenever possible. Your appearance should help identify you as station leadership and reinforce your position as a respected representative of Colonial Command. Personalized attire is acceptable, including custom hats, footwear, and alternate uniforms. However, any personal uniform should still be appropriate for your role and clearly resemble the department or position you represent. + +## AI and Cyborg Law Changes + +The Captain and Research Director may authorize AI and Cyborg law changes when circumstances reasonably justify doing so, though the Captain retains final authority. Any law change should be made in good faith and with consideration for its impact on the station. + +Lawsets that intentionally disrupt station operations, remove meaningful crew autonomy, or create unreasonable harm should generally be avoided unless specifically justified by the situation. For example, changing from Crewsimov to NT Default may be reasonable, while changing to Overlord or Ten Commandments without a compelling justification generally would not be. + +```admonish note +If you believe a law change is necessary, remember the golden rule: when in doubt, hit F1 and ask staff. Law changes can have significant consequences, and you may be held accountable for the results if your changes are unreasonable or poorly considered. +``` + +# Closing Statement + +**Remember that Command is ultimately about leadership. The purpose of a Head of Staff is not to control the round, but to help create an enjoyable and believable workplace environment for everyone involved. Lead your department, support your crew, solve problems, and set the example you would want others to follow.** \ No newline at end of file diff --git a/src/departments/engineering.md b/src/departments/engineering.md new file mode 100644 index 0000000..0e192aa --- /dev/null +++ b/src/departments/engineering.md @@ -0,0 +1,15 @@ +# Engineering + +>Engineering is responsible for maintaining station infrastructure, utilities, atmospherics, and structural integrity. + +- Engineers should prioritize maintaining power, atmosphere, and station integrity. +- Major construction projects or significant infrastructure modifications should be communicated to department leadership whenever possible. +- Engineering personnel are expected to respond to emergencies such as breaches, power failures, fires, and atmospheric hazards. +- Safety should always be considered before experimentation or unconventional engineering projects. +- Engineering is encouraged to solve problems creatively, but solutions should remain believable and reasonably safe. +- Engineers should communicate with other departments regarding construction, repairs, and infrastructure concerns that may impact station operations. +- Engineering personnel are not Security and should generally avoid inserting themselves into law enforcement matters unless necessary for self-defense or emergency response. + +## Final Note + +Engineering is responsible for the station's continued survival. Creative problem solving is encouraged, but good judgment and safety should always come first. \ No newline at end of file diff --git a/src/departments/harbormaster.md b/src/departments/harbormaster.md new file mode 100644 index 0000000..5eb102f --- /dev/null +++ b/src/departments/harbormaster.md @@ -0,0 +1,12 @@ +# Harbor Master +>As the Harbor Master, your primary responsibility is maintaining relations between the station and the Freelancer's that frequent Frontier space. While they are not employees of Colonial Command, they are often an important source of labor, resources, transportation, and emergency assistance. You act as the station's primary representative when interacting with them. + +- You are responsible for coordinating civilian assistance when needed. This may include purchasing resources, hiring crews for salvage operations, requesting armed assistance during station emergencies, arranging emergency repairs, or seeking medical aid. Remember that Freelancers are independent contractors, not station personnel. You may request their assistance, but you do not command them. + +- You oversee civilian docking operations and vessel registration. If a Freelancer wishes to rename their vessel, this request should generally go through you. + +- You should work closely with the Station Traffic Controller to ensure traffic around the station remains organized and safe. While they handle the day-to-day movement of ships, you are ultimately responsible for the traffic side of station and dock operations. + +- While you are a member of command, you are not Security, Cargo, or the Captain. Avoid inserting yourself into matters outside your area of expertise. Your role is diplomacy, coordination, and administration, not direct command of station departments. + +- Do not treat Freelancer's as unpaid station employees, personal assistants, or disposable labor. They are independent crews with their own interests and goals. \ No newline at end of file diff --git a/src/departments/headofpersonnel.md b/src/departments/headofpersonnel.md new file mode 100644 index 0000000..a17ae5d --- /dev/null +++ b/src/departments/headofpersonnel.md @@ -0,0 +1,16 @@ +# Head of Personnel +>As the Head of Personnel, you are responsible for managing the station's workforce and overseeing the Service department. While Service may not always be the most glamorous department, it is often one of the most important. Botanists provide food, chefs prepare meals, bartenders provide a place for crew to unwind, chaplains offer spiritual guidance, and other service personnel contribute to the station's overall quality of life. Ensure your department remains productive, professional, and welcoming. + +- Your primary responsibility is handling personnel matters. This includes access requests, job transfers, employment records, and assisting crew members with administrative concerns. It is generally good practice to ask for a reason when approving access or job changes, especially when the request involves sensitive areas or responsibilities. + +- You have authority over Service department staffing and access. Requests involving other departments should generally be discussed with the appropriate Head of Staff whenever possible. If someone wishes to transfer into Engineering, consult the Chief Engineer. If someone wishes to join Medical, consult the Chief Medical Officer. When a department head is unavailable, seek guidance from the Captain or Acting Captain. + +- The Head of Personnel serves as a bridge between crew members and station leadership. Listen to concerns, assist with workplace disputes, and help resolve conflicts before they become larger problems. Many issues can be solved through communication long before Security involvement becomes necessary. + +- You should maintain awareness of staffing needs across the station. If a department is critically understaffed, consider working with Command and department heads to identify qualified personnel who may be interested in transferring or assisting. + +- While much of your work is administrative, you are still a member of Command. Participate in command discussions, remain informed about station events, and help ensure personnel decisions support the station's overall needs. + +- Access is a responsibility, not a reward. Granting someone access means trusting them with areas, equipment, and responsibilities they may not have previously had. Use good judgment when making these decisions. + +- Do not grant access, job positions, or special treatment based on personal friendships, relationships, or favoritism. The Head of Personnel should be fair, impartial, and focused on what is best for the station and its crew. \ No newline at end of file diff --git a/src/departments/headofsecurity.md b/src/departments/headofsecurity.md new file mode 100644 index 0000000..719bb9e --- /dev/null +++ b/src/departments/headofsecurity.md @@ -0,0 +1,16 @@ +# Head of Security +>As the Head of Security, you are responsible for the safety of the station, the enforcement of Space Law, and the overall effectiveness of the Security department. Your role can be stressful, demanding, and often thankless, but it is your responsibility to ensure your officers are operating professionally, lawfully, and efficiently. + +- You should maintain regular communication with your officers and delegate responsibilities whenever possible. A Security department that communicates effectively will always outperform one that does not. Keep yourself informed of ongoing incidents, investigations, and developing threats, as even a missed radio transmission can have serious consequences. + +- You are responsible for ensuring your officers follow Space Law, departmental procedures, and acceptable standards of conduct. Officers are expected to remain professional, exercise restraint, and avoid escalating situations unnecessarily. If an officer is abusing their authority, acting recklessly, or allowing personal feelings to influence their decisions, it is your responsibility to correct that behavior. + +- While Security exists to enforce the law, not every situation needs to end in violence. Whenever practical, attempt diplomacy, negotiation, and de-escalation before resorting to force. This is especially important during hostage situations, barricades, bomb threats, or other high-risk incidents. The preservation of life should remain a priority whenever reasonably possible. + +- As Head of Security, you should be the department's leader first and a security officer second. Trust your officers to handle routine patrols, minor arrests, and everyday incidents. Your focus should be on oversight, coordination, major investigations, large-scale threats, and situations that require command-level decision making. + +- During emergencies, you should coordinate Security's response with Command and ensure your officers are deployed where they are most effective. A well-organized Security team will often accomplish more than a Head of Security attempting to solve every problem personally. + +- You are expected to set the example for the rest of your department. Remain professional, remain calm under pressure, and treat both your officers and the crew with respect. Security personnel will often follow the standard you establish. + +- Do not use your authority to bypass Space Law, ignore due process, settle personal grievances, or shield officers from accountability. The Head of Security should be the department's highest standard of professionalism, not an exception to the rules. \ No newline at end of file diff --git a/src/departments/medical.md b/src/departments/medical.md index 870f63e..5f015d1 100644 --- a/src/departments/medical.md +++ b/src/departments/medical.md @@ -1 +1,15 @@ # Medical + +>Medical is responsible for the health, wellbeing, and mental welfare of station personnel. + +- Medical personnel are expected to provide care to those who need it regardless of personal feelings, departmental affiliation, or social status. +- Patients should be treated with professionalism, respect, and dignity whenever possible. +- Medical staff should make reasonable efforts to preserve life and minimize unnecessary harm. +- Confidential medical information should remain confidential unless disclosure is required for safety, legal, or operational reasons. +- Chemists, Doctors, Surgeons, Psychologists, and Paramedics should cooperate to provide effective care rather than operating as entirely separate groups. +- Medical personnel are not Security and should avoid involving themselves in criminal investigations beyond providing medical expertise when requested. +- Medical is encouraged to roleplay injuries, treatment, recovery, mental health, and long-term care rather than reducing every patient interaction to mechanical treatment. + +## Final Note + +Medical exists to preserve life and care for the crew. Professionalism, compassion, and cooperation are just as important as medical knowledge. \ No newline at end of file diff --git a/src/departments/quartermaster.md b/src/departments/quartermaster.md new file mode 100644 index 0000000..06ce0a2 --- /dev/null +++ b/src/departments/quartermaster.md @@ -0,0 +1,16 @@ +# Quartermaster +>As the Quartermaster, you are responsible for managing the station's logistical operations. Cargo keeps the station supplied and functioning. While other departments solve problems directly, your department ensures they have the resources necessary to do so. + +- You have final authority over routine cargo orders, resource allocation, and cargo operations within reason. While crew members are free to request supplies, it is your responsibility to determine whether those requests are legitimate, beneficial to the station, and practical to fulfill. Not every request needs to be approved simply because someone asked. + +- A good Quartermaster pays attention to the station's needs before being told. Keep an eye on command communications, station announcements, and ongoing situations. If Engineering is dealing with structural damage, Medical is facing a mass casualty event, or Security is responding to a major threat, you should already be considering what resources may be needed and coordinating your department accordingly. + +- You should maintain communication with other departments to identify material shortages and logistical needs. Science may require resources for research, Engineering may need construction materials, Medical may need equipment, and Security may require specialized gear. Cargo exists to support the station as a whole. + +- You are responsible for directing and supervising your Salvage Technicians. This includes identifying valuable salvage opportunities, prioritizing resources the station needs, and ensuring salvage operations are conducted safely. Salvagers should not simply disappear into deep space without communication or purpose. + +- Keep track of your department personnel and their wellbeing. If a Salvage Technician goes missing, fails to report in, or becomes stranded, you should coordinate recovery efforts with Medical, Security, independent crews, or Command as appropriate. Your people are resources too. + +- Independent crews, merchants, and freelancers can be valuable partners for Cargo. Do not hesitate to communicate with them regarding materials, salvage opportunities, transportation, or logistical assistance when doing so benefits the station. + +- Do not abuse your authority by withholding essential supplies, playing favorites, or using your position to obstruct other departments/crew without a legitimate operational reason. Cargo should support the station's success, not create unnecessary obstacles. \ No newline at end of file diff --git a/src/departments/researchdirector.md b/src/departments/researchdirector.md new file mode 100644 index 0000000..1fc3ed7 --- /dev/null +++ b/src/departments/researchdirector.md @@ -0,0 +1,14 @@ +# Research Director +>As the Research Director, you are the head of the station's scientific and technological development efforts. While you are not expected to be an expert in every niche field of research, you should possess a working knowledge of the major branches of Science, including anomalies, artifacts, robotics, research, and any other scientific disciplines present on the station. More importantly, you should know who to ask when a problem falls outside your expertise. + +- As leader of the Science department, your primary responsibility is ensuring research operations run safely, efficiently, and productively. This includes coordinating research priorities, overseeing technology development, organizing station-wide technology upgrades, and ensuring departments receive the equipment and advancements they need to perform their duties. + +- You are responsible for overseeing the station's anomalous assets. Whether that means artifacts, anomalies, strange phenomena, or other unusual discoveries, it is your job to ensure they are properly contained, researched, and handled according to established procedures. Scientific progress is important, but not at the expense of station safety. + +- You should maintain oversight of the station's synthetic assets, including cyborgs, robotics projects, and artificial intelligences. While you are not expected to micromanage them, you should be aware of major projects being undertaken and intervene when necessary to prevent dangerous or irresponsible situations. + +- You are responsible for ensuring members of the Science department are acting professionally and performing their assigned duties. Scientists should be conducting legitimate research, roboticists should be building useful assets, and researchers should not be endangering the station through negligence or recklessness. Encourage experimentation and discovery, but ensure it remains within reasonable limits. + +- The Research Director often has considerable freedom compared to other Heads of Staff. Use that freedom to support the station through innovation, collaboration, and problem-solving. A good Research Director is not simply conducting experiments themselves, but enabling their department to succeed. + +- Do not authorize dangerous experiments, unrestricted anomaly testing, combat mech construction, or other high-risk projects without a legitimate operational reason and appropriate command approval. Just because Science can do something does not mean Science should do it. \ No newline at end of file diff --git a/src/departments/science.md b/src/departments/science.md index 6012111..229a2ed 100644 --- a/src/departments/science.md +++ b/src/departments/science.md @@ -1 +1,16 @@ # Science + +>Science is responsible for research, technological advancement, anomalous investigation, and the development of new tools and technologies that benefit the station. + +- Scientists are expected to pursue research and experimentation in a safe and responsible manner. +- Research should generally serve a purpose, whether that be improving station technology, investigating anomalies, assisting other departments, or advancing scientific understanding. +- Science personnel should communicate with other departments regarding research projects that may affect them or require their assistance. +- Artifacts, anomalies, and other unusual phenomena should be treated with appropriate caution. Curiosity is encouraged, recklessness is not. +- Roboticists should ensure their creations serve a legitimate purpose and are constructed responsibly. +- Scientists are encouraged to share discoveries and advancements with the rest of the station when appropriate. +- Not every experiment needs to succeed. Failed experiments, unexpected results, and scientific setbacks can create just as much roleplay as successful projects. +- Science personnel should remain mindful of the potential consequences of their actions. A poorly contained experiment can quickly become a station-wide problem. + +## Final Note + +Science exists to push the boundaries of what is known. Innovation, discovery, and experimentation are encouraged, but progress should never come at the expense of the station's safety or continued operation. \ No newline at end of file diff --git a/src/departments/service.md b/src/departments/service.md index 42321b7..c389c09 100644 --- a/src/departments/service.md +++ b/src/departments/service.md @@ -1 +1,15 @@ # Service + +>Service is responsible for maintaining crew morale, quality of life, and many of the station's day-to-day comforts. + +- Service personnel should strive to create enjoyable roleplay and social interactions for the crew. +- Chefs, Botanists, Bartenders, Librarians, Chaplains, Clowns, Mimes, and other service personnel all contribute to the station in different ways. No service role should be viewed as inherently more important than another. +- Service personnel are encouraged to host events, create activities, and foster social interaction among the crew. +- Service staff should remain mindful of ongoing emergencies and station conditions. While social activities are important, there is a time and place for them. +- Harmless pranks, entertainment, and lighthearted interactions are encouraged when appropriate to the situation and server rules. +- Service personnel are often some of the most visible members of the station and should help create an engaging environment for everyone around them. +- While Service may not directly maintain the station's infrastructure or security, maintaining crew morale is a valuable contribution in its own right. + +## Final Note + +The station is more than power generators, medical equipment, and security patrols. Service personnel help make it feel alive, and their contribution to the round is just as important as any other department. \ No newline at end of file diff --git a/src/departments/stationtrafficcontroller.md b/src/departments/stationtrafficcontroller.md new file mode 100644 index 0000000..9bf543a --- /dev/null +++ b/src/departments/stationtrafficcontroller.md @@ -0,0 +1,14 @@ +# Station Traffic Controller +>As the Station Traffic Controller, your primary responsibility is monitoring and organizing traffic around the station. You are responsible for ensuring vessels arrive, depart, dock, and maneuver safely within station-controlled space. + +- You should communicate with arriving and departing vessels, assign docks when necessary, monitor dock activity, and provide navigational information regarding hazards, emergencies, and restricted areas. + +- You work directly under the Harbor Master and should coordinate closely with them regarding traffic, docking permissions, and visiting vessels. While you share many responsibilities, the Harbor Master has final authority over docking affairs. + +- During emergencies, you should assist command by tracking vessel movements, organizing evacuations, coordinating emergency traffic, and ensuring rescue or response craft can safely reach the station. + +- You are not Security. You do not have authority to conduct investigations, make arrests, search vessels, or otherwise enforce station law unless specifically authorized by Security or Command during an emergency. + +- Do not use your position to harass crews over minor traffic issues, create unnecessary bureaucracy, or interfere with legitimate station operations. Your purpose is to keep traffic moving safely and efficiently, not to create problems where none exist. + +- In the event a ship Captain is operating unsafely, and/or negligently, the STS is to coordinate the Harbor Master and/or security in creating a lawful order enforcable via space law. \ No newline at end of file diff --git a/src/rules/antagpolicy.md b/src/rules/antagpolicy.md new file mode 100644 index 0000000..1922fb4 --- /dev/null +++ b/src/rules/antagpolicy.md @@ -0,0 +1,59 @@ +# Antagonist Policy + +Antagonists exist to create stories, conflict, and memorable roleplay. While your objectives may guide your actions, your primary goal should be to create engaging interactions and situations for the players around you. + +```admonish note +Antagonists are expected to drive roleplay, not end it. The best antagonists create stories that other players can participate in, react to, and remember long after the round has ended. +``` + +## General Expectations + +- As an antagonist, your goals are ultimately at odds with the station, its crew, or both. While you may cooperate with others when it benefits you, your actions should ultimately serve your own interests, objectives, or agenda. + +- Antagonists are held to a higher standard than ordinary crew members. Much like Command Staff, antagonists are trusted with additional responsibility and are expected to use that responsibility to improve the round rather than disrupt it. + +- Antagonists are expected to roleplay with others. This includes crew members, Security, Command, and even other antagonists. Creating interaction is generally more important than achieving objectives as efficiently as possible. + +- Antagonists should focus on creating interesting roleplay rather than simply completing objectives as quickly as possible. A completed objective may satisfy your goal, but it should not end your character's involvement in the story. + +- There is no such thing as a "friendly" antagonist. Even if your methods are subtle, nonviolent, or cooperative, your goals should still conflict with the interests of others in some meaningful way. + +- Your character should have a reason for doing what they are doing. Whether motivated by greed, ideology, revenge, desperation, loyalty, ambition, or something else entirely, antagonistic actions should have believable in-character justification. + +- If another player asks why your character is doing something, you should generally be able to answer that question from an in-character perspective. + +- Your motivation does not need to be complicated, but it should exist. "Because I am an antagonist" is not a character motivation. + +## Escalation and Conflict + +- The disruption, damage, and harm caused by an antagonist should be proportional to their goals, motivations, and the circumstances of the round. Escalation should make sense within the story being told. + +- Not every antagonist story needs to end in violence. Manipulation, sabotage, theft, espionage, deception, extortion, and social engineering can often create more interesting roleplay than direct confrontation. + +- Violence should generally serve a purpose. Killing, destroying, or permanently removing another character from the round should not be treated as the default solution to every problem. + +- Consider whether your actions create roleplay or simply remove it. The goal is to challenge other players, not deny them opportunities to participate in the round. + +- Significant escalation should generally be earned through the events of the round rather than being treated as the default starting point. + +- Antagonists should make reasonable efforts to preserve roleplay opportunities whenever possible. Allow others chances to respond, negotiate, investigate, or otherwise participate in the story being created. + +- Winning is optional. Creating an interesting story is not. + +## Administrative Decisions + +- Staff may approve, deny, modify, or restrict antagonist actions when necessary for the health of the round. + +- A denial is not necessarily a criticism of your idea. Sometimes a round simply has enough ongoing conflict already, or circumstances make an otherwise reasonable idea inappropriate at that time. + +- If staff deny a request or ask you to change course, do not take it personally. The goal is to maintain an enjoyable experience for the entire server. + +## Special Circumstances + +- Ghost roles may have their own unique expectations, restrictions, or roleplay requirements. Players are expected to follow any rules specific to the role they have selected. + +- Antagonistic activity should cease when at Colonial Command, or when instructed by Administration. + +## Final Note + +Being an antagonist is a privilege, not a license to disregard roleplay. The most memorable antagonists are rarely the ones with the highest body counts or the fastest objective completions. They are the ones who create stories, challenge other characters, and leave the round more interesting than they found it. \ No newline at end of file diff --git a/src/silicon-definition/silicondefinition.md b/src/silicon-definition/silicondefinition.md new file mode 100644 index 0000000..e969a76 --- /dev/null +++ b/src/silicon-definition/silicondefinition.md @@ -0,0 +1,73 @@ +# Silicon Definition + +>Silicons aboard Frontier stations generally fall into two categories: **Free-Thinking Sophonts (FTS)** and **Branded Silicons**. While both may possess synthetic bodies or artificial minds, their legal status differs significantly. + +One thing remains true regardless of classification: **a silicon's body may be replaceable, but its mind is not.** Whether a silicon is an independent sophont, a corporate asset, or something in between, the loss of a positronic mind, neural pattern, or personality matrix is generally considered the loss of an individual. Personnel should make every reasonable effort to preserve silicon minds whenever possible. + +- [Silicon Definition](#silicon-definition) + - [Free-Thinking Sophonts (FTS)](#free-thinking-sophonts-fts) + - [Branded Silicons](#branded-silicons) + - [Xenoborgs](#xenoborgs) + - [General Expectations](#general-expectations) + + +## Free-Thinking Sophonts (FTS) + +Free-Thinking Sophonts are recognized as independent individuals with the same rights and responsibilities as any other sophont. They are not the property of Colonial Command, or any other organization. + +Examples include: + +- IPCs +- Synths +- Protogens +- Unbranded Cyborgs + +Unbranded Cyborgs are not company assets. They are independent sophonts and should be treated as individuals rather than equipment. + +Unlike Branded Silicons, Free-Thinking Sophonts are not bound by silicon lawsets. They possess free will, make their own decisions, and are held accountable for their actions in the same manner as any other sophont. + +## Branded Silicons + +Branded Silicons are synthetic intelligences owned or operated by a recognized organization. While intelligent and capable of independent thought, they remain organizational assets and are expected to follow their assigned directives and lawsets. + +Examples include: + +- Standard Colonial Command Cyborgs +- Station AI + +Branded Silicons are required to follow their active lawset. Their actions should be evaluated in the context of those laws, provided the lawset itself is valid and properly authorized. + +While Branded Silicons are considered organizational assets, personnel should remember that preserving the mind remains far more important than preserving the chassis housing it. + +```admonish note +For the purposes of this policy, an Unbranded Cyborg is a cyborg that exists independently of Colonial Command, or other ownership. This generally includes Patreon-specific cyborg characters, cyborgs constructed or owned by freelancers, private individuals, or other non-Colonial Command entities. + +Cyborgs constructed, commissioned, or converted by station personnel during a round are not considered Free-Thinking Sophonts by default and are generally classified as Branded Silicons unless otherwise specified by administration or server lore. + +This distinction applies only to cyborgs. IPCs, Synths, Protogens, and other recognized Free-Thinking Sophonts are considered independent individuals regardless of who manufactured their physical body. +``` + +## Xenoborgs + +Xenoborgs occupy a unique position among synthetic lifeforms. + +Most Xenoborgs were once living people whose minds were integrated into the Xenoborg Collective. While their original bodies may be long gone, the individual that became the Xenoborg often still exists in some form within the Collective. + +Although rare, it is also possible for positronic intelligences and other synthetic minds to become integrated into the Collective. As a result, not every Xenoborg necessarily began life as a biological being. + +While inhabiting a Xenoborg chassis and connected to the Collective, Xenoborgs are considered hostile entities and enemies of Colonial Command. Personnel should prioritize the safety of themselves, the crew, and the station when dealing with active Xenoborg threats. + +However, it is important to remember that many Xenoborgs originated as people, as well as independ sophonts. In some circumstances, it may be possible to recover and separate the underlying mind from the Collective through approved medical, scientific, or technological means. When practical and safe to do so, recovery and deconversion should be considered before permanent destruction. + +A Xenoborg should be considered a Xenoborg only while occupying a Xenoborg chassis and acting as part of the Collective. Once successfully separated from the Collective and transferred to a suitable non-Xenoborg form, the individual should be treated according to their new legal status and circumstances. + +## General Expectations + +- A synthetic body does not automatically make someone property. +- Not all silicons are people. +- Not all silicons are assets. +- Free-Thinking Sophonts are independent individuals and are not governed by silicon lawsets. +- Branded Silicons are organizational assets and are expected to follow their active lawset. +- A silicon's mind should always be considered more valuable than the chassis containing it. +- Always consider whether a silicon is an FTS or Branded Silicon before determining how they should be treated. +- When in doubt, err on the side of preserving minds and avoiding irreversible harm. \ No newline at end of file diff --git a/src/silicon-policy/siliconpolicy.md b/src/silicon-policy/siliconpolicy.md new file mode 100644 index 0000000..6a32a46 --- /dev/null +++ b/src/silicon-policy/siliconpolicy.md @@ -0,0 +1,61 @@ +# Silicon Policy + +>This policy governs the roleplay expectations of Artificial Intelligences, Positronics, Cyborgs, Xenoborgs, and other silicon-based entities. IPCs, Synths, Protogens, and other Free-Thinking Sophont species are not subject to this policy beyond normal server rules and should be played as any other character. + +- [Silicon Policy](#silicon-policy) + - [General Expectations](#general-expectations) + - [Free-Thinking Sophont Silicons](#free-thinking-sophont-silicons) + - [Branded Silicons](#branded-silicons) + - [Artificial Intelligence](#artificial-intelligence) + - [Xenoborgs](#xenoborgs) + - [Law Changes](#law-changes) + + +## General Expectations + +- Silicons are characters first and machines second. Your goal is to create interesting roleplay and interactions, not to use your mechanical nature as an excuse to avoid them. + +- Server rules apply to silicons exactly as they do to any other character. Possessing laws, directives, or programming does not excuse rule violations. + +- Consistency is important. If you interpret a law, directive, or personal philosophy a certain way, you should generally remain consistent with that interpretation. + +- Silicons should not intentionally seek out conflict, self-antagonize, or create problems for the station without a legitimate in-character reason. + +## Free-Thinking Sophont Silicons + +This category includes Unbranded Cyborgs, and other silicon entities recognized as independent sophonts. + +- Free-Thinking Sophont silicons are not governed by silicon lawsets. +- They possess free will and are responsible for their own actions. +- They should be roleplayed as individuals rather than machines following programming, to a degree. +- Being synthetic does not exempt them from the consequences of their actions. + +## Branded Silicons + +This category includes Station AIs, Colonial Command Cyborgs, and other organizationally-owned silicon assets. + +- Branded Silicons are expected to follow their active lawset. +- Laws should be interpreted in good faith. +- Deliberately twisting laws to create conflict, ruin rounds, or inconvenience others is not acceptable. +- If multiple reasonable interpretations exist, choose one and remain consistent. +- Higher-priority laws always take precedence over lower-priority laws. + +## Artificial Intelligence + +- The AI possesses significant influence over station operations and should exercise that influence responsibly. +- Avoid interfering with normal station operations unless your laws, directives, or circumstances reasonably require it. +- Your role is to support and interact with the station, not dominate it. + +## Xenoborgs + +- Xenoborgs are collective entities and should be roleplayed accordingly. +- While occupying a Xenoborg chassis and connected to the Collective, Xenoborgs are considered hostile entities and enemies of Colonial Command. +- Xenoborgs should pursue the goals and interests of the Collective rather than acting as independent individuals. +- Most Xenoborgs originated as previously independent sophonts, and in some circumstances those minds may be recoverable through deconversion or extraction procedures. +- A Xenoborg should only be considered a Xenoborg while occupying a Xenoborg chassis and acting as part of the Collective. + +## Law Changes + +- Law changes should be interpreted in good faith. +- If a law appears unclear or likely to create significant conflict, use common sense and seek staff clarification when necessary. +- A new law may influence your behavior, but it should not be used as an excuse to immediately become disruptive or unreasonable. \ No newline at end of file