How to Build and Run a Project Zomboid Discord Community With YourBot

server setup
How to Build and Run a Project Zomboid Discord Community With YourBot

A Project Zomboid Discord should make one persistent world understandable: how to join it, which build and mods it uses, what its rules allow, and where survivors can ask for help. Use YourBot to organize that information, private applications, supply crews, scheduled sessions, temporary voice, and reviewed world changes. Keep actual game-server administration in the hands of authorized hosts.

The common failure is treating “Project Zomboid multiplayer” as one interchangeable experience. Stable, Unstable, and legacy branches can differ; two servers can use different mods, access policies, and survival rules. A Discord role does not fix a version mismatch, and a crew signup does not reserve space on a busy server.

This guide builds Last Light County, a fictional community of about 240 members. It operates a Steam-based, whitelisted PvE world with agreed roleplay boundaries and a small volunteer host team. Its crew sizes, project rules, and event capacities are community choices, not universal Project Zomboid limits.

Start With the Right Project Zomboid Community Model

Publish the exact world and compatibility route

The official Steam page describes persistent player-run multiplayer and local four-player split-screen. Those are different arrangements. A local co-op figure does not establish the capacity of a persistent online server or the size of every expedition.

Last Light County's joining guide identifies its server label, approved client branch/build, mod collection and required settings, access process, region, and current maintenance status. Players need that complete route before a scheduled session. A list of mod names without versions or an authoritative source can leave everyone guessing which setup is current.

Do not assume storefront compatibility. This example uses Steam clients and a matching server. A member using another storefront should check that storefront's current instructions and the host's supported configuration; the GOG product page explicitly warns about its multiplayer crossplay limits. Do not promise one shared pool merely because both copies have the same game name.

Keep Stable, Unstable, and legacy history distinct

The developer's 42.21 Stable announcement, dated September 28, 2026, confirms that update moving from Unstable to Stable. Do not repeat old instructions that describe all Build 42 multiplayer as an early stress test. Equally, do not direct members to a test branch merely because an older support answer mentioned it.

Publish what the actual community server uses, with its last review date. A host choosing a legacy branch or testing a new build should say so explicitly and maintain separate instructions. Compatibility information becomes stale quickly, so the permanent guide should point to the authoritative current record rather than embed an unchanging version number everywhere.

The developer's release notes also explain that some issues remain under development. Avoid claiming that a named update eliminates every multiplayer problem. When a new patch arrives, test the community's actual setup before changing the main world.

Distinguish server population from a useful crew

A four-person supply expedition is a manageable community target. It is not a universal matchmaking party cap. A larger settlement work session may use six volunteers, while the server's overall concurrent capacity remains whatever the host has configured and verified.

Count playing mentors and drivers as players. A mentor inside the world consumes real server capacity even if they are “only helping.” Event attendance, expedition size, Discord voice limits, and the server's population limit should be stated separately.

Avoid fixed tank/healer/damage rosters. Useful matching context includes the world, ruleset, progression expectations, transport plan, intended task, risk agreement, and duration. Skills or professions can be helpful interests, but Discord labels do not verify a character's abilities.

Make survival and privacy rules part of joining

Explain PvE/PvP policy, safehouse expectations, shared storage, vehicle use, character-death rules, roleplay boundaries, and how staff handle world changes. These are the community's chosen rules and settings. Do not imply that every public Project Zomboid server follows them.

Keep private settlement locations, access details, and incident evidence out of public showcases. A convenient screenshot can reveal information the group intended to keep restricted. Hosting passwords, remote-console credentials, account tokens, and recovery material belong outside Discord and YourBot entirely.

The Community We Will Build

Last Light County is an English-speaking North American community with a persistent Europe-friendly weekend session as well. Its main world is a reviewed Steam configuration, and newcomers complete the published access process before joining crew listings. Public Discord membership is broader than the in-world whitelist.

Weekly activities include a newcomer orientation, a supply expedition, a settlement work shift, and an optional roleplay session. Staff publish a dated maintenance plan and keep restart decisions separate from world resets. Builders and explorers can participate without pretending every player must become a server administrator.

YourBot's role in the community

Service Community use
Welcome Explain the current joining path and offer useful interests.
Sentinel Handle Discord scams, malicious links, harassment, and exposed secrets.
Tickets Route whitelist applications, connection help, and private reports.
Group Finder Assemble compatible survivor crews with realistic goals.
Beacon Events Plan orientations, work shifts, and community sessions.
Join-to-Create Voice Give active crews temporary coordination rooms.
Announcements Publish reviewed maintenance, restart, and reset notices.
Social Feeds Follow verified publisher Steam announcements.
Analytics Assess Discord participation and the joining experience.
Giveaways Run occasional optional community celebrations.

1. Create the Foundation With Start Your Server

Have the Discord owner open Start Your Server. Describe the actual world and its access rules before naming channels. The useful design is a small, understandable set of entry instructions, survivor coordination, private help, and staff review spaces.

Separate server hosting authority from Discord authority. A helpful survivor does not need dashboard management access, and a moderator does not automatically need game-host credentials. YourBot dashboard access is its own layer; the bot also needs appropriate Discord channel and role permissions and a position above ordinary roles it grants.

Copy-ready community brief

Build a compact Discord foundation for Last Light County, a fictional
240-member Project Zomboid survivor community. Our main world is a
whitelisted Steam-based PvE server with agreed roleplay boundaries.
Exact approved build/branch/mod requirements live in one joining guide.
Do not invent universal storefront crossplay or online party limits.

Preserve existing structure on this first pass. Keep deletion off.
Provide public rules/joining instructions, one survivor LFG forum,
newcomer help, settlement projects, optional roleplay coordination,
events, official news, private support, and restricted staff review.
Avoid channels for every town, profession, mod, item, or temporary camp.

Welcome gives limited Member access after Discord verification. Offer
Builder, Explorer, Mechanic Interest, New Survivor, Roleplay Interest,
Event Notices, and Maintenance Notices. Staff, Moderator, Server Steward,
and reviewed World Access are never self-selected authority roles.

Use Welcome, Sentinel, Tickets, Group Finder, Beacon Events,
Join-to-Create Voice, Announcements, Social Feeds, Analytics, Giveaways.
Configure supported objects and report unfinished items. Announcement
schedules and Social Feed subscriptions need manual finishing.

Group templates identify world label, exact current compatibility
route, ruleset, task, transport, risk, current players, voice, and
duration. Four-person expeditions are community targets, not game caps.
Playing mentors/drivers count. Larger events depend on host-confirmed
server capacity; Discord signups do not reserve a server slot.

Keep reports, private settlement details, and change reviews restricted.
Never request game passwords, Steam Guard codes, RCON/hosting secrets,
account tokens, recovery information, or unredacted logs containing them.
Do not whitelist, ban in-game, restart/wipe/restore the world, install
mods, import game inventory, or execute any proposed plugin.
Show Channels, Roles, Services and access for review before applying.

A compact channel plan

ENTRY
  welcome-and-rules
  how-to-join
  server-notices
COUNTY
  survivor-chat
  newcomer-help
  supply-crews [forum]
  settlement-projects
  events
  official-news
  roleplay [opt-in]
VOICE
  Join to Create: Expedition
  Join to Create: Settlement
SUPPORT
  open-a-ticket
STAFF [restricted]
  moderation
  world-change-review

Review before applying

Review Channels, Roles, and Services, then use the role-perspective preview. A newcomer needs public access instructions before they have World Access. A Member should be able to ask for help without seeing another settlement's private notes or a moderator report.

Read the safety check and build report, then inspect the actual saved workflows. An enabled service is not proof that every requested object exists. Finish Announcements schedules and Social Feed subscriptions manually in their dashboards.

Use the after-build documentation to understand snapshots and limited undo. Added channels and roles remain after undo, and deleted message history cannot return. Preserve the first build, test with ordinary members, and make small reviewed changes afterward.

2. Welcome: Give Every Survivor One Current Joining Guide

