Combat stays after pvp end, unable to reload
unnamed199cz opened this issue ยท 13 comments
Describe the bug
pvp timer is not showing
people stay in combat after timer ends
pmr reload does not work 2 times then its working (error as screenshot sent)
To reproduce the bug
not sure, just time destroyed it? We had the issues, we restarted the server, it vanished, and after while we have the issues again
Plugin and Server version
[14:02:42 INFO]: Checking version, please wait...
[14:02:42 INFO]: This server is running Paper version 1.21-124-master@df3b654 (2024-08-02T00:02:38Z) (Implementing API version 1.21-R0.1-SNAPSHOT)
You are running the latest version
Previous version: 1.21-109-5a5035b (MC: 1.21)
[14:02:59 INFO]: PvPManager version 3.18.18
[14:02:59 INFO]: A powerful plugin to manage various PvP combat features
[14:02:59 INFO]: Website: https://www.spigotmc.org/resources/pvpmanager-lite.845/
[14:02:59 INFO]: Author: ChanceSD
Screenshots
There has to be another error earlier in the logs, at some point since the server started.
I need that error to be able to tell what happened.
Also the error in screenshot is also cut at the part that would be relevant, the lines after caused by
would provide more details.
Look in your console log files or put them here https://mclo.gs/ so I can search. It should hide all IP addresses
Try this build, hopefully it will print more info when it happens again https://ci.codemc.io/job/ChanceSD/job/PvPManager/395/
There's also this similar error, could be somewhat related to BetterTeams too
[16:00:07] [Craft Scheduler Thread - 20 - BetterTeams/WARN]: [BetterTeams] Plugin BetterTeams v4.9.4 generated an exception while executing task 186743
java.lang.ArrayIndexOutOfBoundsException: null
later on at pmr reload
[19:18:56 ERROR]: Command exception: /pmr reload
org.bukkit.command.CommandException: Unhandled exception executing command 'pmr' in plugin PvPManager v3.18.18
at org.bukkit.command.PluginCommand.execute(PluginCommand.java:47) ~[paper-api-1.21-R0.1-SNAPSHOT.jar:?]
at io.papermc.paper.command.brigadier.bukkit.BukkitCommandNode$BukkitBrigCommand.run(BukkitCommandNode.java:91) ~[paper-1.21.jar:1.21-124-df3b654]
at com.mojang.brigadier.context.ContextChain.runExecutable(ContextChain.java:73) ~[brigadier-1.2.9.jar:?]
at net.minecraft.commands.execution.tasks.ExecuteCommand.execute(ExecuteCommand.java:31) ~[paper-1.21.jar:1.21-124-df3b654]
at net.minecraft.commands.execution.tasks.ExecuteCommand.execute(ExecuteCommand.java:19) ~[paper-1.21.jar:1.21-124-df3b654]
at net.minecraft.commands.execution.UnboundEntryAction.lambda$bind$0(UnboundEntryAction.java:8) ~[paper-1.21.jar:1.21-124-df3b654]
at net.minecraft.commands.execution.CommandQueueEntry.execute(CommandQueueEntry.java:5) ~[paper-1.21.jar:1.21-124-df3b654]
at net.minecraft.commands.execution.ExecutionContext.runCommandQueue(ExecutionContext.java:103) ~[paper-1.21.jar:1.21-124-df3b654]
at net.minecraft.commands.Commands.executeCommandInContext(Commands.java:443) ~[paper-1.21.jar:1.21-124-df3b654]
at net.minecraft.commands.Commands.performCommand(Commands.java:350) ~[paper-1.21.jar:1.21-124-df3b654]
at net.minecraft.commands.Commands.performCommand(Commands.java:337) ~[paper-1.21.jar:1.21-124-df3b654]
at net.minecraft.commands.Commands.performCommand(Commands.java:332) ~[paper-1.21.jar:1.21-124-df3b654]
at net.minecraft.server.network.ServerGamePacketListenerImpl.performUnsignedChatCommand(ServerGamePacketListenerImpl.java:2147) ~[paper-1.21.jar:1.21-124-df3b654]
at net.minecraft.server.network.ServerGamePacketListenerImpl.lambda$handleChatCommand$11(ServerGamePacketListenerImpl.java:2121) ~[paper-1.21.jar:1.21-124-df3b654]
at net.minecraft.server.TickTask.run(TickTask.java:18) ~[paper-1.21.jar:1.21-124-df3b654]
at net.minecraft.util.thread.BlockableEventLoop.doRunTask(BlockableEventLoop.java:151) ~[paper-1.21.jar:1.21-124-df3b654]
at net.minecraft.util.thread.ReentrantBlockableEventLoop.doRunTask(ReentrantBlockableEventLoop.java:24) ~[paper-1.21.jar:1.21-124-df3b654]
at net.minecraft.server.MinecraftServer.doRunTask(MinecraftServer.java:1537) ~[paper-1.21.jar:1.21-124-df3b654]
at net.minecraft.server.MinecraftServer.doRunTask(MinecraftServer.java:201) ~[paper-1.21.jar:1.21-124-df3b654]
at net.minecraft.util.thread.BlockableEventLoop.pollTask(BlockableEventLoop.java:125) ~[paper-1.21.jar:1.21-124-df3b654]
at net.minecraft.server.MinecraftServer.pollTaskInternal(MinecraftServer.java:1514) ~[paper-1.21.jar:1.21-124-df3b654]
at net.minecraft.server.MinecraftServer.pollTask(MinecraftServer.java:1507) ~[paper-1.21.jar:1.21-124-df3b654]
at net.minecraft.util.thread.BlockableEventLoop.runAllTasks(BlockableEventLoop.java:114) ~[paper-1.21.jar:1.21-124-df3b654]
at net.minecraft.server.MinecraftServer.tickServer(MinecraftServer.java:1629) ~[paper-1.21.jar:1.21-124-df3b654]
at net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:1304) ~[paper-1.21.jar:1.21-124-df3b654]
at net.minecraft.server.MinecraftServer.lambda$spin$0(MinecraftServer.java:330) ~[paper-1.21.jar:1.21-124-df3b654]
at java.base/java.lang.Thread.run(Thread.java:1583) ~[?:?]
Caused by: java.lang.ArrayIndexOutOfBoundsException
Alright, so there's different solutions for this issue:
- Set
Nametag Prefix
in config to an empty string like this: '' - Use PvPManager premium or the free v4 version which uses TAB for nametags and avoids this issue
- Try this new dev build if you want to help in further debugging https://ci.codemc.io/job/ChanceSD/job/PvPManager/396/
First one is probably the easiest, and should fully solve the issue as PvPManager will no longer use minecraft teams.
it was both solution 1 and 3, ill try this new thing
also, why nametags have to be disabled, and is there a way it could be enabled in future?
it was both solution 1 and 3, ill try this new thing
also, why nametags have to be disabled, and is there a way it could be enabled in future?
Because with TAB enabled, other plugins can't change nametags, unless they hook into TAB.
And the TAB hook is currently only on premium PvPManager and will be in free version in the future when v4 is out of beta.