lordrichter wrote: »If it is an add-on that is breaking your chat, then yeah, you need to turn it off.
P.S. - you might want to share what add-on it is, for other that come across this, and also let the add-on author know.
Soul_Demon wrote: »lordrichter wrote: »If it is an add-on that is breaking your chat, then yeah, you need to turn it off.
P.S. - you might want to share what add-on it is, for other that come across this, and also let the add-on author know.
You would think if the game itself allowed and actually encouraged these addons from day one they would NEVER pretend that they could not have ever avoided this kind of thing. You know, like being competent at a job usually requires- consideration of impact and quality control first before you drop something on paying customers leaving them to troubleshoot.
lordrichter wrote: »Soul_Demon wrote: »lordrichter wrote: »If it is an add-on that is breaking your chat, then yeah, you need to turn it off.
P.S. - you might want to share what add-on it is, for other that come across this, and also let the add-on author know.
You would think if the game itself allowed and actually encouraged these addons from day one they would NEVER pretend that they could not have ever avoided this kind of thing. You know, like being competent at a job usually requires- consideration of impact and quality control first before you drop something on paying customers leaving them to troubleshoot.
The way the world is. Game developers update and release games. Add-on and mod makers take that and adapt to any changes. ESO generally changes things that impact add-ons once per quarter. In this case, I am guessing that the change to close what sounds like a chat-based exploit resulted in a change that broke an add-on. Oddly enough, maybe the add-on that was causing the problem in the first place.
Fixed an issue where a large number of a specific characters appearing in chat could cause the client to become unresponsive.
Dial back the rage. This problem is add on related and not the base game. While it would be best practice for zeni to communicate changes that impact API components, they would have to understand their game well enough to know the impact and we know that’s not going to happen.
And so using addons means accepting that sometimes they will get broken by unannounced changes, and we will have to turn them off until they get updated. It happens all the time and it’s really not a big deal.
The patch notes that it was related to the game client handling special characters in a way that compromised the client. Im guessing the change altered the chat API which “broke” all addons hat handle chat.
lordrichter wrote: »The patch notes that it was related to the game client handling special characters in a way that compromised the client. Im guessing the change altered the chat API which “broke” all addons hat handle chat.
Not all of them. This is why I am starting to wonder whether this is specific to an addon that, in theory, could have been exploiting this chat bug for personal gain... resulting in ZOS blocking the addon or muting those who were/are using it.
lordrichter wrote: »The patch notes that it was related to the game client handling special characters in a way that compromised the client. Im guessing the change altered the chat API which “broke” all addons hat handle chat.
Not all of them. This is why I am starting to wonder whether this is specific to an addon that, in theory, could have been exploiting this chat bug for personal gain... resulting in ZOS blocking the addon or muting those who were/are using it.
Soul_Demon wrote: »lordrichter wrote: »The patch notes that it was related to the game client handling special characters in a way that compromised the client. Im guessing the change altered the chat API which “broke” all addons hat handle chat.
Not all of them. This is why I am starting to wonder whether this is specific to an addon that, in theory, could have been exploiting this chat bug for personal gain... resulting in ZOS blocking the addon or muting those who were/are using it.
What is it you mean by "not all of them" here? Are you privy to something the rest of the community does not know or have you stumbled upon the cause of this specific problem?
lordrichter wrote: »Soul_Demon wrote: »lordrichter wrote: »The patch notes that it was related to the game client handling special characters in a way that compromised the client. Im guessing the change altered the chat API which “broke” all addons hat handle chat.
Not all of them. This is why I am starting to wonder whether this is specific to an addon that, in theory, could have been exploiting this chat bug for personal gain... resulting in ZOS blocking the addon or muting those who were/are using it.
What is it you mean by "not all of them" here? Are you privy to something the rest of the community does not know or have you stumbled upon the cause of this specific problem?
I don't have chat issues, and I run chat add-ons, so obviously, not all of them...
lordrichter wrote: »Soul_Demon wrote: »lordrichter wrote: »If it is an add-on that is breaking your chat, then yeah, you need to turn it off.
P.S. - you might want to share what add-on it is, for other that come across this, and also let the add-on author know.
You would think if the game itself allowed and actually encouraged these addons from day one they would NEVER pretend that they could not have ever avoided this kind of thing. You know, like being competent at a job usually requires- consideration of impact and quality control first before you drop something on paying customers leaving them to troubleshoot.
The way the world is. Game developers update and release games. Add-on and mod makers take that and adapt to any changes. ESO generally changes things that impact add-ons once per quarter. In this case, I am guessing that the change to close what sounds like a chat-based exploit resulted in a change that broke an add-on. Oddly enough, maybe the add-on that was causing the problem in the first place.
On the other hand, if someone were exploiting this chat thing they fixed, that certain someone may have an in-game social ban in place.
Special characters in the names in the chat window? An exploit? The only exploit I can figure out is when someone uses the special characters in their name in order to avoid being reported when they cheat in game or exploit the game mechanics which is against the TOS.
If that is true …
Special characters in the names in the chat window? An exploit? The only exploit I can figure out is when someone uses the special characters in their name in order to avoid being reported when they cheat in game or exploit the game mechanics which is against the TOS.
If that is true …
VaranisArano wrote: »lordrichter wrote: »Soul_Demon wrote: »lordrichter wrote: »If it is an add-on that is breaking your chat, then yeah, you need to turn it off.
P.S. - you might want to share what add-on it is, for other that come across this, and also let the add-on author know.
You would think if the game itself allowed and actually encouraged these addons from day one they would NEVER pretend that they could not have ever avoided this kind of thing. You know, like being competent at a job usually requires- consideration of impact and quality control first before you drop something on paying customers leaving them to troubleshoot.
The way the world is. Game developers update and release games. Add-on and mod makers take that and adapt to any changes. ESO generally changes things that impact add-ons once per quarter. In this case, I am guessing that the change to close what sounds like a chat-based exploit resulted in a change that broke an add-on. Oddly enough, maybe the add-on that was causing the problem in the first place.
On the other hand, if someone were exploiting this chat thing they fixed, that certain someone may have an in-game social ban in place.
ZOS didnt mention anything about an exploit. Just:
"Fixed an issue where a large number of a specific characters appearing in chat could cause the client to become unresponsive."
So while I suppose its possible that some people went around spiking other player's clients with large blocks of special character text, I would think we'd be able to recognize that happening.
Now, I'm on PC/NA, so I don't often see lots of special characters. Is that more of a PC/EU issue?
Soul_Demon wrote: »lordrichter wrote: »If it is an add-on that is breaking your chat, then yeah, you need to turn it off.
P.S. - you might want to share what add-on it is, for other that come across this, and also let the add-on author know.
You would think if the game itself allowed and actually encouraged these addons from day one they would NEVER pretend that they could not have ever avoided this kind of thing. You know, like being competent at a job usually requires- consideration of impact and quality control first before you drop something on paying customers leaving them to troubleshoot.
BloodSkull_ESO wrote: »what chat addon are you using @Soul_Demon
Soul_Demon wrote: »lordrichter wrote: »If it is an add-on that is breaking your chat, then yeah, you need to turn it off.
P.S. - you might want to share what add-on it is, for other that come across this, and also let the add-on author know.
You would think if the game itself allowed and actually encouraged these addons from day one they would NEVER pretend that they could not have ever avoided this kind of thing. You know, like being competent at a job usually requires- consideration of impact and quality control first before you drop something on paying customers leaving them to troubleshoot.
You are aware addons are 3rd party, and not official, right? You do realise that? Please tell me you understand how a mod works.
Soul_Demon wrote: »BloodSkull_ESO wrote: »what chat addon are you using @Soul_Demon
At present two or so that I know have only chat functions. Pnames, Shissus as primary- unfortunately about 30% of all the guild addons have somewhat of a function in chat too- making the list pretty extensive along with some combat ones. Right now seems to be involved in about half of all the addons I have on- then again it could be just because we don't know for sure what the issue is exactly.
Turning off Shissu's 'chat' line worked for me.
Trinity_Is_My_Name wrote: »libchatmessage was the culprit for me. I think any library with a Chat function will cause the issue.