Configure Welcome around one reliable path: read the rules, complete Discord verification, find the authoritative compatibility guide, and submit the appropriate access request. Verification grants limited Member access; it does not prove game ownership, install a mod collection, or add a character to the server.

Offer Builder, Explorer, Mechanic Interest, New Survivor, Roleplay Interest, and notice preferences. These are interests rather than verified skill levels. Keep staff, stewardship, and reviewed world access separate from self-service menus.

A greeting can say: “Welcome to Last Light County. Read how-to-join for our current world, branch, mods, and access route. Do not use an old invite or pinned mod list from another server. Ask for help if anything differs.” Keep the instructions useful when DMs are blocked.

Make the difference between Discord membership and world access explicit. A newcomer should still find learning resources while an application is being reviewed. Do not expose private settlement information merely to make the server feel welcoming.

Test: Join as a newcomer, verify, choose Explorer and Maintenance Notices, and find the application route. Confirm that staff spaces and restricted world details remain inaccessible until the correct review.

3. Sentinel: Protect the Community From Scams and Public Disputes

Use Sentinel for fake mod downloads, account phishing, malicious links, harassment, impersonation, spam, and attempts to expose private information. Explain which distribution sources staff approve and where suspicious alternatives should be reported.

Start new aggressive filters in Testing. Project Zomboid discussions can include code snippets, long mod names, error text, and unusual filenames. Review false positives before enabling actions; a filter that hides every useful diagnostic will make connection help worse.

Give members a private route for griefing or rule disputes. Staff should distinguish an accident, a misunderstood world rule, and deliberate harmful behavior. Do not invite the whole Discord to judge a player from a cropped screenshot or a single message.

Discord moderation is not game enforcement. A Sentinel action does not change the server ban list, revoke safehouse access, restore lost inventory, or roll back a save. An authorized host reviews any game-side action separately, with the minimum necessary information.

If a secret is accidentally posted, remove its public exposure and have its owner follow the appropriate rotation process outside Discord. Do not copy the secret into a case summary simply to preserve evidence.

Test: Trigger a harmless staff-only rule, inspect the case and appeal route, and verify that a normal redacted compatibility question is still allowed through.

4. Tickets: Separate Whitelist, Connection Help, and Reports

Create three Tickets paths. World Access asks for the intended server, acknowledgement of its rules, availability, and only the nonsecret game identifier the authorized host actually needs. Connection and Mod Help asks for branch/build, approved collection status, approximate time, and a minimal redacted error. Private Report routes incidents to moderators.

Never collect passwords, Steam Guard codes, remote-console credentials, hosting access, recovery codes, or session tokens. Do not ask someone to upload an entire log before considering what it contains. A short error excerpt is often enough to distinguish an outdated mod, wrong branch, or unavailable host.

A reviewed application can change Discord access where configured. The actual game-side whitelist or access action remains the host's responsibility. Tell the applicant who handles it and how they will know the process is finished; do not close the ticket with an unsupported “you are now in-game.”

Keep support helpers and report reviewers separate where privacy requires it. A settlement volunteer should not automatically read conduct reports or another group's private location evidence.

Test: Submit one request of each type. Verify reviewer access, the redaction guidance, and a closing message that accurately states which Discord and game-side steps are complete.

5. Group Finder: Build Compatible Crews, Not Imaginary Party Limits

Project Zomboid is not in the automatic game-detection keyword list inspected for this guide, so create explicit templates manually. Its Social Feeds catalog entry is a separate capability. Use Group Finder to identify the world and task before collecting names.

Create the first template

Template Name: County newcomer supply run
Game: Project Zomboid
Default Party Size: 4
Default Expiry: 2 hours
Description: One playing guide and up to three new survivors on the
approved County world. Four is our expedition target, not a game cap.
Confirm current branch/build/mod route, world access, transport,
ruleset, task, voice preference, and duration before departure.

Use neutral player seats and describe practical responsibilities. A driver, lookout, and two learners can be useful, but do not invent a game-enforced class composition. The leader checks that the actual characters and equipment suit the plan.

Additional template Target size Required context
Quiet supply expedition 4 World, route alias, risk policy, vehicle plan, duration.
Vehicle recovery 3 Authorized vehicle, agreed tools, return plan, rules.
Settlement work shift 6 Approved project, shared-storage policy, material priorities.
New survivor orientation 4 Current joining route, playing guide, spoiler/help scope.
Roleplay scene 4 Agreed boundaries, location access, consent, expected time.
Compatibility check 2 Separate approved test environment, exact proposed build/mods.

All targets are fictional community choices subject to actual server capacity and access. Do not advertise the private location of a settlement in a public listing; use an agreed alias and reveal details only to authorized participants.

Example live listing

County newcomer supply run
World: Last Light main PvE / Steam configuration
Compatibility: current approved build/branch/mods linked in how-to-join
Crew: 2/4 including the guide; two survivor places remain
Access: completed world review; host confirms actual entry separately
Goal: short supply route and return to agreed public drop-off
Transport: one approved vehicle; driver counted in crew
Rules: shared resources follow County policy; no private base locations
Voice: listening welcome; agreed stop/return callouts
Duration: about 75 minutes; no promise of replacing lost equipment

Joining the listing neither creates a game party nor reserves a server slot. Have everyone confirm they can enter before the crew leaves. If the host is unavailable or the server is full, communicate that plainly rather than treating the Discord signup as proof of admission.

Test: Fill the four-person crew, count the guide and driver, and check an additional member's waiting-list experience. Confirm that a person without world access sees the correct next step.

6. Beacon Events: Plan Work Shifts Around the Actual World

Use Beacon Events for an orientation or settlement shift people need to schedule. Last Light County's fictional “Saturday Settlement Shift” starts at 18:00 America/New_York for two hours. The host confirms capacity and access before setting twelve playing places and a waiting list.

Twelve is an operating choice for that world and event, not a universal Project Zomboid cap. Playing guides count among those places. Break the activity into understandable work assignments without implying the bot controls construction, storage, or character skills.

State the approved project, required preparation, privacy rules, host, transport expectations, and voice plan. A member should know whether joining halfway through is helpful or disruptive. A nonplaying coordinator remains separate from the playing attendance count.

Beacon RSVP does not whitelist a character, reserve capacity, teleport a player, grant supplies, or protect a settlement. The host still handles game-side access. Avoid relying on unverified event-created voice lifecycle behavior for a long shift; use an appropriate established or Join-to-Create room.

Test: Add a playing guide, several workers, and a waitlisted member. Check time zone, reminders, access instructions, and how the host communicates a genuine open place.

7. Join-to-Create Voice: Keep Expedition Rooms Temporary

Create Expedition and Settlement lobbies through Join-to-Create Voice. Start with four-person and six-person defaults for the fictional activities, reviewed creator ownership and transfer, and empty-room cleanup. These limits organize Discord conversation; they do not configure the game server.

Explain supported room controls and staff access. A crew can use a short public route alias as a room name without publishing private coordinates. Lock or hide a room when the activity's privacy needs justify it, and check that ownership transfer preserves the intended access.

Respect the server's game communication and roleplay rules. If proximity or in-character communication matters, state when Discord is for planning or debriefing rather than using it to bypass agreed play boundaries. Listen-only participation should remain possible when the activity allows it.

Do not create permanent voice rooms for every settlement. Keep a persistent host or staff room only when continuity serves a clear purpose. Group Finder-created voice has its own lifecycle; choose one room workflow per session instead of assuming both services manage it.

Test: Create, rename, lock, and transfer a crew room, then leave it empty. Verify cleanup, ordinary-member privacy, moderator access, and that no unrelated persistent room is removed.

8. Announcements: Distinguish Restarts, Updates, and Resets

Finish Announcements schedules manually. Use one weekly community plan and individual dated notices for maintenance or approved world changes. Save the actual time zone and review the end date of recurring posts.

A restart is not a world wipe. An update is not automatically a reset. State exactly what the authorized host intends to do, which world is affected, what players should do beforehand, and when the next status update will appear. If the effect on characters or structures is uncertain, resolve that before promising preservation.

Use opt-in Maintenance Notices and Event Notices. Beacon should handle its own session reminders. A server-news message can link the reviewed change decision without publishing private infrastructure details or creating multiple conflicting copies of the joining guide.

Preview mentions and destinations. Immediate-send controls post for real. Keep rehearsals restricted, and do not use a recurring “server updated” notice when staff have not confirmed the actual world is on the new build.

Test: Preview a maintenance notice and ask another staff member to explain what will change. If they cannot distinguish restart from reset or identify the time zone, revise it before scheduling.

9. Social Feeds: Follow Publisher News Without Updating the World

The inspected catalog includes Project Zomboid, key project_zomboid, using Steam news App ID 108600 in the Survival category. Confirm that identity and manually add the subscription through Social Feeds. Keep it in official-news rather than mixing it with local maintenance decisions.

The inspected Steam source requests publisher community announcements and declares a 900-second default interval. It is not a guarantee of immediate or every-post delivery. Support pages, forum details, and other official channels may need staff follow-up. The first check establishes a baseline rather than dumping all old posts.

Read the source date and branch carefully. An Unstable announcement should not be summarized as “the main County world has updated.” The September 28 Stable note is a useful example of why a staged release and the community's own deployment are separate facts.

Preview the source before public posting, and remember that a test sends a real message. Staff review whether a patch affects the approved mod collection or joining guide. News delivery does not install mods, back up a save, restart a host, or approve a reset.

Test: Preview a publisher item, verify AppID and branch wording, and send a restricted test. Confirm that members can distinguish official release news from the host's separate change notice.

10. Analytics: Measure Community Use, Not Survivor Performance

Use Analytics to assess newcomer return visits, LFG activity, event attendance patterns, and temporary voice use. A useful question is whether the joining guide reduces repeated confusion, not which survivor has the best character.

Discord activity does not establish kills, survival days, injuries, inventory, safehouse membership, character skills, settlement output, or actual world population. A voice session is not proof that someone entered the server or survived the expedition. Avoid treating optional presence tracking as game telemetry.

Exclude private reports and sensitive staff areas where appropriate. Use feedback to improve the process without building a surveillance log of personal mistakes. A quiet member maintaining a shared project may be well served by the community even if they rarely post.

Compare similar periods and ask hosts for minimal voluntary context. If newcomer questions repeat, improve the authoritative instructions before adding more channels. If a work shift attracts the wrong audience, clarify its purpose and access requirements before changing its capacity.

Test: Explain one sample metric without inferring a game outcome. Confirm that public views or configured exports do not reveal private tickets or settlement records.

11. Giveaways: Celebrate Without Promising Game-Side Restoration

Use Giveaways for optional community milestones. A legitimate, region-compatible store gift card can be appropriate after the organizer checks its platform and redemption terms. State the actual prize, eligibility, claim deadline, and fallback before entry.

Do not offer automatic restored characters, spawned items, protected safehouses, server privileges, or promises that a winner's game loss will be reversed. YourBot manages the Discord drawing and supported claim workflow; it does not edit the world or grant game entitlements.

Keep entry separate from whitelist review and staff selection. A winner should not bypass access rules or gain ownership of a community project. Never request account credentials, recovery information, or host secrets to deliver a prize.

Practice in a restricted staff space with a harmless sample prize. Read the exact notification and claim route, including what happens if a code is incompatible or the winner does not respond. A drawing is optional community activity, not a substitute for useful help and fair rules.

Test: Complete a staff-only rehearsal from entry through claim and verify eligibility, permissions, winner wording, and the announced unclaimed-prize process.

Maintain One Compatibility Record and a Tested Change Process

Give one steward ownership of the main compatibility record. It should identify the world, branch/build, approved mod source and requirements, date checked, and any temporary issue. Link it from Welcome, support answers, and event descriptions instead of maintaining several inconsistent lists.

When a change is proposed, test the actual combination away from the main world where practical. Record which environment was used, who performed the check, what was observed, and what remains uncertain. A mod working alone does not prove it works with the full community collection.

Keep backup and rollback responsibilities explicit. Record a nonsecret confirmation that the authorized host checked the process; do not put credentials or whole hosting exports into Discord. YourBot can preserve a decision record but cannot make an untested recovery plan reliable.

After approval, update the authoritative guide and publish a dated notice. If the change is postponed, make that visible. Avoid asking every player to troubleshoot independently against a collection the staff have not yet agreed to support.

Define Settlement Responsibilities Before Resources Disappear

Shared storage needs a community policy: which resources are communal, which require permission, and how project owners request materials. A simple public label is often enough for coordination. Private locations and sensitive inventories should remain restricted rather than being copied into every signup.

Explain vehicle borrowing, return expectations, and who handles damage reports. These are rules for people, not claims that Discord roles enforce in-game ownership. A Mechanic Interest role does not prove the current character has the necessary skill or equipment for a recovery.

Handle loss and mistakes predictably. A survivor death, missing resource, or failed trip should not automatically become an accusation. Give members a way to report issues, state the restoration policy honestly, and keep authorized host decisions separate from general discussion.

Use project discussions for constructive planning. If a work shift needs more volunteers, create an appropriate listing or event rather than repeatedly pinging everyone or marking the project complete because six people signed up.

Make World Changes Understandable to Returning Players

Returning members need a short answer to what changed since they last played. Keep a dated change summary covering compatibility, rules, and any approved reset decision. Do not assume someone who has been away followed every patch feed or staff discussion.

Separate restart, configuration change, mod revision, rollback, and reset in the record. Describe their actual intended effect on the community world, with uncertainty visible. A new developer patch does not automatically require all of those actions.

If staff operate a test world, give it a distinct label and joining route. Never let an experimental event masquerade as the persistent main world. Ask participants to acknowledge the test's purpose and risks without treating their attendance as permission for unrelated changes.

Add a County Change and Settlement Register Only When You Need It

Launch with the built-ins first. If approved settlement work and world decisions become hard to trace across chat, check the Marketplace for a maintained record-management solution before using Plugin Builder.

The proposed County Change and Settlement Register stores human-maintained projects and decisions. It does not replace Tickets for reports, Group Finder for crews, Beacon for attendance, or Announcements for scheduled notices. Its central question is what was agreed, for which world, by whom, and whether it is still current.

Copy-ready Plugin Builder specification

Create a proposed private plugin named County Change and Settlement
Register. Store manually reviewed community projects and world-change
decisions. Version 1 uses no external network and does not administer
Project Zomboid, read host files, or connect through RCON.

Roles: Register Steward controls configuration/retention. Server Steward
reviews world changes. Project Owner edits assigned settlement work.
Reviewer approves public summaries. Member reads approved public
records and submits proposals. Conduct reports remain in Tickets.

Fields: immutable record ID, Discord server ID, record type (project,
rule change, compatibility revision, reset decision), world label,
public location alias, owner, summary, materials requested, branch/build
where relevant, proposed effective date, evidence/check date, private
notes, visibility, created/updated/review dates, revision, status,
superseded-record link. Do not store passwords, tokens, exact private
base coordinates, host connection secrets, or full inventory dumps.

States: proposal -> staff review -> approved -> active -> superseded.
Approval requires an authorized reviewer, dated evidence, public
summary, and an explicit description of the decision's scope.
Changing a world-reset decision requires a new revision/review.
Mark stale material requests and compatibility records for review.
Do not infer completion from an event signup or a chat reaction.

Public destination: approved current summaries and nonsecret projects.
Private destination: restricted review dashboard and sensitive notes.
Suggested commands for this NEW plugin only: /county-record propose,
/county-record view, /county-record revise, /county-record review,
/county-record supersede, /county-record export.
Dashboard filters: world, type, owner, visibility, status, effective
date, review age, missing evidence, superseded records.

Authorize every operation server-side. Scope all records/queries by
Discord server and assigned project/team access. A public summary must
never reveal private notes through embeds, autocomplete, search,
errors, logs, direct-record access, or exports. Revoked project owners
lose restricted reads/writes/exports immediately. Do not rely on hidden
buttons or channel permissions alone.

