I always unsub and then resub every update just to make sure Steam actually downloads the update like it is supposed to, something weird was going on though since I had to do that 3 times before Random showed up as an option, I just put it down to Steam being Steam

@the_elder_sign Random start is in here as of Aug 17. If your copy doesn't have it, unsubscribe, wait til it completes, subscribe again, and that should force Steam to re-download the latest version of the scenario. If you host it on a server, you'll need to stop the server, upload the new scenario files, and if your server uses the SharedData download method, create a new .zip of the SharedData folder and update your dedicated.yaml file as needed (to avoid caching you may need to either change the URL or add a date parameter like &date=2025-09-08 to the end)

Any chance we can get the new random start added to the scenario?

Hi all, I just wiped my server which runs this scenario after implementing Build 34. If anyone would like to join, the server should appear in your list as "Space Cowboys RE2 Cust Less Grind +CPU+M/V NA West" or if you have to enter a server address manually it will be 23.17.179.54:30010 but the IP address changes

No worries Red. I tried a few more things and ended up just chalking it up to a coincidental save corruption. Bummed about losing the progress, but I started the save over again. Thanks again for your extra effort to try to solve it for me. Huge fan of your updates to RE2 that tweaks a lot of my dislikes with the original. Keep up the great work.

Sorry that I wasn't able to figure out a solution to your issue. The changed scenario name and the copying of the scenario files thing that I recommended doesn't actually seem to be relevant when it involves a scenario from the workshop. I don't know what caused it, but I have to conclude that somehow your actual save file got corrupted :(

Sadly I just did the game file verification already before I started posting here. I also unsubbed/resubbed to your MOD and loaded it again to insure it redownloaded the latest copy. I just joined your Discord und the same name here.

The yellow text is usually just warnings, but the red text error message leads me to believe that you may have a partially downloaded (or corrupt) BlocksConfig.ecf file in whatever scenario is being loaded by your save. Since you said you've been having the issue for a few days and I only updated the scenario today, you should probably try verifying the integrity of your game files. I find that many times when there's a core game update, like their recent update from 1.12 to 1.13, I often have do this or weird stuff like this starts happening.

If that doesn't work, add me on Steam friends or join our Discord (link is above in the scenario description) and maybe I can take a look at it via screenshots or screensharing or something.

Comes up in yellow complaining about a 'WeaponCVHeavyVulcanT2" not found in block groups ecf file in "HeavyWeaponsLarge" and says skipping. Then in red, it states...

"System.Exception: Unknown block name "HeavyWindowFBottomInvSmall" in action! ECF file syntax error: level max value to this alert level max value (0-20, 21-80...
NullReferenceException: Object reference not set to an instance of an object

It gives you the Continue or Quit error popup while loading the savegame and then stops loading? If you hit the ~ key can you see any notable error messages in red text?

It's not showing me any error at the load screen and shows it should be in the 1.13 folder. Everything looks normal from there. It just gives me the internal error when I attempt to load the save. I copied the workshop folder to my scenario folder and renamed it to 1.12 as you instructed and it gives the same error when I try to start the save again after a complete shutdown and restart of the Emp client.

If you have to move or rename the scenario, you can actually keep the game running, every time you reopen the Load Game screen it should re-check the scenarios folder, and if it finds the scenario, it should stop giving that "The following savegames are no longer usable ... please delete them" error message.

If you have some other issue, like an error part way through loading the save, you have to check the newest game log file to see what the error message is. The current Logs folder is "\Steam\steamapps\common\Empyrion - Galactic Survival\Logs\4795\"

Basically what seems to happen is if the scenario is renamed, the savegame references the old name, and it will think that the scenario files disappeared and you wil lget an error in the Load Game list essentially telling you that the savegame no longer works. It will say something like "The following savegames are no longer usable ... please delete them". If you see a savegame that it says is no longer usable in the list, in the Location column for that savegame it will say the exact name of the scenario in brackets (in this case "Space Cowboys Reforged Eden 2 Beta 1.12"). If you can copy the scenario to a subfolder of your "\Steam\steamapps\common\Empyrion - Galactic Survival\Content\Scenarios\" folder and rename the copy to that exact scenario name, it should work. If it's off by even one letter or symbol it will not match up and it will give the same error.

This is not working either. I've actually been trying for 2 days to get my custom scenarios to work offline using these same directions to copy the workshop folders to the scenario folders to no avail. It seems this option no longer works.

Sorry about that, it's because I renamed it from 1.12 to say 1.13. I really need to remove the game version from the scenario name to prevent this. If you can brows your steam files, you can find the scenario at "Steam\steamapps\workshop\content\383120\3368926920"

Copy that whole folder into "\Steam\steamapps\common\Empyrion - Galactic Survival\Content\Scenarios\" and rename it "Space Cowboys Reforged Eden 2 Beta 1.12" and that should resolve the error.

Since this update an hour ago, I'm getting an "internal error" when trying to load my save that worked fine last night when I last played it on the 1.13 client.

@Chacal It's now updated, and seems to be working in a new single player game. You may need to unsubscribe and resubscribe to force the game to re-download it. Let me know if there are any issues as this was a big update and I did not do extremely thorough testing.

Thanks

@Chacal I'll be working on it soon, but this one may take a few days. RE2 released their v1.13 update 12 hours ago, but I think the RE2 v1.13 update does not add v1.13 vanilla game content. This update is mostly big changes to the galaxy map for the new jump gates feature, however galaxy map changes will not affect existing games. So if you're already playing an RE2 game don't be too worried about this update, you should be able to finish off that existing game just fine without it.

please will the update to v1.13 be released?

Single player, will try that. Thanks.

@Sol In singleplayer or multiplayer? If multiplayer it could be a server sync issue, and most of those are fixed by restarting the game. If singleplayer, I'm not sure why that could be, there have been no RE2 updates since April, so nothing has changed here either. You may want to try an integrity check of the game files, as the base game seems to have weird file problems from time to time when the base game has an update.

Ai Appears to be borked, critters and npcs do not move

@Gurra Whoops! Actually I changed that back to 2 in a recent update, as I increased the Quantum Extenders instead. Apparently my description is out of date.

Think something happend in latest update.
"CV Superior Extenders: Increase max from 2 to 4" That dont work for me can just put 2 as normal!

I like this version for Re2 singel play very much, the QOL changes is nice.
Great edits @RedScourge

@Skotty If you know how to modify the files, you can re-enable Omicron in Sectors\Sectors.yaml on line 211 by changing Starter_Omicron_V2,'' to Starter_Omicron_V2,'Human:1'

Omicron is my favourite starter. Bit of a deal breaker I'm afraid.

I CRAFTED BANDAGES AND OINTMENT IN THE CONSTRUCTOR AND ON ME AND IT DID NOT LET ME FINISH THE REQUIREMENT?