How to Build and Run a 7 Days to Die Discord Community With YourBot

TH The YourBot Team 2026-09-27 · 29 分で読めます
server setup
How to Build and Run a 7 Days to Die Discord Community With YourBot

A 7 Days to Die Discord should be organized around the server people are actually joining, the server's platform/crossplay profile, world rules, Blood Moon cadence, party/allies behavior, base ownership, wipe policy, and the specific survival session being coordinated. It is not a generic five-player co-op game.

The current game supports PC, PlayStation 5, and Xbox Series X|S crossplay under the game's supported cross-platform rules. Dedicated servers can also support console players, but only when the server stays inside the required console-compatible settings. That matters because a vanilla crossplay server and a PC-only modded server are operationally different communities even if both are called "7 Days to Die."

The normal community challenge is not "what is the raid size?" It is:

This guide builds a fictional 246-member community called Navezgane Relay with two intentionally different servers:

Relay Crossplay

Relay Experimental

YourBot handles the Discord structure and coordination. 7 Days to Die remains authoritative for the live world, server connection, player inventory, Party/Allies state, Land Claim Blocks, quests, loot, game stage, server permissions, mods, player saves, vehicles, crafting, and Blood Moon behavior.

Start With the Right 7 Days to Die Community Model

Crossplay server and PC-only modded server are not the same thing

Current crossplay can connect:

But dedicated servers visible to consoles must meet the game's crossplay requirements.

Current support guidance referenced by The Fun Pimps' support team requires a crossplay-compatible server profile with constraints including:

PC players can join a wider range of server configurations than console players. A PC-only server can therefore use mods or settings that would make it disappear from a console player's browser.

That is why Navezgane Relay has two server identities instead of pretending every member can join every server.

Current stable version is v3.2.0

As of September 25, 2026, v3.2.0 is the current stable release.

It went stable on August 26.

The Fun Pimps describes v3.2 as part of a new rhythm of smaller quality-of-life/fix releases alongside ongoing work on v4.0, which is still in development.

The current stable line sits on top of the major v3.0 Dead Hot Summer release, which introduced:

v3.1 then added Henpocalypse features such as Chicken Coops and additional sandbox settings.

Treat v4.0 as future development. Do not write v4 features into today's server rules until they are actually released.

A 7 Days server has a player capacity, not a universal party size

A dedicated server has a configured maximum player count.

For console-compatible crossplay dedicated servers, the important practical ceiling is 8 total players.

PC-only dedicated servers can be configured differently, but server performance and game support need to be considered carefully before pushing player counts upward.

The in-game Party is a separate concept used for cooperative systems such as:

Do not confuse:

server has 8 slots

with:

every eight players must be one permanent party.

The community may have several parties or players doing independent work inside the same server.

Party and Allies are different systems

This is one of the most important community-management details.

Land Claim Block permissions care about Allies, not merely Party membership.

The current official wiki notes that a party member still needs to be an Ally of the Land Claim owner to place or destroy blocks inside the protected area.

That means Discord onboarding should teach:

Party = co-op session grouping.

Allies = persistent trust/claim relationship.

A member can join today's quest party without automatically receiving build rights in the main settlement.

This prevents accidental base edits and griefing.

Blood Moon rules are server-specific

The default configuration uses:

But server owners can change those values.

The Blood Moon also scales with multiplayer conditions. Current server settings include:

Do not write:

Blood Moon is always every seventh night.

Write:

On Relay Crossplay, Blood Moon is currently every 7 days with Range 0.

If the owner changes the sandbox preset, update the Discord schedule.

Quests are cooperative, but players still have individual steps/rewards

Shared quests can coordinate a Party, but not every objective behaves identically.

Current official quest documentation notes:

That makes a Quest LFG useful, especially for:

YourBot can coordinate the humans. It does not start or share the quest in-game.

Server wipes are community policy, not a game universal

A long-running survival server eventually needs an explicit answer to:

Navezgane Relay uses:

Relay Crossplay

Relay Experimental

The Discord should make wipe policy visible before someone spends 60 hours building a fortress.

The Community We Will Build

Navezgane Relay is a 246-member 7 Days to Die Discord.

Relay Crossplay

Relay Experimental

Community activities

YourBot's role in the community

