Not signed in (Sign In)

Support::Auctioneer: Beancounter missing items

Bottom of Page

1 to 3 of 3

  1.  
    • CommentAuthordm9991966
    • CommentTimeJun 3rd 2008
     
    AucAdv 3117: Just noticed that BeanCounter seems to be missing auctions. I purchased 8 stacks of copper bars yesterday, put them all up for auction. they all expired 12 hrs later, retrieved them from my mailbox, but BeanCounter only shows 1 expired auction for today. It shows all the purchases I made yesterday, but only 1 expired auction.
    • CommentAuthorGrabo
    • CommentTimeJun 3rd 2008
     
    I just wanted to report the same bug, so I write a comment here.
    The problem was the same with AucAdv 3104, my first try was to update to AucAdv 3117, but there was no change in the mail-functions.

    The problem is the UniqueID that is checked to find failed auctions in the postedAuctions database.
    I found out, that the UniqueID for some items changes when the auction fails and the item is returned. I am not sure if this is for all stackable items, I just have the problem with all enchant materials that I sell (and I sell lots of them). I believe it was a change with a recent patch, because I have more failed auctions on enchant materials some time ago in my beancounter database (and my selling strategy worked back then :-) ).

    Example for a failed auction:
    Failed auction with 7s offset to expected mail time (I patched findStackfailedAuctions in my copy to search only for the postedAuctions-Element with matching key and stacksize and the closest expected time), so it is most probably the corresponding auction:
    itemString: item:11176:0:0:0:0:0:0:-407286180
    i: item:11176:0:0:0:0:0:0:-405801635
    •  
      CommentAuthorkandoko
    • CommentTimeJun 3rd 2008
     
    Aye, I fixed the issue on unique ID matching recently in the Dev builds, releases 3145 or later should have it.
    Not explicitly stated in the ticket but this was the root cause of the issue http://jira.norganna.org/browse/BCNT-165 />
    Basically the old method of storing the itemLink while fine for most objects caused issues with the Beancounter's 2.0 Database. Since we now have to be concerned with the Unique ID key.

1 to 3 of 3

  1.  
World of Warcraft™ and Blizzard Entertainment™ are trademarks or registered trademarks of Blizzard Entertainment, Inc. in the U.S. and/or other countries.