Skript TimeSpan Parsing

[EquipableMC]

Suggestion

Since you can do and allow "1 day" to be parsed as a timespan, you should be able to do 1d as well.

Why?

This should be possible because of many reasons. People always shorthand 1d to be 1 day, so it would make sense if you could do 1 day.

Other

Please mark this as up to debate as I want to see other peoples opinion on this.

Agreement

• [X] I have read the guidelines above and affirm I am following them with this suggestion.

[Pikachu920]

I think this would make sense to add for the command parse context, but i don't think you should be allowed to use the shorthand in code (set {_one day} to 1d).

[Moderocky]

I think this would make sense to add for the command parse context, but i don't think you should be allowed to use the shorthand in code (set {_one day} to 1d).

Especially since the d suffix is commonly used to denote a double (as I think it used to be in Minecraft's printed NBT)

[EquipableMC]

I mainly just wanted it for command parse context, I can see the issues with variables and all that other stuff that does not have to do with command parse

[AyhamAl-Ali]

Currently this is supported using clock format timespan (HH:MM:SS[.ms])

command /test5 <timespan>:
	trigger:
		broadcast arg-1

Though, this is still a valid suggestion. Suggested format 1y2M3w4d5h7m7s8ms (month maybe M or mo) only in command parse context

[Efnilite]

merged in #7001