egghelp/eggheads community

pub binding bug?

2005-01-01T13:27:45-04:00

well, in such case I can see no other possible explanation than somehow changed shared libs - Tcl or otherwise

you can try to compile & install Tcl in your home dir and recompile & link the bot against it, not the system-wide libs

Statistics: Posted by demond — Sat Jan 01, 2005 1:27 pm

pub binding bug?

2005-01-01T12:59:48-04:00

i didnt change anything in none of each eggdrop/* trees.
no new binaries, no new scripts, nothing.

just for clarity too..the two bots i could see this behaviour are on two different machines with different linux distributions, different scripts installed and they are even different versions.

it really looks like a year-2005-bug or sth o.O

Statistics: Posted by puffi — Sat Jan 01, 2005 12:59 pm

pub binding bug?

2005-01-01T12:56:49-04:00

just for clarity: you haven't changed anything from 2 days ago - you haven't recompiled the bot and installed the new version and you haven't modified your scripts - yet the scripts won't work now as they worked 2 days ago, on the same bot?

Statistics: Posted by demond — Sat Jan 01, 2005 12:56 pm

pub binding bug?

2005-01-01T12:39:59-04:00

exactly. it doesnt matter if i replace the ${thisbot(cmdchar)}topic with .topic it shows the same behaviour.

i found this behaviour on 2 eggdrops with different scripts now, one running 6.16 and one running 6.17

i'm fairly sure 2 days ago the scripts worked just fine

Statistics: Posted by puffi — Sat Jan 01, 2005 12:39 pm

pub binding bug?

2005-01-01T12:21:11-04:00

so,

Code:

bind pub -|- ${thisbot(cmdchar)}topic myown:pub_topic

is triggered by ".topic" and is not triggered by ".topic foo bar", assuming $thisbot(cmdchar) is "."?

Statistics: Posted by demond — Sat Jan 01, 2005 12:21 pm

pub binding bug?

2005-01-01T12:12:19-04:00

doing

.topic
in a channal triggers it.

.topic testargone andtwo
doesnt

the binding itself is okay and did work without any problems. additionally, i didnt change any code...and few days ago .topic testargs did work fine

Statistics: Posted by puffi — Sat Jan 01, 2005 12:12 pm

pub binding bug?

2005-01-01T11:44:40-04:00

try ${thisbot(cmdchar)}topic

Statistics: Posted by demond — Sat Jan 01, 2005 11:44 am

pub binding bug?

2005-01-01T11:05:36-04:00

Code:

bind pub -|- $thisbot(cmdchar)topic myown:pub_topicproc myown:pub_topic {n uh h c a} {  putlog "pub topic n: $n uh: $uh h: $h c: $c a: $a"  return 1}

the point simply is, that the scripts worked all before, like for 2 years or sth.

Statistics: Posted by puffi — Sat Jan 01, 2005 11:05 am

pub binding bug?

2005-01-01T10:47:20-04:00

the very first idea that comes to mind would naturally and obviously be you post your script here

Statistics: Posted by demond — Sat Jan 01, 2005 10:47 am

pub binding bug?

2005-01-01T10:40:05-04:00

Hi, i know it sounds weird but as of 2005 all my pub-bindings work slightly different on my 1.6.17

pub bindings simply dont trigger when i use one or more arguments.

for example, i got a topic-script that tells the current topic with some extra information when a user writes .topic
now for ops of the channel (for real ops, not those who have the flag in the eggdrop, so the bind is for -|-) may edit the topic with + or -
all those bindings dont even work. i put a putlog-line to the very first line of the proc but the proc doesnt even get called.

the same behaviour for all other pub bindings

any ideas?

Statistics: Posted by puffi — Sat Jan 01, 2005 10:40 am