v69-8-g45c52f2

Details

  • Filename
    SimpleItemLevel-v69-8-g45c52f2.zip
  • Uploaded by
  • Uploaded
    Aug 30, 2026
  • Size
    31.87 KB
  • Downloads
    44
  • MD5
    9fa19c57d95c425d66fd74919f584a28

Supported WoW Retail Versions

  • 12.1.0
  • 12.0.7

Supported WoW Mists of Pandaria Classic Versions

  • 5.5.4

Supported WoW Wrath of the Lich King Classic Versions

  • 3.4.5

Supported WoW Classic Versions

  • 1.15.8

Supported WoW Burning Crusade Classic Versions

  • 2.5.6

Changelog

Simple Item Level

v69-8-g45c52f2 (2026-08-30)

Full Changelog Previous Releases

  • Add an automatic import stage for translations
    This is a tweaked version of the script Bartender4 uses. It has been
    adjusted so that it gets the project ID from the TOC, and only deletes
    unused translations from wowace when a release build happens.
  • Adjust usage of L in config so it's clearer what's localized
  • Switch localization to the wowace system
  • Let config checkboxes be indented without whitespace hacks
  • Add GetLocale to luacheck
  • Rearrange localization
  • Follow-up to zhTW localization: don't need to localize item qualities
    Also, why not, color the qualities in the dropdown for clarity.
    Refs #63
  • Add zhTW localization
    Adds a zero-dependency localization table (Locales/Locales.lua) plus a
    zhTW locale file. Untranslated keys fall back to the English source
    string, so clients in any other language are completely unaffected.
    config.lua changes:
    • makeFontString() passes labels through L[], which covers every option
      label in one place
    • checkbox tooltip requirements go through L[]
    • dropdown values (fonts, positions, item quality) go through L[]
    • format strings are looked up before :format() is called
    • the slash-command error message goes through L[]
      Blizzard's own global constants (BAGSLOTTEXT, INSPECT, SHOW_ITEM_LEVEL,
      ...) are already localized by the client and fall through unchanged.
      addon.lua is untouched: its only user-facing string is inside
      if ns.DEBUG then, which never fires in released builds.