Tyler Lartonoix

They do actually have IDs internally, they just aren't exposed in the result sets. That's a holdover from when the data was scraped from Kiranico and the ranks set had...

Added to the backlog!

This is definitely something that I'd like to support in the future. I'm going to add it to the backlog, with the goal of focusing on international support as soon...

I'd like to start working on planning this feature out in the near future. I'm not super familiar with the actual practice of localizing / translating an application, but I'd...

If "zh" is usually used to refer to simplified Chinese, then I'm happy making that the fallback instead. It also sounds like "zh-Hans" and "zh-Hant" are what I was looking...

Would it also be a good idea to include translations for enumerated values, like `weapon.type` or `armor.type`? I'm leaning towards no, since they're a defined list of values, and I...

Localization support has been added with [v1.18.0](https://github.com/LartTyler/MHWDB-API/releases/tag/1.18.0)! For those that were interested in helping with translations, the contribution site will now have a dropdown in the top right that will...

That... is a very good point. I honestly hadn't really considered that when I was putting things together. Sorry about that. As far as the defaulting to English for missing...

Which is basically what happened in #157. That's what I was leaning towards as well, but I wanted a second opinion before jumping straight to that. To keep things simple...

It would probably require a refactoring of how event data is stored. Since it's scraped, there's no persistent data between events. Each time range is its own object in the...