Command Parser

[user622628252416]

Regarding #15, I implemented a tree-style command parser, as well as the /help command for reference.

There is a central CommandDispatcher instance, that is contained inside of a OnceLock (pumpkin::commands::DISPATCHER), from where all commands are dispatched. There is currently no access to the level/world the command is executed in, so what a command can actually do is quite limited. This is more of a temporary solution.

[Snowiiii]

Hey, Mostly looks good 👍 . Could you may fix all Clippy warns ?. I also just pushed a commit which fixes the one warn in packet_encoder

[user622628252416]

I fixed all the warns that I could fix. I did have to suppress two dead_code warns tho because no command needing literals is implemented as of now.

[Snowiiii]

I fixed all the warns that I could fix. I did have to suppress two dead_code warns tho because no command needing literals is implemented as of now.

Great. I just don't really like that in help command, Commands are send multiple times if they have multiple arguments. I find that very confusing. CI is btw unhappy (you have to format the code)

[user622628252416]

I agree about the help command. Sending multiple lines is more of a temporary solution until someone implements merging all the paths on the tree into a single line (which is doable but not without some complexity). I added a todo 👍

[Snowiiii]

Okay. Everything other looks good. Thank you 👍