@Geez any news on this?

Hello Cutie.
Please try the following:

May you please advise if anything has been actioned or investigated at the very least?

looks like everything is fine! Thank youuu!

This has also been a bug bear of mine and many other server owners for a few years too. There is too much ambiguity in the community about some of the definitions on several discord and Facebook groups.

Unfortunately we cannot pinpoint which mod is the one that causes the problem

Can you tell me which mod is causing this problem?

Hello Werhmant.
The issue appears to be related to the mods you are running. This might be either an issue with the mod itself which has to be fixed by the mod creator, or the mod is corrupted.
We suggest that you try to uninstall/unsubscribe all your mods, then verify the game data and re-download the mods again. If the issue still persists upon doing so, then it is very likely an issue within the mod itself.
Regards,
Geez

@Geez any updates to this?

I have done further testing on this and even though the roadway LOD visualizer might have a visual offset for display purposes, it actually affects the physics right now as well. Both on diag and non diag build. So @Tyson this should actually be a bug that needs fixing. Good report. I just stumbled across the same issue on my mods ;)

Hello simonvic.
There have been changes made to this for the third experimental of 1.22!

Thank you, we will investigate with BattlEye.

Cheater shot 3 men, no gunshots, all headshots simultaneously as we were in a shed in our base. Base has walls all the way around.

I approve of this message

O_O

It would also be nice to see some new weapons with better modular system. M4 modular concept was nice back then, but it would be nice to have a weapon where you can also change muzzle / handguard / buttstock / fore grip / bipods ... Think you should bring back bipods, back before engine update it was a very nice feature.

Resolved for the future 1.22 updates.

:) Good to know. Thanks.

Hello davezap.
Reforger scripting documentation is very likely not accurate way to go by when trying to mod DayZ

Just noticed the page is for Arma Reforger scripting, is that even the same as Enforce script for DayZ ? perhaps that's my problem :)

Just to clarify - FIREGEOM will be added back but will be assigned to the same value as RAGDOLL_NO_CHARACTER, which should have no impact.

Hello LBmaster.
This has been fixed for the next experimental update. Also, according to the devs FIREGEOM was unused and nothing was being set to FIREGEOM previously. Therefore you had no reason to use it.

That would be useful and in addition to that, a line where the parser said: "nope, that's not what I expected in line ..." would be perfect

so to followup..

Thank you! I'll test this tonight.

Resolved in the current 1.22 experimental.

Hello Nate_LapT.
Please use type "SpookyArea", not "ContaminatedArea_Static", that should resolve the problem.

23rd was the gear of SkySinner

Hello Norealname.
We can give the additional information that the crash on the 24th was caused by the gear [GM]FaNtOm was using

Hello daddy_bjorn.
These crashes are related to the modded content you are running and in such case there is nothing we can do as the mod creators have to fix the issue on their end.

In T174006#2473533, @Geez wrote:

Yes, that would be the place we would look in.

Good afternoon Following your instructions, all mod weapons have been redone, the number of crashes has decreased significantly, but in the last two days there have been two crashes again, could you tell me if they happened for the same reason?

If this behavior is intentional - please add additional optional argument, like local = false to apply it only for specific player.

Currently the only method using tiles like this, and matching structure edges with more pieces.

config.cpp edit used

class CfgVehicles
{
	class Armband_Black;
	class Armband_test_4_1 : Armband_Black
	{
		storageCategory = 1;
		itemSize[] = {4,1};
	};
	class Armband_test_1_4 : Armband_Black 
	{
		storageCategory = 1;
		itemSize[] = {1,4};
	};		
};