Apply uniform Base64 encoding for RCON options and standardize operation names

This commit is contained in:
2026-08-26 15:06:30 +02:00
parent d0d466881e
commit 3bebae73ed
6 changed files with 21 additions and 10 deletions

View File

@@ -9,10 +9,10 @@
-- tokenization regardless of which token form matched. Base64 has no quote
-- characters in its alphabet, so it survives changeoption intact.
--
-- Only the request channel needs this: responses are written via
-- ServerOptions:putOption (a direct Lua/Java call, not the RCON text-command
-- path) and read via showoptions, neither of which goes through the
-- tokenizer, so they carry raw JSON unmolested.
-- Applied uniformly to every RconDataBridge_* option in both directions
-- (see RDB_OptionsRegistry.register/set), not just the request channel that
-- strictly needs it: a client only ever has to deal with one rule ("every
-- value is base64"), never a request-only exception to remember.
RDB_Base64 = {}