Viability of supporting a user's individual Steam library as a source?

[Leyton Houck (boxsitter)]

Looking at how many of my local packages are steam games, it got me wondering if those games could be given the same feature support as other packages.

Could a user's Steam library be supported as a source using SteamCMD (command-line version of the steam client) and the Steam web API? A user would have to sign into their Steam account but after that, I don't see any reason why UnitGet couldn't access their game library, information about each game from its store page, each game's current version, and manage installing, uninstalling, and updating. I could see it being tricky to pull and format the data for each game and treat it as a source but if that can be figured out, UniGet could cache it and update it every so often.

Steam games would need to be treated fundamentally different than other packages under the hood but besides needing to sign into their Steam accounts, core features should work the same for users. In the end, I think this would be a pretty big step towards minimizing the amount of software outside of UniGet's scope.

I would take a shot at implementing this myself but I don't think my C# is good enough to be helpful here. Even so, I wanted to see what y'all thought?

[Martí Climent (marticliment)]

I guess SteamCMD could be implemented as a package manager...