Server directory
A card, tags, a button to bump. The directory sorts by last bump, not by size.
In short
Your server can show itself in EnderBot's public directory: a card, a description, tags, and a spot in a list that keeps reshuffling.
The directory is not a queue, it is a sorted list. By default it follows the last bump, which gives an active little server its shot ahead of a big sleepy community.
Being listed asks five things at once, and a single missing one takes the server off the list. Nothing is lost for all that: the card stays saved and comes back as soon as the missing condition is met again.
One page serves 24 cards, 100 at most when the directory is queried some other way. The four sorts fight over the order, one at a time, and filters stack under the sort rather than replacing it.
The bump is the only recurring action: one command, 2 hours of waiting, a counter that ticks up. Everything else, description, tags, banner, is set once and for all from the dashboard.
Five conditions, all at once
A single missing one takes the card off the list. That same list decides partnership eligibility: an invisible server strikes none at all.
- Some depend only on you, the others on the bot's moderation. The card comes back on its own as soon as the missing condition is lifted.
Five restrictions, one door each
A restriction closes one precise door, and the first one closes them all. The table reads the four doors the bot opens to a server.
| What each restriction closes | Directory | Partnerships | Encounters | Invite |
|---|---|---|---|---|
 GlobalCloses everything, without looking at what is asked. | Closed | Closed | Closed | Closed |
 DirectoryPulls the card from the public list and from searches. | Closed | Open | Open | Open |
 PartnershipsForbids striking a partnership with another server. | Open | Closed | Open | Open |
 EncountersCuts server encounters. | Open | Open | Closed | Open |
 InviteBlocks the invite link from being shared. | Open | Open | Open | Closed |
- A directory restriction does not merely hide the card: it drops the server from the public page's queries. Nobody finds it again, even knowing its name.
Four sorts, one active at a time
One page serves 24 cards, 100 at most when the directory is queried some other way. Filters stack under the sort without ever replacing it.
| Filter | Shape | What it does | |
|---|---|---|---|
 | Search | by name | Looks inside the server name, ignoring letter case. |
| Language | inside the tags | Language is a tag like any other, so it filters like a tag. |
 | Tags | all required | A server must carry every requested tag, not just one of them. |
| Activity | minimum tier | Drops servers below the chosen tier, leaving the others in place. |
- Changing the sort does not change the cards, only their order. Filters, on the other hand, remove some.
The featured row obeys three rules of its own.
Eight things a card carries
Everything is set from the dashboard, except the last two rows: those are measured, never typed.
- The short description fits in 100 characters, the long one in 500. Past that, the input is ignored on save.
The message of a successful bump
A bump sends no card and no button: plain text, in the channel the command was typed in. Between two bumps, 2 hours of waiting.
⏰ You can bump again in 2 hours.
- The text
The server name is taken from Discord as it stands when the command runs.
- The next one
The countdown starts from the successful bump, never from the last refused attempt.
- The timestamp is rendered by Discord, so everyone reads it in their own timezone and it refreshes on its own.
Four refusals, one sentence each
The command always answers, including when it bumps nothing. The sentence you get names the missing condition, and the 2 hour wait is only one of them.
- A refusal does not spend the wait: the countdown only moves on a successful bump.
The commands
Bump your server to the top of the public server list · servers only