Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem


There are soft caps, however:
1. However many your server can handle before falling apart from extra load and cross-mod conflicts
2. Server mods are enabled as command line arguments, and (at least on Windows) there is a limit of maximum 8191 characters that you can put in a command line, including expansion of all the environment variables. I don't think DayZ server has a command line option to read the mod list from file, so there's that.
On your first point, I have checked my log files and I cannot find any references to mods being in conflict. But then again it might be written I a way I don't understand. The only real crap I get is from Events.xml in the expansion mod, which endlessly tries to spawn in vehicles. But I think I know how to deal with that, I am pretty sure I got that right before I wiped last time. But I might be very wrong, of course.
The thing is that for some reason whenever I exceed a certain number of mods the game crashes when I load it. I have uninstalled some of my mods "to make space" and installed the new ones. The game loaded and all was well. Then I installed the ones I just uninstalled, but then I got past that certain number and I couldn't load the game. I tried 3-4 different type of mods to check if it worked. But it didn't, I can't seem to pass that limit.
On your second point, the command line is 1865 letters long.
As you perhaps understand, I do have a lot of mods installed, but I didn't want a discussion on the number of mods I have. I did not expect such a well meaning answer, I must admit. Thank you.
Once you enable a mod that causes the crash, you can try to identify what it conflicts with using bisecting technique - you should be able to locate the culprit fairly quickly this way.
Of course, there may very well be an actual hard-coded cap on the number of mods somewhere in the server. I found this gem in 1.16 release notes (https://dayz.com/article/game-update/DayZ-Update-1-16):
"Speaking of servers, we have also increased the limits of script class indexing, which were causing issues when combining a larger amount of mods together."
Out of curiosity, how many mods are you trying to enable when the server starts crashing?
Have you found a breaking point where enabling just one more mod causes the crash?
Does it happen to be some power of 2 value, perhaps, e.g. 128 or 256?
Those can indicate an actual hard limit.
In official launcher it has a grey status and no mods showing,
dayzsa server registration also fails