A Squire's Path

While I have discussed knights and squires in the past, I've had a few people ask for a few more specifics about the squiring process.  Newer realms that aren't next door to an established order of knights often seek to start their own order, but several of them will hesitate because they haven't been around the traditions enough to really understand the process. This post's goal, then, is to share my view of how squiring works in a well-established order of knights.

My home realm has many knights, several of which have held their title longer than Belegarth has been its own sport. That isn't exactly common, but many realms have such experience, with or without the title.  Knights here are allowed one squire, and a second if they call and pass a vote to allow it. With so many knights, that means there can be many people going through the squiring process at any given time.  They only true requirement for them to get knighted is to earn enough votes from the council of knights. 

I say that's the only true requirement, but the rest of the requirements come from their knight, and the standards the other knights will use to decide how to vote.  The realm's general requirement is that each squire must beat all of the active knights in challenges, set by the knights.  These can be duels, field challenges, or non-fighting displays of skill or knowledge.  Many knights gauge their squire against Kyrian's list of squire tasks, as it encompasses nearly every type of task one could give a squire. Once a knight feels their squire has completed their tasks, they will bring them up for a vote to be knighted. 

The knight and squire relationship is important to the process.  In addition to their direct training, knights apply their experience to guiding their squire through the process.  Occasionally, this can be harsh truths, comforting words, or a kick in the right direction.  They help keep the squire on task and motivated to finish challenges and tasks.  They also need to point out weaknesses that need improved and extra tasks (like running a specific event).   The main thing the squire needs is a little bit of help outlining what they need to work on and where they stand. Some of this could be done by a realm taking on a squire in lieu of a knight.  Those realm squires, without a knight, do miss out on a little bit of the fun part of squiring--fighting alongside their knight. 

One misconception that seems to be common is that a squire learns everything from their knight.  While a knight teaches their squire many things, a great deal of learning comes from others.  Squires must be on a quest to learn from as many people as possible, while doing their best to think critically of their own techniques. A lot of skill develops from self-evaluation and adapting to overcome skilled opponents.  By challenging the best fighters and seeking their criticism, one can often find what needs to improve, but it takes concentrated effort to actually fix technique. This also applies to service, as most knights have much experience in planning and running events, and can be great at recruitment and retention. Even in areas that have few knights (or those of equivalent experience), a realm might be able to pass along its shared experience and knowledge to a squire who seeks to learn all their area has to offer.  However, one may need to venture beyond their realm to gain more specific knowledge that elder realms/knights might be able to offer. 

As a squire, I always set for myself the goal to "do what a knight should do".  That means a lot of different things to each person, but gives one a guideline to follow.  If there is a gap in knowledge or skill that prevents achieving that goal, then obviously that is something that needs to be worked on and improved.  It also frames the mindset of service, as in if I would complain that a knight should be doing a task, why wouldn't I just take care of it? Of course, this also requires an idea of what knights do, or to have knights to emulate. 

The answer to the problem is complicated, as each knight brings something different to the table.  There are some that make a distinction between "fighting knights" and "service knight". All knights should be both, to varying degrees.  Fighting skill (or knowledge of fighting technique) is important for building a stronger realm and can be a great way to bolster recruitment through displays of top skill.  Service is a broad category, but even knights that focus on fighting still serve the realm through teaching.  It is also helpful for event planners to have fighting experience so they can plan fighting that keeps attendees involved and entertained.  The point here is that both sides bolster each other, and it is important to develop in both areas. 

One aspect of fighting skill that is often overlooked in discussion of squire tasks is field leadership. Taking command and helping the group find success on a large field is something knights should be doing (see above). Many knights have their squires read classic books on military strategy (Art of War, etc) to help build this sort of strategic mindset. Often, squires will be tasked to lead realm battles or shepherd a flock of new fighters to test their leadership.  Developing a keen eye for the flow of a line fight and gaps in the enemy line not only boosts their ability to personally influence the fight, but also to lead others to the same ends.  Smaller groups/realms might find that having a reliable commander might make the experience at major events more fun as they find more success on the field. 

Knights don't have to be the best one on one fighters in every style. However, they do need to be well versed in a variety of weapons and techniques.  Most knights end up specializing in a few weapons or styles, and are often experts in one or two.  I would say "mastered" one or two styles, but I have always felt that there will always be room to improve. At the end of a squire's path to knighthood, they should be able to display a high level of skill in a couple of styles.  Even being an expert in a support weapon should qualify. Controversial as it may be, even a non-combatant might be able to display fighting knowledge that rivals even veteran fighters--leaving the path of non-com squire open to those realms that would find it fitting.  To fit the mold of "someone that could run a realm", a knight needs to be able to teach fighting technique, not necessarily excel at it.  For example, I'm no expert on flails or bows, but I could teach someone how to use them effectively.  

 

All squires should be experts on the Book of War (and/or Dag's Manual of Arms). And by expert, I do mean expert.  They will need to know the rules for combat to be a herald, and the rules for weapon construction to check weapons and to build them. Even someone that has been in the sport for a while should review the rules and study them a little bit periodically, especially if one plans to work towards knighthood.  The hard part for newer realms, or those farther from the traditions, is that it is difficult to learn unwritten rules and old combat conventions without exposure to long serving veteran fighters. This is where disparity appears between realms and regions, especially in realms that rarely make it to large events.  Knights pass along this tradition to their realms.  Squires in more isolated realms should make it a point to visit older realms and learn from elder knights. 

 

Squires/knights should do their best to be paragon of sportsmanship and a good representative of the sport. They need to be an example to others of how great fighting can be.  By having fun, fighting hard, and coming away from a fight with a positive attitude, they can help make a mediocre day of fighting into a great time for everyone on the field.   From a recruiting standpoint, they need to be able to talk to newcomers, teach them the basics, and get them fighting.  They should be approachable and helpful.  Consider who recruited you to the sport, who really sold you on sticking around, and do your best to emulate them.

The benchmark for when a squire is ready to be knighted should be high.  The process should be hard enough to forge a strong fighter and realm leader. It should last long enough to give a squire opportunity for growth and success, as well as a chance to fail and recover, but each one's path is different and takes its own time to complete.  There should be no rush to be knighted, for the more difficult and time consuming the challenge, the more rewarding the title will be.

 

A bit of a side note.  Several people concern themselves with the prestige or reputation of the title "knight". While it is something that many people honor, the meaning of the title rests in the hands of those who have earned it.  Anyone can call themselves a knight, but those that have earned the respect of the knights they have aspired to be will find their title much more meaningful.  The title is more that you have been accepted to join them as a peer of the order.  For those knighted under realms, it is a mark of that realm's respect and appreciation for your efforts. As long as a knight upholds the goals and aims of his realm, there is little reason to concern themselves with what outsiders think about the title.

The Battle of Fort Frost

The following is based on a true story. Names and locations have been altered or omitted out of respect for the dead. Due to the graphic nature of this story, reader discretion is advised.

Fort Frost, named after one of its chief architects, rested along the Suydam river where it could protect the only passable ford for miles.  Channeled around the front of the fort, a branch of the river served as a moat against frontal assaults, with only a drawbridge and small footbridge allowing anyone to enter the fort proper.  Traders and travelers could make use of the shallow fords to cross both branches, but the road passed directly under the watchful eye of one wall of the fort's defenses and a small redoubt tower.

War would find the fort, its position too valuable to be squandered easily or ignored.  The summer heat still lingered during the early parts of fall that year, prompting an attack near the beginning of October.   Fortunate, for the defenders, the harvest feast had drawn in a great deal of local soldiers and knights from their campaigns elsewhere.  They would be well prepared.

Word had spread about the army marching towards the fort, giving them time to prepare a few defenses along the ford.  The drawbridge, like much of the fort, had fallen into disrepair and could not be shut.  They would have to fight hard from the beginning in order to hold out.  Without the gate, they decided to position their forces to each crossing, hoping to be able to defend the bottlenecks from whatever the enemy had in store for them.  The outer defenses that had been placed across the moat would have to be abandoned, as there would not be enough men to hold them and secure the fort.

It was after midday when the enemy approached.  Cloudless skies and the sunny morning had left the humid air at a sweltering temperature across the barren plain to the West.  The enemy approached en masse, carrying no siege equipment and without cavalry; they would find no need of either.  They pushed up into the hail of arrows coming from the fort under cover of a shield formation until they reached the outer defenses.  What had once been planned as the first layer of defense was quickly repurposed by the attackers to protect themselves from arrows and to station archers of their own.



Defenders of the fort try to hold ground near the ford.
Photo by: Ellie Apland

Soon the battle raged across all three crossings.  The attackers found the two bridges to be well guarded.  A central redan tower jutted out into the moat, allowing the defenders to rain arrows down from the sides of both bridges as well as from the main wall.  Palisades had a similar effect in guarding the flanks of the ford, making any attempt to cross a dangerous affair.

The ford was the first to fall. The outer palisades had given them cover from the bulk of the fort's arrow fire, allowing them to mass troops there unopposed. A great blood price had been paid for the crossing, but the attackers had pushed back the defenders to the side gate of the fort. A small band of them skirted past the fort and looked for another way in. They would find the rear sally port lightly defended, only a few guards and one older knight.

Fort Frost at the height of the battle.

With the attacks at the bridges and side gate, this small battle would prove decisive, the victor having free reign to attack the enemy rearguard. The attackers formed up and advanced on the back gate. They expected to easily push through and swarm the fort.

The attackers were unprepared for the ferocity the knight had on the defense. He strode out, by himself, leaving his men to guard the gate. Outnumbered, he fought more as a predator than cornered animal. He strafed back and forth across their line, herding them more than fighting. Anyone who strayed from the line was cut down with a growl. He knew, from his many years of experience, that he only needed to buy time for his allies to crush the rest of the attack.

Even with his skill and determination, it was inevitable that the attackers would land a blow here and there.  The first hit him squarely on the left greave.  It would have been enough to break a man's leg, but it barely slowed him down, his armor absorbing the hit without much complaint.  He returned the strike in kind, cutting into his attacker's arm with a quick slash.  That man would never be able to hold a sword in his right hand again.

The Knight strafed the line, back and forth, keeping the enemy at bay.

He strafed the opposite direction, trading blows with a man towards the middle of the formation.  His bracer was left dented and nearly falling off from the damage, but he managed to land a solid strike to the armpit in return, just above the armor.  The blood flowed easily, covering the victim as he dropped out of formation.

Another swing clanged off of his right greave as one of them rushed in to try to stop his maneuvering.  Undaunted by the charge, he planted his foot squarely in the middle of his attacker's shield.  The sudden impact sent the man reeling, and easy prey for the knight.

As the din of battle subsided around the front and side of the fort, reinforcements arrived to bolster the rear gate's defenses.  They found the knight, still holding his ground against the remnants of the attackers.  The pile of dead surrounding the knight was a testament to his fury.  He took little notice of his allies and continued to press the attack until each and every one of this enemies was either dead or fleeing.

The immense effort finally catching up with him as the adrenaline faded, the knight sunk to the ground, fighting to fill his lungs with breath.  Cheers of victory reached his ears from men who would never know of his role in saving their lives.  Those that witnessed it would drink in his honor that night.

The Glorious Charge of Macintosh

Any embellishment in this story is entirely accidental. A few of the details have slipped by over the years.

A friend's recent post got me to reminisce about the good old days of the local realm. Plenty of great stories and fond memories. Over the years, you get the witness quite a few cool fights and epic/funny moments. The talk of Hiedoran reminded me of one I love to tell from several years ago.

At the time, I was a young fighter at my second or third Oktoberfest. I had spent the bulk of the day heralding. While I really wanted to fight, heralding did give me a great chance to watch some good fights. I was there to witness the carnage caused by Macintosh and his charge into the enemy, glaive in hand.

For those of you who have never had the privilege of meeting him, Macintosh aka Mac, was the leader of Hiedoran. Soft spoken, easy going, and probably one of the nicest people you can meet, he had built up a sizable force from newer fighters. Despite being a little older and less fit than the average Belegarth fighter, he had developed a knack for glaive fighting and polearm formations.

On a typical day, most of Hiedoran's shieldmen were less experienced, resulting in the enemy doing their best to charge Mac and try to reduce the unit's damage output. This wasn't the case this day. Realm battles had been called, and the Knights of Numenor were out in force at that event. They formed up a strong flank along the edge of the field and gave Mac a strong shield wall to work with.

I was heralding near the middle of the fight, watching that side of the field. It started out like a typical battle. The different groups maneuvered and slowly engaged. Numenor was hit pretty hard, to be expected in those days. Mac's glaive went to work, hacking legs, breaking shields, and stabbing down the enemy. The knights rallied to his side, protecting him from arrows and onrushing foes alike.

The tempo of death dealing quickened as he began to break open a gap in the enemy line. Out of the wall of shields burst Mac, fury in his eyes and all the signs of overdoing it. The nicest guy I know was on a rampage, so caught up with his task at hand that those guarding him were running to keep pace. His angry, focused expression alone may have been enough to break the enemy resistance, but his glaive was happily leaving a trail of death behind him.

As to the final tally of dead, I am unsure. Those that fought along side him claimed that they didn't even have to swing their swords. The story has been retold many times, but each retelling fails to capture how truly epic it was.