Status List Release — List of all search keywords

Hello everyone,

Since this is a public post, I would like to take a few line to talk about the project and why it had to seemed to be at a stop for a few months. You can skip to the next section if it does not interest you.

What's going on?

When I started DissidiaDB's next version, last year, I did not clearly have an idea of what I wanted it to be, aside from it being as extensive and complete as opposed to the original website. 

DissidiaDB had started in 2017 when there was nothing to use for DFFOO information aside from Altema, and it was originally geared to only provide translated text for the English community playing the Japanese version. When GL was announced, literally 1 month after DissidiaDB launched officially, I was surprised, happy, and a bit worried. The project was not originally designed to be for two different versions of the game, and it has showed its weaknesses throughout 2018, despite my efforts to keep it as useful as I could, regardless of its limitations. 

From 2018 until early 2019, the most popular page was the Event Schedule, as many of you might remember. Still, the project was pulling very good numbers in terms of visits and I was amazed that my little project could grow so much. But I always remained dissatisfied by its scope. In 2019, I tried to remedy that issue by introducing some deep and not so obvious changes to provide better information about characters and enemies, but again, it ended up having little success, both in terms of motivating me to keep updating v1 and to satisfy the community.

To grow the project and attain my goals, I had to sacrifice DissidiaDB's initial version to work on a new version built almost from scratch. That is dissidia.dev, a temporary location for what I want DissidiaDB to be. I worked on this new project in 2020 but I was still updating v1 at the same time, making it extremely hard to progress efficiently. In late 2020, I made the decision to stop updating v1 and solely focus on the new project. This allowed much of my free time to be allocated to development of new feature and revamps of my DFFOO data processing tools. 

Unfortunately, I had to take a break from the project and focus on my life for a few months from early 2021 to mid-2021. I managed to get back to active v2 development starting early August, and I'm sure plenty of DB users have noticed the resurgence of timely updates. In that span of time, you've had to rely on other resources and there is nothing wrong with that. DissidiaDB was made because there was nothing for the non-Japanese community. Look at today's DFFOO community, there are so many active projects focused on providing information about the game. I'm very proud of this and I'm glad that I no longer have to feel sad when I can't update the project quickly for everyone :P.

The project has become a part of my life, so even if the scene is filled with DFFOO projects, there is no way I would give it up. I still have so many ideas to grow this experience and even if I cannot develop everything on my own, I want to see how far I can get before life forces me to move on. So, this is all about me and my situation.

Status List Release Notes

With the upcoming release of DissidiaDB v2's Status List, I would like to share with you the full extent of the search feature of this new page.

You can type any of these keywords in the search bar for more accurate results.

⚠️ Different keywords must be separated with a comma ","

⚠️ Make sure to use the filters before or after searching to further tweak your results

Alphabetical keywords

• Part of a character's name (English or Japanese)
• Part of a status effect's name (English or Japanese)
• Skill slot (BRV, HP, S1, S2, AA, EX, LD, BT)
• Status type "type:<Type>" (types are buff, debuff, sp, aa, ca, bt, btplus)
• Status target (self, target, enemies, allies, party, caller)
• Frame type (generic, silver, gold, framed for both silver & gold)
• "qs" or "ws" for quest start or wave start (qs includes ws)
• "ext" for extendable status effects

Numerical keywords

❓ Keywords tied to IDs will be made easier to use in the future.

• "<Status_ID>" of a given status effect: displays all status effects sharing the same ID (e.g. "1" displays all Paralyze debuffs)
• "eff:<Effect_ID>": displays all status effects sharing the same effect (e.g. "eff:22" displays all debuff evasion status effects)
• "turn:<Number>": displays all status effects with the desired duration
• "w:<World_ID>": displays all status effects from a particular series (e.g. "w:1" for FF1, this will be changed to an Alphabetical keyword in a future update)
• Any of the Status targets listed above + ":<Effect_ID>" (e.g. "target:1" for ATK effect applied to a targeted unit)
• "pa:<Effect_ID>" or "ea:<Effect ID>" for aura effects (pa = party aura, ea = enemy aura)

Special characters

• Prefixing any of the above keywords with a "+" (plus symbol) adds the results of that keyword to the list.
• Prefixing with a "-" (minus symbol) removes the results of that keyword from the list.

Examples

• "rem,+machina" displays all status effects belonging to either character.
• "atk up, -framed" displays all atk up status effects except framed ones.

Known issues

As with any newly developed product, there will be bugs or issues that I couldn't catch in time. But there is a range of issues that I'm aware of and will fix in due time.

• Maria's Explode, Deuce's Crescendo statuses are empty (their effects are stored differently in the game)
• Totals displayed by the mini party viewer when Ramza is in the party do not take into account the party's total buffs. The maximum BT effect values are displayed.
• Totals displayed by the mini party viewer when Paine is in the party do not take into account her position in the party. Both Throttles' effect values are displayed at their maximum value.
• Certain characters are missing certain sources for their status effects.
• Alphinaud is missing some of his Carbuncle-based status effects.
• Status effects granted from passive abilities are missing (e.g. Cloud's special effect)
• Hidden status effects are not displayed in the mini party viewer but their effects will still be displayed in the totals, so you might end up wondering where a certain effect comes from. That usually means it is a hidden effect. A future update will display them appropriately.
• The search feature's screen overlay (blur) might not work if you click too fast. This will be addressed in a future update.

Closing words

I hope that this somewhat extensive search feature can help you make better use of the Status List until its array of filters is increased and its performance enhanced. If you run into any bug, please join the Discord server to post feedback or send me a report via Twitter or reddit.

With the Status List released, I will switch gears and resume work on other parts of v2 that must be completed to provide the best character section that DissidiaDB can offer. All existing pages will also continue to grow along with the new pages, as I'm sure a few are severely lagging behind the recent UI changes. Feel free to suggest anything that you think would be useful!

Thank you for your support 💖
Rem