As per 1.3 release notes (a bit ligh on details, but enough to go on) So I copied the loading screens folder into my Scenario removed all but the 1st 3 of the jpegs truncated the notes.xt file to jsut 3 lines to correspond lpsUseSpotlights lpsBeWellPrepared lpsFindGoodSpot And the game just loads the vanilla scenario loader shots and phrases? Whaaa? Is there a verbose logging option that I can turn on to yield a bit more detail as to what I silently got wrong here?
They need to go into your scenario's SharedData folder. See project Eden's SharedData folder for an example (I'm not at home at the moment).
Sweet. The release note one-liner documentation never tied in the random "shareddata" folder workings in my reading of it. Thanks I should figure this out from here. I can write it up once I do.
Partly. My "loader" screenshots now appear, but the notes.txt file is not really working, it cannot find the strings. I notice Eden has a config.ecf called Eden_config.ecf and a localization.csv also prefixed in the same way , can anyone fill us in on the glue that ties these files in? I copied the strings in my 'Loading screens' Notes.txt file into a CSV called it 'Craftable Epics_Localization.csv' , but it does not appear to load the strings? Turns out the file must be simply named C:\SteamLibrary\steamapps\common\Empyrion - Galactic Survival\Content\Scenarios\Craftable Epics__2337746040\Extras\Localization.csv not scenario-name_Localization.csv . Sweet.
Sounds like you got it! The Eden_ config files are there so that Eden can be more easily merged with other scenarios such as Reforged Galaxy by just attaching the eden file to the end of the main config file. They do nothing by themselves, they are just for reference, and they are only used for some of the configs. You won't need anything like that.
Thanks Ravien. When it suddenly started working for me I eventually twigged that the eden_xxx file was just a temporary file. I'm pushing into a github repo ,which makes some of this easier to merge. Figuring out a workflow and enough rules to make this automate-able, but still have a lot to learn. The folder structure will eventually make sense to me I hope.