SylenThunder

Nutrition Buffs by Aesirkin - Shows a number of errors. Did you update this for 20.6? kic's RangerMod ver .3 for a20 - This mod hasn't been updated in 6 months. Is also giving an error. Executing command 'bm-playerunderground' by WebCommandResult_for_bm-playerunderground - This is spamming the logs. A feature of Botman I suppose? As far as server performance goes, it all seems just fine. Issue is likely caused by a mod. Either one of the mentioned errors above, or a mod that changes entities.

A server log would be useful.

It's just system overhead you don't need sharing resources. Also, some people will mistakenly start the dedicated client from steam, and that can have very negative results. This will vary based on your hardware and the image it has. portforward.com is a good resource.

Completely disabling all reflections options helps with this. It is a known issue with the glass in that area.

Be sure to fully exclude your client from security software, and allow it through the firewall. This is covered in detail in the Pinned Support FAQ thread.

It's not a great idea to run Steam on a machine that is solely a dedicated server. Hence the suggestions to use SteamCMD. And personally, if you understand basic high-school level English, you're going to have a lot better experience using a headless Linux build. Especially if you have older hardware. I wrote a guide here. Opening ports is done in your local PC firewall to allow the server to communicate with the world. Forwarding ports is done in your modem/router so make sure that the incoming request on those ports is sent to the correct PC in your network.

Moved to a more appropriate section. Read the Pinned threads. Particularly the one about how to report an issue.

I suppose you aren't aware that The Fun Pimps aren't the ones who released the game on consoles. TellTale Games is responsible for the mess. You can't even do anything about it because they don't exist anymore. Also note that Microsoft's return period is two hours of gameplay or 14 days. If you exceed either, you do not get a refund.

It would help a lot if you could just follow instructions. I fixed your post to make it a Pastebin link instead of a wall of text. Common sense tells you that massive walls of text are bad, and the instructions PINNED at the top of the forum that literally tell you to read them BEFORE YOU POST tell you how to post your log properly. All you have to do is use some basic common sense and look around before blasting the heads off of everyone in the forum. I mean it literally took me only about 20 seconds to fix your post, and half of that was just highlighting the text. Some of it is @%$#ed up though thanks to the forum re-formatting it. (Another one of the primary reasons to never dump your log into a forum like that.) Your issue is a lack of understanding how the game works. Again, you could fix this issue by doing some research and reading beforehand. Just because you set max zeds to 64, does not mean you will immediately have 64 zeds. The difficulty is based on your gamestage, and you will not get max spawn until your characters gamestage reflects that. You don't even need to Google this kind of information, it's literally in the Wiki. So we look at where you start your bloodmoon.... 2022-08-14T14:38:51 4399.907 INF BloodMoon starting for day 14 2022-08-14T14:38:51 4399.909 INF Party of 1, game stage 76, enemy max 315, bonus every 12 2022-08-14T14:38:51 4399.909 INF Party members: 2022-08-14T14:38:51 4399.909 INF Player id 171, gameStage 76 Your gamestage is 76 So then we look at the code for ghe bloodmoon spawner. Your gamestage is 76 and the game has chosen to spawn stage 74 for you since that is the closest without rounding up. <gamestage stage="74"> <spawn group="feralHordeStageGS64" num="105" maxAlive="25" duration="2" interval="19"/> <spawn group="feralHordeStageGS69" num="105" maxAlive="25" duration="2" interval="20"/> <spawn group="feralHordeStageGS74" num="105" maxAlive="25" duration="7"/> </gamestage> Based on this, the absolute most you will see alive at one time is 25. Depending on the world around you, they may not all arrive at once.

Sounds like you might not have NAT Redirect/pinhole/loopback. Many ISP's have been removing this feature from their devices. More detailed information would be useful though. Did you read any of the Pinned threads?

XB1 Version 1.0.18.0 is the most current update for your console. TellTale went bankrupt, and development on that platform ended as a result. You can read all about it in the correct section of the forum for Console players. 7 Days to Die - Console - 7 Days to Die

Picked up some RX 6800XT Gaming Z cards for a pretty good price not too long ago. Here's a copy of what I posted in a Steam discussion regarding 1440p gameplay. Overall, I'm seeing 140-160FPS most of the time. When I'm in the cities it will drop to the 120's, and I've seen 60-90 around the troublesome T5 POI's. In comparison with this setup my 1070's in SLI were averaging 90-100FPS most of the time and dipping into the 60's for horde nights.

There is a legal reason why it was removed, and why it cannot return. Did you do any research before starting this?

The port range for the server is TCP 26900 and UDP 26900-26903. If you change your base port, the rest follow of course. Just FYI.

Oh, it's not even the whole log. That isn't very useful. As Star69 noted, it does need to be excluded from MSE/Defender as that will cause a problem. This is covered in the Support FAQ thread that is Pinned here.

A wall of useless screenshots. Please post the log. The instructions are in the Pinned thread that literally tells you to read it before posted.

You're comparing apples to oranges. None of the titles you listed are voxel games with structural integrity and complex AI pathing. Most of them don't even have random maps. It's just static 2D landscapes. Without the voxels, you have a lot more freedom in graphics. I cover this in great detail in the Support FAQ.

You have to remember too, a lot of systems you think are "being revamped" are actually just placeholders that are being replaced with the ideas the developers have had for a long time. Joel has openly talked about his ideas for the current skill perk system since before Alpha 10 was even out. Their ideas on the clothing changes and inventory management go back almost as far as well. I recall long debated discussions about how to balance inventory space and carrying capacity to provide some limitations without doing something as encumbering as a weight system.

The point where that log ends, it's still generating the world. However if you killed it previously before it finished, then you will need to wipe all the save data and generated world data before starting again. If you interrupt it and start over again, you will get a lot of errors like the null ref in your current log. It's a result of the corrupted data from the previously started map. Should also be noted that map generation on the dedi is a bit longer than on a client, especially if you're using older hardware. Either sit and wait for it, or generate it on the game client and then just load the map on the dedi.

You will want to use a 3rd Party server manager. There is a Pinned thread in this very section regarding them.

Last I was aware, localization is sent from the host.

This occurs because the game is constantly reading/writing from the save files. A fix is covered in the Support FAQ thread, though if you attempt to start the save after you had the crash, you have generally roasted the backup file that you could use to restore everything.

That CPU is your limiting factor. It doesn't even meet the minimum spec speed. We are running X5675's at 3.07Ghz, and are starting to see the stain on the CPU. You won't see your total CPU max out because the game sits on one core primarily. As it sits now with our setup, we're seeing some significant FPS drops on horde nights and when a new player is downloading the map. Otherwise, it seems to run just fine. Currently looking at building a new system with a R9 5950X and a X570S motherboard.

You really do need to update Windows though. Even in our enterprise environment we don't allow PC's with older than 1906 to connect to some things. The standard is 20H2, and the current latest is 21H2. Your machine is pretty insecure and lacks optimization at 1607. Even 1803 is pretty pathetic, and you aren't there yet. That may not have been the issue now, but it will be an issue in the near future.

AFAIK it isn't a bug, it's intended.