Adaptive Server Size (1.3.5.3 - 06/14/15)

[ImportBot]

Originally Posted by EBassie*:

 

Aha! I have new information.

 

I have now seen a problem similar to those reported above (details below), but I can confirm that it is not caused by Adaptive Server Size. The problem happened even when I had the plugin disabled and typed in vars.maxPlayers values manually. It may be a game server bug related to CTF.

 

I have CTF set up for 40 max, 6 min, with +4 increments, so when there are 6 players on the server the max is supposed to be increased to 10.

 

However, this morning I saw that serverInfo was reporting 6 players and 6 max. I disabled the plugin and tried manually entering vars.maxPlayers values greater than 6, no change. I restarted the round, no change. The value for vars.maxPlayers was being returned correctly, whatever I last set it to, e.g. 10, but serverInfo continued to report 6 players, 6 max. I wasn't able to clear it without rebooting the game server and dumping out those poor 6 players.

 

I haven't scanned the logs to see what sequence of events lead to 6/6, but I'm pretty sure it's not Adaptive Server Size's fault.

Months ago DICE has fixed this bug where the server got stuck an a certain amount of slots.

But if it's the case again, the 'old' maxPlayers-bug may have returned.

 

There might also have been a connectivity issue between your servers and Battlelog, causing the server to NOT change the slots.

 

I haven't had any issues with it though. My 3 servers are running CTF to start the server.

Every start of a round the server gets set back to maximum slots before scaling down again.

[ImportBot]

Originally Posted by HexaCanon*:

 

Another data point. Works on my 64 slot server set to 64 or 48 or 40, and I made those changes while the rounds were running! I waited until the actual player count was below the number I wanted, of course. Worked flawlessly with player counts ranging from 4 to max.

 

Personally, I found 64 player CTF to be a super camp fest and not very fun. 40 seems about right. Still a lot of camping to the point where I now call the mode "Camp The Flag", but at least once and a while someone can score a point. With 64 we went round after round at 0 vs 0.

[ImportBot]

Originally Posted by xFaNtASyGiRLx*:

 

lol! ^^^

 

my 3 64 flag servers are always full. I was just going to have two but made my aftermath temporary ctf

[ImportBot]

Originally Posted by falcontx*:

 

Umm.. thanks for the off-topic posts?

 

Anyways, back to EBastard and PapaCharlie9, I had a feeling it might be something like that, as the code for the plugin has been working fine for months, now, and there should be no differentiation between game modes.

[ImportBot]

Originally Posted by DHGreenday*:

 

I am currently have a problem with this plugin on my CTF server which we recently changed from AM to give it a go. Its set to 32 max players until it nearly reaches it then it becomes 40 slot. However it just gets stuck on 32 until I disable it.

[ImportBot]

Originally Posted by _lecro_*:

 

I am currently have a problem with this plugin on my CTF server which we recently changed from AM to give it a go. Its set to 32 max players until it nearly reaches it then it becomes 40 slot. However it just gets stuck on 32 until I disable it.

Yea same here ,

Our 40 is only running and also gets stuck at 32 :S

[ImportBot]

Originally Posted by kcuestag*:

 

I am currently have a problem with this plugin on my CTF server which we recently changed from AM to give it a go. Its set to 32 max players until it nearly reaches it then it becomes 40 slot. However it just gets stuck on 32 until I disable it.

Yea same here ,

Our 40 is only running and also gets stuck at 32 :S

Stupid question, but have you guys made sure you didn't cap CTF to 32 players? Check the plugin settings on the bottom!

 

This is how I have mine set:

 

 

Attached Files:

• tD2WFWo.png

[ImportBot]

Originally Posted by TimSad*:

 

lol! ^^^

 

my 3 64 flag servers are always full. I was just going to have two but made my aftermath temporary ctf

Mine would always be full too but all these damn Blaze issues + DoS attacking a-holes are killing us! :|

[ImportBot]

Originally Posted by kunoichia*:

 

Well our plugin seems to lock itself to 16 /24 /32 players also more frequently all since endgame patch.

 

Happens on our vanilla CQ / endgame CQ and CTF and all maps tdm server. So surely something has been changed on DICE side.

[ImportBot]

Originally Posted by GR101*:

 

I am currently have a problem with this plugin on my CTF server which we recently changed from AM to give it a go. Its set to 32 max players until it nearly reaches it then it becomes 40 slot. However it just gets stuck on 32 until I disable it.

I'm getting the same problem where it reaches 32 players and becomes stuck until I disable it.

 

Code:

