Battle for Shiro no Yojin 
Battle for Shiro no Yojin
Location: Shiro no Yojin
Date: 1123
Major Forces: Lion Clan,
Crane Clan
Generals: Akodo Isebo,
Kakita Gensa,
Daidoji Uji
Battles of Rokugan

The Battle for Shiro no Yojin was the unsuccessful Crane attack to retake Shiro no Yojin from the Lion.

Battle Edit

In 1123 [1] the Battle of the Forgotten Tide at Toshi Ranbo had raised the tensions between the clans, and the Crane army invaded the Plains of Battle. [2] The Crane assaulted the former Crane fortress of Shiro no Yojin which was defended by Akodo Isebo against the Crane commander Kakita Gensa. [3] Reinforcements under the command of Daidoji Uji arrived, and the Lion were outnumbered twenty to one odds. [4]

Legacy of the Forge Edit

These events had been fuelled by the Scorpion, as preparations of the incoming Scorpion Coup. [5] The traitor Kitsu Goden and the instigator Bayushi Sozui unleashed the Legacy of the Forge over the battlefield, possessing samurai of both sides for a much more slaughter. [6] With the Lion and the Crane becoming one fighting force trying to extinguish itself, the objective of claiming the castle became unimportant. [7]

Aftermath Edit

A group of samurai managed to perform a ritual that moved the Legacy to the realm they belonged, and the warriors at the battlefield were released of their hold. [8] The Crane seized the holding. [9]

Known Deaths Edit


  1. The Atlas of Rokugan, p. 283
  2. Legacy of the Forge, pp. 42-43
  3. Legacy of the Forge, pp. 54-55
  4. Legacy of the Forge, p. 59
  5. Legend of the Five Rings; Third Edition, p. 19
  6. Legacy of the Forge, p. 50
  7. Legacy of the Forge, p. 60
  8. Legacy of the Forge, p. 62
  9. Otosan Uchi: The Scorpion's Sting, p. 11

Shiba This battle related article is a stub. That means that it has been started, but is incomplete. You can help by expanding this article.

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.