Added admin commands, refactored help command, and created command descriptions + more

[4Benj]

Changes:

• Added default to usage() for command annotations
• Added descriptions to commands
• Added account.hasPermission(permission) instead of using !permissions.contains("*") && !permissions.contains(permissionNode) and changed the usage in CommandMap
• Added a wip kick command. at the moment it just closes the session which just freaks out the server because the client tries to connect like 10 times before it gives up and reconnects (This is more of a placeholder thing until we can actually disconnect players and send like a server message or something)
• Added a stop command which just kills the server and notifies the players
• Added a broadcast command which messages all players
• Reimplemented my sendmsg command but made it sendservermessage (sendmsg as a player sends a direct message from the sent player... I think, I haven't had another device to test it on)
• Changed reload command so there is feedback when sending as player
• Refactored help command to make it look better, display it's description, and not display the same command multiple times because of aliases
• Removed "usage: " from all usages

Screenshot of help command is console:

Screenshot of help command in-game:
/help

/help sendmessage

[alt3ri]

<3

[SpikeHD]

Just as a heads up since they were just added, this is gonna have residual Usage: XYZ strings for the usages of setworldlevel and givechar :)

[4Benj]

Didn't realise that was merged, sorry. I'll make the same changes to those commands as I did with the others

[Lubin502831]

How to solve the relic entry

[4Benj]

How to solve the relic entry

I'm not sure, go ask on the discord and please keep PR comments about the PR

[4Benj]

Just a heads up in case this gets pushed in.
This is the error that spams the console due to the client trying to keep it's connection alive when it's been closed by the server.
Probably should go into a known-issues part of the readme or something (along with the relic thing) until we find a way to actually kick players from the game server.
This also happens when you quickly stop and start the server (even without the /stop command) and the client isn't given enough time to timeout.

[INFO] Client disconnected from 127.0.0.1
[INFO] Client connected from 127.0.0.1
io.jpower.kcp.netty.KcpException: State=-1 after update()
        at io.jpower.kcp.netty.UkcpServerChannel.run(UkcpServerChannel.java:395)
        at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)
        at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:170)
        at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
        at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:469)
        at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500)
        at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986)
        at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
        at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
        at java.lang.Thread.run(Unknown Source)

[MlgmXyysd]

Just a heads up in case this gets pushed in. This is the error that spams the console due to the client trying to keep it's connection alive when it's been closed by the server. Probably should go into a known-issues part of the readme or something (along with the relic thing) until we find a way to actually kick players from the game server. This also happens when you quickly stop and start the server (even without the /stop command) and the client isn't given enough time to timeout.

[INFO] Client disconnected from 127.0.0.1
[INFO] Client connected from 127.0.0.1
io.jpower.kcp.netty.KcpException: State=-1 after update()
        at io.jpower.kcp.netty.UkcpServerChannel.run(UkcpServerChannel.java:395)
        at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)
        at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:170)
        at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
        at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:469)
        at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500)
        at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986)
        at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
        at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
        at java.lang.Thread.run(Unknown Source)

The same error here, but not shutting down the server. This error also occurs when the client exits abnormally. For example, network disconnection, direct click on X (window exit button) and so on.