Function Argument Update Bugs

Fair warning: I have no idea what has been fixed yet or not, so feel free to check off anything that has already been fixed <3

If anything is not a bug/invalid give a strikethrough.

• $allowRoleMentions[]/$allowUserMentions[] when used without inputting any userIDs results in the bot not responding.
• $optOff[] when used on a function-set that doesn't return any outputs results in a error. (see example)
• $textSplit[] now removes spaces from the again, although the bug was fixed a while back.
• Unable to leave argument 3 (label) as empty in $addButton[] even when there is an emoji set (a feature supporting empty labels when emojis are used was added awhile back).
• $isBot[] returns a error if you leave the 1st argument empty.
• If I remember correctly, $isBot[] didn't check if the user actually exists, rather it returned false. Now, it requires the first argument to be a snowflake. I could be wrong about this however, but if this was the case, I suggest making it work like the old way
• $async[] allows the first argument (the async block's name) to be left empty (and $await[] doesn't).
• $removeLinks doesn't work when used without brackets, as it used to.
• $toUppercase[] doesn't work
• $newTicket[]'s second argument (message when no ticket) should be emptiable as it used to.
• $sort[] trims spaces from the last argument (separator), so if you use , it will be outputted as ,.
• …I’ll add more as they get reported / found

Discord Example issue.

I wish the examples on the wiki were more beautiful and well-formatted.

• 1. Write "Today at hour:minute" instead of "DD/MM/YYYY" (06/29/2024);

• 2. "✓ BOT" text does not fit into the bot icon;

• 3. The text in the embed has been reduced several times. I wish it was a normal size;

• 4. Sometimes there are distances between embed components (For example, between title and description).

• Screenshot for PC:

• Screenshot for Mobile:

Source Wiki

• 5. The icons in the channel mentions are faulty.

Source Wiki

• 6. Change the "✓ BOT" to "✓ APP" in the icons (refer to 2.)
• 7. Sometimes (mostly on the phone) the color of the buttons matches the color of the link highlight.

Source Wiki

• 8. The highlight color is also duplicated on the marked text. (This text)

• 9. Marked text uses the Markdown version, but not Discord.

• Screenshot of BDFD wiki:

• Screenshot of Discord:

Source Wiki

• 10. Embed fields is too bold, perhaps this is due to a font size issue. (refer to 3.)

Source Wiki

The Issue

As of right now, deployments to the wiki site have to be manually done.

Resolution

It is possible to have CI resolve this issue.
I'm suggesting that a GitHub action automatically deploys changes when they are pushed.

Resources

• https://github.com/rust-lang/mdBook/wiki/Automated-Deployment%3A-GitHub-Actions#github-pages-deploy
• https://rust-lang.github.io/mdBook/continuous-integration.html
• https://github.com/features/actions

When going to a URL which doesn't exist, the user is directed to a dysfunctional unstyled page rather than a 404 page.

I have rewritten the BDFD ToS to make it a bit more professional-like. This issue is referring to the ToS page: https://botdesignerdiscord.com/tos. It implies that the current ToS is open for modification. This issue is open to feedback and suggestions 👍

Terms of Service

Your use of our service ("Bot Designer for Discord") implies that you agree to the Terms stated on this page, and these Terms will remain in effect while you use the service.

Context and Reference

• "Bot Designer for Discord" refers to "our service".
• "our service" refers to the mobile application, "web app", and any other related product or service that Bot Designer for Discord provides. It should be noted that Bot Designer for Discord is a service provided by parent-company NilPointer Software.
• "web app" refers to our web panel (the "web app" is accessible via most major web browsers) from which users may modify their bot(s) and/or account.
• "template store" refers to the platform which Bot Designer for Discord's mobile application provides. It serves as a way for users to share and use bot command code(s).
• "bot" refers to a user's Discord Bot. A "(bot) command" is a certain order which can be called by a user (a "user" referring to anyone that has access, not just a user of our service in this case) typically in a Discord text or DM channel.
• "using our service" refers to having the application installed on your device, being logged in to our web app, or accessing any related product or service. If you use our service, you are considered a "user". When the phrase "user" is utilized in these Terms; it refers to an individual using our service (unless stated otherwise).
• "spam" refers to an action that's repeated in mass form.
• "Premium Points" are our in-app currency which users can buy via the premium points store. A premium point grants the user one week of premium-hosting for a singular bot, which allows for some extra functionalities that the app provides for said amount of time. For premium-hosted bots, we do guarantee 90% of uptime per week. If it is less, the user (after contacting support), will receive some sort of compensation (e.g. Premium Points) if applicable.
• "promo codes" or "promocodes" are codes (randomized text) that transfer into bot hosting time. Promo codes can be earned by winning an event, giveaway, or Discord Nitro Boosting our Discord Server.
• Users can get free bot hosting time by watching advertisements; using the one-time hosting without-AD button; using Premium Point(s); or by receiving a hosting time promo code.
• "bug" refers to unintended behavior happening, often these "bugs" can be observed by users.
• "token" refers to a Discord Bot Token, a token is essentially a password (and should be treated as such) which grants full access to the bot.
• "ban" refers to a user of our service being temporarily or permanently suspended from using our service.
• "warn"/"warning" refers to a user of our service being notified that they neglected to comply with one or more of our Terms.

Terms

1. You agree that you will not contribute any content/actions that use our service or interact with our service in a manner that:
   a. is dangerous, harmful, fraudulent, deceptive, threatening, harassing, defamatory, obscene, or otherwise objectionable.
   b. is any form of "spam", or any processes that interfere with Bot Designer for Discord's services. As an example, mass creating or modifying your bot(s) with the intent of crashing or otherwise harming the service.
   c. infringes or violates the intellectual property rights or any other rights of anyone else, including ours.
2. You agree to not decompile or modify our software in any way. We may take legal steps if we detect these actions.
3. You understand that we reserve the right to warn/ban users of our service, for any reason and without previous notice; even if the user isn't directly violating our Terms. You also understand, we may ban any user that breaks Discord's Terms of Service and/or Discord's Community Guidelines.
4. You agree not to spam or overuse our computing/storage resources.
5. You agree not to resell your Bot Designer for Discord account, "Premium Points", or "promo codes".
6. You agree not to exploit a detected bug. It should be sent as a report to the developers instead.
7. You agree to cope with any applicable limitations that Bot Designer for Discord has. This includes the 2,399 guild limit per bot. We do not guarantee any amount of uptime (for non-premium hosted bots), however hosting is our best effort.
8. You understand that prices for Premium Points should, but may not include; sales and use taxes. If they do not, the user is responsible for the payment of such taxes related to the purchase.
9. When submitting or using Bot Designer for Discord's "Template store" feature, you are agreeing to the Template Store Terms.
10. You agree to our Privacy Policy.
11. You agree to first contact support before reversing your payment method if you have purchased Premium Points.
12. You agree we shall not be held liable for users that abuse our service to perform malicious, or otherwise unlawful ventures. However, as stated previously in these Terms; we do uphold the right to warn/ban in these circumstances.

We reserve the right to change, modify, add, or remove portions of our Terms at any time, and you will still be expected to comply. It is recommended to check this page periodically for changes.
We may warn/ban users if we discover they didn't comply with these Terms.
All your usage and access to our service is subject to these stated Terms, if you do not agree with them, you shall not use the service.
In case we change our Terms, if you don't agree with the new Terms, you are free to reject them by no longer using our service.
Please note: Registered users may withdraw their data through the mobile application, and request the deletion of data by contacting support.

Contact

If you have questions/concerns about these Terms or our service, you may contact us via email. Support for regular users is available at [email protected], and for paying users at [email protected].

Terms.of.Service.txt

The problem of removing links should be First message and this is sad because some people put the link in the last message or in the middle of a message and the bot can not delete it and this is very annoying

• Test

The Link is https://discord.com/invite/nvBur3ne

Suggestions Upvote Leaderboard

1. $botNode: 41
2. Custom Functions: 40
3. $isBanned[userID]: 34
4. $channelType[channelID]: 34
5. $membersCount[presence (online/dnd/idle/invisible/all) (optional);filter (all/bots/humans) (optional);guildID (optional)]: 34
6. $callbackData[property]: 33
7. returnRoleID option for $createRole[]: 32
8. $botOwnerID[(optional) separator]: 31
9. Channel Variables: 31
10. Make $ephemeral support other interactions (e.g. buttons): 30

Honorable Mentions

• $usersWithRole[roleID]: 29
• Sharding: 29
• Defining whether the original message should be edited or a new message should be sent in $onInteraction: 29

FAQs

Why "Suggestions Spotlight"?
This monthly routine will help the developers with knowing which features users are wanting.

Why isn't my suggestion here?

1. It didn't get enough upvotes.
2. It wasn't something I felt was applicable.

When will this happen?
I plan on making it a monthly thing.

When will this issue be closed?
September 30th or whenever a developer feels it is ready to be closed.

UI Update Bugs Mega-Compile

Command Creation

• Blank screen appears when visiting the Slash Command menu on a new command which has not yet been saved.
• Scrolling through a lot of commands causes a developing blank screen:
  
• Callback help menu is inaccessible:
  
• When cloning a command, it takes you to the command list, not to the cloned command as it should.
• When trying to highlight a piece of text, you get shot down to the bottom of the code.

Command Reordering

• Unable to reorder commands within a folder.
• Moving the last command of the command list results in a error code.
• The ordered command doesn't go where you dragged it, just gets placed somewhere randomly.
• You can drag the "Commands" header (visual bug):
  

Slash Commands

• "Add new" button for slash options doesn't do anything:
  
• The edit button for slash options doesn't do anything:
  
• "Go to bot invites" button doesn't do anything:
  
• Sometimes when clicking on the Slash Commands tab, it just returns a blank screen.
• Sync issues

Template Store

• The template store's image header has text on it ("Template store") which is not viewable because the image is light as well as the text:
  
• When creating a template, "Show preview" button goes to a blank screen:
  
• After reporting a command from the template store, you get taken way back to the dashboard instead of just back to the command templates.

Premium

• Not yet able to access premium page to purchase premium points.
• You can go to the premium purchasing tab via the "Buy premium points" button in User Settings, but not anywhere else in app:
  
• The "Learn more" button in Premium redirects to a non existent page.
  
• Several buttons say the same thing in the Premium tab: "Learn more".
• "Learn more" in the Premium tab under the "Add premium to your bot" section does nothing:
  

Settings

• Unable to change app language from English: (Will be fixed in future update - @kubastick)
  

Functions Help

• Intent warning icon appears misaligned:
  

Variables

• Variable list doesn't update when you delete a variable until you reload the app.

Bot Settings

• After saving something in Bot Settings, it shows a blank screen.
• The "Commands that require privilege intents" page doesn't work - commands that require intents don't appear.

General

• Unable to scroll on Chromebook devices (this may apply to some other devices too).

Promocodes

• Promocodes tab missing.

Dashboard

• Changelog is outdated.
• "Try premium" dashboard item appears empty:
  

Invites

• Typo in the editing invite link permissions tab (should be Use external emojis not Use extrnal emojis):
  

How do you schedule messages in BDFD so that, for example, it will say Good morning in the morning or Merry Christmas on Christmas?

If it is not possible, please tell me.

Loading infinitely

Uploading Screenrecording_20240104_055400.mp4…

Upvote Leaderboard

1. Additional features to "count" functions: $emoteCount[type (optional) (static/animated)], bots/humans filter for $membersCount[], $channelCount[channelType] - 45
2. More user-friendly way of making buttons author-only - 39
3. $hostingExpireTime - 35
4. Increase the max hosting time (14d) to 21d+ - 34
5. Make $ephemeral support buttons and other interactions - 30
6. $isValidLink[] - 29
7. Notification setting for when bot hosting is over - 27
8. New usage of $pinMessage: $pinMessage[channelID;message], and $unpinMessage[channelID;messageID] - 26
9. Escape $;[] characters in $message, $httpResult, $userRoles, etc - 24
10. Voice moderation functions (e.g. $vcMute/$vcUnmute/$vcDeafen/$vcUndeafen) - 24

Honorable Mentions

• Option to disable pings for $reply - 23
• Optional custom time field for $botTyping - 23
• Support for thread permissions - 23
• $getUserBadges[] - 23

Conclusion

Thank you all for the awesome feedback and response last month #103 with Suggestions Spotlight. Special thanks to the developers for implementing a lot of the features suggested as well!
This month is very similar to last month--but with new suggestions 😄

Webhook Feature Request

With the introduction of webhook support on 07-08-2021, this feature request presumes that the concurrent webhook system is editable and open to modifications. This request is based on frequent feedback I've noticed, and solutions I have thought of.

This issue is split into two sections; as there are two separate feature requests.

Webhook Embeds

The current system of sending embeds for webhooks is fine as-is, however; it's very limiting. The reason for this is common embed properties are missing (e.g. authors, thumbnails, images, etc). The second issue regarding webhook embeds is that there are multiple different functions that could possibly be condensed into one or two functions. Here's two ideas I had in mind to combat this issue:
1.$webhookEmbed[webhookURL;content;title;titleURL;description;color;author;authorIcon;footer;footerIcon;thumbnail;image;addTimestamp (yes/no)] - Sends a embedded message as a webhook. Uneeded fields can be left empty.
2. $webhookEmbed[webhookURL;embedJSON] - Sends a embedded message as a webhook from a embed raw JSON.

• The benefit of 1 would be it supports most embed properties.
• The benefit of 2 would be it allows for alot of customization, although the logistics of the function would be difficult.

Deleting Webhooks

Another request in mind is a way to delete existing webhooks, $webhookDelete[].

Avoiding Breaking Changes

To avoid breaking changes on the webhook embed behalf, the solution would be to keep existing webhook embed functions; and simply adding a option to use the more advanced (and customizable) $webhookEmbed[] version.

Epilogue

Thanks for reading this issue and considering it, it's definitely open for conversation :)

Should be:

• label
• value
• description
  Written:
• label
• description
• value
  
  selectmenu.md - commit page

The last time nilpointer-software.github.io/bdfd-wiki was updated was the first of January, since then until now several changes have been made...

But the page was not updated, so the page is still out of date :)