FANDOM


"The Prologue of ACES"
Chapter guide
MangaMagical Girl Lyrical Nanoha A's THE COMICS
Chapter#3.5 (equivalent)
PublishedAugust 29, 2005
Pages19

"The Prologue of ACES" is a standalone manga chapter serving as the prologue of Magical Girl Lyrical Nanoha A's, originally published in Comic Chirality Vol.1.

In the bound volume issue of Magical Girl Lyrical Nanoha A's THE COMICS, this chapter is arranged between Report 3 and Report 4, except for the first four pages arranged before Report 1 with another title "The Outline of Magical Girl Lyrical Nanoha".

SummaryEdit

The first four pages of the chapter are a recap of the first Nanoha season. The rest of the chapter takes place on November 15, 0065, about two weeks before the beginning of A's (i.e. between chapters 03 and 04 of the manga). Aboard Arthra, Yuuno, Chrono, and Fate discuss the latter's release. Chrono mentions that she passed the mage's exam (shown in chapter 02), and Fate thanks them both for their help. The same day, Nanoha, Alisa, and Suzuka receive a video message from Fate. Arisa wonders what country Fate is from and Suzuka guesses Italy because "Testarossa" is Italian. In the end, Fate tells them that she will come to visit soon, and Nanoha starts crying with joy. Meanwhile, at the TSAB HQ, Leti Lowran receives a report of an attack on the Bureau mages and forwards it to Mariel Atenza. At the site of the attack, an unnamed mage is easily defeated by Signum. As a last ditch effort, he summons a dragon but Signum kills it with ease and takes his Linker Core. She then contacts Vita and Zafira but they are busy, and so is Shamal, so Signum returns to her search. The chapter ends with brief shots of the Book of Darkness and Hayate Yagami.

DetailsEdit

Character appearancesEdit

Device appearancesEdit

Locations visitedEdit

Spells castEdit

ReferencesEdit

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.