erdb 0.0.4

parse ELDEN RING files into JSON

[WIP] ERDB: ELDEN RING parser

Tool for generating a parsable, JSON-based sets of data for ELDEN RING. Readable by any; human or program alike.

Features

Adopting the database in a project is beneficial beyond just providing the data itself:

Reliable sources

• All the data is ripped straight from the game files using Yabber and ERExporter.
• Mild dependency on Yapped Rune Bear's Paramdex for naming of a few properties.

99%¹ of data is autogenerated

• Values are free from human error and always up-to-date.
• Values are effortlessly regenerated with new game releases.
• Convoluted game parameters are automatically converted into a coherent layout, without losing information².

User contributed information

• Made in mind with user contributions, new findings can be available in every adaptation of this database.
• Interesting remarks about an item or a weapon's true combo list is kept up to date.
• Designed for easy PRs where every item is contained within its own file.
• Ability to specify game version ranges for which a particular information is valid.
• Each human change is checked for correctness (by accepting a PR) and validity (by CI) [IN PROGRESS].

Schema guarantee

• Layout adheres to a strictly defined schema structure, ensuring integrity of all values.
• Sets up REST API endpoints with OpenAPI-compatible documentation.

Shallow structure

• Structure of JSON designed as shallow and straightforward to parse as possible.
• Digging into nested fields is avoided, while retaining a logically sensible layout.

Data for multiple game versions

• Every released game version is supported, from 1.02.1 and up.
• Sources are retained across versions.

Always available

• No extra servers, data is hosted in a repo, uptime is that of GitHub's [IN PROGRESS].
• Download the files and check for updates (recommended) or view the raw content online.
• Public endpoint exposing a REST API for versatile data retrieval [IN PROGRESS].

¹ Some values or means of retrieving them are hardcoded in very specific cases, all listed here.
² Unnecessary information is lost, ex. armor's separate values for bleed/frostbite are treated as a single robustness value.