Anonymous

Site News
Warning: This wiki contains spoilers. Read at your own risk!

Social media: If you would like, please join our Discord server, and/or follow us on X (Twitter) or Tumblr!

User:Thecornerman: Difference between revisions

From Fire Emblem Wiki, your source on Fire Emblem information. By fans, for fans.
m
no edit summary
mNo edit summary
Line 38: Line 38:


*Add stats and behavior notes for chapter pages that lack it; [[User:Xamad#Wiki projects|Xamad has a list]] of unfinished stuff.
*Add stats and behavior notes for chapter pages that lack it; [[User:Xamad#Wiki projects|Xamad has a list]] of unfinished stuff.
**Need more extensive notes for ''Mystery of the Emblem''
**Need more extensive notes for ''Mystery of the Emblem'' Book II
***Need precise notes on [[Jeorge]] and [[Astram]] as enemies for ''Mystery of the Emblem'' Book II, and what happens in later chapters when they are killed.
***Need precise notes on [[Jeorge]] and [[Astram]] as enemies for ''Mystery of the Emblem'' Book II, and what happens in later chapters when they are killed.
*Work on {{t|tab}} to maybe make it more efficient
*Work on {{t|tab}} to maybe make it more efficient
**The main source of extra template include size is that all content passes through two templates, increasing the effect of any templates in the content fields on the include size by roughly triple. The easiest way, I think, to reduce this would be to split it into component templates: I think a header, middle, and footer template, and tab and content templates; the latter two technically exist in {{t|Tab/Tab}} and {{t|Tab/Content}}, but new templates would need to be made or the existing ones modified to be more efficient outside of {{tab}}. Having a separate content template that is not nested in another template would reduce the include size, as any templates in content would only count for roughly twice their size, rather than thrice.
**The main source of extra template include size is that all content passes through two templates, increasing the effect of any templates in the content fields on the include size by roughly triple. The easiest way, I think, to reduce this would be to split it into component templates: I think a header, middle, and footer template, and tab and content templates; the latter two technically exist in {{t|Tab/Tab}} and {{t|Tab/Content}}, but new templates would need to be made or the existing ones modified to be more efficient outside of {{tab}}. Having a separate content template that is not nested in another template would reduce the include size, as any templates in content would only count for roughly twice their size, rather than thrice.
***Additionally, separate tab and content templates would allow more than 15 tabs to exist at once, though anything already approaching that is probably excessive.
***Additionally, separate tab and content templates would allow more than 15 tabs to exist at once, though anything already approaching that is probably excessive.
*Add help text to all ''Heroes'' skills
*Add help text to all ''Heroes'' skills and characters
*Fill out etymology and help text sections of ''Heroes'' items
*Fill out etymology and help text sections of ''Heroes'' items
*Finish ''Awakening'', ''Fates'', and ''Three Houses'' character epithets for ''Heroes'' name chart
*Finish ''Awakening'', ''Fates'', and ''Three Houses'' character epithets for ''Heroes'' name chart