安裝 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（越南文）
Українська（烏克蘭文）
回報翻譯問題
5 
檢舉此篇文章
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.