cooltrain7/Planetside-2-API-Tracker

Possible incorrect other_id field for GainExperience_experience_id_56

Varunda opened this issue · 1 comments

The payload for GainExperience_experience_id_56 (Squad spawn) may be incorrect, with the other_id field containing the same information as the character_id field.

Example:

amount: "10"
character_id: "5428061686721181409"
event_name: "GainExperience"
experience_id: "56"
loadout_id: "13"
other_id: "5428061686721181409"
timestamp: "1600802045"
world_id: "13"

I would expect the other_id field to contain the NPC ID of the NPC that provided the spawn, such as a sunderer spawn event:

amount: "5"
character_id: "5429038329433132081"
event_name: "GainExperience"
experience_id: "233"
loadout_id: "29"
other_id: "17217290434"
timestamp: "1600801687"
world_id: "13"
zone_id: "4"

The other events that provide spawns (construction spawns, sunderer spawns and galaxy spawns) all follow this same format, with the NPC ID in the other_id field. Having the NPC ID is useful when used with events such as router destroy, and sunderer destroy, as the other_id field in those events contain the NPC ID of the NPC that was destroyed. Only exp ID 56 (squad spawns) does not follow this format, making me believe it is an error.

As an example of what is possible when the NPC ID is used, I can track when a router is spawned (by listening to ItemAdded events), when a router is first used as a spawn, and when that router was destroyed. I can do something similar with sunderers, tracking when that NPC ID first shows up and when it's destroyed by matching the NPC ID field. I cannot do this with squad beacons, which is a real bummer.

[DBG]MangoBean - Planetside discord, api-dev channel:

This is likely intentional, as it looks like that event is used for more than beacons.