How to Build and Run an Old School RuneScape Clan Discord Server With YourBot

Updated September 2026

Build an Old School RuneScape clan Discord around the things members actually do together: finding a team, learning a raid, sharing progress, organizing events, and contacting the right officer. Use YourBot’s Start Your Server to create the foundation, then configure its services for your clan’s recruitment, activity listings, voice rooms, announcements, and moderation.

An OSRS community needs more than a renamed MMO template. Account restrictions, loot agreements, changing RuneScape names, mobile participation, and the difference between a learner raid and an experienced team all affect the setup. A Discord role should never imply that someone’s game account, wealth, or trustworthiness has been verified.

This guide follows Waystone, a fictional 120-member social and PvM clan with regular accounts, Ironman players, returning adventurers, and volunteer raid guides. Its channel names, schedules, capacities, and settings are recommended examples—not YourBot defaults or a claimed customer deployment.

Start With How OSRS Clans Actually Operate

Separate community access from clan membership

Jagex’s Clans system guide describes in-game recruitment, member ranks, permissions, guests, and a home world. These are separate from your Discord server.

Keep three records distinct: who may participate in Discord, who belongs to the in-game clan, and who has been approved for a particular staff or activity role. YourBot can organize an application and grant a configured Discord role; an officer still handles the corresponding in-game decision.

This is not merely theoretical. FOH’s public recruitment instructions direct applicants through Discord and invite them to guest in clan chat while awaiting a decision. The same site highlights skilling competitions, event organization, and achievements. Those are useful workflows to design for, not a reason to copy another clan’s entry requirements.

Make learning and experienced groups different experiences

We Do Raids describes a community built around learning raids and finding teammates. A clan can apply the same useful distinction at a smaller scale: a learner session should advertise patient instruction, while an experienced run should explain its actual expectations.

Define abbreviations on first use: PvM means player-versus-monster activity; CoX, ToB, and ToA refer to Chambers of Xeric, Theatre of Blood, and Tombs of Amascut. KC means kill count. Do not assume a returning member knows every shorthand in a listing.

Account restrictions belong in the planning conversation

Ironman participation is not a single yes-or-no setting. Account variants can have different trading, grouping, prestige, and death consequences. Jagex’s Group Ironman explanation distinguishes the small in-game group from wider social participation and explains why some activities with outsiders affect prestige.

Ask participants to check their current account restrictions and in-game warnings before joining. Do not promise that a learner activity is safe for every Hardcore or Group Ironman account, and do not pressure someone to change account status to participate in your clan. Label activities that require game membership separately from access to your Discord community.

Leave room for the current game, not only familiar raids

Sailing is already part of OSRS: Jagex’s launch announcement dates its release to November 19, 2025. Give returning players a place to ask about it instead of describing it as an upcoming skill.

For a Sailing meetup, record the world, port, activity, and required unlocks. Do not assume a Discord participant cap describes boat capacity. Keep quest and exploration spoilers inside clearly labeled discussions, and add new activity templates as the clan’s interests change.

Give YourBot’s Ten Services Defined Responsibilities

YourBot’s built-in services provide the shared foundation. Assign each one a job before enabling it.

Review current YourBot pricing, AI usage estimates, and any additional marketplace-plugin charges. An available service is not a requirement to use it immediately.

Design Roles and Access Before Channels

Use a small set of permission-bearing roles, then separate optional interests from authority.

Account-interest labels are self-reported. Do not automatically issue a “Trusted Trader,” lender, coffer-access, or staff role because someone selected a name or accumulated messages.

Follow Discord’s permissions model. Place the bot above roles it must manage, and test the combined permissions of real member roles. Allowing two roles on a channel does not automatically require a member to hold both.

Build the Foundation With Start Your Server

Create or select the Discord server, connect it to YourBot, and open Start Your Server as the server owner. Check the building as indicator so the correct bot identity has the intended access.

A clan-branded bot name and avatar help members recognize official community messages. Keep that identity distinct from Jagex staff or an official game-support account.

Copy-ready OSRS clan prompt

Create a Discord server for Waystone, a 120-member Old School RuneScape
social and PvM clan. This is OSRS, not RuneScape 3.

We welcome returning players, regular accounts, Ironman players, and
members who play on desktop or mobile. Our activities include learner
raids, experienced raid groups, bossing, skilling, Sailing, clue discussions,
clan competitions, and optional PvP.

