Skip to content

TAB 6.0.0 crashes on /tab reload with Paper 1.21.11 (Player head component error) #1637

@jonathanthxd

Description

@jonathanthxd

Server version

Paper 1.21.11

TAB version

6.0.0

Plugin list

ℹ Server Plugins (40):
[14:11:05 INFO]: Paper Plugins (6):
[14:11:05 INFO]: - FancyDialogs, FancyEconomy, FancyHolograms, FancyNpcs, FancyTags, nightcore
[14:11:05 INFO]: Bukkit Plugins (34):
[14:11:05 INFO]: - AxAFKZone, AxGraves, AxInventoryRestore, AxMines, AxShulkers, AxTrade, BannerMOTDplus, BetterView, DGlogin, ExcellentCrates
[14:11:05 INFO]: ExoShopkeepers, FastAsyncWorldEdit, FreedomChat, GSit, ItemEdit, ItemTag, JustCombat, LPC-Pro, LuckPerms, Multiverse-Core
[14:11:05 INFO]: packetevents, PlaceholderAPI, simplespawn, SkinsRestorer, StarAC, TAB, TimeBlockEraser, UltraReporty, VanguardClans, Vault
[14:11:05 INFO]: ViaBackwards, ViaVersion, VoidGen, WorldGuard

Describe the bug

When running the command "/tab reload" in-game, the plugin fails to enable and throws an IllegalStateException related to player head components.

The plugin works correctly on server startup and also when executing "/tab reload" from the console. The issue only occurs when the command is executed by a player in-game.

Expected behavior

The "/tab reload" command should reload the plugin safely without throwing any errors, regardless of whether it is executed from the console or in-game.

Steps to reproduce

  1. Start the server with TAB 6.0.0 on Paper 1.21.11.
  2. Join the server as a player.
  3. Execute the command "/tab reload".
  4. The plugin fails and logs an IllegalStateException.

Additional info

  • TAB version: 6.0.0
  • Server software: Paper 1.21.11
  • The configuration was freshly generated (default config, no modifications).
  • Layout feature is disabled.
  • No custom head components are configured.
  • The issue does not occur when running "/tab reload" from the console.
  • Error message:
    java.lang.IllegalStateException: Player head component does not have id, name or skin set

This suggests a possible issue with component re-initialization during reload, potentially related to player head rendering or MiniMessage parsing.

Checklist

  • I am running latest version of the plugin
  • I have read the wiki to make sure it's not an issue with configuration
  • I ticked all of the boxes without actually reading them
  • I have read the Compatibility wiki page and am not trying to run the plugin on an unsupported server version / platform
  • I am willing to cooperate to get this issue resolved faster, including providing any additional information requested or testing new builds

Metadata

Metadata

Assignees

No one assigned

    Labels

    On hold: Insufficient infoNot enough information was providedType: BugPlugin is not working as described on the wiki

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions