GTarcade App

More benefits, more surprises

Get

Details page

Paradox’s 12M Merit Rampage: The Hunt That Almost Backfired

Wars & Stories in Westeros
Article Publish : 08/08/2026 15:29
Translate



Greetings, Fellows! I hope you are doing great. Paradox is back with another invasion story.

After the last Sow match, Paradox was bored with not having any invasion for merit. That's why he started scanning kingdoms to get juicy targets which would give him the thrill that he once enjoyed while hitting a 18 million troops target. But finding a type of target like that is very rare and sometimes a stroke of luck.

He was looking for someone with more than 1B power, so he would get some merit after looking far and deep into the horizon. He was finally able to locate a target with 1.5B power. Paradox was suspicious that he had any troops in defence. He jumped to that kingdom, hoping for the worst case, the target would only have a few troops and be full of research power.

The target was Js6989 and was in rebel gear, so if he had any troops, Paradox would have easily killed him.

When Paradox jumped to his kingdom, he scouted him to see if he had any troops. The scouting time felt like ages, and Paradox was very nervous in case someone attacked him while he was scouting Js6989.

The scout report flashed in front of his eyes; the report was somewhat good, because Js6989 had 7.1 million troops in his defence. But when Paradox saw that he was using bow commanders in his formation. He reviewed the report again, and his fear became reality. He was a bow castle.

But he made a mistake in training his troops; he had trained mixed troops, and he had nearly none T4 bows in his defence. This helped Paradox gain some confidence. He knew that one hit would always be expensive due to hospital, and he didn't want the target to put a bubble or his alliance to drop the defence tower.

This player was also a good way to test Paradox's new advisor, Arya, who had just joined his lineup. But he was still too weak to fully test her. But it was still better than nothing.

Then Paradox launched his first attack; at the same time, a few of Paradox's friends were watching the attacks from the screen, and they all were continuously encouraging him to fully kill the target.

Everyone said:

"Don't even leave a single troop in his defence"

Prove to them who the beast is and who the prey.

Then the first military regiment hit the target sneakily to understand the castle of Js6989, as the first attack was always the foundation.

When the military hit the walls, the castle was engulfed in flames, which meant that the attack was a success. And the report of the first hit appeared on the screen without any delay.

At the same time of attacking, Paradox was also keeping close tabs on the server's strong players in case they made a move against him. Before the first hit. Paradox's appearance was unknown to everyone, but now that he had hit someone from their kingdom, they would surely retaliate. He had bow commanders on his walls, but because he did not have enough bow troops to completely help his lineup. His lineup faced huge losses in the first hit.

He lost 2m troops in the first hit; on the other hand, Paradox only lost 200K.

The second attack was necessary to kill the remaining troops in his defence, but to make sure no one from the alliance garrisoned him when he attacked the target in the second hit. After a pause of a few seconds, Paradox launched the second hit, hoping that this assault would completely raze his castle to the ground.

He was very nervous when he launched his second assault because now everyone knew that a hunter had invaded, so he was keeping an eye on the powerhouses too. In case they made a move. Paradox would stop the hunt because, due to SOW, he could not afford to lose even a single troop.

The second nearly killed all his troops, leaving only 700k troops in his defence, but now Paradox was in continuous alarm condition because now, after two hits, anyone would try to locate the hunter to safeguard their allies, but he saw no movement on the map; everyone was dead silent, as if they didn't care about Js6989. This was very good news for Paradox, and everyone said not to lose this advantage and empty out his RSS reserves. These words of encouragement sparked a flame in Paradox's heart, and without any delay, he launched the third attack on Js6989.

The third attack moved like thunder because now Paradox needed speed to not reveal his location even if no one cared about JS.

But when Paradox's third attack hit the wall, he saw a strange scenario: everyone was calling back their gathering and speeding them up. Which was the sign: if Paradox jumped near the target, forget about RSS reserve. His SOW preparation would go to smoke, and he had to train all the troops again. But Paradox was already short on RSS.

The third hit had more T4 in Paradox's army, because he didn't want to leave even a single troop alive in JS6989's defence. Now, his castle was completely killed by him because everyone on the server was online and ready to pounce on Paradox the moment he revealed his location. He dropped the plan of plundering the troops; this hunt had already given him nearly 12 million merit points, and he was only 30 million points away from his 700 million merit point target.

Even though he dropped the plan, he was continuously keeping an eye on the KL and the royal alliance, in case some fool lost his bubble and gave him the remaining 30 million merit points.

But the royal alliance held an airtight bubble defence; no one lost the bubble, which made Paradox wait for the fervour to end, and he put a bubble on his castle and prepared further for SOW.

🔥Conclusion:

Paradox learned from this hunt that he should not be tempted by Rss as he had too many troops in his defence, even though he now could easily handle soloes from mid-rank players; but for strong players, he was just a sitting duck waiting to be slaughtered for merit points. SO he should hunt in limits until he shifts to Zero castle.

I hope you like this story; stay tuned for more fun like this.

Visual

Translate