Precinct IX

Overview

Precinct IX is a cyberpunk police management and turn-based combat game from indie studio ZataForge, planned for release in 2026 on Windows, macOS, and Linux. You are the commanding officer of Precinct IX, a broke, understaffed police station in a future city where cybernetics are common and unstable. Your officers are all cybernetically augmented women, each carrying abilities, a personal history, and secrets she will not easily volunteer. As trust deepens, their personal stories open up, and the rotten truth beneath the city starts to surface.

The game is a deliberate hybrid: precinct management sim, visual novel with branching character storylines, turn-based tactical combat, and relationship building in the tradition of Persona's social link system. The developer calls this a five-layer design, and all five layers feed into each other. Management decisions determine which officers are available. Dispatch choices determine which cases resolve. Case outcomes determine the relationships that unlock character stories.

Who it's for: Fans of XCOM-style base management, Disco Elysium's moral weight, Persona's social links, and Invisible Inc.'s dispatch tension. Anyone who wanted This Is the Police with more depth and more neon.

Who it's not for: Players who want a single-genre experience, fast action, or a power fantasy. This is a game about scarcity, pressure, and hard choices. The power curve is about surviving, not dominating.

Mac warning: the Steam listing specifies the game is NOT compatible with macOS 10.15 Catalina or above, limiting it to macOS 10.14 Mojave or earlier. Steam dropped its own client support for macOS 10.14 in February 2024, so the practical compatibility of the macOS build with any currently maintained Mac is in question. Windows and Linux are the safer platforms.

---

The Five-Layer Design

The core of Precinct IX is five systems that interact rather than sit side by side. Understanding how they chain together is the difference between commanding a precinct and drowning in one.

1. Intake. Complainants, informants, black-market dealers, and representatives from institutional power arrive with requests, agendas, and pressures. You decide which cases to accept, negotiate terms, and contend with bribery and conflicting motives from the first screen.
2. Resource management. Budget, manpower, weapons, cybernetic components, and medical supplies are finite. Everything must be allocated before officers are ever dispatched.
3. Officer selection. Each officer has distinct capabilities that determine fit for a given incident type. The right officer turns a hard case easy; the wrong one turns an easy case fatal.
4. Field resolution. Cases close through dialogue choices, field commands, or turn-based tactical combat. Outcomes feed back into the precinct's operational state.
5. Relationships. Trust accumulates through every command decision and shared outcome. High trust unlocks individual character storylines, which is where the systemic corruption behind the official cases becomes concrete.

Every decision in layer one spends resources in layer two, which constrains layer three, which determines layer four's outcome, which feeds layer five. Plan across all five at once.

---

Getting Started: Your First Session

Before You Launch

1. Understand the two-layer loop. You play the management layer (office, cases, resources) and the tactical layer (dispatch, turn-based combat). Neither works without the other.
2. Read your officers' files. Their abilities, pasts, and secrets are both content and mechanical advantage. A file read now saves a lost officer later.
3. Expect scarcity. You will not have enough of anything. Budgeting is the game.

Your First 30 Minutes

1. Receive your first visitors. Complainants, informants, and black-market dealers step into your office. Accept cases, negotiate terms, allocate resources.
2. Build your case board. Each case has threads: witnesses to interview, scenes to visit, suspects to interrogate.
3. Dispatch carefully. Choose the right officer for each case based on abilities and condition. A wounded officer is a liability, not a hero.
4. Run your first encounter. Position, abilities, and target priority decide outcomes.
5. Watch the budget. Equipment, loadouts, and medical support drain it fast. Prioritize cases that pay.

Beginner Mistakes

---

Core Mechanics Explained

The Resource Triangle

Three resources anchor everything: budget, manpower, and medical support. Weapons and cybernetic parts sit on top of them.

Case Types and Threats

The city throws recurring incident types at you: runaway cybernetics, memory contamination, hacker attacks, abnormal sightings, and street riots. Each demands a different officer profile. A hacker case wants a technical specialist; a riot wants raw combat power; an abnormal sighting wants an investigator with high perception. Match the officer to the incident type or accept the consequences.

The Investigation Layer

Cases unfold through investigation: interview witnesses, visit crime scenes, gather evidence, interrogate suspects. Every lead costs time and manpower. Investigation is a resource-intensive process, not a free exploration mode. Case outcomes change through dialogue, command, and battle.

Turn-Based Combat

Combat is the tactical payoff. You command your dispatched officers in turn-based encounters against runaway cybernetics, hackers, rioters, and worse. Positioning, ability use, and target priority matter. A botched operation drains supplies and damages officer morale. A clean resolution builds trust and opens access to what an officer has been quietly carrying.

The Trust System

Trust is the currency that opens officer stories. It accumulates through every command decision and shared outcome: choosing the right officer for a case, keeping them alive, making choices they respect. Officers with high trust fight better, reveal more during interrogation, and unlock narrative choices. The stories they open are where the game's promised "rotten truth beneath the city" becomes specific rather than atmospheric.

---

Progression Strategy

The Case Priority Framework

Not all cases are equal. Grade every case before accepting:

The Medical-First Budget

