BackDrop

If you run a Discord roleplay server, you already have the pieces: channels, scenes, maybe muses in MultiMuse, lore scattered across threads. What you often don’t have is one place that holds the geography—a map everyone agrees on, that stays current, and that new players can open without asking “which Google Doc is the world again?”

Backdrop is that shared map. You stack layers of art the way you would on a table, drop pins where locations actually matter, and write lore right on those pins so the story lives next to the place it belongs. When you are ready, you give people a single link—/map/your-slug on backdrop.quest—and they get the same live view your group sees: zoom, pan, read pins, and (if you want it) see who is roughly on scene where.

It is built for how RP servers really work. You sign in with Discord; editors use roles you already trust. You can leave a map public for anyone with the link, add a viewer password if you only want your circle, or open the map as a Discord Activity so it sits beside voice without juggling another tab.

If you use MultiMuse, Backdrop is meant to feel like a natural extension: you can link pins to the channels or forum categories where scenes actually play, so the roster on the map lines up with where people are writing—not a separate fiction you have to maintain by hand. StageHand-style workflows still make sense; Backdrop is the “where on the map is that scene?” layer on top.

Getting started is intentionally small: invite the bot when the dashboard asks for it, create a world in the builder, add your first layer and a few pins, wire Discord links when you care about rosters, then share your /map/... link with your group. The full walkthrough—including roles, publishing, and passwords—is in the documentation.

If you get stuck or want to show off what you built, come hang out in Backdrop support. We are friendly, we ship in the open, and we actually use this thing on our own servers.