Amuhn Ra

Realms often struggle with performance at a simulation distance of 4.

Unless you have increased the processing capabilities to 4.23 times the previous capability level, then yes, this will result in a significant decrease in performance on the realms.

The current main limitation is the processing power for the single main thread that handles the tick process. Loading up and running the tick process on 4.23 times as many chunks will be a MAJOR strain without an accompanying increase in the processing ability of the machine running the realm.

(4.23 = 217/49 .. 217 being the number of ticking chunks per player on a sim distance 10 world, and 49 being the number on a sim distance 4 world)

Edited to add "per player" to numerical explanation

Encountered on BDS as well as Single Player

This only happens if the block is broken while doFireTick=false

If you set it to true, it does not fix existing flames, but will prevent more instances occurring.

To connect you would need to update to 1.16.100 

1.16.100 did add some limitations to the supported hardware it would run on, which is likely why your system has not been able to update.

When loading a world after an update the server will often need to update the world to the new version, Let the world run for a while and the issue will resolve itself.

This is intended behaviour.

Further Information:

This appears to only happen to Double Chests, and only when the two component parts of the chest are in different chunks. 

Possibly caused by the updating of the chunks into 1.16.100

It appears that there is an issue with a chest entity.

Had this happen on our server also.  Identified the chest in-game (see screenshot).

Opening the chest causes a crash,  Breaking the chest with an axe seems to be sufficient to repair the damaged data.

Jadon:

Raids only spawn 3 waves when you play on "Easy", this is expected behaviour.

This is intended behaviour, and welcome behaviour for most server operators.

Forcing vanilla resource packs will prevent anyone from using an xray resource pack for example, which is useful on any public server.

If you are a private server you can provide users with the custom item resource packs to install locally, and then set them as server resource packs, but have them be optional.  If they are installed on the users machine they will be enabled (as though forced) but still allow other resource packs to be added on top of them as well.

To be clear, this is related to non-operator users seeing their own outgoing whispers.

This is not an issue with the operator ability to see all server whispers.

This happens even with server.properties/texturepack-required=false

I have seen the request dialog appear at least once since the update, but it has taken multiple cycles of cancelling and reconnecting to get it to work.

To be clear, this happens when the texturepacks are NOT forced.

This indicates that they were using DNS hijacking to connect to a custom minecraft server version that then allowed them to connect elsewhere.

Use of this custom server version in not supported.

I am correctly seeing all 19 pages in 1.16.0 on Ubuntu, can you confirm if the issue is resolved for you running the latest version also?

If it is not, can I find out which version of BDS you are running, and the platform it is running on?

Dj Martin: Tab completion is a feature when you are ingame, and not inside the console, it uses the same command response for both, but is designed to be accessed from inside the game primarily, hence why you can see the § symbol that is used for colour coding in the console output.

To diagnose this issue further, can I find out all the steps you use to connect an Xbox player to the server?

Xbox does not currently allow you to connect to custom servers outside of your local network, and the issue is likely related to the workaround that you are using to allow this to happen.

This issue was likely caused by a known issue in 1.14 which could cause villagers to relink to new locations when villager chunks were unloaded by using a portal or logging off with them loaded.

This issue should have been resolved in 1.16, but the villagers may need to be relinked to the correct beds to allow them to sleep. They may also need to be relinked to their workstations if they have changed their links to those also.

To test the linking you can break the bed and re-place it. You will see green sparkles on the villager that links to it, Using this and a small bit of time you can break all beds, and replace them in the appropriate reachable locations for your villagers if they are not reachable in the current positions.

I have just identified that this also happens in single player, so will be a client-side issue. I will recreate the ticket as a client-side issue after I have done some more testing.

My apologies for the slow reply, this is using Ubuntu 18.04.

I suspect it may be an issue with using an odd number specifically, but due to significant user access with the new update I have not had a time where no-one is online to do testing with other simulation distance settings to see if it occurs for all or only odd numbers.

If you have updated the PS4 game versions but are unable to connect, this suggests that the Bedrock Dedicated Server software has not been updated.  Please can you verify if it has been updated?
If you have updated it please can you share the operating system that BDS is installed upon?

To help identify possible causes for the problem you are facing can you please provide some more information?

Which operating system and version is Bedrock Dedicated Server installed on?

Which operating system(s) and device(s) are you connecting to the server from?

Have you updated Bedrock Dedicated Server and all game clients being used to the latest release version (1.16.0)?

To help identify possible causes for the problem you are facing can you please provide some more information?

Which operating system and version is Bedrock Dedicated Server installed on?

Which operating system(s) and device(s) are you connecting to the server from?

Are you connecting within the same local network, or between local networks?
If you are connecting between multiple local networks have you tested connecting from within the same network also?

What steps have you used to try to connect already, and what error messages appear for these methods?

To help identify potential causes of the issue can we find out which operating system you have installed Bedrock Dedicated Server on, and which device(s) you are not receiving sound on?

Do all players connecting to the server instance have this issue, or just you?