procon.protected.plugins.setVariable "CAdaptiveServerSize" "Maximum server size" "48"
procon.protected.plugins.setVariable "CAdaptiveServerSize" "Maximum Conquest Large size" "48"
procon.protected.plugins.setVariable "CAdaptiveServerSize" "Maximum Assault64 size" "48"
procon.protected.plugins.setVariable "CAdaptiveServerSize" "Maximum Conquest Small size" "48"
procon.protected.plugins.setVariable "CAdaptiveServerSize" "Maximum Assault size" "48"
procon.protected.plugins.setVariable "CAdaptiveServerSize" "Maximum Assault #2 size" "48"
procon.protected.plugins.setVariable "CAdaptiveServerSize" "Maximum Rush size" "48"
procon.protected.plugins.setVariable "CAdaptiveServerSize" "Maximum Squad Rush size" "48"
procon.protected.plugins.setVariable "CAdaptiveServerSize" "Maximum Squad Deathmatch size" "48"
procon.protected.plugins.setVariable "CAdaptiveServerSize" "Maximum TDM size" "48"
procon.protected.plugins.setVariable "CAdaptiveServerSize" "Maximum TDM Close Quarters size" "48"
procon.protected.plugins.setVariable "CAdaptiveServerSize" "Maximum Gun Master size" "48"
procon.protected.plugins.setVariable "CAdaptiveServerSize" "Maximum Conquest Domination size" "48"
procon.protected.plugins.setVariable "CAdaptiveServerSize" "Maximum Tank Superiority size" "48"
procon.protected.plugins.setVariable "CAdaptiveServerSize" "Maximum Scavenger size" "48"
procon.protected.plugins.setVariable "CAdaptiveServerSize" "Maximum CTF size" "48"
procon.protected.plugins.setVariable "CAdaptiveServerSize" "Maximum Air Superiority size" "48"

[ImportBot]

Originally Posted by EBassie*:

 

Well our plugin seems to lock itself to 16 /24 /32 players also more frequently all since endgame patch.

 

Happens on our vanilla CQ / endgame CQ and CTF and all maps tdm server. So surely something has been changed on DICE side.

All my servers are running End Game at the moment: CQ, CTF and RUSH.

 

I never have an issue with this plugin NOT working. It never fails on the 64 slots server currently running CTF, our 64 CQ End Game or 32 CTF / RUSH server. It never fails. Never locks up the slots.

 

Really wondering why some of you have issues....?

[ImportBot]

Originally Posted by kcuestag*:

 

Is it possible to use some kind of white list for the idle kick of this plugin? I like having idle kicking off when players are below 40 on my server, so I can just idle on it and let it kick me at +40 players, but sometimes when I go to bed I want to idle on the server but it's full, so it kicks me.

 

Any way of adding a white list?

[ImportBot]

Originally Posted by falcontx*:

 

Is it possible to use some kind of white list for the idle kick of this plugin? I like having idle kicking off when players are below 40 on my server, so I can just idle on it and let it kick me at +40 players, but sometimes when I go to bed I want to idle on the server but it's full, so it kicks me.

 

Any way of adding a white list?

This has been answered many times before. The plugin just turns on/off the server-side idle kick and the server doesn't offer a white list.

[ImportBot]

Originally Posted by kcuestag*:

 

Damn!

 

Thanks though!

[ImportBot]

Originally Posted by kcuestag*:

 

Isn't there a way you can actually do this to the plugin in the near future?

[ImportBot]

Originally Posted by MrJakl*:

 

Hi there,

 

is EA/Dice informed that the old bug with stuckings server sizes exists?

 

Here is a link to my post on battlelog forum: http://battlelog.battlefield.com/bf3...4625503342826/

 

Please confirm that bug, so we get help quickly.

[ImportBot]

Originally Posted by EBassie*:

 

Hi there,

 

is EA/Dice informed that the old bug with stuckings server sizes exists?

 

Here is a link to my post on battlelog forum: http://battlelog.battlefield.com/bf3...4625503342826/

 

Please confirm that bug, so we get help quickly.

I've been helping DICE to fix this bug back in May - August 2012 and it is considered fixed.

 

Since the bug was fixed back in August 2012 with server R28 I never have encountered this issue ever again. And I'm using Adaptive Server Size every day since.

 

You have any more details about when it happens?

Do you use VIP slots with aggressive join? What's the server setup?

 

If this bug has returned, I would like to see if I can duplicate your issue.

 

But I guess this is just a hickup, happening when the server may not have contact with Blaze and the changing of the slots does not get registered by the Blaze backend.

