Page 1 of 1

Meta data missing from main exe on Windows

Posted: Fri Mar 02, 2018 1:02 am
by PIE15
Hi Subset folks :)
I have a sort of a semi request come recommendation and I will get to why in a sec:
Please add meta data to the main application exe and keep the version number meta data up to date every time a game update is released.
Here is a picture of FTL's for clarity: https://imgur.com/a/CRxE2

The reasons I have are as follows:

    Slipstream mod manager really needs to know about major updates so that it knows when to refresh it's backup of the game's resource files. Looking at the meta data is a way I think it could be done. Without the version data, it currently cannot be done.
    Meta data helps anti virus developers create their application signature entries in their application signature databases. So adding the meta data _should_ in turn lower the risk of false positives from an antivirus program - it's frustrating for users to have to work around the safety measures they have installed when they just want to get on and play the game.
    You guys really should stamp your copyright on that exe. You guys have worked damn hard on it and the copyright entry is not only an advert for the studio but also a declaration that you made this game and that in the eyes of the law, you are protected against unauthorised use (whether you choose to persue that or not.)

Take it with a pinch of salt if it seems arbitrary to add this. It's just something I observed. Gratz on the release btw. The new game (ITB) looks addicting. :shock:

Re: Meta data missing from main exe on Windows

Posted: Fri Mar 02, 2018 8:04 am
by 4n4
Also, updating the changelog on your own forum and website first would have made a lot more sense than just dropping it in a reddit thread and calling it good.
http://subsetgames.com/ftl_changelog.html

Re: Meta data missing from main exe on Windows

Posted: Fri Mar 02, 2018 8:10 am
by Vhati
Warning: Platforms vary.

On Windows, metadata can be embedded inside an exe.

On Linux, FTL's got a basic launch script that, in turn, points to 32/64 bit binaries. I don't know if there's even a place for metadata.

On OSX, I don't remember what the true executable is, but everything's inside bundle dir with metadata in an xml plist.


Regarding Slipstream merely noticing version changes (timing, not the version string itself)...

Locating and caching an MD5 of the appropriate binary executable would be inelegant but not as inelegant as the mess probing for metadata the proper way for each platform would entail.

On Steam, there's a file ("Steam/steamapps/appmanifest_212680.acf") with a numeric "buildid" field, also a "LastUpdated" timestamp field. Dunno how stable Steam's internals are to rely on. That might alleviate the primary complaint: Steam betas. Standalone players would know when they run an installer.