The Tupperbox alternative for the whole RP server

After inviting Tupperbox to your server, register a character with tul!register CharacterName proxytag — for example, tul!register Kira K:text. Then anywhere in chat, type K:hello and your message gets reposted via webhook with the character name and avatar you set. Edit a Tupperbox message by reacting with the X emoji to delete + retype, or react with the pencil emoji + reply to edit. Multiple characters per user work the same way, each with its own proxy tag.

Go to tupperbox.app, click "Invite Bot", authorize for your server. Discord asks which permissions to grant — Tupperbox needs Manage Webhooks (to create proxy webhooks per channel), Manage Messages (to delete the original "trigger" message), and Send Messages. Grant all three. Once Tupperbox joins, run tul!help in any channel to see commands. Most servers also pair Tupperbox with a roleplay server template — see our roleplay server template page.

React to your Tupperbox message with the pencil emoji, then reply to it with the new text. Tupperbox deletes the old message and reposts via webhook with the corrected text. Alternative: react with the X emoji to delete entirely, then re-type with your proxy tag. Important: only the original author can edit their own Tupperbox messages — Tupperbox tracks who triggered each webhook post.

For roleplay servers that need character proxying plus lore, moderation, character approvals, and AI NPCs, VibeBot builds the full stack as one custom bot. If you only want pure proxy-bot functionality on the shared-bot model, PluralKit covers the same webhook mechanic, with tooling aimed at plurality systems and nothing beyond proxying.

Tupperbox is a single hosted service. When it has outages (which happens a few times a year, sometimes for days), every server using it loses character proxying simultaneously. Check the official Tupperbox status channel in their support server first. The longer-term fix: build your own bot with VibeBot — a custom bot you control means no shared-bot outages — or keep a backup proxy bot configured for your characters.

They use the same underlying webhook proxy mechanic. PluralKit was built for the plurality community (multiple alters sharing one body) with front-tracking, system management, and a clearer mental model for that use case; Tupperbox's UX is aimed at general roleplay (D&D characters, OCs). Both are single-purpose shared bots — VibeBot covers the same proxy mechanic as one of 39+ behaviors in your own custom bot.

Yes — VibeBot's character-proxy builder uses the same Discord webhook mechanic as Tupperbox. The difference is you build your own bot, with your own custom name and avatar, and proxying is just one of 39+ behaviors. You also get lore tools, IC/OOC moderation, and AI NPCs that Tupperbox doesn't offer.

Character data lives in Tupperbox's database, keyed to your Discord ID. There's no automatic export, but the data (character name, avatar URL, proxy tags) is short enough to migrate manually for most users — PluralKit reads Tupperbox-format exports, for example. For VibeBot, you re-add each character via the proxy builder — usually 10-15 minutes per character, and after that the bot and every character in it are yours.