安装 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 sorry for not specifying, but that's exactly how the other mod i mentioned worked, the F2 key was only used to disable the mod, and to enable it you had to go in the options (like yours)
I will have a look into it, I didn't actually know that you could detect input events inside a mod, although it does make sense. I might have a look into it and update the mod with something like that. Although it would probably be a 'disable only' hotkey, and you would still need to enable it manually in the mods tab. Thank you for the suggestion!
If you find line 142 in the file, it should be something along the lines of:
'if (Game.ascendMeterLevel > 0 && timeSinceAscent >= 8000) {'
And then modify the value that is checked against for the 'timeSinceAscent' to something like 40000, that would give you 40 seconds instead of 8 between ascensions.