How to Build and Run an ARC Raiders Discord Community With YourBot

Build an ARC Raiders Discord around the run people are agreeing to: the squad size, objective, map condition, equipment commitment, and plan for getting home. Use YourBot’s Start Your Server to prepare the channels, roles, permissions, and supported services, then configure the teammate listings, learning sessions, temporary voice rooms, support, and update feeds.

That approach solves a familiar problem: three people agree to play, but one wants quest progress, another wants difficult ARC encounters, and the third cannot afford the equipment the others expect. A useful community gets those expectations into the conversation before anybody deploys.

This guide follows Relay House, a fictional 240-member community, through a reviewed Start Your Server build and manual configuration of all ten YourBot services. Existing communities can keep their current channels and follow the service sections directly.

Start With the Right ARC Raiders Community Model

ARC Raiders is Embark Studios’ multiplayer extraction adventure, released on October 30, 2025. The game moves between dangerous surface excursions and preparation in Speranza. It supports solo play and parties of up to three people total. Embark’s official Steam description establishes that limit and the threat posed by both ARC machines and other Raiders.

Squad capacity is not community-event capacity

A duo listing finds one teammate. A trio listing fills three total places. A mentor joining two beginners occupies the third place; teaching does not create an extra slot.

Do not create mandatory Tank, Healer, and Damage slots. Ask what equipment and practical support each person plans to bring, then agree on responsibilities for that run.

Trials add scored weekly objectives and leaderboard progression. Embark’s Trials introduction explains that basic structure; use the current client for the active objectives and scoring requirements, not the old season’s dates or rewards. A Trials rank is not a YourBot-verified measure of PvP skill.

A PvE-focused run is not a PvE-only server

“Questing and avoiding fights” is a useful description of your squad’s intent. It is not a promise that other players cannot attack.

Embark continues adjusting its playstyle-based matchmaking, including how defensive encounters are considered. Its matchmaking update should not be interpreted as a guaranteed peaceful queue. Do not advertise a YourBot role that supposedly certifies friendly lobbies or disables PvP.

Relay House welcomes cautious scavengers and combat-focused players, but requires them to state their intentions. Changing from a teaching run to aggressive player hunting mid-session is something teammates should discuss—not a surprise imposed on a beginner.

Keep cross-platform squads together

The current ARC Raiders site lists PC through Steam and Epic Games Store, PlayStation 5, and Xbox Series X|S. Embark’s account guidance explains the Embark ID used for cross-platform friendship and progression.

Use region, language, availability, and run intent for ordinary LFG. Platform information remains useful for support and checking cross-play settings, but Relay House does not need three isolated communities for the same activity.

Discord verification is separate from Embark account identity. Do not ask somebody to prove ownership by sending a password, login code, or account token.

Keep current updates separate from future content

As of September 20, 2026, Frozen Trail is announced for October 8. Embark has previewed a new map, a high-level ARC Operation, Outposts, and progression changes. Those belong in a dated preparation thread, not instructions claiming the systems are already available. Use the official announcement and revise activity requirements after release.

Keep permanent spaces named #raid-planning, #quest-and-workshop-help, and #progression-discussion. The next update should require refreshed instructions, not a complete Discord rebuild.

The Community We Will Build

Relay House supports occasional duo partners, regular trios, beginner mentoring, quest and workshop preparation, ARC encounters, Trials discussion, and Expedition planning. Its members can participate without joining a permanent team.

The community has one structured recruitment destination, one coordination forum, and separate event signups. Sensitive support and optional story spoilers stay out of public discussion.

These are YourBot’s ten built-in services. Start with the workflows staff will operate; a giveaway does not need to delay working onboarding and teammate search.

1. Create the Foundation With Start Your Server

Sign in with the Discord account that owns the server, select it in YourBot, and open Start Your Server. The builder is owner-only. Check the building as indicator when using your community’s own bot identity.

Review channel access, channel-management permissions, and the bot’s position above the roles it must manage. The server-builder guide explains the prerequisites.

Copy-ready community brief

Create or reorganize an ARC Raiders Discord called Relay House for about
240 members. It supports cross-platform duo and trio play, beginner help,
quest and workshop preparation, ARC encounters, Trials discussion, and
Expedition preparation. Solo players are welcome socially.

Make the newcomer path simple: read the rules, verify, choose a region and
play interests, then find a compatible run or ask for help.

Use Learning, Quest Help, Workshop Goals, ARC Encounters, Trials,
Expedition Interest, and Solo Discussion as optional interests.
Separate LFG Alerts, Event Alerts, and Patch Notes notifications.

Keep Member, Mentor, Event Organizer, Resource Reviewer, and Moderator
access separate. Trusted roles must not be self-selectable.

Normal groups have two or three Raiders. A mentor counts toward the total.
Do not create Tank/Healer/Damage presets. A PvE-focused listing describes
intent; it does not guarantee a PvE-only match or prevent other players
from attacking.

Create one Group Finder listing channel, one coordination forum, event
signups, beginner help, a quest/workshop resource forum, progression
discussion, clips, official updates, and opt-in story spoilers.
Provide private support, mentor applications, and moderation logs.

Prepare Welcome, Sentinel, Tickets, Group Finder, Beacon Events,
Join-to-Create Voice, Announcements, Social Feeds, Analytics, and Giveaways.
Apply supported settings and identify the remaining manual setup.

Provide temporary Duo and Trio voice lobbies with appropriate room limits,
plus a larger social room. Keep private reports out of engagement features.

Do not create item-trading, account-sales, or paid progression channels.
Do not promise automatic game invitations, inventory tracking, live map
conditions, Expedition registration, or game-account verification.

Preserve existing channels, roles, and messages. Do not delete or rename
live channels in the first build. Stage additions for staff testing.

A compact channel plan

START HERE
  #welcome-and-rules
  #verify
  #choose-interests
  #contact-staff

RELAY HOUSE
  #announcements
  #arc-raiders-updates
  #general
  #clips-and-stories
  #story-spoilers           [Opt-in]

PREPARE AND PLAY
  #group-listings
  #group-coordination      [Forum]
  #event-signups
  #beginner-help
  #quest-and-workshop-help [Forum]
  #progression-discussion
  #solo-discussion

VOICE
  The Relay
  Create a Duo Room
  Create a Trio Room

STAFF
  #staff-chat
  #mentor-review
  #support-log
  #moderation-log

Use forum tags for maps, conditions, learning topics, and update versions. Avoid a permanent channel for every weapon, ARC enemy, blueprint, or player level.

Review before applying

Inspect Channels, Roles, and Services. Use See it as for a newcomer, Member, Mentor, and Moderator. Check that unverified members can reach help and that interest roles cannot reveal private records.

Review the itemized build operations with deletions disabled. Read the report and retain the snapshot afterward. Structural undo does not restore messages from deleted channels.

Announcements schedules and Social Feed subscriptions still require manual creation. An enabled service is not a completed calendar or news subscription. Finish the following steps before inviting the whole community into the new workflow.

2. Welcome: Match Interests Without Claiming Game Readiness

Open Welcome. Configure button verification in #verify to grant a limited Member role, then publish multi-select role menus in #choose-interests.

Offer Learning, Quest Help, Workshop Goals, ARC Encounters, Trials, Expedition Interest, and Solo Discussion. Keep notification choices separate so somebody can discuss Trials without receiving every LFG ping.

A player can select several interests. These do not prove their current inventory, unlocked content, skill, or willingness to risk an expensive kit tonight.

Welcome to Relay House.

Read the rules, verify, and choose your region and interests.
For teammates today, use #group-listings.
For a scheduled teaching run, use #event-signups.
For your first questions, start in #beginner-help.

Include your objective, intended squad size, communication preference,
and session length before the group heads Topside.

Keep Mentor, Organizer, and Moderator assignments staff-controlled. Welcome’s optional buddy system can use a reviewed Mentor pool for newcomers who want help. Pairing someone with a buddy does not reserve a game-party slot or promise immediate availability.

Test: a newcomer should verify, select multiple interests, find help, and still be unable to see applications or staff notes. Test with an ordinary account rather than an administrator.

3. Sentinel: Protect the Community Without Policing Every Lost Raid

Open Sentinel, choose the moderation log and authorized moderator roles, and review link, invite, mention, and spam rules. Trial new detection rules in dry-run while moderators inspect false positives.

Focus on phishing, impersonation, harassment, suspicious downloads, account sales, and exploit promotion. A frustrating extraction or ordinary PvP encounter is not automatically evidence of misconduct.

Embark’s enforcement policy also prohibits account boosting and exchanging in-game items for anything of value, not only cash. Relay House therefore does not offer blueprint sales, barter, or paid progression brokerage. Resource discussions help people understand the game; they are not a trading marketplace.

Use Sentinel’s report, case, and appeal workflows for Discord moderation. Avoid a public accusation board or a permanent “dangerous player” label based on unverified claims. Embark handles game-account enforcement and appeals.

Test: send harmless test messages, review the recorded reasons, check exemptions, and confirm that members cannot inspect private cases. Keep human moderation available while tuning automatic actions.

4. Tickets: Separate Beginner Help, Connection Problems, and Mentor Applications

Open Tickets and create distinct intake paths with appropriately limited staff access.

Beginner help should ask for the player’s goal, relevant map or quest, spoiler preference, availability, and whether they want written guidance or a teaching session. A screenshot may help, but a full inventory export is unnecessary.

Connection help should ask for the platform or storefront, the error shown, current cross-play settings, and whether a friend invitation was accepted. Never collect login credentials. Account-linking problems should point to Embark’s own account-management guidance, not an improvised unlink-and-relink procedure: progress does not transfer simply because someone connects a platform to another Embark ID.

Mentor applications can use Form (review queue — no channel). Ask what the applicant can teach, their availability, and how they handle a beginner losing equipment. Route submissions to #mentor-review; acceptance should not automatically grant broad moderation powers.

Keep formal moderation appeals in the designated Sentinel workflow rather than operating two competing case systems. Tickets remains the place for help and private contact that needs a conversation.

Test: submit all three request types. Confirm that a Mentor cannot read unrelated account-help requests or applications merely because they handle beginner support. Check transcript and log destinations as well as the live conversation.

5. Group Finder: Build Duo and Trio Templates Manually

Open Group Finder, connect #group-listings and the coordination forum, and review the settings. ARC Raiders is not in the inspected automatic game-detection keyword table. Create explicit templates rather than assuming the wizard supplies the right squad size.

Start with Local visibility, a two-hour default expiry, one active listing per member, and a modest posting cooldown. These are Relay House recommendations, not game rules. Use descriptions for ARC-specific requirements rather than assuming the dashboard has dedicated inventory or quest fields.

Create the first template

In the template editor’s Basic tab, enter:

Template Name: ARC Raiders — Duo
Game: ARC Raiders
Default Party Size: 2
Default Expiry (hours): 2
Description: Find one teammate. Include region, map and condition,
objective, experience, communication, session length, and equipment
expectations. A cautious run is not a guaranteed peaceful match.

Leave Slots empty for ordinary raids. The editor also offers Branding and Display controls; clarity matters more than decorative role labels.

Choose a size for each saved template rather than entering “2 or 3” as a numeric value. A two-person coaching template is also useful when a beginner prefers individual attention.

Publish what people are agreeing to

Activity: Quest progress and workshop materials
Target group: 3 total; currently 2, looking for 1
Region and language: Europe, English
Map: Dam Battlegrounds, subject to current availability and conditions
Approach: Avoid unnecessary player fights; defend or disengage as needed
Experience: Beginner welcome
Equipment: Modest replacement budget; agree before departure
Communication: Game voice and pings, or Discord by agreement
Session: About one hour, with a check-in before another run
Finishing plan: Regroup and extract when the agreed objective is complete

The target size includes the leader and existing teammates. Reconcile the actual participant display with the description; do not advertise “2/3” while the listing represents only one person.

Joining a YourBot listing does not send an ARC Raiders party invitation. In the game, use Social → Friends → Add Friend, enter the teammate’s Embark ID, and invite them after acceptance. Embark’s Friends & Parties guide explains the game-side flow.

