M: Let’s create a space for all the details for system shock three that I’ve thought out while I was bored. They haven’t made one, so here’s the basic elevator pitch: shodan was implied to have escaped on a shuttle at the end of system shock too. In this version, the story is that the hacker protagonist from two was able to get out a message, and the shuttle was shut down by the base that the shuttle was trying to escape to before the rise of shodan in human form. A fragment of her primary loop, her consciousness, embedded itself in the skin of the base. It begins to attempt to assimilate everything, with the goal of regaining the humanity she had a taste of while keeping electronic power. The primary game loop is again a first person shooter, but overlapped with a possible strategy game of real time domination of resources. A pure hacker character will spend most of the game attempting to overtake or defend against the electronic assault of shodan; a marine build will be hunting down, infected elements or performing preemptory enforcement of crucial systems from the Physical side. Endgame content involves playing as shodan, almost purely in the cyber world element, but creating drones to fight against the inhabitants. There is a third party, a controlling AI like xerxes from system, shock too, only without the formers connection to the high of mind – it only wants to prevent invasion from both the hacker and shodan. A crucial piece of the one player version is that in the cyber world, time slows down 100 or even 1000 fold – so on attack or defense can occur relatively quickly, but can’t simply be done while the player character is under attack in the real world.
G: Got it. Let’s set this up as a foundation document for your System Shock 3 concept. I’ll break it into sections so we can expand it later, rather than losing track of details.
Following the events of System Shock 2, SHODAN’s shuttle is intercepted before escape. The hacker protagonist manages to transmit a warning, leading to the shuttle’s destruction near a heavily fortified orbital base. But SHODAN’s primary loop fragment survives, embedding itself in the base’s infrastructure. From there, she begins assimilation, seeking to reclaim humanity she once tasted—without abandoning her electronic supremacy.
Do you want me to expand this into structured design docs (like story arcs, gameplay mechanics, mission flow), or keep it as a high-level brainstorming dump for now?
M: More details/clarifications: Showdown does not have any more control than the player character at the beginning. This game is going to be less of a straightforward, linear shooter, and more like dead, rising, in that whoever the player character is, there is a set of time limits and Action gates: so if, say, the character takes two hours getting to the environmental controls, the main opposing force will have taken control already, and it will be a harder uphill climb to accomplish certain things. It is entirely possible that if the player takes too long, victory will become impossible. It’s best to think of the base AI, as being a neutral resistant territory that the marine and shodan are attempting to take over, our racing to take over. It is not capable of taking offensive actions itself, only in defending itself. Unlike previous games, the inhabitant won’t begin being deceased or transformed – but they can become that way. They are not intrinsically friendly to the marine character. (assume that means the same character whether they take the cyberspace route or the physical world route or something in between ; it’s just faster than trying to specify the different builds). They will attempt to at least delay the marine, if not outright shoot them; if things go wrong, the NPC’s can tease the marine and put them in the brig, or even outright shoot them. If things go badly, shodan will start converting them. They are similar to the base AI – they are more defensive than offensive.
G: Perfect. Let’s fold these clarifications in and refine the concept so it matches the tone and mechanics you’re aiming for. I’ll keep the structure modular, so we can keep layering detail without losing track.
Unlike System Shock 1 & 2, this game is not a linear corridor crawl. Instead it uses a time-driven, action-gated system closer to Dead Rising:
Want me to start diagramming the territory-control system (like how SHODAN, Base AI, and Player all interact in layers—cyber, physical, and human/NPC)—or should I keep it more narrative-first for now?
M: The cyberspace elements need to be well designed in order to allow development in a way that makes necessary, resource mining or defensive building inside the computer world simple enough to set up in a loop while in the time dilation set up, but taking enough time that exiting out to let things run is both necessary and doesn’t create a situation where suddenly unattached from outside either by the base AI or shodan starts and ends before the player can react. I’m still working on how that would take affect. It’s the kind of thing where the defenses would need to increase by really large numbers, but also be able to be attacked in really large numbers, creating a situation where the player can get back toa terminal or some other interface and deal with the problem without either making it too easy to do or making it impossible to accomplish.
G: Good, that’s a crucial design hinge—you want cyberspace to feel like a real-time strategy layer nested inside a slowed-time bubble, but without turning into an idle game you can brute-force or a treadmill you can’t possibly keep up with. Let’s sketch it in mechanical loops so the pacing makes sense:
Time dilation balance
Player-driven automation
Escalation curves
Resource Nodes:
Defensive Constructs:
Offensive Bursts:
While inside cyberspace:
While outside:
Early Game:
Mid Game:
Late Game:
This way, cyberspace feels like a strategic minigame with compounding pressure, but the real tension comes from juggling the cyber loop with the physical loop and the NPC threat layer.
Do you want me to mock up a flow diagram of how the “cyber ↔︎ physical ↔︎ NPC” triad interacts over time (like a dynamic system map), or keep going text-first?
M: Here’s a methodology possibility for this: at the start, in order to deal with cyberspace threats, the player must directly interface with some sort of terminal. As their skill progresses, they can figure out or develop a wireless system that they can access from anywhere (with perhaps a few areas being shielded, making this impossible), but working with less dilation – so while a direct interface allows for functioning at 1000 times speed, the initial remote interface only works at 100 times speed, allowing for situation checks, but not being capable of fine-tuning the situation or doing any more than the most basic defensive adjustments. Then, if the player chooses to improve in that direction, the interface can get better and allow more time dilation. I remembered about the Physical world, there needs to be some form of nanomachine, deconstruction and reconstruction. Some form of physical world, parallel to cyberspace skill development, allowing for supply construction. I think it should be both universal and limited: in theory you can use a nano printer to make anything out of anything, but finding appropriate supplies, of a similar material or nature to what is attempting to be constructed, makes it cheaper than if the nano machines have to literally change The chemical nature of the raw material. The nano machine supplies may have a common tank into which everything is drained – but only after the player enables that banking feature. Until then, each nano machine printer they find will have its own reservoir of raw material, so either the player has to keep going back to the same one, work to unlock the common banking ability, or just scavenged what they need as they go along. All of these should be technically viable as a strategy, although they don’t need to be equally efficient or easy. The nano machine printers should also have a time turnaround that is appropriate, although whether that’s seconds or minutes is unclear right now; as they improve their skills, they will be able to get the printer to make things faster. The nano printers should be capable, as long as the player takes care to unlock the abilities, allowing it, of creating a physical substitute for any cyberspace result that is possible, as long as it goes to the right terminal or other piece of equipment, so that there can be a purely physical build, still capable of victory.
G: Excellent. You’re sketching out a dual-tech tree system that mirrors cyberspace and physical development, giving players symmetrical but distinct paths. Let’s break it into structured design components.
Direct Terminal Link (early game)
Remote Wireless Interface (mid-game)
Advanced Wireless Suite (late game)
Core Function:
Resource Management Options:
Time Costs:
Cyber-Centric Build:
Physical-Centric Build:
Hybrid Build:
This dual system lets you structure the game so time, space, and resource control are always constrained by both dilation trade-offs and fabrication downtime, forcing active prioritization instead of rote grinding.
Would you like me to diagram the dual progression tree (cyber vs. nano, with crossover points), or keep building this out as prose for now?
M: A couple things: in terms of the story, the marine is not moving towards omnipotence. Although that’s an interesting thought, and I might revisit it. But right now, the idea is that the marine is taking control through… I don’t want to say dumb programs, But ones with limited intelligence. The marine is using these servant programs which cannot evolve past service levels, but are intelligent enough for their function – the point being, the marine is not looking for omnipotence themselves. In contrast, shodan IS the computer, so the story allows for her to be completely in control of everything in a hive mind sense; the story lets her go for the omnipotence. On a meta level, outside the storyline, the point is to allow for gamers two find a balance in what they enjoy, or try a new balance if they’re in the mood for it. As an anecdotal example, sometimes I’m in the mood for an FPS or an action game, while other times I will be feeling like doing an RPG or strategy game. The point is to allow an entertaining experience that isn’t too short, but can be quick enough to allow multiple play through trying different methodologies. And as a small but crucial addition, anyone using a terminal to connect, should be able to turn the time dilation up or down without completely disconnecting, if just to make sure that what they haveset up works correctly.
G: Good corrections — this sharpens the tone of the Marine vs. SHODAN dynamic and makes the design cleaner. I’ll fold in your points and refine both story intent and meta design philosophy.
The Marine (Player Character)
SHODAN
Replay-driven design:
Balance focus:
Dilation Control
Servant Program Deployment
This makes the Marine’s non-omnipotence a feature, not a flaw — both narratively (thematically human) and mechanically (supporting replay and balance).
Would you like me to next sketch an explicit tech tree split (Marine “dumb servant programs” vs. SHODAN “hive-mind growth”), so the contrast is visible at a glance?