PitPicks logo PITPICKS
Direct automation

PitPicks + Streamer.bot

Map race events to Streamer.bot Actions and let your actual iRacing session control overlays, sounds, TTS, lights, chat and more.

Connection: PitPicks uses Streamer.bot's HTTP Server, normally http://127.0.0.1:7474. Port 8080 is normally the WebSocket server and is not the HTTP API field PitPicks uses.

Race Events

Flags

Green flag, caution, restart and white flag.

Position milestones

Took/lost lead, entered/left Top 5 or Top 10, gained/lost 3 from the start.

Incidents

Incident changes plus 4x, 8x, 12x and 16x thresholds.

Pits & penalties

Pit entry/exit, service start/complete, black flag and penalty cleared.

Fuel & tow

Estimated 10/5/2 laps of fuel remaining and tow events.

Finish routing

Separate actions for WIN, P2–P5, P6–P10, P11+ and DNF/TOW.

Betting + viewer events

Market activityOpen, close, void and bet placed.
Participation milestones10 / 25 / 50 / 100 bettors.
Wager milestones10K through 1M virtual currency wagered.
Big momentsLargest wager, biggest payout, 3.0x+ underdog hit.
Prediction streaks3 / 5 / 10 winning picks in a row.
Session championTrigger a celebration when a points session ends.

Two-way control

Streamer.bot can also send commands back into PitPicks. That makes Channel Points, Stream Deck buttons, MIDI inputs or other Streamer.bot triggers usable as PitPicks controls.

Market control

Open, close, void and manually settle markets.

Board control

Force Show, Hide or return the betting board to Auto scheduling.

Viewer currency

Give a viewer virtual currency from an automation.

Manual actions

Configure three quick actions and trigger them from PitPicks or !pp1, !pp2, !pp3.

Setup

1
Enable HTTP Server

In Streamer.bot, open Servers/Clients → HTTP Server and enable Auto Start.

2
Use port 7474

Keep 127.0.0.1:7474 unless you intentionally changed it.

3
Load Actions

In PitPicks click Test + Load Actions.

4
Map + Test

Choose an Action beside each event and use its Test button to verify /DoAction.