FFXIV Wiki:Status effect revamp

Project description: Rework how status effects and their icons are presented on the wiki.
Members: Gurgum (talk)
Status: Backlog
Last updated: 13 September
Discussion: Talk page, Discord

Overview

This project is taking up space in my mind as "the status effect overhaul" but really is about several distinct topics:

The current {{status effect}} icon template has issues.
- Having to specify "buff" or "debuff" every time you use an icon is annoying.
- The current system, where we have a small hardcoded list of names and everything else has to be specified by filename, is not super intuitive for editors.
- I (erin) have been working on {{game icon}} for a bit now, and it works for basically everything except status effects; it would be nice if it worked for status effects too.
We don't currently have status effect descriptions on the wiki.
- Is this even something we want to change? What use would it have?
The list of status effects on Status effects should be more comprehensive, and ideally not be manually maintained.

Erin Umbreon (she/it • talk) 18:19, 19 February 2026 (UTC)

🗹 Decide on the overall strategy for status effect data going forward. - The plan is to start making pages for the statuses. {{Status effect infobox}} has been created, and patch 7.56 status pages have been created. Gurgum (talk) 12:16, 12 September 2026 (UTC)

- Discussion - no consensus yet. Please take a look and contribute your opinion, and add yourself to the member list of this project if you want.
☐ List out what needs to happen next based on that decision.

☐ Create missing status pages. Subtasks:
- ☐ Status effects may be applied by enemy actions, which we don't create pages for. Example: "Tender Anaphylaxis", with an action by the same name. We should figure out what to do with enemy actions so that we don't end up with orphaned status pages.
- ☐ Figure out what we want to do about the many, many status pages that have the same name as the related action, such as "Battle Voice". Those statuses and actions would all need to be disambiguated. Is it still worth creating separate pages for the statuses? Should we consider setting the status as a subobject on the action page?

Many status effects have multiple versions, including versions with different icons, dispellability, max stacks, etc. (Example: Stun) For the moment, I'm keeping things simple by creating a single status page with the earliest version's icon & details. I'm not planning to add more fine-grained details for now (like stack size), as those are the elements most likely to differ between versions. - Gurgum
Many status effects share a name and a nearly identical icon with the action that applies them (i.e. Battle Voice). The action describes the status, so we're not gaining much by creating those pages & icons. For now, status pages with the same name as action will not be created automatically.
GT's patch # for statuses starts at 4.56, so we can't trust them for patch numbers earlier than that. TC seems to have okay patch #'s.
Many status effects are only used to enforce certain mechanics for enemy encounters, or are only used to denote an enemy's current state, or represent obsolete/retired actions. The Fandom version of the Status Effects pages has approximately 2,400 status effects listed (2,220). Ideally, the scope of the project should be determined - are the three categories listed useful to readers? Alyko (talk) 15:21, 12 September 2026 (UTC)