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 (deadlines)[edit source]

This list is for tasks that have a higher priority because they involved limited events or other data that can only be gathered within a short timeframe.

Events[edit source]

Summoning[edit source]

Quests[edit source]

See /Pending Quests.

Other[edit source]

Current list (no deadline)[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 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.

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)
  • Document Aether Raids changes in 3.6.0 and 3.7.0 (defense rewards)
  • Allegiance Battles maps need different initial spots and reinfocements spot for each enemy color. Maybe a colorful version and/or with an icon (red diamond, blue square, green pentagon and grey circle). Other ideas are welcome. Then create a template to call them.

New content[edit source]

Tasks about newly added features or data in updates.

Missing information[edit source]

Missing properties about the game data.

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)
  • Place Template:Lua wrapper on documentations for templates that wrap Lua functions.
  • Update Fire Emblem Heroes Wiki:Tutorials/Cargo so that it doesn't use a deprecated template as an example.
  • Add mandatory and unique to descriptions for all WikiName fields.

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.
  • Improvements to Template:Weapon Infobox:
  • Modify Template:Structure Infobox so that it stores one row per level for each structure, rather than one row for all levels
  • Update Module:FocusRates
    • Not very flexible, currently required to received a 4★ Focus rate of "0.00%" manually for every focus. 5★, 5★ Focus, and 4★ are also all required fields even if they are not part of the summoning focus.
    • Does not support 1★, 2, 3★, and focus focus rarities of those numbers either.
    • Currently converts strings like "10.00%" by removing the last character from the string then converting to number. Instead, it is better to replace "%" with "" so that number-only inputs such as "10.00" or "10" are accepted.
  • In the Stages section of Tap Battle pages, figure out a layout that would display an embedded player for boss themes like what's currently available for stage BGM's.
  • The alphabetical Hero roster in Template:HeroGrid is not particularly helpful for locating Heroes. Idea to solve this problem: Make it into a table organized by color and movement type, and within the same color divide by physical or magical damage. Find other properties to use to further subdivide them so that they are easier to locate. Endilyn (talk) 03:57, 13 February 2019 (UTC)
  • Find a way to add more BGM on {{Battle Infobox}}: 3 are needed for the Grounds of Wind: Wind 9.
  • Audit all uses of {{MF}}, Util.mf, and MF.main and identify cases that require MediaWiki page title canonicalization or decoding of HTML entities. --HertzDevil (talk) 16:56, 30 June 2019 (UTC)
    • I think it is okay to leave MF with using #titleparts, because it is only used for file names which already end up as page titles. Endilyn (talk) 20:45, 2 July 2019 (UTC)
  • Replace Util.strsplit with mw.text.split. --HertzDevil (talk) 18:47, 25 June 2019 (UTC)
  • Replace <font> tags in the following pages with CSS font-size properties: (either in px, or one of xx-small / x-small / small / medium / large / x-large / xx-large)

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.

More Hero properties[edit source]

  • Derive the rarity wikitext from these 3 fields and remove Heroes.Rarity eventually
  • Store in some cargo table: series, tome_class, legendary, special_hero, permanent_hero, refresher from hero_definition --Ale1991 (talk) 00:07, 13 November 2018 (UTC)
    • Most of the boolean values here are stored in Heroes.Properties with "existing in the field" = true and "not listed in the properties" = false. Endilyn (talk)
  • Correct the meaning of Heroes.SummonRarities.
    • It should be used for the general rarities of Heroes.
      • Heroes that are part of the regular summoning pool should have this field filled in with their regular summoning pool rarities.
        • Appearances as 5★ Focus should not affect this field.
          • Heroes that are 3★-4★ but then were featured as a 5★ Focus on a Summoning Focus should remain with this field as 3,4.
          • Heroes that have appeared as only 5★ Focus should have this field blank.
    • Remove all cargo queries that rely on Special Heroes etc. having a value of 5, and fix them so that they query for the special etc. property instead.
    • Blank summoning rarities for non summoning pool Heroes.

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)

Overhaul map pages[edit source]

  • Template:UnitData Will be replaced by Module:UnitData, see Template talk:UnitData and Module:UnitData/test for initial plans. Post suggestions, issues, changes, etc. to that plan here.
  • Internal slot orders and definitions for AI settings have been found, and mockups for wiki presentation are available at User:HertzDevil/sandbox/AI settings. For maps that use different settings across difficulties, decide whether to merge them manually with the Notes column, or present individual tables with a tabber. (we have Lua so we shouldn't need to worry about this yet)
  • Input exact levels for Lv. 40+ maps and units.
  • Come up with a design idea that displays Chain Challenge / Squad Assault stats in a more concise way, possibly deriving them directly in Template:UnitData.
    • A template shows:
Derived map
The stats of these enemies are derived from another map.
Base map (page)
New rarity 5
HP Multiplier 1.2
then it executes UnitData with altered stats. I haven't figured out a system for it being able to pull the base map stats yet. Endilyn (talk) 19:43, 22 March 2019 (UTC)
Template:UnitData already calculates the base stats from the skills it pulls from the database, it should be possible to store the base stats instead of the calculated stats in MapEnemies (I don't think anything on the wiki queries those stats thus far). We also probably need a column for the canonical skill upgrades, the storing part is easy but the retrieval would be quite messy if the Lua-based replacement isn't ready. --HertzDevil (talk) 11:17, 28 May 2019 (UTC)
I think it's a good idea to store the base stats instead of final stats. Ideally the page input would be the base stats as well instead of the calculated stats, so that if a weapon's might is ever altered for instance the map page updates properly when the weapon page is updated, instead of having to update all map pages the weapon appears in. When the new enemy module is ready, is it possible for you to run a bot that can uncalculate stats while converting the old template to the new one? Endilyn (talk) 07:33, 29 May 2019 (UTC)
Same for cooldown counts I assume, i.e. using cd = (non-default charge) instead of cdbonus = (charge reduced), especially considering cooldown counts did change once in 2.0.0. --HertzDevil (talk) 02:17, 30 May 2019 (UTC)
Yes, it is probably better to do a cd parameter instead of cdbonus. In Cargo, we can just store the default counts to be -1 like in the map definition files. Endilyn (talk) 21:54, 4 June 2019 (UTC)
Canonical skill upgrades are in, but we still need two extra fields before we can implement skill promotion, skill_definition::promotion_rarity and skill_definition::promotion_tier (see User:HertzDevil/Reverse-engineering notes#Enemy stats for derived maps). I can't think of a clean way to add them here other adding up to 6 new template parameters in the various skill templates and Template:SkillDefinition. --HertzDevil (talk) 03:00, 7 June 2019 (UTC)
I also cannot think of a cleaner way, that is probably the best possible method. As a fallback, if the promotion data is missing for a skill on the wiki, it could display File:Passive No Image.png and GroupName for passives, and maybe just "Unknown" for other skills. Endilyn (talk) 20:45, 2 July 2019 (UTC)
  • We can in theory dump the remaining fields from map unit definitions into the module; then the module (or whatever top-level module that eventually replaces Module:UnitData) will generate not only the unit lists but related contents like the AI settings table and reinforcement map displays as well. Some preliminary thoughts:
    • The ally property indicates the unit is an ally unit.
    • The use_ally_stats property indicates the enemy unit uses the player version to calculate stats in derived maps.
    • Positions will continue to use the same format as Template:MapLayout parameters (a1, e3 etc.) since they are concise enough for manual input. They will be stored into the database.
    • AI settings will be specified using a nested table like ai={start=1;group=1;delay=2;break_walls=yes;tether=no}. Since this can be tedious when done manually, there needs a way to specify default settings for all units. The output format is based on Template:EnemyAITable, but the settings won't be stored because no other templates or modules need them (as long as this table is emitted next to the map units).
    • Reinforcement settings will be similarly specified using something like spawn={turn=2;count=2;target=Nino: Pious Mage;remain=0} or {...;kills=1}. At the minimum the database should know whether a unit is an initial unit or a reinforcement. Derived maps will most likely need some form of knowledge about the exact reinforcement settings of every unit.
    • Template:MapLayout has been migrated to Lua, so it can be invoked through require('Module:MapLayout')._map. For reinforcements units are grouped according to their spawn settings, just like what has always been done. The initial map display, which sits in the infobox, shall query MapEnemies and fill out the initial units automatically; the player positions will still have to be manually specified.
We will also need to store the map difficulty into MapEnemies as well, they are needed for querying the proper map definitions (I imagine this is difficult for the current template-based approach). One last point: derived units shouldn't be stored into the database unless there is a good reason to query them directly. --HertzDevil (talk) 10:17, 16 June 2019 (UTC)

An idea is that the first unit has globalai={...} specified, and the AI settings are filled in for every unit afterwards except for units that have their own ai={} parameter.

TabName is being stored so that a specfic instance of a map can be queried, even if two different instances of a map have the same difficulty. (Example: Tempest Trials have more than one Lunatic mode)

Storing derived units may be useful for statistical analysis (ex: what is the average spd of PvE units?), and they could be stored with a derived property to prevent accidental querying, but if it's too much trouble then they should just be dropped.

Endilyn (talk) 20:45, 2 July 2019 (UTC)
I can't think of a situation where we need such statistical queries on derived enemy stats (even normal enemy stats).
TabName alone should suffice; strictly speaking, the difficulty is a property of a scenario rather than a map. The other alternative is to store the full map ID (e.g. S3011A, L0001E) and base queries around that rather than the tab names, since they are more stable. --HertzDevil (talk) 09:21, 4 July 2019 (UTC)
Currently Module:UnitData/test/doc/Bows: Special Training is able to group units into their reinforcement types and display the corresponding reinforcement maps. The entire map image, which is just a regular {{MapLayout}} with starting spots and units stripped, is passed to the entry point of the module, and then another {{MapLayout}} superimposes the units on top of it directly, this time inside the module. It is not perfect, but already reduces a lot of manual input and still remains faster than the real deal. At the moment I cannot think of a better solution that does not involve storing terrain information into the Cargo database. --HertzDevil (talk) 21:39, 15 July 2019 (UTC)

Character / game pages[edit source]

Renaming skill pages with non-matching in-game names[edit source]

Change incorrect skill names to the true in-game values with the |name= parameter, and where applicable, by moving the page. For example, Firesweep Sword should be Firesweep S.

  • For skills with / in the title, remove the / entirely, and replace with a space. It appears that even if the page "Atk" is not created and breadcrumb links would not appear on a page titled Atk/Spd 2, {{SUBPAGENAME}} would output "Spd 2" instead of "Atk/Spd 2", showing that it is considered a subpage, unlike its behavior in namespaces with subpages disabled, where it would output "Atk/Spd 2".
  • All instances on the wiki where the page name of the skill was used must be updated with the new page name.
  • For {{OtherLanguages}}, always use in-game texts on skill pages, and do not expand abbreviations or capitalize words unless the in-game texts do. Add |english= if the in-game text does not match the page name.
  • Batch-update build pages which use renamed weapons / Assists / Specials. (Passives already used in-game names before the page moves.)
  • Extend this to other pages that use slashes? (e.g. Atk/Def Bond's Power)

More complete Tempest Trials data[edit source]

  • Create a cargo table for Tempest Trials that contains TT event info including start and end dates.
  • Store reward informations for each TT on its page. Currently only done on Chaos Named, and no other TT has reward information.

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

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

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)

Internal IDs[edit source]

As above, add internal IDs to the following tables:

  • PID_* or EID_* into Heroes (this is done except for Laevatein, Laegjarn, Helbindi, Loki, and Surtr)
  • SID_* into Skills (WikiName can stay unless we are sure we can obtain the SIDs without additional Cargo queries (probably not))

Merge Hero and enemy tables[edit source]

Combine or move these tables:

  • Heroes + EnemiesUnits: Suitable fields have been added to Enemies to make it structurally equal to Heroes. A row represents an enemy unit if its Properties HOLDS 'enemy'. (Can we fill in something for Enemies.GrowthMod?) Something like insource:/cargo_query\s*:\s*tables\s*=\s*[^|]*Enemies/ can be used to search for non-module pages querying the enemies table.
  • HeroStats + EnemyStatsUnitStats: We will need to make sure a single join between the units table and stats table can distinguish Hero and enemy stats, required for Module:UnitData (the PID_* and EID_* tags should work).
  • MapEnemiesMapUnits: This will be handled by Module:UnitData in the future.
  • HeroSkillsUnitSkills: This table already stores enemy skills and we haven't run into any issues with that so far, but joins with the units table will most likely need to check whether a unit is an enemy.

The main benefit is to avoid writing code that queries both the Heroes table and the enemies table, simplifying code and speeding up response times. Editor notes:

  • Because Face_FC.png doesn't exist for generic enemies, we have to decide whether to use Mini Unit Idle.png or import the BtlFace_BU.png files for templates like {{UnitIcon}} (e.g. {{UnitIcon|Axe Cavalier}} → Axe Cavalier Mini Unit Idle.png Axe Cavalier). Either way can be done inside Cargo without separate queries for Heroes, generic enemies, and boss enemies, e.g. Gaius Candy Stealer Face FC.png  Gaius Thief Exposed Face FC.png  Garon King of Nohr Face FC.png  Genny Dressed with Care Face FC.png  Genny Endearing Ally Face FC.png  Gerome Masked Rider Face FC.png  Gharnef Dark Pontifex Face FC.png  Gordin Altean Archer Face FC.png  Gray Wry Comrade Face FC.png  Green Bow Mini Unit Idle.png  Green Cavalier Mini Unit Idle.png  Green Fafnir Mini Unit Idle.png  Green Flier Mini Unit Idle.png  Green Mage Mini Unit Idle.png  Green Manakete Mini Unit Idle.png  Green Thief Mini Unit Idle.png  Greil Heroic Exemplar Face FC.png  Gunnthra Beaming Smile Face FC.png  Gunnthra Voice of Dreams Face FC.png  Gunnthra Years First Dream Face FC.png  Gunter Inveterate Soldier Face FC.png  Gustav Exsanguinator Face FC.png  Gwendolyn Adorable Knight Face FC.png
  • Replace CONCAT(Name,': ',Title) with IFNULL(CONCAT(Name,': ',Title),Name) if rows start disappearing because generic enemy units don't have titles.
  • Enemies is no longer queried.
  • Joins between Units and UnitStats are done using Units.TagID=UnitStats.TagID.

--HertzDevil (talk) 22:57, 1 July 2019 (UTC)

Arena score research[edit source]

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

Other reoccurring 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:

New content[edit source]

Remove {{NewContent}} from old content.


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 Rarity Slot Level HP Atk Spd Def Res Weapon Assist Special PassiveA PassiveB PassiveC Seal
Morgan & Morgan: Bound Hero Battle T0059 Morgan: Lass from Afar 5 40+ Blárserpent+ - Iceberg Mirror Stance 2 Guard 3 Atk Ploy 3 -
To Create the Future Past PC034 Sword Fighter 5 40 31 30 31 22 Slaying Edge+ - Luna - - Res Tactic 3 Drive Atk 2
Røkkr Sieges 2 Arden: Strong and Tough 3 0 10 0 12 10 14 10 Umbra Burst (Sword) - Umbra Calamity - - Drive Def 1 Røkkr
Røkkr Sieges 1 Eirika: Graceful Resolve 3 0 10 0 11 13 12 11 Umbra Burst (Sword) - Umbra Blast Atk/Spd Solo 1 - Odd Def Wave 2 Røkkr
Part 13: Daily (Aug 2017) V0076 Lance Flier 5 19 7 10 5 11 Iron Lance - - - - - -
Part 20: Daily (Feb 2018) V0180 Sword Fighter 5 21 8 8 9 5 Iron Sword - - - - - -
Part 3: Turn Limit V0033 Niles: Cruel to Be Kind 25 28 16 21 10 21 Steel Bow - Iceberg - Seal Atk 1 - -
Part 8: Daily (Aug 2017) V0071 Axe Knight 5 25 12 3 12 4 Iron Axe - - - - - -
The Brink of Chaos XX002 Ursula: Blue Crow 10 19 11 12 6 12 Blárwolf - - - Desperation 1 - -
Vs. Robin F: Reward Map V0238 Robin: Seaside Tactician 5 18 4 9 7 8 Deft Harpoon - - - - - -

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
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
Rival Domains: Event Map (31) Q0031 Rival Domains: Event Map
Rival Domains: Event Map (32) Q0032 Rival Domains: Event Map

More...

List of pages with incomplete languages[edit source]

A repository with all text files in all languages in the game as of 2018-11-05 is available here.

_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 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
Adult (Armored) Adult (Armored)
All-Piercing Arrows All-Piercing Arrows Arc pénétrant Flechas contundentes
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 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
A Trust Earned A Trust Earned Piena fiducia
Accessory Shop Accessory Shop アクセサリー屋
Adult (Armored) Adult (Armored)

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 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
A Trust Earned A Trust Earned Piena fiducia
Accessory Shop Accessory Shop アクセサリー屋
Adult (Armored) Adult (Armored)

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 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
Accessory Shop Accessory Shop アクセサリー屋
Adult (Armored) Adult (Armored)
All-Piercing Arrows All-Piercing Arrows Arc pénétrant Flechas contundentes

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 Promise of Joy A Promise of Joy Paraíso ilusorio Paradis Promis
A Season for Picnics (Focus) A Season for Picnics
Accessory Shop Accessory Shop アクセサリー屋
Adult (Armored) Adult (Armored)
All-Piercing Arrows All-Piercing Arrows Arc pénétrant Flechas contundentes
Alm: Saint-King (map) Alm: Saint-King (map)

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 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
Accessory Shop Accessory Shop アクセサリー屋
Adult (Armored) Adult (Armored)
Alm: Saint-King (map) Alm: Saint-King (map)
An Acquired Taste

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 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
A Trust Earned A Trust Earned Piena fiducia
Accessory Shop Accessory Shop アクセサリー屋
Adult (Armored) Adult (Armored)

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
???: Masked Knight/Misc ???: Masked Knight 謎の仮面騎士 ??? ???: Maskierter Ritter ???: El Enmascarado ???: El Enmascarado ???: Il Cav. Mascherato ???: Chevalier Masqué 神秘的蒙面騎士 ???
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
A Trust Earned A Trust Earned Piena fiducia
Accessory Shop Accessory Shop アクセサリー屋

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: