Hello there! We are conducting a survey to better understand the user experience in making a first edit. If you have ever made an edit on Gamepedia, please fill out the survey. Thank you!

Fire Emblem Heroes Wiki:To-do list

From Fire Emblem Heroes Wiki
Jump to: navigation, search
Wip Laslow.png

Welcome to the wiki's to-do list. Here you can find all the tasks wiki editors plan to do. Feel free to add your own tasks to the list or complete a task. Once you complete a task, remove it from the list.

You may also hold discussions about tasks here if you want, remember to leave a signature with ~~~~ if you do so. Example:

==Current list==
*Do this
::Can this really be done? I tried it and I couldn't figure out anything. Username (talk) 12:12, 12 December 2012 (UTC)
::This is because the other tasks need to be done first, since this task relies on the other templates made by the other tasks. ~~~~
*Do another thing

Current list[edit source]

Please make sure all tasks placed here are removable, that is, they are one-time only (or a limited amount). Recurring tasks can go in the Recurring maintenance tasks section.

Uncategorized[edit source]

Place tasks here if you're not sure what category they go in or don't want to bother categorizing it.

  • Create StatusEffects. Defined here.
  • Find a way to transcribe the notification delivered via the Belgian noticeboard of the news of the game's impending discontinuation in Belgium.
I'm not really sure if it's okay to create a page for it, but you can see it right here: User:RainThunder0/Important notice (Belgium). -RainThunder0 (talk) 07:24, 23 May 2019 (UTC)

New content[edit source]

Tasks about newly added features or data in updates.

  • Create:
    • Weekly Revival Summoning Events
    • Lost Lore
      • {{OtherLanguages
        |english=Lost Lore
        |japanese=おでかけヒーローズ
        |german=Verlorene Kunde
        |spanishEU=Saberes perdidos
        |spanishLA=Saberes perdidos
        |french=Récits perdus
        |italian=Storie perdute
        |chineseTW=英雄出門去
        |portuguese=Memórias perdidas
        }}
    • White Rose and Sable Knight
      • Create {{Lost Lore Infobox}}
      • Improve visual rendering
      • "Start of the Strike" is a tenative name, think of a better one if you can. If not, that's fine too. Section internally referred to as MID_TRIP_SCENARIO_MANEUVER_INTRO. MANEUVER refers to Strike, as seen in MID_TRIP_MANEUVER_BUTTON_START ("Strike") and MID_TRIP_MANEUVER_SPAN ("Strike Lines").

Missing information[edit source]

Missing properties about the game data.

"Single-character" conversations no longer feature single characters in recent Forging Bonds, so this should be preferred to stay consistent with other uses of the story dialog templates. --HertzDevil (talk) 18:26, 24 July 2019 (UTC)
  • Dump in the text with no formatting at all (example: Celica C)

Wiki maintenance[edit source]

Reorganization of wiki texts and resources.

  • Update Free-to-Play Guide with information on versions 3.0.0—3.2.0.
  • update old availability dates (for quests, maps, etc) with links to the corresponding notifications, if applicable.
All summoning focus, Tempest Trials, Forging Bonds, GHB, BHB, Rival Domains, Relay Defense, Blessed Gardens and Tactics Drills until the 14 February 2019 are updated, except Tibarn's Agility and RD 16 as I can't find the notification. Pival13 (talk) 09:27, 15 February 2019 (UTC)

Code maintenance[edit source]

Modifications to templates, modules, and Cargo tables.

  • Move js code in MediaWiki:Common.js that isn't used commonly or globally into separate widgets. That's actually all the code except for mwCollapsibleSetup. Skill Build stuff and weapon dropdown are only used for a handful of pages, but browsers will be forced to download code they probably won't even use. Moving it to separate widget also allows passing in parameters through cargo and allows the weapon dropdown to make use of the weapon types table.
Done for the table dropdown lists (Widget:DropdownSelects, Widget:DropdownSelects/NoColor, Widget:DropdownSelects/Mobile), but for some reason $ is unavailable in those widgets so they use document.addEventListener('DOMContentLoaded', function () { ... }, false); for now. --HertzDevil (talk) 16:28, 6 June 2019 (UTC)
I think the weapon type "Dragonstone" should be "Breath". --Ninoninonii (talk) 17:47, 11 August 2019 (UTC)
Breath weapons are collectively refrered to as dragonstones. See here for further explanation. Markfeh (talk) 18:02, 11 August 2019 (UTC)
Ok, but if you go to Level_40_stats_table or Growth_rate_table, and select "Dragonstone" from the Weapon Type dropdown menu, the dragons do not show up. The "data-weapon-type" value for adult Tiki says "Red Breath" instead of "Red Dragonstone". --Ninoninonii (talk) 18:25, 11 August 2019 (UTC)
That's because individually they are referred to as breaths on the status pages of heroes. E.g. " Red Breath", " Blue Breath", " Green Breath", " Colorless Breath". When referring to all colors of breath weapons, they are called dragonstones. All inheritable dragonstones can be inherited to any dragon unit regardless of their color (unlike tomes). Markfeh (talk) 19:07, 11 August 2019 (UTC)
The reason why it is broken is because it relies on old code that hasn't been updated yet. I haven't touched yet it but I assume that is the case. It's still on this to-do list, which means it is still incomplete and in development. It also hasn't been updated to use the WeaponTypes and MoveTypes cargo tables and relies on hardcoded values. Endilyn (talk) 19:32, 11 August 2019 (UTC)
Fixed, pages should use {{DropdownSelects}} instead of invoking the widget directly. Is there any historical reason the other two widgets exist? --HertzDevil (talk) 22:18, 11 August 2019 (UTC)
I don't know but it looks like some of the styling doesn't work on the mobile view (boxes don't show up, just floating text and an arrow for the selectors). The /Mobile version works correctly with mobile. Though, I also don't know if it was necessary to split the widget to solve that problem. Also, is there a reason the list of classes is not queried? Endilyn (talk) 23:13, 11 August 2019 (UTC)
The lists of weapon properties are injected at query time into Template:Herogrid Entry and tables produced by Module:HeroTableBuilder using CONCAT(WeaponTypes.Type,';',WeaponTypes.Color,';',GROUP_CONCAT(DISTINCT WeaponTypes__Classes._value SEPARATOR ';')). Template:DropdownSelects supplies all those supported properties to Widget:DropdownSelects, which is why the widget itself does not perform any Cargo queries. --HertzDevil (talk) 23:29, 11 August 2019 (UTC)
I meant that I was wondering why Template:DropdownSelects uses a hardcoded list for classes that can be selected from instead of querying them like the other properties. Endilyn (talk) 23:53, 11 August 2019 (UTC)
The set of classes is expected to be stable over time, and also I prefer manually sorting those classes the way they are right now (the other alternative is GROUP_CONCAT(DISTINCT WeaponTypes__Classes._value SEPARATOR ',') |where=_value!='Magic' which follows alphabetical sort or an unspecified order). --HertzDevil (talk) 00:19, 12 August 2019 (UTC)
Done for the build pages as well (Widget:BuildDropdownFilter). --HertzDevil (talk) 23:11, 11 August 2019 (UTC)

Larger projects[edit source]

These tasks are more involved. Actions should be carefully reviewed before performing them, as there may be additional requirements/consequences that are not obvious at first glance.

Internationalization[edit source]

Do an automatic import of quotes in other languages, one language per tab. --Ale1991 (talk) 13:31, 21 August 2018 (UTC)

For non-English and non-Japanese languages, I propose that their subpages would be named after their language code in the game. /EUIT for example. Endilyn (talk) 23:03, 24 November 2018 (UTC)

Character / game pages[edit source]

More complete Tempest Trials data[edit source]

  • Store reward informations for each TT on its page. Currently only done on Chaos Named, and no other TT has reward information.
This is probably because all Tempest Trials except Chaos Named use the same reward pattern described on Tempest Trials. --HertzDevil (talk) 11:52, 2 August 2019 (UTC)

Reupload voice files[edit source]

Interactive event calendar[edit source]

  • Proof of concept: Event calendar. It doesn't work as of July 3, 2019 because of Cargo bug with compound query. Single query calendar like Summoning Focus calendar still works.
  • Currently, only SummoningFocuses, VotingGauntlets, and ForgingBonds have date columns. Other events, like Tempest Trials, etc. do not have a Cargo table, or their table doesn't have any Date or Datetime type column. The PoC above temporarily use the News table for Tempest Trials and Grand Conquests.
  • All special maps (GHBs, BHBs, LHBs, MHBs) also need a Cargo table that stores their availability dates.
{{#cargo_declare:
_table = MapDates
|StartDate=Datetime
|EndDate=Datetime
}}

The template should be used in Map availability section in those map pages. This Cargo table, if created, also helps automating {{Current Events}}, Special Maps, Grand Hero Battle maps etc.

  • Background color for each event types is not good at the moment, and needs some improvement. --RainThunder0 (talk) 09:49, 13 February 2019 (UTC)
Template and Cargo table created at Template:MapDates. Still needs work on its appearance and implementation. Endilyn (talk) 20:45, 2 July 2019 (UTC)
I did notice it for a while ago, but I actually forgot about it xD. I don't think there's a better way of retrieving date pairs from list other than this ugly query:
{{#cargo_query:
tables=MapDates__StartDate=SD,MapDates=MD,MapDates__EndDate=ED
|join on=MD._ID=SD._rowID,MD._ID=ED._rowID
|fields=MD._pageName=Page,SD._value=start,ED._value=end
|where=SD._position=ED._position
|group by=SD._value
|format=calendar
}}
For example, for Tap Battle (not in calendar format):
Page start end
Labyrinth of Mists 2018-02-09 00:00:00 2018-02-23 00:00:00
Shadowed Memories 2018-03-23 00:00:00 2018-04-06 00:00:00
Formidable Foes 2018-04-26 00:00:00 2018-05-11 00:00:00
Sanctuary of the Mages 2018-05-12 00:00:00 2018-06-11 00:00:00
Illusory Dungeon: Legendary Heroes 2018-06-11 00:00:00 2018-07-10 00:00:00
Summer of Heroes 2018-07-11 00:00:00 2018-08-10 00:00:00
Festival of Heroes 2018-08-11 00:00:00 2018-09-08 00:00:00
Farewells 2018-09-09 00:00:00 2018-10-11 00:00:00
Heir of Light 2018-10-12 00:00:00 2018-11-10 00:00:00
Labyrinth of Despair 2018-11-11 00:00:00 2018-12-08 00:00:00
Kingdom of Hoshido 2018-12-14 00:00:00 2019-01-10 00:00:00
Kingdom of Nohr 2019-01-15 00:00:00 2019-02-07 00:00:00
Carrying the Flame 2019-02-11 00:00:00 2019-03-04 00:00:00
Labyrinth of Mists 2019-03-10 00:00:00 2019-04-04 00:00:00
Heartstring's Ties 2019-04-20 07:00:00 2019-05-11 06:59:59
Shadowed Memories 2019-05-23 00:00:00 2019-06-13 00:00:00
Formidable Foes 2019-06-26 00:00:00 2019-07-17 00:00:00
Three Houses 2019-07-25 07:00:00 2019-08-15 06:59:59
Illusory Dungeon: Brave Heroes 2019-08-24 07:00:00 2019-09-21 06:59:59
I think it would be cleaner to use multiple entry per page. The template could be used in "Map availability" section, or integrate into {{Battle Infobox}} (which means we should get rid of Map availability section). Also StartDate and EndDate should be renamed to StartTime and EndTime, respectively.RainThunder0 (talk) 23:07, 2 July 2019 (UTC)
Internally those are duplicate Tap Battles with mostly identical data, not the same Tap Battle with multiple sets of dates (the first rerun is defined in files/assets/Common/TapAction/TapBattleData/TDID_0001_01.bin, and the original in files/assets/Common/TapAction/TapBattleData/TDID_0001.bin), so there should be one row for each run regardless of how the reruns are displayed. (This is in contrast for example to LHBs which do modify the dates of existing special map records in files/assets/Common/SRPG/StageEvent/*.bin.) --HertzDevil (talk) 17:06, 24 July 2019 (UTC)

Quests cargo table[edit source]

Create a template that will store a cargo table for quests, this will allow accessory pages, tap battle pages, etc. to query for related availability or rewards.

{{#cargo_declare:
_table = Quests
|WikiName=String
|Name=String
|Description=Wikitext
|Difficulty=String
|StartTime=Datetime
|EndTime=Datetime
|Reward=Wikitext
}}

Reward definitions[edit source]

Format reward information on the wiki for Module:ObjectArg, the same module that powers the unit definitions in Module:UnitData. The reward definition will have a representation similar to the game's reward payloads, e.g.:

[
  {kind=Hero;hero=Delthea: Tatarrah's Puppet;rarity=4};
  {kind=Hero Feather;count=2000};
  {kind=Fire Blessing}; <!-- "kind" uses actual item names whenever possible, eliminating e.g. the season or "is Great Badge" fields; "count" defaults to 1 -->
]

Then devise a unified template / module that displays these rewards. This is a necessary step towards automating pages such as Blessing distribution (the other part is figuring out how to store this variant data type into Cargo tables). --HertzDevil (talk) 09:19, 25 July 2019 (UTC)

The following fields are sufficient for all reward types if we exclude Forging Bonds conversations and Concert Hall background music from reward payloads:
{{#cargo_declare:_table=Rewards
|Kind=String (mandatory)
|Amount=Integer (mandatory)
|Unit=String <!-- Units.WikiName -->
|Rarity=Integer
|SacredSeal=String <!-- Skills.WikiName -->
|Accessory=Page <!-- Accessories._pageName -->
}}
The Unit and Rarity fields are compatible with Distributions. The real question is where to store the necessary join information and the start / end times, since there are just so many sources of rewards in the game (22 directories under files/assets/Common/ contain reward payloads). --HertzDevil (talk) 23:10, 4 August 2019 (UTC)
WIP module available at Module:Reward. rewardText formats a single reward, mapRewards formats rewards at multiple difficulties. Template wrappers will be added later. Example for Delthea: Tatarrah's Puppet (map):

Delthea Tatarrahs Puppet Face FC.pngPane 3.png (Hard)

Delthea Tatarrahs Puppet Face FC.pngPane 4.png (Lunatic)

Delthea Tatarrahs Puppet Face FC.pngPane 4.png +  2,000 (Infernal)

and Enchantress of the Mist:

Fjorm Princess of Ice Face FC.pngPane 5.png +  1 (Normal)

 1 (Hard)

 1 (Lunatic)

I am leaned towards creating a separate table for every kind of event that already has a table; these reward tables receive whatever information is necessary for joins, plus the reward fields above. For example, Maps would receive:
{{#cargo_declare:_table=MapRewards
<!-- to be used inside Template:Battle Infobox, so _pageName can be used for joins -->
|Difficulty=String
<!-- reward fields -->
}}
while TempestTrials receives:
{{#cargo_declare:_table=TempestTrialsRewards
<!-- to be used inside Template:Tempest Trials Infobox, so _pageName can be used for joins -->
|Score=Integer
<!-- reward fields -->
}}
The code would then explicitly state the reward sources considered, by choosing one of the many reward tables, e.g. Template:Forging Bonds accessory would only query the rewards table for Forging Bonds and nothing else. Distributions would stay, because it is infeasible for certain operations like getting Hero reward rarities to query all the reward tables; should the need arise, there will be similar tables for other specific types of rewards. --HertzDevil (talk) 04:39, 12 August 2019 (UTC)

Messages cargo table[edit source]

Create a cargo table for the messages with one column for the message ID and the other columns for the message text in the various languages. Ex.:

ID EUIT JPJA TWZH EUDE EUEN USEN EUES EUFR USES USPT
MID_PORTRAIT_TITLE_201902 Il kitsune in giallo 消えたオーブの謎 寶珠消失之謎 Der Sphärendieb The Orb Case The Orb Case Robo de orbes Le vol d'orbes Robo de orbes Cadê os orbes?


then use the cargotable to display the text in all the wiki. I think it's more easy to populate one table from the text dumps and then query that table instead of having all the texts scattered around. --Ale1991 (talk) 01:33, 13 May 2019 (UTC)

Problems:

  1. I cannot think of a situation where this would be useful, and there has been no explanation of how this would be implemented. Names and descriptions are already stored for data such as skills and events in their own and storing those in the same table appears to serve no purpose besides making queries more difficult. To "populate one table from the text dump and then query that" would not be easier, it would mean everything would require one or more ID fields to be added on each page, which is still manual work and at that point it is better to just add the text directly since the ID fields would never see any use besides to pull up the description/name.
  2. Not all game text on the wiki is represented exactly the same as the in-game string. There are various formatting changes as well such as adjusting whitespace or inserting html/wikitext inside some strings.
  3. This wiki will quickly run into a problem if there is nobody around to update the text fields. This is not something that can be done easily by the average user without access to the game files or scripts, unlike the current method of putting in text. It is also possible that we may not always have access to these files in the future in the (albeit unlikely) event Intelligent Systems does something such as encrypting them like they did with summoning images. No information that can be accessed without the game files in this wiki mandatorily requires accessing the game files to add.

Endilyn (talk) 07:05, 14 May 2019 (UTC)

Descriptions are never automatically populated from text dumps because links to other articles may be added to them.
I think it is more important to recognize that we don't query Languages that often. We do however already have two sets of IDs in use: Maps.Map, the map file names, and Skills.WikiName, the invented unique identifiers that substitute the real SIDs. The addition of ID fields would be a lot easier if it is restricted to the tables we already have (Heroes, skills, maybe structures and accessories), and they would help write utility scripts on the wiki such as Module:ScenarioArchiveToWiki and Template:NpidToNameplateJP that do use the available dumps.
--HertzDevil (talk) 11:10, 28 May 2019 (UTC)

Arena score research[edit source]

Fire Emblem Heroes Wiki:To-do list/Arena score research (Needs some adjustments before opening to public)

Recurring maintenance tasks[edit source]

The lists here use cargo queries to automatically display the status of certain tasks. The cargo queries update slowly, so they may not reflect the most recent status. List of reoccurring maintenance tasks:

Quests[edit source]

See /Pending Quests.

Item distribution[edit source]

Twitter-related[edit source]

Quote pages with missing audio files[edit source]

Pages with incomplete skill data[edit source]

No results

List of pages with incomplete enemy data[edit source]

Page Map Unit Pos Rarity Slot Level HP Atk Spd Def Res Weapon Assist Special PassiveA PassiveB PassiveC Seal
Part 1: Launch Celebration V0001 Gordin Altean Archer b7 5 19 8 6 9 3 Iron Bow
Part 2: Launch Celebration V0002 Sharena Princess of Askr b7 5 19 9 9 7 4 Iron Lance
Part 3: Launch Celebration V0003 Barst The Hatchet a8 5 20 10 9 6 3 Iron Axe
Part 4: Launch Celebration V0004 Leo Sorcerous Prince a8 5 17 8 4 6 9 Flux
Part 5: Launch Celebration V0005 Felicia Maid Mayhem b5 5 15 5 12 2 10 Iron Dagger
Part 1: Starter Support V0011 Corrin Fateful Prince c5 5 21 9 9 7 6 Iron Sword
Part 2: Starter Support V0012 Eldigan Lionheart d5 5 20 9 6 9 6 Iron Sword
Part 1: Defensive Battle V0021 Lance Fighter ENEMY a3 10 24 11 11 12 8 Iron Lance Armored Blow 1
Part 2: Defensive Battle V0022 Lance Cavalier ENEMY e2 15 25 15 10 11 14 Steel Lance
Part 3: Defensive Battle V0023 Niles Cruel to Be Kind a8 25 28 16 21 10 21 Steel Bow Windsweep 1

More...

Map pages with missing BGM data[edit source]

_pageName Map MapName BGM BGM2
Fire 10: Terrace BG_FIRE_0010 Fire 10: Terrace
Fire 7: Colonnade BG_FIRE_0007 Fire 7: Colonnade
Fire 8: Bridge BG_FIRE_0008 Fire 8: Bridge
Grounds of Wind: Wind 1 BG_WIND_0011 Wind 1
Inside Embla S3103 Inside Embla
Maiden and Devotee S3102 Maiden and Devotee
Part 7: Daily (Dec 2017) V0127 Part 7: Daily
Rival Domains: Event Map (28) Q0028 Rival Domains: Event Map
Rival Domains: Event Map (29) Q0029 Rival Domains: Event Map
Rival Domains: Event Map (30) Q0030 Rival Domains: Event Map

More...

List of pages with incomplete languages[edit source]

_pageName English Japanese German SpanishEU SpanishLA Italian French ChineseTW Portuguese
2nd Anniversary Heroes 2nd Anniversary Heroes Héros du 2e anniversaire
4 Star & 5 Star Heroes (Apr 2018) (Focus) Focus: 4★ & 5★Heroes
4 Star & 5 Star Heroes (Jan 2018) (Focus) Focus: 4★ & 5★Heroes
4 Star & 5 Star Heroes (Mar 2018) (Focus) Focus: 4★ & 5★Heroes
A Hero's Mettle A Hero's Mettle Cœur de héros
A Knight's Mercy A Knight's Mercy Chevalier sauveur
A Pause in Hostilities A Pause in Hostilities
A Promise of Joy A Promise of Joy Paraíso ilusorio Paradis Promis
A Season for Picnics (Focus) A Season for Picnics
A Trust Earned A Trust Earned Piena fiducia

More...

_pageName English Japanese German SpanishEU SpanishLA Italian French ChineseTW Portuguese
2nd Anniversary Heroes 2nd Anniversary Heroes Héros du 2e anniversaire
4 Star & 5 Star Heroes (Apr 2018) (Focus) Focus: 4★ & 5★Heroes
4 Star & 5 Star Heroes (Jan 2018) (Focus) Focus: 4★ & 5★Heroes
4 Star & 5 Star Heroes (Mar 2018) (Focus) Focus: 4★ & 5★Heroes
A Hero's Mettle A Hero's Mettle Cœur de héros
A Knight's Mercy A Knight's Mercy Chevalier sauveur
A Pause in Hostilities A Pause in Hostilities
A Promise of Joy A Promise of Joy Paraíso ilusorio Paradis Promis
A Season for Picnics (Focus) A Season for Picnics
A Sketchy Summer (Focus) A Sketchy Summer 夏、再び Eroi speciali: Schizzi d'estate

More...

_pageName English Japanese German SpanishEU SpanishLA Italian French ChineseTW Portuguese
2nd Anniversary Heroes 2nd Anniversary Heroes Héros du 2e anniversaire
4 Star & 5 Star Heroes (Apr 2018) (Focus) Focus: 4★ & 5★Heroes
4 Star & 5 Star Heroes (Jan 2018) (Focus) Focus: 4★ & 5★Heroes
4 Star & 5 Star Heroes (Mar 2018) (Focus) Focus: 4★ & 5★Heroes
A Hero's Mettle A Hero's Mettle Cœur de héros
A Knight's Mercy A Knight's Mercy Chevalier sauveur
A Pause in Hostilities A Pause in Hostilities
A Promise of Joy A Promise of Joy Paraíso ilusorio Paradis Promis
A Season for Picnics (Focus) A Season for Picnics
A Sketchy Summer (Focus) A Sketchy Summer 夏、再び Eroi speciali: Schizzi d'estate

More...

_pageName English Japanese German SpanishEU SpanishLA Italian French ChineseTW Portuguese
2nd Anniversary Heroes 2nd Anniversary Heroes Héros du 2e anniversaire
4 Star & 5 Star Heroes (Apr 2018) (Focus) Focus: 4★ & 5★Heroes
4 Star & 5 Star Heroes (Jan 2018) (Focus) Focus: 4★ & 5★Heroes
4 Star & 5 Star Heroes (Mar 2018) (Focus) Focus: 4★ & 5★Heroes
A Hero's Mettle A Hero's Mettle Cœur de héros
A Knight's Mercy A Knight's Mercy Chevalier sauveur
A Pause in Hostilities A Pause in Hostilities
A Season for Picnics (Focus) A Season for Picnics
A Sketchy Summer (Focus) A Sketchy Summer 夏、再び Eroi speciali: Schizzi d'estate
A Trust Earned A Trust Earned Piena fiducia

More...

_pageName English Japanese German SpanishEU SpanishLA Italian French ChineseTW Portuguese
2nd Anniversary Heroes 2nd Anniversary Heroes Héros du 2e anniversaire
4 Star & 5 Star Heroes (Apr 2018) (Focus) Focus: 4★ & 5★Heroes
4 Star & 5 Star Heroes (Jan 2018) (Focus) Focus: 4★ & 5★Heroes
4 Star & 5 Star Heroes (Mar 2018) (Focus) Focus: 4★ & 5★Heroes
A Hero's Mettle A Hero's Mettle Cœur de héros
A Knight's Mercy A Knight's Mercy Chevalier sauveur
A Pause in Hostilities A Pause in Hostilities
A Promise of Joy A Promise of Joy Paraíso ilusorio Paradis Promis
A Season for Picnics (Focus) A Season for Picnics
Academy Cap Academy Cap

More...

_pageName English Japanese German SpanishEU SpanishLA Italian French ChineseTW Portuguese
4 Star & 5 Star Heroes (Apr 2018) (Focus) Focus: 4★ & 5★Heroes
4 Star & 5 Star Heroes (Jan 2018) (Focus) Focus: 4★ & 5★Heroes
4 Star & 5 Star Heroes (Mar 2018) (Focus) Focus: 4★ & 5★Heroes
A Pause in Hostilities A Pause in Hostilities
A Season for Picnics (Focus) A Season for Picnics
A Sketchy Summer (Focus) A Sketchy Summer 夏、再び Eroi speciali: Schizzi d'estate
A Trust Earned A Trust Earned Piena fiducia
Academy Cap Academy Cap
Accessory Shop Accessory Shop アクセサリー屋
Alm: Saint-King (map) Alm: Saint-King (map)

More...

_pageName English Japanese German SpanishEU SpanishLA Italian French ChineseTW Portuguese
2nd Anniversary Heroes 2nd Anniversary Heroes Héros du 2e anniversaire
4 Star & 5 Star Heroes (Apr 2018) (Focus) Focus: 4★ & 5★Heroes
4 Star & 5 Star Heroes (Jan 2018) (Focus) Focus: 4★ & 5★Heroes
4 Star & 5 Star Heroes (Mar 2018) (Focus) Focus: 4★ & 5★Heroes
A Hero's Mettle A Hero's Mettle Cœur de héros
A Knight's Mercy A Knight's Mercy Chevalier sauveur
A Pause in Hostilities A Pause in Hostilities
A Promise of Joy A Promise of Joy Paraíso ilusorio Paradis Promis
A Season for Picnics (Focus) A Season for Picnics
A Sketchy Summer (Focus) A Sketchy Summer 夏、再び Eroi speciali: Schizzi d'estate

More...

_pageName English Japanese German SpanishEU SpanishLA Italian French ChineseTW Portuguese
2nd Anniversary Heroes 2nd Anniversary Heroes Héros du 2e anniversaire
4 Star & 5 Star Heroes (Apr 2018) (Focus) Focus: 4★ & 5★Heroes
4 Star & 5 Star Heroes (Jan 2018) (Focus) Focus: 4★ & 5★Heroes
4 Star & 5 Star Heroes (Mar 2018) (Focus) Focus: 4★ & 5★Heroes
A Hero's Mettle A Hero's Mettle Cœur de héros
A Knight's Mercy A Knight's Mercy Chevalier sauveur
A Pause in Hostilities A Pause in Hostilities
A Promise of Joy A Promise of Joy Paraíso ilusorio Paradis Promis
A Season for Picnics (Focus) A Season for Picnics
A Sketchy Summer (Focus) A Sketchy Summer 夏、再び Eroi speciali: Schizzi d'estate

More...

Rival domains related[edit source]

Incomplete Rival Domains (queries for BGM to determine incompleteness, may not be completely accurate):

Missing story text[edit source]

Note: This list is not conclusive, it only lists pages where the story template was added with empty fields. There may be story text missing when the template is not used at all.

English:

Japanese:

Missing story navigation[edit source]

Uses of Template:Story Navbar with either the previous or next map missing are listed here. There should be exactly one item on this list corresponding to the most recent story.