weapon datasheet 'max' and 'min' damage are meaningless due to API quirks about auraxium

[EllyArd]

I realize in retrospect that this is technically under #18, but I think the fact that the datasheet itself is formatted badly (and also where most people would first look? Unless I'm missing some docs that expose the structure of this much more than I've found)

Maybe this is an issue of naming though -- When I saw datasheet, I expected a summary, which daybreak has filled wrong, and isn't the app's 'fault', but it might be good to have a similar summary thing that spits out comparison-relevant statistics.

[leonhard-s]

Hey, thanks for the report!

There is not much to add to your elaboration I think - that table has been flaky for years though, so adding a big "warning: this could be nonsense" banner to the docs would be helpful.

I generally avoid hard-coding my own data types around the API's since this makes the app's code API version specific (and DBG seems to have abandoned versioning the API, unfortunately). It also risks cutting out some weird edge case where you need a specific API key that only works correctly for some entries.
Maybe we also just misunderstand that key's purpose; maybe this is a certain minimum damage amount that cannot be further reduced by armour?

Either way, I agree that reports are the best solution for this. Auraxium can provide a few stock ones (including a replacement for the unreliable weapon datasheets), and users can then use the report system to add custom ones if their app needs them.