SylenThunder

This isn't an a20 issue. This has been an issue for forever because of how the game functions. So much so that it's even described in detail with recovery methods in the pinned Support FAQ thread that you might have glanced at before starting a new thread. So you've chosen to fail before even starting. That's great. Good for you buddy. I'm done with people like yourself being self-righteous @%$#s that can't be bothered to do even the bare minimum research before posting. Maybe you should go shove your frustration in a hole and do some actual research before flaming everything in a thread. If you had instead spent 5 minutes poking around the PINNED threads literally at the top of the forum for the very purpose of assisting you with common issues, you would have had a fix already. Instead you're just sitting here being a slob with your head up your ass. Or maybe learn how to make backups. It's not hard. There is literally tons of free software out there.

Not a bug, and is described in detail in a thread just a few days ago. Before reporting a bug, you need to at least do some background checking to see if it is actually a bug, instead of just assuming it is because the game did something you didn't like.

The player has the connection issue to the EOS servers. Looks like the service is enabled and functioning just fine. No errors about needing C++ redis. I do find two parts of the log interesting though. First we have 2022-01-03T22:28:48 1.564 INF [Platform] Initializing EOS 2022-01-03T22:28:49 2.205 INF [EOS] Initialize: Success This is where we would usually see the error about it not being able to initialize because it's missing the redis. However just a little bit later after loading the base data and server admin... 2022-01-03T22:28:55 8.159 WRN [EOS] [LogEOSAnalytics - Warning] EOS SDK Analytics disabled for route [1]. What disabled it? What is route [1]? Afterwards it seems to connect, but then looses connection. 2022-01-03T22:28:56 9.249 INF [EOS] Login 2022-01-03T22:28:57 9.848 INF [GSM] Skipping me 2022-01-03T22:28:57 10.373 INF [EOS] Login succeeded, PUID: 0002cee7263b47c0a67432725ff78ca2 2022-01-03T22:29:47 60.096 INF [GSM] GameSparks Disconnected 2022-01-03T22:29:47 60.694 WRN [EOS] [LogEOSMessaging - Warning] Lost connection to Stomp on 'wss://api.epicgames.dev/notifications/v1/30b9e9e5f58b4f4e82930b3bef76d9e1/connect' () - will attempt to reconnect after 5.4 seconds. LocalUserId=[000...ca2] 2022-01-03T22:29:53 66.211 ERR [EOS] [LogEOSMessaging - Error] Failed to connect to Stomp! Could not initialize connection 2022-01-03T22:29:56 68.815 WRN [EOS] [LogHttp - Warning] 0000027BE0846A40: invalid HTTP response code received. URL: https://api.epicgames.dev/telemetry/data/datarouter/api/v1/public/data?SessionID=%7B43DB53E8-43CB-EC6A-B569-BA9E59E4CD89%7D&AppID=EOSSDK.PhaseRelease.ReleaseBuild&AppVersion=1.14.1-18059966%20-%20%2B%2BEOSSDK%2BRelease-1.14.1-CL-18059966&UserID=&AppEnvironment=Production&UploadType=sdkevents, HTTP code: 0, content length: 0, actual payload size: 0 2022-01-03T22:29:56 68.816 WRN [EOS] [LogHttp - Warning] 0000027BE0846A40: request failed, libcurl error: 6 (Couldn't resolve host name) 2022-01-03T22:29:56 68.816 WRN [EOS] [LogHttp - Warning] 0000027BE0846A40: libcurl info message cache 0 (Found bundle for host api.epicgames.dev: 0x27c15a436e0 [can pipeline]) 2022-01-03T22:29:56 68.816 WRN [EOS] [LogHttp - Warning] 0000027BE0846A40: libcurl info message cache 1 (Hostname in DNS cache was stale, zapped) 2022-01-03T22:29:56 68.816 WRN [EOS] [LogHttp - Warning] 0000027BE0846A40: libcurl info message cache 2 (Could not resolve host: api.epicgames.dev) 2022-01-03T22:29:56 68.816 WRN [EOS] [LogHttp - Warning] 0000027BE0846A40: libcurl info message cache 3 (Closing connection 1) I can only assume that this is a firewall or security software issue with the connection to the EOS server being blocked. I have not ret received enough information from those that keep having the issue after properly allowing it to determine a cause. My guess would be that it is still being blocked. In most cases though, allowing the firewall passthrough, excluding from antivirus and antimalware, and possibly whitelisting the EOS URL resolves the error. I don't know what effect the client not being able to reach EOS has on playing with the server.

Yes, that's entirely how it is intended. That's why they switched to using gamestages for difficulty instead of basing it on what day it is. It levels the playing field for new people joining servers that have been running for a while.

Yes. Because the spawns for the horde are based entirely on what your gamestage is. The only effect the day count has on it is when then event occurs.

As far as I am aware, this is in the client code. It's not something you will be able to edit easily. Well I look at it this way. In a survival game with tower defense mechanics, you simply don't build a sprawling base for fighting from. The default zone is 41x41 with the LCB in the center. I usually build my central base area no larger than 23x23, and then the outer area is for defense mechanics. Or I might have something large and nice, and then a separate base for fighting the horde from.

LCB does not block anything other than POI sleeper spawns. Bloodmoon zombies can spawn within 30 meters from your lateral position. The direction they come from will change during the night. Sounds like it's functioning as expected.

Then they have a log file.

Just be aware that by doing so, you have likely ruined the save. Probably would have been safer to nuke the main.ttp files, but neither is a good choice. Day count hasn't meant anything for several years now. If people are daunted by the count, they might want to spend some time doing research on why it doesn't matter.

Only issue I see is the drone spam. I think if you have players collect their drones, shut off the server, and then delete the drone files, that should take care of it.

Sounds like a sync issue. Instructions on posting logs are Pinned. If Pastebin doesn't work, use Justpaste.it. Or you can just host the file on Google or something.

Sounds unusual. Ours is sitting higher than it was on a19. With a19 we saw it maxing out at 40FPS, and our average was in the mid 30's. While it was running, it mostly used about 6 cores. In a20 server FPS is topping out at 50, and normal running is 42-45FPS. The server is also using all 24 cores available to some extent. We're bare metal with a pair of x5675's and 96GB RAM.

There is no option with the dedicated server generation to use the sliders that are available in the client. You make the map on your PC, and then upload it to the server. Most hosts allow this.

ERR [EOS] Native library or one of its dependencies not found (e.g. no Microsoft Visual C Redistributables 2022)

You need to use an Alpha 20 config file for Alpha 20. If it doesn't have all the options, you will have issues. You also have old mods installed.

it's called a heatmap. Activity generates "heat", and when you build up enough of it, it attracts a scout. If the scout finds something it calls a horde.

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.