#41 !ALARM trunkates users message - and some suggestions

[Luiz Castelo-Branco]

Only displays 1st word of message to the user who triggers it

<BotUser> DB ALARM s3 test 1 2 3
... 3" later ...
-DB- ALARMCLOCK by BotUser!~lcb@computer.home: test

<BotUser> DB ALARMCLOCK s13 test1 test2 test3
<DB> BotUser: alarm clock set to go off in 0 minutes, 13 secs.
... 13" later ... 
-DB- ALARMCLOCK by BotUser!~lcb@computer.home: test1

While here...
.1 - DEACTIVATING: Command to null ALARM in progress?
.2 - Any way of directing the ALARM/message to CHAN or USER?
.3 - Since this function is not accepting in the same issued command any combination of secs/mins/hrs/days might be better having the channel message according to the asked type of time, i.e. "alarm clock set to go off in 13 secs" instead of "alarm clock set to go off in 0 minutes, 13 secs.".
.4 - More human talk friendly - Having 's' 'm' 'h' 'd' after the time periods instead of before? Better, having alias of 'seconds', 'minutes', 'hours', 'days'?
.5 - (just noticed this one) Lower this command for users level 1 instead of 2?

Obs.: I know these are kind of feature requests; I'm having them here in case the dev needs to have the idea in mind while fixing the command. Also, I don't really want to have any isolated/new feature requests defocusing devs from/while fixing bugs which makes the bot erratic/unreliable. So if any of it gives too much work and not implicitly to the fixing process just leave it for other time and we'll put it as feature requests.

[onefang]

About point .2, that would be covered by a future "clean up the output destinations by making things generic" pass I seem to remember planning.