Split the monolithic test server into a reusable server core and a thin terminal launcher, and add a PySide6 developer GUI. Added server_core.py (FalloutTogetherServer) with lifecycle control, thread-safe client snapshots, stats and log listener support; added client_session.py for per-client state; added dev_server_app.py GUI and requirements.txt. Updated server.py to use the new server core, and revised server/README.md and docs/dev-log.md to document the new structure, usage, and validation steps. Protocol behavior (welcome/transform/disconnect handling and newline-separated JSON) remains unchanged.
Server
This folder is for the external multiplayer test server.
The current server is a local-only TCP test server. It listens on
127.0.0.1:7777, accepts one or more clients, reads newline-separated JSON
packets, assigns incrementing playerId values, sends welcome packets, adds
playerId and serverTime to transform packets, broadcasts transform packets
to every other connected client, and broadcasts disconnect packets when clients
disconnect.
Transform packets may include optional movement-state fields such as
isMoving, isSprinting, isSneaking, isJumping, weaponDrawn, and
movementSpeed. The server preserves these fields automatically because it
broadcasts the original transform packet after adding server-owned fields.
This is still a local prototype. It does not make Fallout 4 multiplayer playable yet.
Run
Terminal server:
cd server
python server.py
Developer GUI server:
cd server
pip install -r requirements.txt
python dev_server_app.py
Then launch Fallout 4 through F4SE and move the player. The plugin should send
local player transform packets, and this server should print matching
transform packets.
If the server is not running, the plugin should log a warning and Fallout 4 should continue launching normally.
Structure
server.py: thin terminal launcher for the local test server.server_core.py: reusableFalloutTogetherServercore for networking, lifecycle control, packet relay, stats, client snapshots, and log callbacks.client_session.py:ClientSessionstate model for connected clients.dev_server_app.py: PySide6 developer GUI that starts/stops the reusable server core, displays logs, shows live stats, and lists connected clients.fake_client.py: lightweight receiver for testing welcome, transform, and disconnect packets without launching a second Fallout 4 instance.requirements.txt: optional Python dependencies for the desktop developer GUI.
The reusable server core exposes methods intended for a future desktop dev server UI:
start()serve_forever()stop()is_running()get_clients()get_stats()add_log_listener()remove_log_listener()
get_clients() and get_stats() return snapshot dictionaries, not live
internal server state. Log listeners receive the same useful console messages
that the terminal launcher prints today.
Current Test Flow
Terminal 1:
cd server
python server.py
Terminal 2:
cd server
python fake_client.py
Then launch Fallout 4 through F4SE and move the player.
Alternative GUI flow:
cd server
pip install -r requirements.txt
python dev_server_app.py
Click Start Server, then run python fake_client.py or launch Fallout 4
through F4SE.
Expected behavior:
- The server assigns a
playerIdto each connected client and sends each client awelcomepacket. - The server receives transforms from the Fallout 4 plugin.
- The server adds
playerIdandserverTimeto each transform packet before broadcast. - The server preserves optional movement-state fields on transform packets.
- The server broadcasts those transform packets to connected clients except the sender.
fake_client.pyreceives broadcast transform packets.fake_client.pystores remote player state byplayerId.- When a client disconnects, the server removes that client and broadcasts a
disconnectpacket with the departedplayerIdto the remaining clients. fake_client.pyremoves disconnected players from its in-memoryremote_playerstable.
The fake client exists so broadcast behavior can be tested before coordinating a second Fallout 4/F4SE instance. It stores remote player transform state only; it does not spawn remote actors or send movement.
Validation
From inside this folder:
python -m py_compile server.py server_core.py client_session.py fake_client.py dev_server_app.py
Then run the terminal server:
python server.py
In another terminal, run:
python fake_client.py
To validate the developer GUI instead of the terminal launcher:
pip install -r requirements.txt
python dev_server_app.py
Click Start Server, then connect fake_client.py or the Fallout 4 plugin.
For in-game validation, launch Fallout 4 through F4SE and confirm the plugin
connects, receives a welcome packet, sends transforms, and receives relayed
remote transforms or disconnect packets when another client is connected.
Implemented
- Start local server
- Accept client connections
- Assign server-owned player IDs
- Send welcome packets
- Receive transform packets
- Add server timestamps
- Preserve optional transform fields
- Broadcast transforms to other connected clients
- Broadcast disconnect packets
- Handle disconnect cleanup
- Reusable server core with thread-safe client/stat snapshots
- Log callbacks for future server console UI
- PySide6 developer server GUI with live logs, stats, connected-client table, and a placeholder Fake Clients tab
Working In Fake Client Only
- Receiving welcome packets
- Receiving transform broadcasts
- Storing remote player state
- Removing disconnected remote players
Planned Later
- Fake client management
- Fake client movement scripts
- Gameplay synchronization
- Authentication
- Public matchmaking
- Anti-cheat
- Persistence
- Quest state
- Settlement state
- Large-scale world simulation