安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
Yeah, you have to go to the checkpoints that the level has set, and if you break sequence then the checkpoints system isn't currently capable of accounting for that.
I might be able to do some things to possibly fix that in the flying mod, but that would probably cause incompatibilities with some maps that the flying mod could otherwise work on. I also am not 100% sure I could make such a fix "logically perfect".
The work-around on the user side is to stop breaking sequence. Just fly to the various checkpoint (even the silent ones) and make sure they're triggered before trying to proceed. Of course, this advice is hard to know how to do unless you more or less just use the flying mod as a way to "run really fast" and just fly close to the ground in a way where you don't go to places you couldn't otherwise walk or jump to.
You could also try filing a bug with Wolfire, but I can tell you that they're not working on the game at this time, and this bug would probably be considered fairly low priority. "if mod breaks game, stop using mod" would probably be their stance, unless you had a way to break sequence without mods that normal users might be likely to accidentally stumble into.