xenon-bot / discord.club Goto Github PK

This could be done via discord ID or something similar. This way, I can build out all of the templates and our mods can come in and edit what needs to be changed.

Rather than create a webhook for each channel when sending embeds, it would be nice to have a dropdown on the web panel to select the specific channel you want the embed sent to. This would allow embeds sent via the bot itself rather than over webhooks.

Is your feature request related to a problem? Please describe.
My feature is not related to any problem.

Describe the solution you'd like
Switch the Embed Generator link to embeds.discord.club

Describe alternatives you've considered
Switch the Discord Bot Club link to discord.club/tools/bots

Describe the bug
I have this JSON code template that I use for changelogs:

{"content":"","embed":{"title":"","description":"<CONTENT>","url":"","color":13017,"fields":[{"name":"Date","value":"<DATE>","inline":false}],"thumbnail":{"url":""},"image":{"url":""},"author":{"name":"anthony#8577","url":"","icon_url":"https://cdn.discordapp.com/avatars/158063324699951104/a_9e473c1a5e566a0ca223e634f0d4b504.gif?size=256&f=.gif"},"footer":{"text":"","icon_url":""}}}

However, the issue I'm having is that the color "13017" isn't actually the proper color code I want. The proper color code's RGB format is (221, 147, 35) which translates to 13017. But the color I get (RGB) instead is (217, 50, 0). This is started to get a bit annoying, so I feel it's appropriate to make a bug report.

To Reproduce
Steps to reproduce the behavior:

1. Go to https://discord.club/tools/embed-generator/
2. Scroll down to "JSON Code" and paste in the code above
3. Scroll up and you should see that the RGB color is (217, 50, 0)

Expected behavior
The expected behavior is that I'm supposed to have (221, 147, 35) as the proper RGB code.

Screenshots
GIF: https://i.imgur.com/eAuGIvd.gif

System (please complete the following information):

• OS: Windows 10 Home Edition (x64)
• Browser: Google Chrome
• Version 69.0.3497.100 (Official Build) (64-bit)

Additional context
N/A

I suggest making it to where Xenon can also save bot permissions in channels if im not mistaken this was implemented before because it worked before this will be really helpful as I do not feel like redoing the permissions that are needed for each bot.
Example:

^^ need it asap... Thank you!

I used to fill only the string "Unembedded" and I managed to make the "webhooks". Now the https://discord.club/embedg/ service requires filling in the "Unembedded" and "Basics" lines. without filling in the string "Basics" he refuses to work.

Be able to delete the saved Json Codes. I accidentally saved on of my embedded formats too many times, and I can't delete and single one. There is just a big list of codes that are saved when I press "Select to load"

After sending a message with embed content, I often find myself wanting to edit its contents, but am forced to recreate it on the web interface, then resend it and delete the old one. This brings up a few issues, like:

• New message notification (some may not want a notification to be triggered)
• New message at the bottom (this may break a logical order, like in rules)
• New message ID (could potentially break features from bots, like Reaction Role, that binds reactions to a message ID, or break custom links that lead directly to the message)
• Has to be repinned (if the original message was pinned, the new one will have to be repinned)

I know it's possible for the embedded content in a message to be edited, as bots like Reaction Role have this option. But as the web interface for Embed Generator uses webhooks to send the message, I'm not sure if that's feasible. It may still be, if the webhook allows to read and/or edit messages.

I've imagined the following solutions (they may not be technically possible, though):

• Specifying a message ID together with the webhook, that points to the original message in the webhooked channel, then proceeding as usual. The updated message would then edit and replace the contents of the original one instead of creating a new message.
• Same as the above, but the web interface would have an option to automatically read the original message and pre-fill the fields with the original content, making it easier to update in case of small changes.
• Same as the above, but with an option to automatically scan the webhooked channel and fetch the messages, allowing you to select them in a dropdown instead of having to find the ID.
• A mix of the above ones with the Embed Generator bot. Maybe the bot could automatically point the web interface to the messages, edit the messages or something similar.

If wanted, I could help in the development of this feature by giving ideas and feedback as it's being developed.

Description:
When I try to add custom emojis to my embed for my server, in the <:EmojiAlias:###########> format, it doesn't send the emoji, it only sends the :EmojiAlias: instead of the emoji.

Describe the bug
As of this moment, you cannot change the webhook URL field on the webpage. It allows you to create one, however, this doesn't change the URL in the webhook field still.

To Reproduce
Steps to reproduce the behavior:

1. Go to the embed page website
2. Try to enter anything in the webhook field

Expected behavior
It should allow you to change the webhook URL.

Screenshots
None.

System (please complete the following information):

• OS: Windows 10
• Browser: Google Chrome
• Version 76.0.3809.132 (Official Build) (64-bit)

Additional context
None.

Currently, "saved" embeds are given a simple timestamp.

I would love the ability to name these embeds so that I can quickly jump to the one I am looking for.

There is an error with the Embed generator you guys have made, it reported the JSON code as {"embeds": ["0"]}, what?
My JSON code in the thing is
https://pastebin.com/AG99fyfb
[Look in the link to see it.]
Can you fix this? It's way far off from the original, I don't think this is normal.

Hey guys, сan you make a similar site in the app? With predrawing, storing webhook keys and titles.

The optional possibility to create two or more embeds in one message with all possibleparameters