Start a clan

Two names and an address, and your clan is live — free, and there is nothing to wait for. This is that, plus the four things worth doing straight afterwards.

Free no card, no trialLive the moment you submit~4 min to a working clan

Step 1

Before you start

You need a Discord account, and that is the whole list. Sign in on beta.anvilosrs.com first: a clan needs an owner, and signing in is how the site knows that is you. Start from Start a clan on the platform pages, or go straight to beta.anvilosrs.com/clans/new.

It costs nothing. There is no plan to pick, no card to enter, and no trial that expires and takes your board with it — a clan starts free and stays usable.

You will be its owner

Owner is the one role nobody can take from you, and it goes to whoever creates the clan. Add staff afterwards from Admin → Clan; see the /guide/moderator.

Step 2

Name it, and pick its address

Three fields, and only two real decisions. The form checks the address as you type and tells you before you submit.

In-game clan nameRequired, and it has to match OSRS exactly. This is not decoration: roster sync matches on it and refuses a roster reported under any other name. That is what stops somebody else’s member list landing on your site.

Clan nameOptional. What people see — on the site, and on every Discord post. Leave it blank and your in-game name is used for both.

AddressYour clan lives at beta.anvilosrs.com/c/your-slug. It is suggested from the name you typed, you can edit it, and a handful of words are reserved. Pick one you will still like in a year: it is the link that ends up pinned in your Discord.

The in-game name is a lock, not a label

If your clan renames in game, change it here too — until you do, roster sync refuses the new name. That is the check working, not a fault.

Step 3

It is live

Press Create clan and it exists. No provisioning, no queue, no “we are building your site, check back in a few minutes” — a clan is a row, so it is serving before the page finishes changing.

You land on a choice of Set it up, which opens the wizard, or Take a look first. Nothing breaks if you wander off and come back tomorrow; the wizard remembers which steps you have done.

Step 4

The setup wizard

Four things stand between a fresh clan and a running event. The wizard walks them in order and skips whatever you have already done.

Name it in DiscordYour display name, your in-game clan name, and an invite link to your server. The invite is what lets sign-up pages and guides point people at you.

Connect DiscordOne shared bot, so there is no application to register and no token to paste. Approve it once and it can post to your channels and read your roles.

Give it a channelAn announcements channel for event posts. Optionally split the plugin’s feeds out: rare drops in one channel, deaths in another, so neither drowns the other.

Make a boardThe first event. Pick a format, add tiles, open sign-ups — that is the /guide/admin, and it is the longest of the four by a distance.

You can skip the wizard entirely and do all of it from Admin → Clan later. It exists because the order matters when you have never done it: Discord before channels, channels before a board that wants to post to them.

Step 5

Getting your members in

Nobody has to sign up, register, or be invited one at a time. Your roster comes from the game.

Roster sync (do this one)Open the clan window in game with the plugin running and press the Anvil button in its title bar. Your whole member list arrives with ranks intact, and it refuses a roster from a clan whose name does not match yours. Repeat it whenever people join or leave — see the /guide/plugin.

They just playAnyone running the plugin who logs in is recognised automatically. If they are not on the roster yet they are tracked as a guest — visible, countable, and one sync away from being a member.

By handAdmin → Clan takes names one at a time, for the person on mobile or the official client who cannot run the plugin at all.

Guests are not a problem to solve

A guest is simply somebody we have seen who is not on your roster — a visiting clan’s player, an alt, someone who joined this morning. They can play in events without ever becoming a member.

Step 6

Your first event

The shortest path to something happening: make a board, add a handful of tiles the plugin can see by itself, open sign-ups, and start it. Drops, kill counts and XP then file themselves.

Two guides carry the weight here. The /guide/admin runs start to finish — Discord, teams, launching, and what to do when it ends. The /guide/board is about tiles specifically: what each kind can actually detect, and the ones that import cleanly and then never fire.

If you would rather not build a board at all in your first week, run a Skill of the Week or Boss of the Week instead. Everyone on the roster is enrolled automatically, the standings move off the hiscores, and there is nothing to author.

Step 7

Events across several clans

An event does not have to belong to one clan. Several clans can run the same board together — two, or a dozen — with each side keeping its own roster, its own staff and its own half of the moderation.

They can also share one pool of players rather than sitting on opposite sides of a scoreboard: one event, everybody in it, however the teams end up cut. Clan-versus-clan is one shape this takes, not the only one.

Each visiting clan gets an invite link per team, so you never collect a single RSN by hand, and a seat that lets their own moderator approve their own members’ proof. The /guide/clan-vs-clan covers hosting one.

Nothing to buy

Joining somebody else’s event is free, and so is hosting one. A clan that only ever turns up to other people’s boards never needs anything beyond its own free clan.

You can change every one of these later from Admin → Clan, except the address — that one is worth a moment’s thought now.