Forum

You can change that, but it won’t make any difference whatsoever.

Right now, you wait ~30 seconds to time out.
Let’s say the server comes back in 40 seconds (10 seconds after you timed)
You can connect again after 10 seconds.

If you change that, all you’ll accomplish is not timing out after those 40 seconds have passed. It’s pretty much the same thing, but you won’t have to go through the VERY difficult task of pressing the up arrow in your console.

Quoted from Ghostface

You can change that, but it won’t make any difference whatsoever.

Right now, you wait ~30 seconds to time out.
Let’s say the server comes back in 40 seconds (10 seconds after you timed)
You can connect again after 10 seconds.

If you change that, all you’ll accomplish is not timing out after those 40 seconds have passed. It’s pretty much the same thing, but you won’t have to go through the VERY difficult task of pressing the up arrow in your console.

In the fine words of Chris.

The door leave through it, now.

…no?

only if some guys actually timeout, but teams usually stop between points to let them back in

all games ive played in where everyone actually remained on the server, the game carried on straight away

Quoted from Admirable

Anything you don’t like in the updates can be blocked via the whitelist by server admins…

I don’t like the reduction in fps from every update.

fps_min 120

Quoted from Ripple

put hide_server 1 into your config and it won’t crash anymore. for us it stopped when we did this and for others aswell.
They are choosing servers randomly to attack and servers they can’t find won’t be attacked.
no need for the timeout cvar, just change this and everything will be fine

^ this.

It will remove your server from the masterserver’s list which will stop malicious package attacks but you have to connect via commandline as the server won’t response otherwise.

regarding the (d)dos: has no one of the big guys (I’m looking at you, Arie & Ronny) figured out what IPs the attacks originate from? :(