Travian Verification Setup, Private Planner Links, and Defence Approval

Hello everyone,

This update focuses on three connected systems: verification setup, the planner, and defence request permissions. The main idea is simple: verification is now more configurable per guild, planner access is private and tied to guild access checks, and defence requests can now be submitted by anyone while still keeping an approval gate.

Verification Options Added to Setup

The verification section in /setup now includes alliance-based controls, not only the verified role. Admins can now configure:

Require Alliance Membership - yes/no toggle
Allowed Alliances - comma-separated alliance IDs and/or tags

If the alliance check is enabled, /verify only succeeds when the player belongs to one of the configured alliances from map data. This makes verification stricter for guilds that want to lock access to alliance members only.

Note: During quick setup, these verification alliance rules are now explicitly collected so guild admins can decide this behavior before going live.

Verification Flow Updates in /verify

The /verify command now handles alliance-related edge cases more clearly.

If a player is in an allowed alliance, verification succeeds normally and they get the verified role. If a player is not in an allowed alliance (or alliance conditions are not met), verification is rejected with a clear response so users know why it failed.

Verification success and alliance data wait message in Discord.
Example: one case where verification succeeds and one case where alliance conditions block verification.

Planner Access and Guild-Scoped Validation

The planner is now fully integrated through /planner with private token links valid for 30 minutes. The planner route validates this token and checks server access before allowing usage.

From the user side, this keeps the flow simple: open the private link, use attack or defense mode, and optionally use the AI copilot to fill planner fields faster. Let me put it this way: after revisiting planner flows like travian.codelab.rs, if you have ever stared at a planner full of long tables, paging controls, and one-more-field-you-must-fill-before-you-can-move, you already know the feeling. So instead of making people fight the UI, I added AI to make planning faster and less painful. On the backend side, token payload includes guild context and access checks happen before calculate/assist routes are used.

The goal was not to make another planner with ten extra clicks and fifty fields you need to decode first. The goal was to keep proper planner power, but remove the friction from normal usage. You can still enter everything manually, but now you can also just type what you want in plain language and let the copilot apply it directly to the planner state. That means less time wrestling with setup and more time actually coordinating attacks and defence timing.

If the flow feels heavy, AI should reduce that weight, not add more of it. You open the link, set mode, paste villages, ask AI to adjust details, generate results, and move on.

TravianBot planner UI with defense mode and AI copilot.
The new planner includes attack/defense modes, share links, and AI-assisted field filling in one interface.

Anyone Can Submit Defence Requests (With Approval Flow)

This is the biggest behaviour change in coordination flow. In the defence request channel, requests are no longer limited only to the old sender role. Any member can submit a valid defence request.

What changed is the gate location:

1. User submits defence request.
2. If requester is admin/defence-sender, channel is created directly (auto-approved).
3. Otherwise, bot opens a pending approval and sends DM buttons to eligible approvers (defence sender role + configured admins).
4. Approver clicks Approve or Deny from DM, and requester gets a result message.

This keeps request intake open while preserving staff control before a defence channel is created.

Defence request approval embed in DM with Approve and Deny buttons.
Approval now happens through DM buttons, so non-coordinator requests still require a trusted approver decision.

Change of the Trial time

I want to clarify this one properly because it affects everyone on trial. The original cutoff announcement was for Friday, April 24, 2026, but I extended that window to Monday, April 27, 2026 at 00:00 CEST.

This was not an easy decision to make, and delaying it by those extra days was intentional. I wanted to give servers enough room to finish their setup and transition without abruptly cutting access, while still closing the abuse patterns that were happening around repeated trial cycling.

Important part: the legacy promise is still honored. That means 3 days trial, plus +30 days for the first 70 servers (early adopters), where applicable. The policy timing changed, but that commitment did not.

Also, once you subscribe and activate with /key, we do not want your carried trial window to be lost. The /key flow will automatically adjust the date in Paddle and in our database, so you will not be charged until the trial period is supposed to end.

You can also participate in the global voting event for extra trial-time rewards. Full details are here: Global Voting Event.

Original global bot announcement about trial time change and key activation behavior.
Original announcement message shared for this trial timing update.

Final Notes

I think this update makes onboarding and day-to-day coordination cleaner for bigger alliances: tighter verification controls, private planner access tied to guild context, and a more flexible defence intake flow with controlled approvals.

If anything feels unclear in your setup, run /setup view and then contact me through /support.

Regards,
Max