Using this with stats

[ttgshiesty]

Question I understand stand that to pull certain stats from the embark api the items gotta be mapped as in enemy-kills weapon-kills map performance summary I’m stuck on this I can pull other stats but I’m stuck on this part do I need a publicuuid and do I just add the assetid to my items json to pull the targeted or mapid do I need to link all the ids toghtier or just {
"slug": "light-ammo",
"itemId": "real-item-id",
"gameAssetId": "real-asset-id",
"nameKey": "ST_ItemNames.ID_LIGHT_AMMO",
"displayName": "Light Ammo"
}

{
"slug": "wasp",
"enemyId": null,
"targetId": null,
"nameKey": "ST_Enemy.ID_ENEMY_WASP_NAME",
"displayName": "Wasp"
}

[alexbowe]

Hey Shiesty, thanks for your question.

Unfortunately I haven't played with the stats API yet, so I'm not sure how to answer.
Do you have an example of a stats request you've logged? If so, could you share it here and I'll try to help.

[ttgshiesty]

Thanks man, I appreciate it. I’ve been stuck on this computer for three days trying to figure this out. I have the extension and everything set up, but my auth token is messed up right now, and getting a token from Xbox has been difficult.

The main problem I’m running into is that I can get stat returns from most of the Embark routes, but I’m stuck on how to correctly link everything together by IDs. The enemy-kills route returns targetId, the weapon-kills route returns weaponAssetId and itemId, the map-performance route returns mapTargetId, and the summary route returns values like totalContainersLooted.

My normal items.json uses item IDs like venator_iv, but the stats API returns weaponAssetId, so I need help mapping those IDs correctly. I’m also confused about what instanceId and publicUuid are used for, where they come from, and whether I need them for stats or only for inventory/stash items.

I already have my stats mostly normalized, but I’m stuck at the point where the API IDs, item slugs, game asset IDs, weapon asset IDs, map target IDs, and enemy target IDs all need to connect cleanly. I’d really appreciate help fixing this mapping layer so the stats, weapons, enemies, maps, and inventory all line up correctly. if you wanna see the source i got no problem uploading the latest copy quick

[alexbowe]

It's been a while since I've dug into the API so I'm a little rusty now, but I think publicUuid can probably be ignored for what you are trying to do. UUIDs are usually just used as references to an instance of something (e.g. a particular item in your inventory). The type of thing it points to is defined by the asset ID (for example, use the UUID to move an item to a different inventory slot, but read the asset ID to know what the item actually is).

I know that they use different names (e.g. weaponAssetId, gameAssetId) for things that essentially mean asset_id, so it might help to just cross reference all returned integers with the asset_index.csv in this repo (which I'm almost certain is complete) to see if there are any hits.

I don't remember seeing any human readable slugs coming from the API. Did you get your items.json file from somewhere? If so that's probably added by whoever made it to have a readable stable ID to refer to instead of the integers (which they would then replace with the integer in the API). But again, I might be forgetting some API response formats.

Lmk how it goes. I'll try look into it myself when I have time (but that might be a while). I'm interested in whatever you find out.

[alexbowe]

Also, Embark patched the web Oauth flow last week.

ArcTracker and Metaforge had that first, but all other places I know of were using code that I wrote (which took ages to work out) that somebody leaked. So if your extension was using that, don't continue down that particular rabbit hole.

[alexbowe]

One more thing: I think this repo should have everything you need for interpreting the API responses.

Everything else is available in the API itself (e.g. game-data). So any fields in an items.json file from somewhere else can be gotten from here or the API, or were added by someone else. I didn't include those fields in this repo because they can be updated whenever (i.e. without a game patch), so it's better to get them from the API.

But if you discover otherwise I'd love to know what else I should add :)

[ttgshiesty]

thanks for the response
man ill let you know how it works out

[baschny]

If you are talking about the stats API (stats-player-v2):

targetId = the object or subject (either an ARC, a target, a mapId, etc). Note that there are plenty more Ids than are currently documented in the asset-index (i.e. another raider ="995408715", the maps have ids, every quest has an id).

What the targetId is, depends on the eventId, which is an integer like "100" = "Dealt Damage (To)", "600": "Items Crafted", etc.

[ttgshiesty]

{
"eventId": 100,
"eventName": "Dealt Damage To",
"targetType": "enemy_or_raider",
"targetId": "995408715",
"resolvedName": "Raider",
"assetMatch": null
}

Thanks man that explains it !

[baschny]

One more thing: I think this repo should have everything you need for interpreting the API responses.

Not completely, there are several gameAssetIds in the API which are not covered in this repo. I think the reason might be that they are not used inside the client but only server-side. Just a guess. Some examples, the mapIds, mapEventIds, seasonsIds, projectIds, questIds, POIs from quests, trials, some grouping targets used in trials.

We can discuss in private what we want to do with those.