You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some addons like chronometer and the whole ace library SpellStatus rely on the event CHAT_MSG_SPELL_FAILED_LOCALPLAYER that fires when the player fails to cast a spell to print a message with that spell's name in chat.
The logging addon replaces these messages with info needed to fill player armory pages, and when it's done with that info it replaces them with NONE.
I suggest that instead of replacing it completely, the addon keeps the original "you fail to perform %s" spell and concatenates the necessary info for its logs after it.
Then the combatlog parser can be changed to simply ignore the first part of that message
Screenshots to clarify the image:
With the log addon
Without it
How it can be made more convenient for the logger: You fail to perform whirlwind: Not Enough Rage. CONSOLIDATED: ZONE_INFO... etc
The website's parser can then just ignore everything before the first period of the string.
I'd highly appreciate if this gets implemented, the number one reason that makes people dislike doing logs is it bugs out a lot of their addons that they use to track their debuff timers.
The text was updated successfully, but these errors were encountered:
Some addons like chronometer and the whole ace library SpellStatus rely on the event CHAT_MSG_SPELL_FAILED_LOCALPLAYER that fires when the player fails to cast a spell to print a message with that spell's name in chat.
The logging addon replaces these messages with info needed to fill player armory pages, and when it's done with that info it replaces them with NONE.
I suggest that instead of replacing it completely, the addon keeps the original "you fail to perform %s" spell and concatenates the necessary info for its logs after it.
Then the combatlog parser can be changed to simply ignore the first part of that message
Screenshots to clarify the image:
![image](https://private-user-images.githubusercontent.com/111737968/294686948-2d004ed8-31aa-4967-b482-28342a69e111.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTg5Mzg0OTIsIm5iZiI6MTcxODkzODE5MiwicGF0aCI6Ii8xMTE3Mzc5NjgvMjk0Njg2OTQ4LTJkMDA0ZWQ4LTMxYWEtNDk2Ny1iNDgyLTI4MzQyYTY5ZTExMS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNjIxJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDYyMVQwMjQ5NTJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0wMzZiOTg3ZTdlMzRkMDFkYzIxZjFlOTA4NjNiN2EzOGJmZWJmMjE0MDdhMzJkZTMzZjY4M2E0NGJkNDE0OTUwJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.ZO9erJWKFZFSyt0qe1FU58po9NAFyQbfRHPtV06J_nk)
With the log addon
Without it
![image](https://private-user-images.githubusercontent.com/111737968/294686970-a5ac5867-af20-4f05-b198-efe0e37f643c.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTg5Mzg0OTIsIm5iZiI6MTcxODkzODE5MiwicGF0aCI6Ii8xMTE3Mzc5NjgvMjk0Njg2OTcwLWE1YWM1ODY3LWFmMjAtNGYwNS1iMTk4LWVmZTBlMzdmNjQzYy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNjIxJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDYyMVQwMjQ5NTJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT03ZDdlMzM4ZGRjMDdmNDFiYmYxZjNiZTQ2ZjdhYjE2YmQ1YjRhOTU5MjU0Y2E3N2M3NTlkZTE4NTZhMmMwM2RjJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.sIDmi8p_nk_czbqympOx0ePfYU_Xa62dv1RiK-H-eT4)
How it can be made more convenient for the logger:
You fail to perform whirlwind: Not Enough Rage. CONSOLIDATED: ZONE_INFO... etc
The website's parser can then just ignore everything before the first period of the string.
I'd highly appreciate if this gets implemented, the number one reason that makes people dislike doing logs is it bugs out a lot of their addons that they use to track their debuff timers.
The text was updated successfully, but these errors were encountered: