From 22b20b856658168e2fd289263bcf3a14782bc1d6 Mon Sep 17 00:00:00 2001 From: Andrii Date: Mon, 9 Sep 2024 23:52:25 +0300 Subject: [PATCH] Fix typo "amound" -> "amount" --- docs/chest.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/chest.md b/docs/chest.md index 04bbbd4..0bfd3d8 100644 --- a/docs/chest.md +++ b/docs/chest.md @@ -109,7 +109,7 @@ The message is sent when user puts `` to the chest to `` messages = } ``` -The message contains an array of other messages (``) which were emitted within a very short interval, and for this reason merged into a batch and sent as a single message. This is needed to prevent burning of connected Lua controllers in case of a large amound of messages within a very short time. This can happen in case of using the feature which allows to move all items of the same type between inventories at once by taking one of them, and clicking on another one while holding Shift. Another theoretical scenario - sending a lot of requests to the server associated with inventory operations on a Digiline chest using a hacked client or custom software. The decision whether to include a message into a batch is made based on the interval from the previous message. For this reason, a batch message is always preceded by a single message which wasn't included into the batch because there was enough time from the previous message, and we cannot know in advance when the next message will be sent to include the current one into the batch too. +The message contains an array of other messages (``) which were emitted within a very short interval, and for this reason merged into a batch and sent as a single message. This is needed to prevent burning of connected Lua controllers in case of a large amount of messages within a very short time. This can happen in case of using the feature which allows to move all items of the same type between inventories at once by taking one of them, and clicking on another one while holding Shift. Another theoretical scenario - sending a lot of requests to the server associated with inventory operations on a Digiline chest using a hacked client or custom software. The decision whether to include a message into a batch is made based on the interval from the previous message. For this reason, a batch message is always preceded by a single message which wasn't included into the batch because there was enough time from the previous message, and we cannot know in advance when the next message will be sent to include the current one into the batch too. ### Fields used within the messages