SharePermissions

The mod provides functionality to manage and share permissions (kick, ban, start game, return to lobby) among players who you trust. That's usually for community hosts who want to delegate moderation tasks to trusted members of their group.

Quick Start

1. Install the mod — that's it, it is active right away (no codes to configure)
2. Tell your trusted friends to install it too
3. In the lobby there's a new button "Mod" next to the menu title — it opens the Members / History / Access / Settings / + panel
4. As the host, click a friend in the Members tab and promote them to moderator

Becoming a moderator

The host clicks a player in the Members tab and promotes them. That issues the player a private access token — their moderator credential. It is presented automatically when they rejoin, so a promotion persists across sessions until the host revokes it (demote them in Members, or revoke the token in the Access tab — that works even while they are offline).

There is no shared secret code anymore: earlier versions could grant moderator to anyone whose SecretCode matched the host's, which meant a leaked or guessed code silently handed out moderation rights. Now every grant is an explicit host decision.

A moderator does not have to hold every power. The host opens Members, clicks the moderator, and turns individual permissions off — kick, ban, persistent ban, Admin Menu, notes (add and delete only), and run control (start the run, cancel the countdown, return to the lobby). A newly promoted moderator holds all six, so promoting someone behaves exactly as it always has; the switches are there to take powers away. Changes apply immediately, are recorded in History, and survive the moderator reconnecting. The Access tab shows a grant's permissions next to the token when they are restricted; a moderator who is offline is adjusted by revoking their access and promoting them again.

A moderator running a version of the mod from before permissions existed still has every action checked by the host — the host is where the decision is made — but their own screen will still show buttons for things they may no longer do, and those buttons will simply do nothing. Their Settings > Diagnostics shows what they actually hold.

What's included

• Members tab: every player with their role, live talk indicator, and (for the host) promote / demote, and per-moderator permissions — six switches (kick, ban, persistent ban, Admin Menu, notes (add and delete only), run control) deciding what that one moderator may do
• History tab: searchable, filterable log of every moderation event, kept across sessions and synced to moderators
• Access tab: the host's issued moderator tokens (revoke one to demote its holder, online or not), the tokens you hold from hosts that promoted you, and a Banned players section showing the host's BanEnforcer list — with a Lift ban action for anyone holding persistent ban
• Settings tab: everything configurable in-game — no config-file editing needed after setup, plus a Diagnostics readout of live state (your version, whether your moderator token was accepted, the private channel's health, everyone's mod version) and a one-click dump of it to the log for bug reports
• Voice channel tab (the microphone icon): the private voice channel's live controls (on/off, 1-on-1 rows, volume)
• Kick/Ban buttons on the lobby player list and the in-game escape menu, for the host and moderators
• Name colors: the host picks nickname colors for themself, moderators, and individual players (Members > a player > Set name color) — shown to everyone running the mod in the lobby list, on the floating name above each player's head in-game, and on the escape menu's volume rows (toggle your own display of them in Settings)
• Run-start countdown on the Start button — everyone sees it, host and moderators cancel it with one click
• On-screen notifications of moderation events for the host and moderators
• RPC-flood protection: auto-kicks players spamming network messages (lobby only, moderators exempt)
• Role head markers in the lobby and truck: crown (host), gem (moderator), diamond (mod user)
• Private voice channel: the host can put themself and their moderators — the whole team, or 1-on-1 with a single moderator — on a voice channel nobody else can hear; see Private voice channel below
• LoadingWidget companion mod (optional, separate install): the moderation panel during loading screens — load states, who's talking, per-player local volume, kick/ban, stuck-load rescue
• Player notes: the host and moderators keep shared notes about players, tied to Steam IDs, carried between lobbies by the moderation team and shown when a noted player joins.

Private voice channel

The host turns this on from the microphone tab of the moderation panel — for the whole moderator team with one button, or 1-on-1 with a single moderator by clicking that moderator's 1 on 1 row (the rest of the team hears nothing and gets no notification; the shared History still records that a private channel opened and closed, but never with whom). Clicking another name switches the pair, clicking the current partner stops it, and a 1-on-1 ends by itself if that moderator leaves or is demoted. Once the channel is on, its members hear each other and nobody else — at full volume, anywhere on the map, through walls, across a whole level, even if one of you is dead. Everyone outside the channel simply stops hearing you, including players running no mods at all, and you stop hearing them. Talking in the channel doesn't attract monsters, and ordinary players still attract them exactly as before. Your ordinary microphone goes silent the instant you turn the mode on, so you can never be caught talking on the wrong channel by accident; the private channel itself takes a moment to connect, and the panel shows you when it's live. Switching off holds your microphone quiet for a moment longer too, so the tail end of a private sentence can't slip out into public chat.

While the private channel is on, an always-visible list in the corner of the screen shows who is in it: every member has a live volume bar that moves while they talk, a muted member shows up in red, and a member who never actually reached the channel shows up in grey — so you can see at a glance who is speaking, how loud, who can't answer you right now, and who isn't really there at all. Pick the corner — or turn the list off — on the Settings tab.

