# ClientInputTelemetryEvent > Fired when a client with input telemetry enabled uploads a batch of raw input events. Batches arrive roughly once per second while the player is connected and telemetry is on. `gg.lode.lecternapi.api.event.ClientInputTelemetryEvent` --- ## Signature ```java public class ClientInputTelemetryEvent extends Event ``` --- ## Notes Each record carries key identity and timing only, never typed text. Anti-cheat consumers are expected to look at distributions across many batches (click interval variance, crosshair-to-click latency) rather than to judge any single event. **Deprecated.** The client no longer collects input timing telemetry, so this event is never fired. Kept so existing listeners still compile. --- ## Variants | Type | Description | |---|---| | `InputRecord` | A single key or mouse transition. | --- ## Methods ### getPlayer ```java public Player getPlayer() ``` --- ### getRecords ```java public List<InputRecord> getRecords() ``` --- ### getDroppedRecords ```java public int getDroppedRecords() ``` How many events the client discarded because its buffer filled between flushes. A consistently non-zero count means the batch is incomplete and timing statistics computed from it will have gaps. ---