Editing Relay
From Bebot Wiki 2
Jump to navigationJump to searchWarning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 18: | Line 18: | ||
'''2.1 Using tells''' | '''2.1 Using tells''' | ||
− | PROS: | + | PROS: easy setup, no relay-bot needed |
− | + | CONS: Only works with 2 bots, possibly illegal, tells might be dropped by the server if coming in to fast1) | |
− | CONS: Only works with 2 bots, possibly | ||
Using tells as relay is discouraged nowadays (and you even run the risk of having your bots banned by funcom without warning), but we will describe it shortly nonetheless. Use at your own risk! | Using tells as relay is discouraged nowadays (and you even run the risk of having your bots banned by funcom without warning), but we will describe it shortly nonetheless. Use at your own risk! | ||
− | Assuming you have two bots “bot1” and “bot2”, you start by allowing each bot to relay to each other. You could do a “!member add bot2” on bot1 and vice versa, but the member-list of org-bots might get wiped during roster-updates. | + | Assuming you have two bots “bot1” and “bot2”, you start by allowing each bot to relay to each other. You could do a “!member add bot2” on bot1 and vice versa, but the member-list of org-bots might get wiped during roster-updates. Refer to section 2.3.2 as to how to create a new security group named “relaybots” with SUPERADMIN level on both bots and then make them member on the other bot's group. |
If you've done this, you let bot1 relay to bot2: | If you've done this, you let bot1 relay to bot2: | ||
Line 52: | Line 51: | ||
'''2.2 Using IRC''' | '''2.2 Using IRC''' | ||
− | PROS: scales well, no relay-bot needed, | + | PROS: scales well, no relay-bot needed, easy setup, allows linking between different game-servers and even games |
− | + | CONS: increases latency, order of messages not guaranteed, item-references will be broken, possibly insecure, doesn't look as nice as the other links | |
− | CONS: increases latency, order of messages not guaranteed, item- | ||
Before you start, please acknowledge that relaying via IRC is considered deprecated, yet it will still work. | Before you start, please acknowledge that relaying via IRC is considered deprecated, yet it will still work. | ||
Line 74: | Line 72: | ||
'''2.3 Using WebSocket''' | '''2.3 Using WebSocket''' | ||
− | PROS: scales up to | + | PROS: scales up to 1000 bots, nice speed, possible sharing of online-lists if all bots are using the same protocol |
− | + | CONS: Needs access to a highway websocket | |
− | CONS: Needs access to a highway websocket | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | This is a compatible option available into most recent bots (Bebot, Tyrbot, Nadybot). | |
− | |||
'''2.4 Using a private channel''' | '''2.4 Using a private channel''' | ||
− | PROS: scales up to | + | PROS: scales up to 100 bots, good speed, possible sharing of online-lists if all bots are using the same DB or !gcr/c |
− | + | CONS: Needs a dedicated relay-bot | |
− | CONS: Needs a dedicated relay-bot | ||
The fastest and most flexible solution is relaying via a private group. All bots you want to connect have to join the same private group and exchange messages. For this to work, we need a new type of bot, a relay-bot, which has the job of creating the private group and inviting all other bots into this group whenever necessary. The org/raid-bots on the other hand are configured much like a tell-relay. | The fastest and most flexible solution is relaying via a private group. All bots you want to connect have to join the same private group and exchange messages. For this to work, we need a new type of bot, a relay-bot, which has the job of creating the private group and inviting all other bots into this group whenever necessary. The org/raid-bots on the other hand are configured much like a tell-relay. | ||
Line 272: | Line 233: | ||
'''2.4.4.2 At least one bot not using the same DB''' | '''2.4.4.2 At least one bot not using the same DB''' | ||
− | Starting from 0.6.3, the online-list of linked bots are automatically syncronized within !gcr protocol (not within !agcr), but all bots have to run at least 0.6.3 or higher for this to work. When you meet these requirements, proceed to set OtherBots as described in 2. | + | Starting from 0.6.3, the online-list of linked bots are automatically syncronized within !gcr protocol (not within !agcr), but all bots have to run at least 0.6.3 or higher for this to work. When you meet these requirements, proceed to set OtherBots as described in 2.3.4.1. |
For other bots than Bebot, like Tyr or Buda/Nad, they have their own particular settings, so you have to read their documentation : | For other bots than Bebot, like Tyr or Buda/Nad, they have their own particular settings, so you have to read their documentation : | ||
Line 290: | Line 251: | ||
PROS: ok speed (2s delay max), sharing of online-lists, no relay-bot needed | PROS: ok speed (2s delay max), sharing of online-lists, no relay-bot needed | ||
− | |||
CONS: All bots need to be using the same database | CONS: All bots need to be using the same database | ||
Line 296: | Line 256: | ||
Keep in mind that this setup only works if all your bots are using the same database. It's can't work elsewise. | Keep in mind that this setup only works if all your bots are using the same database. It's can't work elsewise. | ||
− | First, make sure to grant each of the bots involved in your network access to each other (either by using “!member add botX” or creating a special security group for this as described in 2. | + | First, make sure to grant each of the bots involved in your network access to each other (either by using “!member add botX” or creating a special security group for this as described in 2.3.2. Now do the following (assuming there are three bots, named bot1, bot2 and bot3): |
/tell bot1 !set Relay StrictNameCheck On | /tell bot1 !set Relay StrictNameCheck On | ||
Line 331: | Line 291: | ||
'''4. Extension''' | '''4. Extension''' | ||
− | PROS : can connect to more than one relay | + | PROS : can connect to more than one relay CONS : uses !agcr protocol without online list sharing. |
− | |||
− | CONS : uses !agcr protocol without online list sharing | ||
You may have to connect your bot to more than one relay channel, several networks at the same time. | You may have to connect your bot to more than one relay channel, several networks at the same time. | ||
Line 341: | Line 299: | ||
Then you'll have upto five "Hrelay" (HRelay1, HRelay2, HRelay3, HRelay4 and HRelay5) available in the !settings menu. | Then you'll have upto five "Hrelay" (HRelay1, HRelay2, HRelay3, HRelay4 and HRelay5) available in the !settings menu. | ||
You can edit any by its number, for example with number 1 you do : | You can edit any by its number, for example with number 1 you do : | ||
− | + | !settings HRelay1 | |
It's then up to you to setup on the same model than described upper. | It's then up to you to setup on the same model than described upper. | ||
Usually you'd use Channel mode, as Tells will be risky with many bots, & DB mode quite unusable for bots hosted separately. | Usually you'd use Channel mode, as Tells will be risky with many bots, & DB mode quite unusable for bots hosted separately. |