Allow deactivation of Connected client ids synchronization
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- csharp, unity
- Domain
- networking
Research direction
No files or tests are identified in the issue. Start by locating the server-side synchronization of connected client IDs in Netcode for GameObjects, then determine whether the intended behavior is disabling synchronization or filtering IDs by scene. Done should mean one agreed configuration and verification that clients receive only the intended connected-client information.
Written by the indexing model from the issue text.
Description
Hello, currently the server synchronizes its list of clients connected to the server with all authenticated clients on the server. In my current project, I can't think of any use cases where it's necessary for the server to synchronize all connected clients (except maybe when the server is also a client?).
Being able to disable this function would reduce the number of packets sent by the server (especially on instanced MMOs like my project, which have several hundred connections per server), reduce the chances of attacks on a server instance in one sense because it would avoid a client knowing the number of players on the server.
If this isn't possible, maybe allow to filter which client ids can be shared with clients? In the case where we have a server with instantiated/isolated scenes (as on my project) I don't want clients to see all clients connected to the server, but only the clients in the scene they are in.
- Dominant language
- C#
- Stars
- 2.3k
- Forks
- 461
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 20
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Unity-Technologies/com.unity.netcode.gameobjects
-
stat:import type:bug
Difficulty 4/5 3-5 days Newbie friendliness 68/100
-
stat:reply-needed type:support
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Unity-Technologies/com.unity.netcode.gameobjects#4095 · 10 comments ·
-
stat:awaiting-triage stat:Investigating type:bug
Unity-Technologies/com.unity.netcode.gameobjects#3912 · 5 comments · 1 assignee ·
-
Tracking type:feature-2.x
Difficulty 5/5 Over a week Newbie friendliness 35/100
Unity-Technologies/com.unity.netcode.gameobjects#3870 · 5 comments ·
-
Tracking type:feature
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Unity-Technologies/com.unity.netcode.gameobjects#3830 · 7 comments ·
All issues in Unity-Technologies/com.unity.netcode.gameobjects
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·