Changelog

0.1.1

• Belt bags may hold the Vesper Gold nugget (Josh's decision). It is a native SimpleMoons item, and SimpleMoons lets belt bags take it. Before, the firewall's vanilla belt bag rule threw it out of bags every 2 s, and a client who bagged one got a forged-request strike that leads to a ban. A new config entry, Firewall / BeltBagAllowedScrap (default 51020=Gold nugget, so item id 51020 AND the name Gold nugget must both match), is exempt from both the 2 s sweep and the host's forged-request check. All other scrap is still forbidden, and the 15-item limit and the other bag checks are unchanged.

0.1.0

• New plugin, split out of SimpleSell 0.1.39. Everything about running the lobby moved here unchanged: the whitelist and its perks, bans (by real Steam ID), Steam identity checks, the lobby guard, the RPC and item firewall (lever, purchases, routes, furniture, chat, items, sell desk deposits, belt bags, desk janitor), late join and reopening the Steam lobby, safer joins, the invisible-joiner and crew-list fixes, the join log, the hidden mod tag, the longer host chat box, and the commands /lobby, /players, /kick, /guard, /whitelist, /ban, /unban, /bans. /help lobby lists them.
• Settings come across by themselves. On the first run every [Lobby] and [Firewall] setting and [General] CommandPrefix is copied from local.simplesell.cfg (same names), and the join log from SimpleSell.playerlog.txt. SimpleSell's file is only read.
• No double running. Next to SimpleSell 0.1.39 or older (which still has all of this) SimpleLobby does nothing and tells the host once. With SimpleSell 0.1.40 each plugin answers only its own commands; one whitelist covers both (SimpleSell asks SimpleLobby), and SimpleHQ's bank still finds it through SimpleSell.
• Works without SimpleSell too. The messages a whitelisted friend's game receives keep their old names (SimpleSell.Trust, SimpleSell.LateSync), so friends on SimpleSell 0.1.38/0.1.39 keep their perks.
• New: scrap guard ([ScrapGuard], on, warn). Other players' games may only post the system chat lines a vanilla game sends, and a chat line that is only a scrap readout isn't relayed, so client mods that post interior scrap counts to the lobby (abu AutoScan with HostOnly off, AutoTerminalScanClassic in Everyone mode) reach no one, and you're told who. LCBridgeOverlay (which asks the host first, and stays off here) is named in the report. Action Log | Warn | Kick; whitelisted players are never kicked by it. /guard scrap on|off|log|warn|kick. Counters that only show numbers on their own player's screen can't be stopped by a host (every game already has the scrap; the vanilla terminal scan counts it too); see README.
• Lobby guard reports now name a known mod when its message is recognised.