ESO-Database Game Data API for AddOn Authors

[Keldor]

Originally Posted by DewiMorgan Could it gather and share usage data that HM does NOT provide? For example: I'm interested in making an addon that modifies maps to show where cliffs are. Putting their locations in the map is easy enough manually, but heights are another issue. Crowdsourcing the falling damage taken (before armor etc) would give an idea of how high the cliffs are in a way that's maybe more useful to map readers than knowing how many feet high a cliff is. As well as just making for a very amusing heatmap of where people most often yeet off cliffs. Another example: I've written an addon which needs a translated whitelist of searchable items. I was considering crowdsourcing so that any item people hit E to use, which wasn't already in my addon, would save its location and name in various languages. We could very rapidly build an item-translation database that way. Perhaps even more importantly, we could find cases where items are inconsistently translated (where eg two items, one metal and one wood, both called "barrel" in English, get called "barrel" and "drum" in some other language). This would not easily be found by devs otherwise. I'm sure there are plenty of other crowdsourceable data types that would be super useful to devs; while the answers here seem negative, might that just be that for your first API release, you happen to have selected the very few data types that turn out to already be well-tracked and crowdsourced already?

Hi,

thanks for your ideas.

I still have the TODOs for collecting resources, books, etc. on my list. Unfortunately, I haven't had time for that yet.
The cliff thing is more a very specific part of data collection, right? I think this is to much overhead for "fun data"

I've also been considering building an Item DB, since I already have a lot to do with Item IDs in the ESODB anyway, through the recipes, furnishings, and now more recently the Set Collection. But here I have the problem with the time and effort, because I want to do other things before.

[DewiMorgan]

Originally Posted by Keldor The cliff thing is more a very specific part of data collection, right? I think this is to much overhead for "fun data"

Oh, fersure: my point wasn't "you should implement these specific things for me!" but just to show that even I, a total noob, had already felt the need for crowdsourced data. There will be good things and bad things to gather, and if the possibility's there, I'm sure you'll get a zillion suggestions for both!

So my main point was just to say that perhaps people are only being negative, because they aren't seeing the full power and scope of the things an API like this could offer in the future?

[Keldor]

Originally Posted by DewiMorgan Oh, fersure: my point wasn't "you should implement these specific things for me!" but just to show that even I, a total noob, had already felt the need for crowdsourced data. There will be good things and bad things to gather, and if the possibility's there, I'm sure you'll get a zillion suggestions for both! So my main point was just to say that perhaps people are only being negative, because they aren't seeing the full power and scope of the things an API like this could offer in the future?

Oh, then I actually misunderstood I had understood it as a feature request.