KvK War Room: R4/R5 Roles and Callouts

A bad KvK decision does not always start with the wrong target. Sometimes your guild finds the right castle, but fillers march while the rally leader is examining another one. Other times, everyone sees an incoming attack, but nobody takes charge of the defense callout. A KvK war room closes that gap with clear roles and a simple communication routine. You still need to check the event start time, read the enemy kingdom, and secure your troops. This guide picks up where the pre-KvK enemy kingdom guide leaves off: who turns your intelligence into a decision, and when? For other preparation topics, browse the blog.

Assign roles before assigning players

First, confirm the KvK schedule in the in-game event screen. Then identify the periods when your guild can actually be online. A roster with 20 names does not mean 20 people will answer during a fight. Define the jobs first:

• Shift lead: Makes attack or defense decisions so two people do not issue conflicting orders.
• Observer: Watches for changes in a target’s shield, location, and activity, reporting observations separately from interpretations.
• Rally coordinator: Confirms the troop type and fills for the target selected by the rally leader.
• Defense lead: Contacts the threatened player and checks who can provide support.

For example, if you have a core of 12 available during the first 12 hours, you could set three four-hour shifts. Give each of these four roles an owner on every shift; do not expect everyone to stay in-game throughout. If one player covers two roles, record that beforehand and name a backup in case they cannot answer at the critical moment. An R4 or R5 does not need to send every message personally. Their job is to ensure no decision is left without an owner.

Put every target through three checks

Not every unshielded castle reported to the war room is an automatic rally target. Run three quick checks: Can we reach it? Is it worth the risk? Are we ready? First, recheck the shield and current location. Second, discuss the target’s activity, the possibility of reinforcements, and the losses your guild is willing to risk. Third, confirm that the rally leader, fillers, and players staying back for defense are ready.

Suppose your observer reports three candidates. One has changed shield status, another is active and likely to receive support, and the third is unshielded. Keeping only the third candidate on the table makes sense—but that does not mean marching blindly. Might alone does not reveal troop composition. Scouting options, visible gear, and enemy movements all affect how confident you can be. When information is thin, continuing to watch a target instead of launching a major rally is a valid decision.

Check your own logistics, too: after a fight, can you cover healing and rebuild the troops you need? If resources are short, you can look at RSS resource packs; ready-made resource packs are available through our site. Resource preparation never makes a bad target worth attacking. It helps you carry out a good decision.

Use one format for every callout

During KvK, messages like “come here,” “someone’s over there,” and a stream of screenshots slow decisions down. Give every callout four fields: event, observed status, decision needed, next check. For example, “Unshielded target spotted; activity check in progress; rally approval pending; observer will recheck” is more useful than “target found.” Verify the target’s identity and location in your guild channel; do not share player details in a public guide.

Separate callouts by purpose. An Info message reports an observation. An Approval message asks an R4, R5, or authorized rally leader to decide. An Execute message tells specific people what to do. This prevents two players from starting separate calls on the same target. When three castles are under discussion, label each message by event type so an old observation is not mistaken for a new order.

An enemy castle tracking tool such as LordsRally can monitor a kingdom live and send shield-drop notifications and rally warnings to a WhatsApp or Telegram group. A notification is not the decision. An observer might use !unshielded to narrow down candidates, but must still confirm their current status. See the commands page for command coverage and features for notification options. What matters at the war room is who verifies the information and who turns it into a callout.

Set rally and defense cancellation conditions early

Before starting a rally, answer not only “When do we attack?” but also “What makes us stop?” If the target shields, receives unexpected reinforcements, or your planned fill falls short, the rally leader should call for a reassessment. An earlier approval should not stand after the target’s situation changes. Cancelling is not wasted time; it prevents a march based on outdated information.

Write separate defense instructions for two situations. In the first, the player sees an attack warning and can shield: they check their shield status and protect the castle if possible. In the second, the player cannot shield because they are in fury. Instead of automatically telling them to shield, the defense lead assesses the situation and discusses reinforcement and troop-safety options. Your response to an incoming rally depends on the target castle’s actual status.

For example, an attack opportunity and an incoming rally against a guildmate appear at the same time. The shift lead follows the agreed priority: get a status check from the threatened player first. While the defense lead handles that threat, the rally coordinator checks whether the attack opportunity remains open. To prepare the basics of troop safety beforehand, read the hospital and shelter guide.

Hand over the shift after the first fight

Do not write the plan before KvK and then leave it untouched. The first fight is the real test of your role assignments. After each significant event, the war room should record three things: What did we observe? What did we decide? What must the next shift know? Failing to pass along that a target received reinforcements or a player entered fury makes the next team repeat the same investigation.

At shift change, use a short handover note instead of a long chat transcript: “Targets being watched,” “Open threats,” “Pending decisions,” and “Role owners who could not be reached.” If one of two targets reviewed during the first four-hour shift has shielded, say so explicitly. Do not let the second shift start from an outdated target list. Keep interpretation separate from observation: “Reinforcements spotted” is an observation; “definitely a trap” is an interpretation that needs checking.

Two short drills before KvK can teach you plenty. In the first, report an unshielded target and see who gives approval. In the second, simulate an incoming rally and test the defense callout. The aim is not to set a typing-speed record. It is to make the owner and next step of every callout clear. If two people claim the same authority during a drill, fix the shift roster before the fighting begins.

If you want to adapt the shifts and callout flow to your guild’s roster, get in touch. Start by making it clear who owns each decision.