Currently TimedEvents.In appears to only accept integers, it would be preferable if it also accepted floating point values. For example !in 1.5h would equate to `!in 1h30m'. In the case of weird rounding situations, I'd go with the closest, rather than decimally rounding the float value before conversion. Seems easier to implement and more obvious to me.
Currently TimedEvents.In appears to only accept integers, it would be preferable if it also accepted floating point values. For example
!in 1.5h
would equate to `!in 1h30m'. In the case of weird rounding situations, I'd go with the closest, rather than decimally rounding the float value before conversion. Seems easier to implement and more obvious to me.