Results 11 to 20 of 26
Thread: Go to CODE BEIGE. (Server potentially in danger!)
-
03-13-09, 09:20 AM #11
Re: Go to CODE BEIGE. (Server potentially in danger!)
I really hope this will only change the server's score once per player, rather than once per connection. Otherwise, players with grudges and too much time on their hands could connect to a server over and over again, thus artificially tanking that server's score. Well-run server's have enough shit to deal with from losers as it is, without giving them a weapon with which to actually bring down the server.
Edit: even without that, it might be possible to make a DDoS attack against a server given enough people coordinating (say, a pissed off clan, or something), without much that I can see that the server owners can do to stop it. Has Valve really thought out all the implications of this move?
-
03-13-09, 03:59 PM #12
Re: Go to CODE BEIGE. (Server potentially in danger!)
Originally Posted by CheeseLikeSubstance
Originally Posted by ...bigdog...
It's important to note points are lost the instant you join the server, not when people quit. Quitting only prevents the addition of more points.
Rank is gonna matter if Valve stars delisting servers with really crappy rankings. Last thing we want to is have our mod get us delisted; as much as I'd like to believe we can keep the server going based on people who added us to favorites, we won't gain new folks unless we can retain at least a passing grade. I hope Valve will give us a way to track our own ranking.
-
03-13-09, 11:24 PM #13
Re: Go to CODE BEIGE. (Server potentially in danger!)
Well, "successful connection" sounds like someone that connected and got in-game to me. As long as they stay at least 15 minutes, then we're all good, because it results in a score of 0 - nothing gained, nothing lost. Even at peak times, I don't think people are getting shoved off to make room for reservists faster than every twenty or thirty minutes.
That said, the concept seems a little weak. But I guess life's tough for people who haven't found TTP.
-
03-13-09, 11:58 PM #14
Re: Go to CODE BEIGE. (Server potentially in danger!)
Worst case scenario, the server is full of non-reservists, then reservists start joining. Most score you can loose from that will be 330. Unless those reservists leave with an average of less than 15 minutes played the points will be regained.
So, do reservists on average play for less than 15 minutes?
-
03-14-09, 12:00 AM #15
Re: Go to CODE BEIGE. (Server potentially in danger!)
Originally Posted by FireCrack
-
03-14-09, 12:03 AM #16
Re: Go to CODE BEIGE. (Server potentially in danger!)
Originally Posted by CheeseLikeSubstance
It may seem conceptualy different, but kicking joe-blow who just joined or johnny-peabody who has been playing for a full hour ends up the same mathematically.
Absolutely worst case scenario in which 22 non reservists joined and then 22 reservists join immediatly means that the reservists need to play 30 minutes to balance it out.
Over time, players being kicked for reserved slots is no different from players waiting for slots to open...
-
03-14-09, 12:07 AM #17
Re: Go to CODE BEIGE. (Server potentially in danger!)
Originally Posted by masterPAINb
-
03-14-09, 04:18 AM #18
Re: Go to CODE BEIGE. (Server potentially in danger!)
Nono worst case scenario thers a bug that causes the server to crash then it refills then crashes agian.
-
03-14-09, 10:51 AM #19
Re: Go to CODE BEIGE. (Server potentially in danger!)
I don't think it's any of the above. The real problem is that if we have a full server, anyone that even tries to join our server may grant us a "15 DKP Minus." Every time someone attempts to join our full server, we get -15 unless we can block the connection before Valve scores it as successful. The problem isn't people being kicked: the problem is people potentially trying to connect and failing. I don't know where in the connection code the Non-Reservist block occurs, but we need to make sure it happens at the same time it would happen if the server was "full."
-
03-14-09, 03:27 PM #20
Re: Go to CODE BEIGE. (Server potentially in danger!)
Originally Posted by ZenSaohu
I should have made myself more clear.
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks