Chat Commands
All available Twitch chat commands
Once you've connected a bot account, viewers can interact with Dirework through Twitch chat commands.
Task Commands (All Viewers)
| Command | Description |
|---|---|
!task <text> | Add a new task (auto-activates if it's your first) |
!done | Mark your active task as done |
!done <number> | Mark a specific task by position as done |
!edit <number> <text> | Edit a specific task by position |
!remove <number> | Remove a specific task by position |
!focus <number> | Set a task as your active/focused task |
!check | Show your current active task |
!check @user | Show another user's active task |
!next <text> | Complete your active task and start a new one |
!help | Show available commands in chat |
Task Commands (Broadcaster / Mods)
| Command | Description |
|---|---|
!clear all | Clear all tasks from the list |
!clear done | Clear all completed tasks |
!clear @user | Remove all tasks from a specific user |
Timer Commands (Broadcaster / Mods)
| Command | Description |
|---|---|
!timer start | Start the timer with default settings |
!timer start <cycles> | Start the timer with a specific cycle count |
!timer pause | Pause the timer |
!timer resume | Resume the timer |
!timer skip | Skip the current phase |
!timer reset | Reset the timer to idle |
!timer eta | Show estimated end time |
Meta Commands (Always Available)
These commands are always enabled regardless of task or timer command settings.
| Command | Description |
|---|---|
!dwhelp | Link to this commands reference page |
!dwcommands | Same as !dwhelp |
Active Task & Focus
When you add your first task with !task, it automatically becomes your active task. Subsequent tasks are added as pending.
- Your active task is what shows as your current focus in the overlay and in
!checkresponses. - When you complete a task with
!done, the next pending task is automatically activated. - Use
!focus <number>to manually switch which task is active. The number is the position in your task list (1-based).
Command Aliases
Broadcasters can remap command names in Bot Settings (/dashboard/bot). For example, you could set add to map to task, so viewers can use !add instead of !task.
Aliases only apply to task and timer commands. Meta commands (!dwhelp, !dwcommands) cannot be aliased.
Task Priority
Tasks created by the broadcaster (stream owner) are pinned to the top of the list. Viewer tasks appear below in the order they were added.
Bot Responses
All bot response messages are customizable from the Bot Settings page (/dashboard/bot). Task and timer command groups can also be individually enabled or disabled.
Task Bot Responses
| Message | Default | Variables |
|---|---|---|
| Task Added | Awooo! The task "{task}" has been added to the pack, {user}! | {task}, {user} |
| No Task Added | You're already on the hunt {user}, use !check to see your current task! | {user} |
| No Task Content | Tell the pack what you're working on! Use !task [task] {user} | {user} |
| No Task to Edit | No task found in your den to edit {user} | {user} |
| Task Edited | The hunt has changed! Task updated to "{task}" {user} | {task}, {user} |
| Task Removed | Task "{task}" has been scent-wiped from the list, {user} | {task}, {user} |
| Task Next | Paws-ome work finishing '{oldTask}'! Now tracking '{newTask}', {user}! | {oldTask}, {newTask}, {user} |
| Admin Delete Tasks | All of the user's tasks have been cleared from the forest. | none |
| Task Done | Alpha work! You finished "{task}" {user}! | {task}, {user} |
| Task Check | {user}, your current scent is on: "{task}" | {user}, {task} |
| Task Check User | {user}, {user2} is currently tracking: "{task}" | {user}, {user2}, {task} |
| No Task | Looks like you aren't tracking anything in the forest right now, {user} | {user} |
| No Task (Other) | The scent is cold... there is no task from that user {user} | {user} |
| Not Mod | Grrr! Permission denied, {user}; Only pack leaders (mods) can do that. | {user} |
| Cleared All | The forest has been cleared of all tasks! | none |
| Cleared Done | All finished tasks have been cleared from the den! | none |
| Next No Content | Don't leave the pack hanging! Try !next [task] {user} | {user} |
| Help | {user} Join the hunt with !task, !remove, !edit, or !done. | {user} |
Timer Bot Responses
| Message | Default | Variables |
|---|---|---|
| Work Started | Time to hunt some code! Focus mode activated! | none |
| Break Started | Paws up! Time for a short rest in the den. | none |
| Long Break Started | The whole pack is taking a long snooze! Back soon! | none |
| Work Reminder | Get ready to howl at that code @{channel}, focus starts in 25 seconds! | {channel} |
| Not Running | The timer isn't howling yet! Start it up first. | none |
| Stream Starting | The Blue Wolf is waking up! Stream starting! | none |
| Wrong Command | My ears didn't catch that... Command not recognized! | none |
| Timer Running | The hunt is already in progress! | none |
| Command Success | Paw-fect! Done! | none |
| Cycle Wrong | The cycle cannot outrun the goal! | none |
| Goal Wrong | The goal needs to be further than the cycle! | none |
| Finish Response | Great work today pack! We hunted well. | none |
| Already Starting | The pack is already moving or the timer is running! | none |
| ETA | The hunt will end at {time} | {time} |
Message Variables Reference
| Variable | Description |
|---|---|
{user} | The Twitch display name of the person who ran the command |
{user2} | The Twitch display name of the target user (e.g., !check @other) |
{task} | The task text content |
{oldTask} | The task that was just completed (used in !next) |
{newTask} | The new task now being tracked (used in !next) |
{channel} | The Twitch channel name, used as @mention to ping chat |
{time} | The estimated end time formatted as local clock time (e.g., 3:45 PM) |