The Living Dead Walk Amongst Us

They masquerade in human form, they infiltrate through human mimicry. They laugh, they play, they joke around. They look us in the eyes and our mind fools us, believing what we see - looks like…

Smartphone

独家优惠奖金 100% 高达 1 BTC + 180 免费旋转




Destiny 2 Project Part 3

For my capstone project for flatiron school, I decided on using the Bungie API to make an app that would help gamers that play Destiny 2 view information about their characters. Destiny 2 is an action role playing game by the makers of Bungie (creators of the Halo series) that contains worlds of information, many of which is only viewable by interacting with the Bungie API. You can check out the previous part here.

In part 2 of our Destiny 2 project post, we were able to look at all the different fetches to the Bungie Api. However, these fetches were returning numbers that need to be translated. In this next part, we are going to talk about how we make sense of these numbers using a manifest.

Let’s go back to the api call we made to get equipment information in part two.

Lastly, we also have a ItemInstanceId. Unlike the other numbers that can be translated directly by going to the correct manifest file, ItemInstanceId cannot. This is because Destiny 2 is a living breathing game that is constantly changing. A user may level up their weapon, change certain perks, or maybe even delete the weapon eventually. Therefore, every single weapon for each individual player has its own unique ItemInstanceId. The only way to search for the constantly updating information about a weapon is to fetch from the Bungie Api. Luckily, we have done this process before.

We also need to choose what components to search for. Usually when we are using the GetItem api fetch, the component numbers are in the 300’s:

So if we want to make an api call that gives us basic information, perk information, and stats information about a specific item the api call would look like this in postman:

This would return:

As you can see, we get even MORE numbers. These numbers need to, once again, be translated using another part of the manifest files. However, these actions are starting to become repetitive. The goal of going thru this process is for you, the reader, to better understand how Destiny’s complicated Manifest system works. In the next part, we use Ruby to parse information so that information is much more accessible.

Add a comment

Related posts:

Happiness

I used to think my happiness depended on my parents or my happiness were my parents. I was that cry mama girl (i can not talk about daddy because our time together was very limited). Till they left…

Kubernetes with AWS EFS

Recently I was trying to perform distributed training of ResNet50 model using TensorFlow. I set up EKS (Elastic Kubernetes Service) cluster with 3 nodes by following the AWS EKS getting started page…

Inspiration

I had published this to my page on 12.29.20, and an apparent bug in the create-publication function set me back. Or so it seemed. I now believe that I simply was not ready in the Universe’s eyes to…