Service Community use
Welcome Collect Crossplay/Experimental server interest, platform, playstyle, building/logistics, and new-player interests.
Sentinel Reduce phishing, malicious mod downloads, fake server tools, credential theft, harassment, grief coordination, spam, and raids.
Tickets Route whitelist/access requests, grief/base reports, mod/content issues, wipe questions, and support privately.
Group Finder Coordinate quests, Blood Moon prep, mining, looting, farming, building, and survival sessions.
Beacon Events Schedule Blood Moons, wipe events, build nights, horde-base tests, community challenge presets, and server maintenance-facing events.
Join-to-Create Voice Create temporary survival-party, build-team, and Blood Moon voice rooms.
Announcements Publish server version, sandbox preset, Blood Moon schedule, wipe policy, modpack changes, and maintenance.
Social Feeds Use the existing curated 7 Days to Die Steam publisher feed.
Analytics Measure Discord onboarding, LFG use, event attendance, voice use, support load, and channel health.
Giveaways Run Discord-side drawings without implying YourBot grants game copies, server items, admin rights, or in-game resources automatically.

1. Create the Foundation With Start Your Server

A survival community needs durable operational information.

Do not create permanent channels for every current POI, weapon, skill tree, biome, zombie type, or Trader.

Copy-ready community brief

Design a 7 Days to Die Discord called Navezgane Relay.

Community:
- About 250 Discord members.
- We run two server profiles.

SERVER 1: Relay Crossplay
- PC + PS5 + Xbox Series X|S
- stable branch only
- current stable version should be announced
- max 8 players
- crossplay enabled
- EAC enabled
- vanilla / console-compatible
- no unsupported mods
- community PvE survival
- conservative wipe policy

SERVER 2: Relay Experimental
- PC-only
- 12 configured slots
- curated modlets / custom sandbox settings
- not console-compatible
- staging-first testing
- more frequent wipes

Teach members:
- Server capacity is not the same thing as Party membership.
- Party and Allies are different.
- Land Claim building rights depend on Allies, not merely being in today's Party.
- Blood Moon schedule is server-configured.
- Shared quests still contain individual fetch/reward steps.
- Do not assume the default Day 7 Blood Moon if server settings change.

Roles:
Owner
Administrator
Server Admin
Moderator
Event Host
Builder Lead
Horde Lead
Mentor
Member
New Survivor

Self-select:
Relay Crossplay
Relay Experimental
PC
PlayStation 5
Xbox Series X|S
Questing
Blood Moon
Building
Mining
Looting
Farming
Crafting
Vehicles
Trading
New / Returning
PvP Events
Server Updates

Do not self-select:
Server Admin
Moderator
Builder Lead if it grants base access
Horde Lead
trusted roles

Channels:
START HERE: welcome, rules, choose-roles, server-info
COMMUNITY: general, questions, screenshots, builds-and-loadouts
SERVERS: relay-crossplay, relay-experimental, version-and-modpack
SURVIVAL: lfg-listings, lfg-forum, events
BASE: base-planning, blood-moon-planning
CRAFT & LOGISTICS: mining-and-resources, farming-and-crafting
UPDATES: 7dtd-updates
HELP: open-a-ticket
VOICE: join-party, build-team, blood-moon
STAFF: staff-chat, sentinel-logs, ticket-log, change-control

Safety:
- Never request Steam, PlayStation, Xbox, Epic/EOS, Discord, or email passwords.
- Never request 2FA/recovery codes, session tokens, payment data, hosting-panel credentials, telnet passwords, web-dashboard passwords, API keys, or remote access.
- Treat random mod executables, fake mod launchers, malicious mod archives, phishing, impersonation, and grief coordination as risks.
- Discord roles do not grant server admin/telnet/web-dashboard access.
- Discord Builder roles do not automatically add players as in-game Allies.
- YourBot does not change Land Claims, Parties, Allies, game saves, admin permissions, inventories, or world files.

Configure all ten built-in services:
Welcome
Sentinel
Tickets
Group Finder
Beacon Events
Join-to-Create Voice
Announcements
Social Feeds
Analytics
Giveaways

