How to Build and Run an EVE Online Discord Community With YourBot

An EVE Online Discord should be organized around trust, time zone, operational scope, and what kind of fleet is actually forming. New Eden is not a game where one generic LFG button can describe everything. A three-frigate Abyss run, a five-pilot Homefront team, a 12-pilot Pochven site, a mining fleet, a small-gang roam, and an alliance strategic operation have very different capacity, security, and information needs.

The most common Discord mistake is treating EVE like a conventional MMO guild. A corporation is not just a social tag: its CEO, Directors, wallet access, structures, titles, and delegated roles can carry real in-game authority and asset risk. An alliance sits above corporations, fleets cut across those organizations, and a Discord role does not automatically grant or revoke any of those game permissions. On top of that, operational security matters. A public channel that casually exposes staging systems, timers, routes, doctrines, or movement plans can be more damaging than a poorly organized chat room.

This guide builds a fictional 258-member community called Meridian Relay. Its primary in-game corporation has 174 characters and belongs to the fictional Wayfarer Accord alliance. The community spans USTZ and EUTZ, supports rookies through a highsec training path, and runs industry, exploration, Abyssal PvE, Homefront Operations, small-gang PvP, Pochven trips, wormhole day trips, and alliance fleets. YourBot handles the Discord-side structure and workflows. EVE Online remains authoritative for corporations, alliances, fleets, access lists, structures, wallets, ship fittings, standings, sovereignty, inventories, killmails, and account security.

Start With the Right EVE Online Community Model

Tranquility is global, but time zone still matters

EVE Online's main live server is Tranquility, and most of the global player base shares that same New Eden rather than choosing conventional regional realms. That does not mean geography is irrelevant. Fleet availability, downtime, alliance timers, and human sleep schedules make time zone one of the most important matching fields in an EVE community.

Meridian Relay uses:

• USTZ
• EUTZ
• AUTZ only when there is enough actual activity to support it
• Flexible / Variable

Use EVE Time / UTC for operational scheduling wherever possible. EVE's daily downtime is at 11:00 UTC, so the community should treat UTC as the common operational clock even if YourBot renders reminders in each member's local Discord time.

Do not create North America, Europe, and Oceania as if they were separate game servers. They are availability labels, not shards.

Corporation, alliance, and Discord membership are different things

Meridian Relay's Discord contains more people than its corporation because it includes applicants, alliance guests, approved partners, alumni, and friends.

Keep these concepts separate:

• Discord member
• corporation member
• corporation role/title holder
• alliance member
• fleet member
• blue/neutral/red diplomatic status
• structure or Access List access

A Discord Director role must never be presented as proof that the character is an EVE Director. In EVE, a Director has extensive corporation powers, and only the CEO can assign or remove the Director role. Likewise, a Discord FC role does not make someone an in-game Fleet Commander.

Treat Discord roles as community authorization only unless a separate, verified integration explicitly synchronizes something.

Fleet size is activity-specific

EVE's fleet system can scale to very large operations, but many PvE sites have their own practical or hard limits.

Useful examples:

• Abyssal Deadspace: one cruiser solo, up to three frigates, or two destroyers for cooperative traces.
• Homefront Operations: designed for roughly 4–5 players.
• Pochven after the September 2026 major update: Vigilance Points up to 12 pilots and Observatory Flashpoints up to 12.
• Small-gang PvP: community-defined size; do not pretend it has one native cap beyond the fleet system.
• Strategic operations: potentially dozens or hundreds of pilots; an EVE fleet has a longstanding maximum of 256 pilots, and major coalitions can field multiple fleets.

YourBot Group Finder currently supports listing sizes from 2 to 40. That makes it ideal for small and medium activities, but it should not be used as the sole roster system for a 100-pilot strategic operation. Use Beacon for planned attendance, then form the actual fleet in EVE.

Security status, space, doctrine, and risk change the group

A "PvP fleet" is not enough information. The organizer may need to state:

• highsec / lowsec / nullsec / wormhole / Pochven
• PvE / PvP / industry / logistics / exploration
• staging system
• destination or whether destination is withheld until form-up
• ship class or doctrine
• tackle / logistics / links / DPS / scout needs
• Alpha/Omega restrictions
• security-status or standings concerns
• expected duration
• voice requirement
• whether losses are reimbursable under a corporation or alliance program
• whether the operation is public, corp-only, alliance-only, or restricted

Do not expose sensitive movement details in public listings just because the form has room for them.

