- Minecraft Version
-
- 1.21
CoreAPI
Modular Minecraft network API for Bukkit, Spigot, Paper, and BungeeCord
CoreAPI is a modular Minecraft backend API designed for developers and server owners who want to manage important network systems through one shared foundation.
Instead of creating separate storage logic and data models for every plugin, CoreAPI gives you one central backend for player data, friend systems, clan systems, nickname handling, profile settings, configurable prefixes, and MySQL storage.
It is meant for custom Minecraft server development and is especially useful for networks that want a reusable Bukkit API, Spigot API, Paper API, or BungeeCord API to power multiple plugins with one consistent backend.
What this product offers
CoreAPI is not just a small utility library. It provides a structured base for real Minecraft systems and can be used as the technical core behind many different plugins.
It includes support for:
This makes CoreAPI a strong solution for developers who want to build custom profile systems, social systems, clan systems, rank tools, backend frameworks, or network-wide server systems.
Player data system
CoreAPI provides a shared player model that can be used across different plugins and systems.
The player structure includes values such as:
This allows developers to use one central player object instead of storing different profile data separately in multiple plugins.
Example usage:
Player API
This screenshot fits best with the player model and player-related methods.
View attachment 1316245
It should show how CoreAPI stores and exposes player information for profile systems, menus, account features, currencies, and shared network logic.
Friend system backend
CoreAPI includes a built-in backend for friend systems.
It supports:
This is useful for social server features on survival, citybuild, community, or hub-based networks.
Example usage:
Friend API
This screenshot should show the friend request and friendship methods.
View attachment 1316247
It works well as a practical example of how CoreAPI can be used to build a friend plugin or a social player system without creating all backend logic from scratch.
Clan system backend
The API also provides a ready-to-use structure for clan systems.
This includes:
This allows developers to build custom clan systems, clan menus, clan administration commands, or progression systems without needing to rebuild the database logic from scratch.
Example usage:
Clan API
This screenshot should show the clan methods or clan model classes.
View attachment 1316249
View attachment 1316254
It helps buyers immediately understand that CoreAPI is not just a player utility library, but a real backend for clan-based Minecraft systems.
Nickname and profile settings
CoreAPI includes nickname support and flexible profile settings for future systems.
The nickname side supports:
The profile side supports:
This makes the API useful not only for social systems but also for moderation systems, disguise systems, menu preferences, multilingual networks, and extended player profiles.
Example usage:
Nickname and Profile Settings
This screenshot should show the nickname-related methods together with the language and profile setting methods.
View attachment 1316271View attachment 1316267
It works well because it highlights that CoreAPI is extendable and not limited to one single gameplay feature.
MySQL storage
CoreAPI uses MySQL-based persistence for its main backend systems.
This includes storage for:
This makes the API suitable for networks that need consistent and persistent data across restarts or multiple server instances.
Configurable prefixes and setup
CoreAPI also supports customizable prefixes and MySQL settings through the config.
Configurable values include:
Example:
This helps developers and server owners keep all systems visually consistent while still adapting the API to the style of their own network.
Config Setup
This screenshot should show the configurable prefix and MySQL setup.
View attachment 1316272
It is one of the strongest images for non-developers because it clearly shows that CoreAPI can be customized without editing the source code.
Supported platforms
CoreAPI is designed for:
Summary
CoreAPI is a practical Minecraft network API for developers who need one reusable backend for player data, friend systems, clan systems, nickname handling, profile settings, MySQL storage, and configurable prefixes.
If you are building custom Minecraft plugins for Bukkit, Spigot, Paper, or BungeeCord and want one shared backend foundation instead of repeating the same logic in every project, CoreAPI gives you a clean and extensible base.
Modular Minecraft network API for Bukkit, Spigot, Paper, and BungeeCord
CoreAPI is a modular Minecraft backend API designed for developers and server owners who want to manage important network systems through one shared foundation.
Instead of creating separate storage logic and data models for every plugin, CoreAPI gives you one central backend for player data, friend systems, clan systems, nickname handling, profile settings, configurable prefixes, and MySQL storage.
It is meant for custom Minecraft server development and is especially useful for networks that want a reusable Bukkit API, Spigot API, Paper API, or BungeeCord API to power multiple plugins with one consistent backend.
What this product offers
CoreAPI is not just a small utility library. It provides a structured base for real Minecraft systems and can be used as the technical core behind many different plugins.
It includes support for:
- shared player data handling
- friend requests and friendships
- clan members, clan roles, and clan ownership logic
- nickname storage and validation
- profile language and flexible profile settings
- persistent MySQL-backed storage
- configurable core, clan, friend, and nick prefixes
- support for Bukkit-based and BungeeCord-based environments
This makes CoreAPI a strong solution for developers who want to build custom profile systems, social systems, clan systems, rank tools, backend frameworks, or network-wide server systems.
Player data system
CoreAPI provides a shared player model that can be used across different plugins and systems.
The player structure includes values such as:
- UUID
- player name
- prefix
- coins
- friend request settings
- friend message settings
- show server setting
- first join
- last seen
- nickname
- clan
- language
- additional profile settings
This allows developers to use one central player object instead of storing different profile data separately in multiple plugins.
Example usage:
Java:
Optional<Player> player = coreApi.getMySQL().getPlayer(playerUuid.toString());
if (player.isPresent()) {
String name = player.get().getName();
int coins = player.get().getCoins();
String language = player.get().getLanguage();
}Player API
This screenshot fits best with the player model and player-related methods.
View attachment 1316245
It should show how CoreAPI stores and exposes player information for profile systems, menus, account features, currencies, and shared network logic.
Friend system backend
CoreAPI includes a built-in backend for friend systems.
It supports:
- friend requests
- friendship checks
- accepting requests
- denying requests
- removing friends
- favorite friends
- friend-related player settings
This is useful for social server features on survival, citybuild, community, or hub-based networks.
Example usage:
Java:
if (coreApi.getMySQL().hasFriendRequest(playerUuid, requesterUuid)) {
coreApi.getMySQL().acceptFriendRequest(playerUuid, requesterUuid);
}
boolean isFriend = coreApi.getMySQL().isFriend(playerUuid, requesterUuid);Friend API
This screenshot should show the friend request and friendship methods.
View attachment 1316247
It works well as a practical example of how CoreAPI can be used to build a friend plugin or a social player system without creating all backend logic from scratch.
Clan system backend
The API also provides a ready-to-use structure for clan systems.
This includes:
- clan creation
- clan members
- clan roles
- clan requests
- clan lookups
- member promotions
- member demotions
- ownership transfer
This allows developers to build custom clan systems, clan menus, clan administration commands, or progression systems without needing to rebuild the database logic from scratch.
Example usage:
Java:
boolean inClan = coreApi.getMySQL().isInClan(playerUuid);
Optional<Clan> clan = coreApi.getMySQL().getClanOfPlayer(playerUuid);
if (clan.isPresent()) {
coreApi.getMySQL().promoteMember(clan.get(), memberUuid);
}Clan API
This screenshot should show the clan methods or clan model classes.
View attachment 1316249
View attachment 1316254
It helps buyers immediately understand that CoreAPI is not just a player utility library, but a real backend for clan-based Minecraft systems.
Nickname and profile settings
CoreAPI includes nickname support and flexible profile settings for future systems.
The nickname side supports:
- nickname storage
- nickname blacklist checks
- active nicked player handling
- nickname availability checks
The profile side supports:
- language values
- custom profile settings
- key-value based user preferences
This makes the API useful not only for social systems but also for moderation systems, disguise systems, menu preferences, multilingual networks, and extended player profiles.
Example usage:
Java:
boolean available = coreApi.getMySQL().canUseNickname("ShadowPvP");
coreApi.getMySQL().updateLanguage(playerUuid, "en");
coreApi.getMySQL().setProfileSetting(playerUuid, "chat-color", "gold");Nickname and Profile Settings
This screenshot should show the nickname-related methods together with the language and profile setting methods.
View attachment 1316271View attachment 1316267
It works well because it highlights that CoreAPI is extendable and not limited to one single gameplay feature.
MySQL storage
CoreAPI uses MySQL-based persistence for its main backend systems.
This includes storage for:
- player data
- friends
- friend requests
- clans
- clan members
- clan requests
- nicknames
- profile settings
This makes the API suitable for networks that need consistent and persistent data across restarts or multiple server instances.
Configurable prefixes and setup
CoreAPI also supports customizable prefixes and MySQL settings through the config.
Configurable values include:
- MySQL host
- MySQL port
- MySQL database
- MySQL username
- MySQL password
- core prefix
- clan prefix
- friend prefix
- nick prefix
Example:
YAML:
mysql:
host: "localhost"
port: 3306
database: "coreapi"
username: "root"
password: "password"
prefix:
core: "§6Network §8▏ §r"
clan: "§6Clan §8▏ §r"
friend: "§6Friend §8▏ §r"
nick: "§6Nick §8▏ §r"This helps developers and server owners keep all systems visually consistent while still adapting the API to the style of their own network.
Config Setup
This screenshot should show the configurable prefix and MySQL setup.
View attachment 1316272
It is one of the strongest images for non-developers because it clearly shows that CoreAPI can be customized without editing the source code.
Supported platforms
CoreAPI is designed for:
- Bukkit
- Spigot
- Paper
- BungeeCord-based networks
Summary
CoreAPI is a practical Minecraft network API for developers who need one reusable backend for player data, friend systems, clan systems, nickname handling, profile settings, MySQL storage, and configurable prefixes.
If you are building custom Minecraft plugins for Bukkit, Spigot, Paper, or BungeeCord and want one shared backend foundation instead of repeating the same logic in every project, CoreAPI gives you a clean and extensible base.