安装 Steam
登录
|
语言
繁體中文（繁体中文）
日本語（日语）
한국어（韩语）
ไทย（泰语）
български（保加利亚语）
Čeština（捷克语）
Dansk（丹麦语）
Deutsch（德语）
English（英语）
Español-España（西班牙语 - 西班牙）
Español - Latinoamérica（西班牙语 - 拉丁美洲）
Ελληνικά（希腊语）
Français（法语）
Italiano（意大利语）
Bahasa Indonesia（印度尼西亚语）
Magyar（匈牙利语）
Nederlands（荷兰语）
Norsk（挪威语）
Polski（波兰语）
Português（葡萄牙语 - 葡萄牙）
Português-Brasil（葡萄牙语 - 巴西）
Română（罗马尼亚语）
Русский（俄语）
Suomi（芬兰语）
Svenska（瑞典语）
Türkçe（土耳其语）
Tiếng Việt（越南语）
Українська（乌克兰语）
报告翻译问题
只有受邀才能进组 
Report Player > They are involved in theft, scamming, fraud or other malicious activity > Their account seems to have been compromised > Submit this account for review
...and write that the account is sending dodgy links and has been reported by the owner as stolen.
Hopefully she'll get it back but please for the love of god if you receive an unsolicited link from someone you're advised to ignore it and report the account.
You should also make sure to enable 2 Factor Authentication on your account if you can. It prevents exactly this scenario from happening.
If this happens again then feel free to send me a message on Steam as the cause is 99.99% likely a technical failure rather than us removing someone's VIP.
they will still your steam account lol
Chu was sending out such spam so he might got hacked
watch out folks
good morning :)
Enjoy the consequences.
The Level 7 protection can break the server listing, which we experienced a few days ago when I did further tests. Something in the ISP filters blocks the listing in the server browser. I'm still working on a solution for that at the moment.
Rampage does have normal DDoS protection from the ISP. However as we've seen it's far from perfect. But we'd have that problem no matter which ISP we use. So no easy solution here.
When we used this previously several years ago it did cause issues with server listing and picking up players hence why we stopped using it at that time. However having monitored the server over the past few hours it has picked up several players on it's own so I think the previous legacy issues may be resolved going forwards.
We can disable the L7 protection if the listing bug is still an issue with this configuration. For the moment all we can do is wait and see and monitor the server over the coming days and perhaps hope of improvements to the current DDoS situation.
You can read more about our ISPs Anti DDoS systems here: https://www.ovhcloud.com/en-gb/security/anti-ddos/
if you're interested.
Now when the attack begins it takes a while for the system to properly detect and mitigate the attack. However the server seems to be crashing before that point is reached. We will have that problem no matter which ISP we use going forwards.
Moving forwards we could look at getting the ISPs OSI Level 7 protection and see if that helps. But I recall this caused problems with listing previously which is why we stopped using it. Plus that is an expensive upgrade we don't really have the budget for at the moment, especially if it doesn't work.
At the moment there is no easy solution to this problem.
Since the update that broke HLSW and other RCON remote management tools there was no need to keep the ports open as the software was useless so we closed the TCP port on the firewall.
It used to ban you if you navigated to the server IP and port 27015 in a web browser. However for the reasons above that should no longer be the case.
ZI: zi.zombieislands.com
RMPG: rampage.zombieislands.com
Rampage: 51.81.70.20
Hopefully this is a step in the right direction to resolving the instability issues with that server.