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
The use of "/me does foo" isn't sent through the bridge, and Element returns the error "Your message may not have been bridged: Unsupported msgtype m.emote".
Google Chat does at least kind of support this, and displays User does foo when the chat partner sends "/me does foo".
If this can't be supported, it would be nice if the bridge would just send a raw "/me " over to Google instead of erroring out. Messages that are sent from Google Chat users do appear properly as "/me does foo".
The text was updated successfully, but these errors were encountered:
The use of "/me does foo" isn't sent through the bridge, and Element returns the error "Your message may not have been bridged: Unsupported msgtype m.emote".
Google Chat does at least kind of support this, and displays User does foo when the chat partner sends "/me does foo".
If this can't be supported, it would be nice if the bridge would just send a raw "/me " over to Google instead of erroring out. Messages that are sent from Google Chat users do appear properly as "/me does foo".
The text was updated successfully, but these errors were encountered: