1.0.0
Compatibility
Changes
๐ท๏ธ ApoTags v1.0.0 โ Official beta
Welcome to the first stable release of ApoTags! This version introduces a powerful, lightweight, and highly customizable RGB tag management system for modern Minecraft servers.
โจ Key Features
- Full RGB Support: Native support for Hex codes (
&#RRGGBB) and legacy color codes across all tags and messages. - Interactive GUIs: * Player Menu: A clean, paginated inventory for players to browse and equip their earned tags.
- Admin Panel: Manage, enable, or disable tags in-game with simple clicks.
- Smart Storage: Choose between H2 (high-performance embedded database) or FlatFile (YAML) to suit your server's needs.
- PlaceholderAPI Integration: Use
%apotags_tag%to display active tags in chat, tab-lists, scoreboards, or holograms. - Total Customization: Fully editable GUI files (
gui_user.yml&gui_admin.yml) with Custom Model Data support for resource packs. - Multi-language: Built-in support for English and Spanish.
๐ ๏ธ Administration & Commands
- In-game Editor: Create and modify tags without opening files using
/tags create,/tags setdisplay, and/tags setdesc. - Live Reload: Apply any configuration change instantly with
/tags reload. - Granular Permissions: Full control over every subcommand and individual tag access (
apotags.tag.<ID>).
๐ง Technical Specifications
- Requirements: Built for Paper 1.19.4+ and Java 17+.
- Modern Rendering: Powered by Adventure (Kyori) for flawless text display.
- Performance: Optimized data loading to ensure zero impact on the main server thread.
Developer: ApoloCR
Support: Join our Discord or contact itzapolocr for assistance.
Optional dependencies
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:NcX1MoVL:x3hE6sGM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NcX1MoVL:x3hE6sGM"
}

