Allium v0.2.6a

Wiki: https://github.com/castledking/Allium/wiki

Highlights

• Paper Brigadier compatibility — CommandManager now correctly handles commands registered via Paper's LifecycleEvents.COMMANDS (e.g., AbyssalLib's CommandBus, custom Brigadier dispatcher commands). These commands appear as VanillaCommandWrapper in the command map, whose testPermissionSilent() can false-negative. Allium now allows these commands through and defers permission evaluation to the server's native Brigadier dispatch.
• Derived permission scoped to Allium-owning plugins only — The legacy heuristic that produced synthetic permissions like <pluginName>.<commandName> is now only applied to commands owned by Allium itself. For all other plugins — whether PluginCommand, VanillaCommandWrapper, or custom wrappers — Allium trusts the command's native permission system.

Technical Details

Problem

Commands registered through Paper's modern LifecycleEvents.COMMANDS API (used by AbyssalLib's CommandBus, among others) do not go through Bukkit's plugin.yml command registration. Instead, they register LiteralArgumentBuilder<CommandSourceStack> nodes directly into Mojang's Brigadier CommandDispatcher.

Paper wraps these dispatcher-only nodes in VanillaCommandWrapper (org.bukkit.craftbukkit.command.VanillaCommandWrapper) so they appear in SimpleCommandMap.knownCommands for Bukkit API compatibility. However, VanillaCommandWrapper.testPermissionSilent() does not reliably evaluate the underlying Brigadier node's requires() predicates, often returning false even when the player holds the correct permission.

This caused Allium's CommandManager to block all such commands and display the Allium "no-permission" message, even when the command's native permission system would have allowed execution.

Attempted Fixes (Rejected)

1. Class name matching (className.contains("Brigadier") || className.contains("Wrapper")) — fragile, case-sensitive, and misses VanillaCommandWrapper in the general case since the wrapper extends Command/PluginCommand via different paths depending on the Paper version.
2. PluginIdentifiableCommand instanceof check — Paper's MinecraftCommandMap$CommandWrapper may implement PluginIdentifiableCommand with a null plugin, making the check useless.
3. PluginCommand instanceof check — some Paper wrapper variants extend PluginCommand directly, so negating PluginCommand doesn't reliably capture dispatcher-only commands.

Actual Fix

The fix uses a class-name-exact check for VanillaCommandWrapper as the first gate in hasPermissionForCommand():

if (className.contains("VanillaCommandWrapper")) {
    return true;
}

This immediately allows all Brigadier-dispatcher-registered commands and defers permission evaluation to the server's native dispatch (which correctly evaluates the CommandNode.canUse() predicates at execution time).

For PluginCommand instances, the revised logic is:

1. Explicit permission set — command.getPermission() is non-null → testPermissionSilent already checked it, allow.
2. Derived permission — only computed for commands whose PluginIdentifiableCommand.getPlugin() returns "Allium". The derived string is allium.<baseCommand>.
3. All other commands (PluginCommand from other plugins, vanilla commands with matching Bukkit wrappers) — trust testPermissionSilent.

getPluginForCommand Fallback Fix

The fallback in getPluginForCommand previously returned commandName.toLowerCase() when no plugin could be identified, causing the derived permission to be <commandName>.<commandName> (e.g., relique.relique). This is now null, which propagates through getDerivedPluginCommandPermission as null — treated as "no permission required".

Support and Feedback

Issues: https://github.com/castledking/Allium/issues Wiki: https://github.com/castledking/Allium/wiki Discord: https://discord.com/invite/pCKdCX6nYr Website: https://castled.codes/

Allium v0.2.5a

Wiki: https://github.com/castledking/Allium/wiki

Highlights

• Translation probe config corruption fixed — applyBundledDefaults no longer calls config.save(), preventing the old JAR's defaults from being written to disk on every restart. A new seedMissingProbeConfig() method writes the translation-probe section to disk only when the file actually lacks it (using contains(path, true) to ignore in-memory defaults).
• Hardcoded probe check fallback — loadChecks() now cascades: disk config → bundled resource → createDefaultChecks() with 16 hardcoded checks (meteor + 14 IPN + 2 libIPN). This ensures the probe always has checks even when both the disk config and old JAR resource lack the section.
• Probe enabled fallback — isEnabled() now falls back to root enabled, so the probe registers even when the translation-probe section is entirely absent from the config file.
• Stealthier probe — CloseWindow is sent immediately (no 2-tick delay, sign GUI never renders), and the sign position is Y - 30 below the player (out of view). Zero visual flicker.
• /allium modguard reload — New command unregisters the probe, reloads the config from disk, and re-registers. Requires allium.admin.

Bug Fixes

Files Changed (4)

Technical Details

Config Persistence Chain

The old code had two bugs forming a corruption loop:

1. applyBundledDefaults called config.save() with the old JAR's bundled config (no translation-probe section), overwriting user changes on every restart
2. Even after removing config.save(), seedMissingProbeConfig checked config.contains("translation-probe") — but applyBundledDefaults had already set the NEW bundled resource as defaults, which DO contain the section. So contains() returned true from defaults and seedMissingProbeConfig returned early without persisting

Fix: seedMissingProbeConfig now uses config.contains("translation-probe", true) to skip default-only matches. It also writes the full 16-check section to disk when absent, so subsequent restarts load it directly from the file.

Probe Check Fallback Chain

loadChecks() now follows this order:

1. config().getConfigurationSection("translation-probe.checks") — reads from the in-memory config (loaded from disk or defaults)
2. loadBundledChecks() — reads from the JAR resource (modguard/config.yml) and copies checks into the in-memory config
3. createDefaultChecks() — 16 hardcoded checks: meteor + 14 IPN (key.inventoryprofiles.*) + 2 libIPN

This ensures the probe always has checks regardless of which JAR version is deployed or whether the config file contains the section.

Support and Feedback

Issues: https://github.com/castledking/Allium/issues Wiki: https://github.com/castledking/Allium/wiki Discord: https://discord.com/invite/pCKdCX6nYr Website: https://castled.codes/

Allium v0.2.4a

Wiki: https://github.com/castledking/Allium/wiki

Highlights

• Vault softdepend crash fixed — Allium no longer crashes at startup when Vault is absent. All Vault-typed fields and method signatures were changed to Object, with casts at call sites. VaultEconomyProvider is only created when Vault's Economy class is actually loadable. The FormatChatListener is skipped entirely when Vault Chat isn't available.
• PacketEvents softdepend crash fixed — Allium no longer crashes at startup when PacketEvents is absent. The Glow command and GlowListener are guarded behind isPacketEventsAvailable(), and the glowCommand field was relaxed from Glow to Object to prevent class loading.
• CrowBar 128-block radius limit removed — Added shouldBeVisibleIgnoreDistance to PartyManager so players beyond 128 blocks remain visible on the locator bar, with only same-world and forced-visibility checks applied.
• NPC locator bar flash fixed — PartyManager.updatePlayerVisibility now checks viewer.canSee(target) before calling showPlayer, preventing NPC info packets from being resent every 5 ticks when the NPC is already visible.

Bug Fixes

Files Changed (8)

Technical Details

Vault Class Loading Fix

Paper 1.21+'s PluginClassLoader eagerly resolves type references during class definition. Having Vault types in field declarations or method return types causes NoClassDefFoundError even when the code path never executes. Fix: all Vault-typed fields and return types are now Object, with casts at every call site.

PacketEvents Class Loading Fix

Same mechanism as Vault — PacketEvents types in Glow's method signatures crash class loading. Glow is now only instantiated when isPacketEventsAvailable() returns true, so the class is never loaded on servers without PacketEvents.

Support and Feedback

Issues: https://github.com/castledking/Allium/issues Wiki: https://github.com/castledking/Allium/wiki Discord: https://discord.com/invite/pCKdCX6nYr Website: https://castled.codes/

Wiki: https://github.com/castledking/Allium/wiki

Highlights

• CanvasMC 26.2 support — Migrated from Paper API to Canvas API (io.canvasmc.canvas:canvas-api). Canvas is a Folia fork targeting Minecraft 26.2 (build 835). All scheduling now goes through the new SchedulerAdapter in the codes.castled.allium.scheduler package, which properly handles Canvas's regionized threading model.
• New SchedulerAdapter — Complete rewrite of the scheduling layer. The old util/SchedulerAdapter.java (587 lines of reflection-heavy Folia detection) is replaced by a clean 426-line scheduler/SchedulerAdapter.java with a dedicated TaskHandle abstraction. The old class is kept as a deprecated thin wrapper delegating to the new one, ensuring backward compatibility.
• Tab completion API — New AlliumTabCompletionsEvent + AlliumTabCompletionsListener that populate tab completions with all online non-vanished players when PartyManager is enabled. Other plugins can fire this event to get Allium-aware player name suggestions.
• Vault initialization guard — Fixed a race condition where registerVaultDependentListeners() could be called multiple times if Vault initialized successfully and then the retry timer fired again. Added a registered boolean flag to ensure one-time registration.
• FAWE removed — FastAsyncWorldEdit dependency and repositories dropped from pom.xml. No longer a soft dependency.

