Can confirm this, happened to me before in the 1.12-1.14 demo, bought this version today and still encountering this problem in 1.16
Can confirm this, happened to me before in the 1.12-1.14 demo, bought this version today and still encountering this problem in 1.16