What steps will reproduce the problem?
1.create a Category and set it up to Ignore Random Enchants
2.have one item with random enchant in your bag (for example: Bloodfist Helmet of the Eagle)
3.add item to a group
4.add group to category
5.first time you try to post in the AH, it will NOT take in consideration the Ignore Random Enchants flag from the category. You will notice that the name of the item on top of the window will be the full name (Bloodfist Helmet of the Eagle) AND the scan will not identify variants of the item (i.e. Bloodfist Helmet of Power, etc).
6.if you run the PostScan again, it will then take in consideration the Ignore Random Enchants flag from the category. You will notice that the name on top will show Bloodfist Helmet and all the different variants will be picked by the scanner.
If you /reload and try to post again the same item, it will go back to step 4 above.
What is the expected output? What do you see instead?
expected output: when you post an item with random enchant (of the...) and the flag is set to ignore random enchants, PostScan should find and list all the variants of the item.
what I see instead: the first time we run PostScan in a session it will not consider the ignore random enchants flag and will treat each variant of the item independently. If we run PostScan again during the same session, it will work as expected.
What version of the product are you using (put the actual number - never say "latest")?
Do you have an error log of what happened?
No, the system does not output an error.
Please provide any additional information below.
I believe I found out the reason and solution:
/modules/manage.lua calls TSM:UpdateItemReverseLookup() and TSM:UpdateGroupReverseLookup() functions to build itemReverseTable and groupReverseTable, respectively.
The first function to run (TSM:UpdateItemReverseLookup()) calls TSM.Config:GetBoolConfigValue() which uses groupReverseTable. However groupReverseTable hasn't been built yet because it will be built by the second function (TSM:UpdateGroupReverseLookup()).
As a result, the first time you run the PostScan after logging in or /reload, the system will not have the groupReverseTable and it will not be able to pick the Ignore Random Enchant flags from the categories.
The second time you run the PostScan, the table will be there.
I believe a simple solution would be to swap the order of those functions in /modules/manage.lua Do TSM:UpdateGroupReverseLookup() before TSM:UpdateItemReverseLookup().
A workaround until this is fixed (in case this is actually a bug) would be to run PostScan two times. The first to build the table and the second to actually post the items.
- 2 comments
- Last updated
- Jul 28, 2013
- Mar 27, 2013
- Declined - We decided not to take action on this ticket.
- Defect - A shortcoming, fault, or imperfection
- Medium - Normal priority.