A hundred-player guild does not fit in a chat.

Attendance, KvK points from the game’s own numbers, the night shield watch, the duty roster and a knowledge base — on one screen, in seven languages. The panel runs a living guild every day, not a promo video.

Send a request
  • A living guild, not a showcase
  • No game password needed
  • Nothing to download
  • Seven languages

Sound familiar?

What a guild gets

Not a pile of buttons, but the work of a leader, an officer and a regular member, each put in its place.

Events and attendance

A calendar a month ahead: KvK, Guild Duel, Expedition, monster runs. “I’m in” and “can’t make it” replies, the event roster, recurring events set up once. Times are entered as the game shows them — no time-zone maths.

KvK points from measurements

The panel records kills and gathered resources before and after the battle, works out everyone’s contribution and splits the points. No more “here’s my score” screenshots, and disagreeing is a button.

Rating and wallet

Everyone has their own balance, a history of every entry and a plain line saying what it was for. The rating for the period shows who carries the guild and who merely appears on the list.

Night shield watch

You can see whose shield has expired and who is standing uncovered. Waking someone or letting them sleep is the watchman’s call: the panel never wakes anyone by itself.

Kingdom map

Your roster’s castles on the map: who stands where, who moved, who is left alone out in the open. Set up for your kingdom separately.

Might and kills day by day

A growth chart for every player: who is levelling up, who has stalled, and who has not opened the game for three weeks.

Duty roster and quotas

A weekly duty roster, a daily hunting quota, and a breakdown of who actually met it. One screen instead of a roll call in the chat.

People and contacts

A card for each person, ways to reach them, who trusted whom with an account. Real names are shown only with permission — by default it is nicknames everywhere.

Knowledge base and announcements

Answers to the eternal questions stay where they belong, and an announcement reaches everyone, not only whoever was reading the chat at that hour.

An app on the phone

Installs to the home screen straight from the browser, with no app store involved. Rally calls and the night alarm arrive as notifications.

Problem reports

An “it’s broken for me” button with a screenshot. The report reaches a living person and does not get lost among messages.

For the leader

A guild health board, a breakdown of the roster, a list of everyone who never signed in, and a hint about who is worth calling personally.

The kingdom map, the night watch and the measurements around KvK are set up for your kingdom separately — write to us and we will work it out.

How KvK points are calculated

This is where guilds fall out most often, so here it is in full.

  1. 1

    Measurement before the battle

    Before the event the panel records kills and gathered resources across the whole roster — the very numbers sitting in a player’s public profile.

  2. 2

    Measurement after

    After the battle the snapshot is repeated. The difference is what a person did at this event, not over their whole life in the game.

  3. 3

    Score

    Kills and resources are combined into one number using weights that you set. The score is divided by the event’s target — that gives a share of the contribution.

  4. 4

    Points

    The share is multiplied by the event’s price. Did twice as much — got more. Sat under a shield — got nothing.

  5. 5

    Dispute

    Disagree? Tap “I disagree” right on the card. A living person looks into it, and their decision outweighs any calculation.

Honestly: our score is not the game’s KvK points. The game counts by the tier of the troops killed and the type of resource, while a public profile gives two running totals. So the score is a fair measure of contribution, not a copy of the scoreboard. You tune the weights and the target yourself; no code is involved.

An ordinary week

Monday

The leader sets up KvK for Saturday and the duel for Wednesday. Recurring events appear on their own. The roster sees them in the calendar and on their phones.

Wednesday

People tap “I’m in” and “can’t make it”. The organiser sees a list rather than promises scattered through a feed — and knows in advance who will be missing.

Saturday, KvK

The pre-battle measurement is taken. The organiser presses the rally call — a notification reaches the phone of everyone who signed up.

Sunday

The after measurement arrives, the panel splits the points by contribution. The leader looks at the breakdown, adjusts by hand where needed, and closes the event with one button.

Any night

The watchman opens the shield list. Three have expired — he decides who to wake. The rest sleep and never even learn they were checked.

Who sees what

Leader

Everything: the roster, points, guild health, settings, event prices and the weights of the calculation.

Officer

Sets up events, keeps the roster, awards points and settles disputes. Does not touch guild settings.

Night watchman

Sees the shields and presses the alarm. Nothing else clutters the screen.

Member

Their own points and what they were for, their own events, their own growth chart, the knowledge base. Eight menu items, not forty.

What the panel does not do

The conversation is shorter if this is said up front.

How to start

  1. 1

    Request

    The form below. Tell us about the guild: how many people, which kingdom, what hurts most.

  2. 2

    A conversation

    We answer the way you asked for. We look at whether the panel suits your guild and say so plainly if it does not.

  3. 3

    Setting up your guild

    Your own guild, your own language, your own event types and prices. The roster arrives as an export — no typing in a hundred people by hand.

  4. 4

    Inviting people

    You post a link in the chat. A person registers themselves, installs the panel on their phone and lands in their own guild.

  5. 5

    The first event

    Set up the nearest KvK and close it through the panel. After that it explains itself.

Not much is needed from you: a leader who wants order, and one person willing to answer “where is that thing?” for the first week.

The questions people ask first

Do you need our game password?

No. Nobody signs into your accounts, we do not ask for passwords, and there is nowhere to keep them.

What does it cost?

Terms are agreed in conversation: guilds differ, and we have no single answer for everyone. Ask and we will tell you straight.

How many people can the panel handle?

A hundred-strong roster is an ordinary size, and not just one of them. The panel was built to host several guilds at once, each with its own settings and its own language.

Which languages?

Seven: English, Russian, Ukrainian, Latvian, Bulgarian, Hindi and Chinese. Everyone picks their own — the roster is not obliged to read the leader’s language.

What has to be installed on a phone?

Nothing. You open it in a browser, “add to home screen”, and it becomes an ordinary icon next to the game. No app store, no files from the chat.

What if we keep everything in a spreadsheet?

Then you already have the discipline — that is half the job. The roster arrives as an export, and counting contribution by hand stops.

What happens to our data?

It is yours. The roster, points and events are exported on first request, and this page pulls nothing from third-party sites: no counters, no cookies, no captcha.

What if the leader changes?

Rights are handed over inside the panel. A guild is not tied to the person who created it.

We are not in your kingdom. Does that get in the way?

Not for events, points, the duty roster or the knowledge base — those work in any kingdom. The map and the night watch are set up for yours separately, and we will be honest about that before we start.

Tell us about your guild.

A person will answer, not an autoresponder. If the panel is not right for you, we will say so straight away instead of wasting your time.

A person will read your request and answer the way you asked for.