A Fallout 76 Discord should be organized around platform pool, four-player teams, world type, activity goal, build/readiness context, and the difference between a team and the larger Appalachia world around it. Fallout 76 is not a guild MMO with one persistent raid roster. Public Teams hold four players. Daily Ops and Expeditions are built around teams of up to four. The Gleaming Depths raid is designed for a coordinated party of four. Private Adventure and Custom Worlds can hold eight total players. Public Events and other Activities can involve many people in the same world without turning them into one eight- or twenty-player team.
The most common community mistake is to collapse all of that into one #lfg channel and one generic party size. A PC player cannot simply join an Xbox or PlayStation team. A Steam PC player can play with a Microsoft Store/Xbox App PC player, because both are in the PC environment. A raid team has four real seats. An eight-person Private Adventure night is a world/session event that may contain two four-player teams. A public-event meetup may involve even more community members sharing a world without one giant in-game party.
This guide builds a fictional 248-member community called Appalachian Relay. It supports PC, Xbox, and PlayStation communities inside one Discord while keeping operational matchmaking separate. Its members run Daily Ops, Expeditions, Gleaming Depths, Public Events/Activities, seasonal content, C.A.M.P. tours, trading/vendor nights, roleplay, Private Adventure sessions, and new-player teaching. YourBot handles the Discord-side structure and workflows. Fallout 76 remains authoritative for characters, teams, Worlds, C.A.M.P.s, inventories, vendors, Fallout 1st access, Atoms, Season Tickets, raids, rewards, account state, PvP, and enforcement.
Start With the Right Fallout 76 Community Model
Platform pool comes before build
Fallout 76 currently supports:
- PC
- Xbox One / Xbox Series X|S
- PlayStation 4 / PlayStation 5
Bethesda explicitly confirms that Steam and Microsoft Store/Xbox App players on PC can play together.
Bethesda also confirms that character progress cannot be transferred between different platform families, and that PC characters/progress are not shared with Xbox Console.
For practical Discord operations, treat these as separate pools:
PCXboxPlayStation
Do not put a PC player into an Xbox or PlayStation LFG merely because everyone uses a Bethesda.net account.
Within PC, Steam versus Microsoft Store/Xbox App is generally support context, not an LFG compatibility split.
Native Xbox Series and PlayStation 5 versions are live now
The September 15, 2026 Slasher update shipped native Xbox Series X|S and PlayStation 5 versions.
Bethesda's current release notes describe:
- targeted 60 FPS on Xbox Series X|S, PS5, and PS5 Pro
- current-generation performance/stability improvements
- native downloads through the respective platform stores
That is a platform-support change, not a new matchmaking pool. A PS5 player remains in the PlayStation environment; an Xbox Series player remains in the Xbox environment.
Normal/Public Teams are four players
Bethesda's current support documentation states that Public Teams can have up to four members.
That makes four the most important standard team size for Discord LFG.
Use four for:
- general exploration/farming teams
- Daily Ops
- Expeditions
- Gleaming Depths raid
- event-running teams
- roleplay/exploration teams where the in-game team matters
An organizer can still run with fewer players. Four is the ceiling, not a requirement to fill every listing.
Daily Ops and Expeditions are four-player workflows
Daily Ops are repeatable instanced activities that can be completed solo or by a team, with official Bethesda material describing teams up to four.
Expeditions similarly take the team leader plus up to three teammates outside Appalachia. Only the team leader can start an Expedition.
Discord should therefore include:
- team leader
- target activity
- build/role context
- whether this is speed/reward-focused or learner-friendly
- voice preference
- current team size
Joining the Discord listing does not start the Expedition.
Gleaming Depths is a true four-player raid
The Gleaming Depths is explicitly designed for four highly leveled/geared Vault Dwellers.
Bethesda differentiates it from Daily Ops and Expeditions because it expects:
- coordinated teamwork
- encounter-specific responsibilities
- strong builds
- communication
- multiple boss encounters
This is where a persistent readiness profile can be useful later, but the actual raid listing still has four human seats.
Do not create an eight-player Gleaming Depths event roster unless the event explicitly means two independent raid teams.
World capacity is not team capacity
Fallout 76 has several world modes.
Adventure
- standard live experience
Private Adventure
- Fallout 1st owner can host
- eight total players in the world
Public Worlds
- rotating modified Worlds
- Bethesda support states 24 total players
Custom Worlds
- Fallout 1st custom world
- eight total players
That means:
Private Adventure Night — 8 attendees
can be correct while:
Raid team — 8 players
is wrong.
A Private Adventure with eight community members may contain:
- two four-player teams,
- smaller teams,
- or players doing different things inside the same world.
Fallout 76 has no in-game guild system to mirror
Appalachian Relay is a Discord community, not a game guild.
Fallout 76 has:
- friends
- teams
- Worlds
- C.A.M.P.s
- player vendors
- factions in the game world/lore
- events/Activities
- social roleplay communities
But a Discord role such as Raid Lead, Vendor, Builder, or Responder RP does not correspond to a game-side guild membership system.
That makes the Discord more flexible—but it also means YourBot should never claim to synchronize an in-game clan/Guild that does not exist.
Current live state: The Slasher and Season 26
As of September 25, 2026, the live major update is The Slasher, released September 15.
Current highlights include:
- multi-week Slasher storyline/broadcasts
- new Infestation-related Slasher activity
- native Xbox Series / PS5 versions
- Unique Item Crafting changes
- Legacy Seasons
- Season 26: Beware the Blood Moon
- fall Seasonal Fish added September 22
The Slasher content unfolds over multiple weeks. That means the Discord should use dated update posts rather than pretending every stage is already unlocked.
Season 26 is live now, and Legacy Seasons now run alongside the current season using the same ticket pool.
The Community We Will Build
Appalachian Relay is a 248-member Fallout 76 Discord.
- Platform communities:
- PC
- Xbox
- PlayStation
- Main activities:
- Daily Ops
- Expeditions
- Gleaming Depths
- Activities / Public Events
- Infestations / current Slasher content
- Private Adventure nights
- C.A.M.P. tours/building
- vendor/trading meetups
- fishing/seasonal activities
- roleplay/social exploration
- new-player help
- Community does not claim an in-game Guild/clan.
- Trading/vendor discussion is community coordination only.
- Platform pool is mandatory for operational LFG.
YourBot's role in the community
| Service | Community use |
|---|---|
| Welcome | Verify newcomers and collect PC/Xbox/PlayStation, activity, build, C.A.M.P., trade, and new-player interests. |
| Sentinel | Reduce phishing, RMT/account-sale spam, malicious tools, impersonation, scam links, harassment, and raids. |
| Tickets | Route member reports, teaching requests, trade disputes, event proposals, and Discord access/support privately. |
| Group Finder | Match four-player teams for Daily Ops, Expeditions, Gleaming Depths, and general Appalachia sessions. |
| Beacon Events | Schedule eight-player Private Adventure nights, multi-team raid nights, seasonal/community events, and C.A.M.P. tours. |
| Join-to-Create Voice | Create temporary four-player activity rooms plus larger event/social rooms. |
| Announcements | Publish weekly event plans, Slasher stages, season notices, maintenance, platform changes, and community schedules. |
| Social Feeds | Follow official Fallout 76 Steam publisher announcements through App ID 1151340. |
| Analytics | Measure Discord onboarding, LFG use, event attendance, voice use, support load, and channel health. |
| Giveaways | Run Discord-side drawings without implying YourBot grants Atoms, Fallout 1st, gear, caps, plans, SCORE, or Season rewards. |
1. Create the Foundation With Start Your Server
Build around workflows instead of every current Activity, Public Event, Expedition, weapon, C.A.M.P. theme, or Season.
Copy-ready community brief
Design a Fallout 76 Discord called Appalachian Relay.
Community:
- About 250 Discord members.
- Supports PC, Xbox, and PlayStation communities in one Discord.
- Operational LFG must separate PC, Xbox, and PlayStation.
- Steam and Microsoft Store/Xbox App players on PC can play together.
- Do not claim characters/progress transfer across platform families.
Core team rules:
- Normal/Public Team maximum = 4.
- Daily Ops = up to 4.
- Expeditions = leader + up to 3 teammates.
- Gleaming Depths raid = 4.
- Private Adventure / Custom World = 8 total players in the world.
- Public World = 24 total players.
- World capacity is not team capacity.
Roles:
Owner
Administrator
Moderator
Event Host
Raid Lead
Mentor
Member
New Vault Dweller
Self-select:
PC
Xbox
PlayStation
Daily Ops
Expeditions
Gleaming Depths
Public Events / Activities
C.A.M.P. Building
Trading / Vendors
Roleplay
Fishing
Private Worlds
New / Returning
Season / Slasher Updates
Optional build interests:
Heavy Weapons
Commando
Rifleman
Melee
Shotgun
Pistol
Support/Medic
Power Armor
Stealth
Other
Do not self-select:
staff roles
Raid Lead
Mentor
trusted moderation roles
Channels:
START HERE: welcome, rules, choose-roles, announcements
FOUNDATION: general, questions, screenshots, builds-and-loadouts
TEAM UP: lfg-listings, lfg-forum, events
ENDGAME: raid-learning, daily-ops-and-expeditions
CAMP & TRADE: camp-showcase, vendor-and-trading
SEASONAL: season-and-slasher
UPDATES: fallout-76-updates
HELP: open-a-ticket
VOICE: join-team, join-raid, social-event
STAFF: staff-chat, sentinel-logs, ticket-log
Safety:
- Never request Bethesda/Steam/Xbox/PlayStation passwords.
- Never request Steam Guard, 2FA/recovery codes, session tokens, payment information, or remote-control access.
- Treat phishing, account sales, RMT, scam trade links, malicious executables, and impersonation as risks.
- Discord moderation is not Bethesda enforcement.
- Discord roles do not change team status, Private World access, C.A.M.P., inventory, Fallout 1st, Season progress, or game account.
- YourBot does not verify builds, raid clears, inventory, caps, plans, vendor stock, or character level.
Configure all ten built-in services:
Welcome
Sentinel
Tickets
Group Finder
Beacon Events
Join-to-Create Voice
Announcements
Social Feeds
Analytics
Giveaways
YourBot specifics:
- Fallout 76 is not in the currently inspected Group Finder automatic detection list.
- Create explicit 4-player Fallout 76 templates manually.
- Do not use the generic 5-player Quick Group.
- Fallout 76 is not in the inspected curated Social Feeds catalog.
- Add generic Steam source App ID 1151340.
- Announcements schedules and Social Feed subscriptions require manual finishing.
- Preserve existing structure on first build.
- Keep deletions off.
- Preview New Vault Dweller, Member, Raid Lead, Mentor, and Moderator.
A compact channel plan
APPALACHIAN RELAY
├─ START HERE
│ ├─ #welcome
│ ├─ #rules
│ ├─ #choose-roles
│ └─ #announcements
├─ FOUNDATION
│ ├─ #general
│ ├─ #questions
│ ├─ #screenshots
│ └─ #builds-and-loadouts
├─ TEAM UP
│ ├─ #lfg-listings
│ ├─ #lfg-forum
│ └─ #events
├─ ENDGAME
│ ├─ #raid-learning
│ └─ #daily-ops-and-expeditions
├─ CAMP & TRADE
│ ├─ #camp-showcase
│ └─ #vendor-and-trading
├─ SEASONAL
│ └─ #season-and-slasher
├─ UPDATES
│ └─ #fallout-76-updates
├─ HELP
│ └─ #open-a-ticket
├─ VOICE
│ ├─ 🔊 Join Team
│ ├─ 🔊 Join Raid
│ └─ 🔊 Social Event
└─ STAFF
├─ #staff-chat
├─ #sentinel-logs
└─ #ticket-log
Review before applying
Preview:
- New Vault Dweller
- Member
- Raid Lead
- Mentor
- Moderator
Confirm platform roles do not grant staff permissions.
Keep deletion off on the first build.
Announcements schedules and Social Feed subscriptions require manual finishing steps.
2. Welcome: Platform Before Build
The onboarding order should be:
- rules
- platform pool
- activity interests
- optional build interests
Useful roles:
- PC
- Xbox
- PlayStation
- Daily Ops
- Expeditions
- Gleaming Depths
- Public Events / Activities
- C.A.M.P. Builder
- Vendor / Trader
- Roleplay
- Private Worlds
- New / Returning
- Season Updates
Do not make Fallout 1st a trusted Discord role unless the community has a real notification/use case. Membership status can change and YourBot does not verify it.
A concise greeting:
Welcome to Appalachian Relay. Choose PC, Xbox, or PlayStation before using LFG. PC Steam and Microsoft Store players can play together; console/platform progress is separate. Most team content uses up to four players. Private Adventure can host eight people, but that does not create an eight-player raid team. Never share account credentials or recovery codes here.
Test: Join with a test account, select PC, Gleaming Depths, and C.A.M.P. Builder, then verify only intended roles appear.
3. Sentinel: Protect Trade and Community Spaces Without Policing Appalachia
Fallout 76 communities share:
- build links
- screenshots
- vendor listings
- trade offers
- C.A.M.P. resources
- official Bethesda links
- community guides
Sentinel should focus on:
- phishing
- fake Bethesda/Steam/Xbox/PlayStation logins
- RMT/account-sale spam
- malicious executables
- scam vendor/trade links
- impersonation
- harassment
- Discord raids
- suspicious URL shorteners
- doxxing
Do not claim Sentinel can detect duped items, hacked weapons, cheating, or Terms-of-Service violations inside the live game.
Bethesda's rules are the game authority. The Discord can set stricter trading/community rules for its own members.
Use dry-run/logging for aggressive link rules.
Test: Post a dummy fake-login domain in a staff-only channel and confirm Sentinel handles it without blocking legitimate Bethesda/Steam links.
4. Tickets: Teaching, Reports, Trade Disputes, and Event Requests
Use focused ticket categories.
Member Report
Ask for:
- Discord member
- platform
- message link
- screenshot if safe
- short explanation
- scam/phishing/harassment context
Raid / Build Help
Ask for:
- platform
- character level
- build archetype
- Power Armor yes/no
- Gleaming Depths experience
- encounter causing trouble
- learner / clear / farm
- voice preference
Trade / Vendor Dispute
Ask for:
- platform
- Discord member involved
- what was agreed
- screenshots/messages
- whether the dispute happened through Discord
- whether real money/account credentials were involved
Your Discord can moderate member conduct, but YourBot cannot reverse an in-game trade.
Event / Private World Request
Ask for:
- platform
- Adventure / Private Adventure / Custom World
- host
- Fallout 1st host available? yes/no
- expected attendance
- event goal
- date/time
Never ask for passwords, Steam Guard codes, console credentials, Bethesda tokens, payment info, or remote access.
Test: Open one Gleaming Depths teaching request and one trade dispute. Confirm mentors and moderators receive different ticket paths.
5. Group Finder: Four Is the Core Team Size
Read-only inspection of YourBot's current develop revision shows Fallout 76 is not in Group Finder's automatic detection list.
The generic setup creates a five-person Quick Group.
That is wrong for Fallout 76's core team content.
Create the first template
Template Name: Fallout 76 — General Team
Game: Fallout 76
Default Party Size: 4
Default Expiry: 2 hours
Description: Four-player Fallout 76 team. Require platform, activity, current team size, build/readiness context, voice, and session goal.
Additional templates
| Template | Target size | Context |
|---|---|---|
| Daily Ops | up to 4 | Platform, current Op, learner/speed, build, voice |
| Expedition | up to 4 | Platform, Expedition, leader identified, goal, voice |
| Gleaming Depths | 4 | Platform, raid experience, build, encounter, communication |
| Activity / Public Event Team | up to 4 | Platform, event-running goal; world may include many others |
| C.A.M.P. / Vendor Tour Team | up to 4 | Platform, tour/trade purpose |
| Roleplay / Exploration Team | up to 4 | Platform, theme, pace |
| Private Adventure Event | Beacon, up to 8 world attendees | Host, platform, Fallout 1st host, team structure |
Example raid listing
Title: Gleaming Depths — Learning
Game: Fallout 76
Platform: PC
Target Size: 4
Current: 3/4
Activity: Gleaming Depths
Status: Learning / first clear
Builds:
- Heavy / Power Armor
- Commando
- Support/Medic
Need:
- Flexible fourth with a raid-capable build
Voice: Recommended
Session: ~2 hours
Notes:
- Joining this Discord listing does not create the in-game team.
- Build/readiness information is self-reported.
- Raid remains four players.
Expedition example
Title: Expedition — 2 spots
Platform: Xbox
Target Size: 4
Leader: Confirmed
Goal: Full objectives / relaxed
Voice: Optional
Only the in-game team leader can start the Expedition.
Test: Fill a four-seat raid and confirm a fifth player goes to waitlist. Then create a three-person casual team and verify it is allowed to stay below four.
6. Beacon Events: Private Adventure and Multi-Team Community Nights
Beacon is better for planned attendance that exceeds one four-player team.
Private Adventure example
Event: Appalachia Private Adventure Night
Platform: PC
World Type: Private Adventure
Host: Fallout 1st host confirmed
Capacity: 8 total players
Structure:
- Team A: up to 4
- Team B: up to 4
Activities:
- Public Events / Activities
- C.A.M.P. tours
- trading
- seasonal objectives
Voice: Optional
Waitlist: Enabled
Bethesda's current support confirms Private Adventure supports eight total players.
Double raid night
Event: Gleaming Depths Double-Team Night
Platform: PlayStation
Attendance: 8
Structure:
- Raid Team A: 4
- Raid Team B: 4
Do not advertise one eight-player raid.
Community Event night
For Activities/Public Events, event attendance can exceed one team because the world activity itself is multiplayer and world-level.
State:
- Discord attendance
- team breakdown
- world/host coordination
separately.
Beacon does not:
- reserve a public world
- guarantee all attendees land on the same Adventure world
- create an in-game team
- grant Fallout 1st
- start an Expedition
- reserve raid entry
Test: Create an eight-person Private Adventure event, split members into two teams, fill it, add a ninth to waitlist, and confirm the event language clearly separates world size from team size.
7. Join-to-Create Voice: Four for Teams, Eight for Private World Social
Create:
Join Team
- limit 4
- delete when empty
- creator ownership
Join Raid
- limit 4
- separate label for Gleaming Depths focus
Private World Social
- limit 8
Community Event
- larger where Discord coordination is useful
Fallout 76 also provides in-game communication/pings. Voice should remain optional unless a particular community run explicitly requires it.
The Gleaming Depths was designed with communication/teamwork in mind, but Bethesda also added contextual pinging to support players who do not want voice.
Test: Fill a four-person raid voice room, verify a fifth cannot enter, then test an eight-person Private World room separately.
8. Announcements: Keep Slasher Stages and Seasons Dated
Use Announcements for:
- weekly team schedule
- current Slasher story stage
- Season 26
- Legacy Season reminders
- maintenance
- seasonal Activities
- Double XP/community calendar
- native console update notices
- PTS opportunities
- new raid/content notes
Current example:
Fallout 76 — September 2026
LIVE:
- The Slasher update
- Season 26: Beware the Blood Moon
- Legacy Seasons
- native Xbox Series X|S and PS5 versions
- Unique Item Crafting
- Fall Seasonal Fish
The Slasher unfolds over multiple weeks.
Do not assume every story stage is unlocked at once.
TEAM REMINDER:
- Public/Normal Team max = 4.
- Daily Ops = up to 4.
- Expeditions = up to 4.
- Gleaming Depths = 4.
- Private Adventure world = 8 total players.
Use opt-in roles such as:
@Season Updates@Gleaming Depths@Events@PTS
The current PTS expanded to consoles in August 2026, but PTS content is testing—not live production. Keep that distinction explicit.
Test: Schedule a Season notice five minutes ahead with one opt-in role and confirm it fires once.
9. Social Feeds: Add Fallout 76 Through the Generic Steam Source
Read-only inspection of YourBot's current Social Feeds catalog shows no curated Fallout 76 entry and no App ID 1151340 entry.
Fallout 76's verified Steam App ID is:
1151340
Create:
Source: Steam
Steam App ID: 1151340
Display Name: Fallout 76 — Official Steam News
Destination: #fallout-76-updates
Ping Role: None by default
Digest: Off or hourly
The inspected YourBot Steam source uses:
- public ISteamNews
- numeric App IDs
- publisher community announcements
- default interval 900 seconds
Use Bethesda's official Fallout site for high-confidence release notes and platform support details; the Steam feed is a convenient automated signal, not a guarantee that every Bethesda support/update item is mirrored.
Start Your Server can enable Social Feeds, but the subscription is a manual follow-up.
Test: Add App ID 1151340, preview it in #fallout-76-updates, confirm formatting, and verify no unwanted ping.
10. Analytics: Measure the Discord, Not the Wastelander
Analytics can help answer:
- Which platform pool is active?
- Do new members finish onboarding?
- Are raid-learning sessions filling?
- Which Activities get community events?
- Are C.A.M.P./trade channels active?
- Do returning players stick around?
- Are voice rooms used?
- Which channels have gone stale?
Analytics does not know:
- character level
- S.P.E.C.I.A.L.
- Perk Cards
- legendary effects
- inventory
- caps
- stash
- C.A.M.P. budget
- vendor stock
- Fallout 1st
- Atoms
- Season Tickets
- SCORE
- raid clears
- plans/recipes
- event rewards
- friend list
- Private World access
Do not rank players by Discord activity.
Test: Generate public chat, a Group Finder team, and voice activity; confirm expected analytics while excluding private trade disputes/tickets.
11. Giveaways: Keep Discord Drawings Out of the Game Economy
Safe prizes:
- choose next C.A.M.P. tour theme
- choose next raid teaching night
- temporary Discord cosmetic role
- community art
- legitimate platform/game code where staff understands redemption
Do not imply YourBot grants:
- Atoms
- Fallout 1st
- caps
- weapons
- armor
- plans
- Legendary Mods
- Season Tickets
- SCORE
- C.A.M.P. items
- Private World access
Never request platform/Bethesda credentials to fulfill a prize.
Test: Run a staff-only giveaway for Choose next community event, verify draw/reroll behavior, then use a similarly low-risk public prize.
Keep PC, Xbox, and PlayStation Socially Together but Operationally Separate
Appalachian Relay does not need three separate Discords.
All platform groups can share:
- builds
- screenshots
- C.A.M.P. ideas
- story discussion
- update news
- event guides
- Season progress discussion
But operational LFG must say:
- PC
- Xbox
- PlayStation
Steam and Microsoft's PC client belong together for PC multiplayer.
Do not treat Xbox App on PC as Xbox Console.
That distinction belongs in onboarding help because it is easy for new members to misunderstand.
Separate World Capacity From the Team UI
This is the most important Fallout 76 Discord design lesson.
Four-player team
- Daily Ops
- Expedition
- Gleaming Depths
- normal Public/Private Team
Eight-player world
- Private Adventure
- Custom World
Twenty-four-player world
- Public World
A community event can therefore say:
8 players in one Private Adventure, arranged into two teams.
or:
12 community members trying to join the same public Adventure session, organized across three teams.
Do not label that as a 12-player Fallout 76 team.
Trading and Vendors Need Platform Labels
Fallout 76 supports player trading and player vendors.
A Discord trade post should include:
- platform
- item/category
- wanted/offering
- price/caps/trade terms
- availability
- whether this is player-to-player trade or C.A.M.P. vendor stock
- timestamp
Do not build cross-platform trade expectations.
A PC player cannot fulfill a trade to an Xbox character merely because both users are in Discord.
Keep high-value trade disputes private through Tickets.
The Discord should never hold escrow, passwords, or real-money payments.
C.A.M.P. Communities Are a Real Workflow
Many Fallout 76 communities are as interested in building as raiding.
Create:
- C.A.M.P. screenshots
- build competitions
- theme nights
- shelter tours
- vendor tours
- seasonal decoration events
Beacon is excellent for:
Event: Halloween CAMP Tour
Platform: Xbox
Attendance: 12
World strategy: multiple teams / shared session where possible
Theme: Beware the Blood Moon
Do not make C.A.M.P. building another "raid" template.
Add a Wasteland Readiness Registry Only When You Need It
Appalachian Relay can launch with the ten built-in services.
Group Finder handles the team forming now. Beacon handles scheduled events. Tickets handle disputes and coaching. Announcements handle current updates.
A custom plugin becomes useful if raid leads and event hosts repeatedly ask:
Which members on this platform say they have a raid-ready build, what roles can they fill, and who can host a Private Adventure?
Before building, check the Marketplace for an existing maintained solution. If none fits, create Wasteland Readiness Registry.
Copy-ready Plugin Builder specification
Plugin Name: Wasteland Readiness Registry
Purpose:
Maintain self-reported Fallout 76 player/build readiness for raids, Daily Ops, Expeditions, Private Adventure hosting, teaching, and community event planning without duplicating Group Finder, Beacon Events, Tickets, or Announcements.
Version 1 network policy:
No external network access.
No Bethesda account integration.
No Steam/Xbox/PlayStation integration.
No game API.
No inventory/vendor scraping.
Never request/store:
- Bethesda password
- Steam password
- Xbox/PlayStation password
- email password
- 2FA / Steam Guard / recovery code
- session token/cookie
- payment data
- remote-access credentials
Roles:
Administrators:
- Administrator
- Moderator
Planning:
- Raid Lead
- Mentor
- Event Host
Member abilities:
- create/update own Fallout 76 profile
- archive stale profile
- choose member-visible or lead-only optional notes
Profile fields:
- Discord user ID
- Fallout 76 display name
- platform:
PC | Xbox | PlayStation
- PC launcher:
Steam | Microsoft PC | not_applicable | prefer_not_to_say
- character_level: self-reported integer
- build_archetype:
Heavy | Commando | Rifleman | Melee | Shotgun | Pistol | Support | Stealth | Other
- power_armor:
yes | no | situational
- activities:
Daily Ops | Expeditions | Gleaming Depths | Public Events | CAMP | Trading | Roleplay | Fishing
- gleaming_depths_status:
not_ready | learning | clear | farm | mentor
- preferred_raid_responsibility
- daily_ops_ready: yes/no
- expedition_ready: yes/no
- private_adventure_host:
yes/no
- fallout_1st_host_note:
optional; do not verify membership
- voice_available: yes/no
- current_goals
- usual_availability
- last_reviewed_at
- status:
active | needs_update | archived
Lead-only fields:
- teaching_note
- raid_team_note
- reviewed_by
- reviewed_at
- event_host_note
Search filters:
- platform
- build archetype
- Power Armor
- Gleaming Depths readiness
- Daily Ops
- Expeditions
- Private Adventure host
- voice
- mentor status
- stale profile
Suggested commands:
- /wasteland-profile create
- /wasteland-profile edit
- /wasteland-profile mine
- /wasteland-profile archive
- /wasteland-roster search
- /wasteland-roster raid
- /wasteland-roster expedition
- /wasteland-roster host
- /wasteland-roster stale
- /wasteland-roster mark-reviewed
Dashboard member view:
- My Profile
- platform
- build
- activity readiness
- raid status
- Private Adventure hosting
- goals
- last reviewed
Dashboard lead view:
- platform-isolated roster
- raid readiness filters
- build/responsibility filters
- Private Adventure hosts
- learner/mentor view
- stale profiles
- lead notes
- audit history
Authorization:
- every read/write enforced server-side
- members edit only own profile
- lead-only fields require current Discord roles
- revoking Raid Lead/Mentor removes access next request
- direct record URLs enforce same authorization
- data isolated by Discord server ID
- exports, if ever added, are staff-only and audited
Security/privacy:
- do not store exact inventory
- do not store vendor stock as authoritative live inventory
- do not store Atoms/Season Ticket balances
- do not store payment details
- do not claim Fallout 1st verification
Explicit non-capabilities:
- Does not verify account ownership.
- Does not read level/build/inventory/caps/plans/raid clears automatically.
- Does not create Fallout 76 teams.
- Does not start Expeditions.
- Does not create Private Worlds.
- Does not grant Fallout 1st.
- Does not perform trades.
- Does not transfer items/caps.
- Does not replace Group Finder.
- Does not replace Beacon.
- Does not rank player skill from Discord activity.
Acceptance tests:
1. PC member creates a Gleaming Depths-ready profile.
2. Xbox member remains excluded from PC operational roster searches.
3. Member cannot edit another profile.
4. Raid Lead finds four PC raid-ready members.
5. Event Host filters Private Adventure hosts on PlayStation.
6. Revoking Raid Lead removes lead notes/search access.
7. Direct URL cannot bypass authorization.
8. Server A cannot read Server B Discord data.
9. Archived profile disappears from active roster.
10. No workflow requests account credentials.
Review, test, and continue through the SDK
Review:
- generated source
- manifest
- capabilities
- storage
- commands
- authorization
Test as:
- normal Member
- PC member
- Xbox member
- PlayStation member
- Raid Lead
- Mentor
- revoked lead
Test direct URLs, cross-server isolation, archives, and any export behavior.
Continue using the current YourBot SDK:
yourbot new
yourbot dev
yourbot dev --watch
yourbot validate
yourbot doctor
Marketplace publication is optional.
Passing validation does not prove someone is raid-ready.
Run a Complete First-Week Member Journey
| Scenario | Successful result |
|---|---|
| New PC member joins | Verifies, picks PC and activities, sees no staff channels. |
| Xbox member joins | Shares social channels but cannot accidentally join a PC operational LFG. |
| Daily Ops team | Listing caps at 4. |
| Gleaming Depths | Raid listing caps at 4 and sends the fifth person to waitlist. |
| Private Adventure | Event caps world attendance at 8 and describes two teams rather than one 8-player raid. |
| Trade dispute | Ticket stays private and does not promise game-item reversal. |
| C.A.M.P. event | Beacon handles tour attendance independently from team size. |
| Readiness registry | Member self-reports build/raid status; lead-only notes disappear after revocation. |
| Season update | Slasher/Season 26 announcement is dated and does not imply all multi-week stages are already live. |
Fix platform/team/world confusion before adding more automation.
Frequently Asked Questions
Can PC, Xbox, and PlayStation players all play Fallout 76 together?
Do not treat them as one matchmaking pool. Bethesda explicitly confirms Steam and Microsoft PC players can play together on PC, while progress is not transferable between platform families. Build operational LFG as PC, Xbox, or PlayStation.
How many players are in a normal Fallout 76 team?
Up to four.
How many players are in Gleaming Depths?
Four. It is specifically designed as a four-player endgame raid.
How many players can join a Private Adventure?
Eight total players.
Does that make Private Adventure an eight-player team?
No. It is world capacity. Players can be arranged into multiple teams.
Does YourBot automatically detect Fallout 76?
Not in the read-only develop revision inspected for this guide. Create explicit four-player Fallout 76 templates.
Is Fallout 76 in YourBot's curated Social Feeds catalog?
Not in the inspected catalog. Add the generic Steam source manually with App ID 1151340.
What is live right now?
As of September 25, 2026: The Slasher update, Season 26: Beware the Blood Moon, Legacy Seasons, native Xbox Series/PS5 versions, Unique Item Crafting, and current Slasher stages are live.
Can YourBot read my build, raid clears, caps, inventory, or vendor stock?
Not through the built-in services. The optional Wasteland Readiness Registry is deliberately self-reported.
Build the Discord Around Platform, Team, and World—In That Order
Fallout 76 already has game-side systems for Worlds, teams, Activities, raids, Expeditions, C.A.M.P.s, player vendors, Seasons, and account progression. A useful Discord should make those systems easier to coordinate without pretending to replace them.
Start Your Server creates the stable shell. Welcome separates platform pools. Sentinel protects trade/community spaces. Tickets route raid help and disputes privately. Group Finder uses the real four-player team structure. Beacon handles eight-person Private Adventures and larger community nights without pretending they are giant teams. Temporary voice mirrors actual teams or world events. Announcements keep Slasher stages and Season 26 dated. Social Feeds uses official Steam publisher updates without pretending it replaces Bethesda support/news.
Fallout 76 remains authoritative for characters, teams, World access, Fallout 1st, raids, items, caps, C.A.M.P.s, trades, Season progress, and rewards.
Use Start Your Server to establish or refine the Discord foundation. Add Plugin Builder only when a persistent workflow such as cross-platform readiness/Private World hosting becomes a real recurring need the built-in services do not already solve.