More variables for {requirearg:N}#129

{requirearg:N|emoji}
{requirearg:N|date} (date/time/hour)
{requirearg:N|link} (someone already told that but yeah)

I might edit it later with more ideas :>

commenting bc I see a lot of merges sent here :3c this is going to be short(er) n sweet cus my previous yapfest got DELETED before I could post :sob:

{requirearg:n|range|1-3} ,, number given must be within the listed range (sep from below cus no one wants to type 1|2|3|4|5 for forever /lh)

{requirearg:n|strict|apples|bananas} ,, [$1] given must match one of the listed options exactly

main limits

• adding extra pipes to reqarg can be icky (for the code and / or newer users) – solved by making a sep req_ variable? or if it works as-is then slay.
• for the strict one I can’t think of any neat ways for it to work on multi-word strings (like “option a|option b”) – however I think it still does great as a one-word variable .. if you can make it work tho by all means!

main benefits:

• greatly increases ar flexibility ,, instead of making .cmd a .cmd b for every minor variation of a cmd, we can just have .cmd and not worry about any requirearg inputs deviating from the list we want. can see a tonne of combo potential with buttons and embeds as well :yum:
• VERY beneficial for utility cmds – ppl have asked to limit {requirearg:text} to items / specific items and this is a way to do it without getting hyperspecific :3c you can also add number limits for things like trade or transfer cmds
• these are based off of pre-existing mimu functions (just stricter) so hopefully they are easier to consider implementing ^^

thanks for reading x