setup-resonite-env

Configures the resonite-io devcontainer environment, Gale mod profile, and Wine DLL overrides on Linux.

3|Updated Jun 7, 2026
One-click install
npx skills add https://github.com/MLShukai/ResoniteIO --skill setup-resonite-env-mlshukai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-resonite-env
Source: https://github.com/MLShukai/ResoniteIO/tree/main/.agents/skills/setup-resonite-env
Command: npx skills add https://github.com/MLShukai/ResoniteIO --skill setup-resonite-env-mlshukai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up the resonite-io development environment on a fresh clone involves many failure-prone steps: Docker/devcontainer configuration, GPU vendor detection, Gale mod profile creation, Wine DLL overrides, and AppArmor restrictions. This Skill consolidates the full checklist and explains the common pitfalls so mod-load failures can be diagnosed quickly. ## Core Features & Use Cases - Docker devcontainer setup: Guides just init, .env configuration with ResonitePath, and opening the devcontainer via VS Code, Zed, or @devcontainers/cli, with all .NET/uv/protoc tooling containerized. - Gale profile management: Explains creating a Gale profile at ./gale, importing the bundled GaleProfile.r2z snapshot or manually installing the six required mods, and validating with just check-gale. - Launch and troubleshooting: Covers WINEDLLOVERRIDES="winhttp=n,b" requirements for Steam Launch Options vs container auto-export, AppArmor kernel.apparmor_restrict_unprivileged_userns=0, UDS path constraints under pressure-vessel, and the just resonite-launch / just resonite-stop mod-load verification flow. - Use Case: After a fresh clone, run just init, open the devcontainer, deploy the mod with just deploy-mod, launch Resonite with just resonite-launch, and confirm Loading Plugin ResoniteIO appears in the BepInEx log. ## Quick Start Set up my resonite-io dev environment from this fresh clone, including the Gale profile and Steam launch options.

Frequently Asked Questions about setup-resonite-env

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up the resonite-io dev environment on a fresh clone?

Copy `.env.example` to `.env`, set `ResonitePath` to your Resonite executable directory, then run `just init` on the host. After that, reopen the repo in a devcontainer (VS Code, Zed, or `@devcontainers/cli`), which runs dependency resolution automatically.

How do I configure a Gale profile for Resonite modding?

Create a new Gale profile pointing at the repo's `./gale` directory, which must be empty beforehand. Import the bundled `GaleProfile.r2z` snapshot to install all required mods at once, then verify with `just check-gale`.

Why is my Resonite mod not loading after setup?

The most common cause is a missing `WINEDLLOVERRIDES="winhttp=n,b"` override, without which the Renderer-side BepInEx never starts. For Steam launches set it in Launch Options; container launches via `resoio launch` export it automatically.

Does resonite-io work on Windows or macOS hosts?

No, resonite-io targets Linux only, running Resonite through Steam Play (Proton) and communicating over a Unix Domain Socket. The devcontainer additionally requires an X11/Xwayland session, PipeWire or PulseAudio, and a supported GPU vendor.

Why does the devcontainer fail to start on Ubuntu 24.04?

Ubuntu 24.04 restricts unprivileged user namespaces via AppArmor, which pressure-vessel (Steam Linux Runtime) requires. Set `kernel.apparmor_restrict_unprivileged_userns=0` via sysctl, temporarily or persistently, before launching the container.