Author Topic: relay problems (Read 21604 times)

Tichy · « **Reply #15 on:** February 23, 2008, 02:15:54 pm »

The screenshots looks ok but the copy from the log lines looks suspicious:

Quote

[Tunderrelay] Tunderrelay: .gcr [ Guest] Tunderclash: .gcr [Ascension] Chokotoff: i need an xfer

Tunderrelay is your "hub" used by Tunderclash and Tunderbash, right? Tunderrelay should never say anything in its own private group. Tunderrelay is just a bot doing nothing else than inviting Tunderbash, Tunderclash, ... .

clashbot · « **Reply #16 on:** February 23, 2008, 06:53:28 pm »

ok, so what do I need to do to fix that?

Tichy · « **Reply #17 on:** February 23, 2008, 09:44:05 pm »

Let's go step by step:

1) Tunderrelay should be a simple raidbot:
- configure to run as raid bot
- enable autoinvite for new guest/member (via Settings -> Members)
- afterwards add all you bots as guest/member
- nothing else needs to be touched!

2) The org bots config looks ok. Check that there is no $otherbot["tunder..."] in any of you bot's config files.

3) Test it. If it does not work, post log lines from Tunerrelay and one of the org bots and descrip what exactly is not working.

clashbot · « **Reply #18 on:** February 24, 2008, 02:15:56 am »

ok, done, still not working, gcr isn't even showing up on relay's log window, here is the log from relay and bash

clashbot · « **Reply #19 on:** February 24, 2008, 03:37:41 am »

wildhair guess, but would the fact that one of the bots is using a "." and the other one using a "!" for commands do anything?

Temar · « **Reply #20 on:** February 24, 2008, 06:20:27 am »

yes i think useing a dif prefix would be a problem, try useing the same

Temar · « **Reply #21 on:** February 24, 2008, 06:32:50 am »

say if your bots are useing ! and the relay is set to . it will ignore the !grc as the prefix isnt correct

Alreadythere · « **Reply #22 on:** February 24, 2008, 11:49:41 am »

As Temar said, the bots HAVE to use the same command prefix. Currently there is no way to do it differently.

You got two choices now:
1) Change the command prefix to the same on both bots or
2) Add another org bot in one of the orgs which doesn't handle anything but relaying (simply disable all other modules) but is using the same command prefix as the bot in the other org.

clashbot · « **Reply #23 on:** February 24, 2008, 11:53:58 am »

ok, case finally closed, although it was kinda hokey.... in order for me to get it to work, all bots had to have the command prefix the same, the relay and one bot were using the same prefix, the other bot was technically the backup bot (but the bot I had more control over) was using ".". changed all of them to the same prefix.

second note.

Apparently just being members of the bot wasn't enough. I still had to invite both bots to the private group of the relay. As far as tunderrelay's chat window, it's messy, but not near as messy. The relaying is working now, thanks for everyone's help as I know I've been a pain in everyone's side.

Alreadythere · « **Reply #24 on:** February 24, 2008, 05:31:42 pm »

Quote from: clashbot on February 24, 2008, 11:53:58 am

Apparently just being members of the bot wasn't enough. I still had to invite both bots to the private group of the relay.

Well yes, the idea is to use the private chat group of the relay hub for communication between the org bots. For that they do have to join the chat channels.

Temar · « **Reply #25 on:** February 24, 2008, 07:19:17 pm »

i think he means he still hasn't got autoinv working

clashbot · « **Reply #26 on:** February 25, 2008, 03:02:09 pm »

as the bots are resting on my machine that I have access to, 24/7 it's not a big deal, just means a few more steps if I have to reboot/etc. But that is not the case. But do have a question, that probably would have saved me alot of headaches in the beginning. The bot that is acting as relay in the main org is tchnically the "always on" backup bot...stipulated by a command character of ".". Is there not a way of adding a line in the relay command that that could override that command character to the default for the purpose of the gcr only, so that no matter what command character an org might be using, as far as relay is concerned it will always be "!" and thus prevent the miscommunication of the bots? I am sure there are other orgs that are using something besides the standard command code. This is even more important as I was also planning on having a raid bot join the relay in the same org, and definately don't want 2 or 3 bots all using the same command character..