Muting and reporting
Mute or report a player from the leaderboard in the lobby, or report through the Meta menu if you are mid-round. Include the round, the room and roughly when it happened: GILLA's accounts are PlayFab-backed, so a time is what makes a report checkable.
Checked 18 November 2026 against gillavr.com and the game's privacy policy.
GILLA has two controls that decide whether a session is fun: mute and report. Both are in the lobby leaderboard, and both are easy to forget in the middle of a round. Neither is a replacement for the other. Mute is for you; report is for the next person.
Where the controls are
| Action | Where | When to use it |
|---|---|---|
| Mute a player | Leaderboard in the lobby | Immediately, for your own session |
| Report a player | Leaderboard in the lobby, or the platform menu | When the behaviour breaks the rules |
| Leave the room | Back out to the lobby | When the room itself is the problem |
The leaderboard route is the in-game one. The platform menu route works from anywhere, including mid-round, which matters because the worst behaviour usually happens when nobody can reach a lobby.
Muting is not a punishment, it is a setting
A lot of players treat muting as an accusation. It is not. In GILLA, voice is positional and comes out of your ape's mouth, which means a loud player near a monster is actively dangerous to the team.
Three cases where muting is the correct tactical play, not a social one:
- A player narrating near the Grinner. They are broadcasting your position. Mute them and keep playing.
- A player with a hot mic and background noise. Same reason, plus the game hears the noise too.
- A player who is going to shout at a wipe. You already know how the round ends; you do not need the commentary.
Reporting with something usable
A report that says "he was being annoying" cannot be checked. A report with a time and a room can. GILLA's accounts are PlayFab-backed, so the developer has session records; what they need from you is enough to find the right one.
Include these five things:
- The mode — ROAM, HUNT or Don't Splash.
- Roughly when — an hour is enough, a minute is better.
- The room — public or private, and the map if the mode has one.
- What happened — the sentence, the action, the thing that was done to whom.
- The player's display name exactly as shown. Not the nickname you gave them.
Screenshots help, and on Quest you can capture the last thirty seconds from the system menu, which is usually all the evidence anyone needs.
What the game's rules actually forbid
The developer's fan content page covers player conduct in terms of assets rather than behaviour, but it names the categories that get accounts actioned: modified or cracked copies of the game, cheats, hacks, and mod menus made by players. Those are bans, not warnings.
Harassment, hate speech and the usual platform-level rules sit with Meta rather than the game, which is why the platform menu route exists and why a report there is not wasted. Two reports, one in each system, is a reasonable use of two minutes.
Dealing with the specific griefers this game produces
| Behaviour | Why it happens here | Best response |
|---|---|---|
| Screaming into the mic near a monster | Voice is a mechanic; noise pulls the Grinner | Mute, then report if it was aimed at you |
| Refusing to open the locked door | The keycard holder controls access | Leave. There is no vote-kick in the build |
| Body-blocking a doorway | Arm locomotion makes bodies physical | Walk away and take the other route |
| Team-killing in HUNT | The monster slot attracts it | Report, and switch to a private room |
The doorway one is worth naming because it is the most GILLA-specific: a player standing still in a corridor is a wall, and your movement is physical. There is no shove button documented, so the answer is the second exit, not the confrontation.
Building a room that does not need reports
The most effective moderation in a game with private codes is the code itself.
- Run a private room with people you know for the modes where behaviour matters most.
- Change the code after a bad session. Codes are the only access control; treat one that leaked as public.
- Keep a small group. Three players means everyone is accountable and every round is a fresh monster roll.
The private-room mechanics are in private rooms and joining friends. If what you are dealing with is a technical failure rather than a person, known issues is the faster read.



