Changes

IForgeTileEntity#handleUpdateTag(BlockState state, CompoundNBT tag)

IForgeTileEntity#handleUpdateTag(BlockState state, CompoundNBT tag)

</syntaxhighlight>

</syntaxhighlight>

Again, this is pretty simple, the first method collects the data that should be send to the client, while the second one processes that data. If your <code>TileEntity</code> doesn’t contain much data you might be able to use the methods out of the [[#storing_data|Storing Data/1.16]] section.

Again, this is pretty simple, the first method collects the data that should be send to the client, while the second one processes that data. If your <code>TileEntity</code> doesn’t contain much data you might be able to use the methods out of the [[#storing data/1.16|Storing Data]] section.

{{Tip/Important|Synchronizing excessive/useless data for tile entities can lead to network congestion. You should optimize your network usage by sending only the information the client needs when the client needs it. For instance, it is more often than not unnecessary to send the inventory of a tile entity in the update tag, as this can be synchronized via its GUI.)}}

{{Tip/Important|Synchronizing excessive/useless data for tile entities can lead to network congestion. You should optimize your network usage by sending only the information the client needs when the client needs it. For instance, it is more often than not unnecessary to send the inventory of a tile entity in the update tag, as this can be synchronized via its GUI.)}}

=== Synchronizing using a custom network message ===

=== Synchronizing using a custom network message ===

This way of synchronizing is probably the most complicated one, but is usually also the most optimized one, as you can make sure that only the data you need to be synchronized is actually synchronized. You should first check out the <code>[[latest:advanced:networking:start|Networking/1.16]]</code> section and especially <code>[[latest:advanced:networking:simplechannel|SimpleImpl/1.16]]</code> before attempting this. Once you’ve created your custom network message, you can send it to all users that have the <code>TileEntity</code> loaded with:  

This way of synchronizing is probably the most complicated one, but is usually also the most optimized one, as you can make sure that only the data you need to be synchronized is actually synchronized. You should first check out the <code>[[latest:advanced:networking:start/1.16|Networking]]</code> section and especially <code>[[latest:advanced:networking:simplechannel/1.16|SimpleImpl]]</code> before attempting this. Once you’ve created your custom network message, you can send it to all users that have the <code>TileEntity</code> loaded with:  

<syntaxhighlight lang="java">

<syntaxhighlight lang="java">

SimpleChannel#send(PacketDistributor.TRACKING_CHUNK.with(() -> chunk), MSG);

SimpleChannel#send(PacketDistributor.TRACKING_CHUNK.with(() -> chunk), MSG);

</syntaxhighlight>

</syntaxhighlight>

{{Colored box|title=Alert|content=It is important that you do safety checks, the TileEntity might already be destroyed/replaced when the message arrives at the player! You should also check if the area is loaded using (<code><nowiki>World#isAreaLoaded(BlockPos, int)</nowiki></code>)}}

{{Colored box|title=Alert|content=It is important that you do safety checks, the TileEntity might already be destroyed/replaced when the message arrives at the player! You should also check if the area is loaded using (<code><nowiki>World#isAreaLoaded(BlockPos, int)</nowiki></code>)}}