egghelp.org community

[demond]

hey folks

as seemingly eggheads won't be releasing new bot version anytime soon (although they've patched the bug affecting xchannel almost an year ago in CVS), a need arises for somehow fixing that notorious bug via scripting

how should I do that? by intercepting .chanset and handling xchannel's long chansets writing to chanfile in the script itself? any other ideas?
_________________
connection, sharing, dcc problems? click <here>
before asking for scripting help, read <this>
use [code] tag when posting logs, code

[Sir_Fz]

You can create your own chanfile, and use a command like .xchanset instead of .chanset and .xchaninfo instead of .chaninfo.
_________________
Follow me on GitHub

- Opposing

Public Tcl scripts

[demond]

hmm, on a second thought, that's pretty much the only way to do it - since unfortunately, I simply can't have control over chanfile writing process
_________________
connection, sharing, dcc problems? click <here>
before asking for scripting help, read <this>
use [code] tag when posting logs, code

[demond]

okay folks, I've had it with those lazy eggheads

as apparently they couldn't care less about releasing a new version (it's been year and a half already since the last), I had to do something for xchannel to compensate for that long-standing cut-channel-settings bug in 1.6.17

from now on, you don't need to patch your bot in order not to lose xchannel's settings - a new version 3.5 of the script is out, with proper chanfile saving (in fact, it emulates yet-to-be-released 1.6.18 hehe)

enjoy!
_________________
connection, sharing, dcc problems? click <here>
before asking for scripting help, read <this>
use [code] tag when posting logs, code

[dusk]

Congratz demond, I'm using your script practicually on most of my bots, and still have others to install it in (somewhat 21 intotal) and actually it became a drag to rebuild en change every bot so I could use your script. I'ts a big progress, certainly for me, cause I didn't always got the result I expected when rebuilding the existing bots. Thx.

Fine job

GRTZ dusk

[Alchera]

demond, demond, demond .... There's a very old saying, "Patience is a virtue".

Seriously, this "update/new release" is beginning to get a bit long winded but, when there is only (apparently) one person working on it now I guess delays are inevitable.

* Alchera waits
_________________
Add [SOLVED] to the thread title if your issue has been.
Search | FAQ | RTM

[demond]

well, now that I managed to fix this thing w/o waiting for jolly eggheads to put their act together, maybe I should move on and make eggdrop multiserver hehe - I know they would never do that
_________________
connection, sharing, dcc problems? click <here>
before asking for scripting help, read <this>
use [code] tag when posting logs, code

[Alchera]

I have noticed when loading xchannel for the first time not one of the default settings carry across into other existing channel record(s).

I did notice that not long after it was loaded the bot left the two dynamically allocated channels it was in (after a rehash) and after re-adding them those channels inherited the default settings.

Later adding a channel dynamically I noticed it inherited none of the default settings.

Having the script setup so that the default settings are inherited by all existing channels and those dynamically added to the bot later would be a boon.
_________________
Add [SOLVED] to the thread title if your issue has been.
Search | FAQ | RTM

[demond]

I can't reproduce that on my bots

I'll look into it again when (if) someone else confirms the issue
_________________
connection, sharing, dcc problems? click <here>
before asking for scripting help, read <this>
use [code] tag when posting logs, code

[Alchera]

[demond]

xchannel detects restart (or startup) and schedules script reload after 5 seconds:

[spock]

try using the "loaded" evnt bind
_________________
photon?

[demond]

[spock]

ah.. right you are

edit: actually it does seem to work over here
bind evnt - evnt:loaded ; proc evnt:loaded t { putlog $t }
sure enough, it spits out "loaded" on ./eggdrop -n
_________________
photon?

[Alchera]