V2.4 Stable

View attachment 36804
Hello Survivors!

Today we have a Stable patch that is required for connectivity. The compatibility for EOS versions <1.17.1.3 will expire on October 1st.
We also have some small fixes in this, but the planned content release will come with V2.5 instead of V2.4 now.

For Steam Windows users playing older versions of the game:
To reduce any connectivity issues, make sure Windows is up-to-date to maintain certificate compliance.

Have a great week!

Here's the V2.4 b5 changelog:

Fixed
  • Factory_02 "Shotgun Messiah Factory" quest can again be completed
  • Typo in progression.xml to correctly boost the loot probability of armor magazines with the medium and heavy armor skills
  • Launcher giving "1980-0-0 is not a valid date specification." error when there's SavesLocal folders without any files
  • Connecting to EAC enabled dedi sometimes fails with message size error on server
  • Breaking open a locked police car by driving a vehicle into it doesn't trigger the car alarm event. Also fixes other block game events in cases where a driven vehicle is the damaging entity
  • NRE with airdrop nav object icon.
  • NREs for clients who have connected to a server but not spawned and receive quest related net packages
  • PS5 fails to exit to the main menu due to process restart failure.
  • Steam build reflections are having a strobing effect which can worsen greatly under certain lighting conditions
  • Toggle sprint not turning off when entering or exiting a vehicle.
  • Allow 0 as well as 1 as valid LootRespawnDays value for crossplay servers
  • PS5: Water missing blue hue.
Except it is breaking servers with a tick error. :(
 
That's right. I outlined my proposal and ideas, and ChatGPT edited it, correcting errors and structuring it.
You won't find much interest in anything you post that comes from AI here. Half ends up being incorrect or already known to be either already in the game or else planned. People don't want to talk to AI. If you have your own ideas, it's better to post them yourself without ever going to AI. Structure isn't important here and real opinions rather than stuff from AI is paid more attention to. I didn't even bother reading it because it's from AI and you'll find that is true for a lot of people here.
 
just a question: it does not affect me as I am not playing right now, but, it's almost been a couple of weeks, what is being done to fix the tick? or are TFP waiting for 2.5 to patch it?
 
just a question: it does not affect me as I am not playing right now, but, it's almost been a couple of weeks, what is being done to fix the tick? or are TFP waiting for 2.5 to patch it?

Here is my Local Dedicated Server fix for the tick spam (your mileage may vary depending on your setup):

 
Here is my Local Dedicated Server fix for the tick spam (your mileage may vary depending on your setup):

thanks, I am sure peeps will be grateful.

still curious as to what the problem IS and when will it be addressed. If it's an EOS problem why did it start with the 2.4 update? and are they working with them to fix it? or did the update cause it and they will fix it soon(tm)?
 
thanks, I am sure peeps will be grateful.

still curious as to what the problem IS and when will it be addressed. If it's an EOS problem why did it start with the 2.4 update? and are they working with them to fix it? or did the update cause it and they will fix it soon(tm)?
Most spam like that is nothing more than debug text they add while working on the code and later remove. Sometimes things get missed and are still in there during experimental or even stable, as seen here. I don't know for sure if that's the case with this specific spam, but it's likely. It's usually a simple matter of deleting or commenting out the line that displays the text, but unless it's a serious issue, they aren't likely to put out a hotfix for something like that and it'll just be fixed in the next version.
 
Care to elaborate, or is it a State Secret?
My bad, I had to read the posts from the beginning. Then I found the post
that said it was a security update.

I was initially confused because I have not been updating, so I could spend
time modding, and painting. I did the update to the stable and at first I thought
something was wrong because I didn't see a patch notification.
 
Back
Top