How to Build and Run a World of Tanks Discord Community With YourBot

Build a World of Tanks Discord around the game, account region, battle format, and vehicles people can bring tonight. Use YourBot’s Start Your Server to prepare the channels, roles, permissions, and supported services, then configure platoon recruitment, clan applications, teaching sessions, temporary voice rooms, and update feeds.

That prevents a familiar problem: several people agree to play, then discover that one means Blitz, another has a North American account, and the organizer needs a European PC platoon at a particular tier. A large battlefield also does not mean everybody in your Discord can enter matchmaking as one premade team.

This guide follows Steelbridge, a fictional 240-member community, through a reviewed Start Your Server build and manual configuration of all ten YourBot services. Existing communities can keep their current channels and follow the service sections directly.

Start With the Right World of Tanks Community Model

Steelbridge primarily serves Wargaming’s World of Tanks for PC, with an EU-based clan and a wider circle of learners, returning players, and occasional platoon partners. Other tank-game fans can participate socially without being placed in incompatible game listings.

Identify the game before the device

The World of Tanks name covers different products. “I play on PC” is not sufficient because somebody can also run Blitz on a computer.

Use the actual product pages when answering newcomers: World of Tanks on Steam, Modern Armor’s cross-play guide, Blitz, and the HEAT announcement.

Steelbridge starts with one main PC workflow. Add dedicated Modern Armor or Blitz areas only when members will actually use them. Do not create a shared “cross-platform” LFG template that implies these products play together.

Account region is not the same as timezone

Wargaming’s Steam FAQ identifies shared PC servers according to the selected region: EU, NA, or ASIA. Steam and the regular client do not require separate community groups within the same compatible region.

Ask for the account region first, then language and usual playing times. A member living in Europe may play an account elsewhere; their local clock does not establish matchmaking compatibility.

The same FAQ now permits an existing Wargaming account to be used through Steam after the official account-combining process. Do not repeat old instructions telling returning players they must abandon their account. Account changes belong in Wargaming’s own account management, never in a Discord form asking for credentials.

Match size, platoon size, and event attendance are different

The flagship PC game advertises 15v15 battles, but Wargaming’s Platoon guide limits an ordinary Random Battle Platoon to three players. The same guide requires compatible same-tier vehicles and documents additional vehicle restrictions.

This distinction becomes important in the actual examples: a mentor plus two learners fills a normal platoon, while a seven-player clan session needs a different game mode and workflow.

Keep current rules in the brief, not the channel names

As of September 20, 2026, Update 2.4: Overdrive is live, adding more Tier XI vehicles and changes to matchmaking and vehicle roles. Use the official update hub when refreshing requirements. Do not write an evergreen rule that every endgame activity stops at Tier X—or assume a Tier XI vehicle is eligible everywhere.

Onslaught illustrates another trap. Its standing guide describes two-player Platoons and seven-player Super Platoons, but the Azure Phoenix season announcement disables Super Platoons for that season. Steelbridge therefore does not advertise a seven-person Onslaught queue based on an older guide. Read the season-specific changes alongside the mode guide, then confirm eligibility in the client.

Keep permanent channels named #competitive-discussion and #battle-briefs. A changed season should require revised instructions, not a new Discord layout.

The Community We Will Build

Steelbridge welcomes platoon partners who never join its clan, newer players learning spotting and positioning, regular clan members, and organizers running scheduled activities. Its main clan plays on EU; NA and ASIA visitors identify their own region in any independent listings.

The community uses one structured LFG destination, one coordination forum, separate event signups, and a reviewed learning library. Private applications, coaching requests, and tactical preparation stay out of public chat.

These are YourBot’s ten built-in services. Start with the workflows your staff will maintain. Optional prizes should not delay working onboarding, platoon recruitment, and support.

1. Create the Foundation With Start Your Server

Sign in with the Discord account that owns the server, select it in YourBot, and open Start Your Server. The builder is owner-only. Check the building as indicator when using your community’s own bot name and avatar.

Review channel access, channel-management permissions, and the bot’s position above the roles it must manage. The server-builder guide explains the prerequisites and approval process.

Copy-ready community brief

Create or reorganize a World of Tanks PC Discord called Steelbridge for
about 240 members. Its main clan plays on EU. It also welcomes independent
platoon partners, new players, returning players, and visitors from other
Wargaming account regions.

Make the newcomer path simple: read the rules, verify, select the actual
game and account region, choose activities, then find a group or ask for help.

Separate World of Tanks PC from Modern Armor, Blitz, and other titles.
Do not imply that sharing a Discord or a computer creates shared matchmaking.
Use EU, NA, and ASIA as account-region choices, with language and playing
times recorded separately when needed.

Use Random Battles, Learning, Onslaught, Clan Interest, Replay Review,
and Special Events as optional interests. Keep LFG, Events, Clan Notices,
and Patch Notes as separate opt-in alerts.

Keep Member, Recruit, Clan Member, Mentor, Recruiter, Battle Caller,
Event Organizer, and Moderator access separate. Trusted roles must not
be self-selectable. Discord membership does not grant game-clan membership.

Create one Group Finder listing channel, one coordination forum, event
signups, clan recruitment, beginner help, a tactics/replay resource forum,
public game updates, and restricted clan planning. Provide private support,
applications, and moderation logs.

Prepare Welcome, Sentinel, Tickets, Group Finder, Beacon Events,
Join-to-Create Voice, Announcements, Social Feeds, Analytics, and Giveaways.
Apply supported settings and identify the remaining manual setup.

Ordinary Random Battle Platoons have at most three total players.
Do not create fifteen-player matchmaking parties or MMO Tank/Healer/DPS
presets. Every listing must state the game, account region, mode, tier,
communication expectations, and intended session length.

Preserve existing channels, roles, and messages. Do not delete or rename
live channels in the first build. Stage additions for staff testing.

A compact channel plan

START HERE
  #welcome-and-rules
  #verify
  #choose-interests
  #contact-staff

STEELBRIDGE
  #announcements
  #world-of-tanks-updates
  #general
  #new-player-help
  #tactics-and-replays       [Forum]
  #competitive-discussion

PLAY TOGETHER
  #platoon-listings
  #group-coordination       [Forum]
  #event-signups
  #clan-recruitment
  #battle-briefs             [Reviewed public instructions]

VOICE
  Garage Hangout
  Create a Platoon Room
  Clan Briefing             [Restricted]

STAFF AND CLAN OPERATIONS
  #staff-chat
  #application-review
  #private-support-log
  #moderation-log
  #clan-planning            [Approved roster and officers]

Keep vehicle types as optional interests or forum tags rather than channels for every tank or nation. World of Tanks identifies light, medium, and heavy tanks, tank destroyers, and self-propelled guns. These are vehicle categories—not a reason to require one of each in every group.

Steelbridge also keeps its access ladder small. Member means verified Discord access. Recruit means an application is progressing. Clan Member requires an officer’s confirmation. A self-selected Clan Interest role grants none of those additional permissions.

Review before applying

Inspect Channels, Roles, and Services. Use See it as for a newcomer, Member, Recruit, Mentor, and Clan Member. Confirm that help is reachable before broader access and that choosing a vehicle preference cannot expose tactical notes.

Review the itemized operations and leave deletions disabled for the first build. Read the result report and download the snapshot. Structural undo is useful, but it does not restore messages from deleted Discord channels.

Announcements schedules and Social Feed subscriptions still require manual creation. An enabled service is not a finished weekly calendar or a configured news source.

2. Welcome: Match the Account Region Before the Vehicle Preference

Open Welcome. Configure button verification in #verify to grant the limited Member role. Publish role menus for the actual game, account region, and activities members follow.

Steelbridge’s main choices are Learning, Random Battles, Onslaught, Clan Interest, and Replay Review. A member can follow several activities without claiming eligibility for all of them tonight.

Keep notifications separate from interests. Someone can enjoy Onslaught discussion without wanting every recruitment ping. Likewise, Patch Notes should be an opt-in alert, not a reason to mention the entire server.

Welcome to Steelbridge.

Read the rules, verify, and choose your game and account region.
For World of Tanks PC, include the region, mode, and vehicle tier when
looking for platoon partners.

Find teammates in #platoon-listings and planned sessions in #event-signups.
New and returning players can start in #new-player-help.

Our Discord includes guests and learners as well as clan members.
An interest role is not a clan invitation or a verified skill rating.

Welcome’s optional buddy feature can connect newcomers with a staff-approved Mentor pool. Assign mentors for the areas they teach, such as basic positioning or replay review. Do not award that access automatically because someone posts frequently or selects “experienced.”

Test: join through a normal account, verify, select several interests, and confirm that private applications and clan planning remain inaccessible. Check that the member knows which regional group to join without asking staff.

3. Sentinel: Moderate Conduct, Not Every Lost Battle

Open Sentinel, select the moderation log and authorized moderator roles, and review spam, mention, invite, and link rules. Trial new detection rules in dry-run while moderators check normal conversation and false positives.

For Steelbridge, the priority problems are fake Wargaming sign-ins, account-sale advertisements, malicious mod downloads, harassment, impersonation, and services promising manipulated results. A missed shot or a poor flank does not become a Discord disciplinary case simply because teammates are frustrated.

Publish a fair-play rule that prohibits cheating promotion and arranged matchmaking abuse. Wargaming’s 2026 Fair Play update specifically addresses shooting-control automation, including equivalent hardware macros, and rigged battles. Do not promote an old mod recommendation without checking the current policy.

Give Sentinel ownership of Discord moderation cases, reports, and appeals. Keep evidence and allegations private; public accusations are not reliable game-side anti-cheat verdicts. Your moderators enforce community conduct, while Wargaming handles game-account enforcement.

Test: use harmless synthetic messages to check a link rule, an exemption, and log visibility. Confirm that an unrelated recruiter cannot inspect private moderation evidence.

4. Tickets: Separate Clan Applications, Coaching, and Account Help

Open Tickets and create distinct intake paths with separate staff teams.

Clan applications can use a form-only review queue. Ask for the in-game nickname, account region, usual playing times, activities of interest, relevant vehicle availability, and what the applicant expects from the clan. A small, current vehicle shortlist is more useful than demanding screenshots of an entire Garage.

Coaching requests should ask for one learning goal, the vehicle and tier, account region, availability, and an optional replay or video reference. Route these to approved mentors rather than every clan officer. Publicly sharing a replay should require the member’s agreement, not happen automatically when they submit it privately.

Connection or account-path questions can collect the launcher, region, error wording, and a redacted screenshot. Direct actual account recovery to Wargaming. Community support should never request passwords, authentication codes, account tokens, payment details, or access to somebody’s computer.

An accepted application can begin a Discord trial, but the authorized officer still completes the in-game invitation. Do not duplicate Sentinel’s appeal process with a second unrelated ticket queue; link members to the designated moderation route.

Test: submit each form as an ordinary member. A mentor should see coaching requests, a recruiter should see applications, and neither should gain unrelated private access merely because both can use Tickets.

5. Group Finder: Match the Region, Mode, and Tier

Open Group Finder, connect #platoon-listings and the coordination forum, and review the configuration. World of Tanks is not in the inspected automatic game-detection keyword list. Create explicit templates instead of expecting the setup wizard to generate suitable sizes.

Steelbridge starts with Local visibility, one active listing per member, a two-hour default expiry, and a short posting cooldown. These are community choices. Broader discovery can come later, after staff test reports, access, and the clarity of regional labels.

Create the first template

In the template editor’s Basic tab, enter:

Template Name: World of Tanks PC — Random Battle Platoon
Game: World of Tanks PC
Default Party Size: 3
Default Expiry (hours): 2
Description: Include account region, server selection, vehicle tier,
session goal, communication preference, and expected duration.

Leave Slots empty for ordinary platoons. Members can describe preferred vehicle combinations without imposing an artificial one-light/one-medium/one-heavy rule. Let the game enforce its current restrictions.

Do not create a permanent seven-person Onslaught template while that season disables Super Platoons. A seasonal rule change is a reason to review the template, not quietly reinterpret an old listing.

Publish what people are agreeing to

Game: World of Tanks PC
Account region: EU
Server: Agree on the same available server before invitations
Mode: Random Battles
Vehicle tier: VI
Current group: 1 of 3
Goal: Learn safer early positioning and review decisions between battles
Communication: Discord voice preferred; listening is welcome
Session: About 45 minutes
Experience: New and returning players welcome

Set the total target size, not just the vacancies. Check that members already playing together are represented accurately in the participant display.

The game’s Platoon instructions remain the final step: choose the mode, create the Platoon in the Garage, send invitations, and confirm compatible vehicles. Clicking Join in YourBot does not send those game invitations or inspect a Garage.

For optional skill context, label member-entered ratings as self-reported and name the metric. Do not turn an unexplained number or a Discord activity badge into verified battle performance.

Test: fill a three-person listing, leave, and let a separate test listing expire. Check the count, alerts, coordination thread, and regional description. Confirm that the organizer can actually assemble the advertised group in-game.

6. Beacon Events: Schedule the Roster the Activity Actually Uses

Use Beacon Events for teaching, scheduled clan play, replay clinics, and community evenings. Group Finder also supports scheduled listings; Steelbridge deliberately assigns it individual partner searches while Beacon owns planned event attendance.

Example: a mentor platoon

Title: Tier VI Positioning Practice — EU PC
Category: Other
Date & Time: The organizer's chosen local date and time
Max Participants: 3
Signup Options: Mentor — 1; Learner — 2
Destination: #event-signups

Choose Clear in the signup role tree, then add the appropriate options. Keep the overall participant cap separate from the option capacities. The mentor occupies a playing place rather than appearing as an extra fourth participant.

Example: a clan Skirmish evening

Wargaming’s current Stronghold Skirmish guide lists 7v7 for divisions VI, VIII, and X. Do not copy an older ten- or fifteen-player Skirmish roster into a new template.

Steelbridge begins with this simpler event:

Title: Steelbridge Tier VI Skirmishes — EU
Category: PvP
Max Participants: 7
Signup Options: Playing Caller — 1; Player — 6
Destination: #event-signups

The caller is a playing member of the seven. Use the waitlist for reserves rather than counting them as active players. Vehicle assignments and alternatives belong in the event brief, not a generic MMO role preset.

The authorized host creates the detachment through Stronghold → Clan Battles, selects the division, invites participants, and completes the game-side readiness process. The official guide also distinguishes clan members from volunteers joining a detachment. A volunteer place is not an automatic clan membership.

For a replay clinic, choose a practical teaching capacity instead. Eight Discord attendees discussing recorded matches do not become an eight-player Random Battle party.

Test: fill the intended player places, check overflow and reminders, and verify the time from another member account. For clan play, separately test the actual detachment before relying on the event for a public launch.

7. Join-to-Create Voice: Separate Platoons From Clan Briefings

Join-to-Create Voice supports multiple lobbies with separate defaults. Steelbridge can begin with a three-person Platoon lobby, a larger coaching space, and a restricted area for organized clan activity.

Configure the temporary-room category, creator ownership, owner controls, and delete-when-empty behavior. Review ownership transfer and the allowed-role or category-inheritance settings. A simple name template such as 🎧 {display_name} is enough.

A room owner can manage their temporary space without receiving server-wide administrative powers. However, “temporary” does not mean “private.” Test visibility and joining permissions before discussing applications or tactical plans there.

Keep Garage Hangout available for casual conversation. Members can also use the game’s native platoon communication; Discord is useful for continuity before and after matches, not a required replacement for every casual group.

Test: create a room, admit a teammate, transfer ownership, and verify cleanup after everyone leaves. Test a non-clan account against restricted rooms and repeat the check after removing a former member’s clan access.

8. Announcements: Publish a Weekly Plan, Not Assumed Eligibility

Open Announcements, choose #announcements, configure the timezone, and create the schedule manually. Use opt-in Events or Clan Notices roles instead of mentioning everyone.

Steelbridge this week

Tuesday: Beginner platoons
Thursday: Replay review
Saturday: Tier VI clan Skirmishes
Weekend: Current competitive-mode discussion

Check #event-signups for dates, regions, requirements, and available places.
Use #platoon-listings for partners today.

Matchmaking groups must use the same World of Tanks product and account
region. Check the selected mode's vehicle rules before joining.

Let Beacon handle event-specific reminders and Announcements handle the overview. Avoid two services sending the same last-minute ping.

Date seasonal notices and link the relevant regional announcement. Do not turn a published maintenance estimate into a promise that the servers will be ready at a particular minute, or tell every region to use one local event time.

Test: preview the message in a staff channel. Check timezone, destination, mention behavior, and links before enabling the public schedule.

9. Social Feeds: Add the PC Game Through Steam News

World of Tanks does not have a dedicated tile in the inspected YourBot game catalog. The generic Steam source still supports its PC listing through Steam App ID 1407200.

Open Social Feeds and create the subscription manually:

Source: Steam
Steam App ID: 1407200
Destination: #world-of-tanks-updates
Optional mention: Patch Notes

Check the preview carefully: World of Tanks Blitz is a different Steam product. A correctly working subscription to the wrong game is still the wrong feed.

The inspected adapter requests publisher Steam Community announcements and uses a 900-second default polling interval. That is periodic checking, not guaranteed fifteen-minute delivery or a live service-status connection. The PC game’s Steam announcement page is a useful source check.

The feed can serve regular-client players too; the destination is Discord, not their launcher. It may not mirror every regional competition, support article, or policy notice. Read important changes on Wargaming’s appropriate regional portal before turning them into clan instructions.

Test: verify the product, destination, and role mention, then observe a newly published item. Enabling Social Feeds alone does not create the subscription or prove delivery.

10. Analytics: Measure the Community, Not Battle Performance

Configure Analytics with Steelbridge’s timezone, bots excluded, deliberate retention, and exclusions for private coaching, applications, clan planning, moderation, and automated-feed channels.

Review whether newcomers return, whether planned sessions generate useful participation, and whether the learning forum is being used. Compare those observations with signups and actual support questions. Voice minutes alone do not prove that somebody completed a game session.

YourBot’s built-in Discord analytics do not establish World of Tanks Rating, WN8, win rate, Marks of Excellence, vehicle ownership, clan contribution, or mission completion. Keep community recognition separate from game statistics and access to Mentor or Caller roles.

Avoid public activity cards that reveal private clan attendance patterns. Officers need operational information; the whole Discord does not need a timetable of when a particular team is active.

Test: compare a normal public interaction with an excluded channel and inspect any public cards. Confirm that the displayed information matches your intended privacy boundary.

11. Giveaways: Keep Community Prizes Separate From Game Rewards

Open Giveaways, restrict hosting to approved organizers, and select the public announcement destination. State the actual prize, eligibility, closing time, claim deadline, and fulfillment process.

Steelbridge’s straightforward options are community merchandise, a legitimate store gift card, or a sponsor-provided peripheral. Confirm any regional restrictions before announcing the prize.

Do not advertise automatic delivery of gold, credits, bonds, Premium time, vehicles, or clan resources. YourBot manages the Discord drawing; it does not grant World of Tanks entitlements. Any official-code promotion needs real authorization, a real code, and its actual redemption conditions—not a convincing-looking sample.

Do not make entrants hand over account access or perform arranged battles. A community celebration should not become a phishing route or a mission-manipulation scheme.

Test: run an explicitly labeled staff-only drawing without a real prize. Check entries, closure, winner messages, and who is authorized to reroll or edit it.

Let the Game Handle Platoons, Clans, and Competitive Registration

World of Tanks already has a native platoon search and invitation system. YourBot supplies the community context around it: familiar teammates, stated expectations, teaching, and an organized place to return after the session.

Clan membership is another separate layer. Wargaming’s clan rules cap a clan at 100 members. Steelbridge’s 240 Discord members therefore cannot all be promised a place in one clan. Guests, applicants, former members, and independent players can remain valued community participants.

A Recruiter approves the application; an authorized officer confirms the game invitation and updates Discord access. Removing either side should trigger a deliberate review of the other. Do not claim automatic synchronization unless a separate integration has actually been implemented and tested.

Tournament registration follows the same principle. Beacon records intended attendance, not an entry accepted by Wargaming’s competition system. Captains must check the current tournament’s region, format, vehicle restrictions, substitutes, and registration process separately.

Make Vehicle Readiness and Session Expectations Explicit

A player saying “I play heavy tanks” has not established what they can field for a particular evening.

Ask for the agreed tier and one or two relevant vehicles, then discuss preparation and alternatives. A teaching session should accept an appropriate accessible choice rather than silently requiring an expensive preferred setup. An organized clan session can state stricter requirements, but it should explain them before members commit.

Use a short readiness checklist:

Correct game and account region confirmed
Selected mode and tier confirmed
Agreed vehicle available and ready
Required preparation understood
Voice/listening arrangements agreed
Expected session length and leaving procedure understood

Avoid promises of guaranteed wins, rating gains, mission completion, or credit profit. A credit-focused session describes somebody's goal, not an assured result.

Current vehicles and balance are useful discussion topics, but they should not control the permission model. Keep nation and vehicle discussions in forum tags, with dated advice. A member changing a preferred tank should not need an administrator to redesign the server.

Keep Replay Learning Useful Without Making Mods Mandatory

Steelbridge’s beginner sessions use native tools and ordinary gameplay. The game’s own newcomer systems provide a starting point; the community adds patient explanations, shared review, and consistent teammates.

Wargaming’s replay guide explains battle recording and .wotreplay files. Ask a coaching request to identify the game version, vehicle, tier, map, and one question to investigate. Test the recording before a scheduled clinic and provide an ordinary video alternative when playback is a problem.

Get permission before sharing a private submission publicly. Review decisions rather than turning another player’s mistakes into a public ranking or humiliation thread.

For modifications, direct members to Wargaming’s official Mod Hub guidance and current Fair Play rules. Do not require a random executable or an old mod pack sent through direct messages. Native practice should remain available to members who install nothing extra.

A World of Tanks client modification and a YourBot plugin are different products. The custom project below organizes Discord information; it does not modify aiming, matchmaking, or the game client.

Add a Battle Brief Library Only When You Need It

Steelbridge can launch with the built-in services. A custom plugin becomes useful when requirements and practice instructions keep drifting across old messages.

A Vehicle Readiness & Battle Brief Library would preserve approved activity requirements, alternatives, last-reviewed dates, and separate public instructions from private caller notes. It would not become another roster, ticket queue, or RSVP system.

Check the marketplace for a maintained solution first. Review the actual listing, requested capabilities, support, data handling, and price rather than assuming a World of Tanks-specific integration exists.

The seasonal Onslaught change is a practical reason for versioning: an approved brief must not keep recommending an unavailable party format. Likewise, members who joined a Tier VI event should not discover that the attached instructions silently changed to Tier VIII.

Copy-ready Plugin Builder specification

Build a YourBot SDK plugin called Steelbridge Battle Brief Library.
This is a Discord activity and preparation library, not a game integration.

Administrators configure Brief Author, Brief Reviewer, and Battle Caller
roles, a public approved-brief destination, and a private review destination.

Each brief stores:
- title and author
- game/product and Wargaming account region
- activity or mode
- current season/event when applicable
- intended date range or validity window
- in-game party or roster size, distinct from overall event attendance
- vehicle tier and permitted vehicle requirements entered by the organizer
- practical alternatives for learning sessions
- preparation, communication, and session-length expectations
- public player instructions
- private caller notes
- official source links entered as text
- reviewed game version and last-reviewed date
- status: Draft, In Review, Approved, Needs Review, Archived

Do not generate fake working game codes, player statistics, or eligibility.
Do not assume all modes use the same party size, vehicle tier, or rules.

Authors submit revisions. Reviewers approve, request changes, or archive.
Keep approved revisions immutable. Attach a specific revision to each
published session reference so later edits cannot silently change what
participants agreed to. Display superseded or outdated status clearly.

Allow manually supplied links to the corresponding Beacon event, Group
Finder listing, or Discord discussion. Do not add a second RSVP system,
clan application form, or coaching ticket queue.

Only approved public instructions appear to ordinary members. Private caller
notes are visible only to the author, assigned authorized reviewers,
authorized callers, and administrators. Enforce authorization server-side
for commands, dashboard actions, direct record access, and exports.
Removing a role must remove the associated access.

A member's interest selection never proves tank ownership, game-clan
membership, rating, or current eligibility. Do not award privileged Discord
roles from unverified game claims.

Provide interaction-driven submit, browse, view, revise, review, and archive
actions using supported SDK commands and a searchable dashboard. Evaluate
review dates when a record is accessed or changed. Do not depend on cron
jobs, a background crawler, or automatic patch interpretation.

Keep external network access disabled in version 1. Store source links
without automatically fetching them. Do not download or run submitted files.

Do not collect Wargaming or Steam passwords, login codes, account tokens,
API credentials, payment information, or game-control credentials.
Do not read live Garages or statistics, create Platoons, change clan rosters,
register tournaments, control the client, or award game currency.

Isolate all records by Discord server. Include retention, deletion, and
export controls. Audit changes without copying private notes into public
logs or retaining deleted note contents indefinitely.

Test unauthorized access, revoked permissions, cross-server requests,
private-note leakage, unsafe mentions, changed region/tier requirements,
expired briefs, immutable revisions, and links to deleted events.

Review, test, and continue through the SDK

Use Plugin Builder to review the plan, generated source, manifest, commands, and capabilities. Resolve validation findings before a development installation with synthetic briefs. The documented test installations expire after 24 hours; they are not a permanent operating arrangement.

Test as an author, assigned reviewer, unrelated recruiter, ordinary member, caller, and administrator. Remove a caller’s role and repeat direct-access and export checks. An invisible dashboard button is not proof that the underlying action is protected.

A developer can continue the same generated project in Visual Studio Code. Open its complete folder, select a project Python environment, install yourbot-sdk and the declared dependencies, and run yourbot validate and yourbot dev. The latter exercises a simulated local runner, not your live Discord.

Follow the SDK quick start for packaging and the Dev Portal’s ZIP or supported GitHub workflow. Keep manifest.json and __main__.py at the ZIP root and follow the applicable review and installation process. The library is interaction-driven because the current SDK documentation says marketplace-plugin schedules do not run.

Passing validation does not establish that a brief is correct or private. Test the Discord workflow and separately verify the game rules the brief describes.

A Wargaming API integration would be a separate project

Wargaming does provide a documented developer API. Do not confuse this manual first version with a claim that game data cannot be integrated.

A later project should identify the exact supported endpoints, regional routing, application registration, permission requirements, and refresh limits. Public player lookup is not proof that the requesting Discord member owns that account. Private data requires the appropriate official authorization flow, never a password or access token pasted into chat.

Keep that work separate from the brief library until the community has a specific, reviewed need for it.

Run a Complete First-Week Member Journey

Rehearse the setup with ordinary accounts before announcing it to the whole community. These are acceptance tests, not assumptions about what staff can see.

Also test a former member’s access, a deleted event link, and a temporary voice room becoming empty. Those ordinary transitions often matter more than the perfect first demonstration.

Frequently Asked Questions

Can World of Tanks PC, Modern Armor, and Blitz players platoon together?

No shared party workflow should be assumed. They are separate products. This guide’s main listings are specifically for World of Tanks PC; other titles need their own compatible templates and rules.

Do Steam and regular-client players need separate LFG channels?

No. Wargaming’s current Steam FAQ says they share servers according to the selected account region. Record that region and use the official account-linking path when needed.

Should a Random Battle listing have fifteen places?

No. Battlefield team size and premade Platoon size are different. Use the actual Platoon limit, then let matchmaking assemble the rest of the battle.

Can we offer a seven-person Onslaught group?

Not on the assumption that an older guide still applies. The Azure Phoenix season announcement disables Super Platoons. Review the active season and current client before advertising any organized entry format.

Do all Discord members have to join the clan?

No. A general community can serve guests, learners, and several organized groups. Game-clan membership has its own limit and invitation process.

Can YourBot verify ratings, inspect vehicles, or manage the clan automatically?

Not through the built-in workflows described here. A separate Wargaming API integration would need verified endpoints, account-ownership handling where required, permissions, and testing. The proposed library deliberately uses reviewed community instructions instead.

Is the custom Battle Brief Library required to launch?

No. Start with onboarding, compatible platoons, events, voice, safety, and support. Add versioned briefs when keeping instructions current becomes a genuine operational problem.

Build Around Compatible Platoons and Clear Preparation

A useful World of Tanks Discord gets a player the right regional teammates, gives a beginner a patient mentor, and lets a caller assemble an eligible detachment without confusing a Discord signup with a game invitation.

Start Your Server prepares the foundation. YourBot’s built-in services organize the community around it. Wargaming remains responsible for matchmaking, vehicles, clan membership, competition eligibility, and battle results.

Start your community setup, test the first complete member journey, and expand the same bot with a focused Plugin Builder project when your community needs more.