Thread: Question about kicks vs res slots

Originally Posted by draco7891

Originally Posted by ...bigdog...

and I don't think that thread is up to date. Perhaps that was early in the process...but it was "fixed" to what the TG and other communities were pressing.

TG ran a custom script that worked the way you described it. They had 0 reserved slots, and the script would kick non-reservist players from the server, at random, in order to keep those last 2 slots open all the time. Anyone could join into those last 2 slots (being technically "open"), but if they weren't reservist they would get kicked fairly fast (albeit with no message whatsoever, just a "you have been kicked from the server" default error message).

We don't, we just use the normal default BF2 RS system, built into the server.

Draco

that thread is out of date. The system changed, and was updated. Perhaps in the beggining, it didn't work properly, but brandon modified the code to be more normal of a system.

Originally Posted by bust331

So this is my understanding of how the reserve system works...but I could be completely wrong for that matter.

The server is at 60/64 and a reservist clicks "join game." At the moment CC confirms this player as a reservist it finds a non-reservist to kick...which during this whole process the highest the player count will go is 61/64, and that's only while the reservist is connected, so once the non-reservist gets kicked it drops the player count back down to 60/64...am I right?


Also, if the server is at 60/64, those last four slots are like doors...only open to reservists while it's kicking a non reservist.

that is correct.

:P

Originally Posted by draco7891

Because dude, we run one of the most popular BF2 servers on the planet. Because non-reservists sit at the server browser spamming the refresh button, waiting for the server to dip down to 59/64 (trust me, long ago I was one of them). We are popular. We are successful. Whenever we kick people, the server almost immediately fills back up with players (usually, non-reservists). I've watched it happen for years now.

If anything, it serves to illustrate that we should push reserved slots harder, y'know?

Draco

you're not understanding my point. what you just said above PROVES MY SIDE of the argument.

We are more than popular enough for there to be moments in our player graphs that would show 63 or 64 players stably connected. In the last 24 hours...not even once? Not even for a few minutes? Not ever?

If we can hold steady at 60/64 (which the graphs show), then we could hold steady at 64/64. We don't, because the server is ACTIVELY kicking people off.

the reserve slot system kicks non-reservists. And in BF2, that means 60 reservists can be connected at once.

It says TTP, so it has to be ours, right?

Originally Posted by draco7891

What other servers? Show me such a server. In fact, show me a server that's configured like TTP (with 4 reserved slots and no funny extra MM scripts like TG did) with a higher playercount. At all. Ever.

EXACTLY. Not just our server, but NO SERVER OUT THERE WITH 4 RESERVED SLOTS WILL EVER HAVE MORE THAN 60 PEOPLE PLAYING.

Meaning, the server HAS TO BE KICKING PEOPLE TO MAKE THIS HAPPEN. There can be no other reasonable explanation (and no, saying "oh, people must have crashed" on multiple servers, nationwide, for hours on end is not an excuse).

No server with 4 res slots has a player graph that can hold steady at anything other than 60 players. Not UNLESS they are doing some goofy custom script, and there's far less of those since EA make their EULA ranked rules stiffer/more enforced. In the beginning, and even now, some places get away with being able to access locked folders on their boxes. TG being one example. But that's not how it's supposed to be.

Can't TG do this mainly because they are running PR, which is not a ranked mod/server?

Originally Posted by CivilWars

Can't TG do this mainly because they are running PR, which is not a ranked mod/server?

they run/ran that script on their BF2 ranked and 2142 ranked. We know this certainly for 2142, since the script was an issue when we had a 64 man match (kept kicking TTP guys for reserved slots using PB kicks).

big no no.

Someone fire up the match server and set it for 4 slots, 2 reserved, and I will volunteer to test this RIGHT NOW, so we can put this to bed once and for all.

Ah, forgot about the 2142.