Audit actor, server, record, action, revision, approvals, visibility
changes, exports, and time. Use revision checks to reject stale edits.
Escape untrusted text/mentions. Define retention, correction, and
steward deletion controls before operational installation.

Non-capabilities: no whitelist/ban changes, restart/wipe/restore,
backup execution, mod installation, inventory/character/skill lookup,
safehouse ownership checks, resource transfer, map coordinate import,
game invites, event scheduling, tickets, or cross-server sharing.

Acceptance: member reads public project but not restricted notes;
another server cannot retrieve it by ID; revoked owner cannot export;
stale edit fails; superseded decision links to replacement; approving
a record does not send a notice or execute a world change; confidential
location data never appears in a public field or error.

Review, test, and continue through the SDK

Inspect the plan, source, manifest, storage design, and requested capabilities. Reject unnecessary network or host-control access. Use the Plugin Builder review and validator, and check whether a sandbox test actually ran. Static validation does not prove authorization or recovery behavior.

Test a steward, project owner, reviewer, member, revoked owner, and unrelated server with harmless records. Try direct IDs, searches, exports, visibility changes, stale revisions, and superseded decisions. A hidden private note is insufficient if a direct request still returns it.

Continue in Visual Studio Code using current SDK testing guidance when needed. Review the run/install routes and their requirements; a temporary Dev Bot install is not a permanent operational deployment. Use the Dev Portal and normal review process for distribution. Marketplace publication is optional.

Run a Complete First-Week Member Journey

Scenario Successful result
New survivor arrives Public entry guide works without DMs or world access.
Player uses the wrong branch Private help identifies the mismatch using redacted information.
World application is accepted Discord access and separate host whitelist action are explained.
Four-person expedition forms Playing guide and driver are counted inside the chosen target.
Server has no available capacity Host communicates the limit without treating RSVP as reservation.
Maintenance is announced Members can distinguish restart, update, and reset.
Voice owner leaves Ownership and empty-room cleanup work as intended.
Project request becomes stale Owner reviews or supersedes it without inventing completion.
Project owner's access is revoked Restricted records and exports stop being accessible.

Use the results to simplify instructions and remove unused spaces. Fix a confusing joining route before adding more automation. The community should be easier to rejoin after a week away, not harder to understand with every update.

Frequently Asked Questions

Is a four-person crew the online server limit?

No. Four is this guide's expedition target. Persistent-server capacity depends on the actual host/configuration, while local split-screen is a separate mode with its own stated limit.

Should every player select Unstable for Build 42 multiplayer?

No. The developer confirmed 42.21 Stable in September 2026. Follow the actual community world's current branch/build; do not repeat old test-branch instructions as universal requirements.

Can Steam and other storefront copies always join together?

Do not assume it. This example uses Steam. Check current storefront documentation and the host's supported setup; GOG's product page explicitly warns about its multiplayer crossplay limits.

Can YourBot whitelist people or restore a lost character?

The workflows here do neither. Discord applications, records, and signups coordinate people. Authorized game-side host actions remain separate.

Does Group Finder detect Project Zomboid automatically?

It was absent from the inspected automatic keyword list. Create explicit activity templates; a Social Feeds catalog entry does not establish game detection.

Which news source should we configure?

The inspected Project Zomboid catalog entry uses publisher Steam announcements for App ID 108600. Verify and preview the actual subscription. News delivery does not update the community world.

Is the proposed register required to launch?

No. Begin with one authoritative joining guide, private help, clear crews, scheduled events, and reviewed notices. Add the register when persistent projects and decisions need controlled history.

Give Last Light County a World People Can Rejoin

A Project Zomboid community depends on continuity: compatible builds and mods, understandable survival rules, respectful shared resources, private support, and dated decisions about the world. Start Your Server can establish that Discord foundation, and the ten built-ins can run its daily community workflows.

Leave server configuration, saves, whitelists, character state, and actual survival inside their authorized game-side processes. When the decision history becomes difficult to maintain, a reviewed Plugin Builder project can preserve the record without pretending to operate the county.

← Back to the blog

Find your next plugin

Browse the YourBot marketplace and add exactly the features your server needs.

Browse the marketplace →