SylenThunder

Similar state, except we're using the Improved Hordes mod.

Your character data was corrupted because the client wasn't shut down properly. If you load the save after the crash, it will over-write the backups that are kept. Basically unless you have a manual backup, you cannot recover it. Use console commands to get your levels and gear back.

Not sure why it isn't working for you. Do you have any errors in the log? Where are you hosting the image? I usually use an online service like Gyazo, or put it in the Allocs webmap folder.

Summary: Trader not protected if client data is removed. Game Version: 21.2 (b4) OS/Version: Windows 11 CPU Model: Ryzen 9 3900X System Memory: 32 GB GPU Model and VRAM: AMD RX 6800 XT 16GB Screen Resolution: 2560 x 1440, 144hz Video Settings: High/Custom. Not really relevant though. Game mode: Client on Dedi, not certain on map, but likely one of the pregens. Did you wipe old saves? Yes Did you start a new game? Yes Did you validate your files? Yes, but then I nuked the trader POI files intentionally. Are you using any mods? No EAC on or off? On Status: NEW Bug Description: If you delete the local prefab files for traders, you are free to build and destroy on them for the most part. The protected area that the traders exist in seems to still be invulnerable though. Detailed steps to reproduce the bug: 1) Delete trader prefab files from local client. 2) Join dedi or other mp client. 3) @%$# around in trader. Actual result: You are able to build and destroy inside the trader area. I was even able to plop my LCB down in the area. Expected result: For the trader to be protected. Link to Pastebin Output Log: Mono path[0] = 'D:/Games/SteamGames/steamapps/common/7 Days To Die/7DaysToDie_Da - Pastebin.com You can see in this image where I have destroyed the deco items and replaced them with my bedroll. I have also knocked out the door on the right side of the room, and placed my LCB. Oh, do also note that I was expelled from the trader when it closed. However, I was able to break down part of one of the doors and walk back in for a minute before it kicked me out again.

Assassins Creed and GoW only care about your GPU. 7 Days is CPU-bound. If you follow the instructions and provide a link to a playthrough log on Pastebin, and a published Speccy report, we can help you out better.

Just for reference, here is a link to the report. It contains almost no useful information though, so I'm testing it out now on 21.2 with a TFP internal server.

No they aren't. Your BIOS just prompts the OS to install Armoury Crate if it isn't installed, or when Windows is imaged. Then you just get prompted to install them all. You can totally uninstall them, and they aren't necessary for APU/GPU switching or anything like that. Nvidia drivers already handle that function. Power profiles are un-necessary, and don't require software. The Razer mouse software isn't required for anything but advanced features, and has been well known for almost a decade to cause problems. I have an Asus system with Razor hardware, and the only tool I use is the AI Suite to manage the fans. Razer mouse and headset do not require Synapse or any other software to function. Since you have a craptop, you need to slim down as much as possible. Your GPU is borderline recommended spec, and your CPU should be plenty capable if it isn't overheating. As long as you aren't bogging your system down with other crap, it's not getting overheated, and you're using reasonable graphic options. Sadly your log file has almost zero information outside of the hardware information, so I can't advise you much on what improvements you can make there other than the basic stuff. Disable all premium features. Reflections and shadows aren't going to be a thing for you. Extras like SSAO and light rays are fun, but not for an entry-level laptop.

Trader waypoints is known, and I believe already fixed for the next update. Don't quote me on that though. The question marks on the livemap are part of the new toolset, and it is mostly an example for modders. You can ignore them or remove the map marker mod from the server. Can also just delete them or hide the permissions for it.

Just to note, that laptop is just barely capable. Min spec is a 2.8GHz CPU, and they're rolling in with 2.3GHz as their starting point. It'll be 1.5GHz as soon as it gets hot. Then right off the bat there is a connection problem when trying to make the initial handshake. After that it starts loading data from the server, and throws errors about an invalid block type. This is typically the result of the client missing mods that are required to connect to the host. Since the client is on XBL, they aren't going to be able to install any mods that require disabling EAC. Which is pretty much every overhaul and most asset mods. At the end, it's just a bunch of network errors. Which could be a network problem, an antivirus problem, or just a cascade effect from the previous issues. I would start with them ensuring the client is properly excluded from AV software. (Covered in the Pinned FAQ thread.) Then validate the files a few times to ensure nothing is missing. If there is still an issue at that point, then it's time to start looking into other things like network connectivity, cooling and power settings for the craptop to keep it from having the same performance as a PS4, and again, validating any mods being used on the host are server-side mods that don't require client-side installation.

Current version works fine in a21. I've been testing and using it since before the builds were public.

Doesn't matter. Log didn't show anything other than the server starting up, and then being shut down literally ten seconds later. @Hugo Try posting a log where the server was online, and you tried to connect to it. Include your client log as well. And freaking use Pastebin like you are instructed to do, and don't post a wall of log again.

Moved your post to the correct section. No idea why you posted in the General Discussion section for the old Console port. Please do the needful.

Bug reports go here. Huge red banner at the top. QA will typically not investigate unless you submit it as a bug report in the bug report forum as explained by clicking on the red banner above. It has to be posted in the Bug Pool section.

You posted in completely the wrong section then. Moving to the correct section. Read the Pinned thread on how to report an issue, and follow the instructions.

Not on the console versions. You would need to start a new save.

Validate the files a few times. Else....

System requirements have been updated every couple of builds. I don't see them changing much from where they are at currently, however it should also be noted that they are currently extremely vague. To the point where it isn't very helpful information at all almost. Just stay away from craptops, and you should usually be fine.

Since no one has provided sufficient details to troubleshoot the problem, I doubt it.

Bug reports go here. Huge red banner at the top. QA will typically not investigate unless you submit it as a bug report in the bug report forum as explained by clicking on the red banner above. It has to be posted in the Bug Pool section.

The GPU should be discreet in this case, and is separate from system ram. VRAM isn't virtual ram, it's Video RAM. If it had shared RAM, the system would only be reporting 6GB RAM instead of 8GB. The hardware setup looks like an entry-level gaming laptop circa 2016. The CPU is below current min spec, and the GPU is borderline without being stuck in an underpowered laptop. Add to that the minimum amount of RAM, and the whole setup is a recipe for disaster. You don't have enough VRAM to support loading the textures into the GPU memory, so it has to go to system RAM where you don't have enough overhead to be worthwhile, and all of this is being managed by a CPU that is already too slow when it isn't overheating. Once the CPU warms up a little (which won't be long because the thermal pads expired a few years ago), it gets underclocked to even further below the minimum required spec. Log is too short to determine any specific cause, but that is likely because the system is hung up trying to process anything. If you post a better log, use Pastebin.

Shut server off. Edit file. Start server. Your problem is that you are trying to edit a file that is loaded into RAM while the server is running.

Bug reports go here. Huge red banner at the top. QA will typically not investigate unless you submit it as a bug report in the bug report forum as explained by clicking on the red banner above. It has to be posted in the Bug Pool section.

Our group has three servers on RWG with some mild mods. Did not have this issue at all. OP should probably post logs from when the issue first occurred.