安装 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.