TupperboxA bot dedicated to replacing user messages to emulate having multiple accounts. Great for plural users and roleplay.
Invite button not working?
Please use this link (click or copy/paste into your browser) to invite the bot to your server: https://discord.com/oauth2/authorize?client_id=431544605209788416&scope=bot&permissions=536996928
Tupperbox allows you the convenience of having multiple accounts with different names and avatars without any of the hassle of logging out and in to each of them.
These "accounts" made with the bot are termed "tuppers" by default and the act of sending a message through a tupper is called "proxying". You can set any prefix and suffix (together termed "brackets") to proxy with a tupper.
Proxied messages are sent via webhooks and show up with a "Bot" tag, which obscures who originally sent the message - but Tupperbox does not provide any anonymity by default. Any user can easily react to the proxied message with a ❓ to see who originally sent it.
Tupperbox has found widespread usage in several communities that benefit greatly from these pseudo-accounts, such as plural communities and roleplay servers.
It is successful in these communities because they benefit greatly from being able to send messages under various different 'identities' on the fly, whether that's to represent another person speaking with the account or a character's line of dialogue in a roleplay.
It comes with many moderator tools to prevent abuse as well as an active support community in our support server, you can register as many tuppers as you want, and organize them with groups, individual tags and descriptions, and other fun details.
Like any bot, the help command is the best way to learn how to use it, and can be executed by typing
However, there is a slight learning curve in using the bot, but getting started is very easy. The most basic function of the bot is the proxy function, which is demonstrated below:
Above, I registered a new tupper and then sent the message
>>Hello! which was detected, deleted, and replaced with a message that appears to be sent by my newly registered tupper.
The brackets (
>>text in the example) represent a pattern that Tupperbox looks for in order to activate that tupper. Simply replace the
text in the brackets with what you want the tupper to say, and Tupperbox will recognize the surrounding symbols as an instruction to send the message with your registered tupper.
After registering a tupper, you can edit its info with commands such as
tul!nick, or remove it any time with
tul!remove. Refer to the bot's help command for usage details.
React to a proxy you sent with ❌ to delete it or 📝 to edit it.
Manage your tupper groups and who belongs to which with the
Manage server-specific configuration using
tul!cfg. For example, to instruct Tupperbox to disallow a specific role from proxying (using tuppers), you might use
tul!cfg deny proxies @role. You can change Tupperbox's prefix with
tul!cfg prefix. If your server leans towards a specific usage of Tupperbox, you can instruct Tupperbox to call "tuppers" something else such as "characters" or "headmates" using
If you find yourself mainly using the same tupper a lot in a particular server or channel, check out the
tul!auto command to configure Tupperbox to automatically use that tupper without having to type its brackets.
If you find that Tupperbox is conflicting with another bot that serves a similar purpose (such as PluralKit or Jinkaku) you can use
tul!proxy disable to turn it off in a server or particular channels.
View yours or another user's tuppers with the command
If you ever wonder who sent a tupper message (since you can't easily tell at first glance), you can reply to the message with
tul!showuser or react to it with ❓ to reveal who sent it.
tul!cfg log #channel to set a channel where all usage of tuppers is logged for reference.
You can control your data with the commands
tul!purge. Tupperbox data may be compatible with other bots that serve a similar purpose, such as PluralKit.