Mute/Ban/Reminder times not being parsed correctly
Incident Report for Fire
Resolved
I had just recently been made aware of an issue with commands that use Fire's parseTime function (reminders & temp mutes/bans) not parsing times correctly if the time was at the start of the reason. This would result in the time being parsed as 0 minutes which resulted in errors while creating reminders (saying you can't set reminders for less than 2 minutes) and permanent mutes/bans rather than temporary.
This issue has been resolved as of 13:32 UTC and Fire should start parsing times correctly.

Note: If the time was NOT at the start of the reason, they were unaffected by this bug and therefore were being parsed correctly
Posted Feb 16, 2021 - 13:34 UTC