Artifact offhand always 750 #14


  • Defect
  • Replied
Open
Assigned to esperlily
  • _ForgeUser139744 created this issue Sep 6, 2016

    What steps will reproduce the problem?
    1. Acquire a Legion artifact weapon with an offhand.
    2. Upgrade the weapon.
    2. Check the offhand's iLevel using :GetUpgradedItemLevel().

    What is the expected output? What do you see instead?
    Its iLevel is always 750.  It should mirror the iLevel of the mainhand weapon.

    What version of the product are you using?
    Latest (Release-70000-24).

    Please provide any additional information below.
    1. If you manually examine your offhand, its iLevel matches your mainhand weapon.
    2. If you manually examine someone else's offhand, its iLevel is always 750.
    3. The library's tooltip scanning returns 750 even for your own offhand.

    Notes:
    It's not clear whether the library can or should handle this case, as it has no way to get the mainhand iLevel from the offhand link.

  • _ForgeUser139744 added the tags New Defect Sep 6, 2016
  • _ForgeUser139744 edited description Sep 6, 2016
  • Terciob posted a comment Sep 12, 2016

    since the offhand always have the same ilvl from the main hand, a simple workaround would be check for the itemId (133959 for fire mage) and if is the off-hand, return the ilvl of the main hand.

  • alarthedark posted a comment Sep 13, 2016

    Sorry guys, I am having a bad time in real life and hadnt yet got the chance to level up a toon with an offhand and I played an hunter even in beta. Will try and catch this weekend


    Edited Sep 13, 2016
  • alarthedark posted a comment Sep 17, 2016

    Indeed, this ons is a tricky question As a lib, we should not be allowed to do tricks with other items. How can we assume that the itemlink we are given is from a toon we can scan for main hand? I assume that if we give back the iLevel in tooltip we should never be on the wrong side

  • EsperLily posted a comment Sep 17, 2016

    I don't know why the tooltip scanning doesn't work for the offhand. When I look at my own character sheet and mouse over my offhand, it shows the right level. But if I inspect someone else and mouse over their offhand, it always says 750, which is presumably the same reason why LibItemUpgradeInfo always sees 750 for it.

    I really wish Blizzard would just provide this functionality themselves.

    In any case, alar is absolutely right in that we can't really assume the item link we're scanning corresponds with any particular slot on any particular character whose inventory we have access to.

    Does anyone know offhand if there's a way to tell what relics are slotted into an artifact weapon based on the itemlink? I haven't investigated this yet, but I seem to recall that itemlinks contain info about gems slotted into them. If we can figure out what relics are slotted, and we can get info on them, then we might be able to calculate an item level, though I'm a little skeptical that this will actually work.

  • alarthedark posted a comment Sep 18, 2016

    @eridius: Go

    So, tooltip scanning actually working but it's just the tooltip which is wrong?

  • Bullseiify posted a comment Sep 19, 2016

    for me the tooltip scanning is working. and its not always the offhand thats only 750 item level. I found out that the shield of prot paladins and prot warriors is the one that has the higher item level. So i guess its blizzard's turn fixing that.


    Edited Sep 19, 2016
  • alarthedark posted a comment Oct 30, 2016

    Looks like now we need to anchor the tooltip in order to have it filled Also, GetIteminfo for artifact is returning the true itemlevel, while tooltip scanning was doubling the levels from relics

    I'll keep an eye on Blizzard moves

  • alarthedark removed a tag New Oct 30, 2016
  • alarthedark added a tag Fixed Oct 30, 2016
  • alarthedark closed issue Oct 30, 2016
  • Bullseiify posted a comment Nov 1, 2016

    i know that this ticket is closed but there is still a problem with getting the correct itemlevel from artifact weapons because of delay. and it seems like the lib stores the incorrect itemlevel so you have never the chance to get the real item level again because you always get the cached, wrong, too low one. The addons AverageItemLevel https://mods.curse.com/addons/wow/averageitemlevel and Cloudy Unit Info are checking for that stuff https://mods.curse.com/addons/wow/cloudy-unit-info i guess it would be better to check for that gems and don't return or save an itemlevel if the gems are not cached.

  • alarthedark posted a comment Nov 2, 2016

    @alar: Go

    Actually, I am a bit disappointed with Blizzard...

    Which is the point in releasing a GetDetailedItemLevelInfo api if its values are "random" (and, also, it is never used by blizzard code so no way to guess what its return values are supposed to be :( )

    I will check the addons you pointed me to

  • alarthedark posted a comment Nov 2, 2016

    @alar: Go

    Btw, could you update the version you are using? ticket was opened on rel 24 and now we are at 27 Thanks

  • alarthedark removed a tag Fixed Nov 2, 2016
  • alarthedark added a tag Waiting Nov 2, 2016
  • alarthedark reopened issue Nov 2, 2016
  • Bullseiify posted a comment Nov 2, 2016

    i guess you mean me right? i updated to the latest release. i am refering to the latest version.

  • Bullseiify removed a tag Waiting Nov 2, 2016
  • Bullseiify added a tag Replied Nov 2, 2016
  • alarthedark posted a comment Nov 2, 2016

    @alar: Go

    YEs, was regerring to you :) Could you please write the version number? When I will read this ticket again in a week or two "latest" will not be so useful ;P

  • Bullseiify posted a comment Nov 2, 2016

    Release-70100-27 7.1.0

  • Bullseiify posted a comment Nov 19, 2016

    Did someone answer to my latest post? All i can see is "Created Sep 7, 2016, updated 22 hours ago" for the ticket. but the latest comment on the ticket i can see is my post that i did on the Nov 2, 2016.


    Edited Nov 19, 2016
  • alarthedark posted a comment Nov 21, 2016

    There is a new release which implemented the change you asked for


    Edited Nov 21, 2016
  • bsmorgan posted a comment Jan 17, 2017

    I'm using release 28 and I still sometimes get 750 for my own main hand artifact (Frost Mage). Tooltip always shows 872. Is there a way to clear the cache for an item?


    Edited Jan 17, 2017
  • alarthedark posted a comment Jan 18, 2017

    Well, an "hard one" is /reload. Reloading the interface reset all addons data but not the client cache.

    Will think about something less invasive :)


    Edited Jan 18, 2017
  • bsmorgan posted a comment Jan 19, 2017

    After looking at the code, I tried  libItemUpgrade:CleanCache() and that worked for one character but it didn't for another so the jury is still out.


    Edited Jan 19, 2017

To post a comment, please login or register a new account.