Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ss3server] default config not being applied #247

Closed
dgibbs64 opened this issue Dec 18, 2014 · 8 comments
Closed

[ss3server] default config not being applied #247

dgibbs64 opened this issue Dec 18, 2014 · 8 comments
Assignees
Labels
type: bug Something isn't working

Comments

@dgibbs64
Copy link
Member

Reference commend:#245 (comment)

Server works great now, but I had to make some changes.

I had to add the port to the server startup line.

# Start Variables

ip="192.111.155.210"
port="27015"

https://raw.githubusercontent.com/dgibbs64/linuxgameservers/master/SeriousSam3BFE/help/DedicatedServer_Readme.txt

fn_parms(){
parms="+ip ${ip} +port ${port} +logfile ${gamelog} +exec ${servercfgfullpath}"
}

Only with a different port since I already have something running under that port. Changing the port in the config file didn't appear to do anything. In fact the server doesn't seem to follow anything about the config file. Default config had 12 players, but the server loaded 16. Also my custom server name wasn't picked up. It defaulted to the servers host name.

I have not tried to rename the server config file to dedicatedserver.cfg to see if that fixes the issue. Just so happy to finally be able to host this game on my Linux box now.

@dgibbs64 dgibbs64 added type: bug Something isn't working priority labels Dec 18, 2014
@dgibbs64 dgibbs64 self-assigned this Dec 18, 2014
@lblanchardiii
Copy link

Okay. I have gained some progress on this. So far I have managed to get a cfg file to load. What I have done.

Change the file permissions to 777.
Used absolute file paths in the parms line.
Deleted "commented out" lines from the default CFG file as well as delete a couple lines that kept getting stuck. Will post those two lines in a second, but one of them was the port line. I think because I am calling the port on the startup it's having an issue. The other one was come to thank of it a net host line that I think is the IP of the server that is being called directly in the line anyway.

I do not know which of these actually worked or if it required all of them.

@lblanchardiii
Copy link

Finally got somewhere with this. This is my setup.

https://raw.githubusercontent.com/dgibbs64/linuxgameservers/master/SeriousSam3BFE/help/DedicatedServer_Readme.txt

fn_parms(){
parms="+gamemode ${gamemode} +ip ${ip} +port ${port} +logfile ${gamelog} +exec Content/SeriousSam3/Config/survival.cfg"
}

Then this is what the survival.cfg file looks like:
rcts_strWelcomeNote = "Server GUI RCON";
rcts_strAdminPassword = "";
prj_strLogFile = "";
gam_idGameMode = "TeamSurvival";
ser_iMaxClientBPS = 11000;
prj_iDedicatedFPS = 100;
gam_ctMaxPlayers = 8;
gam_ctMinPlayers= 1;
prj_strMultiplayerSessionName = "Skillz Death Kamp #2 | SkillzServers.com";

gam_bAllowJoinInProgress = 1;
gam_bAllowPowerupItems = 1;
gam_bAllowArmorItems = 1;
gam_bWeaponsStay = 1;
gam_bAmmoStays = 1;
gam_bArmorStays = 1;
gam_bHealthStays = 1;
gam_bAllowHealthItems = 1;
gam_bInfiniteAmmo = 0;

gam_bAutoCycleMaps=1;

prj_strDefaultMapDir = "Content/SeriousSam3/Levels/Z5_Other/";

local prj_strMapList = {
",#SV_Deserted.wld,#SV_Canyon.wld,#SV_MedinaDefender.wld,#SV_UnderPressure.wld,#SV_Villa.wld"
}

Obviously edited for passwords, but it's a survival server. Regular coop doesn't really need a map list unless they want to load the DLC and/or start with something other than the first map.

Additionally I have the survival.cfg file permissions set to 777.

Do note that the gam_ctMinPlayers in the CFG file isn't really needed, but by default survival requires a minimum of 2 players to start. I changed it using that config so I could test quicker rather than waiting for someone to join me each time I made a change.

@dgibbs64
Copy link
Member Author

dgibbs64 commented Jan 9, 2015

Im not sure how best to go about this as I dont run a serious sam 3 server myself. I could do with a default config for each game type and the best default parms to set.

I think the ideal parms are as follows as @lblanchardiii specified. But i'm not sure about the configs.
parms="+gamemode ${gamemode} +ip ${ip} +port ${port} +logfile ${gamelog} +exec Content/SeriousSam3/Config/survival.cfg"

If anyone is willing to post some vanilla default configs for each game mode that they know works I will implement them in to the script. Also is survival the main game mode used or is there another one?

@lblanchardiii you mention that you use absolute path for the config however your example is a relative path. Please can you confirm which is best. Also never use 777 permissions as this is writable to anyone and not best practice (bad things can happen). something like 774 or or 744 may be better. It may be that the server requires write access to the config?

@Scarsz
Copy link
Contributor

Scarsz commented Jan 9, 2015

Should honestly just CHOWN the server's folder if it needs write access imo.

@lblanchardiii
Copy link

Cooperative is the default gamemode and CooperativeCoinOp is similar to the default one but you don't have to worry about dying as much. Survival is a unique gamemode and not very common. Majority of the servers are Cooperative or one of the Versus modes.

With Cooperative and CooperativeCoinOp you don't really need any special parms unless you are running multiple servers on the same install/IP. Then you'll want to be able to change the ip or port. By default everything just works like it should.

For Survival you'll want to use the local prj_strMapList in the config file otherwise it will just play the same map over and over. By default it's the SV_Canyon map that will be set on repeat.

The permissions at 777 might not be required, but it was something I set them to for testing purposes. I never went back to check if it was required or not.

Absolute path is not required as I originally thought.

One thing for sure is though I don't have any "commented out" lines in my config files as that seemed to cause issues with the game engine loading it.

@dgibbs64
Copy link
Member Author

dgibbs64 commented Jan 9, 2015

Cheers @lblanchardiii I will run though your comment fully and come up with somthing.

@dgibbs64
Copy link
Member Author

I have adjusted the game type and added a link in for the SS3 Server GUI 3 tool.
4cb78a3

@lock
Copy link

lock bot commented Jul 19, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants