Server crashing on gamestart

[Ironman44]

just did it and found this in the startup text im having issues with vars.teamKillValueForKick 0

Ill change it and update

[ebar87]

Ah I see that. I can't test right now, having trouble populating the server to test, but it looks like maybe the control panel isn't removing the teamKillValue options when you just want to use overall how many times someone tk's. Since it's set at zero, I would guess that either means its not set (i.e. infinite, which isn't a problem) or its set to instantly kick everyone, which is a problem.

If that is the case, it does not really explain why the server would get caught in some sort of map changing limbo and need to be reset.

[Ironman44]

THIS IS WHAT I FOUND

vars.maxPlayers 32
vars.idleTimeout 300
vars.idleBanRounds 0
vars.vehicleSpawnAllowed true
vars.3dSpotting true
vars.miniMap true
vars.miniMapSpotting true
vars.killCam true
vars.autoBalance true
vars.3pCam true
vars.regenerateHealth true
vars.onlySquadLeaderSpawn true
vars.nameTag true
vars.hud true
vars.teamKillCountForKick 6
vars.teamKillValueForKick 4100 THIS VALUE WAS ZERO
vars.teamKillValueIncrease 1000
vars.teamKillValueDecreasePerSecond 50
vars.gamePassword ""
vars.friendlyFire false

Somehow the team kick value of zero was kicking everyone on startup even though even though FF is set to false
I changed that value via manually editing the startup script
The value would not show up in control panel with FF off

[ebar87]

Thats what I suspected, looks like the control panel isnt properly editing the file. Is the server working correctly now?

[Ironman44]

yup

[Edge100x]

I'm testing the Easy setup page now and it seems to be retaining the value of vars.teamKillValueForKick correctly when FF is disabled. Do you know what change might have triggered it to go to 0?

[Edge100x]

The control panel does set vars.teamKillValueForKick to 0 when "Use the kill-value system to punish TKs?" is disabled, and per the documentation, that should disable the kill value mechanism:

Request: vars.teamKillValueForKick [count: integer]
Response: OK - for set operation
Response: OK <count: integer> - for get operation
Response: InvalidArguments
Effect: Set the highest kill-value allowed before a player is kicked for teamkilling
Set to 0 to disable kill value mechanism
Delay: Instantaneous

If a value of 0 nukes the server, that's a bug in the game, and I'll have to disable it in the CP.

[Ironman44]

The zero value was the problem. I am able to set the servers up as i wish now.

YAY now i can actually play

[ebar87]

When my friends are done with work, I'll test it on my server as well to double check for you guys.

Definitely looks like a bug with the game.

[Edge100x]

I've confirmed that this one is a game bug. The game log shows that it thinks the players all need to be kicked, so it kicks them, and then it crashes, to boot. I've submitted a report to DICE and I'll change the control panel to force teamKillValueForKick to not be zero for now.

In my testing, I also saw the server crash when I used admin.runNextLevel (and admin.kickPlayer), with the same crashing error as teamKillValueForKick. The same bug may triggering all of these problems.

[Ironman44]

Right on, and thanks for the help guys

[Ironman44]

one more quick question, is it safe to use Procon at this time

[Edge100x]

The latest Procon should work OK. It's pretty rough around the edges, though, I believe.

[ebar87]

Awesome, thanks for the help Edge

[.=QUACK=.Major.Pain]

Basics of Procon are working as well as layer.