SylenThunder

These are all things that happen in Beta development. The game is still in Alpha development. The part where major changes to core systems are made. Where simple/temporary placeholders are replaced with the real systems the developers have created. Where the game play style of the game is still being created, and is in flux with each and every update.

Reading the patch notes is useful. Then if that fails....

Need logs

They don't contain private information. I see where the error is in the log, and I'm not noticing any obvious cause previous to it. Please ensure that you have fully excluded the client from security software, and then verify the files a couple of times. Instructions on the former are here. Once that's done, restart your system and try a new save. See if it occurs again.

They don't contain private information. I see where the error is in the log, and I'm not noticing any obvious cause previous to it. Please ensure that you have fully excluded the client from security software, and then verify the files a couple of times. Instructions on the former are here. Once that's done, restart your system and try a new save. See if it occurs again.

You just need to look into gamestages.xml. Assuming that it calculated your group at gs120, it rounds up to the next one since the previous was gs115 <gamestage stage="121"> <spawn group="feralHordeStageGS109" num="171" maxAlive="39" duration="2" interval="15"/> <spawn group="feralHordeStageGS115" num="171" maxAlive="39" duration="2" interval="14"/> <spawn group="feralHordeStageGS121" num="171" maxAlive="39" duration="7"/> </gamestage> Based on this, you should have 24 per player per wave at that gs for the party assuming that the server hasn't already hit its limit somewhere else on the server. Post the full log from the event, and more will be clear. Use Pastebin.

A20 needs Microsoft Visual C Redistributables 2022 to run.

Bloodmoon zombie count will be limited by the gamestage of the players/group. If your gamestage is low enough, you will still be limited in the number of zombies you get.

Could you post a full log please? Use Pastebin.

Could you post a full log please? Use Pastebin.

IIRC, the size must be an odd number.

Moved to a more appropriate section. Please read this....

Verify the client files. Don't forget to exclude the client from security software before hand. Looks like you're missing some.

Moving Save Location to Another Drive This is especially helpful when you are short of space on your 😄 drive, or wish to move your save data to a faster drive for better performance. Open the Steam Client Navigate to your Games Library Right-Click on 7 Days To Die in the left navigation bar. Click Properties Click on the Local Files Tab Click the "Browse Local Files" Button -This will open a Windows Explorer Window. The next Steps Take Place in Windows Explorer Copy serverconfig.xml and rename the copy to serverconfig.SP.xml (or any other name you'll remember). Open serverconfig.SP.xml in notepad and edit the save path to where you want the 7DTD Gamesaves to be stored. Note: Most of the serverconfig.xml properties are ignored when running the Client version of the game, but that property does carry over correctly. Here is an example from my file: <property name="SaveGameFolder" value="D:\GameSaves\7DTD\Saves" /> Save as serverconfig.SP.xml In the steam client. Right Click 7 Days To Die and select properties General Tab, Click Set Launch Options button. Place the following in the box: -configfile=serverconfig.SP.xml Now when you start the game it will use your path for the save files. NOTE: You probably want to move your old save files from "%appdata%\7 Days To Die\Saves" to the new location.

Might not have enough light. If you can plant it, it should be fine.

I think I was helping you yesterday on Discord. Just had a thought.... Have you changed your pagefile settings?

Did you set the launcher so it would start with the config to use another drive? Where is Steam installed? How tight are you on disk space that this is so worrying? You should have at least 30GB free at a minimum.

There is no PI in the files. The server IP is obfusticated , and player information isn't PI. Send the full log, don't edit it, and note the times when it happens.

There is no PI in the files. The server IP is obfusticated , and player information isn't PI. Send the full log, don't edit it, and note the times when it happens.

What do you need to "sanitize"? You have questionable code in your mods that wouldn't be acceptable? If you don't want to actually submit a report, then don't. If you do, then actually do it. Provide the required information.

What do you need to "sanitize"? You have questionable code in your mods that wouldn't be acceptable? If you don't want to actually submit a report, then don't. If you do, then actually do it. Provide the required information.

Right here is the issue. A20 needs Microsoft Visual C Redistributables 2022 to run.

Your Steam ID is not PI. Your IP address is not PI. Your unique Epic ID is not PI. Curious if you knew this already... Epic owns EAC. Has for years. Actually it will run just fine. You can totally disable EOS. Just be aware that your existing a20 saves before you disabled it saved your player data under your EOS ID. So if you disable it after the fact, you'll need to go edit that data to be your Steam ID.

To be fair, some of the tools that the larger servers use to get their increased player counts more stable are not exactly from trustworthy sources. One of which I am almost certain is the source of this attack.