Disabling (Unreliable)RemoteEvent invocation queue

Help and Feedback Scripting Support
#1

DISCLAIMER: My english is not the best, please be aware.

  1. I want to disable RemoteEvent invocation queue
    On the server i have script that fires RemoteEvent every 1 second to all clients. This is loop event, it’s noticing clients to do work related to parts that can be placed by client.
    Client event only connects when this parts is placed. And disconnects when they are removed.

  2. What is the issue?
    Client should ignore all events that happend before part is placed (before connection occurs), i dont even care if it will be lost. But since no handler connected to the event, RemoteEvent queue stores them until first connection appears, then all stored events fire at the newly connected function. After that, it’s start to fire normally, every 1 second (if only i keep connection, if not, then event starts to store calls in queue again, which is anoying). I dont want that behaviour since this is unnecessary and can (and will) call errors with “Remote event invocation queue exhausted” message.

  3. What solutions have i tried so far?

  • I searched internet for the answer, i’ve seen many topics about that error, but none about disabling this queue. No luck there.
  • I asked Assisant about disabling that queue, but he’s response does not make any sense because he is just makes up things sometimes, he told me to do RemoteEvent.Unreliable = true but Unreliable property does not exist (not event deprecated).
  • Only thing that comes to mind is to connect empty handler on event when client connects to game. But i dont want that, except this is the only solution.
  • Yes i’ve tried UnreliableRemoteEvent object, but it does exactly the same as RemoteEvent, documentation says that it “unordered and unreliable”, but in my experience, it act’s exactly as the regular RemoteEvent except maybe it is really unordered (i didn’t tested that).
  • I can also implement debounce timer, but it will save me only from first connection firing miltiple times, not from errors when no connection is exist but queue still grows.

From documentation:
UnreliableRemoteEvent is best used for ephemeral events including effects that are only relevant for a short time, or for replicating continuously changing data. These events are not resent if they are lost and they do not wait for previously fired events to arrive before being processed, potentially resulting in reduced latency and network traffic. When requiring ordering and reliability, use a RemoteEvent instead.

I have not found any method of disabling it or changing queue size.