The Correct Story Behind the Zeroing of KSA – The Former SW Contender
An article went up yesterday on another Game of War site incorrectly detailing the story behind the zeroing of KSA – The Former Super Wonder Contender. Not only is the advertising of false information annoying, but it’s also a slight to the professionals who zeroed KSA. For those of you who don’t know, KSA was actually the most renowned player in Clash Clans a year ago or so, as well as a beast in GoW. KSA is to Clash of Clans, as Stayalive is to Game of War. So to butcher such a prime story on the zeroing of KSA is quite an embarrassment.
Fortunately, we don’t butcher stories here on Game of War Real Tips. In fact, a few hours after the other article was posted with incorrect information, we got contacted directly by School Bus and other members of his team asking us to write what really happened, and providing us with all the details from the very first rally attempts on KSA weeks ago.
The Correct Story
“KSA was one of the biggest players in the game. He used to play in K262 which merged with K252 BRUH a few months back. Dangerzone66 and OMZ were trying to zero him with every new release from Game of War.
In the other article, they gave me and Ctesse most of the credit for the zeroing, when the credit should actually go to Dangerzone66 and OMZ. Danger has tried 8 times over the course of a few weeks to zero KSA, but Danger kept losing his hero.” -School Bus
To be clear, OMZ was the first to burn, but the majority of the zeroing effort was from ONE and OMZ’s team combined. OMZ & co. brought KSA from 55-50B to burn through meat, ONE took him down from 50-46B, and then both teams finished him off together. Both teams lost their heroes quite a few times before being able to consistently burn KSA. Once the meat was burned through, it became difficult to win on kills against higher tiered troops.
“According to OMZ, only recently were cores good enough to hit him.
We had a small crew start zeroing him the first hours. A few heroes were capped but Danger and OMZ had a set that was really really close to burning him. Not long after, we started, OMZ was the first to set him ablaze.” – Andraste
“In this picture you can see me and Danger were rallying and burning him when he was 55B power. OMZ was the first one that burned him, before getting capped for some unknown reason.
So we decided to keep going and zero him, but after he dropped 3-4 billion power, Ctesse and her crew showed up. We didn’t want them poaching our kills so we decided to stop rallying him until they left.
(ONE) couldn’t burn KSA for 30 hours straight because they don’t know the secret about the gems and which set bonus they should use. They were trying use dragonbone and custom infantry instead of frostbitten, which we used to burn him 10x before they showed up.
We were in the call that day playing in different kingdoms, but decided to port back and finish off KSA.
I remember we split into three alliances: me in YOLO, OMZ in Bx$, and DeathByMini “pimpin” in Cx$.
My rally was the first to hit and KSA had 6-7 of ONE Team’s heroes. My hit freed them and our crew kept going three rallies at a time while ONE team was watching.
In the end it became crazy because everyone was rallying to get kills or credit for zeroing KSA. I was lucky because I figured what he had left was cavalry and few infantry so I switched to custom infantry and got big hits in the end. I even got to cap KSA’s hero and I’ve kept it alive in my prison ever since.” – School Bus
More details on the event are shown in the Instagram’s of:
Dangerzone66 – dangerzone2252
Ctesse – ctessedmv
death by AJ – deathbyaj
School Bus – schoolbusgow
With help from School Bus and Andraste