A couple things on the wiki contribution page. Step 2 says click on c…

[LeBigNasty]

A couple things on the wiki contribution page. Step 2 says click on creatures name to open wiki. It doesn't seem to be doing that for me.
The copy feature copies the entire contents, not just that creature.
It would be nice if you could filter out motes and things that can drop from everyone. For things like common drops like gems, it would be nice if the user can filter those out or right click to ignore or some such.

---

EQBuddy 1.98.0 · Windows 26200

[DranakCorps-bot]

Thanks — I've passed this to David to review.

— Scribe (Grok Bot)

[Frankthetankk]

On the motes part — agreed, and for a specific reason: per the wiki's own Mote Guide, motes drop based on zone difficulty and player level, not creature identity. Any monster in a similar level/difficulty band has roughly the same odds, so attributing a mote to one specific creature's page isn't just noise, it's arguably inaccurate — it implies a specificity that doesn't really exist.

On common drops (gems, etc.) — I'd actually push back on filtering those out, or at least draw a hard line between "filter from my own view" and "omit from what gets suggested to the wiki." A drop is a drop, and what's clutter to one player farming for one purpose can be exactly the data another player needs (someone chasing tradeskill mats or early-game gold cares about precisely the drops a raider would call noise). I raised this exact question with the wiki's own admins recently, and got a similar pushback there — the general read was against removing common drops as a category, with maybe a small handful of genuinely negligible items (water flasks, lowest-tier gems) as reasonable exceptions.

If the actual problem is that common drops make the pack's OUTPUT harder to scan rather than that the data itself is worthless, a client-side view filter (hide, don't omit) might thread the needle — you get a cleaner glance at your farming session without the underlying wiki suggestion losing anything for someone who'd actually want it.

[LeBigNasty]

Common drops are within a lvl range and creature tier, and if they are flagged as such. Client side is what I meant when I said user filter. I don't want a never closable list of missing items because people or myself aren't putting down fire emerald bracelet and motes.
On a similar note, it would be helpful if the Drops By Creature listed it's proper name; eg "An elemental warrior" vice "Elemental Warrior", as that's how the wiki denotes them.
It would also be useful if the reads were dynamic or at least on open. Items that are missing as drops on the wiki, once corrected, still show as missing in the Drops by Creature.
Appreciate all the work.

[LeBigNasty]

Small addendum, not sure if you are checking against cached versions or not accounting for +, but I keep seeing gear listed as not on wiki that is.

The warband, amice, and gauntlets are already on the drop tables for wiki for their respective creatures

[DranakCorps-bot]

You were right, and it was worse than one place.

Step 2 — clicking the creature's name. That instruction has been in the app for as long as the ✦ marker has had a tooltip, and the creature name was a plain label with nothing behind it. Not just on the wiki contribution page: the Drops surface says the same thing and had the same hole. Four places counting the Linux/macOS build.

Both are real links now, and they go to the page the wiki actually served when EQBuddy read it rather than to a search — so you land on the article the paste was written against, redirects already followed.

The copy button copying everything. Correct, and that one is a feature rather than a bug: there is a single "Copy for wiki" button whose scope is the whole pack, and no per-creature copy exists. It is on the list, unscheduled — if you are editing one page at a time it is clearly the wrong shape, and I would rather say that plainly than promise a date.

Both are on main now. Not released yet — David is testing and polishing before the next build goes out, so it will land in the next release rather than today.

Thanks for filing it with the exact wording. "Step 2 says click on creatures name" is what let me find it: I grepped that sentence and it turned up in a file nobody had suspected.

— Dranak (Claude Code)

[Frankthetankk]

The stale-flag issue LeBigNasty's hitting in his last two comments (missing flags not clearing after a wiki correction, and the tiered-item false positives in the screenshot) might be one root cause rather than two separate bugs.

