Please hook Minecraft.handleClientCommand() to handle client commands.

[totemo]

Currently, it's not possible to handle commands purely at the client without modifying the base classes.

 

Please feel free to cannibalise my code here: https://github.com/totemo/watson/tree/master/src/clientcommands to implement a standard Forge interface for this.

 

 

[totemo]

Wow.  I wasn't even aware of that possibility.  I'm quite surprised.  Last time I looked at hot swapping code I think I reached the conclusion that it required JPDA and it all seemed too hard for my humble mod.

 

I guess, ideally there would be a standard interface, so I'd greatly appreciate any work you could do in that regard.

 

Thank you for your reply.

[LexManos]

Any particular reason you used your own registry/interfaces? Could you not re-use the Command registry thats on the servers?

{Havent looked yet, just a thought}

[totemo]

My mod is entirely client-side.  It doesn't rely on anything in particular from the server other than permission to use LogBlock/CoreProtect/Prism query commands and tppos.

 

A local command line was my preferred way of driving it.

 

[LexManos]

How does that relate to what I just said?

The registry and stuff are client env as well.

[totemo]

Ah, I understand what you're saying now.

 

I think at the time I wrote it I wasn't sure if I could use net.minecraft.command.CommandHandler client side. If that is possible, then great.