BDScript

1. Unknown Functions

Warns if a function doesn't exist in the BDFD function list. All unknown functions show warnings, including those nested inside other function arguments.

Note: Only $ by itself (without a function name) is treated as a literal string and won't trigger a warning. Everything else that starts with $ followed by a name is treated as a function call.

2. Argument Count Validation

Validates minimum and maximum argument counts. Handles functions with multiple signatures (different argument patterns).

Argument Counting Rules:

• • No brackets: $function = 0 arguments
• • Empty brackets: $function[] = 1 empty argument
• • Semicolons separate arguments: $function[A;B] = 2 arguments
• • Trailing semicolon counts: $function[A;] = 2 arguments (second is empty)

3. Empty Argument Validation

Checks if empty arguments are allowed based on function definition.

4. Enum Validation

Validates that enum arguments use valid values from the allowed list.

{
  "function": "$addButtonCV2",
  "line": 1,
  "message": "$addButtonCV2 - Expected valid enum value in position 3, got 'invalid'. Valid values: danger, link, primary, secondary, success"
}

5. Type Validation

Validates argument types including Number, Boolean, Integer, and Snowflake (Discord IDs).

Type Rules:

• • Number/Integer: Must be numeric (e.g., 123, -45, 3.14)
• • Boolean: Must be true, false, yes, no, 1, or 0
• • Snowflake: Must be 17-19 digit Discord ID
  • Special case - $roleGrant: Requires + or - operator before role ID
  • • +123456789012345678 adds the role
  • • -123456789012345678 removes the role
  • • 123456789012345678 without operator will error
  • • Works with find functions: +$findRole[Staff]
• • URL: Must be a valid http:// or https:// URL, only validated for pure URL type arguments, not String | URL unions.

Special Value: The BDFD special value !unchanged is recognized in $modifyChannel, $modifyRole, and $editThread only and skips type validation. This value indicates "keep the current value unchanged".

6. JSON Syntax Validation

Validates JSON syntax in $jsonParse to catch malformed JSON.

7. Bracket Matching

Detects unclosed brackets during function extraction.

Important:

Escaped brackets \] don't count as closing brackets because they're part of the text content.

Examples:

