If you save a blueprint on Windows with UTF-8 with BOM encoding, anyone who will use it on Linux won't be able to import it, causing Invalid version:'(' exception.
More info in this Github thread: https://github.com/Xeinaemm/Factorio-Ti ... /issues/20
[2.0.69] UTF-8 with BOM encoding causes blueprint import exception on Linux
Re: [2.0.69] UTF-8 with BOM encoding causes blueprint import exception on Linux
Thanks for the report however I am unable to reproduce it working *at all* when with a BOM in the drag-and-drop scenario. I get the exact same error on my machine when I try to use any blueprint string file with a BOM - it's simply an invalid file format.
When I copy-paste the contents onto the clipboard and them attempt to paste them into the game - Windows has already stripped the BOM from the clipboard contents making it a valid string for the game to paste and import.
In both cases - the game only ever accepts a no-BOM string.
Is there something I missed in trying to reproduce it?
When I copy-paste the contents onto the clipboard and them attempt to paste them into the game - Windows has already stripped the BOM from the clipboard contents making it a valid string for the game to paste and import.
In both cases - the game only ever accepts a no-BOM string.
Is there something I missed in trying to reproduce it?
If you want to get ahold of me I'm almost always on Discord.
Re: [2.0.69] UTF-8 with BOM encoding causes blueprint import exception on Linux
I've changed the drag-and-drop file logic for 2.1 so it will ignore the BOM. If there's another case, please let me know.
If you want to get ahold of me I'm almost always on Discord.
Re: [2.0.69] UTF-8 with BOM encoding causes blueprint import exception on Linux
I believe you handled it flawlessly. I'll redirect everyone to this thread if they find anything more.