Fandom

BlazBlue Wiki

Blue Shrine Maiden

Redirected from Azure Shrine Maiden

805pages on
this wiki
Add New Page
Comments0 Share

Blue Shrine Maiden

XBlaze Code Embryo (Illustration, 63)
Profile
Name: Unknown
Alias: Amanohokosaka Shrine Maiden
Blue Shrine Maiden
Gender: Female
Race: Human
Personal status
Relatives: Mei Amanohokosaka (descendant)
Tenjō Amanohokosaka (descendant)
Homura Amanohokosaka (descendant)
Status: Deceased
Appearances
Spin-off(s): XBlaze – Code: Embryo
Voice acting
Japanese voice: N/A
English voice: N/A
The Blue Shrine Maiden (蒼の巫女 Ao no Miko), also known as the Amanohokosaka Shrine Maiden (天ノ矛坂の巫女 Amanohokosaka no Miko), is the ancestor of Mei Amanohokosaka and a minor character in the backstory of XBlaze – Code: Embryo. She is the first of the 'Amanohokosaka Shrine Maidens' and suppressed the Black Beast for several thousand years.

History

The Blue Shrine Maiden is only mentioned in dialog between Mei, Kuon Glamred Stroheim and Tōya Kagari. She was born with an innate ability to communicate with the Blue when she came into contact with the Sheol Gate. During one of her talks to the Blue, the Gate began to open and the Black Beast surfaced out of it. Believing that she may have summoned it, she beckoned the Beast back into the Boundary and sunk in the Sheol Gate alongside the Beast; she then sealed the Gate from the inside, sacrificing her life to save millions of others.

From then on, her family, the Amanohokosaka's, began to guard the land, Wadatsumi, that the Black Beast emerged from. Each of her descendants protected the area for millennia to come, until they eventually began to forget their duty; this was until the events of XBlaze.

Gallery

Navigation

Characters
Playable characters
Non-playable characters
Light novel-only characters
Manga-only characters
Spin-off characters
Minor characters

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.