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

BetterBotTags not working #81

Open
Razzaline opened this issue Oct 30, 2023 · 1 comment · May be fixed by #83
Open

BetterBotTags not working #81

Razzaline opened this issue Oct 30, 2023 · 1 comment · May be fixed by #83
Labels
bug Something isn't working

Comments

@Razzaline
Copy link

Describe the bug
Webhooks tags aren't displaying, and there's console output showing an error.

To Reproduce
Steps to reproduce the behavior:

  1. Enable plugin
  2. Find a message sent from a webhook (e.g. PluralKit messages)
  3. Displays BOT instead of WEBHOOK

Expected behavior
Displays WEBHOOK next to a webhook message

Screenshots
If applicable, add screenshots to help explain your problem.

Details (please complete the following information):

  • Addon Name: BetterBotTags
  • Addon Version: 2.0.1
  • Discord Release Channel: Canary

Additional context

Console output:

BetterBotTags.plugin.js:233 Uncaught (in promise) TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))
    at BoundPlugin.patch (BetterBotTags.plugin.js:233:43)
    at BoundPlugin.onStart (BetterBotTags.plugin.js:275:30)
    at BoundPlugin.start (0PluginLibrary.plugin.js:3663:54)
    at D.startPlugin (renderer.js:5:34310)
    at D.startAddon (renderer.js:5:34103)
    at D.loadAddon (renderer.js:5:6716)
    at D.loadAddon (renderer.js:5:31520)
    at D.loadAllAddons (renderer.js:5:8814)
    at D.initialize (renderer.js:5:3194)
    at D.initialize (renderer.js:5:30719)
@Razzaline Razzaline added the bug Something isn't working label Oct 30, 2023
@Miniontoby Miniontoby linked a pull request Apr 8, 2024 that will close this issue
@Miniontoby
Copy link

@Razzaline Please see my Pull Request #83 since it has the fix for this issue.

You can just see the changes I made and then apply them to the plugin file or just copy paste my edited file into the plugin file

If it fixes the problem (which I am sure it does), then you can close this issue afterwards...

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

Successfully merging a pull request may close this issue.

2 participants