Not getting 'weapon' data for event S_EVENT_HIT on server?

[moggel]

I wrote some logic that tracks hits (listening to S_EVENT_HIT event) for scoring purposes and that logic also records weapon type, mainly to filter out anything that's not bullets. But I later realized that when I run the script on a server the `weapon` field is missing from the event. Is that by design and, if so, why? Is there a way to work around that, or ensure the data gets sent?

[Death Merchant]

How are you trying to get the weapon info?

Weapon = Event.weapon:getCategory()

Should return the value of the category.

https://wiki.hoggitworld.com/view/DCS_Class_Weapon

Do you mind sharing your code? I have built something similar using S_EVENT_HIT to record kills. Sometimes you need to do some error handling such as:

if Event.initiator.country ~= nil then

[Zeagle]

It appears that S_EVENT_HIT returns a table with a key labelled "weapon". However, that key has a value of nil.

It does return a key labelled "weapon_name" with a string value equal to the name of the weapon.

Maybe @Grimes or whoever maintains the hoggit ref can update it. 

 

You can do a simple check on the "event" table with the Lua pairs function to see what is returned by the event.

 elseif event.id == world.event.S_EVENT_HIT then     

 

        trigger.action.outText("S_EVENT_HIT\n", 10, true)

        for k,v in pairs(event) do

            trigger.action.outText(string.format("%s\n", k), 10, false)

        end

[Grimes]

You need to check for its existence first. It is inconsistent in returning in MP, but it can return. In SP it is much more consistent. 

[Zeagle]

Thanks for the clarification. I do all my programming for MP.  

Your hoggit scripting reference is invaluable.

Edited February 9, 2024 by Zeagle

[eekz]

On 2/8/2024 at 11:16 PM, Grimes said:

You need to check for its existence first. It is inconsistent in returning in MP, but it can return. In SP it is much more consistent. 

Encountered same problem that projectiles already don't exist as objects in MP by the time the hit event triggered. Only their runtimeIds are availiable. Which are not of a big use since there is no projectile birth event of something so you cant write them down somewhere. Using export to store and update the projectiles db seems like a bit of overkill to me.

Edited yesterday at 07:52 PM by eekz