• • $sendMessage[hello\] → Error (escaped bracket, missing actual closing bracket)
• • $sendMessage[hello\]] → Valid (escaped bracket as content, then closing bracket)
• • $sendMessage[hello → Error (missing closing bracket)

7a. Invalid Bracket Wrapping

Detects accidentally doubled brackets in function arguments.

Why this happens: BDFD uses single brackets [] with semicolons to separate arguments. Writing $function[[arg]] instead of $function[arg] is always invalid.

8. Unclosed Blocks

Detects unclosed control flow blocks like $if, $try, and $async.

Scope-aware matching:

Blocks are matched within their nesting scope. A $if inside a function argument must be closed inside that same argument — the $endif outside won't match it.

Examples:

• • $description[$if[x==y]ok]$endif - Error: $if inside $description is unclosed
• • $description[$if[x==y]ok$endif] - Valid: $if and $endif both inside $description
• • $if[x==y]$sendMessage[ok]$endif - Valid: both at top level

Block Pairs:

• • $if ... $endif (note: $else is optional)
• • $try ... $endtry (note: $catch is optional)
• • $async ... $endasync

9. Multiple $else and $catch Detection

Detects:

• • Multiple $else statements in the same $if block (only one allowed)
• • Multiple $catch statements in the same $try block (only one allowed)
• • $elseif appearing after $else in the same $if block

The correct order for $if blocks is: $if → $elseif (optional) → $else (optional)

{
  "function": "$else",
  "line": 5,
  "message": "Multiple $else statements in the same $if block (started on line 1). Only one $else is allowed per $if block."
}

{
  "function": "$catch",
  "line": 4,
  "message": "Multiple $catch statements in the same $try block (started on line 1). Only one $catch is allowed per $try block."
}

{
  "function": "$elseif",
  "line": 6,
  "message": "$elseif cannot appear after $else in the same $if block (started on line 1). Use $elseif before $else."
}

10. Context Validation (Parent-Child Relationships)

Ensures context-dependent functions have their required parent functions defined before use.

Order Checking:

Parent must be defined before child, checking both line number and position within the line. This allows multiple related functions on the same line:

• • $jsonParse[{}] $jsonArray[eLog] $jsonPretty[3] - Valid: Correct order
• • $jsonArray[eLog] $jsonParse[{}] - Error: Wrong order

Note: $addTextDisplay and $addSeparator can exist without a parent (optional).

11. Components v2 Validation Rules

Validates BDFD's requirements for Components v2 to catch errors before running code.

• • Sections: Must have at least 1 Text Display and 1 accessory (thumbnail or button); Duplicate section IDs are not allowed (each section needs a unique ID)
• • Containers: Must have at least 1 child component
• • Media Galleries: Must have at least 1 media item
• • Action Rows: Cannot mix buttons and select menus
• • Limits: Maximum 5 buttons or 1 select menu per action row
• • Parent-Child Order: Parents must be defined before children reference them; Empty required parent IDs trigger errors
• • Select Menus: $newSelectMenu and $editSelectMenu must have at least 1 option; $addStringSelect must have at least 1 option; Max value cannot exceed the number of options (you can't select 25 items if you only have 1 option)

12. Modal Text Input Validation

Validates $addTextInput arguments beyond just requiring $newModal.

Rules:

• • Min and max length must be integers between 0 and 4000
• • Min cannot exceed max
• • Value cannot exceed 4000 characters (resolved after escape sequences)
• • Placeholder cannot exceed 100 characters
• • All checks skipped when values contain variable or number-returning functions

Example Errors:

{
  "function": "$addTextInput",
  "line": 1,
  "message": "$addTextInput - Minimum length must be between 0 and 4000, got 5000"
}

{
  "function": "$addTextInput",
  "line": 1,
  "message": "$addTextInput - Minimum length (10) cannot be greater than Maximum length (5)"
}

{
  "function": "$addTextInput",
  "line": 1,
  "message": "$addTextInput - Placeholder cannot exceed 100 characters, got 150"
}

13. Negative Number Validation

Validates that functions which don't accept negative numbers receive valid values.

Functions checked:

• • $random - Both min and max must be >= 0
• • $cropText - Cannot accept negative values
• • $sqrt - Cannot accept negative values

14. Min/Max Value Validation

Validates min and max value constraints for select menus.

15. Variable Name Validation

Validates that "Variable name" arguments contain literal string names, not function calls.

Affected functions:

• • $userLeaderboard[Variable name;Sort]
• • $serverLeaderboard[Variable name;Sort]
• • $globalUserLeaderboard[Variable name;Sort]
• • $getLeaderboardPosition[Variable type;Variable name;Sort;ID]
• • $getLeaderboardValue[Variable type;Variable name;Sort;Position;Return type]

Why? These functions expect a literal variable name (like "points" or "level"), not a dynamic value. Even variable functions like $getUserVar[] are not allowed.

16. Function Context Compatibility

Validates that functions are used in compatible contexts.

Rules:

• • Embed builders cannot be inside message senders:
  • - Embed builders: $description, $title, $footer, $author, $addField, $color, $thumbnail, $image, etc.
  • - Message senders: $sendMessage, $channelSendMessage, $dm, $reply, $replyIn
• • Message senders cannot be nested inside other functions (except control flow like $if, $else, $try, etc.): Message senders are actions that send messages, they don't return values

Valid examples:

• • $if[x==y]$sendMessage[yes]$endif - Valid: control flow is allowed
• • $setUserVar[x;$sendMessage[hi]] - Valid: variable functions can contain anything
• • $setUserVar[x;$description[hello]] - Valid: variable functions can contain anything