For mentor-led groups, distinguish an organizer approving somebody’s join request from a moderator approving the listing itself. Neither process verifies game progression.

Test: fill a trio, check full-group behavior, remove a member, and let a separate listing expire. Confirm the coordination thread and alert settings. Then have the accepted players complete the game’s invitation process themselves.

6. Beacon Events: Schedule a Teaching Run or Several Separate Groups

Use Beacon Events for planned learning sessions, community evenings, and preparation briefings. Group Finder supports scheduling too; Relay House deliberately uses it for squad recruitment while Beacon owns community-event attendance.

Example: one teaching trio

Title: First Topside Run — Guided Trio
Category: Other
Date & Time: The organizer's chosen local date and time
Max Participants: 3
Signup Options: Mentor — 1; Learner — 2
Destination: #event-signups

Choose Clear in the signup role tree before adding these options. Set Max Participants separately. A mentor is one of the three Raiders, not an additional observer in the game.

Describe the learning goal, equipment expectations, approximate duration, and a fallback when the selected condition is unavailable. The session might cover navigation, selecting useful resources, communicating threats, and recognizing when to leave—not promise a valuable blueprint or a flawless extraction.

The editor uses the organizer’s local timezone and converts the time for Discord display. Verify it with another member before publishing. Use the waitlist for reserves rather than silently adding a fourth Raider.

Example: a nine-person learning evening

Relay House can organize three mentors and six learners, then assign three independent trios. The event capacity is nine people; each game party remains separate.

Do not describe this as a nine-player raid, a private server, or guaranteed shared matchmaking. Do not coordinate queue manipulation to place the trios against other players together. A shared briefing followed by separate sessions provides the community benefit without making those promises.

Test: fill the teaching event, check a reserve’s waitlist position, confirm reminders, and verify the three-person assignment. For a larger evening, rehearse the group split before launch.

7. Join-to-Create Voice: Give Duos and Trios Their Own Rooms

Join-to-Create Voice supports multiple lobbies with separate defaults. Configure a Duo lobby capped at two and a Trio lobby capped at three, plus the larger permanent The Relay for social discussion.

Review the temporary-room category, creator ownership, owner panel, ownership transfer, and delete-when-empty behavior. Use a simple name such as 🎧 {display_name}. Check category inheritance or allowed roles: a temporary room is not automatically private.

These are Discord limits, not game-party reservations. Members can instead use ARC Raiders’ native pings and voice. Embark’s communication guide distinguishes party communication from proximity chat, which can reach Raiders outside the squad.

A private Discord room does not stop an open game microphone from broadcasting. Ask members to check their audio settings before discussing sensitive route or inventory details. Agree on recording or streaming before a session, especially during mentoring.

Test: create a room, admit a teammate, transfer ownership, and confirm cleanup only after it empties. Test the actual console workflow and game audio alongside Discord; do not assume every microphone behaves identically.

8. Announcements: Publish a Weekly Plan and Expire Dated Notices

Open Announcements, choose the destination and timezone, and create the schedule manually. Mention an opt-in Events role rather than everyone.

Relay House this week

Tuesday: Beginner preparation and teaching runs
Thursday: Quest and workshop goals
Friday: Duo and trio community night
Weekend: Trials discussion or an available ARC encounter

Find dated sessions in #event-signups.
Find teammates for today in #group-listings.
Check the current game map screen before committing to a special condition.

Let Beacon own event-specific reminders and Announcements own the weekly overview. Do not send duplicate last-minute pings from both services.

For special conditions, use the in-game selection screen and Embark’s Map Conditions page. A weekly post can link to the planner; it does not make YourBot a live condition monitor or guarantee a particular encounter will be active.

Give every time-sensitive notice an owner and a review date. Expedition registration, Trials availability, and an upcoming update should not remain pinned as though their deadlines never pass.

Test: send a staff preview and check timezone, formatting, destination, and mentions. Review dated notices after their deadline instead of leaving an expired invitation in the newcomer path.

