Fallout 4,
together

The shooter decides the hit, because its game is the only one that saw the target where it aimed. The server stamps who fired from the connection itself, so nobody shoots on another player’s behalf, and a script can refuse the hit before the victim ever takes it.

Every projectile a player launches is sent as the launch the game built, and every other client fires the same one from the thrower’s stand-in. Only the thrower’s game decides where it goes off; the blast, the hazard it leaves and the hits it causes are relayed from there, so a grenade cannot hurt the same person twice. Mines are the server’s: it streams them armed, it decides when one goes off, and a script can set one off or lift it unexploded.

Getting into a frame and out of it goes through the game’s own entry and exit on every client, so other players see the suit close around you, see the pieces on it with their mods, and find the frame standing where you left it. Each piece keeps its condition wherever it goes. The fusion core’s charge is replicated too, and every core a player loads or launches out is checked against the server’s inventory record first. A script can read what a player wears, put them in a frame and take them out again.

What you carry is the server’s record, not your client’s. Every change is checked against it: you cannot lose items you never had, and a refused change is answered with the truth and rolled back. Each stack keeps its condition, so a half-spent fusion core stays half-spent wherever it goes.

Every door, lock and container is synchronised. Which doors stand open and which locks are locked is the server’s say, held for the whole session and handed to anyone who joins late, so a door you shut stays shut for everybody. A container’s menu belongs to one player at a time, and what they leave behind is what the next player finds.

Every item on the ground can be picked up exactly once. The first player to ask for it gets it and every other client disables its copy, so two people can never walk away with the same stimpak.

At startup the server takes over the placed actors of every worldspace and interior in the game’s own master files, rolls each leveled list once so every client builds the same NPC, and walks the ones no player is near along the navmesh. A dead one comes back where it was placed. A script can make any of them a player’s companion, and the server takes it along when its leader travels.

Appearance, outfits and the weapon in your hands replicate, mods and ammo included. A server can capture the look of any actor in the game, hand it to a player, or open the look editor on demand, then store the look a player made and put it back next time. Scripts can put a player into any of the game’s own idle animations, and everyone else sees the pose.

Positional voice chat with ranges the server controls, per player and per tier, down to muting and deafening individuals. Each talker is a voice in the game’s own audio engine, placed in the world and mixed by the game the way every other sound is, so a voice falls off behind a wall instead of sitting on top of the mix.

A script puts a station on the Pip-Boy’s dial and decides what goes on air. Every client carries it as a transmitter of the game’s own radio, so it plays through world radios tuned to it as well. The server stamps when a track started and each client seeks to that moment, so somebody tuning in late hears the same bar as everyone else. The game’s own stations can be taken off the dial and put back.

Set the hour, run the day fast or hold it still, force a radstorm or let the weather turn on its own. The world’s state is one replicated entity, so a late joiner arrives into the same afternoon as everyone else.

Client resources open Chromium web views over the game, so a HUD, a menu, a scoreboard or a shopfront is just HTML, CSS and JavaScript, positioned and sized from script. Messages pass both ways between the page and the resource that owns it. A view is locked to its own origin and torn down with the resource that created it.

Client resources also drive the interface Fallout 4 already has: HUD notifications, quest banners, subtitles and help text, screen fades, menus opened and closed by name, the game’s message boxes, and the dialogue wheel with lines of your own. The pick comes back to the script that asked for it, so a conversation can be written in TypeScript.

Level, XP, perks, S.P.E.C.I.A.L., caps and what you are carrying are the server’s record. The game’s own level-ups, perk chart and S.P.E.C.I.A.L. menu still run on your machine; every change they make is reported, replayed against the server’s copy and put back if it does not hold up. A script can award XP, grant a perk, or refuse one before it sticks, and the gamemode keeps the whole character between sessions: the default one saves it to its database and hands it back when you log in.

A resource can ship loose files, plugins and archives. The client holds the handshake while they are checked, unpacked and mounted as game data, then the game loads them the way it loads any other content, so you walk into a Commonwealth the server has changed without installing a thing.

Client resources can put markers on the compass and the Pip-Boy map, read the camera and turn a world position into a point on screen, play sounds, tint the screen, shake it, and place objects only that player sees. A script can also take the game’s free camera, fly it, and set the player down wherever it stops.

Multiplayer sits in the game’s own main menu: browse the public masterlist, find servers on your network, keep favourites, go back to recent ones, or connect straight to an address. Search, filters and sorting included.

The default gamemode is a working base for a roleplay server. Players register or log in at Red Rocket, make their character in the game’s own look editor and S.P.E.C.I.A.L. menu, and come back as it. Staff ranks gate the commands, plain chat is local speech under the character’s name, /me, /do, /ooc, /pm and the rest are there, and /pay hands caps across. It is all TypeScript you can read and change.

A dedicated binary configured by one server.json, with its own resources folder, an interest grid sized to the Commonwealth, and a listing in the masterlist only when you ask for one. Windows and Linux builds are published from CI, the Linux server as a container image you can pull, and the launcher patches a player’s installation to the right build before it starts the game.