Tags
Creators
Details
Licensed GPL-3.0-only
Published 5 months ago
Updated 18 hours ago
All versions
2.1-RELEASE
Release
LuckTAB 2.1-RELEASE4 months ago 466
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Required content
Any compatible version
Changes
LuckTAB v2.1-RELEASE
Lightweight yet powerful tab list, chat format & scoreboard plugin — all configurable in a single config.yml.
Changelog
- Added
/lucktab migrate to-luckperms— pushes all prefixes, suffixes and group weights from config into LuckPerms. Weight is calculated automatically: top rank = 200, each rank below -10 - Added
/lucktab migrate from-luckperms— pulls all prefixes and suffixes from LuckPerms groups into config - Added
prefix-source: luckpermsconfig option — read prefix/suffix directly from LuckPerms player meta instead of config. Correctly resolves inheritance and priorities - Fixed
prefix-source: luckpermsreading from group cache instead of player meta — inheritance now works correctly - Fixed scoreboard line order breaking when line count changes
- Fixed resource leak in update checker — connection now always closed in finally block
- Fixed regex patterns recompiling on every call — now
static finalconstants - Fixed team options (
NAME_TAG_VISIBILITY,COLLISION_RULE) being set every tick — now only on team creation - Fixed migration overwriting other plugins' prefix/suffix nodes — only LuckTAB-managed nodes (matching priority) are removed
New Commands
| Command | Permission | Description |
|---|---|---|
/lucktab migrate to-luckperms |
lucktab.migrate |
Push config prefixes to LuckPerms |
/lucktab migrate from-luckperms |
lucktab.migrate |
Pull LuckPerms prefixes to config |
New Config Option
# lucktab → use prefixes from config (default)
# luckperms → use prefixes directly from LuckPerms meta
prefix-source: lucktab
Dependencies
- LuckPerms — required
- PlaceholderAPI — optional
Support
Join our Discord: dc.gg/paperstream
Author: LucasTHCR
Optional dependencies
Any compatible version
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:MzWKBKRk:6yztfJ7k"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MzWKBKRk:6yztfJ7k"
}

