Altoholic

162 - Tooltip shows "allready known by" wrong character.

When having the mouse over leatherworking recipes at the AH, Altoholic shows that my lowlvl leatherworker knows the same lvl 450 recipes as my highlvl leatherworker do.

My setup is like this:
3 leatherworkers.
2 alliance and 1 horde.
The two alliance LWs are 450 and 442. The horde one is 305.

It looks like it's a display problem and not a store problem, since I've tried to delete my horde LW to reset all data on that character.
In DataStore_Crafts.lua it seems to be oki.
The sequence the characters are stored in that file is: my 442 lw, my 450 lw and my 305 lw.
So it seems when altoholic is making the tooltips, the recipes from my 450 comes over the recipes for my 305 lw somehow.

It might be that this issue isn't just affecting LW, but also other tradeskills. But LW is where it was visible for me.
Altoholic version 3.3.002, DataStore_Crafts r23

User When Change
pompachomp Oct 01, 2010 at 04:02 UTC Changed status from New to Invalid
BoaConstrictor Mar 21, 2010 at 11:46 UTC Create

You must login to post a comment. Don't have an account? Register to get one!

  • 3 comments
  • Avatar of BoaConstrictor BoaConstrictor Oct 20, 2010 at 09:31 UTC - 0 likes

    As a second comment, I can say that I get the exact same result on my laptop also even if I didn't copy the data files over from my gaming PC.

    And that was both when I opened the ticket and now.

  • Avatar of BoaConstrictor BoaConstrictor Oct 20, 2010 at 08:37 UTC - 0 likes

    This one still happens after 4.0.1, running with: Altoholic r96-nolib DataStore r27-nolib DataStore_Crafts r27-nolib

    I still only get it on my leatherworkers, but as I wrote this can be a coincident. Also notice that all Altoholic*.* and DataStore*.* files under WTF was removed after the 4.0.1 upgrade if Altoholic as the changelog told us to do.

    So when this happens over multiple versions and with the same chars each time even if the stored data are removed, I have to say it has to be a bug somewhere.

    If you still think the issue is invalid, then write why you think so and what else you need me to do to help you solve the issue?

  • Avatar of FuxieDK FuxieDK Jun 16, 2010 at 19:45 UTC - 0 likes

    I see this from time to time too...

  • 3 comments

Facts

Last updated
Mar 30, 2012
Reported
Mar 21, 2010
Status
Invalid - This was not a valid report.
Type
Defect - A shortcoming, fault, or imperfection
Priority
Medium - Normal priority.
Votes
2

Reported by

Possible assignees