MogWhere

v0.3.0 (2026-08-26)

Full Changelog Previous Releases

• Document quiet mode, and release 0.3.0
  The command table and the project page both predated it. The CurseForge copy
  leads with the reassurance rather than the mechanism, because "never modifies your
  settings" is the sentence that decides whether somebody clicks.
• Ask AllTheThings whether we are quiet, do not remember it
  The state lived in an "active" flag in our own saved variables, and it drifted:
  the addon reported quiet mode while ATT's profile page said Default and the
  tooltips were plainly back.
  Their profile assignment is per character. Ours was per account. Logging onto a
  second character was enough to make the two disagree, and picking a profile inside
  ATT itself is another way we would never hear about.
  So the flag is gone. "Are we quiet" has one honest answer: is ATT on our profile
  right now. The saved variables keep only what cannot be read back, which is the
  profile to return to.
• Both dialog buttons state an outcome
  The apply button read "if not already quiet, toggle". On a re-ask by somebody who
  was already quiet that did nothing whatsoever, and said nothing either, so the
  click looked broken.
  Neither button guards against the current state now. They declare one, the same
  way /mw quiet on does, and asking for the state you are in says so. "Keep it as
  it is" also has to mean the same thing on the tenth question as on the first:
  AllTheThings showing everything.
  Third silent no-op of the day, after a return value that did not exist and a
  guard that suppressed a line. A refusal has to be audible.
• Reword the popup body
  Drops the qualifier after "windows", and names MogWhere as the thing offering the
  quiet profile rather than describing it in the abstract. Reassurance moved to the
  future tense, which reads as a promise about what the click will do instead of a
  claim about a state the reader cannot yet see.
• Halve the popup text
  Three paragraphs for a two button question. It kept the two things that matter,
  that AllTheThings is genuinely good and genuinely dense, and that the quiet
  profile does not touch the player's own settings, and dropped the rest.
  Around sixty words instead of a hundred and twenty. The dialog measures itself,
  so it shrank to fit without any layout work.
• Say what you want, not the opposite of what holds
  The slash parser only ever read the first word, so any argument was silently
  dropped. It now takes one, and quiet understands on, off, ask, or nothing to
  toggle.
  Set rather than toggle underneath: running "/mw quiet on" twice has to leave the
  same state as running it once, which a toggle cannot promise, and a macro wants to
  state its intent rather than ask for the inverse of whatever holds at the time.
  Asking for a state you are already in says so instead of flipping you out of it.
  "/mw quiet ask" clears the remembered answer and reopens the question on the
  spot, with no reload, which beats telling somebody to run a /run one-liner.
• Verify the profile switch instead of trusting a return value
  ATT's SetProfile returns nothing. The toggle treated "no return" as failure, so
  it announced that nothing had been changed on every single attempt, while having
  already switched the profile.
  Both directions now read the profile back and compare it to the expected name.
  Their getter answers "Default" rather than nil for an unassigned profile, so the
  expected value is normalised before the comparison.
  Second bug of this shape today, after ns.Try capping at six return values and
  silently dropping destGUID. Reading the outcome beats believing the call.
• Measure the dialog instead of guessing its height
  The frame was fixed at 260 pixels with the buttons anchored to its bottom edge.
  The body is three paragraphs, it wrapped past that, and the buttons sat on top of
  the last one.
  Everything is now anchored to the element above it and the height is the sum of
  what those elements actually occupy. That cannot go stale when the wording changes
  or when a translation runs longer than the English, which is exactly what would
  have happened here on the next language added.
• Ask once, the first time AllTheThings is seen
  Neither answer is a sane default. Applying quiet mode unasked would be one addon
  reconfiguring another behind the player's back; doing nothing leaves somebody who
  installed this for a wardrobe panel wondering why their minimap grew a button.
  So the question is asked once, with both consequences spelled out, and the answer
  is remembered. The flag is deliberately not set when AllTheThings is absent:
  install it next month and the question is still worth asking then.
  The pointer to ATT's own options rides in the existing footer line rather than
  becoming a fourth paragraph. The body is long enough.
• Quiet mode: silence AllTheThings without touching its settings
  Somebody who installs MogWhere for the wardrobe panel gets the whole of ATT with
  it, minimap button, tooltip lines, popups and sounds. Fine behaviour from a fine
  addon, and not what they asked for.
  The dangerous way to fix that is to remember every setting, overwrite them and
  hope the restore runs. A crash or an uninstall and the player is left with a half
  configured addon and no idea why.
  ATT has profiles, so none of that is needed. Quiet mode copies their current
  profile into one named MogWhere, switches to it, and only then mutes anything.
  Every write lands in our profile. Theirs is never modified, still appears in
  ATT's own settings, and coming back is one call rather than a replay of thirty
  values. Worst case they pick their profile again from ATT itself.
  /mw quiet, and a checkbox in the options panel that reads the live state.