Sending Stones Roll20: The Ultimate D&D 5e Guide for Players & DMs
Sending Stones look like a throwaway magic item on paper: two smooth rocks, carved to match, good for one short message a day. Then you sit down at a Roll20 table, the rogue wants to quietly warn the cleric about a traitor, and suddenly you are juggling whispers, macros, token actions, and a question about whether the stone in someone's belt pouch counts as "touching." The item is simple; the logistics around it are not.
This guide walks through the mechanical rules you need to get right, then covers the practical side of running Sending Stones in Roll20: character sheet setup, chat macros, whisper workflows, and the table rulings that keep private messages private. Whether you are a DM handing out a paired set as treasure or a player who just found one in a loot pile, the goal is the same, which is making a two-stone walkie-talkie feel magical instead of administrative.
Sending Stones in D&D 5e: The Rules You Actually Need
Sending Stones are an uncommon wondrous item that come in pairs, with each stone carved to match its partner so the pairing is easy to recognize. While you touch one stone, you can use an action to cast the sending spell from it, and the target of that spell is the bearer of the other stone. If nobody is carrying the paired stone, you learn that immediately and the spell is not cast. Once one stone in a pair has been used this way, neither stone can be used again until the next dawn, and if one stone is destroyed, the other becomes a plain, nonmagical rock.
Because the item casts a specific spell, every restriction of that spell rides along with it. There is no spell slot spent, no material component needed, and no requirement that the user be a spellcaster at all. That last point is what makes Sending Stones so valuable in a party without a wizard or bard, since a fighter can absolutely be the one calling for backup across three hundred miles.
What the Item Does (and Doesn't) Do
The sending spell lets you transmit a message of twenty-five words or fewer to a creature you are familiar with. The recipient hears it in their mind, recognizes you as the sender if they know you, and can reply immediately in the same manner using the same word limit. The spell also ensures that creatures with an Intelligence of at least 1 understand the meaning of the message, so language barriers are not a problem in most cases. What you do not get is shared senses, images, emotional impressions, or any kind of two-way channel that lasts beyond that single exchange.
The physical requirement is the part that trips up tables most often. You must be touching your stone to activate it, which means hands, pockets, gauntlets, or a held pouch are all worth discussing with your DM. A stone in a backpack is a judgment call, and a stone left behind in a tavern is useless. Sending Stones also function only once per day per pair, so a pair that gets used at breakfast is silent for the rest of the adventuring day, which is exactly the kind of limitation that forces players to think about timing instead of spamming the channel.
The 25-Word Limit and Its Consequences
Twenty-five words sounds generous until someone tries to explain a battle plan inside it. This constraint is the heart of what makes Sending Stones interesting, because it turns communication into a puzzle. A player cannot narrate a paragraph of context, so they have to lead with the critical detail and hope the reply answers the right question. In Roll20 this is a real risk, since the chat box invites long paragraphs and the habit carries over into messages that technically violate the spell.
Good practice is to draft the message somewhere you can see it before sending it. A journal handout titled "Sending Stone Log" works nicely, and it also creates a record the DM can reference later when an NPC references a message the party sent six sessions ago. A quick word count is usually enough, and a DM who enforces the limit fairly but firmly will find that players start preparing messages in advance. Some tables allow compound descriptors like "twenty-foot-wide," while others count them as two words; the important thing is announcing the ruling once and sticking to it.
Adding Sending Stones to a Roll20 Character Sheet
Getting the item onto a sheet is straightforward with the D&D 5e sheet by Roll20. If your game has compendium access, the fastest route is to search the compendium for Sending Stones and drag the entry onto the character's inventory. If the compendium entry is not available in your game or your sheet of choice, you can create a custom item instead and paste the full rules text into the description field, which is often better anyway because it keeps the rules one click away during play.
The real decision is distribution. When two party members each carry one stone, you can duplicate the item on both sheets with a note explaining who holds the partner, or you can keep a single copy on a shared party handout. Duplicating is more convenient during play but risks confusion when one player forgets which stone they have. A short line in the item description, such as "paired with the stone carried by Kaelen," prevents most mix-ups.
Drag-and-Drop vs. Custom Items
Compendium drag-and-drop is fast and accurate, but it treats the item as static text with no recharge tracking. Since Sending Stones recharge at dawn rather than on a rest, the standard long-rest reset on most sheets will not model it correctly. If you want a visible reminder, build a custom item with a description that states the recharge condition clearly, and consider adding a zero-cost "resource" or a simple checkbox in the item name, such as "Sending Stone (used)."
A custom item also lets you embed the house rules. If your table decides that a stone must be held in a free hand, or that the message is audible as a faint whisper to anyone within five feet of the user, putting that in the item description means nobody has to stop the game to look it up. For games using the Shaped sheet or another ruleset, the same logic applies: the item text is your documentation, so write it the way you want it ruled.
Building a Chat Macro That Reminds Everyone of the Rules
A macro turns the item into a one-click action and removes the awkward pause where everyone tries to remember the word limit. In the character sheet's Attributes & Abilities tab, create a new ability and paste something like this: &{template:default} {{name=Sending Stone}} {{Target=Bearer of the paired stone}} {{Message=25 words or fewer}} {{Reply=25 words or fewer}}. When the player clicks it, Roll20 posts a clean card to chat with the reminders built in, and the message itself can be typed alongside it or whispered separately.
For a private version, prefix the macro with a whisper command so only the DM sees it, such as /w gm &{template:default} {{name=Sending Stone}} {{To=the bearer of the paired stone}}. Once the ability exists, check the box labeled "Show as Token Action" so it appears whenever the player selects their token on the virtual tabletop. A handful of chat commands are worth memorizing for these moments:
- /w gm sends a message only to the DM, which is the default channel for stone messages.
- /w "Player Name" whispers to a specific player, useful for relaying a reply.
- /desc posts descriptive text to chat without a character name attached.
- /em posts an emote in the third person, handy for "the stone grows warm in your hand."
- /talktomyself hides your message from everyone, which is helpful for testing macros.
Running Sending Stones at the Virtual Table
The biggest difference between a physical table and Roll20 is that private conversations have to be engineered. In person, a player can lean over and mutter something to the DM, and the other players simply see a brief sidebar. Online, everything either appears in the shared chat log or has to be explicitly whispered, which means the DM needs a reliable relay routine. The cleanest version is simple: the sender whispers the message to the DM, and the DM whispers the reply back to the sender only.
Pacing matters just as much as secrecy. Because using a stone costs an action, a message sent mid-combat is a real tactical choice, and the DM should treat it that way rather than letting it happen for free. Outside combat, a short exchange is a nice breather, but three consecutive back-and-forth messages can eat ten minutes of table time. Keeping NPC replies terse, mysterious, or slightly unhelpful is both good drama and good time management.
Whisper Workflows for Private Conversations
The standard workflow is for the player to type /w gm followed by the exact message, including the word count if they want to be safe. The DM then replies with /w "Character Name" so the answering voice appears in the sender's chat log alone. If both stones are held by player characters, some tables let the two players whisper each other directly, which is faster but bypasses the DM entirely and makes it easy to forget the twenty-five-word cap and the once-per-dawn limit.
For longer campaigns, keep a running journal entry called something like "Stone Traffic" that logs each exchange with a session date. This is invaluable when a villain later refers to a message, or when the party tries to remember whether they warned the duke about the ambush. Roll20 also supports handout ownership, so you can hand a player a private note about what their stone felt like when it activated, which is a nice way to deliver sensory detail without cluttering the main chat.
Handling Planar Failure, Destroyed Stones, and Paired Bearers
If the target of a sending is on a different plane of existence, the spell has a small chance of simply not arriving. Rolling that check in the open with /roll 1d100 and calling a failure on the low end keeps the result fair and dramatic, and it avoids the sour feeling of a DM fudging a hidden roll. When the message fails, describe the silence rather than the mechanic, and let the players draw their own conclusions about where their ally has gone.
Destroyed stones and changing bearers create excellent story pressure. If one stone is shattered, the partner becomes an ordinary rock, and the players usually will not discover that until they try to use it in a crisis. If a stone changes hands, whether looted by a goblin or gifted to an NPC, the target of every future message changes with it. That single rule is enough to build an entire arc around a missing stone and the stranger who now answers when the party calls. Homebrew variants are easy too, such as a third stone that should not exist, a pair that transmits to something older and hungrier than a person, or stones that leak a few words to anyone standing nearby.
Set up a macro, pick a whisper habit, and hand your players their stones before the next session starts. The moment a fighter uses an action in the middle of a fight to send twenty-five desperate words to an ally two cities away, Sending Stones stop being inventory clutter and start being the reason your table remembers that encounter.