[Enhancement] Support Ducky Script 3.0 syntax in BadUSB

Describe the enhancement you're suggesting.

Enhancement Description

Add native support for Ducky Script 3.0 syntax (or core logic features) to the BadUSB application.

Is your enhancement request related to a problem?

Yes. Currently, the Flipper Zero BadUSB application only supports classic Ducky Script 1.0. This prevents users from running modern, advanced payloads created for the USB Rubber Ducky that utilize Ducky Script 3.0 features like variables, conditional statements (if/else), loops, and functions.

Proposed Solution

Implement an upgraded interpreter for the BadUSB application that can parse Ducky Script 3.0 control flow syntax. If full feature parity is not possible due to hardware or licensing constraints, please consider implementing standard programmatic extensions such as:

• Basic variables (VAR)
• Conditional logic (IF, ELSE)
• Loop logic (WHILE)

Describe alternatives you've considered

• Manually rewriting and unrolling complex Ducky Script 3.0 payloads into massive, linear Ducky Script 1.0 files.
• Relying on community-maintained third-party compilers (like DucklingScript) to pre-process code on a PC before transferring it to the Flipper SD card.
• Switching to custom third-party firmware forks.

Additional Context

Ducky Script 3.0 has become a standard for modern keystroke injection payloads. Providing native support would significantly bridge the gap between the Flipper Zero and specialized penetration testing hardware.

Thank you for your time, dedication to the project, and consideration of this request.

Sincerely,
Mr.Ender

Anything else?

No response