A Valheim Discord should help people join the right world, agree on progression, and finish shared projects without turning every evening into an argument about imported equipment. Use YourBot to build a compact server, welcome newcomers, organize compatible expeditions, schedule world events, and keep voice rooms useful. Leave world hosting, character decisions, and in-game access with the people responsible for them.
This guide follows Northstar Hearth, a fictional 240-member community with a primary crossplay-enabled cooperative world, a separate experimental world, and a mixture of builders, returning Vikings, and first-time explorers. Its policies and event sizes are examples. The community is much larger than any one Valheim session: the official FAQ caps servers at ten players.
Valheim 1.0 and the Deep North arrived on September 9, 2026. That makes returning-player onboarding and spoiler boundaries especially useful. Build the Discord around the world people actually share today, with a clear route for both cautious newcomers and experienced explorers.
Start With the Right Valheim Community Model
A Discord community is bigger than its worlds
Northstar's main world is called Hearth. A second world, Workshop, is reserved for experiments that would disrupt shared progression. These are fictional community labels, not integrations created by YourBot. Every listing names its world before naming its objective. A six-person sailing trip on Hearth does not recruit someone into Workshop simply because both use the same Discord.
Ten is a world population limit, not a requirement to make every outing ten players. Northstar normally sends four people on a newcomer expedition and six on a preparation trip. Those are chosen working sizes. If four other members are already building on Hearth, a six-person event would occupy all remaining seats. The host must consider concurrent occupants, not just the event roster.
Keep one maintained joining guide with world purpose, host region, access process, normal availability, progression boundary, and current build requirements. A hosted session depends on its host being available; a dedicated server has a different operating arrangement. Link the official hosting instructions rather than posting remote administration details in public chat.
Crossplay requires a compatible setup
The current official FAQ lists Windows, Linux, Mac, Xbox One, Xbox Series, PlayStation 5, and Nintendo Switch 2. Platform availability alone does not establish that every combination of clients, builds, and worlds can connect at a particular moment. Follow the crossplay guidance and current platform notices when preparing a mixed-platform session.
Northstar keeps general conversation together and records platform, storefront where relevant, current client build, and crossplay status in the listing. It does not create seven platform categories by default. If a patch temporarily separates versions, staff add a dated compatibility notice and amend affected listings. Remove that restriction when the supported situation changes instead of preserving a permanent silo.
Mods need a separate decision. Iron Gate's FAQ says mods are not officially supported. Workshop therefore has its own explicit mod/version agreement, while Hearth uses the community's stated vanilla setup. A player consenting to one world is not consenting to install an arbitrary executable offered through a direct message.
Progression and building are shared agreements
New arrivals may be experienced elsewhere and still want to discover this world gradually. Ask about preferences, then state the world's policy on outside equipment, boss progression, resource use, and spoilers. These are Northstar's social rules; a Discord role does not inspect a character or enforce them inside Valheim.
Keep detailed boss and later-biome discussion in an opt-in discoveries area. Use neutral public event titles such as “Hearth progression evening” when the boss name would itself spoil the experience. Builders should have a full place in the community even if they skip combat nights. Belonging must not depend on being ready for the latest biome.
The Community We Will Build
Northstar runs a weekly beginner expedition, one progression evening, and a weekend harbor workshop. Two world stewards handle access and changes; mentors teach without automatically gaining moderation powers. The first-week goal is simple: a member understands the charter, joins one compatible activity, and knows where to ask a private question.
YourBot's role in the community
| Service | Community use |
|---|---|
| Welcome | Explain worlds, verification, interests, and spoiler choices. |
| Sentinel | Address scams, unsafe downloads, harassment, and exposed secrets. |
| Tickets | Route access questions, private reports, and host concerns. |
| Group Finder | Fill small expeditions with the right world and expectations. |
| Beacon Events | Schedule progression nights and building workshops. |
| Join-to-Create Voice | Provide temporary rooms for active crews. |
| Announcements | Publish dated plans, maintenance notices, and charter changes. |
| Social Feeds | Follow configured Valheim publisher news. |
| Analytics | Identify Discord onboarding and participation problems. |
| Giveaways | Run occasional legitimate community drawings. |
1. Create the Foundation With Start Your Server
The server owner should open Start Your Server, describe the community, and review the proposed structure before applying it. Give YourBot the Discord permissions needed for intended actions, such as creating channels or assigning ordinary roles, and put it above roles it must grant. Preserve higher staff roles and the owner's authority.
Dashboard authorization is separate from Discord role names. Follow the access-level documentation when delegating page access; naming someone World Steward does not automatically make them a dashboard manager. Start Your Server is an owner workflow in the current dedicated documentation.
Copy-ready community brief
Design a Discord for Northstar Hearth, a fictional 240-member Valheim community.
Our primary cooperative world is Hearth; Workshop is a separate experimental world.
Keep existing channels, roles, messages and permissions on the first pass.
Do not delete or bulk rename anything without a separate reviewed decision.
Newcomers need rules, a short world comparison, verification and a Member role.
Offer opt-in Building, Expeditions, New Viking, Mentor Interest, Event Notices
and Discoveries interests. Mentor Interest is not staff authority.
Do not make Moderator or World Steward self-selectable.
Use a compact LFG area. Listings must name world, host region, current build,
crossplay requirement, vanilla/mod agreement, progression boundary, imported-gear
policy, goal, current occupants, actual group target, voice and expected duration.
Valheim worlds have a ten-player cap; community expeditions are usually four
or six. Playing mentors count inside those numbers. Consider other world occupants.
Plan all ten services: Welcome, Sentinel, Tickets, Group Finder, Beacon Events,
Join-to-Create Voice, Announcements, Social Feeds, Analytics and Giveaways.
Use private intake for access help, conduct reports and hosting concerns.
Create small temporary expedition rooms, not one permanent voice channel per biome.
Keep detailed progression spoilers out of public channel names and reminders.
Exclude private reports and staff channels from community activity comparisons.
Ask for no passwords, hosting tokens, join secrets or remote-console credentials.
Do not claim to configure Valheim, verify gear, change world access or award items.
Show the proposed Channels, Roles and Services for review. Enable Announcements
and Social Feeds where appropriate, but leave their schedules/subscriptions for
manual finishing. Keep game hosting and backups outside this Discord build.
A compact channel plan
START HERE
rules-and-worlds
welcome-and-interests
community-notices
THE HEARTH
general
beginner-help
expeditions
builds-and-projects
discoveries [opt-in]
ACTIVITIES
events
official-news
create-expedition-room [voice lobby]
SUPPORT
ask-staff
STAFF [private]
reports
world-operations
Add channels when real traffic needs them. A separate channel for every biome or crafting station often hides unanswered questions. A project thread is easier to retire than another permanent category.
Review before applying
Inspect Channels, Roles, and Services, including which role can see and write in each destination. Use the documented role-perspective preview as an unverified newcomer, a Member, and a mentor. Resolve safety-check findings before building. Keep deletions off during the illustrative first pass.
Read the build report after applying changes and finish any missing destinations or service settings. Announcements schedules and Social Feed subscriptions require manual finishing steps. A requested weekly reminder is not evidence that the reminder exists.
A pre-build snapshot helps with recovery, but undo is limited: added channels and roles can remain, and restored channels cannot recover deleted messages. Review after-build behavior before making structural changes. Test: use an ordinary member account to reach the charter, choose an interest, find LFG, and open support without seeing staff operations.
2. Welcome: Explain the World Before Offering an Expedition
Configure Welcome around a visible entry path: read the rules and world summary, complete the chosen verification interaction, receive limited Member access, then select interests. A successful Discord verification does not prove ownership of Valheim, correct client version, or acceptance into an in-game world.
Offer New Viking, Building, Expeditions, Discoveries, and Event Notices. Mentor Interest means someone is willing to help; stewards still decide who may run teaching sessions. Do not let a self-service role grant world administration, dashboard management, or moderation permissions.
A useful greeting is: “Welcome to Northstar Hearth. Read rules-and-worlds, choose what you enjoy, and tell us whether you want a beginner expedition or a building session. Every listing names the world and its progression agreement.” Keep these instructions in the entry channel even if you also send a DM; members may block direct messages.
Give newcomers one next action rather than a long checklist. An experienced player can choose a newcomer session without claiming ignorance, while a builder can go directly to a project discussion. Test: complete onboarding with DMs blocked, confirm Member opens intended channels, and check that choosing Discoveries does not grant any staff access.
3. Sentinel: Protect the Community Without Policing Play Styles
Use Sentinel for Discord risks: fake support accounts, suspicious mod downloads, account phishing, harassment, spam, and messages containing hosting secrets. Publish a simple boundary between criticizing a building choice and attacking its builder. A disagreement about resource use should not become a public accusation campaign.
Start aggressive new filters in Testing and inspect legitimate examples before enabling actions. A legitimate link to an official server manual should not be treated like an unsolicited executable. Give moderators context and a private escalation route rather than asking them to resolve every technical question in public.
Discord moderation is not game enforcement. Timing out a member does not remove their character from Hearth, revoke a server credential, or restore a damaged building. World stewards handle game-side actions separately. If a secret is exposed, the responsible host must rotate it through their normal secure administration process; deleting the message alone is insufficient.
Test: submit harmless staff test messages representing a suspicious download and a legitimate official link. Confirm expected cases, staff visibility, and appeal routing without distributing malware or real credentials.
4. Tickets: Separate Access Help From Private Reports
Build three Tickets intake paths. World Access asks for world label, platform/storefront, client build, approximate connection time and timezone, and a non-sensitive error description. Community Report asks for a message link, brief description, and urgency. Host Concern asks for world, planned change, likely impact, and the steward who should review it.
Never request passwords, recovery codes, platform tokens, or hosting control-panel access. Ask members to redact screenshots before submitting them. Reports about a person should go to designated staff, not every mentor or builder. Access-help tickets can go to a narrower technical team without exposing conduct reports.
An accepted application may support a Discord access decision, but the host still performs any approved world-side action. Say that clearly in the closing response. Include what the member should try next and who owns the unresolved step. Closing a ticket does not establish that a connection succeeded.
Test: open each path as a Member, verify the right team receives it, and confirm an unrelated member and an ordinary mentor cannot read it. Recheck access after the ticket closes and after a steward loses their role.
5. Group Finder: Match the World, Progression Agreement, and Crew Size
Valheim is not in the currently inspected setup game-detection list, so create explicit templates manually. Its Social Feeds entry is a separate capability. Do not accept a generic five-player fallback as a Valheim rule. The public Group Finder guide describes Discord listings, capacities, templates, and waiting lists; the world still has its own access and occupancy.
Create the first template
Template Name: Hearth newcomer expedition
Game: Valheim
Default Party Size: 4 total, including leader and any playing mentor
Default Expiry: 2 hours, chosen for this community's near-term listings
Description: Hearth vanilla cooperative world. State build compatibility,
host region, crossplay status, progression boundary and imported-gear policy.
Name the goal, current crew, other world occupants, voice preference and duration.
Do not post joining secrets. Host confirms world admission separately.
Four gives the mentor room to teach while keeping conversation manageable. It is a Northstar recommendation, not a game-enforced party size. The leader confirms whether other players already occupy the world before inviting the crew.
| Additional template | Target size | Required context |
|---|---|---|
| Hearth preparation outing | 6 chosen participants | Agreed progression, supplies, other world occupants, stopping point. |
| Harbor building crew | 4 chosen participants | Approved site, project owner, resource policy, permission to change structures. |
| Sailing reconnaissance | 4 chosen participants | Spoiler boundary, departure plan, return expectation, voice. |
| Recovery assistance | 3 chosen participants | Safe public description, world access, equipment agreement; private details separately. |
| Workshop experiment | 4 chosen participants | Exact mod/version agreement and explicit separation from Hearth. |
| Community tour | Up to 10 world occupants total | Available world seats, guide counted inside capacity, spoiler route. |
Example live listing
Hearth newcomer expedition — shoreline mapping and food gathering
Region: North American host; check your connection before departure
World/build: Hearth, current agreed stable build, vanilla, crossplay enabled
Progression: stay inside this week's published charter boundary
Equipment: locally agreed starter equipment; no imported late-game gear
Crew: 2/4, including the playing mentor; two places available
Other world occupants: steward will confirm before admission
Voice: preferred for directions; text instructions available
Duration: 90 minutes; return to harbor before the session ends
Join through the approved private access process, not public passwords
Ask the leader to update or close the listing when the objective changes. A recovery run becoming a spoiler-heavy expedition needs fresh consent. Joining a Discord listing does not create an in-game party or reserve a Valheim server seat. Test: fill all four positions including the mentor, check waitlist behavior, and have the steward simulate a nearly full world so the crew understands why admission may need rescheduling.
6. Beacon Events: Schedule Progression Without Overbooking the World
Use Beacon Events for activities that need advance attendance. Northstar's “Saturday Harbor Workshop” has eight playing participants, including the guide, with two world seats left for named stewards. This is a deliberate ten-occupant budget, not eight plus an invisible staff allowance.
The description names Hearth, the agreed build, approved project scope, supplies policy, start time with timezone, expected finish, and a link to the current charter. Use a waitlist rather than allowing unlimited confirmations and hoping people stay offline. If other world users cannot be excluded or scheduled, lower the event capacity accordingly.
Choose modest reminders, such as the day before and shortly before the session. Put the final access check in the organizer's checklist. Beacon RSVPs do not register a player in Valheim, start the host, reserve server slots, or grant access and rewards. A public community discussion can have broader attendance than the subsequent ten-seat world session; describe those as separate activities.
Test: register the guide as a participant, fill the event, add a waitlisted member, then withdraw one attendee. Confirm the organizer can communicate the roster change and the joining instructions remain private.
7. Join-to-Create Voice: Give Each Expedition a Temporary Room
Set up Join-to-Create Voice with a visible lobby, a destination category, and a four-user default for small expeditions. Use a second ten-user lobby only if full-world gatherings actually need it. Count a playing mentor within the intended crew; do not use voice capacity to redefine world capacity.
Enable the documented ownership and ownership-transfer behavior appropriate to the server, and cleanup when the room becomes empty. Test that an owner can manage their room without managing everyone else's. A temporary room is useful when a builder and an expedition would otherwise compete for one general voice channel.
Valheim's official FAQ describes in-game text chat and recommends separate software for voice. Provide a text alternative for members who cannot speak. Joining voice does not launch the game, admit a character, or ensure everyone is on Hearth. Put the world label in the conversation before departure.
Test: two members create separate rooms, the first creator leaves, and the remaining member retains the expected controls. Empty both rooms and confirm cleanup without affecting the lobby or another crew's room.
8. Announcements: Publish Dated World Decisions
Create Announcements schedules manually after the foundation build. A weekly plan can point to current expeditions, the harbor project, and the next charter review. A separate one-off notice should explain a maintenance window or progression decision with its date, timezone, responsible steward, and expected member action.
Use Event Notices as an opt-in role. If Beacon already sends the event reminder, the weekly post should link to the event rather than issue another last-minute ping. Do not announce every resource request to the entire community. Reserve broad notices for changes that affect access or the shared agreement.
Patch-specific statements need dates and a source link. If a version mismatch affects one platform, say which confirmed builds and worlds are affected and when staff will recheck. Avoid leaving a temporary warning pinned after it expires. A scheduled Discord post does not update the game or back up a world.
Test: send a staff-only preview, inspect timezone rendering and role mentions, then review how a revised or canceled session changes its future posts. Confirm old maintenance wording will not recur the following week.
9. Social Feeds: Select Valheim and Verify the News Source
The inspected catalog includes Valheim, slug valheim, category Survival, source steam_news, numeric Steam App ID 892970. This matches the official Steam listing. Add the subscription manually to official-news and keep member posting permissions appropriate for a source channel.
The inspected Steam adapter uses public Steam news and filters publisher community announcements. Its class polling default is 900 seconds. That is an implementation default, not guaranteed delivery exactly every fifteen minutes, and it does not mirror every support answer or official forum post. Link the developer's news and support pages for issues that may not appear in that feed.
Keep staff interpretation separate from the source item. A patch note about unexplored terrain does not establish that Northstar will reset Hearth. A steward should make that community decision through the charter and announcements process.
Test: inspect a delivered item for the correct game, publisher destination, formatting, and duplicate handling. If nothing arrives immediately, verify the subscription and upstream announcement before treating a quiet period as a defect. Do not fabricate a new patch to test it.
10. Analytics: Measure Participation and Clarity
Use Analytics to ask whether newcomers reach an activity, whether beginner-help receives responses, and whether expeditions use their temporary rooms. Review trends across comparable weeks rather than treating one quiet holiday evening as failure. A builder who posts one useful project update may contribute more than someone sending fifty short messages.
Keep private reports, staff operations, and automated news out of ordinary member comparisons where the controls allow. Explain to staff why those exclusions matter. Do not publish a ranking that reveals who opened a private access or conduct ticket.
Discord activity does not establish Valheim skill, boss kills, inventory, building ownership, character readiness, or actual time inside Hearth. If an event went badly, ask the participants what was confusing; do not infer a combat problem from voice duration. Northstar's useful first measure is whether a newcomer can find one suitable session and return voluntarily.
Test: compare a human activity channel with a news-only channel, verify the selected scope, and check that a normal staff viewer cannot use a community report to expose restricted conversations.
11. Giveaways: Keep Drawings Separate From World Privileges
Use Giveaways for an occasional legitimate community prize with clear eligibility, closing time, and delivery responsibility. A small store gift card with verified region restrictions is easier to describe than an improvised promise of rare in-game equipment. Check the actual prize's terms before announcing it.
Avoid selling access to the progression group through a drawing. A winner should not gain moderation powers, a privileged world role, or an exception to the imported-equipment policy. YourBot handles the Discord drawing; it does not deliver Valheim items, authenticate a trade, transfer currency, or grant platform entitlements automatically.
Name the staff contact and a claim process that never asks for account passwords or recovery codes. Explain reroll conditions in advance so absence does not turn into a public argument. Test: run a staff-only drawing for a harmless fictional prize, confirm eligibility and closing behavior, then practice the winner communication without purchasing or transferring anything.
Keep the World Charter Short Enough to Use
A shared world needs decisions people can find while the host is offline. Northstar's charter answers five questions: what progression is currently agreed, what equipment may visitors bring, what shared materials may members use, where building changes need consent, and how the next decision will be made. Keep an effective date and a steward beside each rule.
Separate an approved rule from a suggestion. Someone posting an enthusiastic plan for a harbor rebuild has not obtained permission to dismantle another member's house. Ask for a simple proposal showing the area, intended result, likely resource needs, and affected builders. Record the decision and notify those builders before work begins.
Set a review date instead of treating every policy as permanent. Returning players may want a faster progression pace while newcomers want discovery. A second world or a later expedition can sometimes meet both needs without forcing one group out. Record the decision plainly so staff do not have to reconstruct a debate from hundreds of messages.
Plan Updates, Exploration, and Recovery as Different Jobs
The official FAQ explains that new fixed world content generally appears in previously unexplored areas, while preserving already explored places helps protect player builds. That makes exploration boundaries and world-change discussions practical community topics. It does not mean every update requires a new world or that a Discord post can migrate one safely.
Before a significant update, the host reviews the current 1.0 and world guidance, the appropriate hosting manual, and the community's backup process. Announce the planned interruption and who will confirm recovery. Keep actual save files and administration secrets in the host's secure storage, not in a public project attachment.
Afterward, confirm the game-side world is available, then update the Discord compatibility note and reopen affected sessions. If Workshop uses mods, treat its recovery separately. A successful vanilla Hearth session says nothing about Workshop's exact mod set. Keep one steward responsible for the current status so contradictory “all fixed” messages do not spread.
Make Teaching Runs Respect Discovery
A mentor's first task is to learn what the group wants to discover, not to display everything they know. At the start of a beginner trip, agree on the destination boundary, advice style, equipment policy, and stopping time. A short explanation before a dangerous crossing is more useful than a stream of unexplained instructions afterward.
Count mentors as players and give them ordinary crew responsibilities. If a four-person listing contains one leader, one mentor, and two newcomers, it is full. Someone observing through Discord can be outside that roster only when they genuinely are not joining the world; they still need permission to see or hear anything private.
End with one question: what would make the next outing easier to join? Update the template if members consistently miss the world label or mistake an interest role for access approval. Improve the instructions before adding another automation layer.
Add a Hearth World Charter Only When You Need It
Launch with the built-ins first. A pinned charter and a few project threads may be enough. Check the Marketplace for a maintained suitable solution before creating a custom one. The proposed Hearth World Charter becomes useful when multiple worlds, overlapping projects, and frequent revisions make the current decision hard to identify.
This is a proposed manually maintained record library, not an existing Valheim integration. Group Finder still fills crews, Beacon schedules attendance, Tickets handles private support, and Announcements sends notices. The custom project stores durable decisions and approvals those services do not replace.
Copy-ready Plugin Builder specification
Build Hearth World Charter for one Discord server's Valheim community.
Purpose: revisioned world policies and shared-build requests maintained by people.
Version 1 must use no external network access and collect no secrets or game telemetry.
Roles: administrators configure access; World Stewards review and publish;
project owners edit their own drafts; Members read approved member-visible records.
Use server-side authorization on every list, detail, action and export request.
Never trust a hidden button, supplied owner ID or guessed record ID as authorization.
Derive Discord server scope from authenticated context; isolate all stored data by it.
Record types: world policy and build request.
Fields: generated ID, server scope, world label, record type, title, owner Discord ID,
progression boundary, imported-gear policy, shared-resource policy, requested change,
affected builders, visibility, reviewer, effective date, next review date, revision,
created/updated times and decision explanation. No world passwords, join secrets,
hosting credentials, private real-world addresses or detailed account information.
States: draft -> review -> approved -> current -> superseded; rejected proposals
return to draft with a reason. Only stewards can approve or make a revision current.
At most one current policy of each policy type per world. Publishing a new revision
atomically supersedes the old one; stale forms must show a conflict, not overwrite it.
Build requests require an owner, world, clear scope and affected-builder review.
Screens: member current charter with effective dates; world/project search;
my drafts; steward review queue; revision history; configuration and audit log.
Filters: world, type, state, owner, visibility, review overdue.
Suggested commands, to be created and validated as custom names rather than built-ins:
/hearth-charter current; /hearth-charter propose; /hearth-charter project;
/hearth-charter review. Avoid reserved/conflicting service command names.
Permissions: public records visible only at their intended member level; staff-only
operations notes never appear in member search, counts, autocomplete or exports.
Re-evaluate roles on each action; revoked stewards immediately lose edit/review access.
Owners cannot approve their own request unless a separately configured policy allows
it and the audit trail clearly records that exception. Default to independent review.
Validation: bounded text, required world/title, safe link handling, valid dates,
unique current-policy key, duplicate-proposal warning and explicit revision check.
Render user text safely. Reject secret fields rather than encouraging secret uploads.
Archive obsolete records according to a documented retention policy.
Audit: actor, action, time, record/revision and reason for approvals and visibility
changes. Keep restricted text restricted inside history and error messages.
Exports include only records/fields the requester can currently read; log export
scope and actor. Deletion/redaction must follow the configured retention policy.
Acceptance tests: another server cannot read a guessed ID; another owner cannot edit
my draft; member cannot access staff detail or export it; revoked steward cannot act;
concurrent publish yields one current policy; stale revision cannot overwrite;
retired record stays out of current view; approved build request does not claim
to modify Valheim or grant world admission.
Non-capabilities: no game client/server control, backups, RCON, roster sync,
inventory inspection, progression verification, item delivery or automatic building
ownership. No replacement for Group Finder, Beacon, Tickets or Announcements.
Review, test, and continue through the SDK
Use Plugin Builder to refine the plan before generating a draft. Review the actual manifest, source, requested capabilities, data model, screens, and custom command names. Static validation and any available sandbox result are useful evidence, but neither proves the permission model works for Northstar.
Test on a development server with an ordinary Member, a project owner, a steward, and a revoked steward. Try direct record URLs and exports as well as visible buttons. Use fictional records with no credentials. The important result is that a member cannot recover restricted text through search, history, a cached form, or an error response.
A developer can download the files, continue in Visual Studio Code using the current SDK testing guidance, and validate the manifest locally. Follow the Dev Portal review workflow for any eventual listing. Marketplace publication is optional; keep private testing and public publication as distinct decisions.
Run a Complete First-Week Member Journey
| Scenario | Successful result |
|---|---|
| New member joins with DMs blocked | Visible entry instructions lead to verification and limited Member access. |
| Returning player selects interests | Building and Discoveries access work without granting staff authority. |
| Newcomer joins an expedition | World, build, crossplay and equipment agreement are clear before admission. |
| Mentor joins a four-person crew | Mentor occupies one of four positions; the fifth person waits. |
| Workshop member asks for help | Exact world/mod context reaches the appropriate private support team. |
| Harbor workshop fills | Guide and other world occupants count within the ten-player world budget. |
| Crew leaves voice | Ownership transfer and empty-room cleanup behave as configured. |
| Charter changes during a draft | The old revision stays available as history and stale edits cannot replace the new current rule. |
| Steward loses access | Restricted detail, actions and exports are denied immediately. |
Run this journey before opening every feature to everyone. Fix a confusing label, stale charter link, or overbooked event before adding another template. A small server that reliably gets members into the right evening is more useful than a large channel list nobody understands.
Frequently Asked Questions
How many people can join one Valheim world?
The official FAQ caps servers at ten players. Smaller expedition targets are community choices. Count playing mentors and unrelated occupants in the same world before confirming an event's available seats.
Should every platform have its own Discord section?
Usually start with shared conversation and explicit compatibility fields. Confirm crossplay configuration, current builds and any platform-specific notice for the actual world. Separate a genuinely incompatible setup when needed, then review whether that separation still serves members.
Does YourBot automatically recognize Valheim during setup?
Valheim is absent from the currently inspected setup detector, so define manual activity templates. This does not prevent using Group Finder. A Valheim Social Feeds tile is independent of automatic setup detection.
Can YourBot verify character equipment or progression?
The built-ins described here do not inspect a Valheim character or enforce the world charter inside the game. Use clear member declarations and authorized game-side stewardship. Treat a Discord readiness role as a community label rather than proof.
Can we receive Valheim patch news?
The inspected Social Feeds catalog has Valheim through Steam App ID 892970. Configure and test the subscription manually. The source polls publisher community announcements; it is not a complete or instantaneous copy of every official support channel.
Is the custom charter plugin required?
No. Start with a maintained charter and ordinary project threads. Build or adopt a dedicated record library when revision history, permissions and overlapping projects create work that the simpler arrangement no longer handles well.
Build a Hearth People Can Return To
Valheim communities depend on shared expectations: the right world, compatible clients, a ten-player occupancy budget, and consent about progression and building. Start Your Server establishes the Discord foundation, while the ten services handle everyday participation. Hosts remain responsible for worlds and members remain responsible for how they play together.
Keep the first charter readable, the first expedition small, and the first workshop realistically staffed. Add a revisioned project through Plugin Builder when durable decisions become difficult to maintain. Northstar succeeds when a newcomer can find a place at the hearth and a returning builder can understand what changed while they were away.