Separate Community Member, Recruit, Clan Member, Guide, Event Organizer,
Officer, and Moderator roles. Only interests and notification roles are
self-selectable. Verification must not grant clan membership, staff
permissions, or any financial/trading trust status.

Create a compact welcome area, clan information, an application/contact
panel, general chat, new-player help, guides, achievements, skilling and
clues, raid signups, LFG listings, a weekly plan, and game updates.
Keep officer discussions, application review, reports, and logs private.
Use a permanent clan lounge and one join-to-create party lobby.

Enable Welcome, Tickets, Sentinel, Group Finder, Beacon Events,
Join-to-Create Voice, Announcements, Social Feeds, Analytics, and Giveaways.
Prepare supported settings and channel destinations. Begin moderation
with reviewed log-only testing. Leave individual raid templates, forms,
announcement schedules, feeds, and prize details for manual review.

Include short instructions explaining game world, meeting point, account
restrictions, raid mode, and loot agreements. Never ask for Jagex login
credentials, authentication codes, account access, or an item deposit.

Preserve existing channels and roles. Do not delete or overwrite our live
setup without a separate review. Keep channel names clear and mobile-friendly.

A practical target layout

START HERE
  #welcome-and-rules
  #clan-information
  #choose-interests
  #apply-or-contact

COMMUNITY
  #general
  #new-player-help
  #guides-and-gear
  #achievements
  #skilling-and-clues

PLAY TOGETHER
  #weekly-plan
  #raid-signups
  #lfg-listings
  #activity-chat
  #clan-challenges
  Clan Lounge
  Create a Party Room

NEWS AND CELEBRATIONS
  #osrs-updates
  #streams-and-videos
  #community-giveaways

STAFF — RESTRICTED
  #officer-chat
  #application-review
  #ticket-logs
  #mod-log
  #feed-review
  #analytics-alerts

Treat this as a menu, not a minimum channel count. Use threads for individual guides and achievement discussions. Add restricted PvP coordination only when the clan genuinely needs it; an interest role alone should not expose private planning.

Review the actual changes

Inspect Channels, Roles, and Services, then use See it as for a newcomer, Community Member, Recruit, Clan Member, and Officer. Confirm that recruitment remains accessible without revealing its private review channel.

Review safety findings and the itemized build checklist. Keep deletions unchecked during the first pass, retain the pre-build snapshot, and read the completion report. The builder guide explains that undo restores structure, not deleted message history.

Enabling a service does not finish every workflow. In the inspected implementation, Announcements and Social Feeds can be enabled by the builder, but their schedules and subscriptions are created manually. Similarly, review individual forms, event definitions, and activity templates rather than assuming a general prompt completed them.

Finish the Setup Manually: All Ten Services

These sections also work for an established clan that skips the AI builder. Select the server, open Plugins, enable the relevant built-in service, and use its dedicated dashboard. Reuse suitable channels instead of creating duplicate destinations.

1. Welcome: help a newcomer reach their first activity

In Welcome → Settings, choose #welcome-and-rules as the welcome destination. Write a short greeting with three actions: read the rules, select interests, and open the clan application when ready.

Enable verification, choose the Verify Channel, and select Community Member as the Verified Role. Save the settings before using Post / Update message. Do not make Clan Member an automatic join or verification role.

Build role menus for activities and alerts. Keep “Ironman” separate from “Learner Raids”: one describes an account preference, while the other requests a notification. A member may want several interests without receiving every ping.

For newcomer support, use the existing Buddy System. Set Buddy Pool Role to a staff-approved Guide role and choose helpful starting channels. Keep direct messages optional and duplicate essential instructions in a visible channel; blocked DMs should not strand an applicant.

Ask members to provide a public RuneScape name only when needed for coordination. A Discord nickname is a convenience, not proof that the person controls that game account.

Test: A newcomer acknowledges the rules, gains ordinary access, selects a raid alert, and can contact staff. They cannot see application reviews or acquire Clan Member through a self-service menu.

2. Sentinel: protect the community without claiming to police the game

Open Sentinel and run its setup or manually choose the moderation log, staff roles, and required protection settings. Review a starter preset before enabling enforcement.

The inspected setup supports beginning with log-only rules. Use this period to check legitimate gear links, repeated recruitment questions, screenshots, and busy event chat. It should be a short preparation stage, not the permanent state of a publicly advertised server.

Create a clear community policy against credential requests, deceptive downloads, account services, real-world trading, and wagering. Jagex’s OSRS rules explicitly address these risks, including scamming and third-party software that automates gameplay.

Use appropriate link, spam, mention, and attachment controls. A text rule may flag a suspicious message; it cannot certify a download, establish a player’s identity, or prove that an in-game accusation is true. Keep public accusations out of general chat and direct reports to staff.

For a benign test, create a temporary rule matching a harmless test phrase, inspect the resulting log, and remove the test rule. Do not circulate a real phishing link to see what happens.

Test: Reviewed rules catch the test message without double-punishment from another bot. Officers know the manual Discord security actions to use during an incident.

3. Tickets: separate applications, questions, and incident reports

In Tickets, create a recruitment team and an intake form. Ask for the applicant’s public RuneScape name, account type, preferred play times, interests, and what they want from the clan. Let “not sure yet” be a valid activity answer.

Never request a login email, password, recovery information, authentication code, bank screenshot, or item deposit.

For a tidy application queue, use the panel editor’s Channel Mode → Form (review queue — no channel). Set Review Channel to #application-review, attach the intake form and staff team, and configure the acceptance/rejection message. An optional Role granted on Accept can give Recruit—not an unreviewed officer role.

An officer then handles the in-game invitation and confirms Clan Member separately. Jagex’s in-game application system does not become connected merely because the Discord application was accepted.

Create a second Private Channel panel for officer contact and sensitive reports. Collect relevant message links and a brief description, not an unrestricted dump of personal information. A disputed loot split belongs in a limited-access conversation with the agreed rules attached.

Review access to the dashboard, review channel, ticket channels, staff notes, and transcript destination. Publish realistic response expectations for volunteers. This is clan support, not Jagex account recovery or a promise to restore items.

Test: Submit one application and one private report. Confirm that an unrelated member sees neither, staff receive the correct routing, and acceptance grants only the intended Discord role.

4. Group Finder: create OSRS templates instead of inheriting MMO defaults

Open Group Finder and choose #lfg-listings, a staff log destination, and an optional activity-discussion area.

Create OSRS templates manually. The inspected automatic game-detection map does not contain an OSRS-specific starter. Do not publish inherited Tank, Healer, and DPS slots simply because they appeared in a generic setup.

A useful starting configuration is two active listings per person, two-hour default expiry, and a 60-second creation cooldown. These are clan recommendations to tune after use. Set experience labels such as Learning, Casual, Experienced, and Challenge.

Keep the initial board local. Local discovery is not a promise that every associated web surface is confidential; never put credentials, sensitive reports, or private PvP plans in a listing.

Build a small template library

These are sample recruiting sizes, not a table of game maximums. Check the actual activity’s requirements. An eight-person voice room, for example, does not make every boss an eight-player encounter.

For a teaching template, named slots such as Guide: 1 and Learner: 3 may be useful. For an experienced group, leave role slots empty unless a particular encounter assignment improves coordination. Avoid presenting guide status as an automatically validated qualification.

Write a listing members can act on

ToA learner group — proposed Raid Level 100

Four total places: one guide and three learners.
Meet at the Tombs of Amascut grouping area; host confirms the game world.
Allow around two hours for explanations and breaks.

Confirm the required quest unlock and discuss gear with the guide.
Read the listed invocations and agree the loot policy before starting.
Ironman and Group Ironman players: check your current account restrictions
and any in-game prestige or risk warnings before joining.

Voice listening is helpful; tell the host when you need text instructions.
No account access, downloads, item deposits, or paid entry required.

Jagex’s Tombs of Amascut guide establishes the Beneath Cursed Sands unlock, invocation-based difficulty, and the separate in-game grouping interface. The example Raid Level is a teaching choice, not YourBot checking anyone’s readiness.

The listing form’s Platform choices are broad: PC, Console, and Cross-play. For this clan, leave it unset and explain desktop/mobile participation in the description. Jagex’s OSRS Steam listing confirms PC/mobile compatibility; there is no need to divide the clan into incompatible platform teams.

Use Request joining when the leader should discuss readiness first. Require Listing Approval is different: it asks a manager to approve the listing itself. Neither setting approves the player inside the game.

Agree the loot rule before anyone starts

Publish whether the run uses an agreed split of eligible loot or a recipient-keeps-their-loot arrangement, often called FFA. Identify exceptions, how an Ironman participant is handled, and who answers questions before entry. Do not let “standard clan rules” stand in for an explanation a newcomer has never seen.

