v0.2.0

MogWhere

v0.2.0 (2026-08-26)

Full Changelog Previous Releases

• Changelog for 0.2.0
• Correct a comment that claimed the data cannot classify a drop
  It said their database carries creature ids and no classification, so nothing
  could ever say "rare" without guessing. Their headers classify, AddPlace already
  prints the one an item was filed under, and a Krasarang rare shows up as "Rare"
  with nobody inventing anything.
• Name what drops it, when the client cannot
  A boss inside an instance is named twice over, by the client drop lines and by
  the place. A rare standing in a field is in neither, so the panel printed its
  coordinates without ever saying whose they were.
  The line is suppressed when an encounter is already named, otherwise the same
  kill would be announced twice within three lines.
• Banner on top of the CurseForge description, and only two images in it
  CurseForge does not thumbnail images in a description, so one capture per feature
  took the entire page. The banner and the overview stay inline; the other six
  belong in the Media tab, where the gallery resizes them.
  The star line also caught up with the code: it now marks a rare as readily as a
  vendor, and clears on a kill as well as on a conversation.
• Mark what has to die, and stop marking it once it has
  Two gaps that shared one assumption: that every destination is somebody you talk
  to.
  Creature ids were only exposed on recipe offers, so a rare holding the appearance
  itself was never marked at all. They are now on every offer, and the star falls
  back to the first one when there is no vendor or quest giver to aim at.
  Nothing cleared the star on a kill either. The five interaction events are all
  conversations and none of them fire when something dies, so the marker would have
  hung on until the poll gave up a quarter of an hour later. UNIT_DIED from the
  combat log closes it, matched on the creature id inside destGUID.
  That last one is read with a direct pcall rather than ns.Try, which returns at
  most six values. destGUID is the eighth.
• Give the reader somewhere to click
  The README described the addon at length and never once said where to get it.
  CurseForge and the latest GitHub release now close the introduction, centred,
  before the screenshots start.
  The placeholder comment that stood in for the CurseForge link goes with it.
• Keep the CurseForge description in the repository
  It was a block of text pasted once into a web form, with no history and no way to
  tell what the live page says. It is now a file, with the eight screenshots
  hotlinked from this repository so replacing a capture updates the project page
  without touching CurseForge at all.
• Turn the screenshots into bullets with clickable thumbnails
  Full width captures pushed everything else off the page and made the section
  read like a slideshow rather than a summary. Each one is now a bullet with the
  picture centred underneath at thumbnail size, wrapped in a link so a click opens
  the original.
• Declare the CurseForge project id
  The packager needs it in the toc to know where to upload. Without it the release
  workflow builds the zip and stops at the GitHub release, which is what it has
  been doing so far.
• Size the pin from the space it has, instead of checking it afterwards
  The tip crossed the rule below the title block by ten pixels, and the circle sat
  too close to the top edge. Both are now derived from the rule position rather
  than picked and eyeballed, and the script asserts the clearances so a later tweak
  to the layout cannot quietly reintroduce it.
• A banner that sells the function, and an opening that covers every source
  The old banner said the name and a tagline, which tells a browsing player
  nothing. It now states what the addon is, a tooltip for the Appearances window,
  and lists the eight things it answers.
  The opening paragraph only ever talked about vendors. The addon answers quests,
  boss drops and achievements too, and leading with one quarter of the feature set
  undersold the other three.
• Show the whole window before the close ups
  The screenshots jumped straight to cropped panels, which shows what a line says
  but not where any of it appears. The Appearances tab with the panel beside it
  answers "where does this live" before the detail shots answer "what does it say".