Is your feature request related to a problem?
Currently, the /combat tag command only supports default tag durations set in the configuration (e.g., /combat tag <player> or /combat tag <player1> <player2>). There is no way for server administrators or staff to manually apply a combat tag with a custom, dynamic duration for specific scenarios.
Describe the solution you'd like
I would like an extension to the /combat tag command that accepts a custom time/duration argument:
/combat tag <player> <duration> (e.g., /combat tag Player 30s or /combat tag Player 1m, etc.)- (Optional)
/combat tag <player1> <player2> <duration>
This would allow overriding the default combat duration specified in the config.yml for a specific invocation.
Describe alternatives you've considered
No response
Additional context
This feature would greatly improve flexibility for administrative actions.
Is your feature request related to a problem?
Currently, the
/combat tagcommand only supports default tag durations set in the configuration (e.g.,/combat tag <player>or/combat tag <player1> <player2>). There is no way for server administrators or staff to manually apply a combat tag with a custom, dynamic duration for specific scenarios.Describe the solution you'd like
I would like an extension to the
/combat tagcommand that accepts a custom time/duration argument:/combat tag <player> <duration>(e.g.,/combat tag Player 30sor/combat tag Player 1m, etc.)/combat tag <player1> <player2> <duration>This would allow overriding the default combat duration specified in the
config.ymlfor a specific invocation.Describe alternatives you've considered
No response
Additional context
This feature would greatly improve flexibility for administrative actions.