Problem/Bug I am trying to use a command for SetHomes v1.2.5 and can't

Discussion in 'Bukkit Help' started by Legoman1000, May 13, 2020.

  1. Offline

    Legoman1000

    So I'm trying to run commands on a Paper server using SetHomes v1.2.5, and commands are bugging out and only certain commands can be ran by certain players. The error log on the console is as follows when it happens.

    Code:
    [01:19:56] [Server thread/ERROR]: null
    org.bukkit.command.CommandException: Unhandled exception executing command 'sethome' in plugin SetHomes v1.2.5
        at org.bukkit.command.PluginCommand.execute(PluginCommand.java:47) ~[patched_1.15.2.jar:git-Paper-262]
        at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:159) ~[patched_1.15.2.jar:git-Paper-262]
        at org.bukkit.craftbukkit.v1_15_R1.CraftServer.dispatchCommand(CraftServer.java:760) ~[patched_1.15.2.jar:git-Paper-262]
        at net.minecraft.server.v1_15_R1.PlayerConnection.handleCommand(PlayerConnection.java:1852) ~[patched_1.15.2.jar:git-Paper-262]
        at net.minecraft.server.v1_15_R1.PlayerConnection.a(PlayerConnection.java:1660) ~[patched_1.15.2.jar:git-Paper-262]
        at net.minecraft.server.v1_15_R1.PacketPlayInChat.a(PacketPlayInChat.java:47) ~[patched_1.15.2.jar:git-Paper-262]
        at net.minecraft.server.v1_15_R1.PacketPlayInChat.a(PacketPlayInChat.java:5) ~[patched_1.15.2.jar:git-Paper-262]
        at net.minecraft.server.v1_15_R1.PlayerConnectionUtils.lambda$ensureMainThread$0(PlayerConnectionUtils.java:23) ~[patched_1.15.2.jar:git-Paper-262]
        at net.minecraft.server.v1_15_R1.TickTask.run(SourceFile:18) ~[patched_1.15.2.jar:git-Paper-262]
        at net.minecraft.server.v1_15_R1.IAsyncTaskHandler.executeTask(IAsyncTaskHandler.java:136) ~[patched_1.15.2.jar:git-Paper-262]
        at net.minecraft.server.v1_15_R1.IAsyncTaskHandlerReentrant.executeTask(SourceFile:23) ~[patched_1.15.2.jar:git-Paper-262]
        at net.minecraft.server.v1_15_R1.IAsyncTaskHandler.executeNext(IAsyncTaskHandler.java:109) ~[patched_1.15.2.jar:git-Paper-262]
        at net.minecraft.server.v1_15_R1.MinecraftServer.ba(MinecraftServer.java:1093) ~[patched_1.15.2.jar:git-Paper-262]
        at net.minecraft.server.v1_15_R1.MinecraftServer.executeNext(MinecraftServer.java:1086) ~[patched_1.15.2.jar:git-Paper-262]
        at net.minecraft.server.v1_15_R1.IAsyncTaskHandler.executeAll(IAsyncTaskHandler.java:95) ~[patched_1.15.2.jar:git-Paper-262]
        at net.minecraft.server.v1_15_R1.MinecraftServer.a(MinecraftServer.java:1220) ~[patched_1.15.2.jar:git-Paper-262]
        at net.minecraft.server.v1_15_R1.MinecraftServer.run(MinecraftServer.java:958) ~[patched_1.15.2.jar:git-Paper-262]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_242]
    Caused by: java.lang.IllegalArgumentException: Name cannot be null
        at org.apache.commons.lang.Validate.notNull(Validate.java:192) ~[patched_1.15.2.jar:git-Paper-262]
        at org.bukkit.craftbukkit.v1_15_R1.CraftServer.getWorld(CraftServer.java:1112) ~[patched_1.15.2.jar:git-Paper-262]
        at com.samleighton.xquiset.sethomes.SetHomes.getPlayersNamedHomes(SetHomes.java:148) ~[?:?]
        at com.samleighton.xquiset.sethomes.commands.SetHome.onCommand(SetHome.java:61) ~[?:?]
        at org.bukkit.command.PluginCommand.execute(PluginCommand.java:45) ~[patched_1.15.2.jar:git-Paper-262]
        ... 17 more
    I have no clue where to start with this or how to fix it. I am completely new to server hosting and I just don't know what I'm doing.
     
    Last edited by a moderator: May 13, 2020
  2. Offline

    timtower Moderator Moderator

    @Legoman1000 That is a programming error.
    Tell the developer about it.
     
  3. Offline

    Firestare

    maybe not, in the cause section of the error log it says "name cannot be null", you may need to set a name for your home.

    I never used that plugin, so I don't know the syntax but try using something along the lines of

    "/sethome {name}"
     
  4. Offline

    timtower Moderator Moderator

    @Firestare Still, developer should have caught that error.
     

Share This Page