The wotlk version has now been restarted on the Chinese server. Can we enable the functions of wotlk for the convenience of Chinese users?

Those were not in that document that you linked me.

If you can give me the English name of those two items, I can match them up and adjust them.

Our version does not provide an option to change the English language settings; I believe only equipment levels have been modified, so the corresponding English names should remain unchanged.They are Belt of the Merciless Killer and Bracers of the Untold Massacre,I have updated my link with all the latest data(TOC 252装备魔改对比). The drops for Alliance and Horde only have different names, but their attributes are the same.

Thanks – OK I see now, that document just had one side’s version of the items (looks like all Alliance).

So the other piece of information that I need that I can’t obtain is the item IDs of the new items. In that document there was a screenshot of the tooltip of the Alliance versions, and that screenshot had the new item ID at the bottom, e.g. Blade of Tarasque was replaced with a new 252 version with item ID 237062. So I was able to look up the old 245 Blade of Tarasque (which had item ID 46979) and replace it with this new one.

I would need to know those new item IDs for all of the Horde versions as well – they are new and not available in any older or U.S. version of the client. Then I can use the name of the item to match it up to the old version and do a similar replacement.

I just updated the images , I hope this helps you.

Awesome, thanks! With those item IDs I should be able to get that updated sometime today or tomorrow – we have another update in testing, depends on how long that takes.

We just posted an update that should have these other items updated for WotLK.

In the spell hit section, there are still some errors. Please check my screenshot. My spell hit in the game is 331, which is 12.62%. Adding my Draenei’s 1% hit brings it to 13.62%, and with Faerie Fire’s 3%, it totals 16.62%. This is only 0.38% short of 17%, which equals 10 hit rating (0.38 * 26.24 = 10). However, the calculation result from AMR’s BIB suggests reaching 560 hit rating, which is 21.34%. I have also included my screenshot from WoWSim.



https://file.ctitv.uk:8443/s/2qyzem This link is my export data.

I would need to see a snapshot of your settings: you can generate one by pressing the “help” link next to the big “Best in Bags” section header and copy the 32-digit ID here.

My best guess: you have not chosen all of the raid buffs/debuffs on the setup tab in the options under “Step 2: Set Options”.

When I use your export data and then enable the relevant raid buffs, the optimizer gets 340 hit rating on your gear, which looks good to me.

3dd3dcffcef2421d8ed0dc46c0e19c17

You do not have Improved Faerie Fire chosen under debuffs.

I am sure I have selected the Faerie Fire option. Here is my screenshot.

0e3405ff544744439476c5c3daebc9a9

In the first snapshot that you provided, you only had Heroic Presence chosen under “Raid Buffs”, and “Faerie Fire” chosen under “Raid Debuffs”. You would need to choose “Improved Faerie Fire” under “Raid Debuffs”. (You can confirm that by clicking “help”, then at the bottom of the window click “load a snapshot”, then copy the snapshot ID that you provided me into the textbox and click “load snapshot” – you will see that it did not have Improved Faerie Fire selected.)

In this latest snapshot, you have chosen every raid buff and debuff. In your latest snapshot, you will see that the optimizer is getting 340 hit rating total on your gear, which results in 16.96% spell hit, as expected (340 rating gives ~12.96% spell hit, +1% from heroic presence and +3% from the improved faerie fire debuff totals 16.96%).

In short – you provided me two different snapshots with two different sets of buffs. The optimizer is doing the correct calculation and adjusting for the buffs that you provided.

In order to use the Transmogrification system, the Chinese servers have modified the 3.4.3 client to 3.4.4, and many API endpoints have been adjusted accordingly. As a result, the AMR addon is no longer working properly, especially in the gear section where clicking “Import” no longer opens the corresponding window for importing.I have installed both the AskMrRobot and AskMrRobotClassic addons. In the AskMrRobot addon, the import window can be opened normally, but in AskMrRobotClassic, it cannot.
Please help update the addon accordingly.
image

Because I don’t have a 3.4.4 client that I can test the addon with, I might need some help to fix this issue.

Could you install the two addons !BugGrabber and BugSack (available on most addon websites). Those will capture errors and give you a minimap icon that you can click to show them, and copy-paste the error into a post here. With that I might be able to figure out what has changed.

1x AskMrRobotClassic/ui/AmrUiLabel.lua:107: bad argument #1 to ‘SetJustifyH’ (Usage: self:SetJustifyH(justifyH))
[C]: in function ‘SetJustifyH’
[AskMrRobotClassic/ui/AmrUiLabel.lua]:107: in function ‘SetJustifyH’
[AskMrRobotClassic/ui/Ui.lua]:226: in function <AskMrRobotClassic/ui/Ui.lua:160>
[AskMrRobotClassic/ui/Ui.lua]:359: in function ‘Show’
[AskMrRobotClassic/ui/Ui.lua]:336: in function ‘Toggle’
[AskMrRobotClassic/Core.lua]:26: in function ‘OnClick’
[BugSack/Libs/LibDBIcon-1.0-55/LibDBIcon-1.0.lua]:179: in function <BugSack/Libs/LibDBIcon-1.0/LibDBIcon-1.0.lua:177>

Locals:
(*temporary) = FontString {
}
(*temporary) = “MIDDLE”

this is first page

1x AskMrRobotClassic/Import.lua:116: attempt to index upvalue ‘_txtImport’ (a nil value)
[AskMrRobotClassic/Import.lua]:116: in function ‘ShowImportWindow’
[AskMrRobotClassic/Gear.lua]:384: in function <AskMrRobotClassic/Gear.lua:383>
[tail call]: ?
[C]: ?
[safecall Dispatcher[4]]:9: in function <[string “safecall Dispatcher[4]”]:5>
[tail call]: ?
[AskMrRobotClassic/Libs/AceGUI-3.0-36/AceGUI-3.0.lua]:314: in function ‘Fire’
[AskMrRobotClassic/ui/AmrUiButton.lua]:25: in function <AskMrRobotClassic/ui/AmrUiButton.lua:22>

Locals:
self = {
SpecIds =
{
}

this is second page

Thanks – we’ll publish v17 of the classic addon sometime tomorrow and it should fix this issue.