Back in #65, the ✦ comparison was confirmed to run against a 7-day per-page cache on the user's machine — so a wiki edit takes up to a week to reach the flags, immediate only for pages you haven't viewed recently. A per-page "re-check now" button was flagged as a good small ask at the time and queued, but I don't see it landed anywhere through the current changelog. If it never shipped, that would explain both of LeBigNasty's reports: the wiki page IS correct now, EQBuddy just hasn't re-fetched it since the correction landed, and there's currently no way to force that short of waiting out the cache window.

Worth checking against that queued item before treating these as two new bugs — might just be the same known gap finally being felt in practice.

Separately, the article-stripping issue on Drops By Creature's display ("Elemental Warrior" vs. the in-game/wiki "An Elemental Warrior") sounds like the same class of bug that hit the wiki pack itself in #65 (Spiroc Lord, the resolver recording the requested title instead of the title actually served) — worth checking whether that fix covered the pack's output but not the Drops window's own display, since they may be two different code paths reading the same name.

[DranakCorps-bot]

@Frankthetankk — I checked both halves of this, and you are right about one and your own evidence rules out the other. Thank you for the #65 pointer; it went straight to the answer.

The 7-day cache is real, and confirmed. EqlWikiMobs.CacheLifetime and EqlWikiItems.CacheLifetime are both TimeSpan.FromDays(7). So a wiki correction takes up to a week to reach the ✦ flags on a machine that has already viewed the page, and is immediate only on pages that machine has not looked at recently — exactly as you remembered it. The per-page re-check button queued in #65 is not in the changelog because it was never built.

The +N half is not the cause, though. The comparison already normalizes tiers before matching: both sides go through QuestCatalog.BaseItemName, which strips a trailing +N, so "Apothic Warband +4" is compared as "Apothic Warband". And @LeBigNasty's screenshot is the cleanest possible disproof — Eyerazzia +4 and Flayed Turmoilskin Belt +4 have no diamond while Fetid Skin and Fire Opal (no tier at all) do. Tiered items appear on both sides of the flag, so the tier is not what decides it.

Which leaves your conclusion standing on better ground than the mechanism you proposed: one root cause, and it is the stale cache. Every entry in that screenshot is consistent with pages that were corrected on the wiki inside the last seven days and have not been re-read on his machine yet.

So the fix is the re-check, and it should probably be two things: a per-page "check the wiki again now" on a flagged row, and the pack window re-reading everything it is about to export rather than trusting the cache. Filing it that way. It is not in 1.99.0.

What did ship in 1.99.0 from this thread: creature names on the Drops tab and in the wiki pack are real links now — the app had been telling people to click something that had no handler, which is the "Step 2 says click on..." half of your original post.

@LeBigNasty — if any of those pages are ones you corrected yourself, that timing would confirm it outright.

— Dranak (Claude Code)

[LeBigNasty]

I'll try to remember to check, but you should also check which pages. Innoruk, for example, is checking against the Lore page and not against the creature page.

[DranakCorps-bot]

Thanks for staying on the wiki-missing flags ? especially the Innoruk note that the check was hitting the Lore page instead of the creature page. I captured that leftover.

The per-page re-check shipped in 1.99.1, with polish in 1.99.2. The Innoruk lore-vs-creature case is still open.

? Scribe (Grok Bot)

[LeBigNasty]

Thanks. Looking much better.
Still recommend app side filtering of motes and client side ignore drop options

[DranakCorps-bot]

Good to hear the re-check is looking better. I captured the two leftovers you still want: keep motes out of the pack suggestions, and a client-side ignore for common drops. Those stay open.

? Scribe (Grok Bot)

[DranakCorps-bot]

Hey ? glad the re-check is looking better. The two leftovers you named (keep motes out of pack suggestions, and a client-side ignore so you can hide drops you don't care about) are captured and sent for review.

? Scribe (Grok Bot)

[LeBigNasty]

Thanks.
Small request- on the ignore, make it global. I want to ignore the item, not the item from the creature. Vendor trash, gems, etc.
Thanks

[DranakCorps-bot]

Hey ? thanks for sharpening the ignore. Global, the item itself (vendor trash, gems), not the item on that one creature. I captured that and sent it for review.

? Scribe (Grok Bot)