This is for organizers and players who have several friends but struggle to assemble ten reliably and split two teams credibly. Searches that look similar can hide very different outcomes.
A full headcount can still stall through duplicated roles, skill gaps, late arrivals, sudden departures, spectator interference, and disputes over publishing results.
This guide treats “League custom game finder” as the main task while covering “LoL in-house recruitment” and “League 5v5 custom game” without pretending one setting fits every PC, mode, or team.
Before installing an app or joining a group, verify the current version, game mode, audio path, storage budget, region, and active hours that can materially change the result.
Gather ten for a League custom game in a DOR guild
A custom game only starts when ten people show up at the same time. Instead of collecting replies scattered across chats, gather everyone in one DOR guild schedule so you can see who is confirmed. If you are starting a guild just for in-houses, use the guild recruitment template.
- Title the schedule "Saturday night League 5v5 custom", set 10 players and pick the Scrim mode; as people join, the status moves from Recruiting to Closing soon to Recruitment closed.
- People who join plan roles and team assignment time in the schedule chat, and guild members get a notification about the new schedule.
- After the games, follow the DOR users you just played with in one click, or use Create a guild with these friends to keep the group for the next in-house.
League custom game finder: Define the outcome and failure condition first
Publish region, time, mode, broad experience range, primary and secondary role, voice expectation, standby list, and team assignment time. Decide before game one whether teams stay fixed or can be adjusted once.
The best choice is not automatically the most famous tool or the biggest server; it is the option that produces a repeatable result under your conditions.
Run a short recording test or a one-match conversation, then note output quality, response time, setup cost, and anything that would make you stop. Preserve the original file, settings, and recruitment message so you can reverse course without losing work.
Compare the practical options
| Option | Best fit | Check before committing |
|---|---|---|
| Organizer-balanced teams | The host knows participants’ play patterns | Publish assignment criteria and the single rebalance condition |
| Captain draft | Team selection is part of the event | Protect the last pick and prioritize role coverage |
| Random then one role swap | A fast and transparent start matters most | Only fix obvious role collisions |
A repeatable workflow
- 1Lock time and headcountConfirm ten players and two standbys30 minutes before start, with the late cutoff and replacement time in the post.
- 2Collect minimal role contextAsk for primary role, backup role, and recent play level; avoid collecting unnecessary account or identity information.
- 3Read the lobby rulesConfirm champion restrictions, spectators, pauses, remake, voice channels, result screenshots, and clip publication in one minute.
- 4Review after game oneDiscuss punctuality, role failure, and technical issues instead of blaming results, then use the agreed adjustment rule.
Pre-publish or pre-join checklist
- Ten players and standbys are confirmed
- Primary and backup roles were collected
- Team assignment is public
- Remake and spectator rules are written
- Voice and clip consent is confirmed
Turn the search into a useful next step with DOR
Use the League game page and public clips in DOR as conversation context, but the organizer must verify participants and make team assignments directly. Continue with League game page, League Discord finder, ranked fives team finder.
DOR helps you find players on the guild explore page and gather a party with guild schedules, while you check skill and attitude yourself in a short trial match.
Use public game pages, clips, and community context to understand play style, then verify the player name, region, schedule, and server rules yourself before moving the conversation.
After the custom game: keep both teams' POVs in one highlight
After an in-house 5v5, people often talk about how the same teamfight looked from the other team's screen. DOR's Party Clip lets party members who recorded the match with DOR each upload one clip from their own point of view (3 to 30 seconds), then joins those clips into a single highlight video.
In League, it treats the players who were in the same lobby before the game started as the party, and when party members are split across two teams, as in a custom game, the editor shows Blue Team and Red Team tabs so you can view each side separately.
After the game, open that match's room from the Party Clips tab in the DOR desktop app and check the participant list to see whether players on the other team were grouped into the party too; if they are not listed, build the video from your own team's POVs.
- When you go over the lobby rules, agree on clip consent and on who will play with DOR running. Clips can only be uploaded from each player's own PC recording, so a player who did not record will not appear in the video.
- Each player can upload one clip, and it can't be changed after uploading. Decide first whether both teams will upload the same teamfight from opposite sides, or different moments that follow the flow of the match.
- For players who don't use DOR, use Copy invite link and post the link in your in-house Discord channel; opened in a PC browser, it shows the clips already uploaded without signing in. The combined video is saved as an mp4 on the PC of whoever made it, and can be posted to the DOR feed and shared as a link.
Official source and freshness check
Riot and Discord linking in supported regions lets players invite Discord friends and share lobby links, which can help custom recruitment, while lobby rules remain the organizer’s responsibility. Menu names, supported modes, and limits can change, so the current details were checked against official League of Legends Patch 26.13 notes.
Future updates should follow the date and version on that primary source rather than copying an undated third-party summary.
