MirrorNetworking / MirrorNetworking/Mirror

detect only mirror server problems (not user network or.. problems)

Open
#3,587 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
6.3k
Forks
870
PR merge metrics
No merged PRs in 30d

Description

I am using Mirror Networking and the SimpleWeb transport in Unity. I want to be able to detect when there is an issue on the server side, preventing users from connecting to the Mirror server. For instance, if the server becomes unavailable or terminates connections due to its own problems, I need to be notified of these events. My goal is to identify server-side issues rather than user-side problems.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names Mirror Networking, Unity, and the SimpleWeb transport but does not identify a file, entry point, or test. Start by tracing how SimpleWeb reports connection failures and disconnections, then determine how server-side failures can be distinguished from user network problems. Done means users receive a reliable notification for server-originated failures without misclassifying client-side issues.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, unity
Domain
game-dev, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.