BruceChen

Conflict resolution has been completed, I'll do some testing later. ~There are still some issue found with the handling of MessageHeader in 1.19.2~ **Edit:** Fixed.

I tested terrain handling in an official server and a paper server respectively, and they worked fine. @milutinke Let's merge it if all functions are working properly.

> Is this Console Interactive bug? Partially yes, this should be fixed in https://github.com/MCCTeam/Minecraft-Console-Client/pull/2124/commits/b26949e483a289934a40f2a65aa34b53988351bb and https://github.com/breadbyte/ConsoleInteractive/pull/14 and https://github.com/breadbyte/ConsoleInteractive/pull/12. --- > Edit: The only remaining things are the bug above and...

@milutinke Try using /move 35 71 -35

> > /move 35 71 -35 > > That works. It's not really intuitive. Yes, I also encountered this problem when I started testing. Because people are used to rounding...

Perhaps it would be better to upgrade the move command to accept floating point and relative coordinate representations.

> The message appeared after the merge xD > That could be done in a separate PR. Implemented in #2154, it will now move to the exact coordinates entered. :)

> @BruceChenQAQ Seems like a problem with terrain handling, specifically with `SetBlock` in `World.cs` Was it changed in 1.19? This is probably because the dimensional data is not handled correctly...

Switching between different versions of servers may cause exceptions in chunk data processing, trying to fix it

Fixed similar issues(https://github.com/MCCTeam/Minecraft-Console-Client/issues/1780) in https://github.com/MCCTeam/Minecraft-Console-Client/commit/eba309191cd145c95b94dd0fed284c1b788b2e2b and https://github.com/MCCTeam/Minecraft-Console-Client/commit/bb4c13168beaefb278d21140f3ae56ef788b8b00. Try the latest version.