Questie

Questie

116M Downloads

some objective text contain slain text missing in Chinese Client!

kuletco opened this issue · 26 comments

commented

Bug description

some objective text contain slain text missing in Chinese Client

Screenshots

图片

Questie version

QuestieDev-master: 37acad5

commented
commented

I am busy with work recently.
I read your code of QuestieQuest.lua and I try to fix it.
图片

Now it works fine in the Chinese client.
@BreakBB Test other language clients if you can.

Here's my thinking:

  1. We should match text that contains colon first, otherwise, the match will return a '', not a nil in Chinese client, I can't test other language clients for the same problem.
  2. I add two match rules for Chinese client, but I can't test if it has a bad effect on other language clients.

Here are my changes:
图片

commented
commented

20191023111306
With 5.0.0_7-fb7c60e, monster objects are not correct.

commented

What is your exact locale? zhCN?

Can you do a "/dump QUEST_MONSTERS_KILLED" and send me the text and a screenshot for it?

Also "isn't working" doesn't it update correctly? Or is it only displaying the information in an incorrect way?

commented

Can you replace the contents of QuestieQuest.lua with this https://hastebin.com/ajovejuriv.rb and see if it solves the issue!

commented

QQ截图20191024055813
Questie-v5.0.1_2-e2e80b7

commented

https://classic.wowhead.com/quest=2681
https://classic.wowhead.com/quest=5282
These two quests have wrong object text. The other types are correct now.
2019-10-24 091136
Questie-v5.0.1_2-e2e80b7

Good news is no errors msg on some quests. 😄

some debug msg

Questie: [SPAM] [QuestieQuest:PopulateObjective]
Questie: [SPAM] -->Found: 戈洛尔的仆从
Questie: [SPAM] -->ID: nil
Questie: [SPAM] -->Description: 解放拉瑟莱克的仆从:0/9
Questie: [SPAM] -->Found: 瑟温妮的仆从
Questie: [SPAM] [QuestieQuest]: PopulateMeta: nil 禁锢我们的石头
Questie: [SPAM] -->Description: 解放奥利斯塔的仆从:0/3
Questie: [SPAM] -->Found: nil
Questie: [SPAM] -->ID: 7669
Questie: [SPAM] ----> Objective 解放奥利斯塔的仆从:0/3 Dist: 12
Questie: [SPAM] -->Found: 拉瑟莱克的仆从
Questie: [SPAM] -->ID: 7668
Questie: [SPAM] -->ID: 7671
Questie: [SPAM] [QuestieQuest]: Error finding entry ID for objective event 在壁炉谷中寻找一处高地,在那里观察小镇。
Questie: [SPAM] -->Description: 解放戈洛尔的仆从:0/3
Questie: [SPAM] ----> Objective 解放拉瑟莱克的仆从:0/9 Dist: 12
Questie: [SPAM] -->Found: 奥利斯塔的仆从
Questie: [SPAM] [QuestieQuest:PopulateObjective]
Questie: [SPAM] ----> Objective 解放瑟温妮的仆从:0/3 Dist: 12
Questie: [SPAM] ----> Objective 在壁炉谷中寻找一处高地,在那里观察小镇。 Dist: 0
Questie: [SPAM] -->ID: 7668
Questie: [SPAM] -->Description: 解放瑟温妮的仆从:0/3

commented

bug position.
2019-10-24 0931
L_QUEST_MONSTERS_KILLED find nothing in objective.text "解放戈洛尔的仆从:0/3"
print "nil" in game

@Logonz

commented

Wonderful! Looks like I need to upgrade to the latest version.

commented

ah yes @tytannial that logic is incorrect!
I also need to add or not monsterName.

Thanks!

commented

ah yes @tytannial that logic is incorrect!
I also need to add or not monsterName.

Thanks!

It works! 🎉
@kuletco 试试最新的提交,似乎解决问题了!

commented

@tytannial Its working as expected? :)
Ill close the issue in a day or two unless you say otherwise!

commented

ah yes @tytannial that logic is incorrect!
I also need to add or not monsterName.
Thanks!

It works! 🎉
@kuletco 试试最新的提交,似乎解决问题了!

我修改完怎么还是没有解决?地下城任务应该是显示D,还是显示问号

这个单子只是针对任务目标出现的问题,标题的问题你再开一个issue就好了

commented

@tytannial Its working as expected? :)
Ill close the issue in a day or two unless you say otherwise!

Could you update the "QuestieLib:GetColoredQuestName" function?
20191026114207
In non CJK locale this can be easy to get "Dungeon" for "D", but in Chinese you can not get that easily. char = string.sub("地下城", 1, 1), char value is "?". Sub a double byte character
as two code is not cool.😂

commented

ah yes @tytannial that logic is incorrect!
I also need to add or not monsterName.
Thanks!

It works! 🎉
@kuletco 试试最新的提交,似乎解决问题了!

我修改完怎么还是没有解决?地下城任务应该是显示D,还是显示问号

commented

QQ截图20191026053805
Dungeon task shows error, see the red box

commented

ah yes @tytannial that logic is incorrect!
I also need to add or not monsterName.
Thanks!

It works! 🎉
@kuletco 试试最新的提交,似乎解决问题了!

好的,谢谢提醒,不过最近我一直忙于工作,没怎么玩儿游戏。

commented

@tytannial What would be appropriate representation of [24D] and [60R] in CJK? Moreover currently we just use + for all quests that are not normal and add (Dungeon) behind them. Maybe we don't need the first part.

commented

@tytannial What would be appropriate representation of [24D] and [60R] in CJK? Moreover currently we just use + for all quests that are not normal and add (Dungeon) behind them. Maybe we don't need the first part.

[24D] and [60R] is enough, because it is not easy to match them in CJK, also we didn't translate this tag before in quest addons. It's a UTF-8 issue happened because each chinese word actually have 3 characters. The better way is force tag as D/R/E/G for CJK clinet.

commented

@tytannial What would be appropriate representation of [24D] and [60R] in CJK? Moreover currently we just use + for all quests that are not normal and add (Dungeon) behind them. Maybe we don't need the first part.

[24D] and [60R] is enough, because it is not easy to match them in CJK, also we didn't translate this tag before in quest addons. It's a UTF-8 issue happened because each chinese word actually have 3 characters. The better way is force tag as D/R/E/G for CJK clinet.

Agree. 👍

commented

@kuletco @EKE00372 @tytannial @suyunxiu Please try the following version and report if the issue is fixed:

Questie.zip

commented

@kuletco @EKE00372 @tytannial @suyunxiu Please try the following version and report if the issue is fixed:

Questie.zip

IT WORKS!

commented

@kuletco @EKE00372 @tytannial @suyunxiu Please try the following version and report if the issue is fixed:

Questie.zip

'Quest tracker dungeon and raid notation issues # 1529' This issue is fixed in the above file!

Should I use this version instead of downloading the latest version? (Are there any hotfixes for the Korean version?)

commented

@eshukina You should be fine with the file above for now. But we will shortly release a hotfix version containing this fix.

commented

Please use v5.2.1 where this issue is fixed.