General Discussion (#1) - (HubBot) is disconnecting: received bi-directional (#29) - Message List

(HubBot) is disconnecting: received bi-directional

(HubBot) is disconnecting: received bi-directional packet 0x07 from server (ordered to DC).

i get this all the time after a few minutes.

and its already on vip and sysop, any other thing i should look for?

  • Message #82

    If you get it each time after a few minutes then I think the bot is getting kicked because it isn't returning a proper security checksum. Make sure the bot logs into sysop successfuly when it logs on - use *listmoderator to check.

    Also, when it disconnects, you should check the *log to see why it has been kicked. The reason stated will help in determining the cause.

    • Message #83

      im getting this on *log

      says reliable packet lost to bot-name kickout delay exceeded bot-name

      • Message #84

        Hm, we have this problem aswell but for us the bots run fine for days.

        Is there a custom bot you run on TWCore (that might be sending lots of PMs or other "reliable" actions) ?

  • Message #85

    Proz, if you still have the problem - would you mind sending me your server.ini and subbil.ini (if you can't / won't post it here email me at maverick@spamless@dedicational.com)?

    It would give me a chance of finally solving this known bug in TWCore.

    • Message #86

      Sent you the email with the 2 files, i have a local server where i test the bots first, also, i noticed it was happening more constantly if there is lag present on the actual zone.

      • Message #87

        Anything new on this issue?

        • Message #88

          Anything new on this issue?

          i was wondering if there was anything new…

          • Message #89

            Nope sorry, nothing new yet. I haven't had time to investigate into your issue yet.

        • Message #90

          Are you running the latest version from core? Did you change any core settings? What connection type are you using? I'm almost positive it's a cfg error.

          • Message #91

            i was when i started this thread, don't know how much it has changed since then. ill update the core today, i don't think i changed any core setting.

            what do u mean connection type? local / remote ?

            i could probably post the cfg.

            • Message #92

              i updated to the latest core, and it's still happening.

              if it's an ini problem any idea where the problem could be?

              i sent my ini files to maverick.

              • Message #98

                anything new on this issue since last time I replied?