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








However, I believe it is a resource restriction on the hosted server (probably out of mem). I was querying about the crashes to the support but unfortuantely no logs.
The problem is that Chivalry is not optimised to support horde or and game mode with massive amount of characters.
Of couse anybody can help. If you are able to provide instructions on how to reliably reproduce the crash it is as good as fixed. I.e. start by testing the skelly wave locally. You can spawn it manually by typing into console: causeevent darkness (... I think?, u get a list by just typing causeevent). You can set the wave increment in the config (how much the wavecount is increased when the wave is over) to quickly test on high waves.
Can You please tell me how can I test it locally? I don't see any option to play "sandcastle" map offline, nor Horde mode while trying to create offline game via ingame options, I wish to test it on my own
With NORMAL mode, we were able to achieve 52 wave. Then server crashed. This is something better than crashing around level 35-40. Server crashed when 144 enemies were left on 52 level (we completed some objectives already, current one was to push the wagon). And none of players used catasling, so I dont think crashes are related to catasling.
Diff: Hard
Wave 33
168 enemies left
7 players on the server
New player just connected, he received 2300 but no info about it in chat.
None of active players has above 1k frags (i thought that is the reason)
But dev 2 was last restarted 19th. Will contact the hoster.
However, if restarting would be a solution, it suggests a memory leak which may built up after a couple of hours anyway.