search

fredemmott / StreamDeck-Discord

Control the Discord application with the Elgato StreamDeck
MIT License
275 stars 23 forks source link

Discord++ Integration #112

Closed Edstub207 closed 2 years ago

Edstub207 commented 2 years ago

Closes #111

fredemmott commented 2 years ago

FWIW, both that library - and IME the websocket API it uses to talk to discord - are heavily focussed on bots and app integrations.

When I tried using the websocket API instead of the named pipe API, actions would only affect my app, not the overall discord client state

For example, the mute state would only affect the ability of my app to send audio data, it wouldn't affect whether the user was muted in channels they'd joined in the client. Joining/leaving channels would only affect where the app was active, not where the user's client is active.

AIUI this was intended so that games could use discord for in-game voice chat and programatically mute just in the context of that game, without affecting the main discord client state.

If this is still the case, this is unsuitable for this project.

Edstub207 commented 2 years ago

If this is still the case, this is unsuitable for this project.

Interesting! I'll have a play around and see if I can make any progress - It's a real shame if that's still the case with these integrations and Discord doesn't have any plans to maintain that previous functionality.

fredemmott commented 2 years ago

When I tried using the websocket API instead of the named pipe API, actions would only affect my app, not the overall discord client state

Strangely enough ,in my testing (around a year ago), this affected both the gateway API and the (also deprecated) local websocket API

fredemmott commented 2 years ago

I guess that makes sense for the 'in-game voice' feature though

Edstub207 commented 2 years ago

Closing this off - Not worth the effort with Elgato having an official Discord plugin now > https://twitter.com/elgato/status/1485979660844339200