A Phasmophobia Discord should help investigators agree on difficulty, experience, communication, and session goals before anyone enters a contract. Use YourBot to welcome newcomers, assemble compatible four-person teams, schedule teaching nights, create temporary voice rooms, and maintain useful learning notes. Keep the actual investigation, equipment, evidence, and game-side voice settings inside Phasmophobia.
The most common organizing mistake is advertising four students plus a playing mentor. The developer's game page describes four-player online co-op, so the mentor occupies one of those four places. Another mistake is promising a beginner-friendly evening without explaining whether the group wants patient discovery or fast answers from experienced players.
This guide follows Lantern Watch, a fictional 240-member community spanning PC and supported console players, with both VR and non-VR interests. It runs newcomer investigations, difficulty practice, and occasional seasonal nights. Community names, schedules, and teaching policies are examples; Discord attendance is separate from a game's lobby and contract.
Start With the Right Phasmophobia Community Model
Four investigators form one playable team
Use four as the maximum playing roster for an investigation. A leader, a mentor, and two new investigators fill it. Someone waiting in Discord has not gained a fifth game slot. If a community night attracts twelve players, organize three separately led teams of four rather than promising one twelve-player investigation.
The same distinction applies to voice. A discussion room may hold more people before departure, but the game roster still needs its own limit. Ask each leader to confirm their playing roster and identify who is waiting. Avoid adding observers to a private conversation without the team's consent simply because they are not playing.
A short two-person practice session can be a useful chosen target when both players agree. It does not redefine the game's four-player capacity. Make it clear whether a listing needs a full team or is intentionally smaller so members do not wait for nonexistent missing slots.
Crossplay is useful; compatible setup still matters
The developer describes cross-platform multiplayer. The console voice-recognition update explicitly covers PlayStation 5, PS VR2, and Xbox Series X/S, while the Steam edition supports PC play. Keep supported players together for conversation and match the actual client build and joining settings before a session.
Use platform and VR preference as practical listing context, not as assumptions about skill. A VR player may need a slower pace or additional setup time; another may be experienced and ready immediately. Ask what helps rather than imposing a permanent beginner role on a device choice.
If an update creates a real compatibility issue, publish a dated notice with its source and affected scope. Do not preserve old launch-era limitations after they change. In particular, the official voice-recognition announcement establishes console recognition support; a guide should not repeat the old blanket claim that console players cannot use it.
Agree on advice, spoilers, and investigation style
Lantern Watch offers two teaching styles: guided discovery, where the mentor prompts observation, and direct explanation, where participants want efficient answers. Both are legitimate. Ask before revealing a complete solution or equipment routine to someone who wants to learn by investigating.
Record the intended difficulty or custom settings and any equipment contribution agreement. A vague “chill” label does not explain whether players expect a low-pressure learning run, a difficult contract with friendly conversation, or a quick collection of rewards. Use a plain sentence describing success and the stopping time.
Keep detailed learning notes in spoiler-aware areas. A member should be able to join beginner LFG without seeing every ghost behavior or solution in channel titles. Spoiler access is a preference, not a rank that proves knowledge or readiness.
Seasonal activities need an expiry
An event template is useful only when its event is actually available. For the 2026 Crimson Eye iteration, the official announcement gives October 8 through November 1. The separate Twitch drop ended October 15 and the double-XP/rewards period ended October 22. Those earlier windows must not be advertised as benefits of an October 29 session.
Use a normal investigation template as the enduring foundation, then add a dated seasonal variant. When the event ends, retire its scheduled posts and active listing defaults. Historical event notes can remain in a labeled archive without continuing to promise current rewards.
The Community We Will Build
Lantern Watch's weekly rhythm is a newcomer evening, a small difficulty-practice session, and an optional weekend challenge. Mentors teach; Moderators handle conduct; Event Leads coordinate rosters. One person can have several responsibilities, but volunteering to teach should not automatically grant access to private reports.
YourBot's role in the community
| Service | Community use |
|---|---|
| Welcome | Offer clear entry, experience preferences, and spoiler choices. |
| Sentinel | Address unsafe links, harassment, impersonation, and account scams. |
| Tickets | Route private reports, access help, and mentoring concerns. |
| Group Finder | Fill compatible investigations with correct playing counts. |
| Beacon Events | Organize teaching nights and multi-team attendance. |
| Join-to-Create Voice | Provide temporary team rooms and debrief space. |
| Announcements | Publish dated plans and event-window notices. |
| Social Feeds | Follow configured Phasmophobia publisher news. |
| Analytics | Identify Discord onboarding and participation problems. |
| Giveaways | Run occasional legitimate community drawings. |
1. Create the Foundation With Start Your Server
The owner should use Start Your Server to design the Discord and review its changes before applying them. Grant permissions needed for the planned actions and place YourBot above ordinary roles it assigns. Preserve staff hierarchy rather than granting broad authority to every mentoring role.
Distinguish Discord permissions from dashboard authorization. Follow the access-level documentation when delegating service pages. A Discord Event Lead role does not automatically grant every dashboard control, and current dedicated Start Your Server documentation describes an owner workflow.
Copy-ready community brief
Design a compact Discord for Lantern Watch, a fictional240-member Phasmophobia
community with supported PC/console, VR/non-VR players and mixed experience.
Keep existing channels/roles/messages on first pass. No deletions in this build.
Newcomers need rules, verification, limited Member access and one clear first activity.
Offer New Investigator, Mentor Interest, Guided Discovery, Direct Explanation,
VR Interest, Event Notices and opt-in Detailed Learning Notes. These are preferences,
not verified skill or staff authority. Moderator/Event Lead are never self-selectable.
Use one practical investigation LFG area. Listings carry current build, region/timezone,
platform/joining compatibility, difficulty/custom settings, teaching style, equipment
agreement, current roster, voice plan and expected duration. Four total playing
investigators includes leader and mentor. Larger community nights split into separate
four-person teams, each with a leader; RSVPs do not create game lobbies.
Plan Welcome, Sentinel, Tickets, Group Finder, Beacon Events, Join-to-Create Voice,
Announcements, Social Feeds, Analytics and Giveaways. Private ticket routes handle
conduct reports, technical/access help and mentoring concerns. Keep detailed solutions
out of public channel titles. Create temporary four-user team voice rooms; explain
Discord arrangement/debriefing separately from native game audio/recognition.
Keep staff/private support and automated news out of ordinary activity comparisons.
Date seasonal templates and retire reminders after their actual event window.
No passwords, authentication codes, game-account tokens or private real-world details.
Do not claim to read evidence, ghost identity, player levels, equipment or rewards.
Show Channels, Roles and Services for review, including ordinary-member perspective.
Announcements schedules and Social Feed subscriptions require manual finishing.
Do not execute game settings, create game parties or deploy a custom plugin.
A compact channel plan
START HERE
rules-and-first-investigation
welcome-and-interests
community-notices
INVESTIGATORS
general
beginner-help
investigation-lfg
learning-notes [spoiler opt-in]
ACTIVITIES
events
official-news
create-team-room [voice lobby]
SUPPORT
contact-staff
STAFF [private]
reports
mentor-and-event-review
Use threads for individual learning topics rather than a permanent channel for every ghost or location. Public beginner-help should make it possible to ask a question without first reading a complete solution library.
Review before applying
Review Channels, Roles, and Services. Preview the design as an arrival, Member, opted-in learner, and mentor. Check that newcomers can reach the instructions and detailed notes remain behind their intended preference gate. Fix safety-check findings and keep deletion disabled on this first pass.
Read the build report and finish missing settings. Announcements schedules and Social Feed subscriptions require manual finishing steps. A prompt asking for seasonal reminders is not proof those reminders exist or expire correctly.
A build saves a pre-build snapshot; download that backup before further structural changes. Read the after-build limitations. Undo is not a complete Discord restoration: added roles/channels can remain and deleted messages cannot return. Test: a member with DMs blocked reaches entry instructions, chooses a teaching preference, finds LFG, and opens support without seeing staff reports.
2. Welcome: Ask How People Want to Learn
Use Welcome to present a short visible path: read rules, complete the selected verification interaction, receive Member, and choose interests. Verification establishes a Discord interaction, not a player's identity, level, platform entitlement, or investigation skill.
Offer New Investigator, Guided Discovery, Direct Explanation, VR Interest, Detailed Learning Notes, and Event Notices. Mentor Interest can indicate willingness to help, while staff review who leads official teaching sessions. Do not make a self-selected interest grant moderation or private-ticket access.
A useful greeting is: “Welcome to Lantern Watch. Choose the kind of learning you enjoy, then join an investigation that names its difficulty and voice plan. A playing mentor counts inside the four-person team.” This answers a real first-session question without asking newcomers to learn every service at once.
Keep essential instructions in the channel because direct messages may fail. Let members change preferences later without explaining themselves publicly. Test: onboard two members choosing different advice styles, confirm both can find an appropriate listing, and ensure opting into learning notes changes visibility without granting staff authority.
3. Sentinel: Make Scares Voluntary and Harassment Unwelcome
Configure Sentinel for suspicious downloads, fake support, account phishing, spam, harassment, and discriminatory abuse. A horror game's atmosphere does not justify targeting someone who asked to stop a joke. Establish a clear difference between consensual in-game scares and conduct that follows a member into Discord.
Put aggressive new rules into Testing first. Review legitimate game discussion and official links before enabling actions. A frightened reaction or a technical microphone discussion should not trigger a simplistic rule meant for harassment or spam. Give staff a way to inspect cases and explain decisions privately.
Discord moderation is not game enforcement. A timeout does not remove an investigator from a lobby, verify cheating, or change a game account. Members and authorized organizers handle their game session separately. Do not claim image understanding or other unverified scanning capabilities merely because a report includes a screenshot.
Test: use harmless staff samples for an unsafe-link pattern and a conduct report. Confirm the right team sees the case, ordinary mentors cannot access it, and the response describes only the Discord action actually taken.
4. Tickets: Give Private Concerns a Clear Route
Create three Tickets paths. Member Report asks for a relevant message link, short context, and immediate concern. Technical/Access Help asks for platform, current build, affected joining/audio step, approximate time, and a redacted error. Mentoring Concern asks for session label, advice preference, what was uncomfortable, and the desired follow-up.
Route reports to Moderators, technical help to a small support team, and mentoring feedback to designated reviewers who are not automatically the subject of the complaint. Explain who can read the intake and avoid sharing sensitive material with every Event Lead.
Never ask for passwords, two-factor codes, recovery codes, session tokens, or payment details. A ticket can help someone find official support, but it does not authenticate a game account or guarantee a technical fix. Close with a clear next action and leave a route to report that the problem remains.
Test: open each intake as a Member, inspect team permissions and closed-ticket access, then remove a reviewer's role and try the old link. Confirm a mentor outside the assigned team cannot read a private complaint.
5. Group Finder: Put the Investigation Agreement in the Listing
Phasmophobia is not in the currently inspected automatic setup-detection list, so create explicit templates manually. Its Social Feeds entry does not supply correct LFG defaults. Use Group Finder to make the actual four-person investigation and its expectations clear.
Create the first template
Template Name: Guided first investigation
Game: Phasmophobia
Default Party Size: 4 total, including leader and playing mentor
Default Expiry: 2 hours, chosen for near-term community listings
Description: State current build/joining compatibility, region, intended difficulty,
guided-discovery versus direct-explanation style, equipment contribution agreement,
current players, native-game/Discord voice plan, VR needs and expected duration.
Do not post a private lobby code publicly. Leader handles game invitations separately.
Keep the wording understandable without demanding a verified level role. If an activity has a real game-side prerequisite, name it and ask the organizer to check it in game; a Discord label cannot inspect progression.
| Additional template | Target | Required context |
|---|---|---|
| Direct-explanation beginner run | Up to 4 | Mentor included, advice style, difficulty and equipment agreement. |
| Difficulty practice | Up to 4 | Exact selected difficulty/settings, learning objective and review point. |
| Custom-setting experiment | Up to 4 | Agreed settings, consent, expected risk and stopping time. |
| VR-friendly relaxed investigation | Up to 4 | Comfort/pacing preference, current compatibility and voice setup. |
| Seasonal event crew | Up to 4 | Actual active event, selected location, event toggle and expiry date. |
| Two-investigator observation practice | 2 chosen players | Deliberately smaller roster, goal and method of debrief. |
Example live listing
Guided first investigation — patient evidence discussion
Build/pool: current compatible game build, crossplay joining checked by leader
Region: Europe evening; confirm connection and start time before departure
Difficulty: agreed beginner setting named in the lobby before starting
Style: guided discovery; ask before giving a complete answer
Roster: 3/4 total, including one playing mentor; one place open
Equipment: organizer explains contributions before starting, no surprise demands
Voice: Discord for forming/debriefing; agreed native-game audio plan during contract
VR: tell leader about comfort/setup needs; breaks welcome
Duration: 75 minutes; private lobby details through approved access route
Joining the Discord listing does not create a game lobby, issue an invite, or ensure equipment readiness. Update the listing when a group changes difficulty or advice style so later arrivals do not join a different agreement. Test: fill four places including the mentor, verify a fifth waits, and ask a newcomer to explain the session's voice and spoiler expectations before joining.
6. Beacon Events: Split Community Attendance Into Playable Teams
Use Beacon Events for “Lantern Watch New Investigator Night.” Twelve playing attendees become three teams of four, each with a named leader and any playing mentor counted inside that team's four. Confirm that all three leaders are available before advertising twelve usable places.
The event description names the advice style, planned difficulty range, current build requirements, timezone, expected duration, voice arrangement, and how team assignments will be communicated. Keep private lobby codes out of public reminders. If only two leaders can attend, reduce the playable plan rather than leaving eight newcomers to improvise.
A debrief can gather all twelve afterward, but that discussion is not one investigation. Beacon RSVPs do not create lobbies, reserve game places, register rewards, or verify a player's level. Use a waitlist and a clear cancellation procedure.
Test: sign up the three playing leaders, fill the remaining nine places, then withdraw one leader. Confirm the organizer revises the team plan and communicates the change instead of treating the original RSVP count as a guarantee.
7. Join-to-Create Voice: Arrange Teams and Respect Native Audio
Configure Join-to-Create Voice with a team lobby, a four-user default, creator controls, appropriate ownership transfer, and cleanup when empty. Keep a separate debrief room only when the larger community session needs it; do not create permanent rooms for every location.
Agree on how Discord is used during a contract. Native game audio and recognition are part of the actual game experience; a Discord conversation does not configure them. Leaders can use Discord to assemble the team and debrief, then follow the group's agreed in-game communication plan. Test the selected setup before a difficult session rather than promising a particular microphone routing works everywhere.
The official console recognition update covers supported PS5, PS VR2, and Xbox Series hardware. Link that guidance when someone needs setup help, and recheck current language/options rather than copying historical limits. Provide a respectful text/help route for members with different communication needs.
Test: create two rooms, check member controls and ownership transfer, confirm the group can explain its game/Discord audio plan, then empty the rooms and verify cleanup without affecting the lobby.
8. Announcements: Date Seasonal Plans and Retire Them
Create Announcements schedules manually after the foundation build. Use a weekly plan for beginner sessions and difficulty practice, with opt-in Event Notices. Avoid duplicating Beacon's final reminders; link the event rather than sending competing pings.
A seasonal post needs the actual event window, selected activity, source link, and expiry. For the 2026 Crimson Eye period, do not reuse the earlier Twitch-drop or double-rewards copy after those windows end. If a scheduled investigation moves beyond November 1, replace its seasonal promise with an ordinary activity unless a new official extension is verified.
Keep future updates separate from live features. The preparation patch discusses a planned November Unity 6 update; that announcement is not proof the engine update was already available in October. A dated source and a simple current-status check prevent an exciting roadmap item from becoming a misleading setup instruction.
Test: preview a staff-only reminder, verify timezone and opt-in mentions, and inspect the schedule's end condition. Confirm no expired event or reward post can recur after its intended window.
9. Social Feeds: Use the Phasmophobia Publisher Source
The inspected catalog includes Phasmophobia, slug phasmophobia, category Action, source steam_news, key 739630, matching the official Steam page. Add the subscription manually in Social Feeds and keep official-news focused on source items.
The inspected Steam adapter uses public news with the publisher community-announcements filter and a 900-second class polling default. That is not guaranteed immediate delivery or a promise to mirror every help article, platform notice, livestream, and patch discussion. Link the developer's news and help destinations when a question needs more context.
Staff should distinguish the original update from Lantern Watch's interpretation. A seasonal-toggle change does not automatically decide which option a teaching team will use. The leader still records that choice in the listing and lobby.
Test: inspect one delivered item for the correct title, original destination, legible formatting, and duplicate/ping behavior. If the channel is quiet, verify both subscription settings and upstream content before diagnosing a failure or inventing a new announcement.
10. Analytics: Measure Welcoming Participation
Use Analytics to ask whether new members find a team, whether beginner questions receive useful responses, and whether teaching nights bring people back. Compare similar periods and ask participants about the experience. A calm investigator who speaks only when they have evidence should not be penalized for low message volume.
Exclude private reports, mentoring concerns, staff review, and automated news from ordinary member comparisons where appropriate. Do not expose who asked for help or create a public ranking of frightened reactions. Staff should understand which channels and time periods a report includes.
These Discord measurements do not reveal ghost identity, evidence gathered, player level, money, equipment inventory, survival rate, correct identifications, or contract completion. A voice session is not a verified successful investigation. Use voluntary debrief feedback to learn whether the advice style and difficulty matched the group's expectations.
Test: compare a human discussion channel with news-only activity and inspect the selected scope. Confirm a viewer cannot recover private mentoring concerns through the overview, then choose one practical onboarding improvement.
11. Giveaways: Keep Prizes Separate From Game Progress
Use Giveaways for an occasional legitimate community prize with clear eligibility, closing time, claim deadline, and delivery responsibility. If using a game key or gift card, verify its platform and region restrictions before announcing it. Do not tie participation to revealing personal account information.
YourBot does not deliver investigation rewards, equipment, account levels, currency, or platform entitlements automatically. It also does not authenticate an outside seller or a trade. Keep the Discord drawing and any separately authorized legitimate prize delivery clearly described.
Avoid prizes that grant authority over newcomers or access to private reports. Publish reroll conditions before the drawing and identify the actual staff contact so an impersonator cannot exploit the result. Test: run a staff-only sample with a harmless fictional prize, confirm entry and closing behavior, and practice a winner message without purchasing or transferring anything.
Make Teaching Feel Like an Investigation
A teaching session should begin with an agreement about explanation style, pace, equipment contributions, and when to pause. Guided discovery works when a mentor asks what a newcomer noticed and helps them reason from it. Direct explanation works when the group wants concise answers. Problems arise when neither expectation is stated.
Use a brief debrief with three questions: what did the team observe, what remained uncertain, and what will they try next time? Keep notes specific to the difficulty and relevant settings. A result from one setup should not become an unconditional rule for every contract or later patch.
Do not require public performance reports from nervous newcomers. Let a learner ask privately for another mentor or a slower session. Feedback should improve the teaching process rather than establish a ladder of supposedly verified expertise based on Discord activity.
Respect the Game's Audio and the Team's Comfort
Agree on the native-game communication plan before entering a contract. Discord can help people assemble and debrief, but it does not replace the game's proximity, radio, recognition, or input setup. Consult current official guidance when a player changes platform or microphone, and test in a low-pressure setting.
Avoid telling a player that their hardware cannot support a feature based on an old launch article. The console voice-recognition announcement is a concrete example of changed support. At the same time, do not extrapolate its original language list into a permanent limit; follow the current game options and official updates.
Give people permission to stop, take breaks, or change the activity. VR comfort, hearing, speaking, and anxiety needs can differ without making someone less welcome. A team that adjusts the plan respectfully is more likely to return than one that treats endurance as proof of belonging.
Run Seasonal Nights Without Carrying Expired Promises
For the October 29, 2026 context, Crimson Eye remains within its announced October 8–November 1 window. The announcement lists specific participating locations, including standard Point Hope rather than Point Hope Restricted. Verify the selected map against that actual list instead of assuming every location participates.
The v0.19.1.0 preparation patch introduces the seasonal-event toggle. Ask the leader to state the intended choice and confirm it in the actual session. A newcomer run can use an ordinary setup when the group wants that experience; a seasonal label should not override consent about difficulty or expectations.
Retire the seasonal template when its window ends. Preserve useful learning notes as dated examples, with event-specific rewards and conditions labeled historical. The enduring community activity is a compatible investigation and a good debrief, not an expired campaign promise.
Add an Investigator Learning Notebook Only When You Need It
Launch with the built-ins and a few useful learning threads. Check the Marketplace for an existing maintained solution before creating a new one. The proposed Investigator Learning Notebook becomes useful when topics need spoiler-aware access, difficulty context, review dates, and revisions that ordinary pinned messages no longer manage well.
It is a manually maintained training library and debrief register, not a ghost detector. Group Finder fills teams, Beacon schedules attendance, Tickets receives private concerns, and Announcements sends notices. The notebook stores lasting lessons with the conditions under which people learned them.
Copy-ready Plugin Builder specification
Build Investigator Learning Notebook for Lantern Watch's Discord server.
Purpose: human-authored, spoiler-aware training notes and voluntary debrief lessons.
Version 1 uses no external network access, game telemetry, credentials or account links.
Roles: administrators configure; reviewed mentors approve learning content;
authors maintain their drafts; Members read published notes allowed by their current
spoiler preference. Mentors do not automatically read private moderation/support data.
Fields: generated record ID, authenticated Discord server scope, topic, author ID,
difficulty/custom-setting context, optional game-build context, spoiler level,
observed lesson, uncertainty, suggested next practice, source links, review date,
reviewer ID, state, revision and created/updated timestamps. No compulsory member
performance histories, real-world personal details or private ticket transcripts.
States: draft -> mentor reviewed -> current -> needs revision -> archived.
Only authorized mentors publish or change spoiler classification. Authors can edit
their drafts; changes to current notes create a new reviewable revision.
Overdue review visibly marks a note stale rather than silently claiming it is current.
Screens: beginner-safe library, spoiler-filtered topic search, my drafts, mentor
review queue, stale notes, authorized revision history and administration.
Filters: topic, difficulty context, spoiler level, state, reviewer and review date.
Suggested custom commands to create and validate, not existing service commands:
/lantern-notes browse, /lantern-notes draft, /lantern-notes review,
/lantern-notes flag. Avoid reserved or conflicting platform command names.
Authorization: derive server scope from authenticated context and recheck roles,
record state and spoiler preference for every list/detail/search/autocomplete/history
and export. Do not reveal advanced topics in titles/counts to beginner-only viewers.
Deny guessed cross-server IDs without leaking existence. Revoked mentors lose
review/edit/export authority immediately, including old links and open forms.
Validation: bounded text, required context, safe links, valid dates, duplicate-topic
warning and optimistic revision token. Mark hypotheses as uncertain. Avoid treating
a single debrief observation as a universal rule. Concurrent edits must conflict
visibly. Publishing requires a review date and explanatory context.
Audit: actor, time, record/revision, publication, spoiler changes and reason for
revision/archive. Restricted text remains restricted inside history/logs/errors.
Exports include only currently permitted notes and fields; log requester and scope.
Define voluntary-author removal, retention, redaction and archival policy clearly.
Acceptance: beginner cannot retrieve spoiler note through direct ID/search/export;
author cannot publish own unreviewed change; revoked mentor cannot submit old form;
another Discord server cannot read a guessed ID; stale edit cannot replace current
revision; overdue note visibly needs review; an uncertain observation stays labeled;
no action claims to read ghost identity, evidence, player level or contract outcome.
Non-capabilities: no game/client control, ghost detection, reward grants, live stats,
account verification, compulsory player scoring, ticket import or replacement of
Group Finder, Beacon, Tickets or Announcements.
Review, test, and continue through the SDK
Use Plugin Builder to refine the plan before generation. Review the actual manifest, source, capabilities, custom commands, screens, visibility rules, and retention choices. The draft review includes validation and any available sandbox status; those checks do not prove spoiler isolation or revoked-role behavior.
Test with fictional notes as a beginner-only Member, opted-in learner, author, mentor, and revoked mentor. Use direct record links and exports as well as visible navigation. Change a spoiler preference while a page is open and verify the next server-side request enforces the new access.
A developer can continue in Visual Studio Code with the current SDK testing guidance, local validation, and the Dev Portal workflow. Private testing and optional Marketplace publication are separate decisions. The community can keep using simple threads while the proposal is reviewed.
Run a Complete First-Week Member Journey
| Scenario | Successful result |
|---|---|
| New investigator joins without DMs | Visible entry instructions lead to verification and one next action. |
| Learner chooses guided discovery | Suitable listings are clear; detailed solutions remain opt-in. |
| Playing mentor joins a team | Mentor counts inside four; the fifth player waits. |
| Twelve-person night fills | Three actual four-player teams have named playing leaders. |
| Member has an audio problem | Support asks useful redacted context, not credentials. |
| Mentoring concern is reported | Appropriate reviewers handle it privately. |
| Team leaves voice | Ownership transfer and cleanup behave as configured. |
| Seasonal date passes | Expired reminders/templates stop; history stays clearly dated. |
| Mentor access is revoked | Restricted notes/actions/exports are denied through old links too. |
Fix a confusing advice label, missing leader, or expired reminder before adding more automation. The goal is an investigation people understood and enjoyed enough to join again, not a larger list of roles and channels.
Frequently Asked Questions
How many people can investigate together?
Phasmophobia supports up to four players in the described online co-op team. A playing mentor or leader occupies one of those four positions. Larger Discord events need multiple separately led teams.
Should VR and non-VR players have separate Discord communities?
Start with shared conversation and useful preference fields. Ask about comfort, pace and setup needs rather than assuming skill from hardware. Verify current supported builds and joining compatibility for the actual team.
Can console players use voice recognition?
The official recognition update establishes support for PlayStation 5, PS VR2 and Xbox Series X/S. Follow current official guidance and game options for the actual device and language rather than repeating old launch restrictions.
Does YourBot know the ghost or our evidence?
The services and proposed notebook here do not read ghost identity, evidence, player level, inventory or contract outcome. Members write learning notes manually and mentors review their context and uncertainty.
Does automatic setup create the right Phasmophobia team template?
The currently inspected setup detector has no Phasmophobia entry or dedicated starter template. Create explicit four-person templates. The independent Social Feeds catalog includes the game through Steam App ID 739630.
Is Crimson Eye always available?
No. The cited 2026 iteration runs October 8–November 1, with separate shorter reward campaigns. Check the actual current event screen and official announcement before using a seasonal listing, and retire it when the window ends.
Is the custom notebook required?
No. Begin with maintained learning threads and built-ins. Add a library when spoiler permissions, revisions and stale lessons create a recurring problem that the simpler setup no longer handles reliably.
Build an Investigation Community People Trust
Phasmophobia groups work when four compatible players understand the difficulty, advice style, voice plan, and expected pace. Start Your Server establishes the Discord foundation; the ten services organize entry, teams, events, support and everyday communication. The investigation and game-side settings remain with the players.
Keep Lantern Watch's first team small, its mentors counted, and its seasonal promises dated. Add the proposed notebook through Plugin Builder when durable learning needs careful review and spoiler boundaries. A welcoming community gives people room to be uncertain, learn together, and return for another investigation.