A useful Throne and Liberty Discord separates social membership from the in-game guild, matches players by current server and activity, and gives planned guild attendance a clear owner. Build six-person co-op dungeon groups, use the distinct four-person limit for Remnants of Nix, and treat raids and sieges as their own activities. A large Discord roster is not one playable party or a verified guild roster.
YourBot can establish the Discord foundation and operate recruitment, protection, private support, grouping, events, temporary voice, and communication. The game still owns characters, guild membership, readiness, territory, and rewards. This guide follows Astral Accord, a fictional community of about 240 members whose main activities use a current Americas cross-play server, with applicants, social friends, and active guild members sharing the community.
The goal is reliable context. A newcomer should know which group they can join, an officer should see who owns the next event, and a returning player should find current service information rather than an old server name or launch-era assumption.
Start With the Right Throne and Liberty Community Model
Match region and server before filling a party
The official FAQ describes PC Steam, PlayStation 5, and Xbox Series X|S cross-play, with designated PlayStation-only servers as an exception. It also states that cross-progression is not supported. Do not promise that a player can move the same progress between platforms merely because the platforms can play together.
The 2026 region consolidation notice merges the previous American regions into Americas and changes server arrangements, including PlayStation-only availability. Use the current character-selection region and server in a listing. An old NA-East role or historical guild introduction is not sufficient compatibility information.
Six is useful, but it is not every activity's limit
The official gameplay page describes co-op dungeons for a party of six. The Nix release notes identify Remnants of Nix as a different activity with a four-player maximum party and hostile non-party players. A generic six-slot template should not be copied into it.
Raid attendance, guild membership, alliance coordination, and siege participation are separate quantities. Check the current activity interface and official notes for the actual requirement before publishing a roster. Do not describe a community event's chosen attendance cap as a universal raid minimum or guild capacity.
Keep current operations and the announced service transition distinct
As of October 29, 2026, the official transition notice schedules Western service-transition maintenance to begin November 10, moving live operations from Amazon Game Studios to NC. That is a planned transition, not a claim that the new operation is already live.
Account, support, shop, and service instructions can change around that date. Give one staff member responsibility for reviewing official updates and revising the community's help links. YourBot does not perform the account transfer or replace official support.
The Community We Will Build
Astral Accord runs two dungeon evenings, a newcomer orientation, and separately planned guild activities when officers verify current eligibility and schedules. Members include beginners, returning players, active guild members, and friends who want social participation without a guild commitment.
Staff distinguish Moderator, Recruitment Officer, Activity Host, Guild Officer, and Readiness Reviewer. Self-selected activity interests help with notifications; reviewed membership and strategy access are staff decisions. Discord access does not automatically invite a character to the guild or assign in-game authority.
YourBot's role in the community
| Service | Community use |
|---|---|
| Welcome | Explain entry, server context, activity interests, and next steps. |
| Sentinel | Address scams, impersonation, harassment, and unsafe links. |
| Tickets | Route applications, reports, appeals, and access help privately. |
| Group Finder | Form explicit six- and four-player activity groups. |
| Beacon Events | Schedule dungeon nights and reviewed guild attendance. |
| Join-to-Create Voice | Supply appropriately sized temporary group rooms. |
| Announcements | Publish community plans and dated service notices. |
| Social Feeds | Follow a verified publisher source with appropriate limits. |
| Analytics | Improve newcomer participation and community scheduling. |
| Giveaways | Run optional legitimate celebrations outside game systems. |
1. Create the Foundation With Start Your Server
The owner can describe Astral Accord in Start Your Server, inspect the proposed design, and apply supported configuration. State the current community model, reviewed access boundaries, and activity capacities. Do not ask for a channel for every dungeon, weapon, boss, or server name.
Follow the access-level documentation: Discord permissions and dashboard authorization are different. Put YourBot above the ordinary roles it must grant and provide the permissions needed by selected services. Guild officers should receive only the Discord and dashboard access their responsibilities need.
Copy-ready community brief
Design Astral Accord, a fictional Throne and Liberty Discord for about 240
members: active guild players, applicants, returning players and social friends.
Main activities use a current Americas cross-play server confirmed by hosts.
Use America/Chicago for the example community calendar, not a guessed fixed
UTC offset. Record current region/server in every playable listing.
Preserve existing structure on first build; deletions off. Compact entry,
community, grouping, guild, temporary voice and staff areas. Keep strategy
behind reviewed access; no channel per boss, weapon, dungeon or patch.
Welcome: verification to limited Member; optional dungeon/Remnants/guild-event
interests, newcomer/mentor interests, spoiler access and opt-in notices. Staff
review guild/strategy access. No self-granted officer/trusted roles.
Sentinel: conduct, phishing, impersonated officers, account-sale/cheat ads and
unsafe downloads; test new aggressive rules first; private case/appeal route.
Tickets: guild application, member report/appeal, access/service help; distinct
responsible teams, relevant fields only, no account/2FA/recovery/payment secrets.
Group Finder: explicit 6-person co-op dungeon templates and 4-person Remnants of
Nix templates; current region/server/platform pool, activity/tier, self-reported
readiness, host, roles/function preferences, voice, risk and duration. Playing
mentors count inside capacity; actual game invite/readiness remains game-side.
Beacon: dungeon nights and officer-reviewed guild activities with exact dated
schedule, chosen attendance, hosts, reserve list and game-side requirements.
Join-to-Create Voice: 6-person and 4-person group lobbies with creator controls,
transfer and empty cleanup; retain a staff-managed larger briefing room.
Announcements: enable then flag manual weekly schedule creation; date service
transition notices and stop them when superseded.
Social Feeds: enable then flag manual verified publisher-source subscription.
Analytics: public community/LFG/voice participation, excluding private reports
and strategy from community-facing views/exports.
Giveaways: optional legitimate prizes, no game currency/entitlements/access.
Review Channels/Roles/Services and newcomer/member/officer perspectives.
Explain manual finishing/build-report exceptions. No roster sync, account
transfer, game-stat import, readiness verification, game invites or rewards.
A compact channel plan
ENTRY #start-here #rules-and-interests
COMMUNITY #accord-chat #official-news #weekly-plan #learning-library
GROUPS activity-lfg (forum) #newcomer-help
GUILD reviewed briefs and officer-managed strategy/briefing space
VOICE Join a Dungeon Group / Join Remnants → temporary rooms
SUPPORT application/report/help panels → private conversations
STAFF private coordination, application review and service logs
Review before applying
Inspect Channels, Roles, and Services in the review workflow. Preview a newcomer, ordinary Member, reviewed guild member, and officer. Check that public entry remains usable, strategy titles do not leak through summaries, and applicants cannot read other applications or grant themselves officer access.
Run available safety checks, keep deletions off, and read the actual build report. The snapshot/undo workflow has limits: new channels and roles remain and deleted messages cannot be restored. A recovery feature does not replace checking a sensitive permission change beforehand.
Announcements schedules and Social Feed subscriptions require manual finishing steps. Finish them in their services and review detailed panels, templates, and events against the actual report rather than assuming the prompt created everything.
Test: Enter as a new member, verify, find a compatible activity, and request guild access while restricted strategy remains hidden. Repeat from an officer's perspective and check the intended limits.
2. Welcome: Make Belonging Broader Than Guild Readiness
Use Welcome for a short verification path and useful interests. Member access opens social discussion and appropriate public activities. Dungeon Learning, Remnants, Guild Event Notices, and Returning Player Help describe intentions; none should certify readiness or current guild membership.
A greeting can say: “Welcome to Astral Accord. Choose the activities you want, check your current region and server before joining a group, and use the application panel if you want reviewed guild access. Friends are welcome even when they are not on the active roster.” Keep public instructions usable if DMs fail.
Assign officer, reviewer, and strategy roles through staff review. A mentor interest starts a conversation rather than granting access to private player profiles. Verification confirms a Discord interaction, not game ownership, equipment, combat power, or account identity.
Test: Complete entry with DMs blocked, select all interests, and confirm none unlocks officer controls or claims to change the in-game guild roster.
3. Sentinel: Protect Applicants From Scams and Impersonation
Configure Sentinel for phishing, impersonated officers, fake support links, account sales, cheat advertising, harassment, and spam. Service transitions are a good reason to keep official destinations clear: staff should never ask members to hand over account access to a private message claiming to migrate them.
Start new aggressive rules in Testing. Guild abbreviations, item names, and legitimate official links can confuse generic filters. Review false positives and keep reports private. A disagreement about a build or event decision is not automatically a moderation violation; address actual conduct and offer an appeal route.
Discord moderation is not game enforcement. A timeout does not ban a game account, change guild permissions, reverse a trade, or establish cheating. Authorized officers handle their game responsibilities separately, and official support owns account/service issues.
Test: Try harmless dummy content in a staff area and inspect the rule, case, and appeal visibility. Confirm a regular activity host cannot read unrelated reports.
4. Tickets: Separate Recruitment, Reports, and Service Help
Create three Tickets paths: Guild Application, Report or Appeal, and Access/Service Help. Applications ask for current region/server, character name where needed, activity interests, broad availability, self-reported readiness, and expectations. Keep personal information proportional to the actual guild decision.
Reports ask for message links, time, relevant activity, and concise context. Service help asks for platform and the official step that failed, with redacted error information if useful. Never request passwords, 2FA or recovery codes, account tokens, payment information, or credentials for a game or hosting service.
Accepting an application can grant reviewed Discord access where configured. An authorized officer still handles the in-game invitation and any game-side role. A help ticket does not transfer an account to the new operator or make an opt-out choice for the member. Link official instructions and identify the responsible next step.
Test: Submit an application and a report as members. Confirm recruiters cannot browse moderation reports, applicants cannot read one another's answers, and acceptance grants only intended Discord access.
5. Group Finder: Replace Generic Defaults With Actual Activities
The currently inspected setup keyword list recognizes Throne and Liberty as TnL. That recognition is useful, but the inspected starter-template function does not provide a dedicated Throne and Liberty activity library. Create explicit Group Finder templates rather than trusting a generic five-person default.
Create the first template
Template Name: Co-Op Dungeon — Learning Party
Game: Throne and Liberty
Default Party Size: 6
Default Expiry: 2 hours
Description: Six playing positions including host/mentor. State current
region/server/platform pool, exact dungeon/tier, self-reported readiness,
functional role needs, learning pace, voice and duration. Host verifies actual
entry requirements and forms game party. No automatic equipment checks.
Use actual activity needs when discussing roles or weapon setups. Do not make an optional preference a permanent class identity or assume a self-selected label proves the person can perform the role. Ask the host to state what the group needs and what the learner wants to practice.
| Template | Target size | Required context |
|---|---|---|
| Dungeon learning | 6 | Exact dungeon/tier, playing mentor, entry requirements, pace. |
| Dungeon repeat session | 6 | Current activity, expected familiarity, time budget. |
| Dimensional Trial planning | 6 | Exact current activity/requirements checked by host, goal. |
| Remnants of Nix | 4 | Current access, risk, hostile non-party context, communication. |
| Returning-player orientation | 3 chosen attendees | Small teaching/briefing target, current server and scope. |
| Guild brief review | 2 chosen reviewers | Community planning target, restricted access and owner. |
The last two are community coordination sizes, not new game-mode limits. Large guild activity attendance belongs in Beacon with an actual officer plan. Do not force siege attendance into a small-party template or infer a current raid requirement from a historical roster screenshot.
Example live listing
Americas cross-play — co-op dungeon learning
Roster: 4/6 including one playing mentor; two positions open
Server: current character-selection server, confirmed by host before invite
Activity: exact dungeon/tier stated in the listing before opening
Readiness: self-reported; actual entry requirements checked in game
Purpose: patient explanation and retries, not a fast repeat clear
Roles: host states functional needs; players discuss current weapon setups
Voice: listening welcome, questions encouraged before each unfamiliar step
Duration: 90 minutes with an agreed stopping point
Discord joining does not form game party, invite to guild or verify gear.
Keep the listing current if the server, activity, tier, or purpose changes. A returning member's old server role is not proof of compatibility after consolidation or a transfer. Resolve the mismatch before the group waits inside a dungeon entry path.
Test: Fill six including the mentor and waitlist the next person. Open a Remnants listing and confirm it stops at four, with the risk clearly stated before joining.
6. Beacon Events: Plan Guild Attendance Without Inventing Capacity
Use Beacon Events for a Thursday Dungeon Learning Night at 20:00 America/Chicago for ninety minutes. An illustrative cap of eighteen means three six-person teams if enough hosts are available. It is an organizing choice, not a guild roster limit or raid minimum.
For guild raids, territory activity, or siege coordination, an officer checks the current in-game requirements, schedule, roster, and communication plan before publishing the event. State the actual activity, prerequisites, chosen attendance cap, host, reserve route, and meeting point. Count playing mentors and leaders inside relevant groups.
RSVP does not register a character, reserve game admission, verify combat power, join a guild, or grant rewards. Use one or two reminders and let Beacon own them. For long activities, choose a persistent briefing room or separately managed voice rather than assuming event-created voice lasts through the whole operation.
Test: Fill eighteen illustrative signups with three hosts, then remove one host. Adjust teams or attendance before the reminder rather than promising an unsupported third group.
7. Join-to-Create Voice: Keep Six-Person and Four-Person Groups Distinct
Configure Join-to-Create Voice with Dungeon and Remnants lobbies creating rooms for six and four respectively. Enable supported creator ownership, transfer, and empty cleanup. A larger guild briefing should use an appropriately managed separate room.
Discord occupancy is not game admission or party creation. The host sends game invitations and checks the selected activity. Review category access so a public applicant cannot enter restricted strategy merely by creating a room.
State voice expectations in each listing. A learning group can welcome listeners and questions; an activity with fast coordination can explain what participation requires before people commit. Keep written preparation available so the first instruction is not delivered only after everyone enters voice.
Test: Create both room types, transfer ownership, and empty them. Verify cleanup, ordinary-member access, and that temporary ownership grants no officer or strategy permissions.
8. Announcements: Date Guild Decisions and Service Notices
Finish Announcements schedules manually. Publish a weekly America/Chicago plan linking events, current application guidance, and reviewed activity notes. Use opt-in roles rather than notifying every social member about each guild task.
Keep a dated service notice separate from evergreen onboarding. The planned November transition deserves a maintained official link and a named staff reviewer, not a recurring promise that support, shop, and account paths will remain unchanged. Pause or replace a notice when the official schedule changes.
Preview the actual destination, mention, time zone, and links. A live send posts a real message. If an event changes, update Beacon and one maintained announcement rather than leaving competing schedules across channels.
Test: Preview the weekly plan and a transition notice, verify recurrence and end conditions, and confirm Beacon owns event reminders without duplicate pings.
9. Social Feeds: Verify the Current Publisher Source
Throne and Liberty has no curated entry in the currently inspected catalog. Use the generic Steam route in Social Feeds after verifying the official Steam page, App ID 2429640. Absence of a tile does not mean every supported feed route is unavailable.
The inspected adapter accepts a numeric ID, follows publisher community announcements, and declares a 900-second polling default. It does not guarantee immediate delivery, a fixed fifteen-minute service, or every support, operator, server, and website notice. Staff should keep current official news and support destinations available directly.
The service transition is a reason to recheck the actual source and destination after the handover, not assume a feed proves the new support path works. Preview first; initial checking avoids a backlog and the documented Test action posts for real. Publisher news does not automatically revise guild requirements or event eligibility.
Test: Confirm App 2429640 and publisher identity in preview, use a staff destination for a real test, and assign an owner to review the source around the transition.
10. Analytics: Measure Participation, Not Character Readiness
Use Analytics to ask whether applicants reach useful activities, whether dungeon-night times fit members, and whether newcomer groups return. Compare several weeks and ask what blocked participation. An unclear server label or missing mentor may explain an empty listing better than a lack of enthusiasm.
Restrict exports and public views. Exclude private reports, applications, readiness notes, and strategy areas from community-facing comparisons where appropriate. Quiet players and listeners can participate well without producing a large message count.
Discord activity does not verify combat power, equipment, character progress, guild rank, contribution, rewards, or siege results. A self-reported profile remains a report and a staff review remains a community observation. Do not turn a chat leaderboard into raid eligibility.
Test: Review an illustrative period and identify one practical scheduling or onboarding improvement. Confirm ordinary members cannot obtain restricted applicant or strategy data through exports.
11. Giveaways: Keep Prizes Separate From Guild Decisions
Use Giveaways for an optional legitimate celebration with eligibility, closing time, claim route, and manual delivery responsibility. Check region and redemption terms for a purchased gift code before offering it.
Do not promise Lucent, gear, guild access, contribution, or game entitlements YourBot cannot grant. A drawing does not authenticate a trade or change game rules. Never request account passwords, tokens, two-factor or recovery codes, or payment data from a winner.
Keep prize participation separate from applications, event priority, and officer decisions. A harmless staff-only symbolic drawing is enough to verify the workflow before using a real prize.
Test: Run the staff drawing and inspect entry rules, winner notification, claim visibility, and the manual fulfillment note.
Keep Guild Membership and Readiness Separate
Astral Accord's social community can remain welcoming while specific activities have requirements. A six-person learning dungeon, a four-person Remnants group, and a guild activity may need different preparation. State requirements on the activity rather than making one public role the definition of belonging.
Officers handle actual guild invitations and ranks in the game. A Discord role can help route communication, but it should not claim automatic synchronization. When someone leaves a guild or changes server, review the related Discord access deliberately, including direct links and exports, instead of assuming another system removed it.
Readiness profiles should be opt-in and narrow. Ask for the information a host needs, label it self-reported, record when it was reviewed, and let the member correct or withdraw it. A player returning after an update may need help refreshing context rather than a public judgment based on an old number.
Make review useful to the member
A review can end with a practical next step: join a learning group for the named dungeon, confirm the current entry requirement in the game, or update a server label before the next invitation. It does not need to produce a permanent ready/not-ready badge covering every activity. Someone prepared for one task may be learning another.
Keep the scope and date visible. A profile reviewed for a dungeon evening should not silently become proof of readiness for a later guild activity with different requirements. When a patch, server move, or member update changes the context, mark the relevant note for refresh. The purpose is to avoid confusion for both host and participant, not to create an additional gate to social membership.
Give members a correction route that does not require a public argument. A private ticket or the proposed register can let them explain what changed, withdraw an optional note, or ask a reviewer to reconsider. Staff should record the reason for a decision in a limited audience and avoid publishing unnecessary equipment or personal details.
Match Activity and Server Context Before a Guild Night
Use the current region and server names visible in the game. The Americas consolidation means old community labels can remain familiar while no longer describing the actual environment. A host should confirm the destination before invitations, especially when returning members or platform-specific servers are involved.
Check each activity independently. The official co-op description supports six; the Nix release notes specify four for Remnants. Raid and portal requirements can change, and a siege's large participation is not one ordinary party. An officer should verify the current activity interface and published rules instead of copying a generic cap from another event.
Use a short pre-session brief: purpose, server, exact activity, risk, prerequisites, host, group plan, communication, and stopping point. If compatibility or readiness fails, decide whether to help the member prepare, choose another activity, or reschedule. Do not quietly change a learning session into a higher-risk run after people signed up.
Treat Remnants separately in the conversation as well as the template. Its four-person party structure and hostile non-party context mean a dungeon invitation is not an adequate briefing. The host should confirm the intended activity, what participants are comfortable risking, and how the team will communicate before launch. Keep that agreement understandable without requiring members to read a long historical strategy thread.
For larger guild coordination, name deputies before the event. One officer can manage the current attendance record while another handles a game-side responsibility. State how a late member receives current instructions and how an unavailable host is replaced. A role menu alone does not establish that a person accepted the job; confirm it with the actual volunteer.
After the session, revise only what the next host needs. Record a changed prerequisite, an unclear instruction, or an unfinished project with an owner and date. Keep detailed conduct reports out of the shared brief. This preserves useful learning without turning routine guild coordination into a public archive of individual mistakes.
Prepare for the November Service Transition
The October 8 official notice schedules maintenance beginning November 10 and explains that player data, characters, progression, and entitlements are to transfer to NC under the described process. As of October 29, use that as the current official plan, with exact maintenance details subject to later notice. Do not invent a downtime duration or tell members that YourBot carries out the transfer.
The 4.18 preparation notes describe temporary shop/Auction House changes and settings that will reset across the preparation/transition window. They also separate future November 10 changes from the 4.18 release. Link the actual notice rather than summarizing a future system as already available.
Keep account decisions with the member and official support. The transition notice includes a time-sensitive opt-out process and consequences; direct anyone considering it to the official explanation instead of collecting their decision in a guild form or advising them from an outdated summary. Officers do not need credentials to help someone find the right page.
Assign one staff reviewer to update support links, service notices, feed identity, and event assumptions after the transition. Preserve old notices as dated history and make the current one obvious. A guild can plan sensibly without promising that every external service or account path will behave exactly as before.
Use a small change register for the community's own instructions. Each entry can identify the affected link or workflow, the official source checked, the person reviewing it, and the next action. “Needs review” is an honest temporary status when a new operator's support destination has not yet been confirmed. It is better than leaving an old page presented as current guidance.
Do not let a scheduled Discord message become the source of truth for service availability. A recurring event near maintenance should point to the latest official schedule and give a clear community fallback. Once the service returns, confirm the actual player path before restoring the ordinary plan. YourBot can communicate that decision; it cannot establish that an external account or game service is working for every member.
Add a Guild Readiness and Brief Register Only When You Need It
Launch with built-ins and a small maintained learning area. If officers repeatedly lose current readiness context or approved briefs, check the Marketplace before requesting a custom build. A maintained existing workflow may already fit.
The proposed Guild Readiness and Brief Register stores opt-in, self-reported profiles and reviewed community briefs. It does not replace Group Finder, Beacon, Tickets, or Announcements. It records what members and reviewers said, not what the game independently verified.
Copy-ready Plugin Builder specification
Build Guild Readiness and Brief Register for Astral Accord. Proposed manual
workflow only; version 1 has no external network access, account integration,
stat import, operator-transfer function or credential storage.
Roles: Register Admin configures access/retention; Member submits/corrects or
withdraws own opt-in profile; Reviewer records a limited community review;
Brief Author writes permitted activity notes; Officer approves another author's
brief. Self-selected interests grant no reviewer/officer authority.
Destinations: member-safe activity reference, restricted readiness review,
guild/strategy briefs and private audit. A profile is private by default;
public summaries contain no personal readiness, applicant or strategy detail.
Profile fields: server_id, immutable profile_id, member_id, consent scope,
current region/server/platform-pool note, activity interests, self-reported
readiness note, optional resource links, reviewer_id, reviewed_at, review_due,
revision, change reason and status. Avoid detailed inventory or unnecessary
personal data. No passwords, tokens, recovery codes or account-transfer forms.
Brief fields: server_id, immutable brief_id, actual activity, purpose, current
environment, host/coordinator, chosen attendance versus actual game limit,
source/check date, risk/prerequisites, visibility, content, reviewer,
revision, effective date and linked built-in event/listing reference.
Profile states: submitted -> reviewed -> current -> needs refresh -> withdrawn.
Brief states: draft -> review -> approved -> active -> needs revision -> archived.
Relevant server/activity-rule changes flag stale records; approval cannot
silently survive a changed prerequisite. Keep revision/review reasons.
Views/actions: my profile, permitted current briefs, private reviewer queue,
stale records, revision history, consent correction/withdrawal, archive and
authorized export. Filters: activity, server, review age, status, visibility
and coordinator. Proposed command concepts: readiness submit, readiness
update, brief search, brief approve; these are new proposed commands.
Validation: bounded text/allowed states, required context/owner, safe display,
no secrets; warn on duplicate profiles or active briefs; link superseded
records; revision checks prevent concurrent overwrite; require reason for
changed access or readiness review. Do not fetch submitted links.
Authorization: server_id/current roles/ownership/visibility enforced on every
search, direct read, write, transition, preview and export. Members see their
own profile only unless policy explicitly permits more; reviewers see their
assigned scope. Recheck revoked roles at action time. Copied IDs cannot bypass
privacy or reach another server. Exports filter both records and fields.
Audit actor/action/time, record/revision and reason with restricted access.
Admin chooses retention, withdrawal, deletion/anonymization policy. Explain
that review is a community observation, not game verification or entitlement.
No roster sync, game invitations, rank/gear verification, currency/rewards,
server control or account migration. Built-ins retain groups/events/support.
Acceptance: other-member private profile denied; other-server ID denied;
revoked reviewer denied; public snippets/exports omit profiles/strategy;
concurrent edit conflict; withdrawal handled; changed server marks stale;
changed prerequisite invalidates approval; audit follows access policy.
Review, test, and continue through the SDK
Review the Plugin Builder plan, source, manifest, data model, and requested capabilities. Follow current draft review and run options. Validation does not establish correct privacy, consent handling, or current game requirements.
Test members, reviewers, authors, officers, and revoked staff. Try direct profile and brief identifiers, previews, altered requests, and exports from another server. Confirm failures reveal no private name or title. Change a server label or prerequisite and verify the current status/approval needs refresh.
Continue downloaded source in Visual Studio Code using the current SDK and developer testing guide. Distinguish temporary Dev Bot testing from operational private installation. Recheck capabilities after changes and use the Dev Portal publication/review workflow for optional Marketplace distribution. This specification is proposed, not a built or tested plugin.
Run a Complete First-Week Member Journey
| Scenario | Successful result |
|---|---|
| Newcomer enters without DMs | Public verification and first activity remain clear. |
| Mentor joins a dungeon party | Six total playing positions, mentor included. |
| Member opens Remnants listing | Four-player limit and risk differ visibly from dungeon. |
| Returning member has old server role | Actual current region/server checked before invitation. |
| Applicant requests guild access | Private review; game-side invitation remains explicit. |
| Event loses a host | Teams/attendance revised, no invented game admission. |
| Temporary room empties | Correct ownership/cleanup without officer authority. |
| Member withdraws profile or reviewer leaves | Direct access and exports respect changed permission. |
| Service instructions change | Dated notice, links, source and affected briefs reviewed. |
Fix confusing access, stale names, and missing hosts before adding automation. The first week should show that members understand the current game context, not merely that many Discord services are enabled.
Frequently Asked Questions
Can PC and console members play together?
The official FAQ supports cross-play among PC Steam, PS5, and Xbox Series X|S, with designated PlayStation-only servers as an exception. Check actual region/server and current released rules.
Does cross-play mean cross-progression?
No. The official FAQ states cross-progression is not supported. YourBot does not move character progress between platforms.
Is every activity a six-person group?
No. Co-op dungeons use six in the official gameplay description; Remnants of Nix has a four-player party maximum in its release notes. Raids, portals, sieges, and community attendance need separate checks.
Does Group Finder recognize Throne and Liberty?
The inspected setup keyword maps it to TnL, but no dedicated activity starter template exists in that function. Create correct explicit templates rather than trusting generic five-player defaults.
Does Discord acceptance add someone to the game guild?
No. It grants only configured Discord access. Authorized officers handle the actual game invitation and game-side permissions.
Can YourBot verify readiness or perform the service transfer?
This workflow does neither. Profiles are opt-in human reports; account/service processes remain with the member and official operator.
Is the custom register required?
No. Start with built-ins and a few maintained briefs. Add the proposed register when recurring review, privacy, and revision needs justify it.
Build a Guild Community With Current, Clear Context
Throne and Liberty organization works when server compatibility, activity limits, reviewed access, and ownership are explicit. Start Your Server establishes the Discord foundation, and the ten built-ins operate its daily workflows. Game rosters, characters, eligibility, territory, rewards, and service transfers remain game-side.
When members can find the right group and trust the current instructions, Plugin Builder can support a narrow readiness and brief register that records human review without pretending to read the game.