FFXIV Wiki:Desynth data automation

Project description: Display crowd-sourced desynth data from xivstats.com on item pages
Members: Erin Umbreon (talk), Gurgum (talk)
Status: In progress
Last updated: 8 July
Discussion: Talk page, Discord

xivstats.com collects lots of data about random results in XIV, including desynth data. The raw data lives in a JSON file in their Github repo and is hosted at https://gacha.infi.ovh/data/Desynthesis.json

Two tasks that can be handled independently:

1 Write a Lua module/template that can be used on item pages to render the raw data for a specific item in a nice format.
1 Write a long-running bot that will periodically upload the latest Desynthesis.json to the wiki so the data stays up-to-date.
- This is more complicated than it initially seemed because Desynthesis.json is a very large file and Mediawiki is not happy with it. I'm gonna have to break it up into multiple Module:Desynthesis/Results/XX000.json files on the wiki in order to make it all fit, so the update bot will have to know how to do that. Erin Umbreon (talk) 20:43, 11 February 2026 (UTC)
- 1 The script for doing this now exists! Just need to get it set up on my server. Erin Umbreon (talk) 21:20, 17 February 2026 (UTC)
- I cleaned this up further to use the same folder/filename structure as infi uses in the github repo - this simplifies the scripted updates quite a bit. Erin Umbreon (she/it • talk) 01:00, 25 February 2026 (UTC)

Now that those two tasks are done, we have the fun part: backfilling {{desynthesis results}} into all the old item pages.

Everything is basically done, just some cleanup left to do:

🗹 set Has desynthesis result via the module for each desynthesis result. Old pages set {{contains}}.
☐ Update {{contained in}} to display items that have the given item as a desynth result. (Gurgum)
☐ Clean up old desynth data source pages now that I've switched the subpage names to match infi's
🗹 Set bot up on my server
- Been done for a few weeks now. Erin Umbreon (she/it • talk) 17:24, 5 July 2026 (UTC)
☐ Backfill to other pages. In progress. The template has been added to pages that didn't have any desynth info at all. After we've added functionality to populate the table with manually added results (in case XIVStats doesn't have the data - see below), we can start (very carefully) replacing the old desynth sections, passing any user-added items to the module.

Erin Umbreon (she/it • talk) 01:00, 25 February 2026 (UTC)

Data reconciliation tasks

☐ Add functionality to the template to allow rendering manually reported results
- These need to be visually distinct from the data-backed results so it's obvious which results have been verified via the Tracky plugin and which haven't
☐ For crafted items, confirm whether all the ingredients will also be desynth results (eventually). If so, always include those in the table, even if XIVStats has no data. Discord conversation. Gurgum (talk) 15:08, 8 July 2026 (UTC)
☐ Render some sort of note/warning when table is generated from a small sample size (less than 100ish desynths)? (I'm thinking we can skip this - the table already shows the # of desynth attempts, so users can draw their own conclusions re. the reliability of the data. Gurgum (talk) 15:09, 8 July 2026 (UTC))
☒ Add parameters for rendering headers ("==Used for==" and "===Desynthesis===") only if there are results in the table, so we can backfill the table template onto all item pages from the datamining/page creation scripts
- Gurgum decided we don't need this and we'd rather keep the template minimal. This will be handled on the Python side instead. Erin Umbreon (she/it • talk) 03:35, 2 May 2026 (UTC)

Erin Umbreon (she/it • talk) 15:29, 31 March 2026 (UTC)