How adpist/horde works
Project type and purpose
• This is a game‐botting system for Diablo II, comprising three tightly integrated components:
– D2BS (native core) that hooks into the Diablo II process and hosts a JavaScript engine
– D2Bot# (C# manager) used to launch, monitor and orchestrate multiple bot instances
– kolbot (JavaScript library) providing battle scripts, configurations, item pickers and helper tools
• There is also a lightweight web component (LimeDrop) for item management.
File structure
• Top level:
– D2Bot.exe (manager UI)
– d2bs/ (core engine plus script folder “kolbot”)
– data/, logs/, images/ (configuration, logs, assets)
• d2bs/kolbot/:
– default.dbj and D2Bot*.dbj scripts (entry‐point bot scripts)
– libs/ (core script libraries and bot routines)
– pickit/ (item filtering rules in .nip files)
– sdk/ (static game metadata)
– tools/ (JS helper modules)
• data/: JSON files for account, server, profile, patch, schedules
• logs/: runtime logs for console, exceptions, keyinfo
README for additional insights
• Confirms three components (core, manager, scripts)
• Mentions LimeDrop web item manager included by default
• Points to external documentation for manager setup, scripting conventions and LimeDrop usage
– Game Client Process (Diablo II)
– D2BS Core Engine (native DLL)
– JavaScript Host / Script Engine (inside D2BS)
– Script Library (kolbot folder: libs, config, pickit, sdk, tools)
– D2Bot# Manager (C# GUI, process launcher)
– Data Storage (data/*.json, d2bs/d2bs.ini)
– Logs (logs/ and d2bs/kolbot/logs/)
– LimeDrop Web UI / Server (optional web frontend)
– Manager ➔ launches ➔ Core Engine instance
– Core Engine ➔ injects into ➔ Game Client
– Core Engine ➔ hosts ➔ Script Engine ➔ loads ➔ JS Script Library
– JS Scripts ➔ read/write ➔ Data Storage and Logs
– LimeDrop Web UI ↔ API Connector ↔ Core Engine or Data Storage
c. Architectural patterns and principles
– Plugin/script‐based architecture: JS scripts are modular and loaded at runtime
– Separation of concerns: native engine vs. script logic vs. orchestration UI
– Configuration‐driven behavior: JSON/INI inputs and pickit rules drive bot actions
d. Key technologies, frameworks, libraries
– Native C++ DLL injection (D2BS)
– Microsoft .NET/C# for Manager (D2Bot#)
– Mozilla‐spidermonkey or similar JS engine hosted by D2BS
– JSON/INI for configuration, custom .nip file format for item rules
– Optional web tech stack for LimeDrop (Node.js or static HTML/JS)
Detail
• Major script folders (libs, config, pickit, sdk, tools) as sub‐components
• How D2BotAccountCleaner.dbj, D2BotHorde.dbj, etc., plug into the engine
• Configuration templates vs. user overrides
• How LimeDrop interacts (direct file read or via a small HTTP API)