Resolved with 1.21 update.

Workaround for the events crash is

1. Reimport animation
2. Check in anim editor
3. Restart workbench completely
4. Saving events works

video of workbench crashing while saving animation events

Hi there,

Just to give a example what kind of problems for mods this could solve when the parent widget would adjust its content size depending on the children:

Hello M4STURch33fee.
This issue occurs due to H:\SteamLibrary\steamapps\common\DayZ\!Workshop\@NAMALSK TRADER\addons\nothink.pbo' being corrupt.
Please remove or redownload the mod.
Regards,
Geez

Thank you! This message made my day. Another step close to horse :)

Hello Hunterz.
The code you mentions work offline will work in online environment with the update 1.21.
In 1.21, the pivot and positionOnly flags called from 'IEntity.AddChild' will now synchronize in multiplayer.

This is still an issue.

+upvote any updates,? Still an issue.

In T170180#2408842, @Geez wrote:

Hello p4k1tz.
Due to the current priorities with the release and possible hotfix, we cannot address this immediately. I will let you know if there are any new developments.

Thank you for your feedback InclementDab.
I will forward this to the devs and it will be considered.

Thank you for the report. We will take a look into this with the BattlEye team.

Hello bluesun.
This is intended by design so you do not end up with two SVD's at a single heli crash for example.
Regards,
Geez

Further testing showed that the kill source is fine in the EEHitBy and in EEOnDamageCalculated methods.
Just EEKilled fails to return the correct entity in AnimalBase:

I was also able to reproduce the mentioned issue with the kill source.
No matter with what a animal gets killed the entity returns itself as the killer in the EEKilled method on server side if it is inheriting from AnimalBase.

@Geez Thank you very much that's exactly what I was looking for.
I had hard time to figure out how to use it for my needs but now it's done and all seems work well.

Hello Liven.
The developers suggest to use the method Object::ProcessDirectDamage instead of Object::SetHealth to deal the damage in a situation like this.
Regards,
Geez

This MOD is very popular and hopefully developers can help out with this.

After deleting some mods through the publisher the issue seems to have disappeared. Would be nice if this would be looked into as there seems to be a mod limit.

Hello p4k1tz.
Due to the current priorities with the release and possible hotfix, we cannot address this immediately. I will let you know if there are any new developments.

@Geez Has this question been passed to anyone for a potential answer?

This is on console servers...sorry forgot to mention it

My thought is, there starts to be a limit to how much publisher can handle with how many mods have been published overtime. Currently just hit over 50 recently.

@Geez Any new information?

Ticket can be closed, for future reference for others: the class HumanItemAccessor methods for each entity is tied to Human instance. Access it via Human::GetItemAccessor(); and the methods within HumanItemAccessor will be relative to the entity. The features mentioned above in the original ticket are working as intended

@Geez Battlemetrics have same problem to decode A2S_RULES correctly in some cases.

unfortunately no new information I can provide at the moment as the devs will have to dig deeper into this.

@Geez Any new information?

Above is an example response that can be used as a reference. Between offsets 0x0000002E and 0x00000032 should be the steam ID of the mod. But Offset 0x0000002D describes the steam ID length being 4 byes. 2E through 31 are not the correct steam ID, and neither is 2E through 32. I can only assume one of these bytes is a modifier for the steam ID, is corrupt, etc.

In T170180#2404850, @Geez wrote:

Hello again,

According to the devs:

https://developer.valvesoftware.com/wiki/Server_queries

It's just 1b header + long challenge, then some data if challenge is in incoming message - otherwise 1b header + int16 rules count and list of rules - which is as in steam documentation.

Hello again,

In T170180#2404740, @Geez wrote:

Hello p4k1tz.
Is there any relevant reason why do you need to know this information?