Tags
Creators
Details
Licensed GPL-3.0-only
Published 6 months ago
Updated 4 hours ago
All versions
0.1.9a
Release
Allium v0.1.9a5 months ago 13
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
1.20.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
Wiki: https://github.com/castledking/Allium/wiki
Highlights
- Citizens NPC body visibility fixed — Allium no longer strips unlisted
PLAYER_INFO_UPDATEentries for unknown player UUIDs. Citizens uses those packets to send player-NPC profile/skin data while keeping NPCs out of the tab list; removing them made the client fail to render NPC bodies. NPCs are also exempted from PartyManager body visibility hiding. - CrowBarDataSender UUID fix — Fixed a bug where the loop variable
uuid(a String) was being used instead ofplayer.getUniqueId(), causing all CrowBar clients to receive the same UUID for every player entry.
What's Fixed
- Citizens NPC bodies no longer invisible — The confirmed fix is in the PacketEvents tab-list interceptor: unknown/unlisted player-info entries now pass through unchanged instead of being removed. This preserves Citizens' spawn/profile handshake for player-type NPCs. Allium also detects Citizens NPC metadata live and skips
hidePlayer()visibility management for those NPC entities. - CrowBarDataSender player UUID — Each player object now correctly calls
player.getUniqueId().toString(). Previously, a strayuuidvariable from an unrelated context was serialized for every entry, meaning all players appeared as the same entity on the CrowBar locator bar.
Internal
.release/discord-updater-webhook.yml—message_idupdated for the current Discord release post..release/src/spigot-release.js— Modrinth download link corrected.
Requirements
- Minecraft 1.21.11
- Fabric Loader 0.18.4 or newer
- Fabric API 0.141.4 or newer
- Java 21
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible version
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:ygnk0YMD:xZL8YoBT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ygnk0YMD:xZL8YoBT"
}

