For server owners

Raids

Post an X target, your community smashes likes and reposts, and Coral tracks the goal and the leaderboard. No money, recognition only.

What a raid is

A raid points your community at one X post and rallies engagement on it. You post the target, everyone smashes likes and reposts, and Coral tracks live progress toward a goal and keeps a leaderboard of who showed up. There is no money in it. The reward is recognition: streaks, badges, and a weekly top raiders card.

Who can start one

Raids are admin-only. On Discord you need the Manage Channels permission; on Telegram you must be the chat creator or an administrator. Members cannot start a raid, but anyone in the channel can join one once it is live.

Start a raid

Run /raid with the tweet you want to rally on. Only the URL is required; everything after it is optional.

/raid <tweet_url> [metric] [goal] [duration] [--lock]

Here is what each argument does:

Command	What it does
`<tweet_url>`	The X post you want the community to rally on. Required. Paste an existing tweet.
`[metric]`	What counts toward the goal: likes, retweets, or replies. Defaults to likes.
`[goal]`	The target count. Leave it off and Coral picks a sensible number above the current count.
`[duration]`	How long the raid runs, like 30m or 1h. Defaults to 30 minutes.
`--lock`	Restrict the channel to admins for the run. Off unless you add it.

Defaults when you leave them off

Metric is likes, the goal is a sensible bump over the tweet's current count, the window is 30 minutes, and lock is off.

A worked example

This starts a raid on a tweet with a goal of 200 likes and a 30 minute window:

/raid https://x.com/openseaships/status/123 likes 200 30m

Coral posts a live raid card with the target, the goal, a progress bar, the crew count, and the time left. It updates in place as people join and as the tweet's likes climb, then posts a celebration card when the goal lands or the window runs out.

Using --lock

Add --lock when you want everyone heads down on the raid. It restricts the channel to admins for the run, so the only thing happening is the raid. Coral unlocks the channel automatically when the goal is hit or the window expires. It is off by default, so most raids never touch channel permissions.

What members see and do

When a raid goes live, everyone in the channel sees the raid card with a button to join.

Tap to join

On Telegram the button is SMASH IT; on Discord it is I raided. Tapping records your spot on the leaderboard and pops a link straight to the tweet.

Counts once per person

Tapping again does not double your credit. Each person counts once per raid, so the crew count and the leaderboard stay honest.

From there it is on you to like and repost the tweet. The card shows live progress while the raid runs, then a celebration card with the top raiders for that raid when it ends, win or not.

Ranks, XP, and roles

Every raid you join earns XP. XP stacks into ranks, an ocean ladder you climb by showing up: Tide, Reef, Deep, Storm, and Kraken Raider. On Discord each rank is a role you wear; on Telegram a rank-up gets a shout in the finale card.

Streaks

Join consecutive raids to build a streak. A live streak earns bonus XP and lights a flame next to your name on the board.

Badges

Chips you earn on the board: a flame for a hot streak, a trophy for a top-three all-time slot, and hammer tiers by total raids.

The ladder

Tide to Kraken, earned at rising XP. The top ranks are a real grind, so they mean something. Coral posts a weekly top-raiders card to your raid channel.

Turning on rank roles (Discord admins)

Rank roles are off until you create them and we bind them. Create one Discord role per rank (Tide Raider, Reef Raider, Deep Raider, Storm Raider, Kraken Raider), then reach out and we will bind each role to its rank for your server. Until then, ranks are still tracked and a rank-up still gets a finale shout, there is just no role to wear.

Two setup musts

The Coral bot needs the Manage Roles permission, and its own role must sit above the rank roles in Server Settings then Roles. Discord refuses to grant a role positioned above the bot, which is the most common reason roles silently do not apply.

Carry your rank across platforms

Link the same wallet

Earn a rank raiding on Telegram, then link the same verified wallet on Discord, and you instantly wear the matching Discord role. The shared wallet is the bridge.

Identity stays yours

XP is tracked per platform, never silently merged. The wallet link is the one explicit, user-controlled way a rank carries over.

Combined raids across Discord and Telegram

A community that lives on both Discord and Telegram can link the two so one raid spans both rooms. A linked raid shares a single goal and one combined leaderboard, and the card shows a per-platform split so each room can see which side is leading. Members tap in their own room as usual; the count is shared.

The link is a config field, not a command

Linking two surfaces is set in tenant config, not from a slash command. If you run a community on both platforms and want one combined raid, reach out and we will wire the two together. Most servers leave them separate, so their Discord and Telegram raids stay on their own.

Goal tips

Aim just above the count

Pick a goal a bit above the tweet's current likes. A goal the crew can actually land in the window feels like a win; an impossible one just fizzles.

Keep the window short

A tight window builds urgency and keeps everyone on the same post at the same time. 30 minutes is a good default.

Paste an existing tweet

Point the raid at a post that is already up rather than asking Coral to post one. You control the target and it is live the moment you start.

More admin controls

Raids sit alongside the rest of Coral's server features. See Admin controls for muting channels and toggling features on or off.