Document voice muting based on player blocks guide#8319
Merged
Conversation
Adds a new how-to guide covering bi-directional voice muting in lobby voice
calls based on block relationships. Covers two approaches for populating
per-member mute lists — client-side using any client-accessible block signal
(Discord relationships, in-game block lists, etc.) and server-side via lobby
member metadata set at lobby creation — with a shared C++ implementation that
applies mutes in both directions using lobby member metadata.
Also documents the POST /lobbies/{lobby.id}/members/bulk endpoint for adding,
updating, or removing up to 25 lobby members in a single request.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a new how-to guide covering bi-directional voice muting in lobby voice calls based on block relationships. Covers two approaches for populating per-member mute lists — client-side using any client-accessible block signal (Discord relationships, in-game block lists, etc.) and server-side via lobby member metadata set at lobby creation — with a shared C++ implementation that applies mutes in both directions using lobby member metadata.
Also documents the POST /lobbies/{lobby.id}/members/bulk endpoint for adding, updating, or removing up to 25 lobby members in a single request.