Page 1 of 2 1 2 LastLast
Results 1 to 10 of 19

Thread: August 30 Bot Update

  1. #1
    Valve Developer
    Join Date
    Sep 2011
    Posts
    1,704

    August 30 Bot Update

    • Fixed bug that was causing default bots to not know who was near them.
    • Fixed -botworldstatetosocket_radiant and -botworldstatetosocket_dire not sending UDP data to their port properly.

  2. #2
    Basic Member
    Join Date
    Jan 2014
    Posts
    57
    Thank you very much! All of the previous patch problems are gone. But still the channeling one exist. I should confirm that when no Creep is nearby, the BoTs channel their skill properly (I saw another Pudge sample today)

  3. #3
    Quote Originally Posted by ChrisC View Post
    • Fixed -botworldstatetosocket_radiant and -botworldstatetosocket_dire not sending UDP data to their port properly.
    I still cant receive the UDP data with port properly. Anybody else tries it ? the command is :
    -botworldstatetosocket_dire <9090> -botworldstatetosocket_frames 10

  4. #4
    I'm certain that September 4th update broke 'botworldstatetosocket*' option. Can anyone bring us up to speed on this?

  5. #5
    Quote Originally Posted by ppd_reborn View Post
    I'm certain that September 4th update broke 'botworldstatetosocket*' option. Can anyone bring us up to speed on this?
    Does this mean the bots are broke?

  6. #6
    Quote Originally Posted by DreadedGhoul575 View Post
    Does this mean the bots are broke?
    I've mentioned specifically "Bot State Dumping" feature

  7. #7
    Oh ok, so I guess they're fine then? If so, that's good.

  8. #8
    Valve Developer
    Join Date
    Sep 2011
    Posts
    1,704
    The socket stuff recently got switched over to using TCP, if you're having trouble connecting.

  9. #9
    Basic Member
    Join Date
    Dec 2016
    Posts
    731
    @ChrisC What am I supposed to be seeing (if anything) in the console?

    Here are my launch Options for Dota2:
    Code:
    -novid -console -condebug -botworldstatetosocket_dire 12121 -botworldstatetosocket_frames 15
    I launch my Python server to create a lisenting socket on 127.0.0.1 port 12121 using:
    Code:
    import socket
     
    def Main():
        host = "127.0.0.1"
        port = 12121
         
        mySocket = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
        mySocket.bind((host,port))
         
        mySocket.listen(1)
        while True:
                conn, addr = mySocket.accept()
                print ("Connection from: " + str(addr))
                
                data = conn.recv(1024).decode()
                if not data:
                        break
                print ("from connected  user: " + str(data))
                 
                data = str(data).upper()
                print ("sending: " + str(data))
                conn.send(data.encode())
                 
        conn.close()
         
    if __name__ == '__main__':
        Main()
    I verify that everything worked by running "netstat -q" and seeing that 127.0.0.1:12121 is LISTENING

    I launch Dota 2, I load a saved replay (one of the TI7 games), I start watching it. I never get a connection accepted on the specified port.
    Last edited by nostrademous; 09-20-2017 at 09:03 AM.

  10. #10
    Basic Member
    Join Date
    Dec 2016
    Posts
    731
    Hm... I see. We are supposed to act as the "client" not the "server" program.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •