feat(config): zone_override_dir and the limits of edited zone files

World, master and chat servers read files under maps/ through the override folder
named by zone_override_dir (empty: off). The settings for who may send zone files
and how large a set may be are in sharedconfig.ini and the settings catalog.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
Aaron Kimbrell
2026-11-10 18:25:53 -06:00
parent f34577b5a2
commit d124372973
5 changed files with 35 additions and 0 deletions

View File

@@ -130,3 +130,19 @@ replay_sandbox=0
# Live database (sandbox): Set by the capture tool in replay sandboxes: the real server's SQLite file, which a sandbox
# refuses to open. Read when the server starts.
replay_live_sqlite_path=
# Edited zone files (docs/ZonePublish.md). A folder for zone files sent by an external level editor: a file under
# maps/ is read from <zone_override_dir>/maps/... when it is there, and from the client otherwise. The client's own
# files are never written. Relative to the servers' folder unless absolute. Empty = off.
zone_override_dir=
# The lowest GM level that may send, restore or clear a zone's edited files (the account also has to hold the zone's lock)
zone_publish_gm_level=9
# The lowest GM level that may take any zone's lock without being one of its editors, take a lock away, and assign editors
zone_lock_admin_gm_level=9
# Limits of one set of edited zone files: megabytes per file, megabytes and files per set, objects in its scenes
zone_publish_max_file_mb=64
zone_publish_max_total_mb=256
zone_publish_max_files=128
zone_publish_max_objects=100000
# How many replaced sets are kept per zone to go back to
zone_publish_max_backups=20