NiLSPACE

Strangely it seems chunk-specific, which sadly means this is most likely a problem in Cuberite. @madmaxoft did the `cBlockArea` write code change lately?  

Good catch! That means it's most likely an issue with the new `1.11` protocol.

`1.11` is the latest protocol that was introduced, so it's most likely not the stablest. If you want a stable client you'll have a bigger chance if you'd use an...

I'd prefer to switch all variable names to camelCase.

Yeah, that's probably nicer. If multiple syntaxes are allowed we could provide an array of command objects. Handling whatever the parser returns might be a little harder to do nicely...

Perhaps instead of providing a type for the argument we provide a function. I could for example provide the `GetBlockDst` function which chooses the right `BlockTypeSource` depending on the argument.

You mean the whole idea of the command parser?

I have an idea on how to do this which is actually pretty simple. I'd like to try it out first, but I think it could work.

I'm afraid the user won't notice allot, but it makes creating new commands a little easier and nicer.

It seems to be working. A JSON dump of the result gives this: ```json { "Arguments" : { "block" : { "m_BlockTable" : [ { "BlockMeta" : 0, "BlockType" :...