The Forest missing Parameters for dedicated Server

  • Last Post 16 February 2019
Flussburrito posted this 09 February 2019


even with the latest AMP release, I am missing the "-batchmode","-nosteamclient" as they were kind of necessary for me to get a dedicated server running in the background at all.

Also, were is the Server.cfg supposed to be, still in the "User-profileAppData\LocalLow\SKS\TheForestDedicatedServer\ds" of the executing user ? Wonder how this will work with a service running under "network service" ?

-configfilepath would help here a lot.

As another side note the ?-steamac? parameter is also passed to the executing command, even if it is empty.

My "The Forest" Server is only loading until it reaches around 760 MB memory consumption and does nothing, when I start the server manually, using the above mentioned commands it peaks around 1220 MB memory and works.

Order By: Standard | Newest | Votes
Mike posted this 11 February 2019

Have you double checked AMPs logs in debug mode to see the full list of flags it's using? Can you paste those flags?

Flussburrito posted this 11 February 2019

[21:01:19] [API:Admin Activity]   : Starting the application. [21:01:19] [Core:Admin Debug]     : Starting process ./TheForest/556450\TheForestDedicatedServer.exe [21:01:19] [Core:Admin Debug]     : Working Directory: ./TheForest/556450 [21:01:19] [Core:Admin Debug]     : Arguments: -serverip "" -serversteamport "8766" -servergameport "27015" -serverqueryport "27016" -servername "" -serverplayers "8" -serverpassword "" -serverpassword_admin "" -serversteamaccount "" -serverautosaveinterval "15" -difficulty "Normal" -inittype "New" -slot "1" -showlogs -enableVAC [21:01:19] [Core:Admin Debug]     : Started process with ID 7296

 gwmi win32_process | select commandline | format-list

 commandline : "./TheForest/556450\TheForestDedicatedServer.exe" -serverip "" -serversteamport "8766" -servergameport "27015" -serverqueryport "27016" -servername "" -serverplayers "8" -serverpassword "" -serverpassword_admin "" -serversteamaccount "" -serverautosaveinterval "15" -difficulty "Normal" -inittype "New" -slot "1" -showlogs -enableVAC

Flussburrito posted this 11 February 2019

Figured it out,

-serversteamaccount ""

If I leave this parameter out of the commandline the server will start and be available on my local lan.

This parameter can not be left blank or can not be used at all...

Still, -batchmode will save on CPU/Memory

PS C:\Windows\system32> Get-Process the*

Handles  NPM(K)    PM(K)      WS(K)     CPU(s)     Id  SI ProcessName
-------  ------    -----      -----     ------     --  -- -----------
    891     492  1893460    1841412     319.33   5036   6 TheForestDedicatedServer
    788     479  1622436    1584076     133.61   6512   6 TheForestDedicatedServer

Mike posted this 12 February 2019

Something went wrong there because -batchmode has always been in the flags. I've changed it to make doubly sure the extra flags are set though and that empty values are ignored. You can check this build out as the latest nightly.

Flussburrito posted this 12 February 2019

Cant start nightly:

Invalid Program Common Language Runtime detected an invalid program.

Thrown by the 'Core' plugin while performing the 'Login' method.

at GSMyAdmin.WebServer.WebMethods.() at GSMyAdmin.WebServer.WebMethods.Login(IHttpRequest request, WebSession session, String username, String password, String token, Boolean rememberMe) at GSMyAdmin.WebServer.WebAttributes.InvokeMethod(String MethodName, JObject Data, IHttpRequest request, IWebSession Session, WebMethodsBase MethodsClass, String RawRequest) at GSMyAdmin.WebServer.APIService.InvokeAPI(IHttpRequest request, IWebSession Session, JObject Data, String RequestModule, String RequestMethod, String RawRequest)

Mike posted this 12 February 2019

Ah you just caught nightly after a big change that's in the middle of being tested (the one that nothing but the change for this was the previous nightly). Revert back for now.

Flussburrito posted this 16 February 2019

Any working nightly to test ?

harry7877 posted this 16 February 2019

I am also experiencing this exact problem. I tried nightly and also had the same problem.

This is a new server that hasn't been setup before, so I can't revert back to a functioning version since it has never been setup before.

Is there a specific version that's working currently?