YourBot specifics:
- 7 Days to Die is not in the currently inspected Group Finder automatic detection list.
- Do not use the generic 5-player Quick Group as a game rule.
- Use session-target templates.
- Social Feeds already has a curated 7 Days to Die entry using Steam App ID 251570.
- Announcements schedules and Social Feed subscriptions require manual finishing steps.
- Preserve existing structure on first build.
- Keep deletions off.
- Preview New Survivor, Member, Builder Lead, Server Admin, and Moderator perspectives.

A compact channel plan

NAVEZGANE RELAY
├─ START HERE
│  ├─ #welcome
│  ├─ #rules
│  ├─ #choose-roles
│  └─ #server-info
├─ COMMUNITY
│  ├─ #general
│  ├─ #questions
│  ├─ #screenshots
│  └─ #builds-and-loadouts
├─ SERVERS
│  ├─ #relay-crossplay
│  ├─ #relay-experimental
│  └─ #version-and-modpack
├─ SURVIVAL
│  ├─ #lfg-listings
│  ├─ #lfg-forum
│  └─ #events
├─ BASE
│  ├─ #base-planning
│  └─ #blood-moon-planning
├─ CRAFT & LOGISTICS
│  ├─ #mining-and-resources
│  └─ #farming-and-crafting
├─ UPDATES
│  └─ #7dtd-updates
├─ HELP
│  └─ #open-a-ticket
├─ VOICE
│  ├─ 🔊 Join Party
│  ├─ 🔊 Build Team
│  └─ 🔊 Blood Moon
└─ STAFF
   ├─ #staff-chat
   ├─ #sentinel-logs
   ├─ #ticket-log
   └─ #change-control

Review before applying

Preview:

A normal Member should be able to read connection/version rules without seeing server-control secrets.

Keep deletion disabled on the first build.

Announcements schedules and Social Feed subscriptions require manual finishing steps.

2. Welcome: Server Profile Before Playstyle

Welcome should answer:

  1. Crossplay or Experimental?
  2. Platform?
  3. What do you enjoy doing?

Useful roles:

A player can choose both servers if they are on PC.

Do not let a console member select Relay Experimental if the server is intentionally PC-only/modded without a clear warning.

A concise greeting:

Welcome to Navezgane Relay. Pick Relay Crossplay or Relay Experimental before joining a session. Crossplay is vanilla/console-compatible and capped at 8; Experimental is PC-only and modded. Party and Allies are different—being in a quest Party does not automatically grant build rights in someone else's Land Claim.

Test: Join from a test account, choose PlayStation 5, Relay Crossplay, and Blood Moon, and verify Experimental-only access is not accidentally implied.

3. Sentinel: Treat Mod Links and Server Credentials as a Security Surface

7 Days communities share:

That creates a real Discord security problem if every downloadable file is trusted.

Focus Sentinel on:

Do not ban the words:

Staff legitimately discusses them.

Use dry-run/report mode for aggressive URL rules.

Secret policy

Never post:

Discord moderation is not server enforcement.

Test: Post a controlled dummy password=CHANGEME-style server-secret pattern and fake mod executable URL in a staff-only test channel; verify the intended Sentinel behavior.

4. Tickets: Access, Griefing, Mods, and Wipe Questions Need Different Paths

Server Access / Join Problem

Ask for:

Do not request account credentials.

Grief / Base Report

Ask for:

YourBot cannot roll back the world.

Mod / Experimental Issue

Ask for:

The Fun Pimps support guidance recommends disabling third-party mods when isolating game bugs.

Wipe / World Request

Ask for:

Member Report

Ask for:

Test: Open one Crossplay join issue and one Experimental mod issue. Confirm they route differently and neither requests passwords.

5. Group Finder: Use Session Targets, Not the Generic Five

Read-only inspection of YourBot's current develop revision shows 7 Days to Die is not in Group Finder's automatic game-detection list.

The generic setup creates a five-person Quick Group.

That number is not a meaningful universal 7 Days rule.

Create the first template

Template Name: 7 Days to Die — Survival Session
Game: 7 Days to Die
Default Party Size: 4
Default Expiry: 2 hours
Description: General co-op session. Require server profile, platform, goal, current players, whether Allies/build rights are needed, voice, and duration. Four is a community planning target, not a universal game cap.

Additional templates

