This would give support for the follow command declaration:

[Command("kicktargets")]
public void KickTargets(params Player[] targets)
{
    // Kick all the targets here.
}

It would be executed in this manner: !kicktargets PlayerOne PlayerTwo

The command handler would likely need to read the entire remaining message arguments and keep converting these, then adding them to the object list for dynamic invocation.

Name of the requested feature/enhancement:
Expanding properties?

Description:
Instead of having this compact code

[Command("do-stuff", SandboxRealm.Shared, Description = "This command doing some stuff!", Target = TargetPermission.All)]
public void DoStuff()
{
}

we have

[Command("do-stuff", SandboxRealm.Shared)]
[Description("This command doing some stuff!")]
[Target(TargetPermission.All)]
public void DoStuff()
{
}

Additional context
Don't have

One thing that's still unclear is whether or not Reflection will be allowed or not. While we'll be able to disable the access list serverside, not having Reflection clientside would cause a lot of issues, notably with populating commands.

Furthermore, not having Reflection clientside would stop us from running commands on the client after verifying if they have the permission serverside, and all commands will have to be ran on the server.

This repository contains some of the S&Box API (it hasn't been updated for a while so it's probably outdated), so this could be used to reduce the amount of errors and get some Intelisense, of course not all of it needs to be used but some of it being used could help a bit