安装 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(越南语)
Українська(乌克兰语)
报告翻译问题


This is the actual TX address 68.232.162.8:27015
https://imgur.com/a/aSIyozs
and currently the residency inside the server is 0
https://psteamcommunity.yuanyoumao.com/profiles/76561199100962687/
and
https://psteamcommunity.yuanyoumao.com/profiles/76561198954371862/
If this is towards other players, if they are struggling on NR then it is much better for the team to guide them through the map and not exclude them. That was never the intention of this group, excluding players. Now if they joined late and you already have that slot occupied, communicate so before kicking them. Blocking is excessive, especially if you do it on a frequent basis cause that leads to player not knowing what they did wrong to warrant said block
lower nb_update_frequency to match the tickrate and use the extension from the link below to fix issues it will cause.
https://forums.alliedmods.net/showthread.php?t=344019