[ImportBot]

Originally Posted by GR101*:

 

I'm getting the same problem where it reaches 32 players and becomes stuck until I disable it.

I've fixed my server problem by deleting the server config file and started again, works a treat now.

[ImportBot]

Originally Posted by MrJakl*:

 

I've fixed my server problem by deleting the server config file and started again, works a treat now.

Which Server config file did you mean? Whats the name of that file?

[ImportBot]

Originally Posted by DHGreenday*:

 

Hi guys, I've been getting this bug today too, I'm glad I googled and found a link for a fix here just by moving the server on instead of restart as I have restarted the server once already. Got stuck on 8 the first time this last time it got stuck on 12. I have stopped the procon layer hosted by an rcon hosting firm to try and avoid it happening again. However they have been doing maintenance the last couple of days and it may be the cause of it.

 

Edit: It got stuck again even without the procon layer and adaptive server size on

[ImportBot]

Originally Posted by PapaCharlie9*:

 

@falcontx

 

Don't forget to post your plugins for review!

[ImportBot]

Originally Posted by Apex40000*:

 

Same problem here BUT its started to happen only over the last week or so -- roughly the same sort of time I started to get blazes again-- So I wonder if its just that as I've not had a problem in ages with the great plugin --- But on the plus side I think this has answered another question - he heh as I started to use another plugin to do something else-- So I thought it might have been that plugin causing the problem but now it just looks like a blaze crash problem.

 

 

apex40000

 

Hi guys, I've been getting this bug today too, I'm glad I googled and found a link for a fix here just by moving the server on instead of restart as I have restarted the server once already. Got stuck on 8 the first time this last time it got stuck on 12. I have stopped the procon layer hosted by an rcon hosting firm to try and avoid it happening again. However they have been doing maintenance the last couple of days and it may be the cause of it.

 

Edit: It got stuck again even without the procon layer and adaptive server size on

[ImportBot]

Originally Posted by staazvaind*:

 

same here.

 

sometimes its stuck on 8 or 12 players which is pain on a 50 server :-/

[ImportBot]

Originally Posted by OscarMike*:

 

I can confirm that this bug still exists under extreme situations. It only happens on our servers in the aftermath of a blaze disconnect. Once the server is back and accessible in Battlelog server browser, sometimes the slots get locked at the last known server slot size prior to the blaze. Sometimes it may be 8, 16, 46 slots or whatever other random number of players were playing on the server at the time shortly before the blaze incident. This doesn't happen often due to our servers being full most of the time. It has become a problem due to the frequent blazes during the last weeks. Maybe the plugin doesn't realize that the round started with 64 players although the settings are correct in the plugin itself. Also, sometimes the slots don't get locked in the server browser but upon joining the server only a random number of players can load into the round i.e. 8 players and the 9th, 10th, etc. joining players get stuck in a blackscreen and can't load into the round. That can only be fixed by pressing end current round.

[ImportBot]

Originally Posted by xFaNtASyGiRLx*:

 

me too! Only my aftermath server- this happens almost whenever the server restarts. It gets stuck on 16 or 18 or 36. Its really random on what number it gets stuck at and the only way to fix this is to rotate to the next round. This only appears to be happening mostly on Aftermath- all others do not get stuck as much.

[ImportBot]

Originally Posted by Deputydog857*:

 

Hi all. Have been away for awhile but just started our server again, The Cougar Club. I noticed that there have been some changes in regards to min number of players allowed. How is the server popping working now and could someone show me an example of thier setup (.ie 44448888) for the Adaptive Server Size? Thanks a bunch and glad to be back in the community.

[ImportBot]

Originally Posted by woowoo*:

 

Anyone found an answer to the plug in hanging at a certain slot count?

[ImportBot]

Originally Posted by kunoichia*:

 

Nope seems to start happening quite a lot again lately (at 16 players for us).

 

Happens on Metro server, vanilla, rush all dlc and TDM all dlc.

Quite annoying.

[ImportBot]

Originally Posted by Jaythegreat1*:

 

Just curious if there was a way to turn off idle kick during certain hours of the day.. in-case anybody wanted to sit idle during the night.

[ImportBot]

Originally Posted by b0wzy*:

 

Yeah... I experienced the player count bug last night. It was Rush at 40 players, and should of switched to 48 by the time it got to 36 people. Even had people lining up to connect.

 

I tried manually changing the number on my hosts website control panel, even that didn't work. Didn't try the "change to next round" as some had suggested - I'll do that next time.