Changelog

Created: 2025 (pre-stamping; exact date unknown) Updated: 2026-09-20 WoW Patch at last update: 12.1.0 Midnight (Retail LIVE)

All notable changes to GRIP - Enhanced Macro Sequencer are documented in this file.

This changelog follows a variant of Keep a Changelog. It tracks the current release and the previous one only. Earlier release notes live in the git history.

[v2.4.20] - 2026-09-20

Added

• The Accessibility panel says when the bundled font cannot be used on your language. Atkinson Hyperlegible ships with EMS for easier reading and carries Latin characters only. On Korean, Chinese and Russian clients it was missing from the font list with nothing to say why. A line under the font picker now explains it. Every other font is still offered there. That line is in English on those clients for now, because it has not been translated yet.

• A chat line when a panel asks to be themed under a name the theming system does not know. That panel goes unthemed, which used to happen in silence. EMS now names the style it was asked for. The line appears once per name, so a panel that registers many rows cannot flood your chat frame. This line is in English on non-English clients for now, on the same terms as the one above.

Changed

• Four interface colours are lighter and the error red is softer. Muted text, secondary text, the pink accent and the focus border were all dark enough against the backgrounds behind them to be hard to read, particularly on a dim monitor. Error text was a hard saturated red and is now a paler pink that still reads as an error. The High Contrast and Deuteranopia-safe palettes got the same treatment for their error colour, and the Deuteranopia-safe accent is lighter too.

Fixed

• Three windows were never themed. The Conditional Builder, the Conditional Picker and the Keybind Conflict panel each asked for a theme style under a name the theming system does not carry, and the request was dropped without a word. They followed your opacity and scale settings but kept default colours, and none of the three appeared in the theming editor. All three use the general panel style now.

• The Unsilence buttons under the silenced contrast list never appeared. Silencing a contrast warning worked, the count in the header was right, and Unsilence all worked. The buttons for individual entries did not, because that list was built from a set of names the warnings are never recorded against. It is built from the theme elements now, so what you silenced shows up with a button beside it.

• Saving a theme to a slot, or importing one, left its colours tied to the theme you were using. The copy stopped one level short of the colour values themselves, so a saved slot and your live theme pointed at the same ones. Nothing in EMS writes colours in a way that would have let that show, so no saved theme was damaged. The copy goes all the way down now.

• Copy to All Profiles gave every profile the same theme instead of its own. All of them pointed at one set of colours and one set of saved slots, so the next theme edit on any character rewrote every profile at once. Each profile gets its own copy now.

• The step editor in the popup window did not colour macro text. The colouring was wired up before the rest of that editor's handlers, and they replaced it. The step list in the main window was never affected. It is wired up last now, so the two behave the same.

• A shared theme with something odd in its font fields is refused instead of half-applied. The font name and the font style were never checked on the way in, so a theme could pass the import check and then quietly fail when EMS tried to use it. The element never changed font and nothing said so. Both fields are checked now.

• The theme preset list no longer offers High Contrast. Picking it did nothing, because there is no high-contrast theme behind it. The high-contrast palette is a different setting and still works. It is in the Accessibility panel, under Contrast preset. Picking Default from that list now asks first, since it wipes every change you have made, which is what the Reset All button already asked about.

[v2.4.19] - 2026-09-18

Added

• Importing a bundle now asks before it skips a macro you already own. A bundle can carry a macro whose name matches one you wrote yourself. EMS has never overwritten it, but it only told you afterwards, in chat, once the import had already run. The preview marks that macro up front and offers to bring it in under a different name. The sequence steps that point at it are updated to match. Doing nothing still leaves your macro alone. Some names cannot be renamed safely, where the name has anything in it besides letters, numbers and the underscore character, or another of your macros starts with the same words, and those are left alone with a line saying which one and why.

Changed

• The spell list behind the conditions picker is current again. It was still built from 12.0.7 data, so anything added to the game since then was missing when you searched for a known-spell condition. It is rebuilt against the current patch.

Fixed

• The Key Press line now tells you where to look, and says it once. When a Key Press is too long to fit inside some of your steps, EMS tells you so in chat. It used to repeat that on every zone change, on every spell cache refresh and on every recompile, and on a sequence with modifier variants it said it once more for each variant button, which is why it arrived two lines at a time on the same timestamp. Neither line said which button it meant. The line now names the sequence, which version, which variant and its modifier, the key it is bound to, and which steps run without it. Each button says its piece once, and again only when the answer really changes, including when you zone between two versions that fit differently.

• A sequence with modifier variants reports a long Key Press once, not once per button. When your variants run the same steps and the same Key Press as the version they sit under, every one of their buttons has the same thing to say, and you were told it again for each of them. You are told once now. A variant still reports itself whenever it has something different to tell you, such as a different set of steps left out or a different count of the ones that fit. A variant with nothing different to say stays covered by that one line, no matter what it has of its own.

• A Key Release that is too long no longer calls itself a Key Press. Sequences that use only a Key Release were told a Key Press had been dropped, which is not something they had. The line names whichever block ran out of room, or both when the two together are what busts the limit.

• Sequences built on Priority, Reverse Priority or a plugin step function are covered. Only the plain step order was counted before, so those sequences overflowed with no notice at all.