Posted October 27, 2021
Things are taking longer than I thought they would with ESC, as coming to grips with Legendary is proving to be quite challenging. And it is all too easy to make presumptions about command-line parameters.
For instance, you can DOWNLOAD a game or DOWNLOAD & INSTALL a game. The difference between those two appears to be minimal, except if you don't do DOWNLOAD & INSTALL you cannot verify. So not unreasonably, I initially thought there would be a significant difference between the two download options, with just DOWNLOAD being somewhat akin to an offline installer. But no, the files are the same, resulting in a download and decompression (extraction perhaps) to the game folder. Checking the Windows uninstall entries, there is no Registry entry for uninstalling a game when DOWNLOAD & INSTALL was used, so it appears that install only means an entry in an Epic database or manifest.
Legendary uses the manifest, and I am yet to find any way to directly access it or even know where it is. I can retrieve some info from it, and I guess interact with it to some degree.
It is now clear that I need to cater for more of the things Legendary does ... or give less options, foregoing things like Install, Verify and Update ... including dealing with DLCs.
Going into this, I had no intention to develop a frontend for Legendary. I just wanted to do a few basics, like what SteamCMD does for Steam games. But then maybe I should be doing more with SteamCMD.
Part of the challenge is knowing exactly how much to support. Especially as my program ESC is focused more on the idea of backing up DRM-Free games ... or should be.
I am also trying to keep things as simple as possible. That perhaps, is the biggest challenge of all.
It is now looking like I will need to do add one or more program windows (popups) ... at least for downloading and any other related processes anyway (Install, Uninstall, Verify, Update, DLCs, etc).
Another challenge is giving enough feedback to user, while my program remains in control.
For instance, you can DOWNLOAD a game or DOWNLOAD & INSTALL a game. The difference between those two appears to be minimal, except if you don't do DOWNLOAD & INSTALL you cannot verify. So not unreasonably, I initially thought there would be a significant difference between the two download options, with just DOWNLOAD being somewhat akin to an offline installer. But no, the files are the same, resulting in a download and decompression (extraction perhaps) to the game folder. Checking the Windows uninstall entries, there is no Registry entry for uninstalling a game when DOWNLOAD & INSTALL was used, so it appears that install only means an entry in an Epic database or manifest.
Legendary uses the manifest, and I am yet to find any way to directly access it or even know where it is. I can retrieve some info from it, and I guess interact with it to some degree.
It is now clear that I need to cater for more of the things Legendary does ... or give less options, foregoing things like Install, Verify and Update ... including dealing with DLCs.
Going into this, I had no intention to develop a frontend for Legendary. I just wanted to do a few basics, like what SteamCMD does for Steam games. But then maybe I should be doing more with SteamCMD.
Part of the challenge is knowing exactly how much to support. Especially as my program ESC is focused more on the idea of backing up DRM-Free games ... or should be.
I am also trying to keep things as simple as possible. That perhaps, is the biggest challenge of all.
It is now looking like I will need to do add one or more program windows (popups) ... at least for downloading and any other related processes anyway (Install, Uninstall, Verify, Update, DLCs, etc).
Another challenge is giving enough feedback to user, while my program remains in control.