egghelp/eggheads community

After some experimentation i've got it. I am not sure exactly what happened or why but... the first user, (after the owner), mabus2... i had to add the flags and hostmask, and then part and rejoin before it FINALLY worked... all my other users now are being added normally and it works now... Strange...

Well that definately narrows things down, and explains why it's affecting all the scripts. Now how do we fix it :) I am noticing something new..... When I start the bot with ./eggdrop -m debates It starts up, and there are no error messages at all, HOWEVER.... it doesn't actually create a userfule (...

Yes, I recompiled it from scratch.

Ok, I did that; I changed to Mabus2 then in the console I typed .channel #Debates <(Debates> @Mabus2 Mabus 01:24 N ~Mabus@tweakin.com.ar so it saw it, however when i then typed; .match mabus2 I still get <(Debates> Mabus2 no 0 - never (nowhere) After exiting with mabus2, I typed the .channel #Debate...

Step 1, check users' hostmasks... Step 2, add/remove/update hostmasks to properly identify the users in the channel... Step 3, use .channels once again to verify that your eggdrop now recognizes them... I have a fresh clean empty userlist with just mabus in it I added mabus2 with the proper flags I...

Confirmed, this is in fact the problem. The bot does not recognize newly added users to the last seen thing. Anyone have any ideas on how this might be fixed?

Doing a quick test.....

I am finding that users with the Never on the last seen.... are not able to use the flag scripts. Users with info on the last seen >ARE< able to use it.

Whatever is causing this is related to the LAST SEEN thing.

Now how do we fix that

As far as the script is concerned, most of these are scripts which i downloaded from the egghelp file depository, most of them scripts i have been using for many years, which all suddenly stopped working well on the exact same day, the same day the shell changed. So It's not a script problem. As for...

Just to be clear... this is not a script problem.... It's something else to do with the eggdrop.... As I said earlier; This is affecting the handling of the flags on multiple scripts. All of them were working fine until the shell i was one was bought by a new company and migrated the accounts over. ...

I;d appreciate that! I've been running eggdrops since the mid 90's or so, and i've never seen anything like this. Here's an example of a short script that is having this problem. I can op myself with this, other users can't. # Op someone in the channel # Usage: !op <nick> proc pub:op {nick uhost han...

I deleted the script i just posted because it was showing with smiley faces and such from the forum. Was about to upload something else for you to try when I saw you VERY QUICKLY replied, sorry about that :) Yeah The last thing I tried a few days ago, was to create a brand new bot folder, and instal...

You might wanna release that script.. that would rock

I've got a sick bot. Out of nowhere it's developped some sort of flagitus or something. simply put, any script that is flag dependant has gone haywire. They >ALL< work on the owner nick (Mabus), but they refuse to work on any other nickname, no matter what the flags used are. It gets worse.... If I ...

You sir are a genius. Everything works great now, order has been restored to the universe.

Thanks for the updated version.

The problem persists however, tried a rehash and a full restart to no avail. I get the following message in the console;

Tcl error [incith::google::public_message]: Unknown option -urlencoding, must be: -accept, -proxyfilter, -proxyhost, -proxyport, -useragent