Crowdin doesn't understand {%param}, which affects our ability to do QA on Crowdin directly. It does understand {param}, which is the closest neighbour.
* New translations eng.ini (Romanian)
* New translations eng.ini (Russian)
* New translations eng.ini (Vietnamese)
* New translations eng.ini (Vietnamese)
* New translations eng.ini (Vietnamese)
This allows packet handlers to tell the network session to discard any following packets if their buffers were identical to the current one.
This is a very conservative and basic limiter. If we start having problems with multiple packets being spammed at once interleaved, this will become ineffective. However, for now, all the known spam bugs are of single packets, and the buffers of said packets are always identical. Dealing with interleaved packets would be quite a bit more complex. This mechanism is very simple and should avoid any negative side effects.
* New translations eng.ini (Vietnamese)
* New translations eng.ini (Vietnamese)
* New translations eng.ini (Vietnamese)
* New translations eng.ini (Vietnamese)
* New translations eng.ini (Vietnamese)
* New translations eng.ini (Vietnamese)
* New translations eng.ini (Vietnamese)
* New translations eng.ini (Vietnamese)
* New translations eng.ini (Vietnamese)
* New translations eng.ini (Vietnamese)
* New translations eng.ini (Vietnamese)
* New translations eng.ini (Korean)
* New translations eng.ini (Korean)
* New translations eng.ini (Spanish)
* New translations eng.ini (Spanish)
this fixes rendering of underwater TNT and possibly other chemistry blocks.
There doesn't seem to be a shortcut for this, and BDS also appears not to account for
this requirement, which is why underwater TNT also doesn't have the right texture in BDS.
fixes#6494
the intent of this was noble (to make sure nothing was missed), but in practice throwing
errors on this stuff is just a pain in the ass. We don't actually need to care if the
properties are not used, since it doesn't affect the decoding (like it would for
a missing packet field), so the only reasons to complain are for BedrockProtocol to
have a complete picture of the protocol, and to make sure we're not discarding useful
information.
Log a warning in these cases instead, which should be noticed by developers without
being an unnecessary problem for users.
closes#6816
