From download to your first armed module.
Everything Dusk does on a first run, in the order it happens. Nothing installs, nothing registers, nothing signs you in, which is why this page is short.
-
Download one file
Grab Dusk.exe and put it in a folder you can write to, because it updates itself in place. Anywhere under your user folder works; Program Files does not.
Windows will warn you the first time you run it, for two reasons the download page explains in full, along with how to verify the file against its published SHA-256.
-
Run it
Double-click the exe. The menu opens straight away: it never waits for Minecraft, so you can configure everything before the game exists. On the very first launch Dusk asks one question, Simple or Advanced, which decides how many knobs each panel shows. You can change your mind any time.
Dusk needs the .NET 10 Desktop Runtime and the Edge WebView2 Runtime. If WebView2 is missing, Dusk notices on launch and links you to the installer instead of failing quietly.
-
Start Minecraft whenever you like
Launch 1.8.9 on any client, before or after Dusk, in either order. Dusk finds the game in the background and the sidebar status line walks through it plainly: waiting for a client, attached, in game. If several instances are running, Dusk asks which one you mean.
-
Arm a module
Every module page has one master card at the top holding its enable switch and its hotkey. That switch is the only place a module turns on, so there is never a second state to hunt for, and the sidebar shows a green dot beside everything currently armed.
Ctrl K searches every module and every individual setting by name, which is faster than the sidebar once you know what you want.
-
Play
The overlay draws over the game, the menu stays out of your way, and everything you change applies live: there is no Save button anywhere, because the active config tracks your edits as you make them. If a moment ever calls for it, the panic key turns everything off in one press, and its deeper tiers also hide the menu or shut Dusk down entirely.
-
Let it keep itself current
On launch Dusk checks for a newer build, verifies it against a SHA-256 before touching anything, then swaps its own exe and relaunches. No network, no update, no nagging: if the check cannot reach the channel it does nothing and says nothing.
-
Leave nothing behind, if you go
Uninstalling is deleting two things: the exe, and the folder below. There is no installer entry, no service, no registry footprint to clean up, and nothing in your .minecraft folder, because nothing was ever put there.
WebView2 keeps a small cache in your temp directory, cleared like any other temp files.
Where everything lives
One folder, under your local app data. Settings, configs and the log all sit in it, and deleting it resets Dusk completely.
- settings.jsonevery setting, one document
- configs\your named profiles
- dusk.loglocal only, paths stripped
Your game's folder stays exactly as it was: compare your jar's hash before and after, and look in your mods folder and your launcher profile.