FANDOM


Mimase Pass
Date October 8, 1569
Location Mimase Pass, (modern day Aikawa, Kanagawa at Mimase)
Result Takeda victory
Forces
Takeda Hojo
Commanders
Shingen Takeda Ujinaga Hojo
Ujiyasu Hojo

The Battle of Mimase Pass (三増峠の戦い, Mimasetōge no Tatakai) is an engagement that takes place after Shingen's attempted siege of Odawara Castle. He personally leads an army twice the size of Kenshin's forces yet fails within four days due to a fire attack. As his forces withdrew, Ujiyasu's sons broke formation to pursue.

Role in GamesEdit

In Samurai Warriors 3, this is the third level in Shingen's story mode as well as a level in Ujiyasu Hojo's.

In the Takeda scenario, Yukimura, Kunoichi, and Sakon prepare to defend Shingen as he retreats. First, Shingen prepares to eliminate Ujinaga Hojo as he withdraws. Ujikuni Hojo is the next target to open up a detour. Ujiyasu, Kai, and Kenshin enter the fray in an attempt to intercept Shingen's escape path. Shingen's objective is to keep his vassals safe while heading to the escape point.

Ujiyasu's scenario allows players to defeat Shingen before he escapes. The player also need to rescue Ujiyasu's sons and escort the Hojo soldiers to the eastern garrison. Unfortunately, even when successful, the Hojo soldiers is killed in an ambush.

In the Moushouden expansion, only Kotaro gets Mimase Pass on the Hojo side as part of his story. The difference from Ujiyasu's version is that the Hojo soldiers can be rescued and won't die. This will make the Hojo soldiers stop Shingen's advance. The player also need to defeat Shingen twice, as the first one is a clone that is escorted by Yukimura.

This battle also appears in Samurai Warriors Katana when playing the Ninja story.

Historical InformationEdit



Sword This battle article is a stub. You can help the wiki by expanding it.

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.