What is Stally, and why would I use it?

Stally does three things a guild usually does by hand.

It runs a crafting queue, so a request becomes a tracked order rather than a message that scrolls away. It runs an event board, so a raid has a roster that says who is coming and what they are bringing. And it gives newcomers a front door, one message that says what is in this server and where to find it.

You can use one of the three and ignore the other two. Nothing is switched on until somebody sets it up.

The three things

A market

Someone orders with /order, picking the item from a list that already shows the going rate. A crafter claims it with /queue, marks it ready when it is done, and the customer collects. A summary message sits in the channel and always shows the current queue:

🏪  Guild Forge - open orders
    ⏳ OPEN               SB96D2XN  Iron Bind Circlet ×2 - @Aldric
    🔨 IN PROGRESS        3WQ4BRXG  Steel Sheet ×10 - @Bram → @Hilde
    ✅ READY TO COLLECT   QB6695P7  Steel Pickaxe ×1 - @Maren → @Hilde

    3 active · Prices updated 08:13 UTC · updated 09:41 UTC

Item prices come from the in-game market, so a customer sees roughly what a thing is worth as they order rather than finding out afterwards. Your market can follow the market's median, its cheapest listing, or a price you set by hand.

It is not a shop. No money changes hands, no payment is processed, and no prices are enforced. The number Stally shows is information for two people to agree on: a starting point for a conversation, not an invoice.

An event board

/events posts a raid, a gathering run or a guild meeting, and the post carries the sign-up sheet:

┌─ Guild Raid ──────────────────────────────────────
│  Clearing the eastern camps. Bring potions.
│  Led by @ann · 6 September 2026 21:00 · in 4 days
│  🔊 Raid Voice
│
│  🛡️ Tank (2)
│  @bob · @cara ⏰ later
│  ⚔️ DPS (3)
│  @dan · @eve · @finn 🤔 trying
│  💚 Healer (0)
│  Nobody yet.
│  Coming, no role yet (1)
│  @hal
│  Maybe next time (2)
│  @iris · @jon
│
│  Open in the server's Events panel
└───────────────────────────────────────────────────
 [ 🛡️ Tank ] [ ⚔️ DPS ] [ 💚 Healer ]
 [ Arriving later ] [ Trying ] [ Maybe next time ] [ Settings ]

Healer (0) is the line the whole thing exists for. It is the gap a leader is looking for, and it is the one thing a chat thread full of "im in" never tells you.

Pick one button for a plain head count, or tank, DPS and healer for something that needs a shape. People can say they are arriving late or only trying to make it, and both still count toward the roster, because a tank arriving late is still a tank. Sign-ups close a set number of minutes before the start, and you choose how many.

The event also appears in Discord's own Events panel, so it shows up where members already look for one. The roster on the post is the real answer to who is coming, though: Discord's own "Interested" list is invisible to Stally, and the post never pretends otherwise.

A welcome

/welcome prints a single message for somebody who just joined: the server's name, the links you picked out as worth reading, and the server's markets, each name jumping straight to that market's summary board. A market that is not for newcomers can be kept off the list from /stall-config.

Welcome to Northreach

Here is what you will find in this server.

Useful links
- Guild rules - #announcements
- How we split loot - #raids

Markets
- 🔨 Guild Forge - #forge
- 🧵 The Tailor - #tailoring

By default it answers you alone. A flag posts it to the channel instead, for pinning somewhere a newcomer will see it. Sections with nothing in them do not render, so it is never a list of empty headings.

Why a queue beats a chat channel

If your guild crafts for each other, you already have a system. It usually looks like this:

Aldric: anyone able to make me a steel chopping axe?
(nine messages about something else)
Hilde: i can do it, gimme a bit
(two days pass)
Aldric: hey did anyone ever do that axe
Hilde: oh no i completely forgot

Nothing here is anyone's fault. The request is a message in a river of messages, the person who volunteered has no list, and the person who asked has no way to check without nagging. The information exists. It is just scattered across a channel in the order it happened to be typed.

Stally is the same conversation with a spine through it. Three things change:

It answers "is anyone doing this?" without anyone being asked. That is the question that makes crafting-by-chat tiring, and it is the one a queue answers for free.

It chases things so you do not have to. An order nobody claims gets a nudge. A claim that goes quiet gets a nudge, and if it stays quiet the order goes back to the open queue so somebody else can take it. Nothing needs a human to notice it has gone stale.

It tidies up after itself. When Hilde marked that axe ready, Aldric got pinged in the channel, once. When he collected it he pressed Thanks!, and the bot deleted its own messages about that order. What Stally leaves standing in a channel is what you asked it to put there: a market's summary, and any event posts. Everything else it says is either visible to you alone, or deleted within a day.

Why you might not

Being honest about the shape of it:

• It is for guilds who play together, not a marketplace and not a public service. It works inside one server, for the people already in it.
• It only knows Pax Dei today. The engine is not built around that game, but Pax Dei is the only catalogue currently loaded. The event board and the welcome do not care what you play.
• Prices are indicative and can be out of date. They come from community-run market data, and every item card says how old the figure is so nobody treats a stale number as current.
• It cannot read your chat. That is deliberate and permanent, but it does mean Stally cannot pick up an order somebody types as an ordinary message, or notice a raid announced by hand. Everything arrives through a command or a button and nowhere else.

What it asks of your server

Four permissions, and no more: View Channel, Send Messages, Embed Links, Create Events.

The first three are what it needs to speak in a channel at all. The fourth only lets it put an event it created into your server's Events panel. It cannot touch events anybody else made, and Stally works without it, minus that one convenience.

No Manage Messages. No Read Message History. No Manage Roles. No Manage Events. Certainly no Administrator. It cannot read your conversations, not the current ones and not the old ones, cannot touch anyone's roles, and cannot delete anyone's messages but its own.

It acts only in a channel someone deliberately turned into a market, plus wherever a person runs /events, /welcome, /help, /stall-list or /where. Adding it to a server changes nothing until somebody sets something up.

Getting started

Three steps, about five minutes:

1. Add Stally to your server. The link carries the four permissions above and nothing else.
2. Run /stall-setup in the channel you want to be the market. Needs Manage Server.
3. Run /help in that channel. It checks your setup and names what is still missing: crafters, what the market sells, whether prices are loaded.

Then /events if your guild schedules raids, and /welcome to give newcomers somewhere to land. Neither needs a market, and neither needs the other.

Setting it up walks through all of it properly.