// Xonotic version (formatted for machines)
// used to determine if a client version is compatible
-// this doesn't have to be bumped with every release
+// general policy: previous release has "best effort" support, older releases are unsupported,
+// but gameversion_min doesn't have to be bumped with every release
// bump when clients become incompatible or any other perfectly good reason
// (e.g. game data incompatibility, engine version incompatibility, etc
// note: this automatically filters the server browser, clients of the new
// e.g. Xonotic 1.5.1 RC1 will be 15101
set g_xonoticversion git "Xonotic version (formatted for humans)"
-gameversion 802 // 0.8.2
-gameversion_min 0 // git builds see all versions
-gameversion_max 65535 // git builds see all versions
+gameversion 805 // 0.8.5
+gameversion_min 802 // 0.8.2 is the previous release
+gameversion_max 65535 // future versions should nag players to update
// compatibility guideline:
// version a.b.c = a0b0c
seta g_configversion 0 "Configuration file version (used to upgrade settings) 0: first run, or previous start was <2.4.1 Later, it's overridden by config.cfg, version ranges are defined in config_update.cfg"
+// Set the master servers to do DNS lookups we control.
+// This allows us to update the master server IPs without a release.
+set sv_masterextra1 "master1.xonotic.org:42863"
+set sv_masterextra2 "master2.xonotic.org:27950"
+set sv_masterextra3 "" // Got removed from DP, so we can't use this one for master3.
+set sv_master1 "dpm4.xonotic.xyz:27777" // gazby, soylent_cow
+set sv_master2 "dpm6.xonotic.xyz:27777" // gazby, soylent_cow
+set sv_master3 "master3.xonotic.org:27950"
+set sv_master4 "master4.xonotic.org:42863"
+
exec xonotic-client.cfg
exec xonotic-server.cfg
projects / xonotic / xonotic-data.pk3dir.git / blobdiff