Unofficial mirror
This is not the official Darkbot website. imhko.com keeps a public mirror, fork notes and backup downloads. The original project site is darkbot.sourceforge.net.
DARKBOT SECTION
Current fork: 8rc5. This section acts as an on-site backup for Darkbot so the main help, downloads and script pages stay available on imhko.com even if other project sites go offline.
This is not the official Darkbot website. imhko.com keeps a public mirror, fork notes and backup downloads. The original project site is darkbot.sourceforge.net.
Read the full backup help for installation, setup files, commands and usage.
Get the mirrored release archive list and the current fork version on site.
Open the maintained utilities for Setup, AddUser, AddServer and check-integrity.
See the fork additions around search, quotes, deop handling and example data files.
Find the site contact path and fork notes without leaving imhko.com.
Unix install, configure and first-run notes from the mirrored help tree.
Windows install and setup notes from the mirrored help tree.
The main command reference is mirrored here in a grouped backup layout.
Read the current 8rc5 additions such as search, quotes, weather, seen and deop handling.
The mirrored Unix help covers the original flow: unpack the archive, run the setup process, build the bot and edit the offline data files before starting it in a live channel.
The important files stay the same on imhko.com: setup.ini, servers.ini, perform.ini, deop.ini and userlist.db.
The Windows copy mirrors the original install and setup notes without pushing the user off-site. It keeps the same basic sequence: install, configure, connect and verify.
The original command listing is grouped into the same main sections as the SourceForge page: administration, database management, channel operation, status and information, user access and utilities.
The mirrored version keeps that structure on imhko.com so the command reference remains available even if the old project pages are unavailable.
The current fork adds public DuckDuckGo URL results, configurable short URLs, decoded weather, TAF, word of the day, quote/profquote aliases, backup helpers and cleaner public help output.
The mirror also includes restored deop responses, fixed runtime paths and download links for the current source, runtime data, scripts and mirrored database packs.
Shows the active bot prefix and how the command syntax is read.
Shows build-line details from the source tree and compile state.
Reports database size, uptime and current activity counters.
Tracks how often the bot has seen joins during the current session.
Notes the language setup used by the help and status output.
Memory-related readout from the same status group on SourceForge.
Shows the platform string the bot was built and running on.
Summarises permanent ban information from the status page.
Shows whether the command queue is busy or idle.
Reports memory pressure and the bot's current footprint.
Tracks the random-stuff bucket used by the original status set.
Shows the server and location the bot is currently attached to.
Reports how long the bot has been up and running.
This is the read-only status command that tells users which prefix the bot currently expects. On the original help page it is used to confirm whether the bot responds to ! or another configured prefix.
It is a simple sanity check, not an operator control. The mirrored copy keeps it on-site so the command reference stays available even if the source site disappears.
This entry reflects the compiled source state. The SourceForge help describes it as information about the code file, the line count and when the build was produced.
For the current fork, the card points back to the mirrored 8rc5 line and the local build notes on imhko.com.
This status command reports the bot's version line, database size, session uptime and the activity counters for questions, additions and deletions.
It is one of the main read-only commands in the original status group, so it belongs in the on-site backup with the rest of the command reference.
This command tracks how many joins the bot has witnessed during the current session. It is a simple channel activity counter.
The SourceForge status section groups language-related output with the rest of the read-only status commands. In practice it tells users which language handling the bot uses for its replies and status text.
Memory reporting belongs to the same status page as the other diagnostics. It is used to show how the bot is doing in the running environment without changing state.
This is the OS readout people usually look for first. The original help page uses it to show the platform string the bot is running on, so operators can tell whether they are dealing with a Unix or Windows build.
That is the card you asked for: a short preview up front, then the full status explanation underneath on the same page.
This command reports the permanent-ban state tracked by the bot. It is part of the status group on the original reference page and is kept here as mirrored text.
This output tells you whether the bot queue has pending work. It is a read-only diagnostic and does not modify the bot or its data files.
RAM reporting gives a simple view of the bot's memory situation. The mirrored copy keeps it grouped with the other status commands from the SourceForge docs.
This is part of the original status set and is treated as a read-only internal check. The point of the backup is to keep the command list available even when the upstream pages are unavailable.
This is the server/location readout used by the original docs to show where the bot is connected. It is the practical version of the "where is the bot right now" question.
This shows how long the bot has been running in the current session. It sits alongside the other information commands and does not affect configuration.
Verified files are served through Drupal so the mirror does not depend on host static-file handling.
Current fork with docs, example data, search fixes, quotes, word of the day and restored deop handling.
Mirrored database packs from the old Darkbot database section and the current runtime dat files.
countrycodes · file_extensions · ports · rfc
acronyms · acro2 · Jason · mac_errors · usa_phone_areacodes
Legacy release line with the older upstream layout and command set.
Legacy release line from the upstream archive. Mirror file pending.
Legacy release line from the upstream archive. Mirror file pending.
Legacy release line from the upstream archive.
Older release archive from the historical fork line.
Older release with historical configuration examples. Mirror file pending.
Final 7.x RC line before the 8.x series. Mirror file pending.
Older archive release kept for continuity. Mirror file pending.
Older archive release kept for continuity. Mirror file pending.
Older archive release kept for continuity. Mirror file pending.
Older archive release kept for continuity. Mirror file pending.
Older archive release kept for continuity. Mirror file pending.
Older archive release kept for continuity. Mirror file pending.
Older archive release kept for continuity. Mirror file pending.
Older archive release kept for continuity. Mirror file pending.
Very early archive build and compatibility reference. Mirror file pending.
Very early archive build and compatibility reference. Mirror file pending.
Guides initial config and writes the example runtime files into the current tree.
Manages bot access entries and points new admins at the current userlist layout.
Maintains the local server list and keeps the example server file in sync with the fork.
Validates the data files and keeps the runtime files tidy before rollout.
!ddgo, !ddg, and DUCKTOGO use the full query string and return DuckDuckGo result URLs.
!addq, !quote, !qt and !quotetell use the quote database.
The bot responds again when it gets deoped, using the configured script response.
Example values are shipped in dat/ so private details are not committed by default.
IRCII TEST DEMO
[21:00] *** user has joined #darkbot [21:01] <user> !cmds [21:01] <darkbot> Public commands: !weather/!wh, !taf, !ddgo, !short, !wotd, !quote, !backup. More: !help [21:02] <user> !ddgo 3 darkbot irc [21:02] <darkbot> ddgo: https://darkbot.sourceforge.net/ [21:02] <darkbot> ddgo: https://sourceforge.net/projects/darkbot/ [21:02] <darkbot> ddgo: https://en.wikipedia.org/wiki/IRC_bot [21:03] <user> !short www.knaz.nu [21:03] <darkbot> shorturl: https://c9.nu/pq1 [21:04] <user> !wh Goteborg [21:04] <darkbot> weather: 12 C, light rain, wind 4 m/s [21:05] <user> !taf ESGG [21:05] <darkbot> taf: ESGG 211720Z 2118/2218 24008KT 9999 SCT020 [21:06] <user> !wotd [21:06] <darkbot> Word of today: resilient. Able to recover quickly. [21:07] <user> !pq [21:07] <darkbot> quote: The important thing is not to stop questioning. [21:08] <user> !help ddgo [21:08] -darkbot- DDGO [1-4] <text> returns DuckDuckGo result URLs by private notice. [Act: 3] [#darkbot] [darkbot(+i)] [users: 42] [imhko.com/darkbot]
COMMAND TEST SCREEN
[21:10] <user> !ddgo darkbot irc [21:10] <darkbot> ddgo: https://darkbot.sourceforge.net/ [21:11] <user> !ddgo 4 eggdrop [21:11] <darkbot> ddgo: https://www.eggheads.org/ [21:11] <darkbot> ddgo: https://github.com/eggheads/eggdrop [21:11] <darkbot> ddgo: https://en.wikipedia.org/wiki/Eggdrop [21:11] <darkbot> ddgo: https://docs.eggheads.org/ [21:12] <user> !short https://imhko.com/darkbot [21:12] <darkbot> shorturl: https://c9.nu/dbot [21:13] <user> !weather London [21:13] <darkbot> weather: 18 C, cloudy, wind 5 m/s [21:14] <user> !taf ESSA [21:14] <darkbot> taf: ESSA 211720Z 2118/2218 23010KT 9999 SCT030 [21:15] <user> !quote [21:15] <darkbot> quote: I have not failed. I have found 10,000 ways that will not work. [21:16] <user> !wotd [21:16] <darkbot> Word of today: pragmatic. Focused on what actually works. [21:17] <user> !backup [21:17] <darkbot> backup: saved dat files to backups/20260621-2117/ [21:18] <user> !help [21:18] -darkbot- Help is sent privately. Try !help weather, !help ddgo, !help short. [21:18] [#darkbot(+nt)] [user(+i)] [rawbot idle: 00:00:03]
Use the site contact form for project-level questions or updates about the current fork.
The fork is focused on the current `8rc5` line, the shipped scripts and the IRC-facing commands.
The page focuses on the current 8rc5 fork and the pieces that matter for running it: setup, scripts, examples and the IRC-facing commands.