Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/stevensonhouset5-sys/Victor-Launcher/llms.txt

Use this file to discover all available pages before exploring further.

Shared packs let a host bundle multiple mods into a single downloadable pack and distribute them to players using a short room code. Players enter the code in Victor Launcher, which fetches the pack manifest, verifies its authenticity, and downloads each DLL directly into the install queue — no manual file sharing required.

​
Creating and publishing a room

A room stores your mod pack on the Victor Launcher web manager. Once published, anyone with the room code can download the exact set of DLLs you uploaded.
1

Open the web manager

Go to https://ateasvictor.github.io/Victor-Launcher/ in your browser.
2

Create a room

Give your room a name, a room code, and a password. The room code is what you share with players, so choose something short and memorable.Room code rules:
  • Alphanumeric characters, dashes (-), and underscores (_) only
  • Maximum 12 characters
  • Case-insensitive — Victor Launcher normalizes it to uppercase automatically
3

Upload your DLLs

Add the mod DLL files you want to include in the pack. The uploaded files form a draft of your room.
4

Publish the pack

Click Save Room Pack to publish the draft. The pack is now live and available to anyone who enters your room code.
5

Share the room code

Send the room code to your players. They can enter it in Victor Launcher to download the pack.
Published manifests have an expiry time (IssuedAtUtc + ExpiresAtUtc). Players must download the pack before it expires. Re-save the room to generate a fresh manifest if yours has expired.

​
What happens during a download

When you click Download Pack, Victor Launcher runs the following steps automatically:
  1. Sends the room code to the Supabase Edge Function at the room-manifest endpoint (falls back to the get_room_manifest RPC for legacy backends).
  2. Verifies the RSA/SHA-256 signature on the returned manifest.
  3. Checks that the manifest has not expired.
  4. Validates that every file URL belongs to the same host as the configured Supabase project.
  5. Downloads each DLL and checks its SHA-256 hash and file size against the values in the manifest.
  6. Saves each file to BepInEx/mod-imports/<ROOM-CODE>/ using the file name from the manifest.
If any check fails, the download is aborted and the Ship Status bar at the bottom of the launcher shows a warning message explaining what went wrong.

Build docs developers (and LLMs) love

Get started for freeTalk to us