This is a guide on how to get started with Indigauge for the Bevy engine (compatible with Bevy 0.18).
For more examples check out the examples in the repository or the bevy-mod-indigauge README.
Add the package to your game project.
Or add it manually in Cargo.toml:
Have the public api key available from the previous step.
This example initializes the plugin and starts a new session when the game is opened. The only thing that will be sent in automatically is any crash-events.
This example does multiple things:
Space on their keyboard.Enable the tracing feature to forward structured log events to Indigauge
through Bevy's LogPlugin. This is useful for sending telemetry from existing
tracing-based instrumentation.
Cargo.toml:
Usage example with the default tracing layer (forwards all events):
You can also configure the layer with custom filters:
Any tracing event with an ig field will be forwarded:
The ig field must follow the same namespace.event rules as the ig_*
macros (see the Event Naming guide).
feedback (enabled by default): provides the in-game feedback panel rendered
with Bevy UI + picking.feedback_egui (optional): renders the feedback panel using bevy_egui
instead of Bevy UI (native only).panic_handler (enabled by default): capture native panics/crashes as events.tracing: enable tracing-layer integration.On WASM builds the panic handler is disabled. No crash reports will be sent as events to the Indigauge API.
If you need a minimal dependency set (for example for WASM builds), disable
default features in Cargo.toml and opt-in to the features you need.
| Bevy | bevy-mod-indigauge |
|---|---|
| 0.18 | 0.6 |
| 0.17 | 0.5 |
| 0.16 | 0.4 |
| 0.15 | 0.1 – 0.3 |