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

Broken After Latest Discord Update #4

Open
QHV154 opened this issue Dec 8, 2019 · 3 comments
Open

Broken After Latest Discord Update #4

QHV154 opened this issue Dec 8, 2019 · 3 comments
Assignees
Labels
advanced bug Something isn't working hacktoberfest

Comments

@QHV154
Copy link

QHV154 commented Dec 8, 2019

Encrypted Messages can be read but new encrypted messages can't be sent. If you type a message with the padlock activated it sends the message but not encrypted. Sometimes having the plugin active can cause loss of ability to type in the message box. These issues are consistent with all I know who use this plugin.

@EnKrypt
Copy link
Owner

EnKrypt commented Dec 9, 2019

Yup, you're right. I just noticed this today. Thanks for reporting.

Give me a while. I'll spend some time debugging and update this issue when I have more insight.

@EnKrypt EnKrypt self-assigned this Dec 9, 2019
@EnKrypt EnKrypt added the bug Something isn't working label Dec 9, 2019
@EnKrypt
Copy link
Owner

EnKrypt commented Dec 10, 2019

I have some bad news.

In the last update, Discord seems to have completely changed how the message textbox works and replaced it with an instance of some slate editor.

Sadly this makes things quite complicated. It's a breaking change of course, but it also implies that half of the entire plugin might need to be re-written.

Having already spent an hour to debug, I simply don't have the time at this moment to dedicate the half a dozen or so hours it would take to actually fix this.

So hopefully at some point in the future, I will get back to this and this plugin will work again (till then, I advise keeping this plugin disabled).

If you're reading this and you're sad about it, there are a few things you could do to help :

  • Attempt to fix it yourself. All kinds of PR are welcome of course. I will take the time to participate in discussions and help you even if I may not have the time to code myself.
  • Find out how to get a hold of the Discord slate editor instance within React.
  • Find out how to access the slate editor APIs to do things such as getting values, setting values, overriding event handlers, etc.)
  • If you don't know how to do the above things, find someone in your network using the plugin who is a programmer and does.

@EnKrypt
Copy link
Owner

EnKrypt commented Oct 1, 2020

Adding the hacktoberfest label in case someone wants to have a look at this.
Be warned, this is likely not a simple task to fix. I did some preliminary investigation in my free time and found that the underlying modules Discord is using for capturing and queuing messages isn't straightforward.

That said, if you enjoy reverse engineering this is something you can have a lot of fun with.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
advanced bug Something isn't working hacktoberfest
Projects
None yet
Development

No branches or pull requests

2 participants