This is a record of the group’s agreement, not item custody or enforcement by YourBot. Never require an expensive loan, collateral transfer, or account access merely to establish trust.

Test: Create a listing, apply or join, leave, fill the remaining places, check the waitlist, and close it. Confirm whether the host occupies a place before teaching members how to count vacancies.

5. Beacon Events: schedule the session, not just the invitation

Use Beacon Events for a Saturday learner raid, a clan meeting, a quest-help evening, or a skilling-competition opening session.

Create an event and work through Event Info, Roles, Design, Actions, and Finish. For the example ToA session, choose a raid category, describe the teaching objective, and set Max Participants to four.

Under Signup Role Tree, start with Clear and add Guide:1 and Learner:3. Check the overall participant limit separately: changing role options does not necessarily change it. These are signup categories, not Discord permission roles.

The inspected Date & Time field uses the organizer’s browser-local time before conversion for Discord display. Verify the rendered timestamp rather than assuming it uses the timezone selected in another service.

In the description, state the world-confirmation process, duration, breaks, voice expectations, account restrictions, cancellation procedure, and loot agreement. Use reminders sparingly—for example, one the day before and another shortly before the meeting—and identify who handles standby players.

Keep the event’s voice option consistent with your permanent lounge or temporary-room plan. Do not also configure another service to create a second room for the same session.

Afterward, mark the event appropriately and publish a short recap. Signing up is not proof of attendance, a completed raid, or a particular drop.

Test: Fill the event, test the standby/waitlist behavior, inspect the timestamp from another timezone, and verify that a cancellation is visible to participants.

6. Join-to-Create Voice: support both raids and casual company

Keep Clan Lounge permanent. Configure Join-to-Create Voice with a separate Create a Party Room lobby and an appropriate destination category.

Use a readable name template such as 🎧 {display_name}. A default capacity of eight is a convenient community choice for this example, not a game rule. Leave automatic deletion on when the final participant leaves.

Review Creator is owner deliberately. Room-level moderation can help a host manage their party, but it should not become server-wide authority. Use category inheritance or the service’s role restrictions according to your membership policy.

The bot needs the relevant channel-management and member-movement access. Members need to see and connect to the lobby and the resulting room. Keep private officer or PvP planning outside a general-purpose public lobby.

Make voice optional for social skilling. For teaching, agree whether listening is sufficient and offer text accommodations where practical; mobile users should be able to explain their setup without being excluded automatically.

Test: Join the lobby, confirm the move, invite an allowed member, inspect room controls, and verify cleanup after everyone leaves.

7. Announcements: give members one dependable weekly plan

Create an Announcement for #weekly-plan. Set a descriptive internal label, write the member-facing message, select Weekly, choose the weekday and time, and enter an explicit IANA timezone such as Europe/London.

The internal label is for administrators; the message is what members receive. Review allowed mentions and keep mass pings disabled. Use opt-in role notifications only where they add value.

A useful weekly post contains the next learner session, the next social activity, the active competition link, and one reminder about where to request help. Link to the actual Beacon event or Group Finder instructions rather than maintaining a second competing signup list.

Give Announcements ownership of the weekly overview and Beacon ownership of event reminders. That prevents three different systems from telling members about the same raid.

Remember to update the recurring message when the plan changes. Recurrence repeats stored content; it does not independently discover your officers’ latest decisions.

Test: Preview a post in a staff channel, verify its next scheduled time, and check that a member without the alert role is not unnecessarily pinged.

8. Social Feeds: select Old School RuneScape explicitly

The inspected catalog does not include a dedicated OSRS tile. Use Social Feeds → Steam News and create a custom subscription with Steam App ID 1343370, matching the official Old School RuneScape store page—not the separate RuneScape title.

Set the display name to Old School RuneScape Updates and initially choose #feed-review as the destination. Leave the ping role blank until staff have reviewed the output.

The inspected Steam adapter requests publisher announcements rather than Steam’s third-party news aggregation. Its default polling interval is 900 seconds. That is scheduled checking, not a guarantee of immediate delivery or a complete mirror of every website update.

After testing, either route appropriate posts to #osrs-updates or keep staff review and manually publish the items the clan needs. Publisher feeds can still include promotions, surveys, and other announcements; “publisher source” does not mean “only gameplay patch notes.”

Use inclusion/exclusion keywords carefully. A substring filter cannot understand spoiler context or whether a change affects your event. Keep the official OSRS news archive linked as a direct reference, especially around maintenance and major updates.

Add selected creator channels separately to #streams-and-videos, with the creator’s permission where appropriate and no expectation that every upload deserves a clan-wide ping.

Test: Check the saved game ID, source, destination, interval, and observed post. Do not announce a working feed until it has actually delivered as intended.

9. Analytics: measure the community, not RuneScape progress

In Analytics, enable bot exclusion, choose a display timezone, and select a retention window appropriate to the clan’s needs. Exclude unnecessary staff, report, application, and automated-output channels from message metrics.

Review newly created private channels too; do not assume that excluding one existing ticket excludes every future ticket. Restrict dashboard access independently from Discord channel visibility.

After several ordinary weeks, compare unique participants, channel activity, newcomer return patterns, and voice use. A quiet guide channel may be doing its job perfectly. A player who prefers in-game clan chat should not be penalized because their Discord message count is low.

YourBot Analytics is not an OSRS experience or kill-count tracker. For Skill of the Week or Boss of the Week competitions, an optional specialist such as Wise Old Man tracks progress using periodic HiScores snapshots and supports group competitions.

Keep the measures separate: Discord participation for community operations; the selected game tracker for the competition metric. Record competition dates, eligible accounts, name-change handling, and baseline/update procedures. A snapshot-based gain is not evidence that somebody obtained a specific item.

Link competition results from Announcements. Do not automatically promote clan officers, award lending status, or infer raid skill from either message volume or raw XP.

Test: Confirm normal member activity appears, excluded messages do not, and the public leaderboard reveals only information the clan intended to share.

10. Giveaways: keep celebrations separate from loot and wagers

For this guide, choose a modest Discord-only cosmetic accolade with no administrative permissions. Create it through Giveaways with a title, destination, ending time, winner count, and a clear explanation of the reward.

Leave role and booster entry bonuses at zero for an equal-entry celebration. State eligibility and how the winner will receive the accolade; staff can fulfill it manually. Do not imply that drawing a winner automatically trades an OSRS item or grants an in-game reward.

Do not turn a clan celebration into paid random entry, GP wagering, item staking, or “deposit to verify” activity. Jagex’s rules prohibit games of chance involving the kinds of wagers described in its policy. Avoid tying community status to purchases or donations.

A rare raid drop follows the group’s previously agreed loot rules. A Skill of the Week result follows the competition rules. Neither should be settled by whichever giveaway settings happen to be enabled.

Test: Use a clearly marked practice draw with no prize value. Check entry, closure, winner visibility, and how staff document any permitted correction or reroll.

Add OSRS-Specific Depth With Gielinor’s Call

Before commissioning an entirely new OSRS bot, inspect Gielinor’s Call in the YourBot Marketplace.

Its current listing describes an OSRS noticeboard using Calls, member expressions of interest, hosting/participation Deeds, and a Chronicle, alongside /gielinor and /ge commands. It also describes a Grand Exchange watchlist and price lookups. Signing a Call expresses interest; it is not automatic enrollment in a game party.

Choose its role deliberately. Waystone could retain Group Finder for capacity-controlled pickup groups and use Gielinor’s Call for broader community invitations. Alternatively, test it as the primary noticeboard and retire overlapping group posts.

Before installation, review current pricing, capabilities, external domains, settings, and privacy choices. Test one Call from creation through closure and check one item lookup. Treat a guide price as information with a source and timestamp, not a guaranteed trade price or an instruction to invest.

These are listing-documented capabilities, not a claim that every integration was independently exercised. The useful question is whether the installed version improves the clan’s workflow without duplicating it.

Extend the Clan Workflow With a Bingo Evidence Board

Clan bingo is established community territory: Jagex’s 2025 Grid Master announcement credits it as an inspiration. That historical announcement is not an invitation to join an event that remains open today.

Use existing game or specialist tools when they fit. A custom YourBot plugin is useful when the clan needs its own Discord-centered evidence, privacy, approval, and appeal process—not because no other bingo tools exist.

The following is a proposed custom plugin, not an existing YourBot built-in. Start with a small, manually reviewed challenge and avoid entry fees, wagers, or any suggestion that screenshots are unquestionable proof.

Copy-ready Plugin Builder specification

Build an Old School RuneScape Clan Bingo Evidence Board for our Discord.
This is a community record system, not a RuneLite plugin or game bot.

