fix: the master server only starts instances of zones in the ZoneTable

A transfer or private zone request started a world server for whatever
map ID it named, and for as many instances as were asked for. A new
instance now needs a row in the ZoneTable for its zone, and no more
than max_instances (masterconfig.ini, 256 by default, 0 for no limit)
run at once. The character select has no row and is always started.

A request that gets no instance is logged and dropped. Before, the
handlers went on to use the missing instance.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
Aaron Kimbrell
2026-11-10 15:37:09 -06:00
parent 5f20e0b3d2
commit e164f9aaed
8 changed files with 115 additions and 0 deletions

View File

@@ -7,6 +7,10 @@ master_server_port=2000
# The port number to start world servers on. Will be incremented for each world
world_port_start=3000
# The most world instances that run at once. The character select is always started.
# A zone or property that needs a new instance past this is not started. 0 for no limit
max_instances=256
# 0 or 1, should autostart auth, chat, and char servers
prestart_servers=1