9. Social Feeds: Add ARC Raiders Through Steam News

ARC Raiders is not a dedicated tile in the inspected YourBot game catalog. The generic Social Feeds Steam source supports it through Steam App ID 1808500.

Create the subscription manually:

Source: Steam
Steam App ID: 1808500
Destination: #arc-raiders-updates
Optional mention: Patch Notes

The inspected adapter checks publisher Steam Community announcements on a 900-second default polling interval. That is periodic checking, not guaranteed delivery within fifteen minutes, a server-health monitor, or a live event timer.

Embark’s Steam announcement feed can inform members on other storefronts and consoles too. They do not need a Steam copy to read the Discord post.

Keep the channel read-only for ordinary members and move reactions into a discussion thread. Check Embark’s news and support pages directly when an account notice or important gameplay clarification is not represented in the feed.

Test: verify the app, destination, and mention settings, then observe a new announcement. Enabling Social Feeds without creating this subscription is not a completed setup.

10. Analytics: Measure the Community, Not Extraction Performance

Configure Analytics with the community timezone, bots excluded, deliberate retention, and exclusions for private support, moderation, spoiler-sensitive spaces, and automated feeds.

Review whether newcomers return, whether teaching events lead to ordinary participation, and which discussion areas people use. Compare those observations with actual signups and help requests rather than treating every voice minute as a completed raid.

YourBot’s built-in Discord analytics does not establish extraction rate, stash value, quest progress, blueprint ownership, Trials results, Expedition readiness, or hidden matchmaking characteristics. It should not become a player-skill ranking by another name.

Keep trust separate from engagement. A prolific chatter does not automatically qualify as a Mentor, and a quiet solo player may still be a valuable community member.

Test: check a normal public interaction and an excluded channel. Review any public cards separately and confirm that private activity is not exposed through a leaderboard or celebratory post.

11. Giveaways: Use Prizes You Can Actually Deliver

Open Giveaways, restrict hosting to approved organizers, and choose a public destination. State eligibility, the real prize, the closing time, and the claim process.

For Relay House, straightforward prizes are community merchandise, a legitimately purchased store gift card with clear regional restrictions, or a sponsor-provided peripheral. Keep them independent of game progression and equipment transactions.

Do not promise Raider Tokens, blueprints, restored gear, or Expedition rewards from the bot. YourBot runs the Discord drawing; it does not grant ARC Raiders account entitlements.

Never ask a winner for an Embark or platform password. Publish the official contact method so an impersonator cannot turn a celebration into an account-recovery scam.

Test: run an explicitly labeled staff-only drawing with no real prize. Verify entry, closing, winner messages, and who can reroll before running a public event.

Agree on Equipment, Risk, and the End of the Run

A useful listing explains the cost of participating, not only the destination. Embark’s first-raid guide explains that a failed raid can cost carried equipment and collected loot, with Safe Pocket protection subject to the loadout.

Before departure, Relay House asks three questions: what are we trying to finish, what are we comfortable losing, and when do we stop?

For a beginner session, agree on a modest kit and a clear learning goal. Check ammunition, healing, repair needs, and any condition-specific entry requirements in the current client. A basic-loadout option should not be advertised as valid for every special condition without checking it.

For an ARC encounter, discuss the intended approach and the supplies people will bring. Do not require expensive equipment merely to make a Discord listing look serious. A leader who wants a specific setup should explain it before teammates commit.

Agree on who calls the retreat, when to regroup, and what happens after a failed extraction. Someone losing their last comfortable kit should be able to leave without being shamed into another attempt.

Keep detailed inventories and personal progression notes optional. A public recruitment post needs compatible expectations, not an account audit.

Keep Expeditions Separate From Ordinary Raids

An Expedition is a personal progression system, not another name for tonight’s trip Topside. Community reminders should make that distinction explicit.

Embark’s fifth-Expedition notice gives a September 8–29, 2026 registration window, closing at 08:00 UTC on September 29. Completing the Caravan does not register a departure; players must sign up in-game. The notice also announces a pause after this Expedition until early 2027.

