Character-Stats

Destiny 2 Character Stats

Crowdin

This repository contains an up-to-date (usually) collection of ability cooldowns as well as other benefits that character stats provide which can be easily parsed by 3rd party applications. This also includes support for Aspects and Exotics changing the base cooldowns of certain abilities among other things.

All the data stored here is intended for use by 3rd party apps willing to implement them in place of Bungie’s own outdated and incomplete information on Character Stats. This includes cooldown times as well as every other kind of useful information that is available from community research.

Currently used and trusted by Destiny Item Manager and D2ArmorPicker.

Disclaimer

Report Issues/Inaccuracies

If you notice any inaccuracies in the dataset, feel free to file an issue in the Issues tab and fill out the template. Otherwise, feel free to contact me on Discord @starglance (Stardust) as well. You can also find me in the DIM, Clarity, and Massive Breakdowns Discord servers.

Crediting and Usage Policy

Do NOT claim to be the creator/curator of this database or its contents. This includes purposefully showing the data in a way that leads people to think you may be the maintainer of this data.

That’s really about it, I don’t ask for anything else. As long as you don’t break that rule, please feel free to use whatever info is stored here for your projects.

However, I would certainly appreciate it if you linked back to this repository and Clarity’s Ko-Fi page. But it’s not required so it’s entirely up to you.

Database Information

Vital information about the database structure and what each property stored in it represents can be found in the shema.json file here.

In addition to the main database files, the update.json contains the following two values:

Example usage the update.json file for handling breaking changes:

  1. The app developer stores the schemaVersion property during implementation to use it for checks
  2. When accessing the update.json file to check if there is new information available, the app detects that the current schemaVersion does not match the version stored in the app’s code
    • Here, the app developer can choose to display an alert informing the user that the app might be displaying outdated information.
  3. Until the developer updates their implementation to support the new schema, the app can still access the old version’s files by using the coded-in schemaVersion as in the database URLs

Credits

I want to thank Hugo for their amazing spreadsheet which provided the fundamentals of this database and u/Crystic_Knight for their breakdown of Mobility. Last, but most certainly not least, I want to thank RyTako for his spreadsheet and ongoing quality testing to help out the entire science community.