vars.preset Normal must be included in Startup.txt. If it isn't defined, and any other variables are defined in Startup.txt, the server will show as "Custom" (as before) -- even if those variables are correct for it to stay Normal. Our Easy setup page does this for you when it's submitted, so if you're intending to run a Normal server, our system works perfectly.
Hardcore doesn't work right except through the new vars.preset command (and, nothing can be configured after setting that preset, or it will show as Custom). These commands would cause a server to show as Custom, for instance:
vars.preset Hardcore
(after this, the server shows as Hardcore)
vars.3dSpotting false
(after this, the server shows as Custom, even though "false" is the required value for this variable)
.. the same is true for setting any other Hardcore-required variable.
Our Easy setup page does not do this. Instead, it configures all of the individual Hardcore settings in the Startup.txt and through rcon whenever it's submitted, which means that you'll need to use a workaround in order to run Hardcore in the current version of the game: After you submit the "Easy setup" page,
Go to the "File manager" page.
Choose "Admin/Startup.txt" from the drop-down as the file to edit.
Delete everything from the file, except for vars.maxSpectators and vars.commander (if applicable).
Add a new line "vars.preset Hardcore".
Save the file.
Restart your server through the "Server control" page.
Using the Hardcore preset makes var.soldierHealth 59. This should be 60.
ADKGamers wrote:So now after this latest patch, using the Easy Setup, we can change everything that's in there and still be considered "normal" and not "custom"?
What I mean is that if you select "Set normal" on the Easy setup page, it will work as intended, and you'll be Normal (at least after a restart). Changing other settings to non-Normal values will still make your server Custom.
Wraygun, yes, I made DICE aware of that. This patch doesn't actually fix much -- I suspect that it entered QA before many of these other bugs were being examined by DICE.
ADKGamers wrote:So now after this latest patch, using the Easy Setup, we can change everything that's in there and still be considered "normal" and not "custom"?
What I mean is that if you select "Set normal" on the Easy setup page, it will work as intended, and you'll be Normal (at least after a restart). Changing other settings to non-Normal values will still make your server Custom.
Thanks for clarification. Will just have to keep changing ticket counts for one server via console for now as that seems to keep the server normal.
Changing the ticket count through the Easy setup page should also work, if it works through rcon. The page just saves to Startup.txt and submits rcon commands.
Is this vars.preset new with R3 (87254)? Also, if I edit my Startup.txt and start adding back in all the variables that took the server out of Normal preset, you're saying that it'll now show as normal as long as vars.preset Normal is in there somewhere?
TimSad wrote:Is this vars.preset new with R3 (87254)? Also, if I edit my Startup.txt and start adding back in all the variables that took the server out of Normal preset, you're saying that it'll now show as normal as long as vars.preset Normal is in there somewhere?
I could be wrong but I don't think this is resolved. I still get thrown into custom when I attempt to do anything other than add a few lines such as:
vars.preset Normal
vars.maxSpectators 1
vars.maxPlayers 64
vars.serverMessage "Welcome Soldier! Visit Us Online at http://BF4Platoons.com and In Our Forums at http://Forums.BF4Platoons.com"
To startup.tx
Then save. Then restart server. Make other config changes via rcon (in my case procon).
TimSad, it's new, yes. I haven't tested with vars.preset somewhere other than the first line, but I know that if you start with a blank slate, click the Normal settings button, and save the "Easy setup" page, it will work the next time the server is restarted.
GaWebDevDotCom, it worked in my testing, but I was using the "Easy setup" page and starting from a blank file. We don't put vars.serverMessage in there (we put it in a different file instead), and I wasn't defining vars.maxPlayers, so it's possible it was one of those that hurt things for you.
tonixx, did you save the "Easy setup" page after completing the steps? After following these, you need to avoid it (or you'll have to follow them again). Those steps definitely worked for me.