by Korell » Sun Sep 02, 2018 1:39 pm
I've no idea if this should be posted here or not as it is a bug (in fact, would this even be considered a bug?) that I've noticed only with the development builds. It affects g3.6pre-56-g55d1613ea and g3.6pre-57-g2d1043d1d (I've only used the 64-bit versions though, so I don't know if the 32-bit versions are also affected). These are the two development builds released in September so far.
Basically, when you run the game with one of these two development builds the config file is updated so that the line breaks use LF (line feed) only, rather than CRLF (carriage return + line feed). This means that when opening them in Notepad in Windows they are just one huge mass of text. Other text editors, such as Notepad++, however, are able to display them fine. Rolling back to g3.6pre-50-g050d72724 and then re-running the game restores the carriage returns to the config file so that it becomes easily readable within Notepad again.
I've no idea if this should be posted here or not as it is a bug (in fact, would this even be considered a bug?) that I've noticed only with the development builds. It affects g3.6pre-56-g55d1613ea and g3.6pre-57-g2d1043d1d (I've only used the 64-bit versions though, so I don't know if the 32-bit versions are also affected). These are the two development builds released in September so far.
Basically, when you run the game with one of these two development builds the config file is updated so that the line breaks use LF (line feed) only, rather than CRLF (carriage return + line feed). This means that when opening them in Notepad in Windows they are just one huge mass of text. Other text editors, such as Notepad++, however, are able to display them fine. Rolling back to g3.6pre-50-g050d72724 and then re-running the game restores the carriage returns to the config file so that it becomes easily readable within Notepad again.