Build a Kingdom QRF
When your kingdom opens, the raids don't come one at a time and they don't come fair. You get hit at three in the morning by someone three times your size, and your walls were never going to hold. No single city survives that alone. The kingdoms that come through it aren't the ones with bigger players. They're the ones with a faster answer: one standing group that hits back quickly enough to make raiding you cost more than it's worth. The army word for it is a quick reaction force. In this game it usually goes by Portal Patrol. Either name, it's the line between a kingdom that gets farmed and one that gets left alone.
A QRF is a standing group of your kingdom's strongest players, pulled from every clan and loyal to the kingdom over any one of them. Its only job is to answer an attack with a counter-attack. It doesn't guard cities. It goes after the people hitting them, fast, until the rest decide your kingdom isn't worth the trouble.
Make raiding you hurt
You can't wall your way out of an opening. Someone far bigger than you will get through, and a shield only buys a night. What you can do is make every raid expensive. And you have an opening they don't: the game won't let anyone raise a shield while they're holding an enemy banner, so the players actually farming your kingdom are stuck out in the open, which is exactly where a counter-attack catches them.
So it runs on answering, not enduring. Hit back fast, every time, and a couple of raiders get chased home the first night. The rest go find a softer kingdom. The tactic is the easy part. The people are the hard part: the creator who named the QRF watched his own come apart because the clans in his kingdom wouldn't stop feuding long enough to run it. Unity is the whole thing. If your big clans won't sit under one command for a fortnight, you don't have a QRF, you have a group chat.
Who's on it
Small and heavy, not big and broad. One veteran kingdom runs its patrol as its ten to twenty largest players, six hundred million Might between them, and treats that as the number it takes to answer a serious portal. Scale it to who you actually are, but the shape holds: a few of your heaviest hitters, not a militia.
Pulled across the whole kingdom and loyal to it, not to whichever clan they sit in. The patrol has to outrank clan rivalry or it doesn't function.
The counter arm wants G7 troops and up. A Might number built on G4 isn't the same fight as one built on G7, whatever the ranking says.
Specialists hit twice as hard against players as against monsters. Never bring a PvE guardsman army to a player fight. They're earned with Conquest Points from PvP, so they take building.
Organize it before you need it
A QRF is ninety percent logistics and ten percent fighting, and all of the logistics has to exist before the first bad night. Four things have to be running:
- One command. The big clans agree on a single leadership and park the feuds. This is the part that kills most kingdoms.
- A patrol chat, plus the kingdom chat as the log. The strike team talks in one place, and every enemy portal gets called there and written down where the whole kingdom sees it.
- An alarm everyone knows. Get hit, forward the battle report to the patrol. That's the trigger, and it has to be reflex.
- Check-in. Members mark themselves on and off, so at any hour you know whether enough people are awake to close a portal.
Then split the work. The patrol itself stages together and waits on call. Everyone not on it runs border patrol, watching the map for an enemy portal appearing. Cover the clock while you're at it: kingdoms lose cities to nobody being awake, not to being outgunned.
How the patrol answers a portal
The move is quick, which is the whole point. It has to be, because an open enemy portal ignores your walls and your shield both, and a good raider needs about three seconds to drop one next to you, strip your city, and close it again.
- The patrol garrisons together as reinforcements in the commander's city, sitting on call.
- Border watchers spot a hostile portal the moment it opens and call it into the patrol chat.
- A responder drops a defender portal on the tile right next to the hostile one.
- They march straight onto the enemy army and close the hostile portal behind it.
A march always starts from your nearest portal, so one dropped beside the enemy puts your whole massed army a single tile away, travel time gone. And a march engages the portal it's aimed at, so your defender portal catches theirs. The patrol wins by being already stacked and already close, not by being quicker on the road.
Chase them home
Closing the enemy's portal is the counter-attack, not the end of one. When a portal closes, any army still tied to it is thrown into a forced march all the way home, the slow way. You don't catch an army on the road, so you watch where that march is headed and hit them at the other end.
This part is a solo job. A cross-kingdom attack is one player's march, not a clan stack, so it's your single strongest army that follows a beaten raider back and takes down their home city, or any open city in their clan. That's the deterrent doing its real work: raiding your kingdom stops being free the moment it costs them their own.
Why a stack beats a bigger army
The reason a handful of defenders can hold off someone much bigger comes down to how the game stacks them. Reinforcements don't melt into one blob. Each stays its own army, with its own captain and its own bonuses switched on, and the attacker has to beat every single one to take the city.
Fights here open on a coin flip for who strikes first, and the first blow lands on the strongest troop type on the field, where one bad swing can delete the whole type. A lone giant has to win that flip over and over, once against every fresh army you've parked in the way, and it only takes losing it once. That's why the patrol garrisons together instead of spreading out, and why speed beats size: a march starts from your nearest portal, and the right captain or avatar cuts the travel to almost nothing. Cluster tight and your answer lands in seconds.
Don't take the bait
The fastest way to lose your patrol is to spend it on a trap, and the map is full of them. Assume every enemy portal is reinforced, especially the soft-looking ones. A small, low-Might portal parked on a border isn't a gift, it's usually the bait for exactly the army you'd send to punish it. A rival clan showing only one or two unshielded cities is doing the same thing at a larger scale.
Two rules keep you out of it. You can't attack a portal that belongs to a third kingdom anyway, only your own or the one you've opened into, so don't burn a march finding that out. And never send an army you can't afford to lose. A long march home beats a suicide fight every time.
Stand it up before the gates open
None of this can be improvised at 2am with a city already burning. Run the list before the day:
Nobody farms a kingdom
that answers back.
The QRF is one piece of a kingdom's opening. When Your Kingdom Opens is the rest of it: banners, portals, crypting, and the shield discipline everyone not on the patrol should be running.
What we don't know
Nobody outside Scorewarrior knows exactly how a fight with many defenders resolves, whether the attacker grinds through each army in turn or meets them all at once. The picture here, separate armies fought one after another, is how strong players describe it and it holds up in practice, but treat it as their reading rather than a printed rule.
The roster numbers, ten to twenty players and six hundred million Might, are one veteran kingdom's playbook. They're a reasonable starting point, not a standard. Watch what it actually takes to close a portal in your league, and set your own.