A roll becomes a chat event
In a text-based Dungeons & Dragons game, a roll can interrupt the scene twice: first while a player works out what to roll, then while everyone waits for the result. A dice bot compresses that pause into a chat command. A player can request a die—often with a modifier, such as a bonus added to a d20—and the bot returns the total where the group can see it.
That small change fits the medium. In a voice game, a physical die lands while conversation continues. In text, the roll has to be typed, reported, and interpreted. A bot turns the roll into one discrete, shared message rather than another handoff between players.
Trust moves from the player to the tool
The bot also changes what “honor system” means. Players no longer have to announce a number they generated privately; the result appears in the common chat record. That makes the outcome easier for the group to verify and keeps the roll attached to the moment that called for it.
The tradeoff is that the group now relies on the bot’s random-number process and on everyone using it consistently. A bot does not decide whether an attack hits, whether a character succeeds, or what a result means in the story unless the game has specifically configured it to do more. Its basic job is narrower: produce a visible number quickly. In a medium where every action waits to be typed, removing even one extra exchange can keep the scene moving.