Fund medical support before weapons. A dead officer is a permanent loss of ability, story, and trust. Gear can be replaced; officers cannot. Medical support protects your most expensive asset, so it always wins the budget argument in the early game.

The Two-Team Rotation

Never field your best officers for every case. Build two balanced teams and rotate them: one team works a case while the other recovers. This keeps officers fresh, spreads experience, and guarantees a rested reserve for emergencies.

Early-Game Spending Order

1. Medical support (keeps the roster alive)
2. One loadout upgrade per frontliner (combat viability)
3. Cybernetic maintenance for your most-used officer (efficiency)
4. Case board expansion (more active threads)
5. Weapon upgrades (only after the above)

---

Builds / Tier Lists / Best-In-Slot

Officer Archetype Tier List

Officer rosters in the genre settle into recognizable archetypes. Precinct IX's confirmed structure (abilities, personal history, secrets) maps onto these roles:

Best-in-slot logic: build a specialist for each recurring incident type, then keep one generalist as your emergency dispatch. A specialist on their home case type outperforms a generalist everywhere; a generalist never fails you on an unknown case.

Budget Allocation Template

---

Step-by-Step Strategy

Sequence 1: The Intake Protocol

1. Let the visitor speak before you commit to anything. The first version of a story is rarely complete.
2. Grade the case: payout, threat, officer fit, story flags, time sensitivity.
3. Negotiate terms. Some cases come with strings attached; decide whether the string is worth the payout.
4. Read the subtext. Hidden motives mean the obvious choice is often wrong.
5. Accept or decline with full knowledge of what it costs your other cases.

Sequence 2: The Dispatch Decision

1. Open the case file and identify the incident type.
2. Match the officer archetype to the incident: specialist for their home type, generalist for unknowns.
3. Check officer condition. Wounded officers stay home, no exceptions.
4. Check trust level. A high-trust officer resolves faster and reveals more.
5. Allocate supplies for the operation, then commit.

Sequence 3: The Interrogation Exhaustion Rule

1. Never end an interrogation with dialogue options unread.
2. Work through every branch: hidden motives, secret connections, and case-altering revelations surface in the last options.
3. Use officer specialties during interrogation. An Investigator extracts more than a Combatant.
4. Track what each suspect contradicts. Contradictions are case leads.
5. Close the interrogation only when the tree is empty.

Sequence 4: The Turn-Based Combat Checklist

1. Survey the field before moving anyone.
2. Position for cover and sightlines; the city fights back.
3. Prioritize targets: medics and summoners first, then the biggest threat to your lowest-HP officer.
4. Use abilities on cooldown that matters, not on cooldown that exists.
5. Retreat a wounded officer before the mission ends; a live retreat beats a dead win.

Sequence 5: The Relationship Investment Loop

1. Talk to officers between cases, every time.
2. Choose command decisions that match their values; trust is earned through respect, not efficiency.
3. Prioritize cases tied to officer storylines once your roster is stable.
4. Keep the story-relevant officer alive above all else; their arc is the game's spine.
5. Let the trust you build open the corruption storyline that ties the cases together.

---

Advanced Tips

The botched-op math. A botched operation drains supplies AND damages morale. Two failed operations can cost more than the case was ever worth. If a case looks unwinnable with your current roster, decline it. Declining is a valid strategic move.

The bribery play. Not every visitor is honest and not every case is clean. Sometimes taking the black-market deal is the strategic play; sometimes refusing it is. The "obvious" choice in a negotiation is usually the trap. Read the subtext.

The story investment is the best mechanical investment. Officers with high trust improve every case they touch: faster resolutions, better interrogation results, stronger combat performance. Investing in their personal stories is not content tourism; it is the most efficient stat boost in the game.

The reserve rule. Always keep at least one officer off the board. Emergencies do not schedule themselves, and an uncommitted officer is the difference between handling a sudden riot and watching it burn a week of progress.

Scarcity is the design. The game wants you to feel the weight of commanding people, not just tokens on a grid. When you feel the pinch, that is the game working. Spend like a broke precinct commander, because you are one.

Case threads compound. Witnesses, scenes, and suspects connect across cases. A lead ignored in one case often reappears in another. Keep notes on who said what; the game rewards institutional memory.

---

FAQ / Common Mistakes

Q: Is Precinct IX a combat game or a management game? A: Both, simultaneously. The management layer (office, cases, resources, officers) and the tactical layer (dispatch, turn-based combat) are interconnected. Neither works without the other.

Q: When does it release? A: Steam now lists Precinct IX as coming in 2027. It was originally targeting 2026; the window moved during the year, with press confirming the updated timeline in September 2026. No specific date or price has been announced. The game passed 10,000 wishlists in July 2026, announced in character by the developer as one of the precinct's officers.

Q: Is there a demo? A: Not yet. The developer's "city gates aren't open yet" framing suggests one arrives closer to launch.

Q: Do officers die permanently? A: The game emphasizes limited medical support and officer condition. The scarcity framing and "no one can promise you'll come back from a call in one piece" tone strongly suggest officers can be lost. Treat every officer as irreplaceable.

