Travian Discord Coordination Guide

Build Around Decisions

Every channel should help someone make a decision. A defense coordinator needs to know what is under attack, what is real, and what troops can arrive in time. An offense coordinator needs target lists, launch windows, fake coverage, and confirmation that players understand their assignment. A recruiter needs clean intake notes and a quick view of who has been verified.

Start with a small structure and add channels only when a workflow becomes too noisy. Most alliances need leadership, announcements, defense, offense, scouting, artifact planning, troop reports, support, and general chat. Extra channels should exist because they reduce confusion, not because they look organized.

Use Roles As Routing

Roles are most useful when they route information to the right people. A `Defense Coordinator` role should receive defense escalation messages. A `Scout` role should see scout target requests. A `Hammer` role should see offensive operation preparation. A `World Wonder` role should see crop, storage, and supply coordination.

Avoid pinging everyone for every issue. If members learn that most pings do not concern them, they stop reacting quickly. Good routing keeps urgency credible.

Where Travian Bot Fits

A Discord coordination bot such as Travian Bot can support this structure without controlling Travian accounts or taking in-game actions. Its role is to organize Discord workflows: setup, roles, request channels, private action rooms, reminders, transcripts, dashboards, support threads, and links that members use manually.

For Discord setup, Travian Bot provides `/setup` for server configuration, `/give-me-roles` for self-service responder and push roles, and `/assign-role` for configured coordinator roles. For cross-server leadership communication, `/link-channels` and `/link-channel-code` can pair admin channels and relay messages, attachments, replies, DMs, and optional translations.

Use bot-assisted workflows as routing and record-keeping, not as a replacement for leadership judgment. Leaders still decide targets, defence needs, artifact priorities, and operation timing; the bot keeps the relevant Discord channels, pings, links, and history easier to manage.

Temporary Verification For Fast Access

During recruitment waves, server moves, mergers, or urgent coordination periods, leaders sometimes need to let unverified members into the working server before everyone has completed normal IGN verification. The `/temporary-verify` command is designed for that situation.

When an admin runs it, the bot scans the server, skips bots, skips members who are already verified or already have the verified role, and gives the remaining unverified members the configured verified role for 12 hours. Each member who receives the role is also sent a DM explaining that the access is temporary and will be removed after that window.

This should be treated as a short-term access bridge, not a replacement for normal verification. Use it when leadership needs people inside quickly, then guide members back through the permanent `/verify` or welcome verification flow once the urgent setup period is over.

Standardize Defense Calls

Defense calls need a fixed format. At minimum, include target village, coordinates, arrival time, attack count, wall level if known, granary/crop status, current defense already assigned, and whether the request is for standing defense or a timed landing.

When information is missing, coordinators should ask for it immediately instead of guessing. A clear format makes it easier to compare multiple threats and avoid sending the whole alliance to the wrong target.

Keep Operations Controlled

Offensive operations should have one planning channel and one final-instructions channel. The planning room is for target discussion, scout reports, fake coverage, and timing checks. The final channel should contain only assignments, send times, landing times, and confirmation requirements.

This separation matters because operation channels become unreadable when every participant asks questions in the same place where final orders are posted. Use threads for individual player questions when possible.

Make Artifact Planning Visible

Artifact work benefits from a shared view of priorities: target artifact, treasury owner, cleaner, chiefing or capture plan, defense plan, and backup player. Discord should make those assignments easy to audit before artifact day arrives.

Leaders should avoid relying on private messages for artifact commitments. If an assignment matters to the alliance, it should be visible to the coordinators responsible for the result.

Review Noise And Access

Public guide structures should not expose sensitive operation details. Keep member-facing channels useful, but restrict target lists, spy reports, and high-value operation planning to trusted groups.

Review permissions after mergers, leadership changes, and major conflicts. Old access is one of the easiest ways for sensitive plans to drift into the wrong hands.