What causes Photon Fusion logic breaking in Host mode?

Shared mode gives each client state authority over its own objects, while Host mode routes all authority through the host, so code that mutated networked state locally no longer has permission to do so.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix Photon Fusion Logic Breaking After Switching to Host Mode

Quick answer: Move state mutations behind authority checks, use input authority plus RPCs to the state authority, and pick the topology deliberately rather than assuming Shared-mode behavior.

Fusion code that ran fine in Shared mode and falls apart in Host mode is hitting the authority model. In Host mode only the host can change networked state. Here is how to adapt.

How to fix it

1. Check authority before mutating

Only the object's StateAuthority may change networked properties. In Host mode that is the host, so guard mutations with Object.HasStateAuthority and route client intent through input or RPCs.

2. Drive changes from FixedUpdateNetwork

Apply state changes inside FixedUpdateNetwork on the authority using GetInput, rather than reacting to local Unity input on every client. This keeps Host and Shared paths consistent.

3. Pick the topology on purpose

Decide between Shared and Host mode based on your cheat and authority needs, and set GameMode accordingly at StartGame. Do not develop in one and ship the other expecting identical behavior.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Unity error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Ship the fix, watch the signature disappear from the next build. That's how you know it's really gone.