You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Receive the server's banned/approved mod policy (setModPolicy action) and colour
each opponent mod in the lobby list: red (banned), green (approved), white
(unknown). Unknown stays white — we never auto-flag what we can't classify.
- matchmaking.lua: classify_mod / get_banned_mods match the policy case- and
punctuation-insensitively, with version-prefix matching and a dash-boundary
heuristic so a glued "id-version" wire string still resolves (e.g.
"Saturn-0.2.2-E"). The approved list mirrors banned.
- action_handlers.lua: setModPolicy handler sets MP.BANNED_MODS / MP.APPROVED_MODS.
- lobby.lua: colour mod rows via classify_mod.
- start_ready_button.lua: banned warning text uses light/white (readable on the
lobby background).
- core.lua: MP.APPROVED_MODS default fallback.
Pairs with the server (BalatroMultiplayerAPI-Server), which sends the policy on
lobby join, and the website (www), where staff manage the lists.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
0 commit comments