Administrators configure an event title, UTC start/end times, a tile board,
team rosters, published scoring rules, an organizer role, a private review
channel, and a public progress channel. Freeze the rules and rosters when
an organizer starts the event; log any later authorized correction.

Members submit a tile, their team, the public RuneScape name involved,
an event-time claim, a short explanation, and optional evidence links.
Make the submission flow usable from mobile Discord. Do not require a
custom game client, game credentials, an item deposit, or account access.

Keep submissions Pending until an organizer approves or rejects them.
Check permissions in every handler, not only by hiding buttons. Members
cannot approve their own claims. Record the reviewer, decision, reason,
and timestamp. Permit an appeal without silently rewriting the history.

Prevent duplicate approval from awarding the same team/tile twice.
Separate public progress from private evidence and staff notes. Disable
unwanted mentions. Store state per Discord server and survive restarts.

Version one stores submitted links without fetching arbitrary websites.
It does not verify screenshot authenticity, read the game client, detect
loot, trade items, transfer GP, or grant rewards automatically. Include a
staff dashboard, clear errors, retention controls, and an export summary.

Review and test before launch

Use Plugin Builder to plan the workflow, inspect the generated files and requested capabilities, validate the draft, and create a development installation. Confirm the current usage estimate and test-install limits in the product.

Test an unauthorized approval, a repeated interaction, an out-of-window claim, a deleted destination, a denied capability, and a restart. Check that the public board never reproduces evidence or staff notes accidentally. Define how links that expire will be handled before making them essential evidence.

A developer can refine the same project through the YourBot Python SDK. In VS Code, open the complete project in a dedicated environment, install the documented SDK/dependencies, run its tests and yourbot validate, then upload the version through the Dev Portal for the applicable review and installation path.

A temporary development installation is not the final operational deployment. Launch only the version the clan tested, document who maintains it, and keep a manual fallback for event decisions. The publishing documentation explains version pinning and renewed consent when updates request additional capabilities or domains.

Run a First-Week Check Before Expanding

A successful server build is the beginning of operations, not the end. Use real member journeys to check the setup.

During the next month, remove unused channels, shorten confusing instructions, and add only the templates members actually request. Offer newcomer-friendly activities alongside advanced PvM so recruitment does not end at a wall of KC requirements.

For an existing clan, migrate one function at a time. Preserve useful event history and tracker links, test replacement panels privately, and give each automated action one active owner. Do not remove a specialist simply to reach an arbitrary one-bot target.

Frequently Asked Questions

Can YourBot create the in-game OSRS clan or synchronize its ranks?

This guide does not establish either capability. Start Your Server builds the Discord environment; YourBot services organize community workflows. Keep game invitations and rank decisions with authorized in-game officers unless a separately verified integration explicitly supports them.

Do members need RuneLite to use the Discord setup?

No. The YourBot services described here are Discord features. A RuneLite game-client plugin is a different kind of software. Any optional external tool should be evaluated separately, and the clan should retain an accessible path for mobile members.

Should Ironman players have a separate Discord?

Usually not for a social clan. Give them relevant discussion spaces and account-interest roles without excluding them from ordinary community activities. Organizers and participants must still check the particular activity’s current restrictions, loot eligibility, prestige, and death consequences.

Does YourBot track OSRS XP, boss kills, or drops automatically?

Not through the general Analytics service. Use a verified game-data tool for its documented metric, or deliberately build and review an integration. A submitted screenshot, event signup, or voice session is not automatically proof of game progress.

Can the clan organize a loot split through a listing?

A listing can record the agreement so participants understand it before the activity. It does not hold items, enforce a trade, guarantee a payout, or resolve an in-game dispute. Keep reports private and never describe a Discord badge as financial protection.

Should we enable every service on day one?

No. Start with onboarding, moderation, applications, group formation, and a small event schedule. Add feeds, analytics, optional celebrations, and custom workflows when someone owns their configuration and ongoing use.

Build a Clan People Can Actually Participate In

YourBot gives an OSRS clan one configurable Discord foundation without requiring every new idea to become another standalone bot. Start Your Server designs the structure. The built-in services connect recruitment, learning, events, voice, and administration. Gielinor’s Call offers an existing OSRS-specific option, while Plugin Builder and the SDK provide a route for a genuinely missing workflow.

Keep the important boundaries clear: community access is not account verification, a signup is not a game party, Discord activity is not XP, and a recorded agreement is not a guaranteed trade.

Start your server, test the first member journey, and grow the setup around how your clan actually plays.