gen.emu.sharp

A rewrite of the generate_emu_config tool by Mr.Goldberg in C#, credits to them for the original tool.

Changes

• Login credentials are retained for later login attempts inside the folder credentials/, avoiding the need to login each time the tool is used
• Generate all possbile schemas for Achievement Watcher by xan105
• Automatically find the IDs of top reviewers and use them to query for the stats/achievements schema
• Extend built-in owners IDs by adding them to a file called top_owners_ids.txt, each ID on a separate line
• Download various media assets for each app: backgrounds, icons, screenshots, inventory items images, ...

Example

• console.gen.emu.cfg

  console.gen.emu.cfg 420 730 227300 -v --icons --imgs --scrn --thumbs --vid --invicons --inviconslarge
  

• console.vdf.parser

  console.vdf.parser path/to/file_1.vdf path/to/file_2.vdf 
  

• console.stats.schema

  console.stats.schema path/to/UserGameStatsSchema_480.bin path/to/UserGameStatsSchema_730.bin
  

Help page

console.gen.emu.cfg --help

Building

All projects prefixed with console. are meant be executed as console apps.

dotnet clean
dotnet restore
dotnet build

Output will be inside: ./console.gen.emu.cfg/bin/Debug/<DOTNET_VERSION>/

Publishing and packaging a release binary

dotnet allows building a self-contained release binary for any OS, even for ones other than your current OS. These binaries are independent on dotnet runtime, so users do not need to install dotnet.

dotnet calls this process publishing but it has nothing to do with uploading the binaries to an online storage/host, or even using any form of credentials. Just a misleading name for a simple "release build".

The project has publishing profiles set-up and ready for use.

For Linux

dotnet publish /p:PublishProfile=linux-x64.pubxml

For Windows

dotnet publish /p:PublishProfile=win-x64.pubxml

Output will be inside ./console.gen.emu.cfg/bin/Release/publish/<OS_IDENTIFIER>/

Third-party credits

• SteamKit
• ValveKeyValue
• CommandLineParser