Q: Will it run on my laptop? A: Minimum specs are very modest: dual-core CPU, 2 GB RAM, integrated GPU, 2 GB storage. Recommended is a dedicated GPU and 4 GB RAM with 10 GB storage. The pixel-art style keeps the footprint small. Mac users: check your macOS version carefully (see the warning in Overview).

Q: Is there controller support? A: Yes, full controller support is confirmed, alongside Steam Achievements, Cloud saves, and Family Sharing.

---

Final Verdict

Precinct IX is one of the more ambitious indie pitches on Steam: five interconnected systems running XCOM-style management, Persona-style relationships, and Disco Elysium-style moral weight in parallel. The all-female officer roster is a deliberate design choice that shapes the trust system, and the five-layer architecture gives every decision compounding consequences. The macOS compatibility caveat is a real concern for Mac players, the release has slipped from 2026 to 2027, and the lack of a demo means the integration quality is unproven until launch. But the architecture is coherent, the individual layers are proven genre templates, and the 10,000+ wishlist milestone shows real demand. For fans of management tactics with narrative teeth, this is the one to watch into 2027.

---

Case-Type Playbooks: The Five Confirmed Incidents

The store page names exactly what you'll be investigating, and each case type is a different moral problem, a different tactical challenge, and a different draw on the same five resources. Prep for each one now; adjust once launch reveals the true systems.

Runaway Cybernetics

A rogue augmentation is a combat threat with an origin story. The mechanical answer is a Frontline Combatant with heavy loadout, but the case answer is tracing where the cybernetic came from and who maintained it. Runaways connect to black-market dealers in the intake layer; a dealer who sold the part probably knows why it failed.

Playbook: Investigator finds the part's origin, Combatant stands by for the takedown, Negotiator works the dealer angle. Budget note: every runaway you resolve through force burns weapons and medical supplies. Resolve through tracing and you keep the ammo for the next riot.

Memory Contamination

The scariest case type for a trust-based game. Contaminated memories mean witnesses and suspects whose testimony can't be taken at face value — and by extension, officers whose pasts are now in question. Expect these cases to tie into the character secrets that drive the relationship layer.

Playbook: Technical Specialist for detection and decontamination work, Investigator for re-establishing what actually happened. Don't spend trust decisions quickly here; a wrong call about whose memory is real damages the relationship you'll need later in the arc.

Hacker Attacks

The technical specialist's home turf, and the case type most likely to resolve without combat. A hacker case is a race and a trace: stop the intrusion, find the intrusion's buyer. The negotiation layer matters most here — informants sell hacker identities, and institutional pressure may want the investigation to stop before it reaches a comfortable name.

Playbook: Dispatch the Technical Specialist early, before the case escalates. Accept the payout-but-no-glory resolution if it's offered; a quiet win preserves manpower for cases that can't be won quietly.

Abnormal Sightings

The investigation-heavy case type. Sightings reward perception, evidence work, and patience over firepower. The genre signal is clear: these cases are the X-Files slot, where the "rotten truth beneath the city" storyline most likely surfaces first.

Playbook: Investigator leads. Take extra time on the case board; abnormal cases are where ignored leads from other cases resurface. Keep notes on which sightings cluster geographically — the developer's consequence cascade design suggests connected incidents rather than one-offs.

Street Riots

The combat-first case type and the biggest resource sink. Riots demand raw deployment numbers, which means manpower, which means the two-team rotation matters most during riot waves. Medical support funding pays for itself here; riot injuries are the most predictable officer damage in the game.

Playbook: Field maximum officers you can afford, front-load medical, accept that this is the case type where dialogue will fail. The strategic question isn't how to win the riot — it's whether the riot was allowed to start. The intake layer usually shows you the pressure building days earlier; a cheap intervention then beats an expensive battle now.

The Consequence Cascade: Why Every Layer Feeds Every Other

The five-layer architecture isn't five minigames in a trench coat. It's a single machine where each layer is simultaneously input and output of every other. The cascade is the design distinction, so plan for it explicitly:

• A botched field operation doesn't just close a case badly. It depletes cybernetic parts and medical supplies from the resource layer, may remove an injured officer from the selection pool, and forfeits the trust accumulation that would have opened that officer's personal storyline.
• Management decisions affect which officers can be dispatched. Dispatch choices affect which cases get resolved. Case outcomes affect the relationships that unlock the characters' secrets. Secrets drive the corruption story that gives the cases their ending.

The practical read: never evaluate a decision by its layer. An intake negotiation that looks like a 5-minute dialogue scene can decide a combat encounter three layers downstream. A loadout choice that looks like an equipment menu decides whether an officer survives to open her story arc. When the game asks a small question, answer it like a big one.

Pre-Release Buyer's Guide

The game is wishlisted and waiting. Here's how to make a smart purchase decision when the gates open.

Wishlist strategy: wishlisting now costs nothing and catches the launch discount window and any pre-launch demo. If you're on the fence, the demo decision rule applies: play two hours. If the management layer makes you feel the weight of the officers as people rather than stat blocks, buy. If it feels like menus between fights, wait for a sale — the visual novel and relationship content is what carries this design, and it either lands immediately or doesn't.