Neomod Studios

SCOUT / CONNECT / DEPART

Access Routes

The two projects approach the same city through different kinds of commitment. Rainsplice centres on a short intrusion from a carefully chosen physical position. Service Ghost asks how a runner moves within the routines of a working district. Both need readable access and a credible exit, but they should not feel like the same mission with a different time limit.

1
Rainsplice fictional access route

Rainsplice

Inspect the route

Start outside the connection. The runner observes a service frontage, identifies a place to stand and compares the reach offered by nearby access points. One cabinet may expose a useful branch while leaving the runner visible from a walkway. Another may provide shelter but demand a longer retreat through a narrow passage. Once connected, the player chooses a limited objective and watches changes that affect the remaining route. The Rainsplice dossier follows reconnaissance, commitment and withdrawal as one continuous encounter. A partial result can still be valuable if the runner understands what was learned and what remains uncertain.

Open the full encounter dossier →
2
Service Ghost fictional access route

Service Ghost

Inspect the route

Follow an ordinary job before trying to alter it. A maintenance request moves through a queue, a crew receives temporary access and a service lift changes which floors are reachable. The runner studies that sequence and chooses where to participate. The interesting question is whether an action makes sense in context, not whether a disguise grants universal invisibility. The Service Ghost dossier explores temporary permissions, handovers and the moment when an apparently routine movement deserves a second look. This concept has a slower observational rhythm than Rainsplice’s short connection window.

Open the full encounter dossier →

Choose a question, not a difficulty tier

Neither project is presented as the easier version of the other. Rainsplice concentrates pressure into a local decision; Service Ghost spreads uncertainty across a sequence of dependencies. Their proposed interfaces should express that distinction. A short intrusion needs a clear picture of current exposure, while a service routine needs a record of who expects what next. Read the design record for the separate questions behind those interfaces and the studio method for the common standard of readable consequences.