Fire Emblem Heroes Wiki:To-do list

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 informal 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

Speed, convenience, and ease of use are prioritized for the to-do list. You do not have to worry about presentability when adding a task, especially due to the transient nature of the to-do list.

Tasks that might be impossible or no longer possible go on /Impossible tasks.

Current list
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.

Do not add tasks that solely require sysop rights, contact an administrator for that. Note that tasks that do not only consist of parts that require sysop rights can be added, such as adding/fixing things related to code. For example, anyone can create template and design its cargo system, sysop rights are only needed at the final step of creating the table.

Uncategorized
Place tasks here if you're not sure what category they go in or don't want to bother categorizing it.
 * Correct Rival Domains: Event Map (162) map layout.
 * 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)


 * Spring Festival (Focus), being the first page to contain 4 summoning events, causes Lua to time out due to Module:FocusRates. Possible solutions:
 * Optimize the module until it takes Lua well below 7 seconds to execute the code on that page;
 * Replace the simulations with purely theoretical values;
 * Remove the simulations altogether;
 * Remove all simulations except the most recent one (after the module is fixed for focuses, see above);
 * Move the simulations to subpages (this doesn't solve the issue if the simulations alone still take more than 7 seconds to run);
 * Rewrite the simulator as a widget.
 * That page currently has all simulations removed. This has to be decided ASAP since other pages will soon contain 4 summoning events as well (the Weekly Revivals and the Year 1 Special Heroes). --HertzDevil (talk) 14:49, 5 April 2020 (UTC)
 * I have tried to optimize it as much as I can with my amateur programmer skills, but it doesn't appear to be possible to get any more performance out of it (but I could be wrong), so that solution is out. Replacing the simulations with purely theoretical values sounds like the best option, but I do not know how to calculate the rates. So besides these, the best option is probably to rewrite it as a widget and have the clients handle running the simulation. For now, simulations have been temporarily disabled. Endilyn (talk) 23:00, 8 April 2020 (UTC)


 * Finish . Format isIf unsure about addition times for previous data updates, 3 hours before release is usually acceptable. The addition time for the first data update of each version should match the release time of that version update (see ). Preview notifications for Special Heroes should be the ones with YouTube trailers and unit descriptions, rather than the silhouette ones. --HertzDevil (talk) 15:53, 21 May 2020 (UTC)
 * A list of tag and their approximate date has been made. However note that this list is potentially incomplete and/or incorrect. Pival13 (talk) 09:45, 17 April 2021 (UTC)
 * Categorize the following notifications to subcategories of Category:News:
 * 21st Annual D.I.C.E. Awards Celebration Giveaway! (Notification)
 * Arena Promotion (Notification)
 * Concerning the scheduled maintenance for the survey (Notification)
 * Double EXP & SP (Dec 2017) (Notification)
 * Double EXP & SP Event (Notification)
 * EXP x1.5 Event (May 2017) (Notification)
 * EXP x1.5 Event (Notification)
 * Extra Sacred Seals (Notification)
 * Extra Sacred Seals (Sep 2017) (Notification)
 * Fall Log-In Bonus! (Notification)
 * Fire Emblem Echoes: Shadows of Valentia - Release Celebration Bonus (Notification)
 * Fire Emblem Heroes Quiz Reward (Notification)
 * Fire Emblem Heroes wins Best Game of 2017! (Notification)
 * Fire Emblem Warriors Release Celebration Log-In Bonus (Notification)
 * Get Your Ike: Vanguard Legend! (Notification)
 * How to Unlock the Weapon Refinery (Notification)
 * New Year's Event (Notification)
 * Nintendo Switch Release Celebration Bonus (Notification)
 * One-Year-Anniversary Celebration! (Notification)
 * One-Year-Anniversary Hero Fest (Notification)
 * Play Everyday Event (Notification)
 * Quick Hero Battle (Notification)
 * Quick Hero Battle Rewards (Notification)
 * Quick Hero Battle: Final Results (Notification)
 * Rewards from the Tempest Trials Kick-Off Campaign (Notification)
 * Sacred Seal Forge Support Event! (Notification)
 * Six-Month Anniversary Celebration! (Notification)
 * Special Quests: Sacred Seals (May 2017) (Notification)
 * Special Quests: Sacred Seals (Notification)
 * Summer Log-In Bonus! (Notification)
 * Survey Participation Reward (Notification)
 * Survey Request (Notification)
 * The One-Year-Anniversary Celebration Is On Its Way! (Notification)
 * The Opening Movie for Book II Is Here! (Notification)
 * Three-Part Starter Support Event (Notification)
 * Tips for Rival Domains (Notification)
 * Weekend Special: Earn Double SP! (Notification)
 * Winter Log-In Bonus! (Notification)
 * Worldwide Launch Celebration (Notification)

Missing information
Missing properties about the game data.
 * Create:
 * Frontline Phalanx
 * Project:Build Center/Skill
 * Resonant Battles
 * Limited Hero Battles and associated Cargo tables
 * Fire Emblem Heroes: Learn with Sharena
 * Training Tower/Ninth Stratum
 * [[Media:STORYOP4.webm]]
 * [[Media:STORYOP4_2.webm]]
 * Duo Heroes
 * List of Duo Skills
 * Weekly Revival Summoning Events
 * A Hero Rises 2020 (Event)
 * Mjölnir's Strike
 * Talk:Mjölnir's Strike
 * Hall of Forms
 * Lost Lore
 * Lost Lore research discussion
 * Resplendent Heroes
 * Voting Jubilee
 * Finish writeup on Story.
 * Create and expand on story-related pages (Freyr,Freyja,Plumeria,Dökkálfheimr,Ljósálfheimr,Alfaðör, Angrboða, Askr, Embla, Kiran, Breidablik, Order of Heroes, Snjársteinn, Nifl, Múspell, Menja, Zenith, etc.)
 * Double-check maps whose BGM is listed as "Under this Flag" (bgm_map_FE03_01.ogg) or "The Time to Act" (bgm_map_FE11_01.ogg). Since the two songs sound very similar, there's an inconsistency between Michalis' map page and the BGM page. Might as well check the other maps that use these songs, just to be sure.
 * Add Forging Bonds transcriptions. Videos are provided here to aid transcription. A list of all pages missing story dialogue is listed in the recurring tasks section.
 * Defending Ylisse
 * Japanese text: [[Media:defending ylisse_jp.webm]]
 * Rejecting Destiny
 * Japanese text: [[Media:rejecting_destiny_jp.webm]]
 * Create Fire Emblem Heroes Quiz (Event). See Fire Emblem Heroes Quiz Reward (Notification) and Twitter with flags "#FEHQuiz from:FEHeroes_News since:2018-04-20 until:2018-05-15"
 * Create Feh's Quiz Event (Event). See Feh's Quiz Event Rewards (Notification) and Twitter with flags "#FehQuiz from:FE_Heroes_EN since:2019-10-08 until:2019-10-19"
 * Fill all missing map layouts in Grand Conquests.
 * Grand Conquests 1: Area 1, 14, 23.
 * Grand Conquests 2: Area 1, 3, 5, 8, 10, 11, 17, 22, 23, 24, 25, 27, 28, 30.
 * Grand Conquests 3: Area 2, 4, 6, 7, 9, 10, 12, 13, 15, 17, 21, 25, 26, 28.
 * Grand Conquests 4: Area 1, 3, 7, 8, 13, 14, 17, 25.
 * Add "first available" dates to the unit data on Reward units with the firstdate parameter, using availability information of the associated quests / events. This will allow the distributed unit list to preserve the current sort order by displaying those dates, and without having to maintain Module:RewardUnitTable/data manually. --HertzDevil (talk) 08:44, 24 July 2019 (UTC)
 * Automatic, Story, Log-in, and Map reward units complete. Only Quests remain.
 * Purchased (Starter Support Pack, New Year's Bundle, Byleth-M) and Grails units are not visible on the reward units page, but should also have firstdate fields added. Boblers7 (talk) 21:14, 16 September 2019 (UTC)
 * Update: all units currently in the Distributions cargo table now have "first available" dates added. Since this essentially makes Module:RewardUnitTable/data extraneous, should the note about it on the Reward Units article be removed? Additionally, if I'm understanding correctly, should the Reward Units table display the earliest firstdate field in a new column, similar to how the current version displays the latest lastdate in a column? --Boblers7 (talk) 00:10, 17 September 2019 (UTC)
 * Done. --HertzDevil (talk) 10:45, 21 September 2019 (UTC)
 * This removes the sort between Heroes with the same date, like the starting Heroes for instance. Heroes from Three Hero quests are also meant to be obtained in a specific order, since one quest rewards a Hero that allows another quest to be completed, and so on. Endilyn (talk) 02:36, 27 September 2019 (UTC)
 * Hm, good point. How should we approach this, though? We could bring back Module:RewardUnitTable/data, but then we'd have come full circle and have to maintain it going forward. Alternatively, perhaps each Reward Unit table entry could have some tie-breaker field added? For example, Heroes released at the same time could be assigned a tie-breaker number of 1, 2, 3, etc according to their obtaining order. Sorting would then sort first by initial date, then by tie-breaker, both ascending.--Boblers7 (talk) 04:18, 27 September 2019 (UTC)
 * You don't need the rewarded unit from a Three Heroes quest to finish the other quests, though. There is no need to maintain the quest order on a table that lists all reward sources; besides, these quests won't be able to maintain the sort order anyway if any unit is already previously handed out. We could do that when we have the quest tables ready and display separate tables for each kind of reward source.
 * If we carefully lay out the data definitions, then  may be used as a tie-breaker, since it maintains the relative order between   invocations. Template:Heroic Grails Hero List does this, but this is not as easy if the definitions are not all from the same page. --HertzDevil (talk) 10:07, 27 September 2019 (UTC)


 * Document Aether Raids changes in 3.6.0 - 3.9.0 (defense rewards, double cost)
 * Find out and document how bane neutralization from the first merge affects levels 1-39 and document in Stat growth
 * It seems stats with a flaw are then consider as normal. When the flaw stat is greater or equal to the neutral stat, it still gain +1, and follow the flaw line of stat until the normal line of stat become greater or equal. Some example: a Florina, level 25 with a flaw on Res (20 Res) have after the merge 26 Res. A Seliph level 21 with flaw on Res (10 Res) have 11 Res after the merge. Then it gains +1 on level 23, 25 and 28, where the normal Res is greater than the flaw. The next stat increased is at level 29.
 * Dragonflower seems to follow a similar rule. As an example, an Edelgard with flaw on Atk which receive two dragonflowers have +1 on HP and Def. After the merge, the Def still have the bonus with dragonflower. Pival13 (talk) 19:32, 12 October 2019 (UTC)
 * Fix a bug on Stats calculator where Flaw stats increase by 3 or 4 on Lv 1 after the first merge, rather than by 1.
 * Reupload:
 * File:VOICE Arden Strong and Tough ATTACK 1 jp.wav with https://cdn.discordapp.com/attachments/273269173118042112/615377804032344066/VOICE_Arden_Strong_and_Tough_ATTACK_1_jp.wav
 * File:VOICE Kjelle Fair Fighter DEAD 1 jp.wav with https://cdn.discordapp.com/attachments/273269173118042112/615377809593991186/VOICE_Kjelle_Fair_Fighter_DEAD_1_jp.wav
 * File:VOICE Lif Lethal Swordsman STATUS 6 jp.wav with https://cdn.discordapp.com/attachments/273269173118042112/672332931662086144/VOICE_Lif_Lethal_Swordsman_STATUS_6_jp.wav
 * Aether Resort
 * document R&R Affinity costs of Structure slots #19-24
 * recover the dates that new Hero slots, Structure slots, and Amenities were added
 * The version 2.10.0 update on added Abyssal modes to the GHB Rotation 1 maps, but since these maps change each day, not every map's new Abyssal mode was actually playable on the day of the update. Therefore, we need to calculate the earliest date after the update that each map was available to play. Then, change the phrase "(Abyssal difficulty was added on 2018-10-09T03:00:00Z)" on each map's article to reflect that calculated start date.
 * Dining Hall research to be done:
 * What happens when a dish fails?
 * Do secret ingredients have any effect on star rating? For example, do they allow dishes to reach that cannot otherwise reach that rating? Does using a secret ingredient make it impossible to have a star rating below, or even ?
 * What is the difference in effect between Choice Meat vs regular Meat, and Choice Eggs vs regular Eggs? Do they only take effect when used as secret ingredients, or do they also affect the dish when used as normal ingredients? Do they have any effect on star rating?
 * If a dish is made Home-Style, does that affect star rating?
 * If a 2-ingredient dish is made as a result of an invalid 3-ingredient dish, does that affect star rating? Does this also apply to 2-ingredient dishes made from invalid 4-ingredient dishes, and 3-ingredient dishes made from invalid 4-ingredient dishes?
 * Missing voice files:
 * All of Chrom: Crowned Exalt's JP voice files
 * All of Resplendent Micaiah's voice files
 * Add BGM of extra stages to the list of BGM on Tap Battle

Wiki maintenance
Reorganization of wiki texts and resources.
 * Update Project:Beginner's guide with information on versions 4.0.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)


 * Add  and   to descriptions for all   fields.
 * Replace dates with UTC datetimes whenever possible, to avoid confusion.
 * Some places, such as Squad Assault and Use Heroic Grails availability, require datetimes for app or data updates, but exact times for these updates are unknown because some devices in some parts of the world may receive updates earlier than the others. Decide on a convention to use when determining past update datetimes (e.g. assume all data updates associated with summoning events happen 2.5 hours before the summoning event). --HertzDevil (talk) 10:26, 4 September 2019 (UTC)
 * I think the first recorded time is sufficient. However I don't think all times should be assumed to be a single offset from before the summoning event, but that could be used if there is no information since accuracy down to the hour is not too important for these. Endilyn (talk) 05:09, 5 September 2019 (UTC)
 * App updates could use the upload times of their associated notifications which should be good enough. --HertzDevil (talk) 09:07, 5 September 2019 (UTC)
 * Add to pages with story dialogue that are missing story background images.
 * Add official names for some Arena maps from https://guide.fire-emblem-heroes.com/en-US/sa033/ to Arena and List of Arena maps
 * 9 out of 10 arena maps added in Version 2.1.0 have trenches, I don't think calling one of them "the" trench map would be helpful at all. Adding those names to a trivia section should be enough. --HertzDevil (talk) 21:50, 24 August 2019 (UTC)
 * Replace screenshot files on the wiki with up-to-date screenshots or files with dimensions 1080 × 1920, where applicable.
 * Decide on how to display Røkkr Sieges availability: Røkkr Sieges 1 has none, Røkkr Sieges 2 uses the round table for Voting Gauntlet, Røkkr Sieges 3 uses an availability section similar to maps.
 * I just put both in one on Røkkr Sieges 4. Pival13 (talk) 17:12, 19 September 2019 (UTC)
 * Update old Quests and Missions archive pages with.
 * Correct quests with missing or potentially incorrect informations or rewards using these JSON dumps (since 2017-02-02 until 2020-06-30, using HertzDevil's format).

Code maintenance
Modifications to templates, modules, widgets, and Cargo tables.
 * Modify Template:Structure Infobox so that it stores one row per level for each structure, rather than one row for all levels
 * Add better support to Module:SummoningEvent for Summoning Focuses with limited pulls, since statistics for multiple pulls should not be shown there:
 * Known units, e.g. New Heroes: Brave Heroes
 * Unknown units with known colors, e.g. Special Hero Summon (Year 1)
 * Unknown colors, e.g. 2nd Anniversary Heroes
 * Describe the April 2019 summoning pool changes on Summonable Heroes, which uses Module:HeroListBySummonRarity and Module:SummonableHeroList.
 * Define the random unit pool via Template:Hero Infobox rather than Randomized units. Assume the timestamps for all Heroes before the Fire and Ice update are correct and never modified in history.
 * Update the enemy slots in the Randomized Units sections on each Tempest Trials page to match the slot indices from Module:UnitData. (Just remove the "(slot x)" part entirely and adjust the "Enemy x" number.) --HertzDevil (talk) 19:51, 10 August 2019 (UTC)
 * Done. I was just wandering what is the difference between and  as they are both used. Pival13 (talk) 19:04, 21 August 2019 (UTC)
 * The former uses the random unit pool directly, the latter queries the unit table and assumes that units are added to the random pool as they are released (which is wrong). The reason we haven't fully switched to Template:RandomTTUnits is because we do not have the random pool information before the end of Book II yet. --HertzDevil (talk) 06:03, 22 August 2019 (UTC)
 * We now have everything in, so can be replaced with  if the two output the same units. --HertzDevil (talk) 15:53, 29 September 2019 (UTC)
 * The later template does not assume that, the input date is supposed to match their release date only for differentiating earlier and later groups of Heroes for the purpose of selecting them, so the date would often not match the Tempest Trials dates. Since the order of Heroes released and the order of them being added to the random pool were the same, the template worked, even if the actual times had a gap. I agree that it was not a good system though. The assumption that "timestamps for all Heroes before the Fire and Ice update are correct and never modified in history" is also incorrect. It also seems that brave heroes (and possibly staff users) may have had their random status modified at one point. User:Valexiv appears to have left relevant notes whenever the random pool changed on the appropriate pages (e.g. Tempest Trials or Rival Domains pages), but these notes are scattered and not consolidated so they will be difficult to sift through, it is unknown whether they are complete, and they may have been deleted in batch page editing. Endilyn (talk) 19:23, 29 September 2019 (UTC)
 * The last point is right; I checked RainThunder's files and found that these Heroes used to be in the random pool:
 * CYL1 Heroes were available during -  (the 2017_09_15 update to be exact).
 * Olivia, Azura, and Ninian were available since launch and removed at either 2017_08_29 or 2017_09_06 (which cannot be determined from those files alone as one revision was missing).
 * All other changes to the random pool were correct. --HertzDevil (talk) 10:05, 21 May 2020 (UTC)

or Rename Units.Origin to Units.Appearances and do the appropriate replacements or Do nothing as we have been doing, and leave the field as it is since the internal name is not displayed anywhere, just remember that the field actually stands for appearances, not origin. Endilyn (talk) 21:03, 6 September 2019 (UTC) Never displayed anywhere except for Template:Characters Navbox where it makes no significant difference compared to just displaying the page name, and actually conflicts with Lucina, displaying "Marth" instead. Exists solely for joining with for the purposes of differentiating duplicate  values. The second portion of the origin value, i.e. the portion that follows. value of Heroes that come from the corresponding game. The second portion of the origin value, i.e. the portion that follows series. This eliminates the need for a wiki-defined Person parameter. May be autogenerated in the same manner as currently is (see notes later under both tables). Derived from processing the description. Semantically means the games a Hero appears in, use for pages like game pages or List of Heroes by appearance. The "Appears in" text will need to be re-added to the Hero descriptions for this. This will also have the benefit of making the descriptions 1 to 1 with the game. An automatic exact copy of. Intelligent Systems will make them correspond to each other. Manual entry is allowed in the case that this is ever not the case or processing fails due to a typo (such as the "Appear in" typo previously at Marth: Royal Altean Duo's description). Semantically means the game data for entries used in the filter menu, for use in pages like limited hero battles. No changes. With this new structure, the separation of pure game data and wiki-specific data should be clearer. The only benefit to the old system I can think of is that it saves entering origin values for every new Hero, but this is faulty as well, since technically every new Hero would then need a Units.Person entered in order to link them to their origin values. The benefit is that Units.Person defaults to Units.Name, but a similar benefit can be had with csv2 defaulting to a csv2 from another Hero with the same Units.Name and Units.Series only if one distinct value is returned. This makes an assumption, but it is the same assumption the current system makes. Additionally, in both defaulting systems, a csv2 must be entered at least once somewhere on the wiki. Endilyn (talk) 08:21, 25 May 2020 (UTC)
 * Edit Hero Infobox to store and display multiple origins. (Naga: Dragon Divinity Appears in Fire Emblem: Mystery of the Emblem and Fire Emblem: Awakening)
 * These are not origins like the in-game Origin/Character value used in Lost Lore or Catalog of Heroes, that is simply flavor text from the description, although they are often made to match and get confused between a lot. That's why the Hero Infobox says "Appears in" instead of "Origin". I actually think the Hero descriptions on the wiki should not be trimmed and should include everything, including the "appears in" section. As it is right now, the cargo and template fields are named 'Origin', yet correspond to Appearances, and the true Origin value when needed is derived from Appearances with . Two possible suggestions: Change to actually define "Origin", then create  as a   and use that on pages that want the appearances like Series Distribution, List of Heroes, and the game pages accordingly.
 * Entry sort lists Naga under both series, and similarly for Leif; they are the only Heroes whose . The   field is being used in the in-game filter and Limited Hero Battles, so sooner or later the information needs to be somewhere in the database. --HertzDevil (talk) 10:05, 21 May 2020 (UTC)
 * I propose the following changes. In the following,  means "the game portion of the origin value". .        All games represented when using the "Entries" filter, minus the games that are already present in .        Exists solely for joining with . Defaults to .  In other words, it exists solely to resolve composite key issues that would arise from using  corresponding to  + .      Defined by wiki to be name of a character, which is defined by wiki. The only strict requirement is that it must be able to uniquely identify a given origin value alongside . Defaults to the page name it is defined on.  In other words, it exists solely to resolve composite key issues that would arise from using  corresponding to  +.
 * About the current fields: is already produced by the concatenation of   and   before storage. So if I understand this correctly, the new field mappings from the Person JSONs are:
 * ← (grep from )
 * ← (extract bitmaskss from )
 * Anything that migrates the wiki database towards the underlying data model should be okay. --HertzDevil (talk) 21:14, 25 May 2020 (UTC)
 * ← (extract bitmaskss from )
 * Anything that migrates the wiki database towards the underlying data model should be okay. --HertzDevil (talk) 21:14, 25 May 2020 (UTC)


 * It might be possible to sort items inside Template:RewardText according to their internal values. --HertzDevil (talk) 11:46, 23 August 2019 (UTC)
 * Rename to something like Scenarios, and then create a new table in place of Maps to store per-tab information.
 * Map availability should also be defined per difficulty, to properly handle cases like Narcian: Wyvern General (map) (Infernal and Abyssal had separate start times, so the map cannot be assumed to give the rewards at these difficulties since the beginning).


 * Add team counts to Template:Battle Infobox.
 * Convert Rival Domains maps so that they feed the entire tabber to Template:Battle Infobox's mapImage parameter, instead of constructing the tabber from the V2 / V3 parameters.
 * Modify Template:HeroGrid such that the new heroes row automatically displays new Grand Hero Battle units, while their events are active.
 * Create Template:HeroGrid GrandHero, similar to the existing Template:HeroGrid TempestHero and Template:HeroGrid LegendaryMythicHero.
 * Phase out usage of  and   classes throughout the wiki.

Larger projects
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.

Skill note templates overhaul
I am going to overhaul the skill note system to be more well-defined and flexible, and I've noticed errors in some of the templates and their placements that seem to stem from misunderstanding of game mechanics (such as placing the bonuses template on combat boost skills), so I will fix those as I go along as well.

Some examples:
 * During combat: One or more effects apply only during combat.
 * Support actions, such as healing or using, are not considered as combat.
 * Effects that apply during combat, such as increased stats, are not considered for skills that apply outside combat (e.g..

Here are the current specifications for the new system. The completed specification will later be available at Project:Note templates.
 * Every top level entry has a simple bolded header denoting a name for the effect/timing/condition/etc.. Other than the boldness, no special formatting or icons are allowed in the header.
 * Names of effects or conditions are not allowed to be another skill's name, since skills consist of both effects and conditions.
 * Usage of 'this skill/weapon/passive' is disallowed, as effects may come from more than just skills, e.g. GC Area Effects or Aether Structures, and these templates may be used on those pages.
 * Usage of is disallowed, as a skill's name may differ from the page name. There is also the possibility the templates may be used on pages that cover a broader subject than just the skill at the point in the page the template is describing.
 * When using SkillText, the level must always be specified. This is because relying on the max rank can be a problem if the max rank drastically changes the skill. Take the hypothetical scenario where you say  before Steady Stance 4 was released to illustrate the extra def stats stack, but then Steady Stance 4 is released and now the text is misleading.
 * Use of is limited to only where grouping of skills is important and neccessary. Otherwise, use SkillText.
 * Notes are allowed to refer to other notes. Example: {{#tag:pre| [...]

Pagination
A few pages on this wiki have grown excessively long. These pages are difficult to navigate, take a long time to regenerate, and are restricted in their complexity due to include size limits. This can be alleviated by splitting the contents across multiple pages. --HertzDevil (talk) 14:25, 24 August 2019 (UTC)

Aether Raids

 * Create pages for each season, similar to the Coliseum seasons. Define seasons on those pages instead of List of Aether Raids bonuses.
 * Similarly modify List of Aether Raids bonuses, based on List of Arena bonus Heroes.

Quests and Missions archive

 * Quests and Missions archive is now fully paginated. Adjust links to quests on that page so that they point to the monthly archive pages where the quests are originally defined. Same for links to yearly archives (2017, 2018).
 * Use QuestPage with those links too so that they can be handled by Cargo in the future (see ).
 * Also create archive pages for yearly quests (quests which last for an entire year): 2017, 2018, 2019.
 * Create Template:Quests and Missions Navbar for navigation on mobile view.

Other pages

 * Item distribution transcludes all distribution tables from all years. Consider splitting that page by year.
 * Split Summoning Focus archive by year or by month.

Internationalization
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

 * Finish and/or improve game pages, e.g..
 * Find a way to transclude character trivia on Hero pages. Endilyn (talk) 22:17, 22 September 2018 (UTC)

Interactive event calendar

 * 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.
 * As compound query doesn't work, it is possible to do create a calendar using a simple query. However, this query would called as base on which it is possible to join others table, which make it very huge and take a lot of time and ressources to generate. Moreover, some adjustement are needed to get the StartTime of each event as well as color or name wanted. An exemple with specials and events maps is here. There is still a problem, it seems previous revival of a maps doesn't appeared. Pival13 (talk) 19:24, 12 September 2019 (UTC)
 * That's a brilliant idea. I think it's good enough and you should put it in Event calendar while we are waiting for the next Cargo version. You should also create Special Maps calendar (and add it to Special charts, too). And what exactly is missing in your calendar? I don't see any problem with it, as the old LHBs still appeared correctly. RainThunder0 (talk) 11:59, 16 September 2019 (UTC)
 * I've completed it with focuses, story, paralogue, TD, HO, CC, BG and SA. Ideas about colors are welcome. About the problem, it is due to the limit. When I don't specify it, I have everything until August 7, 2019, and with a limit of 1000, until November 2018. There is also a problem with views. It only loads informations from the current, previous and next time interval. By exemple, as of September 16, 2019, I can't see A Splendid Soiree and Peforming Arts on week view if I don't switch to month view (which is truly ununderstandable). Pival13 (talk) 20:04, 16 September 2019 (UTC)
 * New Cargo version is up. I commented out the summoning events because there are too many of them. --HertzDevil (talk) 01:26, 25 September 2019 (UTC)


 * 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.
 * Created . Start and end times are determined by the first and last rounds respectively. --HertzDevil (talk) 07:23, 27 August 2019 (UTC)
 * All special maps (GHBs, BHBs, LHBs, MHBs) also need a Cargo table that stores their availability dates.

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:
 * For example, for Tap Battle (not in calendar format): [removed]
 * 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  and   should be renamed to   and , 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, and the original in  ), 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  .) --HertzDevil (talk) 17:06, 24 July 2019 (UTC)
 * Done. Might need a separate WikiName to distinguish reruns in the future though; I suggest, e.g.  ,  , and.
 * I also replaced 's definition for a similar reason, but that one doesn't need WikiNames for the moment. --HertzDevil (talk) 14:02, 23 August 2019 (UTC)
 * All maps now have date information. See for an example of retrieving currently active non-permanent maps: --HertzDevil (talk) 11:30, 21 September 2019 (UTC)
 * Template: Current Events can now work with the below query for all kind of Hero Battle:We must take care of Tempest Trials maps which are also presents on and  tables. There is currently only two banner images with a bad name: File:Banner Grand Hero Robin F.png and File:Banner Grand Hero Kana M.png as their gender is present on it. Pival13 (talk) 10:14, 8 September 2019 (UTC)
 * This query also work for Rival Domains and Relay Defense maps, but I would recommend to keep . For other events map (Daily (Aug 2019) (Event) or Nifl and Múspell (Event)), a banner image is needed as well as a MapGroup . Currently, I've supposed the banner image can be give as 5th arg on Template:Current Events/format and use File:Banner Event.png by default. Pival13 (talk) 11:52, 8 September 2019 (UTC)
 * For Rival Domains and Relay Defense, I think we should make a new query at the end of the table to keep the in-game display, otherwise they will appear above the events which have begun the previous week. Pival13 (talk) 14:14, 8 September 2019 (UTC)
 * There is no need to create more redirect for hero battles banner as now use the .webp file directly. Pival13 (talk) 06:52, 21 September 2019 (UTC)
 * Template:Current Events has been ported to Lua, any map that uses Template:MapDates should automatically appear there. As an additional benefit, events are now properly sorted by time remaining across event types. --HertzDevil (talk) 04:39, 22 September 2019 (UTC)
 * There is no need to create more redirect for hero battles banner as now use the .webp file directly. Pival13 (talk) 06:52, 21 September 2019 (UTC)
 * Template:Current Events has been ported to Lua, any map that uses Template:MapDates should automatically appear there. As an additional benefit, events are now properly sorted by time remaining across event types. --HertzDevil (talk) 04:39, 22 September 2019 (UTC)

Reward definitions
--HertzDevil (talk) 09:55, 22 August 2019 (UTC)
 * For rewards available in a single game mode, create new tables as necessary, based on and . See Template:RewardDefinition for details.
 * When storing mutually exclusive rewards, if one of the rewards is strictly better than all other rewards (normally the top-score or top-rank reward), then it is safe to store only that reward into the database.
 * For rewards of a single kind available in all game modes, the closest analogue at the moment is ; think about how it can be generalized to all events, e.g. by inventing a WikiName that is unique across every possible source of rewards.
 * Proof of concept: Sacred Coin distribution 2018 now uses to generate the rows for Tempest Trials. --HertzDevil (talk) 10:57, 23 August 2019 (UTC)
 * Reruns are now supported, this requires corresponding  fields on both event and reward tables. Put   in Module:ItemDistribution/data to enable it. --HertzDevil (talk) 20:46, 23 May 2020 (UTC)

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

Recurring maintenance tasks
Some of 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:
 * A list of news pages needing transcriptions is located at: Category:News pages needing transcriptions
 * This category is currently: 
 * List of images needed or needing newer versions located at at Category:Images needing improvement
 * This category is currently: 

Monthly additions

 * Seasons
 * Compile Combat Manuals
 * Use Heroic Grails
 * Structure / Mechanism updates
 * Accessory Shop
 * Concert Hall
 * List of version updates

Item distribution

 * Orb distribution (updated July 31, 2020)
 * Refining Stone distribution (updated December 3, 2019)
 * Sacred Coin distribution (updated December 3, 2019)
 * Blessing distribution (updated December 3, 2019)
 * Heroic Grail distribution (updated Dec 31, 2018)
 * Aether Stone distribution (not created)
 * Dragonflower distribution (updated ???)
 * Hero Feather distribtion (not created)
 * Midgard Gem distribution (not created)
 * Divine Codes distribution (not created)

Twitter-related

 * Calendar Wallpapers (updated October, 2019) (updates once or twice monthly)
 * Fire Emblem Heroes: Heroes' Everyday Lives (updated October, 2019) (updates weekly)

List of pages with incomplete enemy data

 * Category:Pages with incomplete unit data

Missing story text
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.

Missing story navigation
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.