Unity Multiplayer Netcode and Simulation Review
Networked shooters fail at the boundaries between simulation, time and ownership. We review what the server actually authorizes, how clients predict and reconcile, and how systems behave when latency, packet loss and player count change.
Start by documenting authority for every important state
Before comparing NGO, Mirror, Photon Fusion or a custom solution, write down which system is authoritative for movement, health, inventory, projectiles, match clock, spawning and win conditions. The hardest bugs often occur when authority is split informally: a predicted client updates health locally, the server uses a different hit timestamp, and a late correction shifts players through collision volumes.
We inspect the authority model, ownership transfers, tick rate, state history buffers and command validation. A lobby that works with two LAN clients is not a correctness test for an internet shooter.
| System | Audit question | Failure mode |
|---|---|---|
| Movement | Which tick owns collision and position correction? | Rubber-banding or diverging collision |
| Weapons | Who chooses shot origin, timestamp and target? | Unfair hits or client-forged damage |
| State replication | Which fields are relevant and at what frequency? | Bandwidth waste, stale remote state |
| Round progression | Can late packets or reconnects replay a transition? | Duplicate rewards, invalid match state |
| Persistence | When is a server-side result committed? | Lost or duplicated progression |
Prediction, reconciliation and lag compensation
For responsive local movement, client prediction can advance using local inputs while the server remains authoritative. Reconciliation must compare matching simulation ticks and replay buffered inputs against corrected state. Using inconsistent timestamps or non-replay-safe logic can produce constant correction churn even on a stable connection.
Lag compensation requires a deliberate policy: what historical transforms are stored, what rewind window is allowed, how shot timestamps are validated, and what happens when a player has extreme latency. Do not simply rewind the entire world to a client-supplied time without validation. Projectile simulation may need different handling from hitscan weapons, especially when projectiles interact with dynamic obstacles.
Tick and input history
Check tick sequencing, buffer lengths, dropped commands, interpolation delay and how commands are validated.
Authoritative hit validation
Audit rewind bounds, historical colliders, obstruction testing and weapon cooldown enforcement.
Correction visibility
Measure average and worst reconciliation distance, frequency and animation-side effects.
Host migration/reconnect
Test ownership recovery, stale state rejection and duplicate event protection where those modes are supported.
Reproduce bad network conditions deliberately
- Establish a deterministic or repeatable input sequence and a server-authoritative outcome log.
- Test realistic latency variation, jitter, loss, reordering and temporary disconnection rather than fixed ping alone.
- Record server tick time, outgoing bytes, queued messages, correction events and player-perceived motion.
- Repeat weapon scenarios around collisions and cover while comparing server traces with client video.
- Scale concurrency gradually and investigate CPU and bandwidth growth independently.
- Re-run the same network matrix after fixes, checking both fairness and responsiveness.
Bandwidth budget is not only bytes per snapshot. Reliable-ordered queues, interest management, replicated change rates and fan-out patterns determine how performance changes with spectators, AI actors and player counts. The most expensive architectural change may be a server-side entity interest design rather than choosing a different transport.
Network architecture that fits gameplay requirements
We evaluate your current transport and framework before recommending replacement. Moving a production codebase from one networking stack to another carries hidden costs: serialization, authority semantics, animation coupling, UI flow and test coverage. If the existing architecture is salvageable, targeted synchronization fixes usually reduce delivery risk.
When dedicated servers are proposed, we examine who owns game-state transitions, rate limiting, server resource constraints, match lifecycle and failure recovery. A server-authoritative model is not automatically secure; exposed endpoints and unchecked commands still create attack surfaces.
Audit report and engineering roadmap
Deliverables may include tick-flow diagrams, a table of authoritative ownership per feature, reproduction videos under a network simulator, identified race conditions and a plan for fixes ordered by fairness impact and implementation risk. If the scope includes implementation, we submit isolated changes with regression scenarios and server load measurements.
We do not publish confidential netcode diagrams or client repository contents in marketing case studies without permission.
What to send Fyros
Share a build or code access, networking framework and version, target player count, hosting assumptions, typical latency geography, reproduction of the visible failure and release timeline. Include authority diagrams and trace data if available, but do not wait until documentation is perfect to report the blocker.
What you receive
Capture manifest
A record of device, scene route, build hash and profiling configuration so the measurements can be reproduced by your team.
Bottleneck register
The top issues ranked by player impact, estimated fix risk, dependency and confidence in the diagnosis.
Before/after protocol
A repeatable test definition and acceptance criteria for each proposed fix, not an unexplained FPS screenshot.
Delivery roadmap
A practical order for high-confidence corrections, investigations requiring more data and architectural work needing a larger milestone.
An audit is distinct from a full optimization implementation. If you want us to carry out the fixes, we can agree a second milestone based on what the measurements actually reveal.
How this connects to production visuals
Rendering optimizations cannot be evaluated independently of the game's presentation. A replay camera needs believable shadows, a hero weapon needs high-fidelity surface response, and an outdoor environment needs sufficient depth to preserve visibility. Our background in Unity presentation and optimization makes those visual constraints part of the acceptance review rather than an afterthought.
See our Lacrosse 26 contribution for a real example of the kind of scene-presentation work Fyros has performed. This page does not claim a specific measured improvement from that project.
What we need from your team
Provide a player build or source access, target device list, a repeatable performance complaint, the frame-rate and image-quality requirements, and the next release milestone. If you already have captures, include them even if they are incomplete.
For private console hardware or SDK-dependent problems, all access remains subject to the platform holder's developer program and the client's authorization. The first conversation establishes whether a review is viable and what access is required.
Engagement and acceptance criteria
A focused engagement starts with a problem statement and ends with work your team can test. We agree on scope, deliverables, review milestones, data access and acceptance criteria before implementation. Outcome depends on the state of the project and measured constraints.
Questions production teams ask
Do you recommend Photon Fusion over Mirror or NGO?
No single framework is right for every project. The authority and gameplay requirements determine the trade-offs.
Can client prediction be completely free of correction?
No. Corrections can still occur due to authoritative differences, collisions and network conditions. The goal is bounded, measured correction behavior.
Is server authority enough to prevent cheating?
No. Inputs and actions must still be validated, and state transitions need security review.
Can this include a dedicated server plan?
Yes. Hosting, tick budgets, serialization and scaling can be included after the gameplay authority model is clear.
Technical references and further reading
Relevant vendor documentation for validating version-specific behavior. These links are references, not claims of a measured result from an undisclosed project.
Multiplayer development | Multiplayer architecture discussion
Explore other specialist Unity engagements or learn about co-development for active productions.
Get the problem fixed, not just diagnosed
Fyros Games Studio works with studios and publishers on scoped Unity engineering, rendering, optimization and production tasks. Share the technical blocker and we will discuss a measurable work package.
TALK TO FYROS