GRIP-EMS v2.4.9

Some abilities are replaced by another while a buff or a form is up, and while that is happening the game answers questions about the original with the replacement. Save or edit a step in that moment and EMS stored the temporary spell instead of the one you typed. Once the buff dropped, the step silently did nothing: no error, no warning, and the step text still looked correct. Blood Death Knights running San'layn hit this on Heart Strike, which is replaced by Vampiric Strike while the proc is up, and a poisoned step stayed dead for the rest of the run. EMS now checks whether it has been handed a spell you only hold temporarily and stores the one you actually own instead, both when a step is saved and when it is read back, so what you typed is what survives. Ravage on Druid of the Claw is covered as well: the game offers no route back from that one, so EMS carries a mapping measured on a live client. A step already stored the wrong way is corrected the next time EMS checks your steps, and that check no longer marks itself finished while it still has rows it could not fix, so anything it skips is retried on your next login instead of never again.

Paste an import the addon cannot take, say a collection whose sequences are all stored in a form EMS will not read, and the preview came up completely blank: no list, no summary, and no explanation anywhere on the screen. The reasons existed the whole time, but you only ever saw them after pressing Import, which nothing on that empty screen gave you any reason to press. The preview now opens with a "Not imported" section listing one plain line for each thing that was turned away, above whatever it did manage to read. Those lines wrap onto as many rows as they need, so a long reason stays readable instead of being cut off, and nothing in that section can be ticked or counted towards what you import. An import with nothing wrong with it looks exactly as it did before.

Deleting any macro moves every macro below it up one place. EMS remembered its own macros by position and only corrected the one it had just deleted, so from that moment every other macro it owned was recorded one place too high. The next time one of those sequences changed, EMS wrote the new contents into the wrong macro and left that macro's name untouched, leaving you with a button labelled for one sequence that runs a different one, and with the sequence whose name was taken being handed a brand new macro on every reload from then on. Renaming a sequence deletes a macro as part of the rename, which is why renaming imported sequences set this off; deleting a macro yourself in the macro window did it too. EMS now finds its macros by what they contain instead of by where they sit, and it looks each one up at the moment it writes, not beforehand, so a deletion in between cannot mislead it. If it cannot find one at all it now writes nothing, instead of writing over whoever is in that place. Separately, sequences whose long names shorten to the same macro name no longer end up sharing one. EMS now checks the macro names you actually have, including macros you made yourself, so each sequence gets a name nothing else is using.

In a preview long enough to scroll, ticking or unticking one sequence could leave a different row further up looking unticked when it was still going to be imported, or put a gold "auto" tag on a row that had no business carrying one. The count on the Import button was right the whole time and so was what actually got imported; only the row you were looking at was wrong. This happened because rows are reused as you scroll and one row was still following the settings of whatever had previously been in its place.