updater owner console live site
Updater

Protect and publish your DLL.

Pick your build and the channel it belongs to. The Updater checks the file, hashes it, and pushes it live. Players on that channel get it the next time they launch.

  • Nothing is served in the clear. Each download is AES-256 encrypted for the requesting machine, so a captured response is not a runnable dll.
  • Your filename and entry point stay private. The public catalog never lists them; the loader trades an HWID for a 60 second token first.
  • One upload, every player. Publishing replaces the previous build for that channel immediately - there is no version to bump by hand.
mane_updater no channel
the letter in brackets is a shortcut · click a › line to select it

What the Updater checks before it publishes

File header
The first two bytes have to be MZ. A .dll that starts with anything else is a zip, a text file or a truncated download, and the loader would only fail on the player's machine.
SHA-256
Hashed in your browser before the upload and printed in full - hover the line to copy it from the title. The upload line then reports the byte count the server accepted, so a cut-short transfer shows up as a stalled percentage rather than a silent success.
Channel
The menu you picked, plus what players need to open it: free channels need only a machine id, paid channels need a key that binds to the first machine that redeems it.
What it does not do
It does not obfuscate, recompile or strip your build - the bytes you pick are the bytes players get, encrypted in transit. Test your dll in game before publishing it.