Keeping a LoL in-house group alive — so people keep showing up
Updated: August 11, 2026
Why in-house groups quietly die, and the things that keep people coming back — records, scheduling, and small pieces of fun.
How groups usually end
Most in-house groups don't blow up in an argument. They go quiet. The organiser gets busy, a couple of people drift off, and one week the post just doesn't appear.
The structural problem is that everything depends on one person: recruiting, splitting teams, keeping records. When that person gets tired, the group stops.
Take work off the organiser
- Replace the announcement with a sign-up sheet people fill in themselves.
- Let the team split be calculated — less time spent, fewer complaints.
- Make records automatic. Anything that has to be typed by hand eventually stops.
- Decide rule changes by vote. An organiser who decides alone also absorbs the blame alone.

What brings people back
People return because it was fun, but also because there's a thread to pick up. Last week's games to talk about, a position on a table, something to take back.
A leaderboard and personal records do that job: what your win rate is, whether it went up since last week, who you actually win alongside.
Keep some of it silly
If the only thing on the board is a serious ranking, only the top half enjoys it. Records that have nothing to do with skill give everyone something to talk about.
- Who spent the longest dead
- Who spammed the most pings
- The two people with the worst win rate together
- Who played the most different champions
These get used as ammunition, so keep an eye on the tone. In most groups, though, they generate far more conversation than the ranking does.
Looking after newcomers
The hardest part of joining is the context everyone else already shares — where the rules are, what happened last week. Without it people hover at the edge.
A group page full of records lowers that wall. Someone joining can see past games and standings immediately, and their own record starts from their first night.
Written and maintained by the ONNJ team
This guide is written and maintained by the team that develops and runs ONNJ.
If you find an error or the guide differs from the current interface, please let us know by email.
onnj.official@gmail.com