Setting Stally up

For whoever runs the Discord server. It takes about five minutes, and most of it is one command.

The short version:

Add Stally to your server.
Run /stall-setup in the channel you want to be your market.
Run /help and work the checklist it gives you.

Everything below is detail on those three, plus the two things worth doing afterwards.

Before you start

Worth knowing, because it is a short list:

Stally only acts where you ask it to: a channel you turn into a market, plus wherever somebody runs /help, /welcome, /stall-list, /where or /events.
It cannot read your messages. It receives slash commands and button presses and nothing else. That is a property of how it connects to Discord, not a promise it is making.
It asks for four permissions and no more: View Channel, Send Messages, Embed Links, and Create Events. No Manage Messages, no Read Message History, no Manage Roles, no Administrator.
Create Events is the only one it can work without. It lets Stally put an event in your server's own Events panel. Without it the event is still posted and people still sign up. The panel entry is simply missing, and Stally says so rather than failing quietly.
The only permanent message it posts is one summary per market channel, which it edits in place. Everything else is either private to you or deleted within a day.

If you want the longer answer to why first, read What Stally does.

1. Add it to your server

Add Stally to your server. The link carries the four permissions above; there is nothing to configure at invite time.

If Stally is already in your server but cannot add events to the Events panel, it is missing Create Events. Open the link again and Discord will ask you to approve the one permission, or grant it in Server Settings → Roles. /help → Setup check says which of the two you are in.

2. Turn a channel into a market

In the channel you want the market to live in. The command turns this channel into one:

/stall-setup name:"Guild Forge" game:paxdei world:demeter

name is what customers see. world decides which market prices are read from, and its suggestions list the ones that exist. Optionally set owner to hand the market to whoever will actually run it. It does not have to be you, and they will not need Manage Server afterwards.

Needs Manage Server. One market per channel; a server can have as many as it has channels.

3. Run `/help` and work the checklist

This is the step that replaces reading anything. /help → Setup check shows a live checklist of what a working market needs, computed from your server as it is right now, and every imperfect line names the command that fixes it:

✅ I can post here. Send Messages, Embed Links and View Channel are all set.
✅ This channel is a stall: Guild Forge.
⚠️ No crafters listed, so only you and server admins can claim orders. /stall-config → People.
✅ Selling the whole catalogue. Narrow it in /stall-config → What's for sale.
✅ Prices cached, updated 15:12 UTC.
⚠️ No summary message yet. /stall-config → Rebuild the summary posts it.

Only somebody who can manage the server, or who owns the market, sees the checklist. Members get the ordering help instead.

Two lines are worth pre-empting, because almost every server hits both:

Crafters, in /stall-config → People. Until you set this, only you and your server admins can claim orders. Crafters are a plain list of people rather than a Discord role, deliberately, so that running a market does not need Manage Roles.
What's for sale, in /stall-config → What's for sale. This narrows a 1,743-item catalogue to what your crafters actually make. Leaving it open is a valid choice, not a mistake.

4. If your guild schedules things, run `/events`

Nothing has to be set up first: /events works in any channel, in a server with no markets at all. Only you see the reply.

Set two things once, under Settings. The timezone your server thinks in, because otherwise every time is read as UTC, and who may create events. Anyone can sign up; only admins, the people you list, and whoever created an event can change it.

5. Give people a front door

/welcome shows what is in your server: your own links, and every market, each one linking straight to its board. Two things are worth doing once:

Add your links. /welcome → Manage links takes up to ten. Right-click a message, choose Copy Message Link, paste it and give it a title. Your rules, your loot policy, anything a newcomer would otherwise have to be told twice.
Post it where newcomers land. /welcome public:True puts the panel in the channel for everyone, with a Refresh button anyone can press when it goes out of date.

A market can be kept off that panel without hiding it anywhere else, in /stall-config → Tagline, banner & listing. It stays findable through /stall-list and /where.

Optional: tidy the command picker

By default all fourteen commands appear in every channel's picker. Most of them only work in a market channel, and anywhere else they answer "this channel isn't a stall" and do nothing, so hiding them is cosmetic. The exceptions matter: /help, /welcome, /stall-list, /where and /events are useful anywhere, and /stall-setup has to run in a channel that is not a market yet.

If the clutter bothers you: Server Settings → Integrations → Stally → Commands, deny All channels at the app level, allow your market channel, then put /stall-setup back to all channels so a second market can still be created.

Two things that will confuse you if nobody says them:

You will not see any difference. The Administrator permission bypasses channel-based command restrictions, and a server owner always has it. The restriction works for every ordinary member, so check it with a non-admin account.
Adding a second market channel later means updating this, or the commands go missing there while still working in the old channel, which looks exactly like a bug.

Pausing, closing, and deleting

Three different things, and the differences matter.

Pausing, in /stall-config → Availability. The market stays alive: the queue, /orders, the summary and every order already placed keep working. Only new orders are refused. This is the one for a quiet week, a holiday, or a crafter who needs to catch up.

Closing, with /stall-disable. The channel stops being a market and every command in it says so. History is kept, and an admin can reopen the channel later by running /stall-setup in it again. Neither of these destroys anything.

Deleting, with /stall-setup revert:True. This one does destroy things, and it is the only thing in Stally that does. It erases the market, every order in it, everything in their history and anything already archived. It exists so that a server admin can answer somebody who asks for their data to be deleted.

It asks twice, and tells you the number of orders about to go both times: first a warning naming exactly what disappears, then a box asking you to type the market's name. Type it wrong and nothing happens. Manage Server only, not the market's owner, unless they have that permission too.

What "done" looks like

A member runs /order, picks an item, and the summary updates within a few seconds. A crafter runs /queue, claims it, and works through claim → ready → delivered in that one message. The customer is pinged once when it is ready, presses Thanks!, and both messages disappear from the channel.

If you use events: someone runs /events → Create, fills in a name and a time, confirms, and the post appears with a button per role. People press one, the roster fills in, and sign-ups close on their own when the event starts.

Nothing needs babysitting after that. An order nobody claims and a claimed order nobody works on both get chased on their own, sign-ups close without anyone remembering to close them, and Stally deletes its own messages once they are older than a day.

If something looks wrong

Run /help → Setup check first. It is the diagnostic, not just the introduction: permissions, market, crafters, catalogue, prices and summary in one place, which is faster than guessing.

Commands appear but nothing happens in a channel. It is not a market. Run /stall-setup there, or use the market channel.
Commands work but Stally never posts. Missing Send Messages or Embed Links in that channel. A channel override beats the invite, and this is the commonest one by a distance.
Items show no price. No price data cached for that world yet. Ordering is never blocked on a price.
The catalogue looks empty. The tag filter matches nothing. /help marks this as a failure rather than a warning, because a market selling nothing looks like a broken bot to every customer.
The summary is missing. /stall-config → Rebuild the summary. It reposts if the message was deleted.
A crafter cannot claim. They are not on the crafter list. /stall-config → People.

Still stuck? Ask in the Stally Discord. That is what it is for.