MCBackpack

What Is MCBackpack?

• A modular backpack framework for Minecraft servers on PaperMC, SpigotMC, and FoliaMC.
• Persistent, password-protectable backpack storage backed by multiple database engines.
• A service provider: the plugin itself carries no gameplay commands — it hosts the backpack provider and the extension manager, and extensions deliver the in-game behaviour.

How It Works

• Platform entrypoint: the plugin jar for your server boots, reads its configuration, and prepares the platform-specific runtime.
• Provider starts: the backpack provider is created around the configured database and exposed as the central API for every backpack operation.
• Extensions load: the MCExtension manager scans the extensions folder and loads extensions asynchronously — they register commands and listeners against the provider.
• Data persists: backpack contents and password hashes are stored through the selected backend — SQLite, MySQL, or a remote API server.

Architecture

• api — pure Java interfaces and data models; everything is asynchronous.
• common — platform-independent logic: the core provider plus the SQLite, MySQL, and remote API database implementations.
• platforms — thin plugin entrypoints for PaperMC, SpigotMC, and FoliaMC that host the provider, manage extensions, and ship as shaded plugin jars.

Features

• Robust database backends: SQLite for zero-setup servers, MySQL for networks, or a remote API backend when backpack data lives on another service.
• Password protection: per-backpack password hashing with set, check, change, and delete operations; raw hashes never leave the server on remote backends.
• Modular extension system powered by MCExtension: external plugins register custom behaviour and commands on top of the backpack provider — load, unload, and reload at runtime.
• Multi-platform builds: native builds for PaperMC, SpigotMC, and FoliaMC from a single codebase, including Folia-aware region scheduling rules.

Configuration

• The plugin generates a config.yml where you pick and tune the storage engine.
• db.type selects the backend: sqlite, mysql, or api.
• SQLite stores its database file under plugins/MCBackpack by default.
• MySQL settings cover host, port, database name, user, password, and SSL.

Explore