Cirosan Posted May 4, 2016 Share Posted May 4, 2016 I made a post about this on the Bethsoft forums, but the thread has kinda gotten bogged down in arguments - and besides, I figure the more people I ask, the better. I'd also like to stress that I'm not planning on removing FDI from the Nexus or anything, I'm just trying to prepare for console ports, and getting stuff to work on the Bethesda platform is part of that. Anyways, I'm preparing to release FDI on the Bethesda site, but I've hit a snag I can't seem to get around: .strings files, even when included in an archive with an uploaded mod, do not override the .strings files in the Strings folder. Meaning that even if changes are made to .strings files in the archive, it doesn't amount to a thing because the game appears to prioritize the contents of the Strings folder. In any other circumstance this wouldn't be a problem - just put altered .strings in the folder directly - but on the Bethesda platform that obviously isn't an option. I've taken a look at other mods available on this platform that alter strings of text, but all those alterations seem to be hard-baked into the related .esp rather than using a .strings file. Is there any way to force the .strings files in a BA2 archive to override those in the Strings folder, as everything else in an archive seems to behave? Link to comment Share on other sites More sharing options...
mcguffin Posted May 4, 2016 Share Posted May 4, 2016 No: loose files always win over archives, and even if there was an unknown setting, it will be stored in ini configs files and I don't think you will have access to them either. Link to comment Share on other sites More sharing options...
registrator2000 Posted May 5, 2016 Share Posted May 5, 2016 Right now it does seem like you're out of luck - loose files always take precedence over those in archives. However, if your intention for the version on Beth.net is for consoles, you might want to hold out still - who's to say that console versions will have the same folder structure as PC? Perhaps consoles have their strings in archive format as well - only way to find out is to test it out when Beth actually opens up their platform for consoles. @mcguffin - I've only recently found out that it *is* possible to have INI settings packaged with a mod! Any *.ini file in the root Data folder with the right syntax (can be in BA2 archives) will be recognized and have its effects merged with the main Fallout4.ini file. Link to comment Share on other sites More sharing options...
Cirosan Posted May 5, 2016 Author Share Posted May 5, 2016 @registrator2000 - Would you mind sharing this method of packaging .ini files to be written? Could come in handy in the future, even if this particular .strings problem doesn't work out. Barring that, I'm inclined to agree with mcguffin and say that there's no way to do it, currently. If worse comes to worst, however, I can always bake the text changes directly in the .esp and override the topic names. It'll be messy and a compatibility nightmare, but it's better than nothing. Still a chance the consoles might have a different file structure, though. Link to comment Share on other sites More sharing options...
Deleted15964729User Posted May 5, 2016 Share Posted May 5, 2016 CirosanRegarding the inifiles, spring cleaning does that to incorporate the sprint fix. I think format is mymod.esp=mymod.ini Edit: Damn phone. Link to comment Share on other sites More sharing options...
registrator2000 Posted May 7, 2016 Share Posted May 7, 2016 @Cirosan According to foreverasir on the Beth forums (https://community.bethesda.net/thread/11036), just place them in the Data root directory with your ini setting and the right section header, formatted according to Fallout4.ini's structure. Link to comment Share on other sites More sharing options...
Recommended Posts