Monday, September 2, 2024
[00:03:02]
Excalibur
*** <Boole@Epiknet> a mis le mode #eggdrop +l 20
[00:05:15]
Excalibur
-//- <uto@Epiknet> a quitté
[00:06:03]
Excalibur
*** <Boole@Epiknet> a mis le mode #eggdrop +l 19
[00:28:02]
Excalibur
*** <Boole@Epiknet> a mis le mode #eggdrop +l 20
[02:50:33]
*
[Guru]
set mode +l 17
[04:44:03]
*
James
joined #eggdrop
[04:44:42]
*
[Guru]
set mode +l 8
[04:45:05]
*
[Guru]
set mode +o Excalibur
[04:45:05]
*
Excalibur
joined #eggdrop
[04:45:30]
*
bds.zeolia.chat
set mode +o CrazyCat
[04:45:30]
*
bds.zeolia.chat
set mode +l 17
[04:45:31]
* Netsplit healed 9 users rejoined
Click to toggle user list
takeover
worm
ZarTek
ced117
Laurent
CrazyCat
PeGaSuS
Maria
Jarvis
[04:45:47]
*
[Guru]
set mode +l 18
[08:50:49]
*
[Guru]
set mode +h BdS
[08:50:49]
*
BdS
joined #eggdrop
[08:51:29]
*
[Guru]
set mode +l 19
[10:09:00]
Excalibur
-//- <Xizor@Epiknet> a quitté (Ping timeout: 181 seconds)
[10:09:02]
Excalibur
*** <Boole@Epiknet> a mis le mode #eggdrop +l 19
[10:20:02]
Excalibur
*** <Boole@Epiknet> a mis le mode #eggdrop +l 20
[10:40:38]
*
[Guru]
joined #eggdrop
[10:40:38]
*
[Guru]
set mode +lo 5 [Guru]
[10:40:39]
*
Excalibur
set mode -l
[10:40:53]
*
[Guru]
set mode +l 19
[10:51:02]
*
[Guru]
set mode +h Amand
[10:51:02]
*
Amand
joined #eggdrop
[10:51:22]
*
[Guru]
set mode +l 20
[11:52:52]
Excalibur
<MenzAgitat@Epiknet> yop
[11:58:34]
Excalibur
-//- <ced117@Epiknet> a quitté (Ping timeout: 180 seconds)
[14:58:38]
PeGaSuS
Q: how do I make a proc to wait like 5s between each `putserv`?
[14:59:09]
CrazyCat
To slow the messages ? Use puthelp :)
[14:59:55]
PeGaSuS
I really need a specific time between the 1st and second message
[15:00:51]
CrazyCat
Ok, so you'll have to create your own queue and add a timer to read it
[15:01:11]
PeGaSuS
sometimes I wish TCL had a `sleep` function
[15:02:10]
CrazyCat
Or if it's only for specific message, do a putserv of the first and for the next one: utimer 5 [list {putserv ......}]
[15:02:43]
PeGaSuS
yeah, it's only for one message
[15:04:19]
PeGaSuS
does `utimer 5 [list {putserv "..."; putserv "..."}]` works also?
[15:10:15]
CrazyCat
utimer will execute everything in the list in the same time
[15:11:48]
PeGaSuS
right. so, those two messages will be sent at once
[15:21:38]
PeGaSuS
after is blocking, iirc?
[15:22:03]
PeGaSuS
I was just fixing some script logic inside the chansec script
[15:22:21]
PeGaSuS
looks like this as *final* product
[15:28:29]
CrazyCat
PeGaSuS: if I were in your shoes, that's not the way I made it
[15:29:15]
CrazyCat
utimer 5 [list resend_code $nick $uhost $hand ""]
[15:29:45]
PeGaSuS
I can do it that way right?
[15:29:47]
CrazyCat
Why having twice the same putserv when you can use the same proc ?
[15:31:31]
PeGaSuS
I guess I like to have each function doing it's own job
[15:31:44]
PeGaSuS
resend only resends on request
[15:31:59]
CrazyCat
So you have a proc to (re)send the password
[15:32:38]
PeGaSuS
it's to resend only
[15:33:21]
CrazyCat
What is exactly the difference between send and resend ? Check of +Z ? When sending, you know the user can't be +Z
[15:33:32]
PeGaSuS
somehow I hate having to call procs from inside a proc that *may* call another proc
[15:33:36]
CrazyCat
So the proc works in send and resend
[15:34:33]
CrazyCat
I hate having twice the same code because if I've to change something, I've 2 place where it must be changed
[15:34:44]
PeGaSuS
the user must be +Z when resending
[15:35:29]
CrazyCat
Sorry: when sending, you know he's +Z
[15:35:45]
CrazyCat
As the first thing you do is to add the +Z
[15:36:05]
CrazyCat
BTW, do the code as you like it, it was just an advice
[15:36:46]
CrazyCat
(not sure the list will work as expected)
[15:40:09]
PeGaSuS
right. I was changing the code a bit and now I set +Z before sending the messages
[15:40:14]
*
[Guru]
set mode +l 19
[15:40:22]
PeGaSuS
it used to be after the messages have been sent
[15:42:12]
PeGaSuS
the "" at the end of list is to cheat on the number of args?
[15:42:32]
PeGaSuS
since resend_code needs 4 args?
[15:45:07]
CrazyCat
Yes, sending an empty string as argument
[15:49:36]
CrazyCat
hmmmm, I noticed a little bug in your resend_code proc
[15:50:15]
CrazyCat
You don't manage when an user is not in your userlist and will do a /msg botnick resend
[15:52:34]
CrazyCat
The user will receive a msg as he's already verified
[15:52:45]
CrazyCat
But in fact, he's unknown
[16:10:37]
*
[Guru]
set mode +l 18
[16:43:05]
PeGaSuS
I do check if he's +Z
[16:43:14]
PeGaSuS
if it's not, then it is verified
[16:43:35]
PeGaSuS
users already added to the bot manually aren't verified at all
[17:07:00]
*
[Guru]
set mode +h Amand
[17:07:00]
*
Amand
joined #eggdrop
[17:07:13]
*
[Guru]
set mode +l 19
[18:12:32]
Excalibur
-//- <Lucie@Epiknet> a quitté (Ping timeout: 181 seconds)
[18:12:49]
*
[Guru]
set mode +l 18
[18:13:03]
Excalibur
*** <Boole@Epiknet> a mis le mode #eggdrop +l 19
[18:13:21]
Excalibur
-//- <Clara_@Libera> a quitté (Ping timeout: 246 seconds)
[18:15:25]
Excalibur
--> Clara_!~Clara@user/Clara/x-5934776 entre sur #eggdrop-fr@Libera
[18:16:04]
Excalibur
*** <Boole@Epiknet> a mis le mode #eggdrop +l 20
[21:14:06]
Excalibur
*** <Boole@Epiknet> a mis le mode #eggdrop +l 21
[21:31:40]
Excalibur
-//- <PeGaSuS@Epiknet> a quitté (Quit:: ASCII a stupid question, get a stupid ANSI!)
[21:32:00]
*
[Guru]
set mode +l 17
[21:32:05]
Excalibur
*** <Boole@Epiknet> a mis le mode #eggdrop +l 20
[21:33:13]
Excalibur
-//- <uto@Epiknet> a quitté (Ping timeout: 180 seconds)
[21:33:23]
*
PeGaSuS
joined #eggdrop
[21:34:09]
*
[Guru]
set mode +l 18
[23:05:48]
Excalibur
-//- <James@Epiknet> a quitté (Read error)
[23:06:02]
Excalibur
*** <Boole@Epiknet> a mis le mode #eggdrop +l 19
[23:06:23]
*
[Guru]
set mode +l 17
[23:11:18]
*
James
joined #eggdrop
[23:11:37]
*
[Guru]
set mode +l 18
[23:12:02]
Excalibur
*** <Boole@Epiknet> a mis le mode #eggdrop +l 20
