Files
DarkflameServer/resources/masterconfig.ini
Aaron Kimbrell dce2037d9d feat: worlds starting up on the dashboard; the prestarted worlds are a setting
The dashboard shows worlds master has launched but that aren't connected
yet (Starting) and those shutting down, on the main page's world list
and in /api/worlds (state: starting|stopping), without a shutdown
button. Master's server list now carries each world's state (appended
after the UGC fields, one byte per world) and master pushes the list to
the dashboard whenever a world is launched, becomes ready, is told to
shut down or goes away, instead of the dashboard only seeing it on its
30 second poll. Starting worlds are kept apart from the running ones,
so counts, events and shutdown requests still only see running worlds.

prestart_worlds (masterconfig.ini, zone ids) lists the worlds master
starts when prestart_servers is on, instead of the hardcoded character
select (0) and Venture Explorer (1000), which stay the default when it
is missing or empty. It is on the Settings page as a zone list (restart
only), shown when prestart_servers is on.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-28 22:31:14 -05:00

25 lines
804 B
INI

# The internal ip of the master server
master_ip=localhost
# Port number
master_server_port=2000
# The port number to start world servers on. Will be incremented for each world
world_port_start=3000
# 0 or 1, should autostart auth, chat, and char servers
prestart_servers=1
# The worlds (zone ids, comma separated) started with master when prestart_servers is on. Empty: 0,1000
prestart_worlds=0,1000
master_password=3.25DARKFLAME1
# Enable the web dashboard (0 = disabled, 1 = enabled)
# Dashboard settings are configured in dashboardconfig.ini
enable_dashboard=0
# Start the UGC server, which makes and serves the meshes and icons of what players build (0 = disabled, 1 = enabled)
# Its settings are in ugcconfig.ini; see docs/UgcServer.md for the client's boot.cfg settings
enable_ugc_server=0