Default/placeholder values in a required command argument makes all subsequent arguments optional.

[sovdeeth]

Skript/Server Version

[23:08:57 INFO]: [Skript] Skript's aliases can be found here: https://github.com/SkriptLang/skript-aliases
[23:08:57 INFO]: [Skript] Skript's documentation can be found here: https://docs.skriptlang.org/
[23:08:57 INFO]: [Skript] Skript's tutorials can be found here: https://docs.skriptlang.org/tutorials
[23:08:57 INFO]: [Skript] Server Version: git-Paper-125 (MC: 1.19.2)
[23:08:57 INFO]: [Skript] Skript Version: 2.6.4
[23:08:57 INFO]: [Skript] Installed Skript Addons: None
[23:08:57 INFO]: [Skript] Installed dependencies:
[23:08:57 INFO]: [Skript]  - WorldGuard v7.0.8-SNAPSHOT+2200-4a21bf4

Bug Description

When giving required type arguments default values in commands (<number=1>), Skript automatically makes that argument and all subsequent arguments optional. See the provided snippet in Steps to Reproduce.

Expected Behavior

This should, at most, make just the argument with the default value optional.

Steps to Reproduce

command test <number> <number=1> <number>:
    trigger:
        send "%arg-1%, %arg-2%, %arg-3%"

Errors or Screenshots

Other

Personally, I'm of the opinion it shouldn't make anything optional, and optional arguments should only be those surrounded by []. The behavior of the argument becoming optional is un-intuitive, as normally the only optional arguments in commands are surrounded by []. Since this argument isn't, it appears required but actually isn't. Enforcing [] for all optional commands would also mean commands would more closely follow the generally accepted convention for Minecraft commands:

Agreement

• I have read the guidelines above and affirm I am following them with this report.

[Fusezion]

As for your "other" portion I'm creating a discussion in proposals rn on that topic and how we might be able to go about changing it. just will cause a fairly heavy breaking change

[TheLimeGlass]

When you define the default argument, that's insinuating that the argument is opinional when provided, and because of that every other argument after must be optional when the default argument is provided. Skript does this because if an argument is a string, everything is going to go wrong.

This could throw an error when all the arguments are not strings, but this is intended behavior.

Skript could be able to tell the amount of arguments to improve this suggestion.

[sovdeeth]

Skript does this because if an argument is a string, everything is going to go wrong.

That makes sense. However, I think this behavior is hidden and not intuitive, and that we should error (or warn) if a required argument has a default value. Since every variable with a default value is optional, we should ensure that users explicitly make an argument optional before giving a default value in order to avoid confusion about why unrelated arguments are becoming optional.
Basically just what I said in the Other section.