Minecraft Version Support

API / Dependency Changes

• pom.xml: io.papermc.paper:paper-api replaced with io.canvasmc.canvas:canvas-api
• pom.xml: <paper.version> bumped from 26.2.build.37-alpha to 26.2.build.835-alpha
• pom.xml: Added canvasmc-releases and canvasmc-snapshots repositories
• pom.xml: Removed FastAsyncWorldEdit-Core dependency
• pom.xml: Removed IntellectualSites repositories
• plugin.yml: Removed FastAsyncWorldEdit and WorldEdit from softdepend

New Files

SchedulerAdapter API

The new codes.castled.allium.scheduler.SchedulerAdapter provides:

// Global (main thread equivalent)
SchedulerAdapter.runGlobal(plugin, runnable)
SchedulerAdapter.runLaterGlobal(plugin, runnable, delayTicks)
SchedulerAdapter.runRepeatingGlobal(plugin, runnable, delayTicks, periodTicks)

// Async
SchedulerAdapter.runAsyncNow(plugin, runnable)
SchedulerAdapter.runAsyncLater(plugin, runnable, delayTicks)
SchedulerAdapter.runAsyncRepeating(plugin, runnable, delayTicks, periodTicks)

// Entity (Folia entity scheduler, Bukkit fallback)
SchedulerAdapter.runEntity(plugin, entity, runnable, retired)
SchedulerAdapter.runLaterEntity(plugin, entity, runnable, delayTicks)
SchedulerAdapter.runEntityRepeating(plugin, entity, runnable, retired, delayTicks, periodTicks)

// Location (Folia region scheduler, Bukkit fallback)
SchedulerAdapter.runAtLocation(plugin, location, runnable)
SchedulerAdapter.runAtLocationLater(plugin, location, runnable, delayTicks)
SchedulerAdapter.runAtLocationRepeating(plugin, location, runnable, delayTicks, periodTicks)

// Utility
SchedulerAdapter.cancelTasks(plugin)
SchedulerAdapter.isFolia()

All methods return codes.castled.allium.scheduler.TaskHandle which wraps both BukkitTask and Folia's ScheduledTask.

Deprecated API

codes.castled.allium.util.SchedulerAdapter is now a deprecated wrapper. All methods delegate to the new codes.castled.allium.scheduler.SchedulerAdapter. Existing code continues to work but should be migrated:

Files Changed (31)

Technical Details

Scheduler Detection

Folia/Canvas detection uses Bukkit.getServer().getClass().getMethods() to find getGlobalRegionScheduler — more reliable than string-matching server name/version. The detection result is cached in a static final boolean at class load time.

TaskHandle

Wraps either a BukkitTask (Paper/Spigot path) or a raw Folia ScheduledTask object (accessed via reflection for cancel). Thread-safe cancellation via AtomicBoolean. The isScheduled() method returns best-effort status.

Vault Initialization Fix

Previously, if initializeVault() succeeded on attempt N but the timer tick was already queued, registerVaultDependentListeners() could fire twice. The fix adds a registered[] boolean flag checked before each registration call, ensuring idempotency.

Support and Feedback

Issues: https://github.com/castledking/Allium/issues Wiki: https://github.com/castledking/Allium/wiki Discord: https://discord.com/invite/pCKdCX6nYr Website: https://castled.codes/

Wiki: https://github.com/castledking/Allium/wiki

Highlights

