Weirdness in setting time using miltary time

In SCFG timed events, entering "0500" as an execution time sets the time to 500:00 which isn't valid. It would be nice if it at least popped up an error if it won't parse military time and the result is out of bounds.