EMS-Changelog

GRIP-EMS v2.4.12

Released September 3, 2026. 2 entries in the author's notes.

Every entry

The author's own words, complete. Long sections are sorted into areas by LazyGrip.

Fixed

2
A sequence with one damaged version no longer breaks the version display.#

v2.4.11 stopped a badly stored sequence taking the rest of the addon with it by checking each place that read one, and this release moves the check to the one place they all read from, which closes the rest of them and fixes the version number along with it. If a sequence held a version stored in a shape EMS did not expect, nothing on screen would tell you which of its versions was live: no LIVE badge in the editor, no marker beside the version in its menu, no tag on the sequence list row, and no number on the tracker, on a sequence that had a live version the whole time. The tracker also disagreed with itself, printing a number in one place and a blank in another for the same sequence, and the list and the editor disagreed the same way. Where two versions happened to hold the same value, the badge picked the wrong one and named it live. A sequence with context overrides carried one more problem: what EMS had written down about the live version and what it read back never matched, so every context change and every talent loadout change queued another reload of that sequence, on and on. All of it came from one question being answered in more than one way.

A badly stored sequence no longer stops the parts of EMS that draw nothing on screen.#

The same check went into four of them: answering another player who asks to see your sequence list, duplicating a sequence, activating one whose step text was stored as something other than text, and building the steps for a sequence that pulls in another sequence's steps. Each read a stored part of the sequence without checking its shape first, so steps that were not a list, step text that was not text, or a record of what a sequence had been copied from that was not a list could stop that job where it stood. The list answer had a second fault of its own: where the steps were stored as plain text, nothing stopped at all, and the count that went out was taken from the length of that text, so the player who asked was told a number of steps the sequence did not have.

Grab it

Release notes written by Sataana and reproduced here with his permission.