Author Topic: Relay on bebot 0.6.2 (Read 5191 times)

Webby · « **on:** April 13, 2009, 04:11:47 am »

Hey all, I have tried to see if anyone has had this issue before, but have not found anything. I have worked through a lot of weird bot issues before, but this is certainly the oddest and have not found a permanent fix.

First a little background... up till the other day I was running 0.4.3 and everything was working well. I did my research and tested moving them from 0.4.3 to 0.6.2 and had everything laid out and knew everything that I needed to do for it. Once I got to updating them everything went fairly smooth (just a few little odd issues, but they were easily fixed.) There are 2 relays working off of this one bot. One is a custom module that a member in our alliance created (used for our alliance), and the other is the normal relay module (used to go between our main org and farm org). Both modules co-exist on others bots and they have no issues.

I had the relay working, everything was set so I changed it over to DB so that all the chat could be just passed over on my server. Everything was working great... then out of nowhere it stopped working. I spent several hours looking into it and I did not find anywhere on why it would work, and then just stop. Nothing in the bot logs say that any changes were made.

After looking into it a bit, and setting the relay on both bots to point to me I noticed a difference in what they were sending for !gcr. the main org was sending straight text like !gcr [CoH] Webbette: test

With the above I was getting a reply back from the bot like /tell bot !help

The farm org was sending !gcr [##relay_channel##CotH##end##] ##relay_name##Webbette:##end## ##relay_message##.. ##end##

I tried to change a ton of things (disabling relay and enabling it, shutting the bot down and replacing hte relay module, changing the relay color schemes, etc) and nothing worked for fixing it. I then renamed the folder that the main bot was hosted out of, and created another folder using the same process as before and it worked again. I thought it was fixed, but the next time that I logged on the same thing happened again, and I deleted the folder that it was hosted out of and recreated it again and it now works again. (the second time it had the same plain next without any ## in it, and nothing in the logs to say anything had changed)

Please let me know if you need more details or have questions, and I am expecting that as I sleep tonight that it will stop working again... Sorry for the long winded post, but I just want to try and give as much info as possible.

Has anyone seen this, or have a clue on what could be causing it?

Thanks!

Webby @ RK2

Alreadythere · « **Reply #1 on:** April 14, 2009, 03:24:23 pm »

I don't know what is happening, it sounds mysterious.

But if you get /tell bot !help then either is the sending bot missing the rights to execute the !gcr command or the receiving bot doesn't have the command registered. The color tags shouldn't break the command, worst they can do is create ugly output.

Webby · « **Reply #2 on:** April 15, 2009, 02:15:56 pm »

After the third time of deleting the folder and setting up the bot again, it has been ok for 2 days.

I completely does not make sense, but as long as it does not stop working again then all is well.

Webby · « **Reply #3 on:** April 17, 2009, 03:21:35 am »

OK so after a few days, I have now figured out exactly what was causing the issue with relay... I am using the slave bot module found: http://bebot.link/0-6-x-customunofficial-modules/slaves/

If I do not have this on everything works well, as soon as I enable it I get the /tell bot help from the other bot that I am relaying into. The reason that this was working as soon as I deleted and reinstalled the bot was that I did not have this as part of the install (and did not put it in immediately and just noticed tonight that I was not getting notify on some of the org members).

I am going to be looking into why this is happening now that I have the root cause, but if anyone has any thoughts on why this is happening that would be awesome!

Webby · « **Reply #4 on:** April 19, 2009, 02:50:59 am »

Any thoughts on this, or what maybe happening???

Webby · « **Reply #5 on:** April 19, 2009, 03:51:09 pm »

OK. So it looks like I finally got this working properly.

Something in adding the Slave module changes the way that relay works slightly. In the end to correct this I added the slave module to the bot/Main folder on the second bot and restarted it. Since doing that it now understands relay from the first org and all is well.

Thanks for the help and suggestions.