OPie: Tomato

Release Notes

Tomato 9

  • Patch 7.0.3 compatibility update.
  • On 7.0+ WoW clients, in OPie macros, [spec:1] [spec:2] etc conditionals refer to your current active specialization (for example, these would evaluate to true for Balance and Feral druids respectively).

Tomato 8

  • Fixed an error which could occur when deleting rings.
  • Fixed format errors in localization strings for some locales.

Tomato 7

  • Added [race:orc/human/bloodelf/...] extended conditional.

Tomato 6

  • Fixed an issue preventing the [spec:1] and [spec:2] conditionals from working correctly in macros triggered from OPie rings.

Tomato 5

  • For Paladins, Monks, Shadow Priests, Destruction and Affliction Warlocks, the combo:X non-secure conditional now checks the relevant alternate power (e.g. chi) instead of combo points.
  • Fixed an error that occurred when using Spade.

Tomato 4

  • Fixed an error that occurred when a macro contained /stopmacro.
  • Bindings involving the [;] keys are now displayed correctly in the bindings UI.

Tomato 3

  • Added [combo:X], [selfbuff:name], [selfdebuff:name], [buff:name], [debuff:name], [owndebuff:name], and [ownbuff:name] non-secure conditionals.
  • Added #parse metacommand, which causes the following command to have its arguments parsed as secure options.

Tomato 2

  • The "Only [Character Name]" option in the "Make this ring available to:" custom ring dropdown will now prevent the ring from appearing for characters of the same name on different realms.
  • Fixed an issue that caused slices of some faction-specific mounts to appear inconsistently on cold logins.

Tomato 1

  • Added [horde] and [alliance] extended conditionals.
  • Added [moving], [have:item name/id], and [ready:spell name/spell id/item name/item id] non-secure conditionals.
  • Fixed an issue preventing some equipment set items from displaying correctly.

Files

← Other releases