JavaScript is required to use Bungie.net

Group Avatar

BungieNetPlatform

"Updates, discussions, and documentation of the BungieNetPlatform API."

Request Join
originally posted in:BungieNetPlatform
7/15/2015 1:47:06 PM
0

Engrams + Mobile Manifest Cache History

So you might have seen a few threads pop up on the forums talking about how if you farm older strike playlists for engrams, these will have a chance of holding past DLC and vanilla items (ideally of the legendary persuasion). Rather than grinding for hours, I thought I would try and debunk this rumour using the APIs... Normally when new content gets added, a new version of the same item gets created since players can potentially have both versions of the same item at the same time (ie like Iron Banner Weapons). The problem with engrams, is that they all look the same so there's not a lot of ways to be able to tell what kind of engram you are holding. Looking at a combination of item attributes (perkHashes, sources and values), you can sort of make assumptions where some of the engrams come from, such as that fact that any Rare engrams with an Uncommon values tier should be from before the 1.0.2 Patch (the engram patch), and using my [url=https://www.bungie.net/en/Clan/Post/39966/138407555/0/0]perkHash assumptions[/url], you could assume that any engrams that don't have a certain 2 perkHashes are either not used by the game or they are random reward engrams that automatically decode upon receiving them. None of the engrams that have the Cryptarch or Xur as a possible source include the 2 perkHashes you see on other engrams, which is what makes me think that they will only drop on the ground if they have those perks. Another option is looking at when a said engram was added to the database. Unfortunately I only have cached versions of the mobile manifest going back as far as 1.1.0 - Expansion I: The Dark Below (but if anyone actually has older versions I would love to get a hold of them for tinkering... even if all this was for naught :p), but assuming the itemHashes are never recycled, you can sort of get a better picture about how old engrams (and other stuff in the manifest) are. [url]https://www.dropbox.com/s/r7f1a6ruez611e1/engram-test.jpg?dl=0[/url] Assuming the time when an engram was added relates to what it can contain, you could say that all engrams added after 1.2.0 should contain House of Wolves items in the loot pool. Interestingly most of these have a hash which was removed and then added again later, meaning items may be recycling hashes or that engrams are getting repurposed (I'm currently only comparing between manifest versions using hashes so I can't tell). And to test the rumour, I did a handful of Tiger Strikes until a got a few engrams from the reward screen. Even if it proves true that you could theoretically obtain older gear by farming older strike playlists, I really wouldn't recommend it given you are likely to get 1 engram for every 3 or so strikes, especially since the Cryptarchs are [b]clearly[/b] colourblind... 4143281036 - Rare Special Weapon (1.2.0) 1192888947 - Rare Gauntlets (1.1.0 or older) 42955693 - Rare Chest Armor (1.2.0) 1518110335 - Rare Chest Armor (1.1.0 or older) 395266917 - Rare Leg Armor (1.1.0 or older) I think if there was a definitive way of locking down which engram will only contain items prior to a specific update (assuming that the item pools are tied to each engram instance and don't change as time goes on), it would be cool to build an Engram Scanner that you could drop in an engram and get an idea of what "might" be inside (even though you really have next to no chance of scoring anything legendary from a rare engram...). Same would go for Reward Packages, however it definitely isn't possible to obtain those once a new DLC comes out. I kind of think farming for classic weapons IS just a rumour created by forum trolls, but it was fun trying to debunk it with what information is available, even if most of what I have said is just based on assumptions :p

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon