Gamer

207 KVK 28 – KE + No Mercy

Kill Event Changes

We buckled down for this final round because we presumed k133 would want payback from the payback we gave them. Such a vicious cycle that only ends with the matchup and sometimes not even then.

As such a new rule was implemented in k207 to ensure we had ample troops for the event. Alliances were required to send 10% of their membership to KVK to be safe on KE. Sometimes a little healthy fear is necessary.

To some in chaotic war kingdoms this sounds unfair; however we have had peace for a long time and this has made KE peaceful as well. This was intended to allow growth for KVK. Then the alliances started sending less and less each round. This meant the same group of people were rebuilding every event.

We rule fair and abide by the rules we implement. Every decision we make as kingdom leaders is for k207 and not for ourselves. If the opposite were true we would feed our dragons every KE. We had no intent to disable our kingdom if an alliance failed to send the required amount; however examples would be made.

The point being that you send troops for KVK and get a 300% buff to rebuild and k207 shares in the losses or fail to help and lose your troops entirely by those who bleed every KVK. If you enjoy the peace a small sacrifice is required. Or peace will end.

It was a wakeup call and everyone joined together. We received so many people that we had to boot farmers. Our usual size is less than 50 members which is just 7 main accounts and the rest farms. I have not completed the final tally but it is approximately 75 people all in.

KVK 28

We ended up with rank 4 globally and were not disappointed. It did not dissuade k133 from invading which created a 400 million power loss for k207. Instead of this being spread across 10 players it was spread among 50 and was easier to swallow by all.

As you can see sometimes rules are good to have and in the end we still had the troops to keep going and walked away victors. As I write this post, k207 and k277 are done. Only k133 remains and I don’t expect they will be allowed to gain their throne without more heat.

They poked the bears in k207 and k277 and at this point it is a matter of ego and pride. We will never meet them outside spire and firelands and this is the last time we can give them a what-for in KVK and show them that while we may be weaker we have a bigger heart and an amazing team who coordinates every detail.

I do have some amazing footage to share of KVK 27 and 28. If you have not already please subscribe to my YouTube channel. I often post content there that I do not feature on my blog.

I also created a Twitter account with the intent of publishing my day to day thoughts. I love our KOA community and ask if you enjoy my contribution to please follow me on one of the many platforms I use.

PurlsHQ.blog

Facebook.com/PurlsHQ

Twitter.com/PurlsHQ

YouTube.com/PurlsHQ

♡ 207

Advertisements
Gamer

207 KVK 27 – Allies + Tower Hockey

Allies

Sometimes there are things I cannot share because it may affect the rest of a match in KVK in unfavorable ways.

We were matched with k133 and k277 for KVK 26 – 28. Both proper beasts in comparison to k207. It was our hard/impossible match. Usually we lose 2 out of 3 defenses on these match ups. This time we are proud that we defended our kingdom and won the throne all three rounds. It is expected that our next match will be easy/equal. These are our invasion rounds and quite fun.

The untold truth of this match is that we allied with k277 in KVK 26. When Moe, Larry, Curly, and Shemp aka Rider, Sampson, Tornado, and Wood in k133 invaded k207 early on we gave them a fight. Then they left us, slightly wounded, and invaded k277. I immediately added k277’s strongest, Guardian, as a contact and we exchanged quick hellos.

Then he asked if we could ally. We created a room in game and in Line. It was great. K277 has a similar culture to us and out of the three kingdoms were the bigger beast – imo – this matchup. You don’t turn down that type of alliance in KVK after being manhandled by the other kingdom.

Guardian of k277 proves the point I’ve tried to make to others and slaughtered k133.

Stats > SH

It was amusing to see a sh32 murder sh35’s. He is now sh33 and as others should, he maxes out before upgrading a stronghold. He is also a decent guy and we had a lot of fun together.

KVK 27

Guardian was not on the k277 throne when KVK started. It seemed another alliance was given a chance to see what KVK was all about. We were told by Guardian that his 277 alliance which held the kingdom would not interfere with our fun in their kingdom. Were given two hours to invade for some Dragon xp before he would start their throne timer for defense.

The issue we faced was we didn’t have sufficient troops to stack everything and invade. We did not want to leave ourselves open to attacks from k133 but also wanted to have a little fun.

We sent Unicorn Police, Unicorn Porn, Cunning Stunt, and Scrubalotimus to take towers. These are just farms of our core KVK group and they often provide comedic fun to our invasions. Due to technical difficulties I only captured Scrub.

Then Game decided that he’d port over to lead a mega rally and brought his farm KK to join. I was unable to join on Purls as I was defending k207; however I sent my alt sh26 H.Q. Dew was not in a building and neither was another core player The Dude. Dew brought his alt NomNom as well.

Game started with a solo hit and that did not end well. We knew the stats but were distracted and it didn’t register until the hit was done. Just one of those things.

In the end, we had some fun and still managed to keep k207 secure. After defending we visited k133 with Guardian and played tower hockey for some time. Because we could. Because they messed with us first. They failed to do their research and lacked the experience required to lead a successful invasion. I hope they learned lessons this KVK and wish them the best on future matches.

♡ 207

Gamer

207 KVK 26 – Lesson One + Lesson Two

Oops

So this KVK round was disappointing but not in the way you’d imagine. I’ve been playing with various encoder setups because the Android Game Tools only lets you record to internal memory. This means I get maybe 4 hours of video and it kills my phone.

So I tried one called AZ Screen Recorder. I downloaded it just before KVK because real life had been busy. It had good reviews and my first tests were great… it allowed me to steam to YouTube privately and that video was saved on YouTube not my phone. For future editing.

Perhaps I had the settings wrong because the quality was shameful on the action I did capture. It is the action I missed that is more upsetting. It stopped recording all by itself after an hour.

So I tapped record again and this time 2 minutes. I checked my internal storage… nope it’s not taking space on my phone. That was the original thought. No time restrictions were active.

So in a nutshell I did not get any of the good stuff on camera and what I did get is so poor that I don’t think anything is salvageable. That’s okay. Lesson learned.

So no decent YouTube action for this KVK; however there is a gem from Round 25 you may enjoy. I’ll write another post when that is ready.

Back to KVK

Since KoA is fond of rotating between easy/equal matches to hard/impossible matches we knew that conquering this time may be off the list. No worries. We like our weekends too.

I created my spies and ventured into the unknown. We review leaderboards in each kingdom. Lord, dragon, power, stronghold; and evaluate from there. Rarely in a new hard match do we attempt to poke the bear.

All was calm the first hour and half. Everyone minded their own throne. We thought, maybe it’ll be a boring KVK. We had no real intent to invade after my spy run. Unless opportunity presented itself.

Then this happened. Let’s call them Moe, Larry, and Curly. We did because it was amusing.

Three sh35 against a sh33, 32, and a handful of 31s. Obviously we had 30s and down helping but we’re talking about t11 vs t10 here.

Spoiler Alert: t10 won.

We gave the good fight for an hour. They knocked North and West towers down after several solo hits and then rallied South. We pulled South because senseless death is counterproductive. East was solid and they weren’t taking that without a fight. Instead Tornado rallied the throne. It hurt but it wasn’t enough to reset us. It wasn’t a mega.

I guess that didn’t sit right with them. We were a bigger bite than they thought and not going down easy. Don’t judge a book by its cover.

Then Wood aka Shemp pulled from 133’s throne and popped over to 207 to lead a mega rally on our throne. Yes. Their strongest player left their throne defenseless. We had not seen his stats but we had no doubt he was the power player.

So in true 207 style our fearless leader said, well if they think they can reset our throne I’m going to reset theirs. And he did. It was grand.

Of course ours was reset too because Slak had 207 locked in a mega garrison. We had no intent to sacrifice troops and the decision was made for Slak to pull and port to reset 133.

Lesson One: Do not leave your home throne vulnerable. Defense is Priority.

So we kept them busy with tower hockey. Tornado stacked the throne and Samson attempted to keep four towers from firing by his lonesome. It was hilarious. It seemed they may be new to invading but they were quick learners. Samson finally achieved keeping two of the towers from firing each rotation by sending cavalry to reset our one troop.

Slak smashed Tornado off our throne and then he and Samson disappeared. When they did not appear in 133, we checked 277’s shore and watched in glee as they were tossed around like debris in a storm. It did not end well for 133 and ended with 277 defending their throne first.

It was not over for 133 yet. 277 returned the favor and visited them for a spell. Watching the tower hits was a lovely thing. 133 also took some big hits, one a mega rally we all knew they’d lose.

Lesson Two: Do not take a hit you are not positive you will win.

Taking a mega rally is not something you should do if you can bubble or port.

133 claimed their throne second and 207 last. We had no further visits and after the first two thrones were won we hung out in Discord mapping out our reaction to various scenarios that never happened.

It was fun and personally I was glad for a short KVK weekend. It had been a long week at work and I was exhausted even though I slept a good seven hours before KVK started.

Stay tuned!

♡207