D2Dropper Remastered

D2Dropper Remastered browses an existing Kolbot inventory, creates Trade Lists, and prepares Kolbot-compatible item delivery jobs. It reads the existing ItemDB.s3db directly; no inventory conversion is required.

Install on Windows

1. Download the latest Windows x64 ZIP from Releases.
2. Extract the complete ZIP to a private folder.
3. Double-click install.bat.
4. Follow the setup page that opens in your browser.

That is all. The packaged release includes PHP, required extensions, application packages, and frontend assets. A normal Windows user does not install PHP, Composer, Node.js, npm, Apache, IIS, or Docker.

Windows 10 or Windows 11 x64 is required. PHP also needs the Microsoft Visual C++ 2015–2022 Redistributable (x64), which is already present on most Windows systems. If it is missing, the launcher displays a direct explanation instead of closing silently.

After installation, double-click start-server.bat whenever you want to use D2Dropper. It starts only on 127.0.0.1:8666 and opens the application automatically. If it is already running, the launcher simply opens it.

Migrating from original D2Dropper

1. Keep and back up the original installation.
2. Install Remastered in a separate folder.
3. Select a copy of the existing ItemDB.s3db during the first test. It is used directly without conversion or migration.
4. Select an isolated Drop directory first, then enter the existing case-sensitive Kolbot profile names.
5. Keep Kolbot unchanged. After the smoke test succeeds, select the intended ItemDB and Drop paths.

Existing web users are not imported; create Resellers from Administration. Existing saved packs can remain in the legacy html\savedlist directory when D2DROPPER_SAVED_PACKS_PATH points there. Pack creation is not yet migrated.

Administrators explicitly assign each account zero or more configured Drop profiles. When several profiles are assigned, D2Dropper automatically rotates mule-account groups across available profiles; items from one mule account stay together and profiles with pending jobs are skipped. Normal Drop publication does not require a manual profile choice.

First browser setup

The setup page asks for:

• the sole Administrator username and password;
• the existing ItemDB path;
• an existing writable Drop directory;
• the exact Kolbot profile names allowed to receive Drop jobs;
• basic application settings.

Setup does not modify ItemDB or Kolbot and does not create a Drop job. The Windows installer stores the Laravel database in a private per-user folder under %LOCALAPPDATA%\D2Dropper Remastered\instances\, records its absolute path in .env, and preserves it when run again. This keeps SQLite journal activity out of Desktop and other protected extraction folders.

Data safety

The application deliberately uses two databases:

• the database configured by DB_DATABASE is Laravel-owned and contains users, sessions, selections, settings, Trade Lists, Drop metadata, backups, and audit events; packaged Windows installs place it under %LOCALAPPDATA%\D2Dropper Remastered\instances\;
• ItemDB.s3db remains the legacy inventory source and is not imported, converted, or migrated.

Keep .env, both databases, private storage, backups, and Drop files outside public/. D2Dropper Remastered only reads inventory data during ordinary browsing, but Kolbot must retain write access to the ItemDB file and its folder so it can refresh inventory after muling and Drops. SQLite write administration is an explicit Administrator maintenance feature that requires confirmation and a backup.

The browser installer creates exactly one Administrator and writes storage/app/installation.lock. Preserve the Laravel database and all of storage/app/ together during upgrades or restores.

Troubleshooting Windows startup

The installer and launcher keep their console open when a failure occurs and show the failed check. Common causes are:

• an incomplete ZIP extraction, reported as missing bundled PHP or vendor/autoload.php;
• a missing Microsoft Visual C++ 2015–2022 Redistributable (x64), reported when PHP cannot start;
• port 8666 already being used by another program;
• an unwritable application or per-user application-data folder;
• running start-server.bat before install.bat.

Server logs are written to storage\logs\local-server.log and storage\logs\local-server-error.log.

Developers and advanced source installs

Source checkouts do not contain PHP or vendor/. They require PHP 8.3 or newer with pdo_sqlite, sqlite3, GD with FreeType, OpenSSL, JSON, mbstring, and fileinfo, plus Composer 2. Node.js is needed only when rebuilding frontend source assets.

From PowerShell:

powershell -File install.ps1 -PhpPath "C:\path\php.exe" -ComposerPath "C:\path\composer.phar"

For an internet-facing deployment, use a proper Apache/PHP or Docker deployment with only public/ exposed. Do not expose Laravel's local server over a network. See the detailed deployment guide below.

Detailed documentation

• Installation and administration
• Windows release, source, Apache, Docker, and scheduler deployment
• Safe upgrades and rollback
• Smoke-test checklist
• Isolated real Drop test

This project is licensed under GPL-3.0-or-later and preserves original D2Dropper authorship and licensing notices.