Events

Register strongly typed handlers on the client:

client.OnReady(func(_ context.Context, event *osmose.ReadyEvent) error {
	log.Printf("connected as %s", event.User.Username)
	return nil
})

client.OnMessageCreate(func(ctx context.Context, event *osmose.MessageCreateEvent) error {
	if event.Message.Content == "!ping" {
		return event.Reply(ctx, "Pong!")
	}
	return nil
})

Available events

Every handler receives a context.Context and returns an error. Registration returns a removal function:

remove := client.OnMessageUpdate(handler)
defer remove()

Message events expose Message, Author, Client(), and Reply(...) where appropriate. Interaction events expose the typed Interaction model, Respond, Reply, Acknowledge, and Defer. The underlying protobuf value remains available through Raw on the model. Event payload fields are derived from the current Osmium update types, so absent optional protocol fields remain nil where relevant.

Connection events use ConnectionEvent:

client.OnReconnecting(func(_ context.Context, event *osmose.ConnectionEvent) error {
	log.Printf("retrying connection %d in %s", event.Attempt, event.RetryIn)
	return nil
})

Attempt starts at one. RetryIn is populated for OnReconnecting, and Err is populated for failed connection attempts. Voice events expose the room control-plane models; they do not carry audio packets.

Configure Config.OnHandlerError to observe returned handler errors and panics. The callback runs on the event worker and should not block.

Dispatch behavior

Updates are delivered through a bounded worker pool with one worker by default, so a slow handler cannot create an unbounded number of goroutines. Set EventWorkers above one when handlers may run concurrently. If the queue is full, the update is dropped and logged so the client stays responsive. Client.DroppedEvents() exposes the cumulative drop count and Config.OnEventOverflow can report it to application metrics or alerts. Keep the overflow callback short.

For waiting on messages inside a confirmation or form flow, use the typed message collector instead of managing a temporary handler by hand.