droppedEvents

Events KitePlayer.events could not take because its buffer was full.

A collector slower than the session makes this rise, and every one of those is an occurrence a consumer counting on the event stream never saw. It was silent before: the engine ignored the answer tryEmit gives it, so a lost seek completion looked exactly like one that never happened. Anything above zero means the event feed is not a complete record for this session, and the fix is a faster collector.

Not the same thing as an event nobody was listening for. This flow replays nothing to a late collector by design, and that case is undetectable and deliberate; it is also why every warning is additionally kept in KitePlayer.warningHistory.