BlackMageJ: I've been trying to get Galaxy to launch a few games via source ports rather than DOSbox. Previously, I've been able to do this by editing the game's .info file, but lately it seems that if I make any changes to those files, the game in question vanishes from Galaxy, and doesn't get picked up on a folder scan unless I restore the original .info
Now, .info editing has been suggested on these forums by blues in the past, which suggests it's a supported trick, but it looks as if Galaxy is now checking for and rejecting anything with a modified file. Is this actually the case, or am I just getting things wrong and breaking them?
It's not possible to say with certainty what is causing the issue for you, but the goggame*.info files are very much editable. Being JSON data however the file syntax is extremely strict and any errors found cause the file to be considered corrupted and will be ignored or blown away.
It is absolutely crucial if editing these files that the syntax is strictly adhered to with absolutely no syntax errors in order for them to work properly. This is just the nature of JSON files and their parsers by design. When the beta program was running (is it still? There was never any formal announcement of it closing... ), we often had to edit these files in order to try to find workarounds for games that were not launching properly etc., and details would be communicated here in the forums on how to workaround problems for various games.
In addition to this, it is possible to create your own custom .info files for launching other games from other platforms or just about anything, so long as the syntax is correct and Galaxy will gladly load them. There is a 3rd party program available for creating shortcuts for off-platform games from what I understand (never used it myself).
So if you're modifying or creating your own .info file and it is being ignored or deleted by Galaxy, then there is a high degree of likelihood that syntax errors such as a missing or extraneous comma are present in the file (a common mistake), or some other similar typo or bad syntax. We were trained to ALWAYS pass the *.info file that we modified through an online JSON lint checker and make any corrections before trying to have Galaxy read the files in order to avoid problems from unintentionally corrupted files.
That'd be my recommendation today, to pass the JSON files through an online JSON checker first to ensure they are syntactically correct.