Antagonist-Optional Design

src/design-proposals/antag-optional-design.md

@@ -0,0 +1,123 @@
+# Antagonist-Optional Design
+
+| Designers             | Implemented | GitHub Links |
+|-----------------------|-------------|--------------|
+| AraiMaia, pirakaplant | :x: No      | TBD          |
+
+## Overview
+
+This document proposes a change in direction pertaining to the game design philosophy of Funky Station. 
+It removes antagonists as the required driving force of round engagement, and proposes that the game should be engaging on its own terms: through economic pressure, labor conflict, structural friction built into command and department roles, and environmental hazards. 
+It also proposes removing escalation and alignment rules in favor of encouraging in-character behavior and consequences. Antagonists aren't removed per-se, but they stop being load-bearing: a round with zero antagonists should be just as engaging as one with several, and this should be true across every single round. 
+Antagonists should be the spice that adds onto everything, not the main attraction.
+
+**This document's primary objective is a statement of intent: Funky Station will no longer balance, design, or evaluate systems in terms of antagonist impact.** 
+It should be read as formal notice that systems built to serve antag balance and nothing else, at the expense of believability and authenticity to the setting, are expected to be reworked or outright removed as a consequence of this shift. That outcome should be treated as this document succeeding, not as some unfortunate side effect. 
+Anyone proposing or reviewing a change to Funky Station should be able to point to this document as the reason "but what about antags" is no longer a valid objection on its own.
+
+## Background
+That reworking has to start from an honest look at why the game currently can't survive without antagonists. This document is built around the current state of the game, where two things are true:
+
+1. Almost all of SS14's systems are designed under the assumption that antagonists exist and will cause friction and tension within the round. 
+This makes antagonists a design crutch: remove them, either through the antagonist's own incompetence, bad luck, poor design or a million other ways, and most of the game has nothing left to push against. 
+Greenshifts are uninteresting for this exact reason. 
+
+2. Funky Station is a whitelisted, RP-focused server where players are expected to play believable characters and, therefore, generate conflict organically. 
+That expectation is already at odds with a ruleset built around escalation rules and antag/crew alignment, which exist specifically to prevent non-antag conflict from happening unsupervised.
+
+These two facts can't coexist indefinitely: a server that demands believable characters cannot also run rules whose entire purpose is stopping those characters from believably colliding. Something has to give, and this document argues it should be the ruleset, not the believability.
+
+This document's thinking owes a direct debt to Taydeo's essay ["I just want to play the video game"](https://taydeo.substack.com/p/i-just-want-to-play-the-video-game), which argues that expecting the game to protect a player's individual comfort, survival, or control over outcomes is itself entitlement, at the expense of everyone else's story. 
+An antag-required design panders to exactly that entitlement: it promises players a legible, fair, rules-mediated threat instead of asking them to live with the unpredictability of other real characters. 
+This document treats that essay as required reading alongside it, not just a citation, and returns to its arguments repeatedly.
+
+Beyond this, the same entitlement shows up institutionally, not just in individual play. The broader design discussion around Funky has repeatedly circled the same tension this document tries to resolve directly: proposals tend to frequently get pushback on the basis of how it would interact with antagonists.
+In practice this shows up as a recurring veto: 
+
+*"we can't do this because what if antags"* or *"this will harm antags"*. 
+
+Often applied to gameplay changes that have nothing to do with antagonists at all. This document takes the position that this assumption is itself the problem - it's **the** design crutch being named. Systems shouldn't need to justify themselves against *"but what if antag"*.
+
+This document is the philosophy Funky will sit on, the thing to point to when arguing that a system change doesn't need to justify itself in terms of antagonist balance. What follows is what actually changes as a result.
+## Features to be added
+
+This is primarily a design philosophy and ruleset change, not a single system. It has four core parts, plus scope notes and a minor footnote on remaining antagonist-adjacent content.
+
+1. Antagonists are optional, not load-bearing.
+Round engagement should not depend on whether an antagonist was played *"correctly"*. 
+Antagonist-adjacent content still appears, but game balance, SOP, and Security's day-to-day purpose must all make sense in a round where none do. 
+This should be true across every round. Rounds should hold up fine with no antagonist content at all.
+
+2. Escalation rules are removed.
+The current escalation rules exists to prevent conflict between crew from happening without in-character justification. While this is better than outright forbidding escalation (self-antagging in other servers), many players still feel like they will be punished for over-escalating, even if the action in question is something their characters would realistically do. 
+Removing it means crew members can react to each other realistically and authentically, including with violence, based on their character and the situation, not formal ruling gating when IC conflict is "allowed." 
+It is not a removal of standards for what counts as acceptable violence. "Play your character" remains the rule to cite against beating someone to death over a minor inconvenience. Removing the escalation ladder removes the step by step "escalation graph", not the requirement that violence stay tethered to who your character actually is and what just happened to them.
+
+3. Alignment rules are removed.
+There is no crew-vs-antag meta-layer to enforce. Characters act according to their own in-game motivations, driven by in-game happenings or events, employer, debts, and relationships, including working against other crew, their corporation, or the station's interests, without needing a game-assigned antag role to justify it. 
+Motivations need to trace back to something that actually happened in the round, not just to a character concept invoked after the fact.
+
+4. Systems that exist only to serve antag balance are expected to be reworked or removed.
+Anything currently justified purely by "but antags" should be re-evaluated by its own merits under this philosophy. If it doesn't hold up without an antag to justify it, removing it is the expected outcome, in the same spirit as prior removals like Greencomss, IPCs and Atmos Tech.
+
+None of this works if there's nothing left to fill the gap. Antagonists were doing a job. something else has to do it instead.
+
+**What replaces antag-driven engagement:**
+- Union labor disputes and strikes (pay, conditions, benefits).
+- Scrip-driven friction, i.e. bribery, embezzlement, wage disputes.
+- Department budget competition over limited scrip/resources.
+- Structural role friction by design.
+- Environmental and non-player hazards (hull breaches, fires, disease, supermatter instability, and similar)
+
+**Structural role friction by design:**
+Beyond systems, this document proposes adding built-in friction between roles and departments, as much as is possible. 
+Recent command restructuring work has intentionally separated the Head of Security from the chain of command succession specifically to create political tension between the Captain and HoS. 
+This pattern, designing roles so their interests naturally conflict, should be treated as a general, reusable principle.
+
+**What will need balancing:** 
+- Security's baseline lethality and authority need real tuning so that security don't instantly collapse rounds into early, decisive violence every time. 
+- Scrip/Unions/Budgets will also need to reliably generate friction even in rounds with low player-initiated conflict, so the game doesn't go quiet when nobody starts anything.
+
+Antagonists themselves don't need to vanish to make room for any of this; they just need to stop being the thing everything else depends on. Their defining trait, per this document's philosophy, is that they must be able to accomplish nothing, or succeed completely silently, without the round being worse for it.
+
+## Game Design Rationale
+
+None of the above is arbitrary. The core principle this aligns with is that a round's engagement should come from the systems and people actually in the round, not from some switch that was flipped at round start.
+
+An antag-balanced design is cancerous; it means every other system can quietly rot as long as the antag content is fun, and it means moments of genuine crew-driven conflict get treated as errors to be corrected by admins rather than the game working as intended.
+Removing escalation and alignment rules is not deregulation for its own sake, it's a bet that a whitelisted, RP-committed playerbase can generate better conflict organically than a designed antagonist or rules can generate for them, provided the consequences are real.
+Round-removal should be common, a heavy consequence that this bet relies on: violence has to matter mechanically, or it degrades into random chaos.
+
+That bet only holds up because of what this station actually is underneath the corporate branding. Our corporate-dystopia theming supports this directly. Security isn't some neutral peacekeeping force, it's a corporate boot, and Command cannot be good people in this setting: holding a Command position means being paid to extract more from the crew's labor than it costs to keep them working, and the moment a Head of Staff stops doing that, NanoTrasen replaces them with someone who will.
+Both are expected to be pressured, self-interested, and corrupt as an emergent, in-character reality of working for a company that doesn't care about them, not as an occasional character flaw some players opt into. 
+This is intentionally left as a cultural/RP expectation rather than as written SOP: codifying "be corrupt" as a rule is a contradiction.
+
+None of this should be mistaken for asking for a calmer server, so it's worth being explicit about what this document is not arguing: it is not asking for less violence, less death, or a quieter, lower-stakes server.
+The volume and intensity of round conflict should stay the same or even increase. The goal is to diversify where that conflict comes from, away from an antag roll being the only legitimate source of it.
+
+## Roundflow & Player interaction
+
+This will be the new default state of the game. Every round now has to hold up without antagonists, because it's likely they will not have one, or will have one whose entire presence is a footnote. 
+Round pace is expected to come from departmental friction, personal character motives, and environmental hazards rather than an antag player. 
+A greenshift should be a fun experience across every job on its own terms.
+
+Players should interact with this by playing believable characters with real motives: Greed, grudges, self-preservation, loyalty to a department or union, et cetera, allowing those collide naturally. 
+This includes Command, who are not exempt from corporate self-interest or pressure just by virtue of rank. 
+Players should not treat the absence of escalation rules as license for arbitrary violence disconnected from character or circumstance; the enforcement mechanism for that is IC consequence (round-removal, meaningful medical injuries, long arrest period and trial, etc.), not an admin deciding after the fact whether it was allowed.
+
+## Administrative & Server Rule Impact
+
+This document takes the position that admin involvement in IC conflict should become even more hands-off than it already is. The escalation rules currently gives admins a concrete measurement ("was this step skipped") to intervene on over-escalation; removing it means admins should generally let believable IC conflict, including violence, play out rather than stepping in to arbitrate whether it was "justified." 
+Admin attention should concentrate on OOC problems, i.e. metagaming, harassment, bigotry, actual griefing devoid of character motive, rather than IC judgment calls about whether a shooting was escalated properly. 
+An admin correcting a believable, if unlucky or unfair, in-character outcome is enforcing the same entitlement this document argues against; The expectation that the game owes a player protection from consequences other characters chose to hand them.
+
+Admins need clear rules and methods for distinguishing IC conflict from OOC misconduct, since the escalation rules no longer does that sorting for them.
+
+Security being expected toward violence as a corporate boot, and Command being expected to be self-interested rather than benevolent, raises the bar for player judgment in both roles. 
+A security or command main playing corruption believably is different from one being needlessly cruel OOC, and admins will need to adjudicate that distinction more.
+
+Round-removal, medical consequence, and arrest/trial systems remain the actual enforcement mechanism for in-round violence and are treated here as core systems this document depends.
+
+## Technical Considerations
+
+This all depends on Unions, Scrip, and Department Budgets being implemented and balanced, but otherwise this document mostly servers as a server philosophy piece. The rest is the re-evaluation of current content, carried out one at a time.