Rick 07ef2bbab9 Fix incorrect command serialization by creating new Command (#11671) ... Fixes #11649 - As noted in the issue, when CommandNodes are serialized they are used as the key in a Map. Their equals()/hashcode() should only match if they are equal nodes (name & command), but due to the erasure of the command field pre-serialization, nodes with different commands can be mapped onto the same value. This causes the client to interpret both nodes as the same, causing suggestions where they should not. This is fixed by creating a different no-op command for the erasure, instead of them holding the same lambda.		2024-12-08 16:43:09 -05:00
..
api	Add command block material tags (#11720)	2024-12-08 22:40:02 +01:00
removed	Start update, apply API patches	2024-12-03 17:58:41 +01:00
server	Fix incorrect command serialization by creating new Command (#11671)	2024-12-08 16:43:09 -05:00