The September 8 update adds another important correction to older guides: quest progress is no longer reset by default on departure. That does not mean departure preserves every other part of a character. Ask each player to review the current in-game confirmation for the full consequences.

Relay House can host a preparation discussion and help people understand their options. Staff should not pressure the entire community to depart together or present a Discord RSVP as registration.

Trials have a separate timetable. The same Expedition announcement says the current Trials season ends September 22 and pauses until October 8. A recurring Trials event needs a fallback discussion or another activity during that gap—not a promise that scoring remains available.

Use dated source links for these notices. Do not build a permanent countdown from an older fixed-cycle description.

Give Solo Players and Returning Raiders a Place

Not everyone who joins wants a regular trio. Keep solo discussion, clips, map questions, and preparation help available without a party requirement.

A solo player may want help understanding an objective while still choosing to deploy alone. That is different from putting several people in voice and promising they can coordinate within the same solo match.

Returning players need a short route back into the game: a current official update, the community’s revised requirements, and somebody who can explain unfamiliar systems. Tag older guides with their last-tested version rather than deleting the entire resource forum whenever equipment or progression changes.

For a new map or story update, keep discovery optional. A mentor should ask whether someone wants hints, a direct answer, or a spoiler-free first attempt. Do not reveal late quest steps through a public signup title or notification preview.

Add a Raider Goals & Expedition Journal Only When You Need It

Relay House can launch with the built-in services. A custom plugin becomes useful when people’s longer-term goals disappear between short-lived group listings: which workshop task they were preparing for, what they wanted to learn, or which Expedition questions they planned to review with a mentor.

A Raider Goals & Expedition Journal would retain that context without replacing the game’s quest log. It would also avoid creating another RSVP system: Group Finder recruits teammates, Beacon schedules sessions, and Tickets handles private help.

Check the marketplace for a maintained solution first. Evaluate the actual listing, permissions, support, and data handling rather than assuming an ARC Raiders integration already exists.

The project below is a proposed Discord workflow, not an implemented feature or live game-data integration.

Copy-ready Plugin Builder specification

Build a YourBot SDK plugin called Relay House Raider Journal.
This is a member-maintained goals journal with optional mentor sharing.
It must not read or control ARC Raiders.

Administrators configure Mentor and Resource Reviewer roles, an approved
public resource channel, and private review access. Use a dashboard and
supported slash-command interactions, not passive scanning of chat.

A member can create a private goal with:
- title
- category: Quest, Workshop, Map Learning, ARC Preparation, Trials,
  Expedition Preparation, or Custom
- description entered by the member
- relevant map and condition as optional text
- game version or update reference
- last-confirmed date
- optional source URL stored as text
- optional review-by date
- status: Planning, Ready to Discuss, Working On It, Completed,
  Needs Review, Archived
- optional private note

Treat all completion and readiness information as member-reported.
Never infer inventory, quest completion, blueprint ownership, account
level, or ability from a Discord role or a journal entry.

By default, only the member can view their journal through the application.
A member can share a specific record with a selected current Mentor.
Sharing requires explicit consent and can be revoked at any time.
Do not grant every Mentor access to every journal.

Check authorization server-side for commands, dashboard views, direct
record requests, exports, and edits. Removing a Mentor role must remove
that person's mentor-based access. Document any administrator support
access separately; do not claim encryption or privacy from the hosting
operator that has not actually been implemented.

Let members publish a separate, minimal help request containing only
fields they intentionally choose. Publishing a request must not expose
the full journal, private note, or unrelated goals.

Allow optional links to an existing Group Finder listing, Beacon event,
or support conversation. Do not create another signup, ticket, or reward
system. Do not reserve game-party positions.

Resource Reviewers can maintain approved preparation checklists with a
source, revision, last-reviewed date, and status. Public resources must
remain separate from personal progress. Never invent working item codes,
guaranteed loot locations, or completion requirements.

Show stale or expired guidance when records are viewed or edited.
Keep version 1 event-driven; do not depend on cron, background polling,
or scheduled hooks. Use the existing Announcements service for timed
community reminders.