Template Target Context
Quest Party 4 Server, Trader/tier, POI goal, shared quest, Allies not required
Mining / Resource Run 4 Server, biome/resource, vehicle, duration
Build Crew 4 Server, base/horde-base, Ally/build permission required
Blood Moon Team up to 8 on Crossplay Server, base, Day, prep roles, voice
New Survivor Catch-up 4 Server, quests, gear/progression, teaching
Experimental Mod Session organizer-defined PC-only, modpack revision, test goal
Crossplay Full Night Beacon 8 Server-wide attendance, not necessarily one Party

Example quest listing

Title: Tier Quest Loop — need 2
Game: 7 Days to Die
Server: Relay Crossplay
Platforms: PC / PS5 / Xbox Series X|S
Target Session Size: 4
Current: 2/4
Goal: Trader quest progression
Party: Yes
Allies / Build Rights: Not needed
Voice: Optional
Duration: ~2 hours
Notes:
- Shared objectives are coordinated in-game.
- Fetch supplies remain individual.
- Each player turns in for their own reward.

Example build listing

Title: Horde Base Reinforcement
Server: Relay Crossplay
Target: 4
Allies Required: Yes, for build/claim permission
Goal: repair + concrete + electrical traps
Blood Moon: Day 42, current server schedule
Voice: Recommended

Do not assume someone should be added as an Ally just because they joined one mining run.

Test: Fill a four-person quest session and confirm a fifth waits. Then create an eight-person Blood Moon planning session for Relay Crossplay and confirm the listing clearly states that eight is server capacity, not a permanent party rule.

6. Beacon Events: Blood Moon, Wipe, and Server-Wide Nights

Beacon is ideal for schedule-driven survival events.

Blood Moon

Event: Relay Crossplay — Day 42 Blood Moon
Server: Relay Crossplay
Server Capacity: 8
Blood Moon Schedule:
- Frequency: 7
- Range: 0
Staging: 20:00
Attendance Cap: 8
Horde Base: Relay North
Roles:
- Repairs
- Ammo / Guns
- Electric Traps
- Melee / Breach
- Medical
- Reserve / Logistics
Voice: Recommended

Never hard-code Day 42 into the permanent Discord; derive the next event from the current world day/server settings.

Wipe night

Event: Relay Experimental — Season Reset
Status: WORLD WIPE
Notice Period: 7 days
Archive:
- screenshots encouraged
- old save retained privately by server admin if policy allows
New World:
- new seed/preset
- modpack revision published before launch

Crossplay community night

Eight attendees can fill Relay Crossplay.

The event should still distinguish:

Beacon does not:

Test: Create an eight-seat Blood Moon event and overfill it. Confirm waitlist behavior and that Builder roles do not automatically imply in-game Ally access.

7. Join-to-Create Voice: Separate Survival Party, Build Team, and Full Server

Create:

Join Party

Build Team

Blood Moon

Experimental Test

Enable:

The game already supports party voice through EOS. Discord voice is optional community infrastructure.

Test: Fill a four-person Party voice room and confirm the fifth cannot enter. Test the eight-person Blood Moon room separately.

8. Announcements: Publish Version, Server Profile, Blood Moon, and Wipe State

Announcements should answer operational questions immediately.

Current example

7 Days to Die — Relay Status

CURRENT STABLE:
- v3.2.0

Relay Crossplay:
- Stable branch
- PC / PS5 / Xbox Series X|S
- Max 8
- EAC on
- Vanilla / console-compatible
- Blood Moon Frequency: 7
- Blood Moon Range: 0

Relay Experimental:
- PC-only
- Modpack revision: EX-2026.09
- Stable branch unless #change-control says otherwise
- 12 configured slots

UPSTREAM:
- v4.0 is in development, not live.

Reminder:
- A major version/modpack change may require world compatibility review.
- Do not update production servers blindly.

Announcements should also cover:

Test: Schedule a staff-only version notice five minutes ahead with @Server Updates, then verify it posts once.

9. Social Feeds: Use the Existing Curated 7 Days to Die Entry

Read-only inspection of:

mmo_maid/plugins/social/game_catalog.py

shows an existing curated entry:

Slug: 7daystodie
Name: 7 Days to Die
Source: steam_news
Steam App ID: 251570
Category: Survival

