Created
February 3, 2019 20:40
-
-
Save therealbill/336e1686eb466129e565eb91d595c243 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In Terminal go to "~/Library/Application Support/Steam/steamapps/workshop/content/281990/". From there you'll need to identify the mod you want to modify by looking in "~/Documents/Paradox Interactive/Stellaris/mod" files. I look through them in Finder using preview. Get the "remote_file_id" value and go to the subdirectory in Terminal. | |
Then unzip the zipfle using 'unzip FILENAME' where FILENAME is the name of the zipfile there, ending in ".zip". Next you need to determine the localisation directory. Some mods use a subdirectory of "localisation/LANGUAGE/" some just put them in localisation. For this example, I'll assume "localisation/english/". The files in there need to have their BOM added. | |
So from the mod's directory (where the zipfile is) enter this in Terminal: | |
========== | |
for f in $(ls localisation/english/*.yml); do echo $f | |
cp $f $f.sav | |
sed -i .presed '1s/^/\\xef\\xbb\\xbf/' $f | |
done | |
zip -u ZIPFILENAME localisation/english/*.yml | |
========== | |
That will add the BOM to each of the files and update the archive. Then you need to start Stellaris fresh from steam and if that was the mod w/the problem it should now load, though you'll now see the error log claim those files don't have the BOM. -.- So I suspect it is in their localization code, perhaps not detecting BOM correctly. | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment