Skip to main content

Button Configuration

Overview

iReporter supports up to 8 buttons. Each button is independently configured with its own label, messages, webhook target, crash/incident fallbacks, and voice text. The number of visible buttons is controlled by the Number of Buttons setting.

Button Fields

Label

A descriptive name for the button shown in the settings panel (e.g. Contact Report, Yellow Flag). This is for your reference only and is not included in any sent message.

Message Templates 1, 2, 3

Up to three message lines can be configured per button. When the button is pressed:

  • All three messages are sent in sequence if populated.
  • Messages support Message Variables — placeholders filled with live iRacing data at press time.
  • If a message contains a variable that has no current value (e.g. a crash variable when no crash is active), the message is skipped unless a fallback is configured.

Webhook

Selects which of the three configured webhooks receives this button's messages. Set to None to disable webhook posting for this button.

Disable Text Logging

When ticked, this button's presses are not written to the log file even if logging is globally enabled. Useful for buttons used very frequently (e.g. a heartbeat or status button) that would clutter the log.

Crash Fallback

Visible only when Crash Capture is enabled in iRacing Options. Enter a message to be sent instead of (or in addition to) the normal messages when a crash is currently active. Crash variables ({CRASHCAR}, {CRASHNAME}, etc.) are available in this field.

Leave blank to disable crash-specific behaviour for this button.

Incident Fallback

Visible only when Incident Capture is enabled. Works identically to the Crash Fallback but uses incident variables ({INCCAR}, {INCNAME}, etc.).

Voice (Speak Text)

Visible only when Voice Options is enabled. Enter the text to be spoken aloud when this button is pressed. Supports message variables. Leave blank for no speech on this button.

Tick Disable Voice for this button to suppress voice output for this button while keeping the speak text saved for future use.

Test Fire

The TEST FIRE button at the top of each button section simulates a button press without requiring a physical button press. Useful for testing your messages, webhook delivery, and voice output during setup.

Message Templates (Saved)

The Message Templates dropdown allows you to save and load commonly used message sets. Click Manage Templates to create, rename, or delete templates. Applying a template overwrites the current button's three message fields.

Conditional Messages ({IF} blocks)

Messages can contain conditional sections using {IF:CONDITION}...{/IF} syntax. For example:

{IF:CRASH}Contact involving {CRASHCAR}{/IF}
{IF:NOCRASH}No active contact{/IF}

See the Variables Reference for all supported conditions.

Back to top