• Glow command — New /glow command for per-player colored glow outlines using PacketEvents virtual team packets. Supports all 16 vanilla colors, rainbow cycling, and per-color permissions. No scoreboard pollution — teams are sent directly to viewers and never registered on any Bukkit scoreboard.
• Join/Quit message permissions — Permission-based join/quit message formats via allium.join_message.<id> and allium.quit_message.<id>. Set custom formats with LuckPerms metadata.
• Chat system rewrite — ChatMessageManager, FormatChatListener, and PacketChatTrackerImpl significantly reworked for better PacketEvents integration and staff moderation features.
• Flight restoration refactor — FlightRestoration rewritten for improved Folia compatibility and reliability.
• Command management — CommandManager now caches the server's known commands map with a 2-second TTL, eliminating repeated reflection calls. Help command caches available commands per-player with a 3-second TTL.
• TP companion teleportation — Pet/entity teleport-on-TP moved from TP listener to dedicated TeleportBackListener for cleaner separation.
• Inventory snapshot optimization — InventoryManager.saveSnapshot() simplified to run directly on the calling thread instead of through SchedulerAdapter.run().

New Commands

New Permissions

New Config

join-and-quit-messages:
  join:
    enabled: true
    format: "&e%name% &7has joined the server"
  quit:
    enabled: true
    format: "&e%name% &7has left the server"
  broadcast-scope: server  # server, world, or global

Setting Custom Join/Quit Messages with LuckPerms

Set a permission with a metadata value on a player:

/lp user <player> meta set allium.join_message.vip.a "rift in the universe has spawned %player%"
/lp user <player> meta set allium.quit_message.vip.a "%player% has left through a rift"

Supported placeholders: %name% (display name, respects /nick), %player% (real name), %prefix% (Vault prefix), %suffix% (Vault suffix).

The first matching permission (alphabetical by suffix) is used. If no permission metadata is found, the default config format is used.

Technical Details

Glow

• Uses PacketEvents WrapperPlayServerTeams with TeamMode.CREATE (includes both team info and player entries in one packet)
• TeamMode.UPDATE for rainbow color changes, TeamMode.REMOVE for cleanup
• Packets sent to all online players including the target (the client needs to receive the team packet to render the colored outline)
• No Bukkit.getScoreboardManager() usage — completely virtual
• Folia-safe: no region-scheduled tasks needed

Join/Quit Messages

• Handled via standard PlayerJoinEvent / PlayerQuitEvent (main thread on both Bukkit and Folia)
• Permission metadata read through Vault Chat's getPlayerInfoString()
• Falls back to default config format if no permission match found
• Vanish check: vanished players don't show join/quit messages

Chat System

• ChatMessageManager rewritten with improved message storage and retrieval
• PacketChatTrackerImpl updated for better PacketEvents 2.11.1 compatibility
• FormatChatListener significantly expanded with new formatting options

SchedulerAdapter

• All scheduled tasks route through SchedulerAdapter which auto-detects Folia
• Folia path: uses EntityScheduler for entity-specific tasks, GlobalRegionScheduler for global tasks
• Bukkit path: uses standard BukkitScheduler
• No raw Bukkit.getScheduler() calls in new code

Files Changed (22)

Support and Feedback

Issues: https://github.com/castledking/Allium/issues Wiki: https://github.com/castledking/Allium/wiki Discord: https://discord.com/invite/pCKdCX6nYr Website: https://castled.codes/

Wiki: https://github.com/castledking/Allium/wiki

Highlights

• CrowBar same-world payloads — CrowBar player data is now built per recipient and only includes players in the recipient's current world.
• CrowBar quit refresh — Sends an immediate snapshot when a player quits so CrowBar clients can remove stale dots and name tags without waiting for expiry.
• CrowBar join/world snapshots — Sends delayed targeted snapshots after joins and world changes so reconnecting CrowBar clients get nearby player positions before movement updates.
• NPC filtering — Citizens NPCs are excluded from CrowBar player-data payloads.

Support and Feedback

Issues: https://github.com/castledking/Allium/issues Wiki: https://github.com/castledking/Allium/wiki Discord: https://discord.com/invite/pCKdCX6nYr Website: https://castled.codes/

Allium v0.2.0a

Wiki: https://github.com/castledking/Allium/wiki

Highlights

• CrowBarDataSender NPC Filter — Prevents NPCs from Citizens from having their data sent to CrowBar

Support and Feedback

Issues: https://github.com/castledking/Allium/issues Wiki: https://github.com/castledking/Allium/wiki Discord: https://discord.com/invite/pCKdCX6nYr Website: https://castled.codes/

Wiki: https://github.com/castledking/Allium/wiki

Highlights

• Citizens NPC body visibility fixed — Allium no longer strips unlisted PLAYER_INFO_UPDATE entries 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 of player.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 stray uuid variable 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_id updated 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