An Enshrouded Discord works best as a home for compatible worlds, shared progression, and creative projects. Put the world, platform, spoiler expectations, and session goal in front of players before they join an expedition. YourBot can organize the Discord side: newcomers, exploration crews, building nights, temporary voice, official updates, and a durable record of community projects.
The important compatibility change is the full release. Enshrouded 1.0 launched on October 15, 2026. Keen Games' launch information distinguishes up to 16 players on PC from eight on PlayStation 5, while the launch FAQ says cross-platform play was unavailable at launch. A generic sixteen-seat listing shared indiscriminately across platforms would therefore mislead members.
This guide follows Emberlight Fellowship, a fictional 240-member community with a primary PC progression world and a separately hosted PS5 group. The community includes returning players, first-time Flameborn, builders, and explorers. Its world names, policies, events, and member counts are illustrative. The goal is a Discord that helps those people cooperate without implying that YourBot controls their game worlds.
Start With the Right Enshrouded Community Model
Name the world before naming the activity
A community can have many members while a particular world has a much smaller simultaneous population. Emberlight labels its primary PC world Hearth-PC and its console world Lantern-PS5. These labels appear in every group listing, event, support request, and project record. They are convenient community identifiers, not game-generated integrations.
Specify the host's region, usual availability, access process, and current world rules in one maintained joining guide. A locally hosted world depends on its host being available; a dedicated-server arrangement has different operational responsibilities. Link the official multiplayer and server-hosting knowledge base for technical instructions instead of turning public Discord messages into a repository of hosting credentials.
Separate character readiness from community membership
Enshrouded's FAQ explains that characters can move between worlds with equipment, inventory, and character progression, while important world-dependent unlocks are separate. An experienced visitor can therefore change a beginner world's experience even when everyone joins successfully. Emberlight asks visitors to respect an agreed progression and imported-equipment policy.
Use a self-reported New Flameborn interest role and an optional Returning Explorer role. Neither should unlock staff controls or certify a character's readiness. A player who enjoys building can belong fully without joining the latest combat expedition. Record the actual session's prerequisites in its listing rather than maintaining a brittle ladder of permanent gear-level roles.
Treat platform compatibility and spoilers as separate decisions
Keep shared screenshots, building discussion, and beginner advice together where they work across platforms. Use platform-specific listing fields and world labels for joining play. Crossplay and cross-save are different features; a role saying PS5 makes no promise about transferring saves or entering the PC world.
Create a spoiler-safe public help channel and one opt-in discoveries area. Members should be able to find a compatible group without reading an endgame boss name in the channel title. When a host changes the progression boundary, update the joining guide and open listings together. Do not let yesterday's event description become today's accidental spoiler policy.
The Community We Will Build
Emberlight runs a weekly newcomer exploration, an agreed progression evening, and a weekend settlement workshop. Members choose the activities they want; staff approve actual world access separately. The first goal is to help a newcomer reach one suitable session within a week. A second goal is to keep shared projects understandable when their original organizer is offline.
Keep the server compact. A single well-used LFG forum can cover gathering, exploration, and building when each listing carries its world and purpose. A channel for every biome, weapon, and crafting station makes people choose where to post before they know what the community calls anything.
YourBot's role in the community
| Service | Community use |
|---|---|
| Welcome | Explain the two worlds and offer activity and spoiler interests. |
| Sentinel | Limit impersonation, unsafe downloads, spam, and harassment. |
| Tickets | Route joining problems, private reports, and host requests. |
| Group Finder | Fill compatible exploration and building crews. |
| Beacon Events | Organize workshops and progression evenings. |
| Join-to-Create Voice | Give crews temporary conversation rooms. |
| Announcements | Publish community plans and dated maintenance notices. |
| Social Feeds | Follow the verified Steam announcement source. |
| Analytics | Review newcomer participation and Discord channel health. |
| Giveaways | Run optional, legitimate community drawings. |
1. Create the Foundation With Start Your Server
The Discord server owner should begin with Start Your Server. Describe the community's actual worlds and habits, then review its proposed structure. Give the bot the permissions required for the actions you intend, including channel creation and ordinary role assignment where applicable, with its role above roles it grants. Administrator is not a substitute for understanding that hierarchy.
An existing server deserves a smaller first pass. Preserve established conversations, identify redundant channels for later human review, and keep deletions off. Ask the owner to review integrations that another bot already manages so two systems do not issue conflicting welcome roles or duplicate reminders.
Copy-ready community brief
Design Emberlight Fellowship, a fictional 240-member Enshrouded Discord.
Primary world: Hearth-PC, PC co-op; separate Lantern-PS5 group.
Do not imply cross-platform joining. Respect PC16 / PS5 eight-player ceilings.
Use compact channels for entry, world guides, beginner help, LFG, events,
building projects, opt-in discoveries, news, private support, and staff.
Offer Member after verification, Explorer, Builder, New Flameborn,
Mentor Interest, PC, PS5, Discoveries Access, and optional event/news pings.
Staff roles are owner-assigned. Mentor Interest grants no authority.
Explain world rules, imported equipment, spoilers, and access applications.
Plan Welcome, Sentinel, Tickets, Group Finder, Beacon Events,
Join-to-Create Voice, Announcements, Social Feeds, Analytics, Giveaways.
Use activity-sized temporary voice rooms and separate platform/world labels.
Keep tickets and staff notes private; never request hosting or account secrets.
Preserve existing channels, roles, and conversations; deletions off.
Review Channels, Roles, Services and report manual finishing steps.
Do not claim to create game worlds, reserve seats, read inventory,
change progression, or configure a host. Schedules and feeds are finished manually.
A compact channel plan
ENTRY: #start-here #rules-and-worlds #choose-interests
FELLOWSHIP: #campfire #beginner-help #build-showcase
PLAY: #lfg #events #project-board #discoveries [opt-in]
UPDATES: #community-notices #official-news
SUPPORT: #open-a-ticket [private ticket area]
VOICE: Join Exploration Join Workshop [temporary rooms]
STAFF: #staff-room #moderation-log #host-handover [private]
Review before applying
Review Channels, Roles, and Services independently. In a role-perspective preview, check what an unverified visitor, ordinary Member, discoveries subscriber, and moderator can see. The world guide must remain reachable before verification; a private ticket must not become visible through a permissive parent category.
After applying the reviewed design, read the actual Build report, follow flagged finishing tasks, and open each service. Announcement schedules and Social Feed subscriptions require manual finishing steps. A requested workshop does not prove an event or every detailed setting was created.
The after-build guide describes a pre-build snapshot and undo. Newly added channels and roles stay, and restored deleted channels return empty. Undo cannot recover deleted Discord messages. Save the snapshot, keep structural changes modest, and verify the result before inviting members into the new flow.
Test: Preview the server as an ordinary Member with no discoveries role. They should see the joining instructions, create a compatible listing, and open a ticket, while staff handover notes and spoiler discussion remain hidden.
2. Welcome: Make the First World Choice Understandable
Configure Welcome with one clear public entry path. Use the supported verification method that fits your moderation needs, then grant a limited Member role. Explain that verification checks a Discord interaction; staff still handle world access and any host-side membership decision.
Offer Explorer, Builder, New Flameborn, Mentor Interest, platform interests, and separate notification choices. Leave staff, host, and trusted-world-access roles out of self-selection. Someone choosing Mentor Interest has volunteered to help, not passed a safety review or acquired permission to change a shared base.
The greeting can say: “Welcome to Emberlight. Read the world guide, choose PC or PS5 for joining help, and tell us whether you want your first exploration or your first build project. Keep discoveries in the opt-in area.” Include a link to a short first-session checklist rather than a wall of advanced terminology.
DM greetings are useful but should not carry the only instructions, since members can block DMs. Invite newcomers to introduce a goal without disclosing age, location, or account details. A buddy can answer where to begin; that relationship does not require sharing a game login.
Test: Join using a nonstaff account with DMs blocked, complete verification, choose Builder and PS5, then remove the news-ping role. The public entry path should still work, and removing pings should not remove ordinary membership.
3. Sentinel: Protect Builders and Returning Players
Use Sentinel to address Discord risks around survival-game communities: fake host messages, malicious “performance fix” downloads, credential requests, repeated recruitment spam, and harassment over shared-world decisions. Start aggressive new filters in Testing and inspect their proposed actions before enabling enforcement.
Allow members to discuss legitimate server problems and building disagreements. A message saying a patch damaged a project is not automatically abuse. Staff should distinguish frustration from targeted harassment, and move evidence about a suspected griefer into a private report rather than encouraging public accusations.
Keep official links in a maintained guide and discourage unsolicited executable files in help channels. Attachment rules do not establish that a file is safe, and a moderation action does not verify the contents of an image. Moderators should explain consequential actions using the service's case workflow and keep appeals reachable.
Discord moderation is not game enforcement. A Discord timeout does not remove someone from a world, change server permissions, or reverse damage. Hosts need a separate authorized process for game-side access and backups.
Test: Use harmless sample messages in a staff test channel: a fake login request, repeated spam, and an ordinary criticism of a build. Confirm that the first two are flagged under the intended rules and that normal disagreement is not punished.
4. Tickets: Route World Access and Private Problems
Build three Tickets paths: Joining help, Private member report, and World or project request. Joining help should ask for platform, world label, game version, approximate error time, and a redacted error description. Staff do not need the member's password, authentication code, save archive, or the host's remote-access credentials.
Route technical joining questions to host helpers and behavior reports to moderators. A request to change a shared landmark belongs with project stewards; an accusation about a member should not be sent to every builder. Give each team only the ticket access it needs and name a responsible reviewer so cases do not sit in a general queue.
An approved joining application can grant a Discord access role where configured. The authorized host still performs any game-side invitation or access change. Explain that distinction in the closing reply so applicants do not repeatedly attempt to join a world that has not been prepared for them.
Close resolved tickets with a short useful outcome and follow your community's retention policy. A transcript can help staff understand a recurring connection problem, but it is not an unlimited archive or a reason to keep unnecessary personal data.
Test: Open one joining ticket and one private report as a Member. Confirm that only the intended staff team sees each, a builder without staff status sees neither, and accepting the request does not claim to have changed game access.
5. Group Finder: Match World, Progression, and Purpose
Set up Group Finder in the LFG area and configure explicit templates. Enshrouded is absent from the automatic setup-detection list in the current read-only repository inspection; a manually named game field is therefore the reliable approach. Detection, a news catalog entry, and an actual game integration are separate mechanisms.
Create the first template
Template Name: Hearth-PC newcomer exploration
Game: Enshrouded
Default Party Size: 4 total, including the playing mentor
Default Expiry: 2 hours
Description: PC Hearth world, spoiler-light exploration, patient pace.
Required context: current world/version, region, meeting point,
progression boundary, imported-equipment policy, voice, session length.
Four is Emberlight's chosen teaching-crew size, not the PC world's maximum. A PC world may accommodate up to sixteen simultaneous players, and the PS5 limit is eight. Account for people already using the destination world. Two four-person listings do not reserve eight seats or prevent an unrelated builder from joining.
Avoid fixed Tank/Healer/DPS slots. Enshrouded supports flexible character development; this community needs useful loadout notes and agreed expectations rather than mandatory MMO composition. A mentor who plays occupies a real seat. A nonplaying adviser in Discord should be described separately and should never make a full game roster appear to have an extra place.
| Additional template | Target size | Required context |
|---|---|---|
| Lantern-PS5 first expedition | 4 chosen crew target | PS5 world, host availability, progress, remaining world space |
| Hearth progression expedition | 6 chosen crew target | PC world, agreed unlock boundary, equipment, spoilers |
| Settlement workshop | 6 chosen crew target | World/platform, approved project, materials policy |
| Gathering circuit | 3 chosen crew target | World, resource goal, storage destination, duration |
| Adventure playtest | 4 chosen crew target | Platform/world, creator instructions, spoiler and feedback scope |
A worked live listing
Title: Hearth-PC — first exploration, patient pace
Game/world: Enshrouded / Hearth-PC / current community version
Region/language: North America East / English
Crew: 2/4, including one playing mentor; two learner places open
Goal: a spoiler-light route agreed in the world guide
Progression: beginning-world boundary; bring only agreed equipment
Voice: listening welcome; text coordination available
Length: 90 minutes; host confirms world space before departure
Joining: use the listing, then follow the approved world-access guide
Use one clear question when a listing is incompatible: “Are you joining Hearth-PC or Lantern-PS5?” Correct the listing before assembling the crew. Close it when the session starts or ends as appropriate instead of leaving an apparently available group overnight. Joining the Discord listing does not create the in-game party or grant world admission.
Test: Fill the four-person teaching listing, send a fifth Member to its waiting list, and check that the mentor is included in the four. Then have a PS5 member inspect it and identify the PC restriction before trying to join.
6. Beacon Events: Plan World Nights Without Reserving Fictional Seats
Use Beacon Events for planned attendance. Emberlight's example is Hearth Settlement Workshop, Saturday at 7 p.m. America/New_York, two hours, with six builders including the host. State the PC world, project approval, materials policy, accessible meeting location, and whether voice is optional.
The six-person attendance cap is a community choice within the PC world ceiling. The host must also check other world occupants and access. A larger community showcase can use several separately hosted tour sessions; do not present a thirty-person RSVP list as thirty simultaneous places in one world.
Use activity interests rather than combat roles for a workshop: host, contributors, and learners can describe responsibilities without implying game restrictions. Add a waiting list and a sensible reminder, then tell reserves exactly how the host will contact them. A signup does not reserve a server slot, unlock progression, or deliver resources.
For a long workshop, use a suitable persistent room or the separate temporary-voice workflow. Do not rely on an event-created room remaining available for the entire session without checking its lifecycle.
Test: Sign up six test attendees, place another on the waitlist, and remove one confirmed attendee. Check the resulting roster and reminder text, then verify that the event still tells participants to confirm world access with the host.
7. Join-to-Create Voice: Give Each Crew a Room
Configure Join-to-Create Voice with an exploration lobby and workshop lobby under a visible voice category. Use four as the ordinary exploration-room limit and six for the community's workshop target. These are Discord conversation limits, separate from the sixteen-player PC and eight-player PS5 world limits.
Enable empty-room cleanup, explain creator ownership, and configure automatic ownership transfer for departures. Teach members to rename rooms with their world and purpose, such as Hearth — beginner route, rather than a late-game spoiler. Staff retain their own moderation authority even when a member owns a temporary room.
Do not create a permanent room for every dungeon or resource. When several groups share a world, a persistent host room can serve real coordination needs, but it should not become a mandatory place where all players must talk at once. Respect people who prefer listening or text.
Test: Create a room, fill its chosen limit, transfer ownership, and have everyone leave. Confirm cleanup and the new owner's controls; verify that none of these actions creates or changes an Enshrouded world.
8. Announcements: Publish the Community's Decisions Clearly
Create Announcement schedules manually. Start with a weekly world plan and a dated maintenance notice. A plan should name the world, affected activities, time zone, and where members can ask questions. A maintenance message should distinguish a routine restart, a game update, and an intentional world reset.
Use opt-in world or workshop pings. Beacon already owns reminders for its event; the weekly plan should point to that event instead of sending the same countdown through another service. Preview the wording and mentions before saving. A real send action is not a private preview.
Keep a human owner for notices involving saves or progression. “We will review the update on Friday” is an honest plan; “the bot will safely migrate the world” would claim an integration this setup does not provide. Pause outdated recurring notices when host availability changes.
Test: Preview a weekly plan with a test role and an explicit time zone. Confirm only the intended role is mentioned, and check that a canceled workshop no longer appears in the recurring message.
9. Social Feeds: Add the Verified Steam Source
The inspected catalog has no curated Enshrouded tile. Use the generic Steam news route in Social Feeds, with App ID 1203620, verified against the official Steam listing. Send it to #official-news without defaulting to a server-wide mention.
The reviewed Steam source polls public publisher community announcements with a default interval of 900 seconds. Polling does not guarantee exact arrival times or complete coverage of every support article, forum reply, or console notice. Keep the official news site and support knowledge base linked in the world guide for members who need the original details.
Put commentary in a separate discussion space. A feed item about a new feature does not authorize the host to alter the shared world immediately. Staff should read the source, confirm which platform and version it concerns, and publish a community-specific plan through Announcements when action is needed.
Test: Check the saved App ID and destination, inspect the source's available item or preview, and verify that its link opens the publisher announcement. Observe the actual feed behavior without promising an instant test post.
10. Analytics: Measure Participation Around the Hearth
Use Analytics to ask whether newcomers find useful conversation, whether LFG is active, and whether workshop nights bring people back. Compare a few weeks of Discord activity before changing the entire structure. A quiet exploration channel might mean members are happily playing; ask hosts before treating silence as failure.
Exclude private tickets, staff areas, and automated feed traffic where appropriate. Record a simple operational question alongside each review: “Did the new first-session link reduce repeated joining questions?” Combine the Discord trend with voluntary host feedback rather than claiming one chart proves a causal effect.
This setup does not provide verified Enshrouded levels, inventories, quest completion, base ownership, or live world occupancy. Discord activity is not a player-skill score, and a member who rarely writes may still be the person maintaining a beloved settlement.
Test: Review the selected channel scope and compare an active public channel with the official-news stream. Confirm private reports are excluded and that the dashboard is described to staff as community activity, not game telemetry.
11. Giveaways: Keep Prizes Separate From World Privileges
Use Giveaways for an occasional legitimate prize, such as an authorized storefront gift compatible with the winner's region. State eligibility, end time, delivery responsibility, and what happens if a winner cannot use the prize. Confirm availability before advertising it.
Avoid giving scarce world access, staff trust, or permission to modify shared builds as random prizes. Those decisions affect everyone and need consistent community rules. A drawing should not pressure people to reveal personal information or spend hours posting low-value messages to qualify.
YourBot manages the Discord drawing; it does not grant game items, transfer equipment, validate trades, or deliver a game entitlement automatically. Handle delivery through an appropriate authorized route without collecting account passwords or authentication codes.
Test: Run a clearly labeled staff-only drawing for a harmless imaginary prize. Exercise winner selection and the documented claim process, then verify that the public community was neither pinged nor promised a real reward.
Agree on Progression Before Opening a Shared World
Write a short world charter before the first major expedition. Emberlight's charter names the current progression boundary, how shared resources may be used, what equipment visitors can bring, and which decisions require the regular group to agree. The charter should explain how a returning player can help without completing everything for a newcomer.
Use concrete examples. A builder can improve a public path without permission for every block; demolishing another member's landmark requires review. A veteran can answer a crafting question without revealing the whole next biome. A gathering crew should know whether materials go to a project chest or remain personal property.
Review disagreements privately when they involve specific people, then publish the resulting general rule without exposing the report. The aim is predictable cooperation, not a legal code for every possible tool. Mark the charter's revision and effective date so members can tell which agreement applied to an older project.
Make Shared Building Easy to Join and Easy to Leave
A useful project brief includes purpose, world, owner, public-safe location label, approved scope, materials request, and the next small task. “Build the west gate” is less actionable than “finish the entrance roof using the agreed palette; leave the central arch unchanged.” Credit contributors without making participation a competition.
Name a backup contact for long-running projects. If the owner disappears, staff should know whether to pause, reassign, or archive the work. Do not treat a deadline in Discord as authority to take another player's resources. Contributors should be able to stop participating without losing ordinary community access.
For Sparkworks or Adventure Sharing experiments, state whether the session is a playtest, a showcase, or a construction workshop. Invite specific feedback about navigation and clarity rather than promising that every community creation behaves like official content. Keep creator instructions and version notes attached to the brief so testers can reproduce the intended experience.
Give Hosts an Operational Handover Without Sharing Secrets
Maintain a staff-only handover containing the world label, responsible people, last announced maintenance, backup ownership, and where the authorized host keeps its own operational documentation. The handover should record responsibility and completion, not copy passwords, tokens, remote-console credentials, or private save-download links into Discord.
Before a significant game update, the host should confirm its own backup and compatibility procedure, announce the expected interruption, and state how members will learn that play can resume. YourBot can carry the notice and collect questions; the actual server work remains with authorized operators.
When something fails, publish a plain status: affected world, known symptom, time of the next update, and whether members should stop attempting to join. Avoid unsupported assurances about recovery. A calm, maintained status is more useful than ten speculative messages from different volunteers.
Add an Emberlight Project Register Only When You Need It
Launch with the built-ins and a clear project post first. If approved builds and resource requests become hard to track, assess the Marketplace. DecisionBook already offers durable decision records; it may suit a modest charter or approval process. Do not commission a second system just because a custom project has an appealing name.
The proposed Emberlight Project Register earns its place only if the community needs structured world labels, spoiler-aware visibility, materials requests, project states, and scoped exports together. It is a build specification, not an existing Enshrouded integration or a tested plugin. Group Finder still recruits crews, Beacon schedules sessions, Tickets handles private disputes, and Announcements publishes decisions.
Copy-ready Plugin Builder specification
Build Emberlight Project Register, a manually maintained project library.
Version1: no external network access and no game-client/server control.
Roles: Members propose; Project Owners edit their own drafts; Stewards review;
server owner configures roles and retention. Staff status is never self-selected.
Screens: Current Projects, My Proposals, Review Queue, Project Detail, Audit,
and Export. Filters: world, spoiler tier, state, owner, overdue review.
Fields: immutable record ID and Discord server ID; title; world label;
project owner; public-safe location label; purpose; materials request;
spoiler tier; visibility; due date; review date; revision; reviewer;
created/updated timestamps. Optional staff note is separately restricted.
States: proposed -> approved -> in progress -> ready for tour -> archived.
Stewards approve and archive; owners request review of material scope changes.
Validate title/notes lengths, required world, allowed state transitions,
dates and current role permissions; reject secrets and unsafe mass mentions.
No inventory totals, coordinates, progress or ownership is automatically verified.
Persist records and revisions across restart. Use optimistic revision checks;
stale edits must not overwrite newer approvals. Warn about likely duplicate
world/title/location proposals; let a steward link or merge with an audit entry.
Authorize each list, detail, action, search and export on the server.
Derive server identity from the authenticated context, never a caller's field.
Owners cannot approve their own work by changing an ID or request payload.
Recheck current roles after revocation. Private notes never leak in public cards,
notifications, search snippets, counts, or ordinary exports.
Exports include only records/fields currently visible to the requester.
Audit actor, action, time, old/new state and revision; no secrets in logs.
Offer plain-language actions Propose, Revise, Submit, Approve, Start,
Request Tour and Archive; final command names depend on reviewed implementation.
Acceptance: two-server isolation; guessed private ID denied; revoked steward
cannot approve; owner cannot self-approve; stale edit rejected; duplicate handled;
restart preserves state; spoiler-hidden record excluded from public export;
archived record remains auditable; deletion follows configured retention.
Do not rebuild LFG, events, tickets or announcements. Never collect credentials.
Review, test, and continue through the SDK
Review the generated plan, source, manifest, storage behavior, and requested capabilities. A record library should not need arbitrary web access or access to every message. Validation can identify structural problems; it does not prove that a revoked steward loses record access or that a spoiler-hidden title stays out of exports.
Follow the current Plugin Builder testing guide for a private test route. Use a development server and representative roles before considering normal use. Test the direct record URL and export action as carefully as the visible buttons; hiding a button alone is not authorization.
A developer can continue through the SDK quickstart in Visual Studio Code, review persistence and authorization, and manage versions through the Developer Portal. Follow the publishing documentation if optional Marketplace distribution becomes useful. A private experiment is not a public listing or proof that the workflow has passed review.
Run a Complete First-Week Member Journey
| Scenario | Successful result |
|---|---|
| A new PS5 member joins with DMs blocked | Public instructions lead to the console world guide. |
| A PC learner finds an expedition | World, progression and voice expectations are clear. |
| A mentor joins the teaching crew | The mentor occupies one of the four places. |
| The workshop fills | A reserve understands the waitlist and host confirmation. |
| A private joining problem is reported | Only the right support team sees the ticket. |
| A voice owner leaves | Ownership transfers and the empty room later disappears. |
| A project changes scope | Its reviewed revision and materials request are updated. |
| A steward loses their role | Direct record actions and exports lose access too. |
| A returning player asks about the next biome | Staff use the current spoiler/progression agreement. |
Ask each tester where they hesitated. Fix the unclear world label, inaccessible instruction, or stale project before adding another automated workflow. The community benefits more from one understandable first session than from a large collection of unused channels.
Frequently Asked Questions
Can PC and PS5 members share one Enshrouded group?
They can share the Discord, but the launch FAQ says cross-platform play was unavailable at the 1.0 launch. Keep playable listings tied to the actual platform and world until official information confirms a change.
Is every Enshrouded group sixteen players?
No. The launch material specifies up to sixteen on PC and eight on PS5. Emberlight's four-person teaching crew is a smaller community target, and other occupants still count toward world capacity.
Does a Discord role prove that someone unlocked the next area?
No. Roles communicate interests or reviewed Discord access. Hosts and players must check the actual character, world, and agreed progression prerequisites.
Will Group Finder automatically choose Enshrouded templates?
The inspected setup detector has no Enshrouded keyword or dedicated starter template. Create the explicit world-specific templates and check their capacities rather than relying on generic defaults.
Can Social Feeds follow Enshrouded without a catalog tile?
Yes, the supported generic Steam route can use App ID 1203620. It follows publisher announcements available through that source and does not mirror every support page or guarantee immediate delivery.
Does YourBot back up the game world or verify project materials?
This setup does neither. Hosts manage their actual saves and infrastructure. Project owners manually maintain materials requests; the proposed register does not inspect inventory or the world.
Is the custom register required to launch?
No. Start with a clear world guide, the built-ins, and a small project process. Assess an existing Marketplace solution before using Plugin Builder for additional structured requirements.
Build a Fellowship That Respects the Shared World
Enshrouded coordination depends on the destination world, platform, progression agreement, and the kind of experience players want. Start Your Server establishes a reviewable Discord foundation; the ten services help members arrive, form crews, plan workshops, talk, and find reliable notices.
Keep world admission, backups, save changes, character readiness, and actual construction with the people responsible in the game. Add the Project Register only when lasting projects need more structure than existing tools provide. Emberlight succeeds when a newcomer can join the right expedition and a builder can return next week to find the shared plan still understandable.