Author Topic: !timers suggestions: alts, public timers in tell, different default levels (Read 9779 times)

Hyde · « **on:** August 08, 2008, 07:13:11 pm »

Ok so if any of this has happened since BeBot 4.0 (or was already possible in 4.0 and I missed it) I won't have seen it. Sorry if its a dupe. But ...

1) a) It would be really handy to have !timers that checked !alts just like flex security can. So that when I have a personal timer set from one toon, then log a different toon, I can see the timers I set on the first toon via !timers.

... 1) b) It could even check to see which alts were online and send messages to those alts instead of the original toon. If I'm on -2- alts it could buzz both of them. Would be extremely handy for dual-logged situations and for handling perk resets and such.

2) I have the bot set up so that timers set in orgchat are public and in tells are private. I would like to be able to check my orgs bot's public timers (ie, those times I set via !timer in the org channel) with a tell command. Like "/tell bot !timerspublic").

3) Similar to #2 I'd like to be able to -set- a public timer via tells (like "/tell bot !timerpublic {spamlevel} {time} {description}").

note: I called it timerspublic and timepublic because it would seem easier to create a new command name rather than modifying the parameters passed to the !timer command since more logic around whether the parameter was a spamlevel (like lowspam, standard, etc) or a class (public or private). I don't care how the actual implementation works.

4) I'd like to be able to have different default spam levels for private and public timers. So that I can keep the org channel timers as "lowspam" but private tells as "standard". People liked the spammy private timers ... but it was way too much spam on orgchat. I know they can designate the spamlevel manually (well, if I had the newer !timer module) but most are barely clued in enough about !timer to send them in tells.

Alreadythere · « **Reply #1 on:** August 08, 2008, 08:49:53 pm »

Nice ideas, I'll look into them (and no, pretty sure none of those ideas is implemented).

Hyde · « **Reply #2 on:** August 09, 2008, 03:12:32 am »

Cool. I'm doing bot upgrades to 5.x in a month or so. Let me know (just post here, I'll subscribe to it) if you have something you want tested. If you're getting close to some of these I might hold off on upgrading while you're looking into it.

Alreadythere · « **Reply #3 on:** August 24, 2008, 10:58:04 am »

Quote from: Hyde on August 08, 2008, 07:13:11 pm

2) I have the bot set up so that timers set in orgchat are public and in tells are private. I would like to be able to check my orgs bot's public timers (ie, those times I set via !timer in the org channel) with a tell command. Like "/tell bot !timerspublic").

3) Similar to #2 I'd like to be able to -set- a public timer via tells (like "/tell bot !timerpublic {spamlevel} {time} {description}").

note: I called it timerspublic and timepublic because it would seem easier to create a new command name rather than modifying the parameters passed to the !timer command since more logic around whether the parameter was a spamlevel (like lowspam, standard, etc) or a class (public or private). I don't care how the actual implementation works.

Both implemented in trunk now. The command is !ptimer, with aliases of !ptimers, !publictimer or !publictimers.

As I don't got that much time anymore to work on the bot and I don't have any 0.4 bots running anymore, I won't be backporting it to 0.4.
On the other hand we should be able to release 0.6 soon. And 0.5.x seems pretty stable.

Hyde · « **Reply #4 on:** August 24, 2008, 07:12:46 pm »

Quote from: Alreadythere on August 24, 2008, 10:58:04 am

As I don't got that much time anymore to work on the bot and I don't have any 0.4 bots running anymore, I won't be backporting it to 0.4.
On the other hand we should be able to release 0.6 soon. And 0.5.x seems pretty stable.

Awesome. No worries about backporting. Thanks

Alreadythere · « **Reply #5 on:** October 11, 2008, 10:19:46 pm »

Quote from: Hyde on August 08, 2008, 07:13:11 pm

4) I'd like to be able to have different default spam levels for private and public timers. So that I can keep the org channel timers as "lowspam" but private tells as "standard". People liked the spammy private timers ... but it was way too much spam on orgchat. I know they can designate the spamlevel manually (well, if I had the newer !timer module) but most are barely clued in enough about !timer to send them in tells.

Implemented. Well, almost - added class settings for timer classes, which means the definition isn't static anymore, or linked to one normal setting. Just missing a neat UI to change all the stuff, next on my list.

Alts system will be integrated too, will do that after the UI.