Use that entry and send it to #7dtd-updates.

The inspected Steam adapter uses:

That is a good fit because The Fun Pimps currently publishes stable-update notices through Steam, including v3.2 and v3.1.

Do not claim the feed tells you:

Those are server-operator decisions.

Test: Select the curated 7 Days to Die entry, preview it in #7dtd-updates, and confirm no unwanted role ping.

10. Analytics: Measure the Discord, Not the World Save

Analytics can answer:

Analytics does not know:

Do not use Discord message counts as a survival-skill score.

Test: Generate public chat, LFG, and voice activity; verify private tickets/change-control stay excluded where appropriate.

11. Giveaways: Keep Discord Drawings Out of the Server Save

Safe prizes:

Do not imply YourBot grants:

Never ask for account or server-control credentials.

Test: Run a staff-only giveaway for Choose next sandbox preset event, verify winner/reroll behavior, then use the same safe model publicly.

Run Crossplay and Modded Servers as Separate Products

This is the most useful structural decision Navezgane Relay makes.

Relay Crossplay

Priorities:

Relay Experimental

Priorities:

Do not promise:

Experimental is crossplay too.

Do not install one mod on Crossplay and assume console players will "probably be fine."

Publish server identity clearly.

Teach Party, Allies, and Land Claims as Three Separate Concepts

A mature 7 Days community needs to teach these early.

Party

Allies

Land Claim

A good server rule:

Never request Ally status purely to join a quest group. Ally status is granted when the owner intentionally trusts you with protected-base access.

This reduces griefing and accidental damage.

Make Blood Moon Operations a Real Community Workflow

Blood Moon prep is the closest thing 7 Days has to a recurring "raid night."

A serious Blood Moon post should include:

Because party Game Stage and configured enemy counts influence pressure, adding players is not always a free difficulty reduction.

Do not promise:

More players always makes Blood Moon easier.

A poorly prepared eight-player base can create more pressure than a well-designed smaller group.

Treat Wipes, Mods, and Version Changes as Change Management

Every survival server eventually becomes an operations project.

Before updating:

  1. read upstream notes
  2. back up world/save
  3. confirm mod compatibility
  4. test on staging when possible
  5. decide whether wipe is required
  6. update #version-and-modpack
  7. announce maintenance
  8. update production
  9. validate joins/quests/base state
  10. publish completion

For v3.2 specifically, The Fun Pimps changed server/mod-facing behavior including custom POI delivery and XML-related behavior.

For v4.0, do not assume compatibility until the release actually exists.

Add an Apocalypse Server & Settlement Registry Only When You Need It

Navezgane Relay can launch with the built-in services.

Group Finder handles today's session. Beacon handles Blood Moon/wipe events. Tickets handle access/grief/mod support. Announcements handle version and maintenance.

A custom project becomes useful if admins repeatedly ask:

Which server is current, what preset/modpack is deployed, when is the next wipe/Blood Moon, and which settlement teams have approved build access?

Before building, check the Marketplace for a maintained solution. If none fits, create Apocalypse Server & Settlement Registry.

Copy-ready Plugin Builder specification

Plugin Name: Apocalypse Server & Settlement Registry

Purpose:
Maintain Discord-local operational metadata for 7 Days to Die servers, wipe policy, sandbox profile, Blood Moon planning, and member-created settlements without connecting to the live server.

Version 1 network policy:
No external network access.
No telnet.
No WebDashboard/control-panel API.
No Steam/EOS API.
No hosting API.
No save-file access.
No mod-download automation.

Never request/store:
- telnet password
- WebDashboard password
- server password intended to remain secret
- Steam/EOS credentials
- hosting-panel token
- SSH/FTP/SFTP credentials
- API key
- payment data
- world backup credentials

Roles:
Administrators:
- Administrator
- Server Admin

Operational editors:
- Moderator
- Event Host
- Builder Lead

Member:
- can view public server records
- can create/update own settlement record if enabled

Server record fields:
- server_name
- environment:
  crossplay | pc_modded | staging | retired
- game_version
- branch:
  stable | experimental
- max_players
- crossplay_enabled:
  yes | no
- console_compatible:
  yes | no | needs_review