Current live state: Cradle of War and the September major update

As of September 25, 2026, Cradle of War is the current EVE Online expansion. It introduced Military Campaigns, a new starter region called Exordium, titles and achievements, a historical Epic Arc, four navy destroyers, and four command carriers.

The September 22 major update materially changed fleet operations. Ansiblex jump bridges now consume capacitor charge, are limited to subcapital ships, and are usable only by capsuleers in the alliance that owns them. Pirate Insurgencies move faster, Class 1–3 wormhole combat sites were modernized, Pochven site fleet sizes changed, and additional ship balance arrived.

Those facts should influence planning, but they should not become permanent channel names. Build durable channels such as #ops, #doctrines, and #updates; put current expansion specifics inside dated posts and event records.

Operation Avalon, by contrast, ran July 7–20, 2026 and is finished. Do not schedule it as current content.

The Community We Will Build

Meridian Relay is a 258-member EVE Online Discord.

• 174 characters are in the primary corporation.
• The corporation is a member of the fictional Wayfarer Accord alliance.
• Primary time zones: USTZ and EUTZ.
• New players enter through a highsec training path before gaining access to sensitive corp/alliance operational areas.
• Recurring activities: Homefront training, Abyssal runs, mining/industry fleets, exploration, wormhole day trips, Pochven trips, small-gang PvP, and alliance operations.
• Operational details are segmented by access; public/community channels do not expose staging, timers, routes, or restricted doctrines.
• Discord authorization never substitutes for EVE corporation roles, Access Lists, alliance membership, or fleet invitations.

YourBot's role in the community

1. Create the Foundation With Start Your Server

Start with durable information boundaries rather than a channel for every region, ship, doctrine, or activity.

The first build should preserve existing structure, especially if the corporation already has sensitive channels. Never ask an AI server builder to freely reorganize an established EVE corporation's operational channels without reviewing every permission.

Copy-ready community brief

Design an EVE Online Discord server called Meridian Relay.

Community:
- About 260 Discord members.
- Primary in-game corporation has about 175 characters and belongs to an alliance.
- USTZ and EUTZ are the main time zones.
- Mix of rookies, experienced PvE pilots, industrialists, explorers, small-gang PvP pilots, and alliance fleet members.
- Activities include Homefront Operations, Abyssal Deadspace, mining/industry, exploration, wormhole day trips, Pochven, small-gang PvP, and alliance operations.

Critical EVE distinctions:
- Tranquility is the primary live server; time zone is availability, not a regional shard.
- Discord membership is separate from corporation membership, alliance membership, EVE roles/titles, fleets, and Access Lists.
- Never claim a Discord role grants EVE corporation permissions.
- Do not expose staging systems, timers, routes, doctrine details, pings, structure information, or intelligence to public/applicant channels.
- Use EVE Time / UTC for operational scheduling.
- Abyss cooperative limits: 3 frigates or 2 destroyers.
- Homefront Operations are designed around roughly 4-5 players.
- Current Pochven Vigilance Points and Observatory Flashpoints support up to 12 pilots.
- Group Finder supports small/medium groups; large strategic fleets should use events/attendance planning and form in-game.

Roles:
Owner, Discord Administrator, Moderator, Recruiter, Fleet Commander, Event Host, Mentor, Member, Applicant, Alliance Guest.
Optional interests: PvE, PvP, Industry, Mining, Exploration, Wormholes, Pochven, Abyss, Homefront, Logistics Pilot.
Optional time-zone interests: USTZ, EUTZ, AUTZ, Flexible.
Never make Director, CEO, Recruiter, Fleet Commander, or trusted operational roles self-selectable.

Channels:
START HERE: welcome, rules, choose-roles, public-announcements
COMMUNITY: general, questions, fits-and-learning, screenshots
RECRUITMENT: corp-info, open-a-ticket
FLEETS: lfg-listings, lfg-forum, events
OPERATIONS (restricted): ops-briefing, doctrines, after-action
INDUSTRY: industry, mining
INTEL (restricted): intel, travel-advisories
UPDATES: eve-updates
VOICE: join-to-create lobby
STAFF: staff-chat, sentinel-logs, ticket-log, access-audit

Safety:
- Never request EVE account passwords, email passwords, 2FA codes, backup/recovery codes, session tokens, or payment credentials.
- Account sharing violates EVE rules.
- RMT is prohibited by EVE.
- EVE permits many in-game scams, but the Discord may impose stricter community rules.
- Treat fake SSO pages, phishing, malicious downloads, impersonation, and credential theft as security incidents.
- Do not publish private applicant/security information.
- Do not store sensitive operational secrets in public custom-plugin fields.

Configure all ten built-in services:
Welcome; Sentinel; Tickets; Group Finder; Beacon Events; Join-to-Create Voice; Announcements; Social Feeds; Analytics; Giveaways.

EVE-specific setup:
- Group Finder must use explicit EVE templates rather than a generic 5-person preset.
- Announcements and Social Feed subscriptions require manual finishing steps.
- Analytics is Discord analytics, not EVE character, wallet, killmail, fleet, or sovereignty analytics.
- Giveaways do not deliver in-game assets.
- Preserve current channels and permissions on the first pass.
- Keep deletions off.
- Preview Applicant, Member, Alliance Guest, FC, and Moderator perspectives before building.

A compact channel plan

MERIDIAN RELAY
├─ START HERE
│  ├─ #welcome
│  ├─ #rules
│  ├─ #choose-roles
│  └─ #public-announcements
├─ COMMUNITY
│  ├─ #general
│  ├─ #questions
│  ├─ #fits-and-learning
│  └─ #screenshots
├─ RECRUITMENT
│  ├─ #corp-info
│  └─ #open-a-ticket
├─ FLEETS
│  ├─ #lfg-listings
│  ├─ #lfg-forum
│  └─ #events
├─ OPERATIONS [MEMBERS+]
│  ├─ #ops-briefing
│  ├─ #doctrines
│  └─ #after-action
├─ INDUSTRY
│  ├─ #industry
│  └─ #mining
├─ INTEL [RESTRICTED]
│  ├─ #intel
│  └─ #travel-advisories
├─ UPDATES
│  └─ #eve-updates
├─ VOICE
│  └─ 🔊 Join to Create
└─ STAFF
   ├─ #staff-chat
   ├─ #sentinel-logs
   ├─ #ticket-log
   └─ #access-audit

Review before applying

Review Channels, Roles, Services, and every overwrite. Preview the server as an Applicant first. An Applicant should be able to read recruitment information and open a ticket but should not see operational staging, intel, alliance plans, doctrine libraries, or staff channels.

Then preview Member, Alliance Guest, Fleet Commander, and Moderator.

Keep deletion off on the first build. Read the build report for skipped permissions. A snapshot is useful, but it is not a substitute for reviewing sensitive access before you apply changes.

Announcements schedules and Social Feed subscriptions require manual finishing steps.

2. Welcome: Separate Applicants From Operational Members

EVE recruitment often involves more trust than joining a casual game server. Welcome should establish a safe, minimal public identity without pretending to validate a character.

A new arrival can receive Applicant or Newcomer. After rules/verification, give them only the channels required for recruitment and public community participation.

Useful self-selectable roles:

• USTZ
• EUTZ
• AUTZ
• PvE
• PvP
• Industry
• Mining
• Exploration
• Abyss
• Wormholes
• Pochven
• Logistics Pilot
• New / Returning Pilot

Do not make Corporation Member, Alliance Member, Director, Fleet Commander, Recruiter, or Intel Access self-selectable.

A concise welcome:

Welcome to Meridian Relay. Choose your time zone and interests, then open a recruitment ticket if you want corporation access. Never share your EVE password, 2FA/recovery codes, or account access here. Discord roles do not grant corporation, alliance, structure, or fleet permissions in EVE.

Avoid asking for real-world identity information during ordinary onboarding.

Test: Join with a clean Discord test account, choose EUTZ and Exploration, and verify that it can see recruitment/public channels but not #intel, #ops-briefing, or staff areas.

3. Sentinel: Protect the Discord Without Pretending EVE Has No Scams

EVE is unusual because many in-game scams are allowed when they use legal game mechanics. Your Discord can still prohibit scamming its own members, but moderation guidance should not falsely claim that every deceptive in-game trade is a rules violation.

Sentinel should focus aggressively on risks that cross the line into account/security abuse:

• fake EVE SSO pages
• password or 2FA harvesting
• malicious downloads
• fake recruitment-authentication portals
• RMT/ISK-selling links
• account-sharing solicitations
• impersonation of staff or game officials
• Discord invite spam
• mass mentions and raids
• harassment and doxxing
• suspicious URL shorteners or newly introduced domains

For EVE-specific authentication, teach members to verify the real SSO domain before entering credentials. Do not create a Discord workflow that asks people to paste SSO tokens or account credentials into tickets.

Use dry-run for aggressive link or keyword rules before enforcement. EVE communities legitimately share many third-party tools, battle reports, maps, fittings, and killboards, so a simplistic "block every external URL" rule will create noise.

Discord moderation is not game enforcement.

Test: Send a harmless staff-only message containing a controlled fake-domain pattern, verify Sentinel logs it, and confirm the enforcement action matches the configured rule.

4. Tickets: Route Recruitment, Access, SRP, and Security Privately

Meridian Relay uses four focused ticket paths.

Corporation Application

• Discord display name
• EVE character name
• Alpha/Omega if relevant to the corp's requirements
• time zone
• primary activities
• approximate experience
• previous corporation/alliance if the applicant wants to provide it
• acknowledgement that Discord acceptance is not an in-game corporation invitation

Access / Role Issue

• Discord role/channel affected
• corporation or alliance relationship
• who approved access
• whether this is Discord-only or an in-game access issue

Security Report

• suspicious Discord user
• message link
• suspicious domain/link as plain text if safe
• screenshot
• whether credentials were entered
• immediate staff attention required

SRP / Operation Question

• operation/event name
• ship/doctrine
• loss link or internal reference if your organization uses one
• FC
• short question

Do not ask for EVE passwords, email passwords, authenticator codes, backup codes, session cookies, API secrets, payment information, or account sharing.

If your corporation uses ESI or another auth tool, link members to the approved tool and teach them to verify its domain and requested scopes. Do not accept copied tokens in Discord.

A closed recruitment ticket does not automatically join the corporation. A resolved Access ticket does not modify EVE Access Lists. An approved SRP ticket does not transfer ISK.

Test: Open a test Corporation Application and Security Report, verify each reaches only the appropriate staff roles, and confirm no sensitive ticket is visible to Alliance Guests or ordinary members.

5. Group Finder: Use EVE-Specific Templates, Not the Generic Five

Read-only inspection of the current YourBot develop revision shows EVE Online is not in Group Finder's automatic game-detection list. The setup wizard can still create the listing and forum infrastructure, but its generic Quick Group defaults to five players.

That five-player default happens to be reasonable for some Homefront content, but it is wrong as a universal EVE template.

Create the first template

Template Name: EVE Homefront Operation
Game: EVE Online
Default Party Size: 5
Default Expiry: 90 minutes
Description: Highsec Homefront team. State time zone/EVE Time, site type, staging system, expected ship/role, voice, and whether rookies are welcome. Target 5 because Homefront Operations are designed around roughly 4-5 pilots.

Additional templates

The last two are community targets, not hard EVE site caps. Change them to fit the operation.

Do not use Group Finder for sensitive alliance strategic fleets if listing visibility would expose form-up information. Group Finder listings can be local, network, or public; EVE operational listings should normally remain local unless an FC explicitly approves broader sharing.

Example live listing

Title: T3 Frigate Abyss — need 1
Game: EVE Online
Visibility: Local
Activity: Cooperative Abyss
Target Size: 3
Current: 2/3
Time: 20:30 EVE Time
Staging: Jita 4-4
Filament: T3 — exact weather in thread
Doctrine: Corp frigate fit v4
Need: 1 DPS frigate
Experience: Learning-friendly if you have the fit
Voice: Required
Estimated Session: 60 minutes
Risk: Ships/pods/assets at risk; verify the fit before undocking
Notes: Joining this Discord listing does not join the in-game EVE fleet. Leader sends the fleet invite after roster confirmation.

A listing should not post private destination systems, wormhole chains, structure timers, or strategic routes when that information belongs in a restricted thread or voice channel.

Test: Fill a three-pilot Abyss listing, confirm the fourth interested member waits rather than becoming a fake fourth Abyss seat, then close the listing and verify its coordination thread locks/archives as expected.

6. Beacon Events: Schedule Operations Without Confusing RSVP With Fleet Membership

Use Beacon for anything that has a form-up time:

• mining fleets
• Pochven nights
• wormhole day trips
• PvP roams
• doctrine classes
• new-player orientation
• Military Campaign objectives
• alliance form-ups
• corporation meetings

For a current Pochven event:

Event: Vigilance Point Fleet
Form: 19:30 EVE Time
Undock: 19:45 EVE Time
Participant Cap: 12
Roles:
- FC: 1
- Logistics: 3
- DPS: 6
- Utility / Support: 2
Requirements:
- Approved doctrine
- Correct staging
- Voice required
- Read #ops-briefing before form-up
Waitlist: Enabled

The 12-person cap is appropriate because the September 2026 update raised Vigilance Points to fleets of up to 12. Observatory Flashpoints are also now capped at 12.

For larger strategic operations, Beacon can track planned attendance, tentative/late/bench status, reminders, and availability. The actual in-game fleet still forms in EVE. If the operation exceeds one in-game fleet, the alliance must handle the actual fleet structure and FC chain.

Beacon RSVP does not:

• invite a character to fleet
• reserve a ship
• grant corporation/alliance access
• verify doctrine skills
• reimburse a loss
• move a character to staging

Test: Create a 12-seat staff-only Pochven event, fill one role, overfill it to trigger the waitlist, remove a signup, and confirm the longest-waiting appropriate member is promoted.

7. Join-to-Create Voice: Create Rooms for the Fleet That Actually Exists

Permanent voice channels named for every doctrine or activity become stale quickly.

Create:

• 🔊 Form Small Fleet
• 🔊 Form PvE
• 🔊 Form Industry

and place temporary rooms in a controlled category.

Useful default limits:

• Cooperative Abyss frigates: 3
• Cooperative Abyss destroyers: 2
• Homefront: 5
• Pochven: 12
• Small-gang roam: community-defined
• Strategic operation: use dedicated controlled rooms instead of assuming one temporary room should hold the entire command structure

Enable delete-when-empty, creator ownership, and ownership transfer.

For sensitive operations, do not rely on a publicly accessible join-to-create lobby. Use a restricted member/FC category or Beacon-created event voice with sign-up restrictions.

EVE already has in-game fleet mechanics; Discord voice does not create or command the in-game fleet.

Test: Create a five-person temporary Homefront room from the member-only lobby, transfer ownership, leave all test accounts, and verify the empty room is removed.

8. Announcements: Use EVE Time and Date Operational Changes

EVE is a live sandbox. Patch changes, war state, structures, routes, doctrines, and expansion content can make yesterday's instructions dangerous.

Use Announcements for:

• weekly corporation schedule
• recruitment/open-house notices
• doctrine revisions
• scheduled classes
• current travel advisories at a non-sensitive level
• extended downtime
• current expansion/patch reminders
• corp meetings
• dated operational policy changes

Prefer UTC / EVE Time in the announcement body even if the Discord timestamp localizes automatically.

A current example:

Cradle of War — September major update reminder

The September 22 update changed several movement and fleet assumptions:
- Ansiblex bridges now use capacitor charge.
- Ansiblex access is limited to members of the owning alliance.
- Coalition partners should not assume shared bridge access.
- Pochven Vigilance Points and Observatory Flashpoints now use 12-pilot caps.

Check the current #travel-advisories and approved doctrine before moving assets.
This is a dated notice; do not treat it as a permanent route guide.

Keep sensitive timers, destinations, and tactical orders inside restricted operational channels rather than broad announcements.

Start Your Server can enable Announcements, but schedules are still created manually.

Test: Schedule a staff-only announcement five minutes ahead in UTC, target an opt-in role, and confirm it fires once with the expected mention behavior.

9. Social Feeds: Use EVE's Official RSS First, Steam as a Useful Secondary Source

Read-only inspection of YourBot's current Social Feeds catalog shows no curated EVE Online entry.

EVE is unusually well suited to manual Social Feeds because the official community site exposes RSS feeds for EVE news, dev blogs, patch notes, and related channels.

A useful setup is:

Feed 1
Name: EVE Online — Official News
Source: RSS
Source URL: official EVE Online News RSS
Destination: #eve-updates
Digest: Off or hourly
Ping: None by default

Feed 2
Name: EVE Online — Patch Notes
Source: RSS
Source URL: official EVE patch-note RSS
Destination: #eve-updates
Digest: Hourly if volume is high
Ping: @Patch Watchers only

Feed 3 (optional)
Name: EVE Online — Steam News
Source: Steam
Steam App ID: 8500
Destination: #eve-updates

Use URLs copied from the official EVE RSS page rather than guessing them. Test each feed before relying on it operationally.

The Steam option is useful as a publisher-announcement source. The inspected YourBot Steam adapter uses public ISteamNews, numeric App IDs, publisher community announcements, and a 900-second default interval. YourBot's current Social Feeds docs also list Steam and RSS among 15-minute-default sources.

Do not claim any one feed mirrors every forum post, emergency notice, launcher alert, security bulletin, or alliance-relevant change. For extended downtime, the official status page and launcher remain important.

Start Your Server can turn Social Feeds on, but subscriptions are a manual finishing step.

Test: Create one official RSS subscription, preview/test it, confirm the destination and ping behavior, then verify the first real new item posts without dumping historical backlog.

10. Analytics: Measure Discord Operations, Not New Eden Performance

Analytics can answer:

• Do applicants finish onboarding?
• Which LFG templates get used?
• Do Homefront and Abyss groups fill?
• Which event times get the strongest attendance?
• Are training channels active?
• How much temporary voice capacity is actually used?
• Do new members participate after their first week?

It does not know, by default:

• ISK balance
• skill points
• ship inventory
• wallet history
• killboard efficiency
• killmails
• corporation wallet data
• structure access
• sovereignty
• standings
• security status
• market orders
• doctrine readiness
• fleet attendance inside the EVE client

Do not use Discord message count or voice time as a proxy for PvP skill, corporation value, or trustworthiness.

If you later build an ESI integration, treat that as a separate authenticated system with explicit scopes and privacy review; it does not magically become part of Analytics.

Test: Generate activity in public member channels and a Group Finder listing, then confirm the expected Discord metrics appear while private tickets and sensitive staff areas remain excluded as intended.

11. Giveaways: Do Not Turn a Discord Drawing Into an ISK Transfer Claim

A community can use Giveaways for harmless prizes such as:

• choosing the next training class
• a Discord cosmetic role
• an approved corp-funded ship giveaway
• a legitimate game-time/PLEX-related prize only when staff understands the allowed fulfillment method and current EVE rules

YourBot only selects the Discord winner. It does not create an EVE contract, transfer ISK, deliver PLEX, hand over a ship, or verify an in-game transaction.

Be particularly careful around RMT. EVE's current rules prohibit buying or selling in-game goods for real money outside authorized systems.

Never request an account password, payment credential, EVE SSO token, or account sharing so someone can "deliver" a prize.

Test: Run a staff-only giveaway for Choose next rookie class topic, verify the winner/reroll flow, and keep the first production giveaway similarly low-risk.

Protect Operational Security Without Making the Discord Unusable

EVE communities need more access segmentation than most game servers.

A practical trust ladder:

1. Public / Applicant
2. Verified Discord Member
3. Corporation Member
4. Alliance Guest / Alliance Member
5. Fleet Commander / Recruiter / Officer
6. Director / executive staff

That is a Discord access ladder, not a mirror of EVE corporation permissions.

Keep #intel, private timers, strategic doctrines, movement orders, and internal after-action material restricted. Avoid posting full wormhole chains, cyno routes, capital movements, structure timers, or strategic destinations in general-purpose LFG.

At the same time, do not lock basic learning behind needless secrecy. Public fit theory, rookie guides, non-sensitive Homefront information, and general PvE discussion should remain easy to find.

Distinguish In-Game Authority From Discord Authority

EVE corporation roles can grant meaningful access to wallets, hangars, structures, starbases, and management functions. Directors have especially broad authority.

That means a Discord Director role should only be assigned through a deliberate staff process and should still be described as Discord-side authorization.

Never automate EVE corporation roles merely because someone gained a Discord role unless you later build a thoroughly reviewed ESI/SSO workflow that explicitly supports that action—and even then, verify whether the EVE API actually permits the action you want.

The same separation applies to:

• corporation titles
• alliance membership
• Access Lists
• structure permissions
• fleet boss/FC status
• standings
• war eligibility

YourBot can organize requests and approvals. It does not alter these systems by itself.

Build Fleet Templates Around Risk and Capacity

A strong EVE template tells a pilot what risk they are accepting before they click Join.

For PvE, include the exact site type and capacity. For PvP, include doctrine and security-space context without leaking sensitive objectives. For industry, make clear whether hauling, boosts, compression, or security support are needed.

The September 2026 Pochven changes are a good example of why this must remain editable. Vigilance Points now allow up to 12 pilots, while Observatory Flashpoints were reduced to 12. If CCP changes those numbers again, update the template rather than preserving a historical number because it appeared in an old blog post.

For alliance-scale fleets, move away from Group Finder once the 40-seat listing ceiling becomes a constraint. Beacon can still manage attendance and reminders; EVE manages the real fleet.

Treat the September Force-Projection Changes as Current, Not Permanent Lore

The September 22 major update changed Ansiblex travel significantly:

• bridges now have capacitor charge
• each transit consumes charge based partly on hull/distance
• they are subcapital-only
• access is restricted to members of the alliance that owns the bridge

For an alliance corporation, that means old coalition travel guides may be stale. Meridian Relay should maintain a dated #travel-advisories channel and avoid promising that coalition partners can use alliance infrastructure.

This is exactly why the Discord should be built around durable workflows rather than permanent assumptions. Announcements carry the current rule. The channel structure survives the next balance pass.

Add an Operation Readiness Board Only When You Need It

Meridian Relay can launch without a custom plugin. Group Finder handles today's fleet; Beacon handles scheduled operations; Tickets handle applications and private requests; Announcements handle policy changes.

A custom plugin becomes useful when FCs repeatedly ask:

Which members say they are ready for this doctrine, role, or operation before I publish the fleet?

Before building anything, check the Marketplace for a maintained solution. If none fits, build Operation Readiness Board.

Version 1 should be self-reported and Discord-local. Do not start by requesting ESI access. You can always add a carefully scoped integration later after reviewing privacy, token storage, and API permissions.

Copy-ready Plugin Builder specification

Plugin Name: Operation Readiness Board

Purpose:
Maintain per-server, self-reported EVE Online readiness profiles for future corporation operations. Help FCs see who says they can fly a doctrine or fill a fleet responsibility before an event is created.

Do not duplicate:
- Group Finder: current/open group recruitment
- Beacon Events: scheduled attendance and reminders
- Tickets: applications, private support, SRP questions
- Announcements: operation notices and policy updates

Version 1 network policy:
No external network access.
No ESI calls.
No EVE SSO.
No killboard scraping.
No third-party API calls.

Never request/store:
- EVE password
- email password
- 2FA code
- backup/recovery code
- browser cookie
- session token
- EVE SSO refresh/access token
- payment information
- full real-world identity

Roles:
Admin roles:
- Discord Administrator
- Fleet Commander
- Doctrine Manager

Read-only staff:
- Recruiter
- Mentor

Member capabilities:
- Create/update own readiness profile
- Mark doctrines/roles as Ready, Training, Not Ready, or Needs Fit
- Archive stale profile
- Choose whether non-sensitive profile data is visible to Members or FCs only

Profile fields:
- Discord user ID
- primary EVE character name (self-reported)
- time_zone: USTZ | EUTZ | AUTZ | Flexible
- clone_state: Alpha | Omega | Prefer not to say
- activity_interests
- fleet_roles: DPS, Logistics, Tackle, EWAR, Scout, Command, Mining Boost, Hauler, Other
- doctrine_readiness entries:
  - doctrine_id
  - doctrine_name
  - ship/hull
  - status: ready | training | needs_fit | not_ready
  - self_reported_skill_note
  - staged: yes | no | unknown
  - last_reviewed_at
- jump/travel capability tags, if the member chooses to provide them
- voice_available: yes/no
- availability note
- status: active | stale | archived

Staff-only fields:
- staff_note
- reviewed_by
- reviewed_at
- restricted_operation_eligible: yes/no
- access_review_note

Doctrine fields:
- doctrine name
- version
- public summary
- restricted details destination
- active/retired status
- approved roles
- minimum self-reported requirements
- last revised date

Security:
- Do not store staging systems, cyno chains, structure timers, target systems, wormhole chains, or classified operation plans in member-visible records.
- Restricted doctrine details must either remain outside the plugin or require FC authorization on every request.
- Enforce authorization server-side on list, search, record view, edit, export, and direct URLs.
- Revoking an FC/Doctrine Manager Discord role must remove privileged access immediately on the next request.
- All data must be isolated by Discord server ID.

Suggested commands:
- /readiness set
- /readiness mine
- /readiness doctrine
- /readiness archive
- /fleet-readiness search
- /fleet-readiness doctrine
- /fleet-readiness stale
- /fleet-readiness mark-reviewed

Dashboard member view:
- My readiness
- Doctrine cards
- Training / Needs Fit warnings
- Last reviewed
- Visibility controls

Dashboard FC view:
- Filter by doctrine
- Filter by role
- Filter by time zone
- Filter Ready only
- Stale profiles
- Export restricted to authorized FCs
- Audit history

