-
Notifications
You must be signed in to change notification settings - Fork 1
Setup Guide
Screenshots to come later — this covers every setting and what it's for in the meantime.
File → Add Bot... opens the same Bot Configuration window used to edit an existing bot later
(right-click a bot tab, or File → Edit Selected Bot...). Every section below is an Expander
in that one window; click a header to open/close it.
At the very top:
- Display name — whatever you want this bot's tab to show.
- Tab group (optional) — bots sharing the same group name collapse into one top-level tab with their own sub-tabs, handy for running several bots on the same server. Leave blank to keep the bot as its own tab. Once grouped, you can also pick a Group icon for the shared tab.
Pick the product first — everything else in the window reacts to this (which server options show, whether you need a CD-key, etc.). Supports the classic BNCS lineup (StarCraft, StarCraft: Brood War, Diablo, Diablo II, Diablo II: LoD, Warcraft II: Battle.net Edition, Warcraft III / The Frozen Throne) plus the Stimpak-backed modern products (StarCraft II, StarCraft: Remastered, Warcraft III: Reforged).
- Auto-connect when the app starts — connects this bot automatically on launch.
-
Auto-reconnect after an unexpected disconnect (+ delay in seconds) — only triggers on a
disconnect the bot didn't cause itself; clicking Disconnect never auto-reconnects. Note: on
official Battle.net, a drop can be the server's anti-bot check (
SID_REQUIREDWORK/ExtraWork), which this bot deliberately doesn't implement a workaround for — reconnecting just retries like a normal client would, it won't change the outcome if that's the cause. - Battle.net Server — a dropdown of known official servers where the product still supports them, otherwise a free-text/autocomplete field for a private/PVPGN server address. Some products (noted with an orange warning) only work on private servers any more.
- Battle.net port / Realm (Diablo II only).
-
BNLS Server — the CD-key/version hashing helper, defaults to
bnls.bnetdocs.org. Only change this if it stops working. - Version byte override (advanced) — only needed against a private/PVPGN server pinned to an older client version than BNLS's database assumes; its version check rejects BNLS's byte even though the CD-key/hash parts are fine. Leave blank unless you actually hit that. Turn on Debug logging (Appearance section doesn't have this — it's the bottom of a bot tab's own UI) to compare BNLS's own value against your override.
- StarCraft II connects through Battle.net's modern login system instead — no server/BNLS/ version byte to configure; see Account below for logging in.
- Flood protection delay (ms) — minimum gap enforced between outgoing messages (including trivia questions/hints/answers) so a fast burst doesn't get the bot muted or disconnected. Raise it if you still get flooded off; lower it if your server is more permissive.
- Disable join/leave notifications entirely, or Hide join/leave spam (only for a specific user once they cross a configurable rate within a time window — e.g. someone with a flaky connection bouncing in and out repeatedly). Everything underneath (roster tracking, rank behaviors, join count) still happens as normal either way — this only affects what's shown in the chat log.
- Show game icons next to usernames in chat — a small icon before each chat/emote line from the speaker's own tracked game. On Stimpak-backed products (SC2/SC:R/WC3:R) every speaker shows this bot's own product icon instead, since that protocol doesn't report which game each person is using.
-
Idle Message — set minutes of inactivity (0 = off) and a message to send once the channel's
been quiet that long; doesn't repeat until real activity resumes first. Supports placeholders,
resolved fresh each time it actually sends:
%Ver%,%Uptime%,%MusicPlaying%(blank if nothing's playing),%Username%. Also settable live via theidle <minutes> <message>chat command (see the Commands page) — same setting either way.
Routes this bot's connections (BNCS/BNLS/D2 realm) through a SOCKS5 or HTTP CONNECT proxy — host, port, optional username/password. Each bot can point at a different proxy, so several bots you run can appear to come from different IPs instead of sharing one, useful against a server's per-IP (rather than per-connection) flood/connection limit.
- Classic products: Username, Password, and (if the product requires it) CD Key / Expansion CD Key.
- StarCraft II / SC:R / WC3:R: instead of username/password here, pick a Battle.net Profile — a saved login you can reuse across multiple bots (e.g. two bots on the same account), or create a new one. Signing in happens automatically on Connect, or manage profiles directly from Customize → Manage Battle.net Profiles....
- Bot Master — the account that always has full command access regardless of clan rank.
-
Trigger — the single character other users type before a command in chat (e.g.
!); the bot's own operator can always use/locally regardless of this setting. -
Home channel (classic products) — where the bot joins by default and rejoins with the
homecommand.
Off by default. Turning on Enable clan management for this bot adds the Clan tab (roster,
ranks, aliases, trivia score) for this bot — the roster itself is shared across every bot you
run, on any game, so this setting just opts this particular bot into it. Set a Default rank for
new chatters to auto-track everyone who talks (not just people you've explicitly added) — leave
it blank to turn auto-adding off. Set a Banned rank name; assigning that rank via
clanrank <name> <banned rank> blocks someone from every bot command, including the otherwise-
always-open trivia join/score.
Manage the roster and ranks from the top-level Clan menu (only visible once at least one bot has clan management on): Manage Members... (the full roster/seen-list — search, per-member rank/nickname/aliases/notes/platforms, right-click a user in a bot tab for quick actions — see Commands) and Manage Ranks... (create/edit ranks, each with its own Allowed Commands list plus optional auto-whisper/auto-kick/auto-ban behavior for anyone seen holding it).
Off by default per bot. Ships with a starter question pack (Diablo/Warcraft/StarCraft) — drop
more .txt files into the Trivia folder (File → Open Config Folder) to add your own. Set a
Trivia group name to link several bots into one shared round: whichever bot runs trivia on
relays the question to every group member's own channel, and a correct answer on any of them ends
it for the whole group. Scoring is graduated by how many hints have already shown — set the point
values for before-first-hint / after-first-hint / after-second-hint.
- Chat Color Scheme — pick a built-in scheme or one of your own (create/edit those from Customize → Manage Colors...).
- Icon Set — pick a named icon-set snapshot for this bot specifically (see the Icon Sets section below for what a "set" actually is and how to make one).
Zero ping fakes a near-0ms reading; Negative ping shows no ping reading at all.
Off by default. Relays chat between this bot's Battle.net channel and a Discord channel — connects/disconnects alongside the bot itself, no separate button.
- Create a Discord bot application in the Discord Developer Portal, grab its bot token, and turn on the Message Content privileged gateway intent on the Bot page — without that intent, other users' messages arrive empty and nothing relays.
- Invite the bot to your server.
- In Discord, turn on User Settings → Advanced → Developer Mode, then right-click the channel you want bridged and Copy Channel ID.
- Paste the bot token and channel ID here, turn on Enabled, and pick which direction(s) to relay (Battle.net → Discord, Discord → Battle.net, or both). Relay delay (seconds) throttles each direction independently from the general chat flood-protection delay above.
Once connected, the bridge bot also sets its own Discord activity/status to reflect where it's
connected (e.g. "Playing Invigoration in <channel> on <server>"), refreshed on connect and on
every channel join.
A global feature (not per-bot) — toggle it from Customize → Music Player, which adds a
persistent Music tab. Pick a service (YouTube Music, Spotify, or Pandora) from the small button
row at the top of that tab; sign in once and it stays signed in across restarts. Control playback
either from that tab directly, or from chat via the skip/thumbsup/thumbsdown/nowplaying
commands (see Commands).
Customize → Music Bar (bottom) adds an optional thin playback bar docked at the bottom of the whole window, visible no matter which top-level tab you're looking at — now-playing text plus skip/thumbs-up/thumbs-down, so you don't have to switch to the Music tab just to skip a track.
Notes per service:
- Pandora: thumbs up/down only appear while playing an actual station (radio), not on-demand playlists/albums — that's a real Pandora distinction, not a bug.
-
Spotify: has no "dislike" concept in its web player (only a Save-to-Library heart), so
thumbsdownquietly does nothing there.
Customize → Manage Icons... is where every chat/status icon lives. At the top, one combined dropdown lets you apply an icon set in one click:
- Battle.net 1.0 Classic — the original small classic.battle.net chat icons.
- Warcraft III Classic — a sharper, larger (64x64) version of the same classic icon family.
- Battle.net 2.0 — modern account.battle.net-style game icons, with status badges (Blizzard Rep/Admin/Moderator/Speaker/Squelched) borrowed from the Warcraft III Classic set to match (the Moderator one gets a green glow to read better against the brighter modern art).
- Any set you've saved yourself also shows up in the same dropdown.
Below the dropdown, every individual icon (game icons, status badges, friend/custom icons) can be overridden one at a time with your own image file — pick a slot, choose a file, done; Reset clears just that one back to the set's default. Save Current As Set snapshots whatever mix of icons is currently active (bundled + your own individual overrides) under a name of your own, so you can swap back to it later — each saved set is just a plain folder (Open Icon Sets Folder to see/back them up directly).
Per-bot, the Appearance section of that bot's config picks which saved set (if any) applies to it specifically, on top of whatever's globally applied.
Right-click any entry in a bot's classic Users list for two quick display toggles (see also Commands for the other right-click actions on that same menu):
- Classic Icon Style — when on, a privileged user's rank badge (Moderator gavel, Blizzard Rep logo, etc.) replaces their game icon in that one slot, matching real classic Battle.net behavior, instead of showing both side by side (the default).
Moderators/Blizzard Reps/Admins/Speakers also always sort to the top of the Users list now (in their own join order), with everyone else below — matching classic Battle.net's own ordering.
Customize → Manage Colors... lets you create/edit named color schemes (every chat-message category — usernames, whispers, errors, etc. — gets its own color) and save them to your own library. Pick "Custom" as a bot's Chat Color Scheme (in its Appearance config section) to select one of your saved schemes for that bot.
Customize → Manage Battle.net Profiles... manages the saved logins used by the modern Stimpak-backed products — create one profile per account, reuse the same profile across multiple bots that share a login, or keep separate profiles for separate accounts. Assign a bot's profile from that bot's own Account config section.
Right-click a name in the classic Users list or the Friends list for Whisper/Profile Info/Clan Rank/Squelch/Add Friend — see the Commands page for the full rundown, including the real (editable, for your own account) Battle.net profile window that opens from "Profile Info".