Largest Rally Hit in Game of War History! 1 Billion Power Loss!
Tonight in K106 Krainarius a truly tragic yet amazing turn of events. SexyViper AKA AussieViper AKA too many to list. Ok, she’s Viper, we get it, zeroed herself on her ex-boyfriend, a person we will not mention to protect the definitely guilty… Eventually she was set on by L:S and they gave us this spectacular hit.
Brace yourselves, ownage is coming…..
So, this poor girl fell for a fella who broke her heart. She zeroes herself on his walls from 12 B to about 9 B. Meanwhile her alliance mates are just chatting away in Kingdom Chat to MGd. Boasting about their drop in power and how MGd is just awful. The whole time their ally is sending march after march into her ex-boyfriends walls. Classy group VK is in K106. Keep it up guys! Youcontinue to provide a goldmine of blog material!
A couple things to note about this rally. As you can see, no hero was present. At some point she sent hero to her ex-boyfriend. Also, the rally size was 3,115,750. Frostbitten Core set was used. And the attack debuff boost she used didn’t do too much for her snicker or the attack buff for that matter.
I’d love to hear your comments below. Also, check out the Amazon Coins for cheaper packs than retail or Itunes, $85/pack!
Over the weekend an alliance member was taking a rally. A few of us reinforced with T4 troops and to our surprise some of our reinforcements were killed. The alliance members hospitals were not full and none of his troops were killed.
We were lucky the idiot rallying us did not send his hero!
Update: I received an explanation for these results. First, my alliance mate has few T3. He had focused on T4. So, once the limited T3 were in hospital T4 began being killed starting with the reinforcements. So while the defender’s T4 were being hospitalized to the remaining beds of hospital space, the reinforcement troops were being killed.
Conclusion, to save reinforcement more troops were needed in defenders stronghold, either T3 or T4.
Since this posting the defenders has improved gear vastly and was able to take two 6 x Relic rallies with only a six minute delay without burning. Troop numbers are important to a point, but limited troop numbers can be effective with proper gear. So get to crafting!
Over the weekend, Mz matched us up with our equal in terms of kingdom age. It proved to be a bloody encounter. I lost more tier 4 troops this weekend than all kvk events of the last combined.
A couple hundred thousand were the result of errors made from sleep deprivation and carelessness but most were from rallying 200m reinforced outlanders.
At first, we had a problem getting our rallies to actually hit them without shielding first. Later, it was taking heavy losses when they actually did.
We did have some tremendous luck with one outlander who apparently rallied his hero before our rally hit him for some reason.
In the end, we lost the kvk. K100 is another dead kingdom, something we see far too often these days. The top alliances of the kingdom destroy their own kingdom so there are basically zero points available to outlanders. This is one strategy that can be used, but thankfully k94 has not resorted to it yet. Some k94 alliances have tried to destroy all opposing in this fashion, but so far we have quelled them.
Our alliance is working on new strategies for the next kvk. They include less offensive measures and more defensive tactics, but enticing the opposition to attack seems to be the key to victory.
I immediately ported to a tile that was the target of a rally. The rally marching to the tile should have immediately struck the target player who ported off the tile. Instead, the rally hit my Stronghold.
I’m told others have experienced this same rally bug.
Here are my losses broke down by troops:
I don’t usually ask for “do-overs” or hand-outs, but I feel that these losses were a result of faulty programming in game of war and not poor game play. I was simply trying to fill a hole before the enemy kingdom. The rally should have immediately hit that player at his new location.
I hope MZ answers my bug report and is able to make me feel whole again. As you can see I’ve lost quite a bit due to a bug in their programming.
Update: MZ contacted me and wanted to know who hit me. They are “investigating the matter further.”
I received the following email from MZ support today:
SEP 08, 2014 | 02:18PM PDT
Bambi Sloan replied:
Hi there Brent,
I’ve discussed this with others, and it seems that this was a fair hit. I’m very sorry but I would not be able to offer you any compensation for this issue.