explaingit

minotaursofoundry/creaminstaller

28Audience · generalComplexity · 1/5Setup · easy

TLDR

A portable Windows tool that scans Steam, Epic Games Store, and Ubisoft Connect to detect installed games and generate DLC-related configuration files, with no manual path entry required.

Mindmap

mindmap
  root((repo))
    What it does
      Scans gaming platforms
      Detects installed games
      Generates config files
    Platforms
      Steam
      Epic Games Store
      Ubisoft Connect
    Setup
      Portable executable
      .NET 7 runtime
      No installation
    Audience
      PC gamers
      Windows users
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Automatically scan all your Steam, Epic, and Ubisoft games to detect installed titles and their directories.

USE CASE 2

Generate DLC configuration files for your installed games without manually entering any file paths.

USE CASE 3

Run a cached scan of your gaming platforms to quickly review detected game and DLC data.

Tech stack

.NET

Getting it running

Difficulty · easy Time to first run · 5min

Requires .NET 7 runtime on Windows, runs as a portable executable with no installation step.

No license information is provided in this repository.

In plain English

CreamInstaller is a Windows desktop tool that scans gaming platforms, specifically Steam, Epic Games Store, and Ubisoft Connect, and generates configuration files related to downloadable content (DLC). The application detects installed games and their directories automatically, without requiring manual path entry, and caches scan results to speed up repeated runs. The README describes the tool as focused on organizing DLC information and preparing configuration files, and states that it does not include or distribute actual DLC content. It runs as a portable executable with no installation step and requires the .NET 7 runtime. Users select which platforms to scan, wait for the scan to complete, review the detected data, and confirm changes. The README is sparse on technical details and does not explain how the configuration files are structured or what software reads them. The tool is associated with CreamAPI, KoalaAPI, and SmokeAPI based on its topic tags, which are names commonly associated with DLC bypass patches for PC games.

Copy-paste prompts

Prompt 1
I want to use CreamInstaller to scan my Steam library, what are the steps to run it on Windows and what does the generated config file look like?
Prompt 2
CreamInstaller requires .NET 7, how do I check if I have it installed and where do I download it if I don't?
Prompt 3
What is CreamAPI and how does CreamInstaller's generated config file relate to it?
Open on GitHub → Explain another repo

← minotaursofoundry on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.