Shady Shipping Wiki Underdog Studios
Under the hood

How the game fits together

The framework is what every system stands on: the round itself, the network and the data. It was built first, and no system is allowed to work around it.

The layers: what players see reads the game state, gameplay systems own their state on the server, and the framework owns the round, the network and the data
The layers: what players see reads the game state, gameplay systems own their state on the server, and the framework owns the round, the network and the data

One owner for everything

One rule applies to every system in this document:

This stops cheating, and it stops two machines disagreeing about what happened. If the courier's screen and a cop's screen disagreed about whether an arrest finished, the round would split in two. One owner on the server makes that impossible (Gregory, 2018; Epic Games, 2024).

The systems

Abdullah builds every system. Dafydd owns every gameplay number and the city map. Ieuan owns the HUD design. The team run the playtests together. Xabi owns the sirens and audio tests.

SystemWhat it doesStatus
Match, strikes and exitsRuns the round: countdown, strikes, stars, exits, resultsBuilt and playtested
Arrests and the drop-inArrest ring, the strike cutscenes and dropping the van back inBuilt
Parcels and jobsJobs, loading bays, parcel tiers, ditchingBuilt and playtested
Money and profilesRound cash, wallets, pay, the host's databaseBuilt and playtested
Heat and detectionWhat each side knows: radar, search circles, sightingsBuilt and playtested
DispatcherPages from the boss that change a run mid-driveHooks built, director planned
Police tools and abilitiesTwo abilities per player, for both sides10 of 18 built
Vehicles and damageHandling, health, dents, wrecks, cameras, soundBuilt and playtested
DestructionScaffolding that collapses, props, balloon pedestriansPrototype only
Traffic and pedestriansCars and walkers that fill the cityPrototype only
Lobby and garageReady-up, the name wheel, the garages, the trip to the cityBuilt and playtested

How the systems talk

Read across: the row system sends something to the column system. It shows where a change in one system ripples into others.

FromSends toWhat
Lobby and garageMatch, Vehicles, Abilities, MoneyWho drives the van, each player's look and abilities, purchases
ParcelsMoney, Match, HeatA delivery (pay and stars), the cargo tier
HeatPolice radarSearch circles, blips, sightings
ArrestsMatchA full arrest bar becomes a strike
VehiclesMatchA wrecked van becomes a strike
MatchDrop-in, MoneyEach strike starts the drop-in and pays the cops
Police toolsVehiclesNet drag, burst tyres, an EMP switch-off

Two things stand out. Match is the only system that starts and stops others, so round-flow bugs have one place to live. Vehicles is the most connected system, which is why it was built and tuned first: our pitch named bad driving feel as the biggest risk to the game.

The flow of a round

The flow of a round, from the lobby to the results
The flow of a round, from the lobby to the results
StageWhat happensHow long
LobbyReady up, the name wheel picks the courier, each player picks abilities and customisesGarage 90 s
Trip to the cityA team-styled cover hides the map load; the round waits until every PC runs smoothlyUp to 90 s
CountdownEach player sees an intro of their own car, then GO5 s
RoundDeliveries, chases, strikes and drop-insUntil a win
ResultsEach player's round summary from the host's database10 s

A round can end in only two ways, and the server decides both.

EndingRuleResult screen
The van escapesAfter the first star, drive through an open exit at speedThe van wins, with its star bonus
Third strikeThe van is wrecked or arrested for the third timeThe police win: WRECKED, or BUSTED for an arrest

Each stage switches a fixed set of systems on. This follows finite state machine practice: states never overlap and changes between them are explicit, so a system can never run in the wrong part of the round (Nystrom, 2014). For example, police tools cannot fire during the countdown.

Online design

Every system is designed for a host machine that decides everything. The design rules are:

RuleWhy
The server decides every outcomeNo player can cheat or disagree
Each car is predicted on its own driver's machineSteering feels instant at 50 to 70 ms of lag
Effects done to a player are never trusted to that player's machineA van cannot ignore a net or an EMP
Times are sent as an end time, not a ticking numberOne message instead of one every second
Destruction shares the result, not the physicsDebris may differ; the blocked road never does
The police screens only show what the heat system allowsThe courier's job, bays and parcel are never sent to police PCs

How each rule is built is in the Technical Specification.

The tuning sheet

Every gameplay number lives in a table the game reads, not in code. The numbers are kept in one Google Sheet shared by the team. Dafydd owns every value, and the safe range next to each one becomes the limit in the code. A change in the sheet reaches a running game in 5 to 10 seconds, and in an online round the server passes it to every player, so everyone drives on the same numbers.

The big decision: where the master sheet lives. Each option was built and timed with a real phone edit.

OptionForAgainstVerdict
A copy in source controlVersioned, works offlineCopies go stale; needs a lock rule; no phone editingRejected
A shared OneDrive folderStays an Excel fileA phone edit took over 5 minutes to arriveRejected
A OneDrive share linkStill Excel, no sync appAbout 25 s per edit; uni accounts may block linksFallback
A Google Sheets share linkEvery phone edit arrived in 5 to 10 s; several editors at onceLeaves Excel; needs the internetChosen

Google Sheets was the only option that delivered a phone edit within one five-second check every time. The game can read a OneDrive link too, so the choice can be reversed by pasting a different link. Abdullah and Dafydd made this call together.