- eac_enabled:
  yes | no
- modded:
  yes | no
- modpack_revision
- sandbox_preset_name
- sandbox_code_note:
  optional non-secret text
- pvp_mode_note
- blood_moon_frequency
- blood_moon_range
- current_world_day:
  manually maintained
- next_blood_moon_note:
  manually maintained
- wipe_policy
- next_planned_wipe
- last_backup_confirmed_at:
  status/date only, not backup secret
- last_update_reviewed_at
- public_join_note
- status:
  online_unknown | maintenance | planned | retired

Settlement record fields:
- settlement_name
- server_name
- owner_discord_user
- purpose:
  main_base | horde_base | farm | crafting | trading | community | other
- ally_required_for_building:
  yes/no
- builder_roles
- public_location_note:
  optional; avoid exact coordinates if community policy treats them as sensitive
- current_project
- materials_needed
- blood_moon_ready:
  yes | no | needs_review
- last_reviewed_at
- status:
  active | abandoned | archived

Staff-only fields:
- change_note
- rollback_note
- grief_case_note
- restricted_location_note
- reviewed_by
- reviewed_at

Suggested commands:
- /7dtd-server list
- /7dtd-server view
- /7dtd-server set-version
- /7dtd-server set-wipe
- /7dtd-server bloodmoon
- /settlement create
- /settlement edit
- /settlement list
- /settlement materials
- /settlement archive

Dashboard member view:
- server cards
- stable/experimental identity
- max players
- crossplay/PC-only
- current version
- modpack revision
- Blood Moon policy
- wipe policy
- active settlement projects

Dashboard staff view:
- all member fields
- staging records
- change notes
- review dates
- backup-confirmation timestamp
- restricted settlement notes
- audit history

Authorization:
- every read/write server-side authorized
- members edit only settlements they own or are explicitly allowed to manage
- server records editable only by configured operational roles
- revoking Server Admin/Builder Lead removes access next request
- direct record URLs enforce same policy
- data isolated by Discord server ID
- exports, if added, staff-only and audited

Secret rejection:
Reject or warn on fields containing:
- telnet password
- WebDashboard password
- API token
- SSH private key
- FTP credential
- hosting token
- Steam/EOS password
- session cookie

Explicit non-capabilities:
- Does not query server uptime.
- Does not query player count.
- Does not modify serverconfig.xml.
- Does not start/restart the server.
- Does not execute telnet/RCON/admin commands.
- Does not add Allies.
- Does not change Land Claims.
- Does not read world saves.
- Does not install/update mods.
- Does not perform backups.
- Does not calculate guaranteed Blood Moon difficulty.
- Does not replace Group Finder, Beacon, Tickets, or Announcements.

Acceptance tests:
1. Member can see Crossplay server version and wipe policy.
2. Member cannot see staging/rollback notes.
3. Builder creates a Horde Base settlement project.
4. Normal member cannot edit another settlement.
5. Revoking Builder Lead removes elevated settlement access.
6. Server Admin updates version and audit record appears.
7. Direct URL cannot reveal staff-only change notes.
8. Server A Discord cannot read Server B registry.
9. Secret-like telnet/control-panel values are rejected.
10. No operation makes an external network call.

Review, test, and continue through the SDK

Review:

Version 1 should require no external network access.

Test as:

Test direct URLs, secret rejection, archived settlements, and cross-Discord isolation.

Continue with the current YourBot SDK workflow:

yourbot new
yourbot dev
yourbot dev --watch
yourbot validate
yourbot doctor

Marketplace publication is optional.

Passing validation does not prove server settings are console-compatible or that a save is safe to update.

Run a Complete First-Week Member Journey

Scenario Successful result
New PS5 member joins Selects Relay Crossplay and cannot mistake Experimental for console-compatible.
PC mod player joins Understands Experimental uses a separate mod/version policy.
Quest party Listing uses a practical session target and explains shared versus individual quest steps.
Build crew Requires Allies/build permission explicitly.
Blood Moon Event uses current server day/frequency rather than assuming every seventh day forever.
Grief report Ticket captures evidence without promising automatic rollback.
Version update Announcement publishes v3.2.0 and server-specific revision state.
Social Feed Curated official publisher news lands in updates channel.
Registry Member sees public server/wipe state; secret/control notes remain restricted.

Fix crossplay/mod/Party/Allies confusion before adding more automation.

Frequently Asked Questions

What is the current stable version of 7 Days to Die?

As of September 25, 2026, the current stable release is v3.2.0.

Is v4.0 live?

No. The Fun Pimps says v4.0 remains in development while the smaller-update team ships releases such as v3.2.

Can PC, PS5, and Xbox Series X|S play together?

Yes under the current supported crossplay setup. Dedicated servers must remain inside the console-compatible crossplay requirements.

Can a crossplay dedicated server be modded?

Do not design a console crossplay community around mods. Current crossplay guidance requires a console-compatible/vanilla-style configuration; PC-only modded servers should be treated separately.

How many players can a crossplay dedicated server have?

The current console-compatible dedicated-server requirement caps ServerMaxPlayerCount at 8.

Is the in-game Party also limited to the server's maximum?

Server capacity and Party state are separate concepts. On an 8-slot crossplay server, eight is the total world/server population ceiling; members can still have different Party/Allies relationships.

What is the difference between Party and Allies?

Party is the current cooperative group. Allies are persistent trust relationships relevant to systems such as Land Claim building permissions. A Party member is not automatically allowed to build in another player's claimed base.

Does YourBot automatically detect 7 Days to Die in Group Finder?

Not in the read-only develop revision inspected for this guide. Create explicit 7DTD templates manually.

Is 7 Days to Die already in YourBot Social Feeds?

Yes. The inspected curated catalog includes 7daystodie using Steam App ID 251570.

Can YourBot read my world day, player level, Land Claim, save, inventory, or server config?

Not through the built-in services. The optional Apocalypse Server & Settlement Registry is deliberately manually maintained in version 1.

Build the Discord Around the Server Rules That Actually Exist

7 Days to Die already provides the game systems for worlds, Parties, Allies, Land Claims, quests, crafting, Blood Moons, sandbox presets, dedicated servers, mods, and player progression. A useful Discord makes those systems understandable and coordinated without pretending to replace them.

Start Your Server creates the durable community shell. Welcome distinguishes crossplay from PC-only Experimental play. Sentinel protects a mod/server-heavy community from bad downloads and credential leaks. Tickets separate join problems, griefing, and mod support. Group Finder coordinates real survival sessions without pretending five is a universal party size. Beacon schedules Blood Moons, wipes, and full-server nights. Temporary voice mirrors the session. Announcements publish version/preset/wipe state. Social Feeds uses the existing curated 7 Days to Die publisher feed.

7 Days to Die remains authoritative for server/world state, saves, Parties, Allies, Land Claims, quests, inventories, player permissions, mods, and Blood Moon behavior.

Use Start Your Server to establish or refine the Discord foundation. Add Plugin Builder only when persistent server/wipe/settlement state becomes a real operational need the built-in services do not already solve.

← ブログに戻る
2026-09-27 ·31 分 How to Build and Run an EVE Online Discord Community With YourBot Build an EVE Online Discord with YourBot: corp recruitment, activity-specific fleets, strategic events, operational security, temporary voice, and current New Eden updates. 続きを読む → 2026-09-27 ·28 分 How to Build and Run a Roblox Discord Community With YourBot Build a Roblox Discord with YourBot: experience-specific LFG, Parties and private-server events, safe onboarding, temporary voice, official updates, and creator workflows. 続きを読む → 2026-09-26 ·26 分 How to Build and Run a Star Wars: The Old Republic Discord Community With YourBot Build a SWTOR Discord with YourBot: server- and faction-aware 4-player Flashpoints, 8/16-player Operations, Guild/Conquest workflows, PvP/GSF, and current 7.9.1/GS11 planning. 続きを読む → 2026-09-26 ·34 分 How to Build and Run a World of Warcraft: Forever Discord Community With YourBot Build a World of Warcraft: Forever Discord with YourBot: ruleset-aware groups, leveling cohorts, profession campsites, Legacy planning, guild recruitment, and beta-to-launch preparation. 続きを読む →

次のプラグインを見つけよう

YourBotのマーケットプレイスで、サーバーに必要な機能だけを追加しましょう。

マーケットプレイスを見る →