If a member reports a new progression cycle or an Expedition departure,
offer to archive selected goals and start a new journal section.
Require confirmation. This affects Discord records only, never the game.
Do not automatically erase journals on a presumed wipe date.

No trading board, paid carries, barter matching, escrow, or progression
reward promises. Never request Embark, Steam, Epic, PSN, or Xbox passwords,
2FA codes, session tokens, or game-control credentials.

Keep external network access disabled in version 1. Do not fetch submitted
URLs, run downloads, read the game client, query inventory, track live map
conditions, verify Trials scores, or register Expedition departures.

Isolate every Discord server's records. Provide member deletion/export
and administrator retention controls. Audit changes without permanently
copying deleted private notes into the audit log. Escape user-provided
mentions and keep spoiler-marked text out of public previews.

Suggest /raider-goals actions for create, view, update, share, revoke,
archive, export, and delete using the SDK's supported command format.

Include tests for unrelated-member access, unrelated-Mentor access,
revoked sharing, removed roles, cross-server record access, exports,
expired guidance, mention abuse, duplicate submissions, deletion, and
public-preview leakage.

Review, test, and continue through the SDK

Use Plugin Builder to review the plan, generated source, manifest, commands, and requested capabilities. Resolve validation findings before a development install. The documented development installations expire after 24 hours; they are a testing stage, not permanent deployment.

Test with synthetic goals as a member, unrelated member, invited Mentor, unrelated Mentor, and administrator. Remove the Mentor role and revoke sharing separately. Repeat the checks through direct record requests and exports, not only visible dashboard buttons.

A developer can continue the generated folder in Visual Studio Code with a project Python environment and yourbot-sdk. Run yourbot validate and yourbot dev as described in the SDK quick start. The local runner is simulated; it does not replace a real Discord development-install test.

The SDK documentation also says marketplace-plugin schedules do not run. Keep this journal on-demand and let Announcements own timed notices. For release, upload the tested ZIP with manifest.json and __main__.py at its root, or use the supported GitHub workflow. Follow the Dev Portal’s review and installation process; public marketplace distribution is a separate decision.

A successful validator result does not prove correct privacy or accurate game advice. Test the actual version intended for use and recheck guidance after relevant game changes.

Run a Complete First-Week Member Journey

Before announcing Relay House’s new setup, rehearse the experience with ordinary accounts. These are acceptance tests to perform, not assumptions about how an administrator’s screen looks.

When introducing the optional journal, add a revoked-sharing test before real private notes are entered. Preserve a simple help path for people who would rather ask a question than maintain another record.

Frequently Asked Questions

How many people should an ARC Raiders listing allow?

Use two for a duo or three for a trio, including the leader and any mentor. A larger Discord event must divide into separate parties; attendance does not create extra game slots.

Can a “PvE-focused” role guarantee a peaceful match?

No. It describes the player’s intention. Do not use it to promise protection from other Raiders or access to a special non-PvP queue.

Can PC, PlayStation, and Xbox members share this Discord?

Yes. Use the supported cross-play and Embark friend system, with platform information available for troubleshooting. Check incompatible settings in the game rather than assuming Discord membership resolves them.

Does joining an Expedition event register a departure?

No. A Discord event is a preparation session. The player must review and complete the game’s current registration process themselves.

Can YourBot verify inventory, quests, Trials scores, or extraction results?

Not through the built-in workflows described here. The proposed journal stores voluntary member updates. A future integration would require a separately verified interface, permissions, and data-handling design.

Is the custom journal required to launch?

No. Begin with useful onboarding, compatible squad listings, support, events, and voice. Add a journal only when persistent goals and selective mentor sharing solve a real problem.

Build Around Compatible Raiders and Clear Expectations

A useful ARC Raiders Discord gets a solo newcomer one compatible partner, helps a trio agree on a run before risking equipment, and gives returning players a clear path back into current content.

Start Your Server prepares the foundation. YourBot’s built-in services manage the Discord workflows around it. The game remains responsible for parties, matchmaking, inventory, progression, and departure decisions.

Start your community setup, test the first complete member journey, and extend the same bot with a focused Plugin Builder project when the community needs more.