You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This TSM port will account for the wrong quantity/money value.
Realm
Seasonal
Tested with only this addon
Yes
No
Lua Error
No response
Reproduction Steps
Buy 1 Jaggal Clam Meat for price X, retrieve it from the mailbox. You now got a entry in the database for 1 Jaggal Clam Meat costing X. Now buy a stack of Jaggal Clam Meat for example a stack of 5 costing X each resulting in a total price of Y.
Retrieve it from the mailbox, Now u got a second entry in the database, also for only 1 Jaggal Clam Meat costing now Y instead of X. -> messing up every operation,custom price source using any form of AVGBUY.
Same is true for sale value. Here a screenshot of the example. (the base price was not the same on both but still lower price was stack of 1 higher price stack of 5 resulting is roughly 500% of the "per item" price tag.
Last Good Version
No response
Screenshots
Screenshot of the example, not 100% same base values on the purchases but still lower value for 1 higher value for 5 -> both accounted as quantity 1. Error also confirmed from Xan in the discord.
The text was updated successfully, but these errors were encountered:
Description
This TSM port will account for the wrong quantity/money value.
Realm
Seasonal
Tested with only this addon
Lua Error
No response
Reproduction Steps
Buy 1 Jaggal Clam Meat for price X, retrieve it from the mailbox. You now got a entry in the database for 1 Jaggal Clam Meat costing X. Now buy a stack of Jaggal Clam Meat for example a stack of 5 costing X each resulting in a total price of Y.
Retrieve it from the mailbox, Now u got a second entry in the database, also for only 1 Jaggal Clam Meat costing now Y instead of X. -> messing up every operation,custom price source using any form of AVGBUY.
Same is true for sale value. Here a screenshot of the example. (the base price was not the same on both but still lower price was stack of 1 higher price stack of 5 resulting is roughly 500% of the "per item" price tag.
Last Good Version
No response
Screenshots
Screenshot of the example, not 100% same base values on the purchases but still lower value for 1 higher value for 5 -> both accounted as quantity 1. Error also confirmed from Xan in the discord.
The text was updated successfully, but these errors were encountered: