The kick message is "Warning 0x00040004. You were kicked off the game. Connection with host has been lost.".

So I'm going to start bumping this with user feedback when I have time and when I see it

I've already helped many servers work around the problem, doesn't mean it isn't a problem

Its to do with the mod name from the workshop and the folder name on the server AND the players PC all needing to be the same.

Further information: It appears to be caused by folder names having to directly match mod names. Some mod names have characters that Windows cannot use in mod names

@Geez majority of modded servers aren't able to be joined because of this error screen

We had 2 servers affected by this same exploit. I presume we were used as just another place to test it.

I also agree with this. Just because DayZ hadn't updated doesn't mean mods aren't updating.

@Geez this didn't come in 1.10, when will it come?

Always get this error when combining a lot of mods that have many scripts in 4_World, such as:

In T149789#2112717, @zysen wrote:

Hello All.
There appears to be a limit of 2140 defined classes in the modding interface.

Using the following script and nodejs i generate a c file with 2140 empty classes.
If i build a mod with this inside and run the server with no other mods i get the dreaded "scripts/4_World/classes\useractionscomponent\actiontargets.c(726): Can't find variable 'DEFAULT'"
If i remove a single class, it works just fine.

const MAX_CLASSES = 2140;
const fs = require('fs');
fs.writeFileSync("output.c", "");
for(let i=1;i<=MAX_CLASSES;i++){
	fs.appendFileSync("output.c", "class some"+i+"class {}\n");
}