@Greeniousity The plugin instance passed to the scheduler is null. Does the name in the plugin.yml match the string supplied to the...
@Greeniousity This line: playerData data = new playerData(); is creating a new instance. This is where you'll have to retrieve the instance stored...
You're creating a new instance in the local scope; the join event does nothing here. I assume you want a single instance of the playerData class...
Considering this, the condition is either false or the #boostSetup method does nothing. Assuming the condition is true and the #boostSetup simply...
@Greeniousity You reverted the change. You should still check if the item is (not) null. Add that back in (still as the first condition), then...
@timtower The ItemMeta#getDisplayName() method is annotated as @NotNull. I went to check the source code, and it should just return an empty...
@Greeniousity InventoryClickEvent#getCurrentItem() is @Nullable; it returns null when there is no item at the current slot. Make sure you don't...
@Greeniousity Assuming you print a message to the console upon the event triggering and that messages isn't coming up (as mentioned earlier),...
@Greeniousity Yes, you're currently registering the listener instance in the constructor, but if you never create this instance, it will not be...
Did you create an instance of this class ("boosters") upon the plugin being enabled (i.e. the onEnable method of your main class)? By the way, you...
@Rival54548545 Assuming you want player input from the chat, you can listen for the AsyncPlayerChatEvent. You can cancel the event to prevent the...
@Zunynz I don't believe the server receives any indication of the player interacting with an item that cannot be picked up. I see two immediate...
@Zunynz You can listen for the EntityPickupItemEvent, then check if the item entity is one of your dropped blocks.
I believe they're requesting a feature that allows unbanning (pardoning) of the player in guise of a resurrection.
According to Vault's README, LuckPerms is supported. Vault should handle any version-dependent code, so you can probably just go ahead by hooking...
Separate names with a comma.