BYOND Version:511
Operating System:Windows 10 Home 64-bit
Web Browser:Chrome 67.0.3396.87
Applies to:Dream Maker
Status: Open

Issue hasn't been assigned a status value.
Descriptive Problem Summary:

When using a named argument with step_to() (and potentially more), it'll make all non-named arguments before it ignored, resulting in a "step_to: expected 2 to 4 arguments (found 1)"

Numbered Steps to Reproduce Problem:

1) Use the code below.

Code Snippet (if applicable) to Reproduce Problem:
step_to(src,target,min=0) // Error
step_to(src,target,0) // No error.

Expected Results:

It to treat named arguments the same as other procs.

Actual Results:

Named arguments eating previous arguments.

Does the problem occur:
Every time? Or how often? Every time.
In other games? Yep.
In other user accounts? Yep.
On other computers? Yep.

When does the problem NOT occur?


Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit to download old versions for testing.)

Downgraded to 511 to make sure it wasn't a beta issue, probably been an issue for a long time.

This has been a thing ever since named args were introduced. Built-in non-object procs don't support it unless they explicitly say so.
It's more that the error is misleading than wanting it to work, it should probably tell you not to used named arguments instead of acting like no arguments but that one exist.