That last one is worth its own sentence: being put on the channel and arriving on it are different things, and they used to look identical. A moderator whose client is too old to know the channel exists, or whose connection just failed, sat on the list looking like someone being quiet. Now they read as absent, on the corner list and on the host's 1 on 1 rows alike.

There is deliberately no separate mute for the channel: the game's own mute is the one mute, and it applies to the private channel exactly as it applies to ordinary voice chat. Press the game's mute key (B by default) and you are muted everywhere at once — and everyone in the channel sees your row turn red. Push-to-talk works too: releasing the key silences you in the channel like anywhere else, it just shows as an idle (empty) bar rather than red, because resting push-to-talk isn't a mute. What you hear is yours to control with the + tab's Private volume slider (0–300%), which also goes all the way to silence.

It comes with some honest limits, worth knowing before you rely on it:

• It's a moderation convenience, not a secure channel. The channel's name is the only thing keeping it private — anyone who learns it can listen in.
• Revocation is by re-keying, and it costs a reconnect. The channel is re-keyed when a moderator is demoted and when a member leaves the lobby, which is what stops either of them listening in afterwards — but Photon offers no way to actually evict someone from a room, so the re-key is the only lever there is. Everyone still on the channel reconnects when it happens (a second or two of dead air), and several people leaving at once are handled as one re-key rather than one each.
• Text chat isn't part of the private channel. Whatever you type is still visible to the whole lobby, and it's still read aloud to everyone by their own text-to-speech, exactly as if the mode were off. Only your microphone is made private.
• While it's on, other mods' "force microphone on" features stop working for you. The mod deliberately holds your ordinary microphone silent while the channel is active — that's what keeps your voice out of the public room.
• A moderator running an older version of the mod never joins the channel. They stay on ordinary public voice chat instead. The corner list and the host's 1 on 1 rows show them in grey as not on the channel, so at least the rest of the team can see it — but nothing tells them they're missing it.
• An outsider who hasn't finished loading yet (or is stuck as a ghost) can still be heard through chat. The mod only silences the text-to-speech readout of players whose in-game character actually exists, so a still-loading or ghost outsider's typed messages stay audible to channel members.

How it works under the hood

Moderator clients send requests to the host's client; the host verifies the request arrives over the live connection of someone it actually promoted (an unforgeable connection identity, authorized by the access token — never a claimed Steam ID) and performs the action itself. Nothing runs on other players' machines.

Integrations

• BanEnforcer (Omniscye-BanEnforcer v4+, optional): if the host has it installed, the Kick/Ban popups and the Members panel offer Ban (persistent) - the ban is written to BanEnforcer's on-disk list, so it keeps working after restarts. Moderators can use it too; only the host needs BanEnforcer installed. The Access tab's Banned players section shows that list too, with Lift ban for anyone holding persistent ban - it's the host's own list, so a lift only affects that host, and without BanEnforcer on the host the section says so rather than showing an empty list.
• R.E.P.O. Admin Menu (proferabg-RepoAdminMenu, optional): moderators can open the Admin Menu when the host runs it and has Settings > Admin menu > Grant to moderators on (the default). Unlike BanEnforcer, this one needs the mod on both machines - it draws its own local menu, so there is nothing to unlock on a moderator who does not have it. A moderator's actions are carried out by the host and recorded in History as Admin Menu events. Covers the whole menu - settings, upgrades, kill/heal/revive/crown/truck, teleport and summon, spawning items/valuables/enemies, and the map controls. Things spawn where the moderator stands, and Kick/Ban inside it obey SharePermissions' own rules (the host is never kickable; a moderator only by the host). Note that this hands moderators cheat powers over everyone in the room, the host included - the grant switch is the control.

Misc

In folders with config files there's a sharepermissions.log file that contains all performed actions with timestamps and player names.

The mod's own interface — the moderation panels, its toasts and its popups — can be shown in Russian; English stays the default. The setting is a button at the top of the Settings tab that cycles the language and names the current one in that language: Language: English, click, Язык: Русский. On first run the mod guesses once, from the game's own selected language and then your system language, and records that it guessed so it never overrides a choice you make afterwards — delete the LanguageAutoDetected line from the config file to have it guess again. This translates the mod, not R.E.P.O.: the game's own text is unaffected.

A few things worth stating plainly:

• The button relabels itself the instant you click it, but the rest of the panel only picks up the new language the next time you open it. MenuLib panels have caused enough in-game-only surprises in this mod before that rebuilding one while it's open was ruled out; reopening it is the safe way to pick up the change.
• History's stored records — and everything moderators exchange to keep History in sync — stay English in every language, on purpose. That is what keeps an entry comparable across a mixed-language moderation team and useful pasted into a bug report, which is also why the History tab's own titles and filters are translated while the record text underneath is not.
• Diagnostics, its log dump, sharepermissions.log and the config file's own descriptions are deliberately left in English too. They exist to be read by whoever is troubleshooting a bug report, not translated for the player who filed it.