Skip to main content
There are two ways to use SkyNET V3:
  • Public — invite Beta Core’s hosted bot (easiest)
  • Self-Host — run the binary yourself against your own Fluxer instance

​
Public SkyNET

  1. Use the invite on the Introduction page (or invite from skynet.beta-core.net).
  2. Give the bot Administrator, or make sure its role can manage what you need.
  3. Place the SkyNET role above the roles it should manage.
  4. Try !help (or your server’s custom prefix — see Commands).
The public Dashboard is available for the hosted bot. Full command list: skynet.beta-core.net/commands.

​
Self-Host

Self-hosting is for people running their own Fluxer. Most communities should invite the public bot instead. You will need:
  • A Fluxer bot application + token on your instance
  • A MySQL server SkyNET can reach
  • A Windows x64 or Linux x64 host
Downloads: skynet.beta-core.net/download

​
Install

  1. Download SkyNETV3-win-x64.zip or SkyNETV3-linux-x64.zip and extract it on the host.
  2. Linux: chmod +x SkyNET SkyNETV3 (first install only — updates fix execute bits afterward).
  3. Start the bot:
    • Windows: SkyNETV3.exe
    • Linux: ./SkyNET — do not run ./SkyNETV3 directly (updates can leave an orphan process you have to kill by hand)
  4. First boot creates SkyNET.json and exits. That is expected.
  5. Edit SkyNET.json (see below), then start her again.
On Linux, ./SkyNET reads launch settings from your config (PROCESS_NAME, optional SCREEN_NAME). With SCREEN_NAME set, she starts in a detached GNU screen session and the launcher exits. Needs screen on PATH. Ignored under systemd and on Windows. Details: Configuration.

​
What to set before the second start

At minimum: If the database does not exist yet, SkyNET will create it from EmptyDB.sql next to the binary (keep that file with the install). Full option list: Configuration.

​
After she is online

  • Invite your bot to your Fluxer servers (not the public Beta Core invite).
  • Same permission rules as public: Administrator (or enough rights), role above what it manages.
  • Set up admin ACL with !perms (see below) — self-host has no Dashboard by default.
  • Optional: Twitch / YouTube / Steam keys in config if you use those features.
  • Optional: drop third-party command packs under modules/ — see Modules.
  • Official updates: leave AUTO_UPDATE on (default) or turn it off to pin a version.
The Dashboard for self-hosted installs is a Patreon perk. The bot itself runs without it; SkyAPI in config is what the Dashboard talks to when you use one.
Without the Dashboard, !perms is how you give staff access to admin commands.

​
Admin ACL (important for self-host)

SkyNET does not use Fluxer’s “Kick Members / Manage Roles” flags for most staff commands.
Admin commands use SkyNET’s own ACL (stored in MySQL). Public users configure that in the Dashboard; self-hosters usually do it in chat.
Until you grant roles with !perms, only the Fluxer server owner can run ACL admin commands (!mute, !ban, !modlog, !prefix, …).
Staff with powerful Fluxer permissions still get denied unless their role is on the allowlist.
Who can manage ACL
  • The server owner, or
  • Anyone listed in OWNER_IDS in SkyNET.json
Those people run !perms / !permremove. You cannot bootstrap ACL by giving yourself a role first — that is intentional (no chicken-and-egg). Commands Examples:
Notes:
  • Grants are per command — mute access does not automatically include ban.
  • @everyone cannot be granted.
  • Empty allowlist for a command = owner only.
  • Third-party module commands are not ACL-gated (Everyone) in API v1.
  • Alias names usually work (!perms ce for createevent, etc.).
If someone gets an ACL deny embed, grant their staff role the command(s) they need, or have the server owner run them.

​
Quick checks if something fails

  • Bot token not set / invalid FLUXER_URL — edit SkyNET.json and restart.
  • MySQL errors — host, user, password, and that EmptyDB.sql is beside the binary.
  • Fluxer connection failed — token and URL must match your instance (HTTPS only).
  • Linux weird double process after an update — you started SkyNETV3 instead of ./SkyNET.
  • Staff can’t use !mute / !ban / … — set ACL with !perms (see above).