FAQ
Answers to the questions people usually ask before trying the mod or companion.
Do I need the companion?
The mod can be installed manually and controlled through ws_* console commands, but the companion is the supported path. It handles setup, launch mode, local library browsing, keybind settings, publish, install links, and the overlay.
Does the mod send telemetry?
No. The Lua mod has no network code. The companion contacts windrose.build only for explicit account, browse, publish, install, and update flows. The Discord support button opens the public invite in your browser only when clicked.
What does Steam sign-in track?
Steam sign-in is used for creator credit, publishing, companion pairing, supporter status, and moderation. windrose.build stores your Steam64 id, Steam display name, Steam avatar, site username, profile fields, account tier, companion access, and last sign-in time. It does not receive your Steam password, inventory, friends list, game library, playtime, or Steam payment details.
Does capture interfere with left click?
It does not need to. Capture runs through the build menu instead of shovel clicks, so left click stays native everywhere. Mark corners with E, remove the last with R, and confirm with T.
Why do settings require a restart?
UE4SS keybind registration happens at boot, and this build has no safe unregister or hot-rebind path. The companion writes state\keybinds.json, then the mod applies it during the next launch.
Can I publish private builds?
Yes. Publish from the companion and choose public or private visibility. Public builds appear in browse and profile surfaces; private builds stay owner-scoped.
What happens if a game update changes assets?
Reflection calls are guarded in the Lua mod so missing classes or changed properties show up as log lines instead of crashes. Capture and paste coverage may still need follow-up work after a game patch.