Issue: UnreliableRemoteEvents generate “Remote event invocation discarded” errors when the event arrives after the remote has been destroyed. Standard RemoteEvents handle this scenario silently without errors.
Reproduction Steps:
- Create a script with both a RemoteEvent and UnreliableRemoteEvent
- Fire the remote event from client
- Immediately destroy the remote (e.g., via character respawn/cleanup)
- Results:
- RemoteEvent: Event discarded silently (correct)
- UnreliableRemoteEvent: Throws error when event arrives (incorrect)
Technical Details: When an UnreliableRemoteEvent is fired and quickly destroyed, the event is still in transit. Upon arrival at the server, it finds no valid receiver and throws an error instead of failing silently.
Environment: MacOS Sequoia 15.4.1, M4 Max
Expected Behavior: UnreliableRemoteEvents should match RemoteEvent behavior, and silently discard events that arrive after the remote is destroyed.
Impact: Output spam from legitimate gameplay scenarios (character deaths, object cleanup) makes debugging tedious and visually taxing, especially for high-frequency events like camera updates.
