Quick answer: Host the party voice channel on a party-scoped lifetime independent of any match, and migrate members between match audio and the persistent party channel rather than recreating it.

A party that loses voice every time it returns to the lobby or starts a new match has its voice tied to the match lifecycle. Hosting party chat on a party-scoped channel that outlives any single match keeps the group talking continuously.

How to fix it

1. Scope party voice to the party

Create the party voice channel when the party forms and keep it alive for the party's lifetime, independent of any individual match session.

2. Switch channels, do not destroy them

When entering a match, move members into match voice but keep the party channel alive in the background, and return them to it on match exit instead of rebuilding it.

3. Reconcile membership on changes

When players join or leave the party, update the persistent channel's membership directly so the party voice always matches the current group.

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 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.

Most of the time the fix is small. Seeing the failure clearly is the part that actually costs you.