Deutsch
English
Español
Français
Italiano
Nederlands
Polski
Português
Русский
Svenska
Türkçe
Whenever a command asks for a duration, whether it's muting someone, setting up a giveaway, or issuing a temp-ban, Axis will use a flexible time parser to determine what you were trying to set. Here's how it reads what you type.
Examples
| You type | Axis reads it as |
|---|---|
2h30m |
2:30:00 |
1 months 2 hour |
32 days, 2:00:00 |
in 20 minutes and 30 seconds |
0:20:30 |
20 minutes & 30s |
0:20:30 |
3mo2d1h2m1s |
93 days, 1:02:01 |
99 years |
36135 days |
Formatting rules
| Rule | Example |
|---|---|
| Combine units freely | 1h30m -> 1 hour 30 minutes |
| Full words work too | 1 month 2 hours -> 1 month, 2 hours |
| Filler words are ignored | in 20 minutes and 30 seconds -> 20 minutes, 30 seconds |
& works like "and" |
20 minutes & 30s -> 20 minutes, 30 seconds |
| Months are 30 days, years are 365 days | 99 years -> 36135 days |
| A bare number with no unit uses the command's default unit (often seconds or minutes) | 20 -> 20 minutes, depending on the command |
| Invalid input returns nothing | beans -> not a valid duration |
Best practices / recommendations
-
When in doubt, spell out the unit. 30m is alot less ambiguous than just 30.
-
Avoid bare numbers. We don't recommend using a duration like 20 without a unit, since its meaning depends on the specific command and it's easy to get an unexpected result. Use 20m instead.
-
Break longer durations into their largest units first, such as 1mo2d rather than 2d30m or 32d, so it's easier to read back and confirm what will happen before you hit enter.