Economy · Concept

Partnerships

A pact between two servers: a cross-announcement, and the referral system that makes it measurable.

In short

A partnership binds two Discord servers. Each introduces the other to its community, and what the announcement brings in shows up in the referrals it triggers.

A pact runs through four states, from the first message sent to the end of the deal, and each state decides what remains editable. The targeted server must hold four conditions to be announceable: a partnership does not open with a server the public page already refuses to show.

Eligibility is not a checkbox but the very rule of the public server page, read in the same place. One restriction laid down by moderation is enough to break it, and five restrictions exist, one of them global and blocking everything at once.

The partnership pays nothing by itself. What it brings in goes through referrals: a player of level 1 000 and above hands out their code, a player of level 2 500 and below may enter it, and the referred player then explores with an XP multiplier of x3.

A referral is a window, not an annuity. It lasts 21 days, pushed up to 50 days by the referrer's three premium tiers, and the link closes when the referred player reaches level 3 000. A partnership therefore gains by bringing players in early.

The announcement itself

The message has no template: it is composed freely in the web builder, block by block, then goes out as two twin copies, one on each side. What follows is an example, not an imposed model.

Example
EnderBot
BOT
1🤝 New partner: welcome to Railgun, go take a look!
2Railgun
3A community of several thousand members built around PvP and weekly events. Open voice rooms, staff around at all hours, and EnderBot installed there since day one.
4railgun-banner.png
5Official partner · pact live
6 Join Railgun
  1. 1
    The free text
    Written as is in the builder. No block is mandatory, this one included.
  2. 2
    A title
    A text block like any other, simply brought forward: nothing forces a message to carry one.
  3. 3
    The body
    Written by the server owner, never generated: the bot writes no line in their place.
  4. 4
    An image
    Served as is, from the partner module or from any link: nothing is retouched at send time.
  5. 5
    A footer line
    Here the official partner badge, but the line is written freely.
  6. 6
    Link buttons
    The only clickable component a stored message can carry: a link survives a restart, a coded button does not.
The builder offers others
A separator
A line, or just blank space, to cut the message into parts.
A gallery
Up to ten images side by side instead of a single one.
A thumbnail
An image set to the right of a text rather than across the full width.
An attached file
A file sent along with the message, never a remote link.
A coloured frame
The block's edge colour is picked: it is the only colour in the message.
  1. State 1
    Requested
    The request is filed, the deal is not written yet.
    texts can be written
    the channel can change
    the announcement can go out
    the pact can be closed
  2. State 2
    Draft
    The announcement takes shape: texts, channel, artwork.
    texts can be written
    the channel can change
    the announcement can go out
    the pact can be closed
  3. State 3
    Published
    The announcement is out, the pact is running.
    texts can be written
    the channel can change
    the announcement can go out
    the pact can be closed
  4. State 4
    Ended
    The deal is closed. It can be read again, never reopened.
    texts can be written
    the channel can change
    the announcement can go out
    the pact can be closed
  • The home message goes to the official server, and its channel is frozen at publish time: changing it later does not move what is already posted.
  • The builder is the message-template one: text, images, separators, link buttons. Everything there is optional, the bot fills in no line, and no interactive component is accepted.

What the dashboard counts

Four steps are counted, and two rates link them. The bar says what is left from one step to the next, the numbers stay your server's own.

Views
pages opened
Visitors
distinct people
Invite clicks
buttons pressed
click rate
Joins
accounts joined
join rate
  • The first two steps come from the public page analytics and are missing when it is unavailable; the last two are counted by the bot itself.

What the pact pays

A partnership pays nothing by itself. What it returns comes through the referrals it triggers and through the structures on the server across from you.

The referred player's multiplier
×3
A player brought in by the announcement explores with this XP multiplier for 21 days.
One attribution only
1
A player carries a single referrer. A second attempt is refused, months later just as on the same day.
Partner structures
+50 %
A structure placed on a partner server produces more. An official partner reaches +100 %.
The listing conditions
4
The targeted server must meet them to stay announceable. A moderation restriction removes them without closing the pact.
  • None of these figures depend on the partner server's size: they apply to the first referred player exactly as to the hundredth.

Who decides what

Three hands touch the pact, and none of them does another one's work.

The server owner
They write the texts, pick the channel, publish and close. None of it is delegated.
The EnderBot team
It approves the request. Without that approval the announcement never leaves the draft.
The bot
It checks that the targeted channel really is a text channel it can write in, then posts both messages together.
  • None of the three stands in for the other two: that is what keeps an announcement from going out unread.

The referral bounds

Referrals come down to four numbers: a window of 21 to 50 days, and two levels that decide entry and exit.

The XP multiplier
×3
What the referred player gains while exploring, for the whole length of the window.
The referral window
21 / 35 / 50
In days: 50 at best, depending on the referrer's own premium, never the server's.
The referred player's level cap
2 500
Past it a player can no longer enter a code: referrals aim at newcomers.
The level that closes the link
3 000
The referred player reaches it, the referral stops, and whatever window was left is lost.
  • The link settles at level 3 000. The window may still be running: it is the referred player's progress that stops it, not the calendar.

The points shop

Referral points are only spent here. Three resource families in tiers, plus cosmetics that are bought once.

Small purse
200 endercoins
50 pts
Purse
750 endercoins
150 pts
Large purse
2 500 endercoins
400 pts
Handful of essence
2 000 essences
50 pts
Pouch of essence
7 500 essences
150 pts
Case of essence
25 000 essences
400 pts
Mana vial
500 mana
75 pts
Mana flask
1 500 mana
200 pts
Mana carafe
5 000 mana
500 pts
Slate cat skin
once only
10 000 pts
Ambassador title
once only
2 000 pts
Recruiter title
once only
5 000 pts
Legend title
once only
10 000 pts
  • The price is the same for everyone: no premium tier discounts the shop, the only lever is how many referrals you carry to the end of their window.
  • A cosmetic already owned is no longer offered. Resources are rebought as often as the points allow.

The commands

>referral
>ref

Manage your referrals and referral rewards

code Get your referral code to share with new players
join Join a referral program using a code or mention
  • <code> Referral code or @mention of the referrer
shop Browse the referral shop
Also historyprogressstatus