CI Tests and Coverage CI Lint Release License Java 25

Build plugins and services, not database plumbing.

DataProvider is shared infrastructure for plugin developers on Velocity and Bukkit/Paper.
It gives you one clean API for MySQL, MongoDB, Redis, and Redis messaging so your plugin code can stay focused on gameplay and business logic.

• Faster development: stop rewriting connection, pooling, and lifecycle code in every plugin.
• Consistent developer experience: same registration and access flow across multiple backends.
• Safer multi-plugin setup: caller-scoped access rules prevent cross-plugin misuse.
• Cleaner codebase: typed APIs reduce casting and repetitive boilerplate.
• Better runtime behavior: connection reuse and lifecycle cleanup are handled centrally.

• Following data backends are implemented: MYSQL, MONGODB, REDIS, REDIS_MESSAGING
• Platform support: Velocity + Bukkit/Paper
• Optional ORM (through hibernate) support for relational workflows (ORMContext)

• Java 25
• Velocity 3.5.0-SNAPSHOT and/or Paper API 26.1.2+ (compile targets)
• MySQL, MongoDB, and/or Redis for the backends you enable

Resolve the API from your platform runtime:

Velocity:

DataProviderAPI api = proxyServer.getPluginManager()
 .getPlugin("dataprovider")
 .flatMap(container -> container.getInstance()
 .filter(DataProviderApiSupplier.class::isInstance)
 .map(DataProviderApiSupplier.class::cast)
 .map(DataProviderApiSupplier::dataProviderApi))
 .orElseThrow(() -> new IllegalStateException("DataProvider is unavailable."));

Bukkit/Paper:

RegisteredServiceProvider<DataProviderAPI> registration =
 Bukkit.getServicesManager().getRegistration(DataProviderAPI.class);
if (registration == null) {
 return;
}
DataProviderAPI api = registration.getProvider();

Optional<RelationalDatabaseProvider> mysql = api.registerDatabaseAs(
 DatabaseType.MYSQL,
 "default",
 RelationalDatabaseProvider.class
);
if (mysql.isEmpty() || !mysql.get().isConnected()) {
 // Handle unavailable connection
 return;
}
api.unregisterDatabase(DatabaseType.MYSQL, "default");

If you maintain multiple plugins, this gives your team one standard integration model instead of backend-specific code per project.

• /dataprovider help shows command usage.
• /dataprovider status [summary|connections] [unhealthy] [plugin <name>] [type <databaseType>] shows active connection diagnostics.
• /dataprovider config prints current runtime config state (orm.schema_mode + backend enablement).
• /dataprovider reload reloads config.yml from disk.

Permissions:

• dataprovider.command.status
• dataprovider.command.config
• dataprovider.command.reload

1. Build or download DataProvider.jar.
2. Put it in your server plugins/ directory.
3. Start once to generate default configuration.
4. Configure plugins/DataProvider/config.yml and plugins/DataProvider/databases/*.yml.

Coordinates:

• groupId: nl.hauntedmc.dataprovider
• artifactId: dataprovider
• version: current release

Repository:

• https://maven.pkg.github.com/HauntedMC/DataProvider

Maven:

<repository>
 <id>github</id>
 <url>https://maven.pkg.github.com/HauntedMC/DataProvider</url>
</repository>

<dependency>
 <groupId>nl.hauntedmc.dataprovider</groupId>
 <artifactId>dataprovider</artifactId>
 <version>2.0.0</version>
 <scope>provided</scope>
</dependency>

Gradle (Groovy):

compileOnly "nl.hauntedmc.dataprovider:dataprovider:2.0.0"

GitHub Packages authentication details are in the docs.

mvn -q -DskipTests compile
mvn -q test
mvn -B verify
mvn -B -DskipTests checkstyle:check
mvn -B package

Build output:

• target/DataProvider.jar

• Documentation index
• Architecture
• Usage guide
• Configuration
• Development
• Testing and CI
• Release process
• Examples

• Contributing
• Code of Conduct
• Security Policy
• Support

This project is licensed under the GNU Affero General Public License v3.0.