Audit:
Record:
- readiness changes
- doctrine version changes
- staff review changes
- visibility changes
- exports
- archived/restored records

Explicit non-capabilities:
- Does not verify EVE character ownership.
- Does not inspect skills, wallets, assets, fittings, killmails, standings, corporation roles, or location.
- Does not invite characters to fleets.
- Does not assign Discord or EVE corporation roles automatically.
- Does not create EVE contracts.
- Does not calculate SRP.
- Does not move ships or assets.
- Does not rank pilot skill.
- Does not expose restricted operations to applicants.

Acceptance tests:
1. Member creates a readiness profile and marks one doctrine Ready.
2. Another ordinary member cannot edit it.
3. FC can search Ready logistics pilots in EUTZ.
4. Applicant cannot view corp-only readiness records.
5. Revoking FC removes FC-only search/export access.
6. Direct record URLs enforce the same authorization as list pages.
7. Server A cannot read Server B data.
8. Retired doctrine no longer appears as active readiness.
9. Stale profiles are clearly flagged.
10. No workflow requests an EVE or SSO credential.

Review, test, and continue through the SDK

Review the generated plan, source, manifest, capability requests, storage, commands, and dashboard permissions before approving it.

Test as:

• Applicant
• normal Member
• Recruiter
• Fleet Commander
• Doctrine Manager
• user whose FC role was revoked

Test direct URLs, exports, stale data, retired doctrines, and cross-server isolation.

Continue in Visual Studio Code with the current YourBot SDK workflow: yourbot new, yourbot dev or yourbot dev --watch, yourbot validate, and yourbot doctor. Marketplace publication is optional.

Passing validation proves the package meets platform checks; it does not prove your authorization design or operational-security model is correct.

Run a Complete First-Week Member Journey

Fix any confusing permission or group-size workflow before adding another automation.

Frequently Asked Questions

Is EVE Online split into regional servers?

For normal live play, Tranquility is the main global server. Time zone matters heavily for scheduling, but USTZ/EUTZ/AUTZ are not conventional regional shards.

How many players should an EVE LFG use?

There is no universal number. Cooperative Abyss supports three frigates or two destroyers; Homefront Operations are designed around roughly four to five pilots; current Pochven Vigilance Points and Observatory Flashpoints support up to 12. Other fleets are community/operation-defined.

Can YourBot Group Finder run a 100-person strategic fleet?

Not as a single current Group Finder listing: its party-size field supports 2–40. Use Beacon for planned attendance/reminders and form the actual strategic fleet in EVE.

Does YourBot automatically detect EVE Online in Group Finder?

Not in the read-only develop revision inspected for this guide. Use Group Finder setup for the infrastructure, then create explicit EVE templates.

Is EVE Online in YourBot's curated Social Feeds catalog?

Not in the inspected catalog. Add EVE's official RSS feeds manually. EVE is also on Steam with App ID 8500 if you want publisher Steam announcements as a secondary source.

Can YourBot verify corporation membership, character skills, wallet, or ship inventory?

Not through these built-in services. Treat those as external game data. The optional custom readiness plugin in this guide is deliberately self-reported and has no ESI access in version 1.

Are scams against EVE rules?

Many scams conducted through legal in-game mechanics are allowed. Account theft, phishing, RMT, impersonating official services, exploit abuse, and other prohibited conduct are different. Your Discord can also set stricter community rules than EVE's sandbox permits.

Do we need Operation Readiness Board?

No. Start with the built-ins. Add it only if persistent doctrine/readiness tracking becomes a recurring operational need.

Build the Discord Around Trust, Risk, and the Fleet That Actually Forms

EVE Online's Discord problem is not a lack of channels. It is a lack of clear boundaries.

Start Your Server can establish the durable foundation: applicants, members, operational access, LFG, scheduled fleets, temporary voice, help routes, updates, and staff areas. Welcome handles the front door. Sentinel reduces account/security abuse without pretending all in-game deception is bannable. Group Finder handles the small and medium fleets where exact capacity matters. Beacon handles scheduled attendance. Announcements and Social Feeds keep the organization aware of a game that changes constantly.

EVE itself remains authoritative for the things that carry real in-game power: corporation roles, alliance membership, fleets, Access Lists, structures, wallets, assets, sovereignty, standings, routes, ship state, and character ownership.

Use Start Your Server to build and refine the Discord foundation. Add Plugin Builder only when a persistent workflow such as doctrine readiness is genuinely missing from the built-in services.