dofes
- dofes
- JIRAUSER576819
- Europe/Stockholm
- Yes
- No
BDS-10195
MCPE-178461
until 1.17.32-bds,this bug still not fix
a error for recipes of the blocks
if you want to craft gold block or iron block ,then you will find you can't craft it
the recipe system seems broken?
Summary:
This bug report addresses a client-side caching issue related to the handling of subchunks in Bedrock Dedicated Server (BDS), leading to anomalies in block entities. This issue seems specific to environments using subchunk caching, as similar tests on third-party servers like Nukkit and Geyser, which use full level chunks, did not exhibit this problem.Steps to Reproduce:
Player 1 is in a location with multiple campfires.
Player 1 teleports to a distant location.
Player 2 destroys the campfires at Player 1's original location.
Despite the destruction, Player 1 does not receive the update about the destroyed campfires.
Player 1 teleports back and observes that the campfire particles still exist.
Player 1 places a chest (or any block with an entity) at the original campfire location.
This results in a collision box anomaly for Player 1's chest block entity.
Attempting to open this anomalous chest causes the UI to freeze, requiring the player to exit the game to resolve the issue.Expected Behavior:
Upon leaving the area, block entities should be unloaded correctly from the client's memory, especially in environments using subchunk caching. This unloading is crucial to ensure that when a player returns or receives updates about changes in that area (such as the destruction of campfires), the client reflects these changes accurately. The absence of this behavior in servers using full level chunks suggests that the issue may be specifically related to the handling of subchunks in BDS.Actual Behavior:
In the BDS environment, which presumably uses subchunk caching, the client retains outdated subchunk data. This leads to collision box anomalies and UI freezing when interacting with newly placed block entities in the affected area.Summary:
This bug report addresses a client-side caching issue related to the handling of subchunks in Bedrock Dedicated Server (BDS), leading to anomalies in block entities. This issue seems specific to environments using subchunk caching, as similar tests on third-party servers like Nukkit and Geyser, which use full level chunks, did not exhibit this problem.Steps to Reproduce:
1. Player 1 is in a location with multiple campfires.
2. Player 1 teleports to a distant location.
3. Player 2 destroys the campfires at Player 1's original location.
4. Despite the destruction, Player 1 does not receive the update about the destroyed campfires.
5. Player 1 teleports back and observes that the campfire particles still exist.
6. Player 1 places a chest (or any block with an entity) at the original campfire location.
7. This results in a collision box anomaly for Player 1's chest block entity.
8. Attempting to open this anomalous chest causes the UI to freeze, requiring the player to exit the game to resolve the issue.Expected Behavior:
Upon leaving the area, block entities should be unloaded correctly from the client's memory, especially in environments using subchunk caching. This unloading is crucial to ensure that when a player returns or receives updates about changes in that area (such as the destruction of campfires), the client reflects these changes accurately. The absence of this behavior in servers using full level chunks suggests that the issue may be specifically related to the handling of subchunks in BDS.Actual Behavior:
In the BDS environment, which presumably uses subchunk caching, the client retains outdated subchunk data. This leads to collision box anomalies and UI freezing when interacting with newly placed block entities in the affected area.
This file contains very important information. For community developers, this is extremely important, and I don't understand why it needs to be removed.
I would like to add that this issue seems to potentially affect all situations where subchunks are used, including in realms and on the client-side in general. This leads me to believe that the problem is not isolated to a specific server implementation (like BDS) but could be a more widespread issue in any environment utilizing subchunk caching.
As of now, I am uncertain if this issue also exists in older versions of the software. However, the core of the problem appears to be with the client's inability to correctly unload block entities. This improper handling of unloading could be causing the observed anomalies and UI issues. Further investigation or testing in different versions and environments might be needed to fully understand the scope and history of this issue.
I would like to add that this issue seems to potentially affect all situations where subchunks are used, including in realms and on the client-side in general. This leads me to believe that the problem is not isolated to a specific server implementation (like BDS) but could be a more widespread issue in any environment utilizing subchunk caching.
As of now, I am uncertain if this issue also exists in older versions of the software. However, the core of the problem appears to be with the client's inability to correctly unload block entities. This improper handling of unloading could be causing the observed anomalies and UI issues. Further investigation or testing in different versions and environments might be needed to fully understand the scope and history of this issue.