Solved Help command not working when Op'd (Direwolf20)

  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

Lutia

New Member
Jul 29, 2019
2
0
0
I'm running into an issue on a server where whenever someone is Op'd (or is the server themselves) the help command doesn't work and spits out a stack trace.

Code:
[13:24:58] [Server thread/ERROR]: Couldn't process command: '?'
java.lang.IllegalArgumentException: Comparison method violates its general contract!
    at java.util.ComparableTimSort.mergeHi(Unknown Source) ~[?:1.8.0_25]
    at java.util.ComparableTimSort.mergeAt(Unknown Source) ~[?:1.8.0_25]
    at java.util.ComparableTimSort.mergeCollapse(Unknown Source) ~[?:1.8.0_25]
    at java.util.ComparableTimSort.sort(Unknown Source) ~[?:1.8.0_25]
    at java.util.Arrays.sort(Unknown Source) ~[?:1.8.0_25]
    at java.util.Arrays.sort(Unknown Source) ~[?:1.8.0_25]
    at java.util.ArrayList.sort(Unknown Source) ~[?:1.8.0_25]
    at java.util.Collections.sort(Unknown Source) ~[?:1.8.0_25]
    at net.minecraft.command.CommandHelp.func_71534_d(SourceFile:84) ~[au.class:?]
    at net.minecraft.command.CommandHelp.func_71515_b(SourceFile:38) ~[au.class:?]
    at net.minecraft.command.CommandHandler.func_71556_a(CommandHandler.java:94) [z.class:?]
    at net.minecraft.server.dedicated.DedicatedServer.func_71333_ah(DedicatedServer.java:370) [lt.class:?]
    at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:335) [lt.class:?]
    at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:547) [MinecraftServer.class:?]
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:427) [MinecraftServer.class:?]
    at net.minecraft.server.MinecraftServer$2.run(MinecraftServer.java:685) [li.class:?]

I thought it might be a Java 8 issue originally but I was also seeing it on Java 7 (32 bit and 64 bit).

Any ideas?[DOUBLEPOST=1414953659,1414870012][/DOUBLEPOST]Nevermind, the update from 1.0.0 to 1.0.1 seemed to fix it.