Quickstart Guide - NexusLaunch Docs
One Launcher. Infinite Worlds. Configure headless environments and custom asset paths in under five minutes.
Prerequisites & Environment Setup
This guide targets studio administrators and power users deploying NexusLaunch across multiple workstations. Ensure your target machines run Windows 10/11 (21H2+) or Ubuntu 22.04 LTS with at least 16GB of RAM and .NET 8.0 runtime pre-installed.
The latest stable binary (v4.2.1) includes the updated Vulkan 1.3 loader and direct storage optimization for NVMe arrays. Download the headless package from the official artifact registry, then extract the `nexus-cli` executable to your system PATH before proceeding to silent installation.
Terminal Commands & Silent Installation
Bypass the interactive installer using the `--silent` flag. Combine it with `--accept-eula` and `--skip-desktop-shortcut` for clean, unattended deployments via SCCM, Intune, or Ansible playbooks.
Standard Silent Deploy
nexus-cli install --silent --accept-eula --target "C:\Nexus\Launcher" --no-restart
Force Background Daemon
nexus-cli service register --headless --auto-update "nightly" --log-level "warn"
Verify Installation
nexus-cli status --check-permissions --validate-integrity --output json
JSON Configuration & Custom Library Paths
Redirect game assets, mod caches, and shader compilations away from the OS drive. Drop a `nexus.config.json` file into `%APPDATA%\NexusLaunch\config\` to override defaults before the first daemon boot.
Primary Library Override
{"libraryRoot": "D:\GameAssets\NexusLibrary", "fallbackPath": "Z:\Backup\Nexus", "allowSymlinks": true, "maxConcurrentDownloads": 12}
Mod & Asset Directories
{"modStaging": "C:\NexusMods\Staging", "assetCache": "E:\RenderCache", "shaderPrecompile": true, "verifyChecksums": true}
Network & CDN Preferences
{"cdnRegion": "us-east-2", "mirrorFallback": "cdn.nexuslaunch.io/backup", "bandwidthLimit": "50MB/s", "enableIPv6": false}
Run `nexus-cli validate --config nexus.config.json` to confirm path permissions and schema compliance. The daemon will automatically mount the specified directories and begin background indexing within 45 seconds of service startup.