Authors CurseForge

Can you describe a specific scenario where you actually need it, given that no errors are generated when you register or unregistering events that don't need to be? All the places my code used them no longer needed them after moving from Ace2 to Ace3.

Couple of small feature requests:

- Add ability to change announcement color
- Add toggle for sending the icon in the announcement. Some you can send as a parameter (SCT, MSBT, etc...) but not sure if LibSink directly supports them yet or not. For others you can send as embedded images in a font string using an escape sequence:
|TTexturePath:width:height:xoffset:yoffset|t

That is already there. You can just set their color opacity to 0%, and they will be hidden.

SCT is now using LibSharedMedia 3.0. Your other mods need be updated to use it if you want to use the SCT fonts with them.

It only takes 1-2 lines of code to make the blizz option frame movable. SCT does it by default and it doesn't hurt anything if multiple addons do the same thing.

I dunno, the blizzard option frame is very easy to use, very easy to work with, and makes it so every user knows (or will know) a consistent place to always find addon options.

That's not exactly right. All damage and healing events have a source and destination. By the nature of EavesDrop, one of the two has to be the default for when they are the same. I chose destination to be the default for damage and for healing. This works as expected 99% of the time, you just found that 1% where it doesn't.

Because that trinket actually says "You damage..." and not "You suffer..." ED views that as being you doing damage. SW:D says "You damage..." for your damage to your target, but the damage to you is "You suffer...", so ED correctly interrupts that as damage to you, regardless of the source.

zarevak, that is the correct behavior. You are doing damage to something, even if its to yourself.

Rayanea, that is the intended behavior. It was bugged before on some localizations and not showing spell colors correctly. If you are wanting to use the pet colors you need to uncheck using spell colors. Same thing with showing the "phsycial damage" text, you need to uncheck the option to show the damage type.

There is an issue with copying profiles right now. I have not had a chance to track it down, so I would suggest not using that until later. Proximo is pretty straight forward to setup, even for each character.

Unholy_prince, the actual display field, display="", like you have in the examples. As I mentioned in the original post about the new custom events, you have to set the value AlwaysLoadEvents to true at the bottom of the file if you are making changes to the file. Or you have to reset all custom events to defaults in the option menu. You probably would be better off using the in game menu than using the file.

Ackis, SCT doesn't do anything with the combat log, so you may need to start turning off other mods until you find the culprit. If you aren't getting any errors, not sure what it could be.

If a line is commented out, the game doesn't load it or even know it exists.

To create an event that shows nothing (stop spam), you just give the event no display value. I'll try and make that clear through the tooltips in a future update. Also, just to be sure, the search criteria needs to be in your localization.

Unholy_prince, that line is commented out and you have to give it a name in the update. You can either use something like this:

[21] = {name="VampSpam", display="", type="HEAL", target="ANY", search="Vampiric Embrace", r=256/256, g=256/256, b=0/256, class={"Priest"}},

Or create the event using the in game option menu now. You can also use the built in Healing Filter to just filter out small heals.

I committed some changes to fix the issues with new events and some other stuff.

That is the Main Assist Target, which usually defaults to yourself. That cannot be turned off.

I think part of the issues is I am not giving new events enough information by default to work. I made the assumption you would save them before using them, but that is a bad assumption to make. I'll adjust the new event code to make sure it functions properly regardless if you save it or not.

next96, I'll take a look at it. The issue is that skills still need to be parsed from the old chat message system. I don't want to use a full parserlib just for that, so tried to make a global string to use. I guess its not working with the Korean global string.