Discord Bot Construction Kit šŸ¤–

Plugin
67

Great. Btw I will gladly consider any useful generic improvements to this plugin in case you decide to get coding again :wink:

2 Likes
68

Okay letā€™s start slow. I just submitted my first pull request to this repo :smile:.
https://github.com/merefield/discourse-discord-bot/pull/3

4 Likes
69

merged :slight_smile: danke!

4 Likes
70

Hey! Iā€™ve been trying to find a plugin that will give users in Discord a role based on the badges they have on their Discourse profile. Is this possible with your plugin? If not, is it even possible? Thanks!

2 Likes
71

Not at present but no reason why you couldnā€™t fork it and add an appropriate command to implement that!

If implemented well I would consider merging a PR. However it might be a little specific for general use because presumably youā€™d have to maintain some kind of mapping unless the badge names were same as role names? In any case youā€™d have to filter out most of them? That might get messy for general use. If you find a really clean way to manage that which would work for general users of the plugin let me know.

But fork away, fill your boots!

2 Likes
72

I would definitely like to see if it is possible. That would make me even more interested in this plugin. :smiley:

1 Like
73

Just a small question: do we have to manually run !discsync every time we want to update roles, or is it automatic?

2 Likes
74

Unfortunately yes. It might be a nice enhancement to add a ā€˜repeat in x hoursā€™ parameter (PR welcome or hire me to implement), but as Iā€™ve mentioned before in this Topic, it would be better if someone produced a new plugin using their API and created some scheduled sidekiq jobs to do that. A bot is a fun solution but not the best architecture for scheduled syncing.

2 Likes
75

Oh, thanks anyway. Yeah, we have already thought about a possible alternativeā€¦
We wanted to sync Discourse groups with Discord roles, but it looks like there is no perfect solution that suits.

We are now going to make some kind of bot using webhooks: Discourse will trigger a webhook when an userā€™s groups is updated (or username change as well) to a custom solution, which will then assign roles in Discord. We will keep using the Discord OAuth choice in order to get guilds, and by creating a custom Data Explorer query, we can get through the API those guilds.

It would be something like this:

  1. User changes groups or username
  2. Webhook to custom solution is triggered
  3. This custom solution will call back to Data Explorer API to a custom query that returns the guilds from the user
  4. With that guild, we call Discord back to update roles
2 Likes
76

A proper batch job would be better so you donā€™t lose data integrity due to one-off event glitches. Both would be perfect.

2 Likes
77

Well, I didnā€™t go through that wayā€¦ :sweat_smile:
Iā€™ve forked your repo, and made a new plugin that suited our needs:

It basically syncs all groups with Discord roles, but automatically. When a user is added or removed from a group, it will run a sync job and update their roles according to the public groups. In addition, Iā€™ve added a setting to mark a ā€œverified roleā€, that will be added to all users who have a Discourse account. And also it supports adding a list of safe roles, which the bot will ignore when syncing users (useful, for example, if wanting to set different admins and mods in the server than in the forum).
Iā€™ve also added a username-nickname syncer. It can enforce users to have the same server nickname as the forum username.

Iā€™ll open a plugin topic after cleaning up a couple of things, as maybe someone can find it useful.

7 Likes
78

@barreeeiroo what was really interesting about your fork was your leveraging of DiscourseEvents hooks.

I had assumed that wasnā€™t possible because the bot is running in a separate thread. But as youā€™ve discovered, it seems we can act on events and influence the bot. So thanks for that, thatā€™s a really important insight we can develop going forward.

So Iā€™ve started adopting that technique in the main repo, starting with the ability to set some watches on new posts or Topics that willl be announced in the admin channel of Discord.

https://github.com/merefield/discourse-discord-bot/commit/9f8498c6a56baebb4d21009dff57932b35a46b86

The functionality may be of little use as it currently stands but it demostrates the concept for others to leverage.

5 Likes
79

OK Iā€™ve developed the plugin a little further now and have POC for two way communication working:

Here are the new settings

image

  • You can designate an Announcements Channel on Discord in the plugin settings.

  • You can now type into the assigned Discord Announcements Channel and this will post your message to your assigned Discourse Topic in the plugin settings

  • You can set up a list of Categories in Discourse to post to the Announcements channel on your Discord if someone Posts there or adds a new Topic (either or both).

https://github.com/merefield/discourse-discord-bot/commit/a19aa35f6aab2504aa220a1ab3856475f27c795a

In addition Iā€™ve added a new file to manage Discord events supported by the discordrb API, with Announcements logic being the first example (feel free to develop new ones and PR if of general use to the community).

Iā€™ve also removed the changes required to app.yml to install libsodium-dev as this is now optional having updated the dependencies and not required for the plugin at present (no need to handle voice). This will make installation much simpler.

9 Likes
80

I followed the installation instructions and everything went smoothly up to the restart. The bot did not join the room, so I checked /logs:

image
image789Ɨ100 8.56 KB

Is this referring to the discord_bot_token? Itā€™s filled in, and I verified the value. Any clues?

image
image651Ɨ821 29.7 KB

3 Likes
81

Mark, apologies, I somehow missed this.

Did you discover the issue?

Can you please update and try the new version and weā€™ll take it from there

2 Likes
82

A significant update funded by the Discourse team :tada:

FEATURES: new message auto-copy and history copy command by merefield Ā· Pull Request #4 Ā·
merefield/discourse-discord-bot (github.com)

  1. A new command !disccopy <number-of-messages> <optional-target-category-name> <optional-target-topic-name> which allows you to copy Discord message history (in that channel) to your Discourse instance from within Discord chat. This can safely cope with 1,000ā€™s of messages in one go (but for that volume will take time).

  2. Automated per message chat copy, by channel to any identically named Category on Discourse: if the channel name matches the Category name, it will copy the message into Discourse if this is set:
    image

  3. For any message copied into Discourse from Discord, the User will now show correctly if that user has logged into Discourse using the Discord login (So Discord Bot is able to match the user accounts).

  4. Localisation support added for a lot of features.

Thanks to @erlend_sh & Discourse team for speccing & sponsoring this work!! :pray:

More bot stuff coming :wink: :robot:

5 Likes
83

If they login with Discourse auth or any auth other than Discord OAuth, would this plugin simply ignore them?

1 Like
84

Doesnā€™t ignore them, itā€™s just unable to match the user with the person on the other system. As a result copied messages will appear to be from ā€œsystemā€

2 Likes
86

Are threads supported?

4 Likes
87

Not yet, Klaus, but itā€™s potentially in the pipeline. Waiting for the Ruby API to be updated (blocker) then a backer to add that feature.

2 Likes