Chunky (Bukkit)

Chunky (Bukkit)

20.6k Downloads

Error setting worldborder size with different world sizes

Closed this issue ยท 6 comments

commented

I'm using the latest version of Chunky v1.4.40 for Minecraft version 1.21.7 on my personal server with friends. We've set a different maximum size for each Minecraft world. For example, it's 20,000 for the overworld, 2500 for the nether, and 10,000 for the end.

When I try to preload the different worlds with Chunky, I use "/chunky world world" to select the overworld, and when I type "/chunky worldborder", the following error appears in the server console. The exact same thing happens for all other worlds.

[14:27:16 ERROR]: Command exception: /chunky worldborder org.bukkit.command.CommandException: Unhandled exception executing command 'chunky' in plugin Chunky v1.4.40 at org.bukkit.command.PluginCommand.execute(PluginCommand.java:47) ~[paper-api-1.21.7-R0.1-SNAPSHOT.jar:?] at io.papermc.paper.command.brigadier.bukkit.BukkitCommandNode$BukkitBrigCommand.run(BukkitCommandNode.java:83) ~[paper-1.21.7.jar:1.21.7-17-b4466ec] at com.mojang.brigadier.context.ContextChain.runExecutable(ContextChain.java:73) ~[brigadier-1.3.10.jar:?] at net.minecraft.commands.execution.tasks.ExecuteCommand.execute(ExecuteCommand.java:30) ~[paper-1.21.7.jar:1.21.7-17-b4466ec] at net.minecraft.commands.execution.tasks.ExecuteCommand.execute(ExecuteCommand.java:13) ~[paper-1.21.7.jar:1.21.7-17-b4466ec] at net.minecraft.commands.execution.UnboundEntryAction.lambda$bind$0(UnboundEntryAction.java:8) ~[paper-1.21.7.jar:1.21.7-17-b4466ec] at net.minecraft.commands.execution.CommandQueueEntry.execute(CommandQueueEntry.java:5) ~[paper-1.21.7.jar:1.21.7-17-b4466ec] at net.minecraft.commands.execution.ExecutionContext.runCommandQueue(ExecutionContext.java:105) ~[paper-1.21.7.jar:1.21.7-17-b4466ec] at net.minecraft.commands.Commands.executeCommandInContext(Commands.java:451) ~[paper-1.21.7.jar:1.21.7-17-b4466ec] at net.minecraft.commands.Commands.performCommand(Commands.java:357) ~[paper-1.21.7.jar:1.21.7-17-b4466ec] at net.minecraft.commands.Commands.performCommand(Commands.java:345) ~[paper-1.21.7.jar:1.21.7-17-b4466ec] at net.minecraft.commands.Commands.performPrefixedCommand(Commands.java:336) ~[paper-1.21.7.jar:1.21.7-17-b4466ec] at net.minecraft.server.dedicated.DedicatedServer.handleConsoleInputs(DedicatedServer.java:435) ~[paper-1.21.7.jar:1.21.7-17-b4466ec] at net.minecraft.server.dedicated.DedicatedServer.tickConnection(DedicatedServer.java:386) ~[paper-1.21.7.jar:1.21.7-17-b4466ec] at net.minecraft.server.MinecraftServer.tickChildren(MinecraftServer.java:1738) ~[paper-1.21.7.jar:1.21.7-17-b4466ec] at net.minecraft.server.MinecraftServer.tickServer(MinecraftServer.java:1530) ~[paper-1.21.7.jar:1.21.7-17-b4466ec] at net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:1252) ~[paper-1.21.7.jar:1.21.7-17-b4466ec] at net.minecraft.server.MinecraftServer.lambda$spin$2(MinecraftServer.java:310) ~[paper-1.21.7.jar:1.21.7-17-b4466ec] at java.base/java.lang.Thread.run(Thread.java:1575) ~[?:?] Caused by: java.lang.NoClassDefFoundError: com/wimbli/WorldBorder/Config at Chunky-Bukkit-1.4.40.jar/org.popcraft.chunky.integration.WorldBorderIntegration.hasBorder(WorldBorderIntegration.java:12) ~[Chunky-Bukkit-1.4.40.jar:?] at Chunky-Bukkit-1.4.40.jar/org.popcraft.chunky.command.WorldBorderCommand.setBorderViaIntegration(WorldBorderCommand.java:72) ~[Chunky-Bukkit-1.4.40.jar:?] at Chunky-Bukkit-1.4.40.jar/org.popcraft.chunky.command.WorldBorderCommand.execute(WorldBorderCommand.java:39) ~[Chunky-Bukkit-1.4.40.jar:?] at Chunky-Bukkit-1.4.40.jar/org.popcraft.chunky.ChunkyBukkit.onCommand(ChunkyBukkit.java:98) ~[Chunky-Bukkit-1.4.40.jar:?] at org.bukkit.command.PluginCommand.execute(PluginCommand.java:45) ~[paper-api-1.21.7-R0.1-SNAPSHOT.jar:?] ... 18 more Caused by: java.lang.ClassNotFoundException: com.wimbli.WorldBorder.Config at org.bukkit.plugin.java.PluginClassLoader.loadClass0(PluginClassLoader.java:205) ~[paper-api-1.21.7-R0.1-SNAPSHOT.jar:?] at org.bukkit.plugin.java.PluginClassLoader.loadClass(PluginClassLoader.java:172) ~[paper-api-1.21.7-R0.1-SNAPSHOT.jar:?] at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:528) ~[?:?] at Chunky-Bukkit-1.4.40.jar/org.popcraft.chunky.integration.WorldBorderIntegration.hasBorder(WorldBorderIntegration.java:12) ~[Chunky-Bukkit-1.4.40.jar:?] at Chunky-Bukkit-1.4.40.jar/org.popcraft.chunky.command.WorldBorderCommand.setBorderViaIntegration(WorldBorderCommand.java:72) ~[Chunky-Bukkit-1.4.40.jar:?] at Chunky-Bukkit-1.4.40.jar/org.popcraft.chunky.command.WorldBorderCommand.execute(WorldBorderCommand.java:39) ~[Chunky-Bukkit-1.4.40.jar:?] at Chunky-Bukkit-1.4.40.jar/org.popcraft.chunky.ChunkyBukkit.onCommand(ChunkyBukkit.java:98) ~[Chunky-Bukkit-1.4.40.jar:?] at org.bukkit.command.PluginCommand.execute(PluginCommand.java:45) ~[paper-api-1.21.7-R0.1-SNAPSHOT.jar:?] ... 18 more [14:27:16 INFO]: An unexpected error occurred trying to execute that command

I don't know exactly if it's an error in Paper, which is the loader I use, or in the plugin itself.

For any questions, do not hesitate to write to me, greetings

commented

Hi, sorry for the delayed response. I believe this has to do with the WorldBorder plugin being installed, either an outdated or modified version of it. Can you check if this is the case?

For more quick help, I recommend joining the Discord server as troubleshooting is usually faster there.

commented

No, I don't have any plugins that use WorldBorder. I configured everything manually using the /worldborder commands in the different worlds.

The only plugin I use besides Chunky is SkinsRestorer. I don't think it has anything to do with it.

Greetings, I await your response.

commented

Does this happen if you try again? I have seen weird class loading issues in the past. Sometimes they are one-off.

If you can reproduce this consistently, please share details on your setup and I will try to reproduce. Otherwise, there might not actually be anything I can follow up on from my end, as this hasn't been reported by anyone else so far.

commented

I understand this may be an isolated case. I'll try to replicate it later. I'll record a video of the exact steps I followed and share it with you on Google Drive.

When I have it, I'll write to you on this same post.

Best regards.

commented

Hi, I couldn't replicate it while making the video. I copied all the settings to a new test server and followed the steps I took, and the error doesn't occur.

You may be right, and it's an isolated issue that occurred for some reason I don't understand. On the server where it occurred, I replicated it again, but this time nothing happens; everything works as expected.

Sorry for the inconvenience. If it happens again in the future, I won't hesitate to report it so this fantastic plugin can continue to improve and grow.

Thank you very much for your attention, and best regards.

commented

Thank you for testing. That's somewhat what I expected, I'm not sure what causes these sorts of issues, but it is rare enough that I don't see it as an issue. The WorldBorder code is mostly there for compatibility though, it can likely be removed at some point in the near future as I don't believe there are many using this anymore since it has been abandoned.