Dungeon Drip keeps track of what is in the Glamour Dresser and Armoire, and answers the same question at each point where something might be picked up.
On entering a dungeon or alliance raid it lists the gear that drops there and is not yet collected. Any duty can also be looked up without entering it. While a Need/Greed roll is open, a companion window beside it marks the pieces still missing. And at a vendor, a panel beside the shop lists the glamour gear it stocks, marked by where each piece is already held. Outside a duty it names the role to queue each roulette as.
Its answers also reach the game's own right-click menus, and the window has a second view for the collection as a whole — which outfit sets are closest to finished, how full the dresser is, and which carried pieces a box already has.
All of that draws as ordinary plugin windows by default, and can instead be drawn as the game's own — following the UI theme, scaling with the UI scale, and hiding with the rest of the interface. See Drawn as game windows.
Not yet in the official Dalamud plugin list. In the meantime it is available from a third-party repository.
In game, open /xlsettings → Experimental → Custom Plugin Repositories, add this URL
and press save:
https://raw.githubusercontent.com/Spibane/DungeonDrip/main/repo.json
Dungeon Drip then appears in /xlplugins under All Plugins, and updates arrive the same
way as any other plugin.
Dalamud offers only minimal support for third-party repositories and would rather the official list were used, so treat this as temporary — it goes away once the official submission lands.
loot sources collection
┌──────────────────────────────┐ ┌──────────────────────────────┐
│ Teamcraft every duty │ │ Glamour Dresser + outfits │
│ Console Games Wiki per duty │ │ Armoire │
│ with per-boss tables │ ├──────────────────────────────┤
│ drops seen in game live │ │ bags, armoury, saddlebags │
│ loot-overrides.json by hand │ │ retainers: bags, and worn │
│ │ │ separately - both opt-in │
└──────────────┬───────────────┘ └───────────────┬──────────────┘
│ merged, keyed by territory │ snapshot per character
└─────────────────┬────────────────────────┤
▼ │
missing = drops − owned │
│ │
┌───────────────┴───────────────┐ └────────────┐
▼ ▼ ▼
main window companion window beside panel beside vendor
(by slot, role or boss) the Need/Greed roll stock, panels beside
│ the dresser and the
▼ Armoire, and the
collection view game's own menus
(sets in progress, dresser
pressure, carried gear)
Everything on the right branches straight off the collection: those ask only "do I have this?", so they need no loot data and work at any shop, any board and any dresser — not just the ones that involve duty gear.
Sitting outside that pipeline entirely is a second answer about a piece: how it can be obtained when it is not a duty drop, read from the game's own recipe, shop, quest and achievement sheets. It joins none of the merging above — it is keyed by item rather than by territory, and it changes only when the game does — but it appears wherever a piece does. See Where gear comes from.
The Glamour Dresser needs opening now and then. The game wipes dresser data on every zone change and only loads the Armoire on demand, so nothing is readable from inside a dungeon. Dungeon Drip works from the last snapshot it managed to take, per character, and the window reports its age.
Retainers are read the same way and one at a time: their bags only load while that retainer is open, so each is snapshotted on a visit and answered from the cache afterwards. A retainer that has never been opened is simply not counted rather than counted as empty. Settings → Data lists each one with the age of its snapshot and can forget any of them — useful for a dismissed retainer, since nothing in the game ever comes back to say so.
A retainer is somewhere gear is held, not somewhere it is stored. Nothing outside the Glamour Dresser and the Armoire can be worn as a glamour, so a piece with a retainer is one that is owned and not put away — the same footing as one in the bags. Counting either is opt-in, and both live under one heading in Settings → General.
Gear the retainer is wearing is counted separately, and is off even when retainers are on. It is not in their bags, so a bare "one is owned" means seven pages searched for something that was never going to be there — and it is doing a job where it is, since a retainer's item level decides what their ventures bring back. Switch it on under the retainer setting and it is named for what it is: worn by one of your retainers, never in their bags.
Open a shop and a panel appears beside it, listing only stock that can be kept as a glamour. Materials, dyes and food are left out entirely, so an unmarked row in the shop never means "already collected".
| Marker | Colour | Meaning |
|---|---|---|
| x | red | Not collected |
| tick | grey | In the Glamour Dresser |
| layers | grey | In a stored outfit set that still has gaps |
| star | green | In a completed outfit set |
| archive box | grey | In the Armoire |
| briefcase | grey | Carried or equipped |
| figure | grey | In a retainer's bags |
| figure in a tie | grey | Worn by a retainer, not in their bags |
| ringed question mark | amber | Not in the dresser, and the Armoire that could have it has not been read lately |
| question mark | amber | No dresser data — nothing can honestly be said either way |
The marker carries the state; the name only says whether the thing is needed. Missing pieces are named in plain white and everything already held is greyed out, so the only two things that catch the eye are the red x and the green star.
A stale snapshot turns the red x amber, not the grey ticks. Dresser contents are near-monotonic: glamours are added far more often than they are removed, so an old snapshot's "owned" almost always still holds, while its "not owned" is exactly what goes out of date. Amber on an x means probably new, but worth checking.
The Armoire has its own age, and it is usually the older one. The dresser is re-read on any glamour operation; the Armoire only loads when it is opened at an inn. A piece the Armoire accepts, that the dresser does not have, gets the ringed question mark rather than the red x whenever that Armoire read is older than the staleness setting — including when it has never happened at all. It still counts as missing and still shows in the lists, because most of what the Armoire accepts is not in anybody's Armoire; the mark says the plugin cannot rule it out, not that it has.
Three buttons at the top flip the list filters without a trip to Settings — whether owned pieces are listed, whether the list is held to the current job, and whether weapons are included. They write the shared settings, so they change the duty list too, and each tooltip says so.
The panel lists whatever the vendor is currently showing: switching a category or tab re-reads it, scrolling does not. It opens at the shop window's height with the list scrolling inside so a long list cannot run off the screen, and its width fits the longest name. Drag it to any size and that size is remembered; a fourth button appears while a custom size is in use, to go back to matching the shop. It cannot be dragged elsewhere, so fold it to its title bar when it is in the way.
It reads the shop window's position and stock but never draws into it, so it cannot fight with
plugins that do. Covered: gil vendors and Calamity Salvagers, item-exchange counters, currency and
scrip exchanges, Grand Company quartermasters, free-item counters and the Firmament. Anything else
gets no panel — run /dungeondrip shop there and report the addon name it prints.
Open a board, pick a category, and a panel appears beside the browse list marking which of that gear is already held — the same markers as at a vendor, and the same amber-x rule.
Only the browse list gets a panel. The listings for a single item do not: by the time that window is open the piece has been chosen, so the question was needed one screen earlier, and every row there would be the same piece repeated once per seller.
Results arrive from the server in pages of twenty, so the panel fills in as the category loads. Scrolling does not re-read anything, and a text search lists the search's results rather than the category's underneath them.
This is where a stale snapshot matters most and where it costs the most, since a board is reached by travelling to one and zoning is exactly what wipes the dresser data. The amber x means probably new, but worth checking before the gil is spent.
Open a dresser and a panel appears beside it listing carried gear that is not stored yet — the mirror of every other panel, which ask whether the gear the game is showing is needed. This is the one surface where the answer can be acted on without going anywhere.
The marker column shows where the piece is rather than whether it is stored, since by construction it is not: a case for the bags, a box for the armoury chest, a figure for something worn and a horse for the saddlebag. A row is amber when something has to happen first — taking it off, or fetching it from the saddlebag. Settings → Panels → Glamour Dresser lists the markers. The header says how full the box is, because "which of these do I put in" only becomes a question when they will not all fit.
A toolbar button drops armoury-chest gear from the list, since that gear usually belongs to a gearset rather than being loose.
Rows read not stored rather than "this can be added". Some of the dresser's refusals are not readable from outside it, so a few pieces the game turns down will still appear.
The panel waits for the box's contents to arrive rather than the window: a list built against an unloaded dresser would claim every piece owned is unstored, at exactly the moment it would be acted on.
The same panel, beside the Armoire, listing held gear the Armoire has not got. The game's own Store an item screen cannot answer that: it lists what the Armoire accepts, which is a fact about the item rather than about the character, so a piece already deposited sits in that list looking exactly like one that is not — and the only way to find out is to pick it and be told no, one piece at a time. The header says how many of the pieces on the character the Armoire already has, which is the number that screen will not give.
The Store an item screen only. The Armoire's own window lists what is in there already, which is a question it answers by itself.
Markers, the amber rows and the two toolbar buttons work as they do at the dresser, and those two buttons are the same setting on both panels: gear a gearset is using is using it whichever box is being stood at.
There is no header about how full it is and no snapshot warning, and neither is an omission. The Armoire has no capacity — what it holds is decided by the game's own Cabinet sheet, so which pieces to put in is never a choice between them — and its contents are read live in front of the player, so the age of the dresser snapshot says nothing about this list.
Like the dresser panel, it waits for the Armoire's flags to have been read rather than for the window, and a row means "the Armoire has not got this" rather than "the Armoire will take it from here". Whether it reaches into the armoury chest is not something readable from outside it, so no row claims either way.
Outside a duty the window shows, per roulette, which role to queue as:
| Roulette | Queue as | New | Chance |
|---|---|---|---|
| Expert | Melee DPS (NIN VPR) | 12 | 35% |
| Level Cap Dungeons | Healer | 8 | 27% |
New counts uncollected pieces that role can roll Need on across the roulette; Chance is those as a share of everything it can roll on there, which is what the ranking uses. Roles are the grouping used everywhere else, melee split by gear type. Hovering gives every role.
Listed roulettes are Expert, Level Cap Dungeons, Alliance Raids, High-level Dungeons and Leveling — the ones whose gear is tracked. Membership and names come from the game's own sheets, so a renamed or re-pooled roulette follows the patch.
Odds are per rollable piece, not per run, and assume the pool is unlocked; only the character's level is readable. Roles with nothing levelled enough, and duties above that level, are left out.
Looking a duty up replaces the table; the toolbar's pin button lets go of it again, showing a die when that lands back here and a thumbtack when it lands on the duty currently being stood in.
The toolbar's first button swaps the window between duty loot and the collection as a whole. Three tabs, none of which involves a duty, and the window reopens on whichever was last used:
Sets in progress — outfit sets part way through, closest to done first. Expanding one lists what is missing and where each piece drops. A set with nothing collected from it is not "in progress", and neither is a finished one; that definition is what keeps the list a readable length.
Ready to buy — one group per currency in your Currency tab, listing the unowned gear it buys with what you can afford right now on top. The balance and an affordable count sit on the heading, so a currency worth spending is the one at the top of the section.
A currency is whatever is in that tab, and that is deliberate. The shops sheet prices gear in 2,919 different things, of which 2,530 buy exactly one piece — because most are not currencies at all but gear being traded up, one base piece for one augmented one. Reading the tab settles it with no guesswork and follows whatever a patch does. The limit that comes with it: a currency you hold none of is absent, so this answers what can I spend rather than what would farming this be worth.
Gil starts collapsed — it prices around 5,000 storable pieces, more than every other currency together. Each group lists its ten cheapest with a Show all toggle, and a piece appears once per currency, since the same till often lists one piece twice. A piece buyable two different ways appears under both. Needs Say how gear is obtained besides dropping.
Outfit sets only — a toggle on the section, and in Settings, holding the list to pieces that belong
to an outfit set. Worth having because most priced gear is single pieces: about one in seven belongs to a
set, and for gil it is 483 of 5,690. A currency that buys no set pieces at all drops out entirely — Sack
of Nuts prices 450 pieces and none of them is in a set — so the section gets shorter by whole groups as
well as by rows. Hunting one particular piece is quicker through /dungeondrip item <name> than by
scrolling this.
Gear a counter will only sell back to you is left out by default. The game's files record what a shop stocks, not what you are entitled to, so 1,053 pieces would otherwise be listed at a price most characters cannot pay at any balance — 1,028 of them in gil, the balance everybody has. This is the one filter here that is on by default, because it corrects the list rather than narrowing it.
Two kinds of counter, recognised differently:
| Counter | How it is spotted | Pieces |
|---|---|---|
| Calamity Salvager, Recompense Officer | the shops those NPCs offer | 337 |
| Rowena's representatives, buying back | any special shop whose only cost is gil | 716 |
For the event counters, being in their stock is enough on its own. A third of those pieces are listed against another vendor too, which looks like proof the piece is ordinarily for sale and is the opposite — those vendors are the events' own: the creepy peddler, the Starlight supplier, the House Valentione maid, the Moonfire Faire vendor, the Little Lady, the uma and hitsuji shonin. None is in the world the rest of the year.
Gil alone means a buy-back; gil beside another cost does not. Augmented Ironworks Helm of Fending is listed at 345 gil, and that is a re-purchase — the real route is the upgrade trade, one Ironworks Helm plus a 100 gil fee, which 712 of the 716 also carry. So a lone gil price is hidden and a gil fee paid alongside something else is not.
Everywhere a piece is described — the chat lookup, the right-click menu, the tooltips — a buy-back is named as one rather than as a vendor:
| Piece | Reads |
|---|---|
| Augmented Ironworks Helm of Fending | Special Shop — 1 Ironworks Helm of Fending (the real route; the 345 gil buy-back is dropped) |
| Augmented Crystarium Milpreves | Re-purchase — 600 gil (no other route exists; one of only 4) |
| Pumpkin Head | Event re-purchase — 47 gil (337 pieces; gone unless you were there) |
The price is kept in every case, since it is still what the counter charges. Only the claim that it is a way to obtain the piece is removed.
The setting reaches these descriptions too, but not evenly. With it on, the 4 pieces whose only route is a bare gil buy-back read Source unknown everywhere — a price with no way to earn the thing tells you nothing. The 337 event pieces keep their line, because hiding it would have a lookup answer Source unknown about a Pumpkin Head, which is the one thing worth knowing about it.
MGP quotes the dearer of its two prices. The cheaper is the Make It Rain campaign, a fortnight a year, and the sheet marks neither — so the standard price is the honest one to plan against. MGP is the only currency this applies to: its discount is a consistent 30% across all 158 pieces it prices twice, and nothing else in the sheet behaves that way.
Glamour Dresser — two lists, because they are the same errand from both ends: the box filling up, and the gear that could be got rid of to empty it. First, how full it is and what would free space. An outfit stored a piece at a time could be one set item instead; a piece in both the dresser and the Armoire is duplicated. Collapsing is phrased as a conditional, because it needs the outfit item — a tradeable attire box — and owning all the pieces does not produce one. The loose copies also come back to the bags, so the space only appears once those are cleared.
Then Already in your collection, under a rule on the same tab — every row is two copies of one piece: one being held, and one the collection already has. Named for the fact rather than the conclusion: it reports the second copy and leaves the decision alone, because that decision is irreversible and is being read off a snapshot that may be days old. Split by where the held copy is — bags, armoury, saddlebag, then one heading per retainer, with In Ysayle's bags and Worn by Ysayle kept apart — since what is safe to do differs and a second copy is no use without knowing which retainer has it, let alone whether it is in a bag at all; nothing equipped is ever listed. Each heading collapses with a click, keeps its count while it is shut and stays collapsed between sessions. The section says how old the snapshot behind it is, and says so when no retainer has been read.
The heading says where the held copy is; the row says where the second one is — also in your glamour dresser, also in your Armoire, or amber for also part of a stored outfit set. Hovering names both in full.
Amber is the one worth reading twice. There, the second copy is not a piece sitting in the dresser: it is one filled slot of a whole outfit set sitting in the dresser, so it only exists for as long as that set does. Take the set out and the held copy is all that is left. The row says so and stops there.
Retainers appear here whether or not they are being counted as owning a piece — that setting decides what makes a piece collected, while this list is about the holdings themselves either way. The same is true of the bags.
Right-click gear anywhere the game offers a menu — inventory, armoury, inspect, a chat link, the dresser, a vendor, the market board — and the plugin's options are there. This is the only place Where does this drop? appears: inside the plugin's own windows the duty is already on screen, so it would only be restating the obvious.
| Option | |
|---|---|
| Try on outfit: name | One per set the piece belongs to; fills the fitting room with the whole set |
| Where does this drop? | The duties that drop it, and opens whichever one is picked |
Only what the game does not already offer is added. It has its own Try On, Link and Copy, and a second of each would sit next to the real one saying the same word.
The entries sit directly on the menu rather than under a heading of their own, so trying an outfit on is one click. A piece belonging to several sets gets a row each; the D marks them all as this plugin's.
Settings → In-game UI can also mark the game's own item tooltips, adding an icon and a word to the category row — the one that says Body or Hands — saying where the piece is in the collection. Shorthand rather than a sentence, because that row is not wide.
| gold star | Put away — the Dresser, the Armoire, or a finished outfit |
| silver star | In a stored outfit that still has gaps |
| orange diamond | Carried or with a retainer, in no box at all — the word says which |
| no entry | Not collected |
Four icons for seven states, because the word beside it already says which one. The stars are a scale of how well collected a piece is; the diamond is deliberately not a third grade of star, because gear being carried is not a worse kind of stored — it is a different thing, and one trip to a vendor from being gone. It is off by default: it is the only thing in the plugin that changes what a game window contains rather than sitting beside it, and the only thing that hooks a game function. It appends and never replaces, and marks its own line so it cannot double up or overwrite another plugin's. If a patch moves what it hooks, the line simply does not appear and Settings says so — nothing else is affected.
Everything above describes the plugin as Dalamud draws it — overlay windows in Dalamud's own style, which is how the plugin has always looked and how it looks by default. Almost all of it can instead be drawn as the game's own windows, under Settings → In-game UI → Draw the panels as game windows. The switch takes effect immediately; nothing needs reloading.
What that buys is the things an imitation cannot do. A game window follows whichever UI theme is chosen in Character Configuration — Dark, Light, Classic and Clear Blue all work — and takes its text colour from the same place the game's own windows take theirs, so it changes with them rather than being told to. It scales with the game's UI scale, and each window can be scaled on its own from the right-click menu on its header. Its frame, header and scroll bar are the game's, because they are the game's.
The main window is the only one of them the player opens rather than one that appears beside something, so it is the only one with a close button and a remembered position. It survives zoning and opens itself on entering a duty exactly as the Dalamud one does.
Everything moves except Settings. The four panels that ride beside a game window — vendor, market board, Glamour Dresser, Armoire — the companion beside the Need/Greed roll, and the main window with both of its views are drawn as game windows. Settings stays a Dalamud window permanently: it is by far the largest surface, it is opened rarely and never during play, and the widgets it leans on are the ones a game window is worst at. So a mixed look is the destination rather than a stage on the way to something.
Both looks list the same things in the same order, with the same markers, the same wording and the same right-click menus. The marker table under At vendors is true of either.
| Dalamud windows | Game windows | |
|---|---|---|
| Resizing | drag any edge, and the size is remembered per panel | no resize handle — scale the window from its header's right-click menu |
| Reset to the game window's size | a button appears while a dragged size is in use | absent, because there is never a dragged size to undo |
| Getting one out of the way | fold it to its title bar | switch that panel off in Settings → Panels |
| Long item names | the panel widens to fit the longest | cut with an ellipsis; the full name is on the row's tooltip |
| The duty search | every match, in a list that scrolls | the first twelve, with a line saying how many more |
| Outfit sets and the Armoire's lists | an arrow you open | the same framed bar a section heading uses |
| Group headings on a light theme | readable | dark text on a dark bar — see below |
Group headings are hard to read on a light theme, and that is a standing limit rather than a bug to be fixed here. A collapsing header's bar is a dark texture under every theme, so its label wants to be pale in all four — but the library that draws it colours the label from the themed body text colour, which goes dark brown wherever the theme writes dark text. The label sits on a node the library keeps private, so it cannot be corrected from this side; the fix is a one-line change upstream. Carrying it as a local patch was tried and rejected, because pinning to a commit no other clone can fetch trades a colour for every build but one.
If the game windows cannot start, the plugin falls back to the Dalamud ones for that session and says so in the log. They are built on a library pinned to a particular commit, and a game patch can break it independently of anything else here — so a break on patch day is a temporary downgrade rather than a plugin with no windows at all.
| Command | What it does |
|---|---|
/dungeondrip |
Toggle the window |
/drip, /ddrip |
Aliases, claimed only if no other plugin owns them |
/dungeondrip <duty name> |
Show that duty; an ambiguous name opens the picker |
/dungeondrip <gear name> |
Say where a piece is in the collection and every way to obtain it |
/dungeondrip item <name> |
The same, forced — for a piece whose name is inside a duty's |
/dungeondrip config |
Settings |
/dungeondrip refresh |
Re-read the dresser and armoire |
/dungeondrip update |
Re-download the loot data |
/dungeondrip shop |
Identify the open vendor window, for reporting one that is not covered |
Settings are split by what they affect. General holds the rules every gear list obeys — the duty window, the loot-roll companion and the panels alike. Duties and Panels hold only what is specific to those surfaces. In-game UI covers what the plugin adds to the game's own windows, and which of its own it draws as game windows. Data covers where the plugin's answers come from, and Files holds the config folder and the one button that empties every cache — neither of those is a setting, which is why they sit apart from the rest.
Each tab scrolls on its own if it does not fit, and the window is held inside the screen rather than growing past it — the Data tab lists one row per retainer read, so its height is not something the plugin can bound.
| Setting | Tab | Default |
|---|---|---|
| List owned pieces, greyed out | General | off |
| Only show gear the current job can wear | General | off |
| Leave out gear locked to the other gender | General | off |
| Leave out gear locked to another race | General | off |
| Skip weapons, main hands and off-hands | General | off |
| Compare against Dresser, Armoire or both | General | both |
| Also count bags, armoury, equipped, saddlebags | General | off |
| Also count gear in your retainers' bags | General | off |
| ...including gear the retainer is wearing | General | off |
| Outfit-set ownership: any set, or all sets | General | any |
| Open automatically on entering a duty | Duties | on |
| ...unless nothing is missing | Duties | on |
| Close again on leaving the duty | Duties | on |
| Call out the role with the most missing | Duties | on |
| Group the list by slot, role, or boss | Duties | slot |
| Companion list beside the loot window | Duties | on |
| Panel beside vendor windows | Panels | on |
| Panel beside the market board | Panels | on |
| Panel beside the Glamour Dresser | Panels | on |
| Panel beside the Armoire | Panels | on |
| Include armoury-chest gear on both store panels | Panels | on |
| Include worn gear on both store panels | Panels | on |
| Group each panel by slot | Panels | on |
| Gear options on the game's right-click menus | In-game UI | on |
| Marker on the game's item tooltips | In-game UI | off |
| Draw the panels as game windows | In-game UI | off |
| Warn when dresser data is older than | Data | 7 days |
| Record gear that drops in duties | Data | on |
| Fill gaps from the wiki | Data | on |
| Say how gear is obtained besides dropping | Data | on |
| "Ready to buy" lists outfit-set pieces only | Data | off |
| Leave out gear only sold back to you | Data | on |
| Reference site for item links | Data | Teamcraft |
Labels above are shortened from the in-game wording. Everywhere the plugin lists gear, only pieces the chosen store can actually hold are shown. Duty coverage is dungeons and alliance raids; trials, 8-player raids, deep dungeons and the rest are not tracked.
Beside the duty it drops in, a piece carries the other routes to it, read out of the game's own Excel sheets — so this needs no download, cannot go stale, and is exact to the installed patch.
Every line reads Route - detail.
| Line | Read from | Detail |
|---|---|---|
| Crafted | Recipe |
the crafting job and recipe level |
| Vendor | GilShopItem, and any special shop charging gil |
gil |
| Special Shop | SpecialShop |
whatever the till takes, named — tomestones, scrips, marks, gemstones, or an exchange material |
| Grand Company | GCScripShopItem, GCScripShopCategory |
Storm, Serpent or Flame Seals — the company that actually stocks it |
| Quest | Quest |
the quest and its level |
| Achievement | Achievement |
the achievement |
One line per kind, not one per route. A piece handed over for any of eight different materials would otherwise spend eight near-identical Special Shop lines and push the useful one off the end. Of 18,707 pieces answered, 13,737 have one line, 3,792 two and 1,178 three.
The seal is named because the stock is company-exclusive. Of the 464 storable pieces a quartermaster sells, 445 come from exactly one company and only 19 from all three — so "Grand Company seals" would hide a real restriction on 96% of them. The 19 sold by every company keep the generic wording. Prices never differ between companies.
A gil route is hidden where an achievement route exists. An achievement reward can be re-bought from a vendor once claimed, which the sheets record as an ordinary sale — so the piece would look purchasable outright. All 94 achievement-reward pieces carry such a route, so this is exact rather than a heuristic.
The sheets are exhaustive about recipes and shops and silent about everything distributed another way. The Mog Station, seasonal events, PvP series rewards, deep dungeons, treasure maps and relic steps leave no trace in them. So nothing here ever says a piece cannot be obtained. The answer is Source unknown, with untradable or try the market board after it where the item row settles that much — and nothing of the sort while the setting is off, since a question never asked cannot have come back empty.
A price names its own currency because the route name cannot carry the distinction. Most of what the special-shop sheet describes is an item-for-item exchange rather than a currency purchase, so Special Shop alone would read identically for a tomestone counter and an upgrade hand-in.
Which vendor, and where they stand, is deliberately not answered — see Not implemented.
Any piece's right-click menu, and the end of a chat lookup, links out to a reference site of your choosing.
Links are labelled with the site's bare name — a coloured, hoverable name in chat is already recognisable as a link.
| Site | Addressed by | Can it miss? |
|---|---|---|
| Teamcraft (default) | item ID | no |
| Garland Tools | item ID | no |
| Universalis — market prices rather than sources | item ID | no |
| Console Games Wiki | article title | yes |
| Gamer Escape | article title | yes |
| Lodestone Eorzea Database | search query | lands on a results list |
A title-addressed link is a guess. The URL is built from the item's name, so an oddly titled piece lands on the site's "no such page" screen. That is why the default is addressed by ID.
Every cache has a reset on the Data tab beside its own refresh, since a reset only makes sense next to what it resets. The one button that does all four together is on the Files tab:
| Reset | Throws away | Comes back |
|---|---|---|
| Forget collection | This character's Dresser, Armoire and retainer snapshots | Whatever the game has loaded, immediately; the rest on the next visit |
| Forget one retainer | That retainer's snapshot alone | Next time they are opened — or never, for a dismissed one |
| Forget the download | The loot dataset and the tags that answer "nothing has changed" | Re-fetched at once, in full |
| Forget every lookup | All cached wiki lookups | One duty at a time, as each is viewed |
| Forget them | Drops learned from watching loot messages | Only what is seen dropping from here |
Each takes two presses, since a dresser snapshot can be weeks of visits. Nothing in the game is ever touched, and settings are not part of this — every one of these is disposable cache that rebuilds itself, so a reset costs time rather than anything permanent.
Headings collapse with a click and stay collapsed between sessions.
By slot — head, body, hands and so on. Each piece appears once, and this is where the "missing X of Y" count comes from.
By role — who can roll Need, for claiming during a run. Melee splits by gear type, since those pieces go to different jobs:
| Heading | Gear type |
|---|---|
| Melee DPS (DRG RPR) | Maiming |
| Melee DPS (MNK SAM) | Striking |
| Melee DPS (NIN VPR) | Scouting |
| Melee DPS (MNK DRG SAM RPR) | Slaying accessories |
Role view repeats a shared piece under every heading that can roll on it, so Slaying accessories also show under Maiming and Striking, and "of Aiming" shows under both Physical Ranged and Scouting.
By boss or coffer — what each fight and each chest in the duty actually drops, in the order they are met, bosses first and coffers after. A piece in two coffers appears under both, since it really is in both.
This one is only as complete as the wiki lookup for that duty: the downloaded dataset gives a duty one flat list with nothing saying where inside it anything comes from, and per-boss tables are read off the Console Games Wiki alone. A duty with no lookup groups into a single not attributed heading and says so above the list rather than leaving it to be guessed at. A lookup cached before per-boss tables were being read has no attribution either, until it next refreshes — Settings → Data → Re-fetch this duty does it now. Whichever grouping is on, a piece's tooltip names the bosses and coffers known to drop it.
A dresser slot can hold a whole outfit set, and its pieces count as owned. Hovering a piece shows the sets it belongs to and where each stands:
| Meaning | |
|---|---|
| stored, includes this piece | Nothing to do |
| stored, but this slot is empty | The outfit is held; this slot needs topping up |
| not stored | The outfit is not in the dresser |
A piece can belong to more than one set, so settings offer two readings: owned when any set containing it is stored, or only once all of them are.
The strict reading reaches the store lists too. Under all of them, a piece one of its two sets is holding is one the plugin says is not owned — so a loose copy of it appears on the panel beside the dresser, and the row says which rule put it there and that storing that copy on its own settles it. Under any, nothing changes: one stored set is enough, and there is nothing left to put in.
The game ships no loot tables, so drop lists come from elsewhere. Each entry's source is named in its tooltip.
| Source | Covers | Refresh |
|---|---|---|
| FFXIV Teamcraft | Every duty | Checked on each plugin load |
| Console Games Wiki | The duty being viewed, per boss | Cached 14 days |
| Drops seen in game | Duties played, including other players' rolls | Immediate |
loot-overrides.json |
Hand-written additions | On reload |
Teamcraft lags on brand-new dungeons, which is what the other three are for. Everything is cached on disk, so the plugin works offline and says when it is. Nothing is uploaded anywhere.
The wiki is also the only source that says where inside a duty a piece drops, since its pages carry a drop table per boss and per coffer. Those headings are read alongside the items and are what the by-boss grouping groups on; a page laid out some other way contributes its items as usual and simply attributes nothing.
A duty does not always own its own title. "Ala Mhigo" is the city, "Alzadaal's Legacy" and "the Fell
Court of Troia" are disambiguation pages, and all three duties sit at <name> (Duty) with a full set of
tables on them. A page that turns out to carry no drop table at all is followed there once — which is
the difference between those three having nothing from the wiki and having all of it. The handful of
duties that really do drop no gear, the Praetorium among them, pay one request that finds no page.
To add drops by hand, put a loot-overrides.json in the config folder
(Settings → Open config folder), keyed by territory id:
{
"1252": [45123, 45124, 45125]
}All in the Dalamud plugin config folder:
| File | Contents |
|---|---|
dungeon-loot-cache.json |
Downloaded dataset and its upstream ETags |
wiki-loot-cache.json |
Per-duty wiki lookups, including their per-boss tables |
learned-loot.json |
Drops seen in game, per territory |
ownership-<contentId>.json |
Per-character dresser, armoire and retainer snapshots |
Each has a reset in Settings; see starting again.
Clone with submodules — the game windows are drawn by
KamiToolKit, which publishes no package and is
vendored under external/ and pinned by commit:
git clone --recurse-submodules https://github.com/Spibane/DungeonDrip.gitAn existing clone catches up with git submodule update --init --recursive. Without it the build
fails on a missing project reference rather than on anything that names the cause.
Then the .NET 10 SDK (10.0.101 or newer) and the Dalamud dev assemblies, which the SDK finds from a local XIVLauncher install:
| Host | Path |
|---|---|
| Windows | %AppData%\XIVLauncher\addon\Hooks\dev\ |
| Linux | ~/.xlcore/dalamud/Hooks/dev/ |
| macOS | ~/Library/Application Support/XIV on Mac/dalamud/Hooks/dev/ |
dotnet build DungeonDrip.sln -c ReleaseWithout XIVLauncher, extract https://goatcorp.github.io/dalamud-distrib/latest.zip and set
DALAMUD_HOME to it. The target framework is net10.0-windows but builds fine on Linux and macOS.
The solution sets Platform=x64, so the DLL lands in DungeonDrip\bin\x64\Release\; building the
project rather than the solution puts it in bin\Release\. The latest.zip beside it is the
distributable, not the build that gets loaded for testing.
Windows — /xlsettings → Experimental → add the full path to DungeonDrip.dll, then
/xlplugins → Dev Tools → Installed Dev Plugins → enable.
Linux — Dalamud runs inside Wine, so typed paths must be Wine-visible (Z:\home\...). Use
the devPlugins folder instead, which is scanned automatically:
mkdir -p ~/.xlcore/devPlugins/DungeonDrip && cp DungeonDrip/bin/x64/Release/DungeonDrip.{dll,json,deps.json} ~/.xlcore/devPlugins/DungeonDrip/Enable it in the same Dev Plugins list, then re-copy and reload after each rebuild. Open config folder does not work under Wine, so the settings window shows the path with a Copy path button.
DungeonDrip/
├── Plugin.cs services, territory tracking, commands
├── Configuration.cs
├── CommandRegistration.cs claims commands, skipping any already taken
├── LegacyConfigMigration.cs carries data over from the plugin's former name
├── Data/
│ ├── HttpFetcher.cs the one HTTP client; capped, timed-out reads
│ ├── JsonStore.cs every cache file; atomic writes
│ ├── LootDataService.cs Teamcraft download, ETag revalidation, disk cache
│ ├── WikiLootSource.cs per-duty wiki lookup, cache, backoff
│ ├── WikiDropTables.cs the wikitext parse: items, and the boss each sits under
│ ├── LearnedLootStore.cs drops seen in game
│ ├── DungeonLootData.cs merges every source; territory → gear, and per boss
│ └── LootModels.cs
├── Game/
│ ├── DresserReader.cs prism box and outfit-set expansion
│ ├── ArmoireReader.cs
│ ├── InventoryReader.cs ids in bulk, and stack by stack with locations
│ ├── RetainerReader.cs the retainer currently open, snapshotted per retainer
│ ├── OutfitCatalog.cs which sets a piece belongs to, and how far along each is
│ ├── TryOnService.cs feeds the fitting room, one piece per frame
│ ├── ItemActions.cs what the right-click menus offer, in one list
│ ├── GameContextMenu.cs that list, rendered into the game's own menus
│ ├── GearRowFactory.cs item id -> drawable row, cached, shared by the panels
│ ├── ShopWatcher.cs which vendor is open and what it is selling
│ ├── MarketBoardWatcher.cs what the board's browse list is showing
│ ├── DresserAddWatcher.cs carried gear the dresser has not got
│ ├── ArmoireAddWatcher.cs the same of the Armoire, whose own screen will not say
│ ├── LootRollWatcher.cs what is up for a Need/Greed roll, and what is missing
│ ├── OwnershipTracker.cs per-character snapshot and staleness
│ └── LootObserver.cs records gear seen dropping
├── Core/
│ ├── MissingItems.cs the ownership decision
│ ├── CollectionMarkers.cs that decision turned into a glyph
│ ├── GearRow.cs one resolved row, shared by every panel
│ ├── LootRoll.cs one item up for roll, and whether it is collected
│ ├── DutyReport.cs territory + ownership → the drawn list
│ ├── DutyCatalog.cs duty list for the picker
│ ├── DropSources.cs the loot tables backwards: piece → duties
│ ├── SetCompletion.cs how far through each outfit set the collection is
│ ├── DresserPressure.cs how full the box is and what would free space
│ ├── CarriedGear.cs held gear, split by whether it is stored
│ ├── ContentFinderIndex.cs duty names; coverage; roulette pools
│ ├── RouletteAdvice.cs which job to queue each roulette as
│ ├── JobRoles.cs who can roll Need on a piece
│ ├── StorageEligibility.cs what each store can hold
│ ├── ItemNameIndex.cs item name → id, for the wiki
│ ├── GearNameIndex.cs the same for every storable piece, for the command
│ ├── EquipSlots.cs
│ ├── Format.cs
│ └── Sources/ how a piece is obtained when it is not a duty drop
│ ├── ItemSources.cs the facade, and the rules its builders obey
│ ├── AcquisitionSource.cs one route, and what it costs
│ ├── ItemLink.cs an item's URL on the chosen reference site
│ ├── CraftSources.cs Recipe: the job and level that makes it
│ ├── ShopSources.cs gil, currency and Grand Company tills
│ ├── QuestSources.cs Quest reward columns, checked before believed
│ └── AchievementSources.cs
├── IPluginUi.cs the seam Plugin.cs talks to, whichever look is on
├── Presentation/ what each surface shows, named rather than drawn
│ ├── Display.cs the node kinds both renderers walk
│ ├── PanelPresenter.cs the addon panels: rows, headings, filters, warnings
│ ├── StorePanelPresenter.cs the same for "what should go in this box"
│ ├── LootCompanionPresenter.cs the roll list, and why it refuses without a snapshot
│ ├── ColourRole.cs what a colour means, before either look picks one
│ ├── GlyphToken.cs what a marker claims, before either look draws it
│ ├── ToolGlyph.cs the same for a filter button's two states
│ ├── ToolButtonModel.cs one button: state, tooltip, and what pressing it writes
│ ├── GameSymbol.cs marks taken from the game's own icon set
│ ├── MarkerGlyph.cs collection state → marker and colour
│ ├── PanelGrouping.cs slot headings and the filter counts
│ ├── DutyGrouping.cs the duty list's headings
│ ├── CollectionSnapshot.cs the collection view's figures
│ ├── HeaderState.cs which headings are folded, remembered once for both looks
│ ├── PanelText.cs wording a surface uses in either look
│ ├── AddonAnchor.cs where a panel sits beside a game window
│ └── AddonFrame.cs how much of a game window's rectangle is ornament
├── Windows/ the Dalamud look
│ ├── ImGuiUi.cs owns the window system
│ ├── ImGuiRenderer.cs walks the description into ImGui calls
│ ├── MissingItemsWindow.cs picker, freshness banner, item list, roulette advice
│ ├── CollectionView.cs the window's other mode: sets, dresser, carried gear
│ ├── AddonPanelWindow.cs anchoring, sizing and the drag latch every panel shares
│ ├── VendorPanelWindow.cs what is vendor-specific about the vendor panel
│ ├── StorePanelWindow.cs what the two "what should go in" panels share
│ ├── DresserPanelWindow.cs the add list beside the Glamour Dresser
│ ├── ArmoirePanelWindow.cs the same beside the Armoire
│ ├── MarketBoardPanelWindow.cs what is board-specific about the board panel
│ ├── LootCompanionWindow.cs read-only list beside the Need/Greed window
│ ├── Palette.cs ColourRole → an ImGui colour
│ ├── Glyphs.cs GlyphToken → a FontAwesome glyph, read by both looks
│ ├── ToolGlyphs.cs the same for the filter buttons
│ ├── GameSymbols.cs GameSymbol → one of the game's icons, read by both
│ ├── UiShared.cs the widgets more than one window draws
│ └── ConfigWindow.cs
└── Native/ the game-window look
├── NativeUi.cs owns the one controller, and falls back if it will not start
├── NativeRenderer.cs walks the same description into game interface nodes
├── NativePanelAddon.cs what every panel beside a game window shares
├── NativeStorePanelAddon.cs what the two "what should go in" panels share
├── VendorPanelAddon.cs ┐
├── DresserPanelAddon.cs │ the four panels: anchor, rows, header, filters
├── ArmoirePanelAddon.cs │
├── MarketPanelAddon.cs ┘
├── LootCompanionAddon.cs the roll list, sized once and never after
├── NativeToolbar.cs the filter buttons as game buttons
├── NativeContextMenu.cs one menu per panel, refilled per click
├── NativePalette.cs ColourRole → the theme's own colours
└── GlyphTextures.cs a font glyph rendered into a texture a node can show
Neither renderer holds any of the plugin's content. Both walk one description, which is what keeps
the two looks from drifting: a change to what a surface says is made once, in a presenter, and
appears in both. Only the files under Native/ name a type from the interface library, so if that
library ever has to be replaced the exposure is bounded.
The companion window reads the loot addon and never draws into it, so it does not conflict with plugins that recolour game UI nodes.
Try-on is the one place the plugin asks the game to do something rather than reading what it has already done, and it only ever happens because it was picked out of a right-click menu. Everything else - dresser, armoire, inventory, shop and loot addons - is read and nothing more.
The game's right-click menus are the one place the plugin appears inside the game's own UI rather than beside it. That goes through the interface Dalamud provides for exactly this, which composes plugin entries rather than letting one overwrite another, so no game UI node is touched. It can be switched off under Settings → In-game UI.
A release is one pull request, then one tag. Four things move together in the pull request — they are checked against each other, so a release cannot go out half-bumped:
| File | Change |
|---|---|
DungeonDrip/DungeonDrip.csproj |
<Version> |
CHANGELOG.md |
### Unreleased becomes ### vX.Y.Z - date |
README.md |
the version badge |
repo.json |
python tools/make-repo-json.py |
Merge that, then tag the merge commit:
git tag v0.16.0 && git push origin v0.16.0.github/workflows/release.yml then builds the tagged commit on windows-latest and attaches
DungeonDrip.zip to a GitHub Release. Nothing in CI writes to main, so main can require
pull requests like any other branch.
repo.json is generated by tools/make-repo-json.py rather than hand-edited, so the store entry
cannot drift from what was built. It takes the version from the csproj, the API level from the
Dalamud.NET.Sdk version, and everything else from DungeonDrip/DungeonDrip.json — nothing from
the build output, which is why it can be committed up front. CI runs the same script with
--check and fails if the committed file is not what it would have written; the build workflow
does too, so a forgotten regeneration fails on the pull request rather than after a tag exists.
The download links are pinned to the tag, not to releases/latest. repo.json is on main
before the release is published, and with latest the manifest would advertise the new version
while the link still served the previous release's zip — installing the old plugin under the new
version number. A pinned link is simply absent until the release exists, which fails visibly.
Three things the workflow refuses to do, each of which produces a release Dalamud silently
ignores: publish a tag that is not on main, publish a tag whose version disagrees with the
csproj, and publish when repo.json does not match either.
.github/workflows/build.yml builds on windows-latest, fetching the Dalamud dev distribution so no
game install is needed, and uploads the packaged plugin.
- The retainer market. Gear listed for sale can sell while nobody is there, so a snapshot of it would go wrong in the one direction that matters — calling off the hunt for a piece that is no longer owned. The seven bag pages and whatever the retainer is wearing are read.
- Per-boss attribution for a piece the wiki's tables do not list. Every dungeon and alliance raid that drops gear has a page laying it out per boss, so a duty is attributed as soon as it has been looked up — but a piece only the downloaded dataset knows about was never in a table to be read out of one, and is left unattributed rather than guessed into the nearest fight.
- Which vendor sells a piece, and in which zone. The chain that would answer it —
ENpcBase's handler ids matched against shop rows, then theLevelsheet for a location — was tried and dropped: a shop reached throughCustomTalk,TopicSelectorPreHandlerindirection resolves to no NPC at all, and an NPC appears in severalLevelrows with nothing to say which is meant. The currency and the price are given instead, and the linked reference site answers the rest properly. - Gathering, fishing and retainer ventures as sources. Mining, botany, fishing and spearfishing were measured against the sheets and yield no equippable gear at all. Ventures do turn up 358 pieces, but 357 come from Quick Exploration — random, gated on the retainer's level, and every piece in the pool obtainable some other way that can actually be aimed at.
- Whether a named quest or achievement is already done. Both are per-character state the client only holds once its own window has been opened, so the honest answers would be "done", "not done" and "cannot say yet", with the third showing most often. The quest's level is given instead, which is what makes an old one recognisable.
- Resizing a game window by dragging, and the button that undoes a dragged size. Neither exists in the game's own windows, so under Draw the panels as game windows a panel matches the window it accompanies and is scaled from its header's right-click menu instead. Both are still there in the Dalamud windows.
- The Settings window as a game window. It is the largest surface the plugin has, it is opened rarely and never during play, and the widgets it leans on are the ones a game window is worst at — so it stays a Dalamud window, and a mixed look is the destination rather than a stage.
- A duty search that lists every match as a game window. It offers the first twelve and says how many more there are, because a search nobody has narrowed matches every duty in the game — and the alternative, a list that scrolls inside a window that already scrolls, was worse than the cap.
- Nothing else currently planned.
The distributed plugin also contains KamiToolKit, under the MIT licence. Its notice is in THIRD-PARTY-NOTICES.md.
Largely written by an AI model; see AI-DECLARATION.md.