Jussidude vs Zadam - The Price of a Single Opening | Kingdom 523

📘 Prologue - Two banners far from home

RRH and LWP were no strangers to the bonds of alliance; they knew full well what an expedition into Kingdom 523 entailed. In such ventures, far more than just banners were at stake: reputation, martial prowess, and a necessary measure of caution for any given castle might, in principle, conceal an army far more formidable than its outward appearance suggested.

RRH drew on the experience of an alliance accustomed to seeking out opportunities beyond its borders, wherever they might lie; meanwhile, LWP was serious about its ambitions for Kingdom 523, ensuring that neither side could expect an easy day.

Amidst the many castles dotting the map, two vastly different military compositions were thus set to clash: on one side, the speed and impact of cavalry; on the other, a mass of archers capable of severely punishing even the slightest mistake.

Jussidude is a cavalry player in RRH who didn’t need to make a flurry of moves to become a threat in Kingdom 523. His cavalry alone was enough to make any potential target far more vulnerable the moment an opportunity arose.

All that remained for him was to handle a single element relatively simple in itself namely, turning an opening into a genuine attack. However, since he was facing a specialized army, raw power alone offered no guarantee of success. Choosing a flawed target or vastly overestimating the impact of the strike could prove fatal, even for a seasoned attacker.

Upon encountering Zadam’s castle, Jussidude found himself facing precisely this kind of dilemma. The LWP player had fully manned his defenses with archers, meaning the matchup between the two army compositions promised a particularly fierce clash.

Zadam is an archer player in LWP. When Jussidude took an interest in his castle, the sluggish, flawed setup was nonetheless sufficiently garrisoned to ward off any offensive plans against it; it formed the rearguard of an army led by its Lord.

The sheer number of archers promised to complicate the impending duel. Facing Jussidude’s cavalry, every second of the clash mattered; any losses sustained in the initial engagement would be decisive, revealing which side had gained the upper hand.

Zadam certainly had assets to defend, but he also held cards for a counterattack should things go wrong.

His castle still stood. His Lord remained inside. His army was intact.

⚔️ First Attack - The Lord Behind the Archers

Jussidude’s approach did not immediately trigger a battle. For a few moments, Zadam’s castle seemed suspended in time, an air of uncertainty hanging over both camps as they waited to see who would make the first move. Yet, the tension deepened precisely because that move remained undetermined. Jussidude faced a defensive line of archers, knowing that a single miscalculation in his cavalry charge would spell his doom. Zadam, meanwhile, saw the threat looming so close that he could no longer ignore it. His troops were in position and his Lord was secure in the castle, yet no preliminary skirmish had allowed him to gauge the true strength of the resistance awaiting him.

Then, Jussidude made his move.

The cavalry surged from his castle in a tight formation, rapidly closing the distance. There was no prolonged period of observation. When the charge reached Zadam, the impact was instantaneous. As LWP’s archers bore the brunt of the initial shock, the defense held firm enough to make the outcome uncertain and inflict mounting casualties on Jussidude’s forces. They remained limited, yet they revealed the essential: Zadam was no mere dummy target, and his archers were truly fighting.

On the defensive side, however, something quickly went awry.

The cavalry did not slow down after the initial contact; on the contrary, the pressure intensified. Each engaged group of archers had to contend with the arrival of fresh units, while Jussidude faced a highly unfavorable ratio of damage taken. Zadam tried to hold enough troops between the cavalry and the heart of his castle, but he could only buy a moment. One section of his army collapsed, then another. This was no longer a defense executing a measured retreat; multiple elements were buckling almost simultaneously under an assault too ferocious to allow anyone time to stabilize the situation.

By this point, the battle had taken on a multitude of implications. Jussidude had gained some ground, but the primary objective remained unachieved. Zadam’s Lord could still slip away if he managed to escape the attack before the cavalry or their mounts exhausted themselves pushing forward. This was the final real threat for Jussidude: winning the engagement decisively, only to leave behind the very thing he had come to claim.

Zadam continued to defend what remained, rallying his last forces around the final strongpoints. For a moment, the sheer press of numbers seemed to create a situation less favorable for the cavalry to exploit. Yet Jussidude had already suffered too many losses; the final line of defense was mounting a counter-pressure before he could capitalize on the breakthrough.

The last archer units were scattered. The path to the center lay wide open inevitably.

This time, there were no obstacles left.

Zadam’s Lord was captured.

Jussidude’s victory: 2M lost against Zadam’s 354M

The disparity lent a raw quality to the outcome one that seemed almost jarring when contrasted with the tension of those opening seconds. Ultimately, Jussidude lost a mere 2M in power, a figure dwarfed by the 354M Zadam forfeited in a single battle. Yet, the true significance of the victory went beyond mere numbers: the LWP player’s Lord had been captured.

The main battle had been decided in a single attack.

⚔️ Second attack - The aftermath of the initial clash

After an opening clash of such magnitude, any pretense that both sides stood on equal footing was gone. Zadam’s castle had already sustained 354M in losses, and his Lord had been taken. Jussidude, meanwhile, had sacrificed only 2M in power. Under these circumstances, the second phase of the assault would play out differently. There was no longer a massive archer defense to breach, nor a Lord shielded by hundreds of millions in power. What remained of Zadam’s forces was far more modest though still present and Jussidude was determined to leave nothing standing.

The cavalry surged forward once more.

This time, however, the charge did not yield the same results. Zadam’s castle was already reeling from the initial assault, and his remaining forces lacked their former potency. Nevertheless, combat only resumed once the gap had been closed. The surviving troops engaged, and the clash reignited, offering the defender one last chance to make Jussidude pay for his decision to return.

The vanguard of the cavalry swept past the outer defenses without encountering the dense resistance that had characterized the previous attack. Zadam threw whatever forces he had left against the advancing army. Archers were regrouped in more confined positions, enabling them to mount at least enough resistance to inflict casualties. This concentration immediately created a balance of forces that was more apparent than real; the horsemen were forced to enter the kill zone, and several volleys struck their ranks.

But the situation had changed too drastically. Jussidude did not slow down for even a moment to let the resistance become dangerous. His cavalry cut through the first formation, regrouped, and was already charging toward the next units. Zadam had redeployed his remaining troops not into a massive defensive line, but into small groups designed to slow the advance. This single difference made the battle the polar opposite of the previous one: there was no longer a solid wall to shatter; instead, Jussidude hunted down and eliminated pockets of resistance before they could even regroup.

One pocket gave way. A second was overtaken moments later.

That left only a final concentration of archers all Zadam had left to throw in the cavalry's path. The final clash was brief. The archers loosed a last volley, but Jussidude’s units struck with enough momentum to absorb the impact in good order, losing no significant force. The cavalry reached their position and swept away the last group.

Then, the reports ceased.

Jussidude wins: 0M losses vs. 39M for Zadam

This time, Jussidude lost no power, while Zadam suffered another 39M in losses.

The second assault was never intended to outperform the first; it was merely a direct consequence of it. The initial 354M losses and the capture of the Lord had already decided the duel; this additional 39M simply closed the last remaining door.

After two cavalry strikes, there was no fight left to pursue.

📜 Conclusion - An opportunity that wouldn't come again

In Kingdom 523, a single battle was all it took for Jussidude to settle the score with Zadam. The decisive action occurred during the first charge: the RRH cavalry struck with remarkable impact in a compact formation, piercing the heart of a defense that was still capable of inflicting damage.

The capture of the Lord added a whole new dimension to this victory. Jussidude wasn't merely executing a strategy to weaken the opponent; the primary objective was achieved, while the force remained largely capable of continuing the campaign.

It was at Zadam’s castle judging by the outcome of the first assault that the battle was ultimately decided. The last remaining forces attempted to resist, but it was a futile effort.

The cavalry struck again without giving the defense a chance to regroup or mount an effective counter. Ultimately, the battle was won through the ability to immediately capitalize on a fleeting opportunity. There were no repeated, drawn-out assaults, nor a long search for a staged opening; when the moment presented itself, it was seized.

And as the cavalry withdrew, the battle belonged to RRH!

END