Guides

What you can build for LonelyIce, the tools you need, and the order in which to read the developer guides and reference.

A plugin that greets every player on login, from an empty folder to a package installed by the launcher.

Short patterns from real plugins for server code: hooks, timers, commands, config, databases, messages, gossip, creatures, translations, per-player data and playerbots.

Give a plugin a config file and a group in the launcher's Settings, and read the values in server code.

Tables and rows in the server's databases: folders, file names, when the SQL runs, and the SQL that works on every backend.

Add spells and other DBC rows with patch recipes: named ids, server rows, the generated client archive and what happens on removal.

Build an existing AzerothCore module as a LonelyIce plugin without forking it: a pinned source, small patches, its conf and SQL laid out with the plugin.

How a plugin like lonelyice.mysql adds a database backend to the core and a storage to the launcher.

Logs, loader errors, running the server process by hand, attaching a debugger, and switching a plugin off.

Choosing version numbers, declaring depends and conflicts, shipping several platforms, rebuilding for a new core ABI, and stating languages.

From a built plugin to the catalog: packing, uploading, automatic checks and review.

Every automatic check on an upload, what each message means, how moderators review and decide, and a checklist before you upload.

Serve your packages from a folder or a web server: the index.json format, building it with --pkg pack, and adding the catalog to the launcher.