ApplicationCommandOptionType: DATETIME

[i0bs]

ApplicationComamndOptionType: DATETIME

This is something that I've been wanting to see for a while now, because I see so many practical uses. Let me firstly get the case of uses that I can currently think of:

• Moderation bots
• Giveaway bots
• Poll bots
• Any functionality/dependency requiring a time window, range and/or set event
• Support bots

What is this?

The DATETIME option type for application commands would enable bot developers to give users the ability of specifying either a data and time, or a time "window" with a given range. This could be used for numerous situations, including probably more than I was able to think of. The addition of this option, to me, I feel would be extremely beneficiary because of the incessant need some users have with things like trying to either plan an event ahead of time on Discord (and don't necessarily want to use built-in features) or need to search for something within a given time window.

What would the data look like?

Having a new option type for application commands, DATETIME would be very nice to set of the two or both: a time range where it returns an array of 2 ISO8601 values, e.g.:

{
    "before": "19700119T163126.578-0500",
    "after": "19700119T162707.367-0500"
}

Or it would be able to return a singular ISO8601 value for a specific date (and time), e.g.:

{"during": "19700119T163545.778-0500"}

I believe that ISO8601 for this would be great as it follows with most of the given returned time stamps in the API's schema for fields giving that, i.e. messages sent, joined/creation account times and etc.

How will a bot developer code it?

Since the Discord Web API works off of serialized JSON data, we can use the already given schema with how ApplicationCommandOption is registered in an HTTP request for creating or updating an application command.

{
    "name": "date",
    "description": "This is the name of my option.",
    "type": 11,
    "required": false
}

(11 is a pseudo-given type for the option as an example.)

How would this look?

I believe that already adopting the given calendar system we have for searching up messages would make it easy and more intuitive with users trying to use this in a bot's suite of commands. Please note that this example I am giving does not consider the new "editable pills" design that Mason has mentioned as of the Discord Developers Stage event.
(My photoshop skills are bad I'm sorry)

Credits to LordOfPolls#1010 for the bot shown in this screenshot.

[advaith1]

• Date argument type for slash commands #3303

[i0bs]

Looks like I was too late :(