安裝 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(越南文)
Українська(烏克蘭文)
回報翻譯問題
They have absolutely no idea what they're doing, it's pathetic...
Another, probably better, solution might be to use the global timer like you do (because this way it will automatically apply to all modded quests too I presume), and then use a boolean to mark quests "exempt" from this? Insert a boolean into the scriptConfig field in a given quest template, get it in main.lua (like in init) with config.getParameter() while considering it as "non-exempt" by default, and make it so your timer is only used if the quest is "non-exempt". So instead of a global On/Off you have an optional Off switch for individual quest templates. Would this work?
what were the makers of this game thinking ?!
The way I think it works is that since the game isn't checking the conditions as often, it has difficulty counting monsters defeated, so they might not register every time. Not game-breaking or anything, just be careful ^^
The game actually do that??
Why people who has no clue to coding makes games?
Nice to see someone picked up on this issue and released a fix for it. Good job.