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.

Once Victor Launcher is installed and Among Us is running, you are a few button presses away from having your first mod active. This guide walks you through opening the launcher, queuing a mod for install, and restarting the game to apply changes.
Victor Launcher queues mod changes — it does not hot-swap DLL files while the game is running. You must restart Among Us after installing, enabling, or disabling any mod for the changes to take effect. The launcher reminds you of this with the label “Restart Among Us manually after mod changes” displayed next to the F7 hotkey indicator.

Installing your first mod

1

Open Victor Launcher

Launch Among Us and press F7 from any screen. The Victor Launcher overlay appears. The bottom of the overlay shows the Ship Status bar — confirm it reads Ship Status: Ready before proceeding.
2

Pick a DLL file

Click the Pick DLL button. A native Windows file picker opens. Navigate to the .dll file for the mod you want to install and select it.Victor Launcher only supports BepInEx-compatible DLL mods. Make sure the mod you are installing is distributed as a .dll and is designed for BepInEx IL2CPP.
3

Confirm the mod is queued

After selecting a file, Victor Launcher copies it into BepInEx/mod-imports/. This is the staging area — mods placed here are not yet active. You will see the mod appear in the Queued Folders section of the launcher overlay.The mod-imports/ folder acts as a safe holding area so you can review what will be installed before committing to a restart.
4

Install the queued mod

In the Queued Folders section, locate your staged mod. Click Open Folder to see the individual DLL, then click Install to move it from mod-imports/ into BepInEx/plugins/. Alternatively, click Install Folder on the group card to install all DLLs in that folder at once.A restart prompt appears after a successful install.
5

Restart Among Us

Click Close Now to exit immediately, or Later to close the game on your own. BepInEx loads all plugins in BepInEx/plugins/ on startup, including the one you just installed.
6

Verify the mod is active

After the game restarts, press F7 to open Victor Launcher again. Your newly installed mod should now appear in the Installed Folders section. The Ship Status bar confirms everything loaded correctly with Ship Status: Ready.
If a mod you just installed or enabled does not appear in the list, click Refresh Lists. This re-scans the plugins/, plugins-disabled/, and mod-imports/ directories and updates the overlay without requiring a restart.

Understanding the queue

When you pick a DLL, Victor Launcher places it in BepInEx/mod-imports/ rather than directly in BepInEx/plugins/. This staging step exists because Among Us loads all plugins at startup — a DLL added to plugins/ while the game is running cannot be loaded until the next launch. The queue makes the pending state visible so you always know what is waiting to be installed. To move a staged DLL from mod-imports/ into plugins/, you must click Install (for individual mods) or Install Folder (for a group) in the Queued Folders section. Victor Launcher does not automatically install staged files when the game restarts — you always review and approve what gets installed first. The same pattern applies when you disable a mod: Victor Launcher moves it from plugins/ to plugins-disabled/ immediately, but the game continues running the old in-memory version until you restart.

Checking Ship Status

The Ship Status indicator at the bottom of the overlay is your primary feedback channel. It shows one of two states:
StatusMeaning
Ship Status: ReadyEverything loaded correctly and no action is required
Ship Status: WarningAn error occurred — read the message shown next to the status label for details
Error messages appear near the bottom of the menu next to the Ship Status indicator. If you see a warning, read the message to understand what went wrong before making further changes.

Build docs developers (and LLMs) love