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






Hope to see more of you in the future!
@Zyranix You need to find a button which spawns a Time Pon. I've added a couple of clues in the latest patch
When I get to the finish area, it says I need 9 Rift Pons to access the bonus area but I only have 4 after collecting all of the Rift Pons I could find.
I remember doing the bonus stage back when workshop stuff was kinda new, but I tried this level again today and couldn't progress.
*Now supports a Chapter screen! However, if bugs occur, this change will be reverted
*Snatcher now informs the player when they have collected all mail letters
*About seven minutes after talking to Snatcher, he'll remind you to collect mail
*Time Pons and Mail Letters now have different SFX when collecting them
Just had a freeze for a moment after the first well open, surprised when there was a part after the 2nd well, hard time with the final rush hehe!
It's on my to do list, plus another bug fix involving overlapping text in one of the missions. Maybe some design tweaks, too; who knows. I'll push out a patch very soon if I have time :)
The Switch Panels, when their Time Pon is collected, the Block Cannon Time Pon completely fails to spawn from the button when the player dies. (Sorry for so many notifications, sirs and madams, I really felt like I could help this map be fixed!)
Perhaps getting the first time piece, then trying to go for that pon breaks the mission. (I'll test it myself, and post results)
Never knew about the TimeStop mission's Rift Pon not appearing at all, however. People did report the pon not appearing but never explained what caused it. I'll try debugging that one when I have time :)