v0.10.4

Automatic pre-release of 0.10.4 for 84c042e

v0.10.3

Automatic pre-release of 0.10.3 for f5df36a

v0.10.2

Automatic pre-release of 0.10.2 for 21c4cde

v0.10.1

Automatic pre-release of 0.10.1 for bb19384

v0.10.0

Automatic pre-release of 0.10.0 for fb3e0ae

v0.9.0

Automatic pre-release of 0.9.0 for d432c15

v0.8.4

Automatic pre-release of 0.8.4 for 4aa1643

v0.8.3

Automatic pre-release of 0.8.3 for d3e33b8

v0.8.2

Enhanced .help with IConverterUsage

Now custom converters can implement IConverterUsage like:

// Example of matching horses in LeadAHorseToWater

public record Horse(Entity Entity);

public class NamedHorseConverter : CommandArgumentConverter<Horse, ChatCommandContext>, IConverterUsage
{

// New:
     public string Usage => $"Closest horse in {RADIUS} unit radius, first matching name if provided."
     const int RADIUS  =25;
...
}

public Enum HorseType {Special, Regular}

Enums and Usage in .help

Now for commands that have a Horse argument, invoking their individual help will list the possible values of Enum i.e.

[Command("example")]
void UpdateType(ChatCommandContext ctx, Horse closest=null, HorseType type = HorseType.Regular) => ...

When running .help example included in the response will be

Horse: Closest horse in 25 unit radius, first matching name if provided.
HorseType: Special, Regular

Enums should parse strictly

Fixed decaprime/CommunityCommands/issues/12 via framework change. This is a great bug to be reported, thank you @robotomist . The expectation is that VampireCommandFramework should handle argument matching and parsing, in this case the built in converter for Enums was letting in values that weren't valid as expected in the commands and so was fixed by #17.

What's Changed

• Enhance parameter help by @decaprime in #18
• 🐛 Resolve #16 by adding defined check for EnumConverter by @decaprime in #17

Full Changelog: v0.8.0...v0.8.2

v0.8.1

Automatic pre-release of 0.8.1 for 9e30cb2