Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Support for plugin "Boop" #54

Open
Brend-Smits opened this issue Mar 8, 2017 · 3 comments · May be fixed by #81
Open

Add Support for plugin "Boop" #54

Brend-Smits opened this issue Mar 8, 2017 · 3 comments · May be fixed by #81

Comments

@Brend-Smits
Copy link

Would you be able to add support for the plugin "Boop"?
Boop breaks DiscordBridge.
It prevents the bridge from picking up the chat and sending it to discord.

Dualspiral suggested the following about this:
image

@ProsperCraft
Copy link

We are having the same problem.

@nguyenquyhy
Copy link
Owner

nguyenquyhy commented Mar 19, 2017

As said in the plugin description, this is not something that can be done from my side alone:

Discord Bridge does not forward messages that are not public (any messages with custom Sponge channel), to guarantee it does not leak non-public chat (e.g. staff chat) to public Discord channel. Due to this design, currently Discord Bridge does not work with several Sponge plugins that set custom Sponge channel for public chat (e.g. Boop, UltimateChat).
The only workaround would be for the authors of those plugins to NOT set custom channel to public messages, or to provide a way for other plugin to differentiate between public and non-public "custom" channel.

@pie-flavor
Copy link

pie-flavor commented Mar 20, 2017

I want to keep compatibility, but I need a custom channel so that I can override the transform. Perhaps you could add a way of identifying appropriate custom channels. Maybe this could be customizable?

@CDAGaming CDAGaming linked a pull request Mar 15, 2018 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants