Agent Smith is kinda right here. We already employ dedicated hosts with anti-ddos solutions. If there was a practical way to get more protection, we would investigate it, but so far there's really no good avenues to take from here.Would need a firewall with rules to mitigate excessive amounts of traffic, or employ a dedicated server host, as those often have built-in protection (not sure if EGO does this already, but if so it may be worth considering a provider with better protection).
This makes sense, but I do have another idea as well. If possible, it might also be worth enforcing a minimum account age to connect to the server (3 days would seem appropriate, as it's not an excessive amount of time that I could foresee having a negative impact on playerbase).Agent Smith is kinda right here. We already employ dedicated hosts with anti-ddos solutions. If there was a practical way to get more protection, we would investigate it, but so far there's really no good avenues to take from here.
Imma agree with Darkfry here on the account age thing if that’s possible…seeing as our servers (in GO at least) probably aren’t the type of thing players who are new to steam or gaming would start with. I would say tho that our TF2 servers are a great place to start learning TF2 and ik there are people who join with new accounts so I’d ensure those changes aren’t applied to TF2 if they are to CS:GOThis makes sense, but I do have another idea as well. If possible, it might also be worth enforcing a minimum account age to connect to the server (3 days would seem appropriate, as it's not an excessive amount of time that I could foresee having a negative impact on playerbase).
I say this because the times I've seen the server get "DDoSed", it was immediately after an account (a brand new one) joined, and as soon as the account was kicked/banned, it stopped. Seen it happen twice, and have a clip of one of those times if you wana see what I'm talking about. Server started lagging out (seemed like a DDoS) but these attacks regarding excessive network traffic may be linked to a specific account (that needs to be connected to the server) in a lot of cases. Might not stop the issue, but it could potentially make it more difficult and more inconvenient for the attacker(s).
At the expense of 10$ and around 30ms+ more latency for all users and some moderate configuration and some IP changes there isAgent Smith is kinda right here. We already employ dedicated hosts with anti-ddos solutions. If there was a practical way to get more protection, we would investigate it, but so far there's really no good avenues to take from here.
I for one don't want a 30ms increase in ping. I'll take infrequent ddos over an increase in average pingAt the expense of 10$ and around 30ms+ more latency for all users and some moderate configuration and some IP changes there is
DM soon to be sent xoxoxo