How blizzhackers/kolbot works
Project type and purpose
• This is an open-source Diablo II botting system (“d2bs”) with three distinct components:
• D2BS (core, written in C++) – hooks the game process and exposes a scripting API
• D2Bot# (manager, written in C#) – a Windows GUI/CLI that launches and monitors bot instances
• kolbot (script library, written in JavaScript/Node) – a set of JS modules, systems, and user scripts that drive the bot’s behavior
• There is also a “limedrop” web component (Node/TypeScript) for item management and remote monitoring.
File structure
• Top-level:
• D2Bot.exe (C# manager binary)
• d2bs/ (native core + embedded JS engine, config, SDK, logs)
• limedrop/ (web UI code, probably a small Node/TS app)
• package.json, tsconfig.json, .eslintrc.js, etc. (tooling for JS/TS code)
• d2bs/kolbot/:
• libs/ (core modules, config templates, manual-play overrides, extension points)
• modules/ (higher-level plumbing: HTTP, Socket, Worker, Team, etc.)
• systems/ (prebuilt “systems” like automule, autorush, crafting, mulelogger, etc.)
• scripts/ (dozens of user-facing automation scripts, e.g. “Act bosses,” “MFHelper,” “ShopBot”)
• pickit/ (NIP files for item pick-up rules)
• sdk/ (statically shipped data files and TypeScript definitions for the JS API)
• threads/ (JS code run in parallel threads within the bot runtime)
• data/ and logs/ store JSON settings, schedules, key info, and runtime logs.
README for additional insights
• Confirms three main components, community-supported, meant for offline or private servers
• Mentions dependencies: MSVC++ 2010, .NET 4.x for the manager, Node.js/TS for kolbot tooling and limedrop
• Points to live documentation, guides on setup, multi-botting, manual play, character config
Elements
• Blue = Native layer (C++, Game Process)
• Green = Manager & tooling (.NET, Node)
• Orange = Scripting layer (JS modules, systems, scripts)
• Gray = Data/config/log files