Beelzybub

Get the latest version. Also, the author of the mod is very active in the mod's thread on this forum and on the UL Discord channel. If you have issues with the latest version, asking there would likely get a better response than here.

If the Launcher/Tools/Clean game data... and verification didn't work, maybe this cleaning technique will help you.

Your log is from April so I'd bet it is not the latest one. In A20.4 the location of logs changed to %appdata%\7DaysToDie\Logs Can you post a current log?

This appears to be a hardware error, not a game error. So can be closed.

Same error in (b87) Caught fatal signal - signo:11 code:2 errno:0 addr:0x1f4e3f8 Obtained 2 stack frames. #0 0x007f5e47847420 in funlockfile #1 0x00000001f4e3f8 in (Unknown)

The dedi server version does not include a launcher.

No, you need to run using Rosetta to play on an M1.

I think those are instructions for an older version. From the instruction I see: "Undead Legacy manual install for Mac OSx by Galaktus. Works on Catalina and Big Sur."

Land claims don't stop bloodmoon spawns. How big is your base?

Also happening now in (b86) https://pastebin.com/dX4nkSmJ

Open the output log file with notepad. Press crtl a to select all the text. Press cntl c to copy all the text. at pastebin.com where it says "New Paste" press ctrl v to paste all the text. Scroll to the bottom of the page and select paste experation 1 month. Then select "create new paste". Copy the link and paste it here. If you still can't figure it out, use google and search for "How to use pastebin"

Since it's a crash to desktop, there should be an error in your Windows Event viewer at the same time stamp as the crash. Check for that and post the error here. Maybe it will show something of value.

The first thing to try is to clean the game using the Launcher/Tools/Clean game data... menu. Check all the boxes and press "Clean". After that, don't start the game. Verify files through steam, then try again to play.

Press the 'Enter' key.

Enter this in your windows search bar to find your log files. "%appdata%\7DaysToDie\Logs" (without the quotes). Copy the contents of your latest log to pastebin.com and then post the link here.

Enter this in your windows search bar to find your log files. "%appdata%\7DaysToDie\Logs" (without the quotes). Copy the contents of your latest log to pastebin.com and then post the link here.

If you don't have a savegame that you want to try to continue, then yes all of them.

Enter this in your windows search bar to find your log files. "%appdata%\7DaysToDie\Logs" (without the quotes). Copy the contents of your latest log to pastebin.com and then post the link here. Someone will read it and see what the problem is. Did you use the Launcher/Tools/Clean game data... menu yet?

A couple things I think get regularly overlooked are: 1: Change the name of the serverconfig.xml file so it doesn't get overwritten by an update or verify. 2: Backup the save folder daily. 3: Ports that need forwarding are the base port plus 3, ie., If your base port is 26900, you need 26900 TCP and 26900 through 26903 UDP forwarded in your router. 4: Use the <property name="UserDataFolder" value="absolute path" /> in the serverconfig.xml to set a custom path for your save data.

DF works with A20.5, maybe check in on the DF discord. Also make sure you have the latest version which is compatible with A20.5. afaik, the version from nexusmods is not the latest version.

2022-06-20T22:31:54 0.092 INF Last played version: Alpha 19.6 This line from your log makes me thing that the server wasn't cleaned up before installing the new alpha.

Try using the Launcher/Tools/Clean game data... menu to sort things out. After cleaning, use Steam to verify files.

From the main screen select Options/Video/Display/Resolution. Select 1920 x 1080.

You need to install this on the server os.