Pramochak
A Minecraft studio that launches in one click.
Why it exists
01Minecraft on a laptop is a pile of folders: versions, mods, resource packs, skins and saves. Keeping that pile straight across launchers and updates is the least fun part of playing.
Pramochak puts the pile in one window. Pick an instance, switch mods on or off, change a skin, press launch. The point was to remove the folder archaeology, not to add another dashboard.
Recorded 2025—2026
Kaushambi, India
The constraints
02- 01No official launcher API — the studio has to work with the same files the game already reads.
- 02A mid-range Windows laptop with no dedicated GPU; the shell has to stay light.
- 03Tauri v2 with a Rust backend, so file scans and process launches do not block the interface.
- 04Mods and skins are user files. Nothing should be moved or overwritten without saying so.
The approach
03One window, three rooms
Home, Mods and Skins share a single shell, and the launch control never leaves the screen. Tabs change the work surface, not the context.
Filesystem work belongs in Rust
Scanning instances, reading mod metadata and writing configuration happen in Rust commands. The React layer only renders the result, so opening a large mod folder does not freeze the window.
Show the path before touching it
Every instance and mod is shown with its real name and location. Toggles are explicit, and the studio never silently downloads or replaces a file.
What it actually does
04- 01Instance list with version labels and a one-click launch.
- 02Mod manager with per-mod toggles and file names.
- 03Local skin library with a preview of the selected skin.
- 04Shortcuts to the instance folder, logs and screenshots.
- 05Light and dark interface inside the same shell.
Technical notes
05The desktop shell is Tauri v2. React renders the studio; Rust commands walk the instance directory, parse mod metadata and spawn the Java process with the selected classpath and arguments.
The exit code and stdout of the game process are captured so a failed launch leaves a readable log instead of a window that closes. The hardest part was path handling across spaces and non-ASCII folder names.
- Role
- Product, desktop shell, filesystem and process integration
- Year
- 2025—2026
- Platform
- Windows
- Stack
- Tauri, Rust, React, TypeScript
- Status
- v2.0 · shipped
Honest limits
06- 01Windows build only; there is no macOS or Linux package yet.
- 02Mod conflict detection is manual — the studio shows files, not compatibility verdicts.
- 03Skins are local files; there is no online skin catalogue.
- 04No automatic updater, so new versions are installed by hand.
What it taught me
07“A launcher is mostly file I/O and process management. The interface is the easy part; the trust is in what the app does to your folders when you press launch.”