steveseguin
Is it normal to not see twitch emote on multi chat as a host?
As far as I know, it should be working. It might not work if using the websocket-mode, which is new, but the pop out or classic mode should work.
if that is a BTTV/7TV emote, you need to enable the option to support them in the menu.
How can I test this all myself? It's possible that since you're using the dashboard, versus the normal pop out ilnk (https://www.twitch.tv/popout/evarate/chat?popout=) , there might be a different there I'm missing?
It could also be that you have installed a third party browser extension that is breaking the chat, making it so I can't detect things. If so, what do you have installed ?
Me have enabled them BTTV and 7TV, and the output on the right in the screenshot is through OBS, if that got anything to do with it?
Emotes seem to end chat messages prematurely, cutting everything starting at the emote. - Image shows the social_stream combined chat on the left and the Twitch popout chat on the right.
Also as a note, this seems to only be an issue with Twitch chat. (My Kick & Trovo chats look fine with emotes). Also seems to be fine with basic emojis, but breaks with Twitch, BTTV, & FFZ emotes. (I don't have any 7TV emotes to test with)
FFZ browser extension (chrome frankerfacez/fadndhdgpmmaapbmfcknlfgcflmmmieb) is conflicting with it. Now I need to figure out which FFZ setting(s)... :\ Current stable is 4.77.4, but I won't bother testing before 4.77.5 (which is currently in nightly build) is out as that version fixes multiple (probably unrelated) issues I'm having with it.
Thank you for finding that out. That helps a lot; I might be able to fix the issue. You can technically disable it also, and use the built-in FFZ function, however that might not be ideal for your use case.
I pushed a fix for FFZ support. I dont know it's perfect, but it fixes the cut off issue I believe.
I pushed a fix for FFZ support. I dont know it's perfect, but it fixes the cut off issue I believe.
I only noticed now that your last update(s) was/were released with the same version number (3.22.7), so my browser extension never reported that a new version was availlable. I just updated now, so I'll test it out and see if it fixes the issue on my end.