On my ( Skipped Intro ) outlaw rogue I opened a bag and got a 200 Condensed Anima Sphere Conduit.
Added it to my forge.
A little later opened another bag and got two more 200 Condensed Anima Spheres.
Yup I got the same problem. Except I ended up with 6 in total
Same, I got 3 iLvl 200 Spirit Drain conduits yesterday, 2 from the same chest! This was a pain in 9.0, but it’s worse in 9.1, especially since the current daily hub is no where near your covenant hall.
Did you acquire the second bag before learning the Conduit? Because that’s a known issue since launch, the contents of caches from Callings etc. are generated when you acquire the item.
1 Like
Generated and stored where? Until you open them and they get stored in your inventory?
Possible, but seems more likely its an item with a onclick reference to a method to generate the items.
At any rate, I did add it my forge before getting the bag and the bag still generated two of the same item.
On the server, most likely. The exact circumstances I can only speculate on, but it’s likely that the cache has its contents saved in some variable assigned to the item, but your client only learns about this data when it attempts to open the cache.
This was probably the case forever, but it was verified (possibly not for the first time) on the player side when people tried to hold onto Emissary caches during Legion that were earned before some patch or season launch happened, in the hopes of either increased AP gains or Legendary chances, not sure anymore. However, all these caches contained loot from before the patch/season.
Hence, the contents are determined when you acquire the cache - if you haven’t learned a Conduit then but it’ in your bags, it can be in the cache, again.
That’s possible, stored in a metadata string but that would be a risky place to store it as far as hacking is concerned.
It would mean that there’s a routine to generate items defined in another items meta data, and that meta data is much more exposed. There are addons that let you see some of it and I would assume there are ways to edit it client side or client side requests to save changes to it.
No, nothing immediately accessible to your client, as I said, the data would still remain on the server until the client actually attempts to open the cache.