Private Valorant Lobby with Subscribers: Setup, Queue, and Rules
First, choose the format for your subscriber game
It's better to launch a private Valorant lobby not on a "first come, first served" basis, but around a specific scenario. Decide in advance whether it will be a single match, a series of maps, short modes, a game for beginners, or a rotation after each map. The format determines the rosters, queue rules, and where the lobby fits into your stream schedule.
For the first run, a match with a fixed number of participants and a substitution list is easier. Open entry looks friendly but often leads to arguments over slots, random players, and long assembly times. The fewer decisions you have to make on stream, the smoother the match goes.
Create a custom game in the Valorant client
Before going live, open Play and select Custom Game. In the lobby, you can assign participants to teams, leave spots for spectators, and choose the map and game mode. Don't change settings during sign-ups unless necessary: viewers are signing up for a specific format, not a random mode at the last minute.
If Tournament Mode is available in your client version and region, you can enable it in the custom game settings. Availability of this mode may vary by region and current game version, so check it in advance on a test lobby. When the mode is enabled, a join code is generated. This is the only way to enter such a lobby without manually adding a player by Riot ID.
Don't show the code on your stream and don't post it in public chat. If outsiders have already seen the code, it's better to create a new one before the next match. Invites by Riot ID give you more control but require manually verifying names and tags. A code speeds up assembly, but viewers may forward it to others.
Set up access before announcing sign-ups
Don't open the lobby before you've explained the sign-up process to viewers. If the code appears before the rules, free slots are taken not only by queued participants: players' friends, viewers from another channel, or people who don't plan to finish the match may join.
The working scheme is simple: first a list is assembled, then selected players confirm they're ready, and after that they receive an invite or code. With manual sign-ups, a moderator verifies the Riot ID. With code entry, only confirmed participants of the current roster receive it. The downside of this scheme is that it requires discipline from the moderator and viewers, but it reduces the number of random connections.
Use a single sign-up method for the match
The main source of conflict in subscriber lobbies is slot allocation. Choose one channel: template messages in chat, a form, a separate community channel, or a queue via a bot. Don't mix methods within a single stream: some viewers will wait in chat, some will send direct messages, and some will try to join with an old code.
- State the number of slots in the current lobby.
- Keep a separate substitution list.
- Collect the exact Riot ID if you're inviting manually.
- Name the method for confirming readiness.
- Immediately prohibit holding a slot for a friend out of turn.
Sign-ups via chat are convenient with low viewership, but messages are easy to miss during an active broadcast. A form or community channel is easier to sort, but some viewers won't want to switch to another platform. A queue via a bot removes some of the routine but requires checking commands and moderation permissions in advance.
Pin short rules before assembling teams
No one will study a long rulebook before a match, especially a viewer who arrived mid sign-up. Pin the conditions in chat, the stream description, or the community channel and repeat them before issuing invites. The rules should explain not only prohibitions but also the consequences of violations.
- The player must be ready to accept the invite and start the match without a long wait.
- Intentionally hindering the team, throwing rounds, or blocking teammates is not allowed.
- Insults, provocations, spam, and streaming audio into voice chat are prohibited.
- In case of lateness, AFK, leaving, or rule violations, the slot goes to a substitute.
- The streamer's or moderator's decision on the current match is not debated endlessly in chat.
Strict rules won't please the part of the audience that expects free communication. But without boundaries, the lobby quickly becomes uncomfortable for viewers who came to play, not to argue with rule-breakers.
Build lobby assembly into your stream schedule
Player assembly rarely fits into the moment you announce the start. Someone doesn't see the message, sends the wrong Riot ID, doesn't accept the invite, or joins the wrong team. The first roster usually takes longer to assemble than subsequent ones: viewers are just learning the rules, and the moderator is checking the workflow.
Don't schedule the start of the first map right at the beginning of the stream. Set aside a separate block for sign-ups, confirmations, and lobby checks, and in your schedule, name not the exact map start time but the queue opening time. While assembly is underway, you can chat with viewers, go over the match format, or show rosters without access codes.
After the first map, rotation usually goes faster if the substitution list is ready. The downside of a tight schedule is that any delay shifts the entire stream. A time buffer lets you avoid rushing players and canceling the last match due to a drawn-out assembly.
Assemble teams considering skill differences
If one roster ends up with several strong regular players and the other with random newcomers, the match becomes one-sided in the first rounds. In subscriber games, what matters more than precise rating balance is the feeling that both sides have a chance to compete.
You can ask participants in advance to state their approximate skill level and preferred role. It's useful to distribute strong players across different teams and not always put regular teammates together. This doesn't guarantee an even score: a player may perform noticeably better or worse than usual. But it reduces the risk of a practiced five-stack facing people who are seeing each other for the first time.
Separate voice chat and appoint a moderator
A shared voice channel for all participants usually turns into noise: players talk after dying, interrupt calls, argue, or play stream audio. It's safer to keep in-game team voice chat or create separate voice rooms for each team.
Team rooms don't mix opponents' communications and help coordination. Their downside is that it's harder for the moderator to monitor multiple channels, and the streamer has to switch between them. In-game voice chat is easier to set up, but options for muting individual offenders and controlling noise may be limited.
If more than one full lobby is planned, hand off the queue and invites to a moderator. They confirm readiness, collect Riot IDs, call in substitutes, and log violations. The streamer shouldn't simultaneously play, read chat, send invites, and resolve a conflict: it breaks the match's pace.
Act consistently with AFK, leaving, and toxicity
Problems during a map need to be resolved according to a pre-announced procedure. A mistake, poor aim, or not knowing the map is not a violation. Sanctions are needed for deliberate game sabotage, aggression, constant AFK, ignoring warnings, and intentionally leaving a match.
- If a player is AFK at the start of the match, give them a short time to respond and reconnect. If there's no contact, don't wait indefinitely.
- If a participant leaves before the start, their spot goes to the next confirmed substitute.
- If a player disconnects during a map, first give them a chance to return. The ability to bring in a substitute mid-match depends on settings and the client.
- If a mid-map substitution isn't available, finish short-handed or restart only an early match — choose the rule before going live.
- If a player is toxic, stop the argument, disconnect them from the external voice channel, and don't invite them to future lobbies.
Kicking mid-map doesn't always solve the roster problem, especially if the client doesn't allow adding a substitute right away. But keeping a toxic player for the sake of formal balance is worse: they'll continue ruining the match for both teams. Don't discuss the violation publicly for long — state the decision and get back to the game.
Reduce the risk of stream sniping and code leaks
You can't completely eliminate stream sniping on a public broadcast: a participant may watch the stream from another device or get information from viewers. Don't show the lobby code, the full participant list unnecessarily, or team tactics before the round starts.
Stream delay makes on-screen information less useful but worsens live chat interaction. Hiding the minimap or switching to another scene between rounds also protects some data, but it makes it harder for viewers to follow the match. For a friendly game, basic caution is usually enough; for a series with a competitive mindset, restrictions should be tightened.
Check the lobby against a checklist before launching
- The lobby code is hidden from the stream and hasn't been left in old chat messages.
- The main roster matches the queue, and the substitution list is ready.
- All participants have confirmed readiness and are on the correct teams.
- The map, mode, custom game settings, and spectator slots have been checked.
- Participants have been reminded of the rules on voice chat, AFK, leaving, and toxicity.
- The moderator knows who receives the slot in case of lateness or a violation.
- Viewers know whether there will be a rotation after the map and who gets priority in the queue.
A couple of minutes of checking saves more time than a restart due to the wrong mode, a random participant, or mixed-up teams. It's better to issue the code, rosters, and rules in stages rather than publishing everything at the start of the stream.
Announce rotation between matches in advance
When there are many people wanting to play, keeping the same roster for several maps annoys the queue. For regular subscriber games, you can change some players after each match or assemble entirely new teams. Rotation conditions should be stated before the first map, not changed after requests from chat.
A full roster replacement looks fairer, but players don't get enough time to build chemistry. Partial rotation maintains the pace and gives teams a chance to develop teamwork, but regular participants get more airtime. Each option has a downside, so choose a scheme that fits your stream's goal and stick to it until the end of the gaming block.
Last Articles
What has changed in design and functionality We have updated the website to make working with it faster and more convenient. The main changes affect ..
Good afternoon, I've collected all the news during this time.: 1. The main news is that prices for twitch viewers have been greatly reduced, while Tw..
1. Use promo code "December2025" for a 15% discount for all our viewers2. We have reduced the base prices for our configurator and the most affordable..
Twitch services are working stably, so we are ready to cooperate with squads, resellers, service owners, bot owners, and many others.Individual te..
We have completely updated our Twitch viewer services, and they are now working stably. We only use high-quality IP addresses for the viewers.The ..
Hello everyone! Today, we are announcing a new feature—"Twitch Viewer Configurator". Now, you can customize any plan for your Twitch channel. Choo..
Greetings, I have compiled a guide for streamers, which will be very relevant at the moment. Now YouTube and twitch have disabled monetization from vi..
We have finally developed the APINow it will be more convenient for our partner sites to work with us.To update the maximum tariffs for YouTube, an up..
Due to the huge popularity of the partnership services and referral program, we have made a cooperation table. The essence is very simple: more live a..
Our Services for Streamers
Our Services for Content Creators










