user guide document

[lokyse]

Any document to guide user how to use this library?

[brebernjak]

+1, please consider doing so as node-dota2 is now deprecated and this seems to be the most up to date client out there.

[paralin]

If someone wants to contribute one, I'll merge it.

[UnixCr3wR0x]

@paralin atleast at low level docs then we can try we actually cant use it

[paralin]

Basic overview:

1. SetPlaying(true)
2. Wait a moment (like 0.5 second)
3. SayHello()
4. Wait for the connection status event to indicate you have a gc session (IsReady() = true)
5. Send SayHello every few seconds until you get a session
6. Once you have IsReady() = true send CreateLobby.

I don't want to give too much detail as I'm not interested in being responsible for a flood of low-quality bots.

[AngelloFD]

Any update on this? Is anyone working on a documentation or at least have a way to start a project up with the library correctly?

[voltageeee]

Any update on this? Is anyone working on a documentation or at least have a way to start a project up with the library correctly?

sorry to re-open this thread, but i guess some people will need help with this library from time to time.

as far as i see, everyone wants to create a lobby, so i will go through it in details (as much as i can)

a little not for those, who don't know anything about how dota, gc and steam exchange dota (honestly, i'm quiet puzzled too, but i think i understand the basics)
protobufs is a protocol developed by google and used by valve to exchange data before servers, clients and gc (game coordinator). protobuf messages are constructed from .proto files, and those are being constantly updated in the steam-db repo (which is a module for go-dota2)

first of all, you'd need to update protobufs and generated api code since it is, for the most part, outdated
look into go-dota2/generator/update_protos.bash, as it's responsible for the generation of protobufs. it won't work however, as these packages require a parameter "go_package" to be generated into go code. you can write a simple script to go over each .proto file and add at the head of each file, or go over all the protos manually :/

after you've generated the protos, go into the apigen folder and run apigen.bash (if you're on windows - well, help you god).
it will re-generate such files as client_generated.go, events_generated.go and so on to properly function with the new protobuf versions. it will spit out some errors like:
unable to find proto for: k_EMsgClientToGCOverworldDevResetPath
in this case, go to apigen/msg_overrides.go and add another message override for the problematic enum.

after you've generated the code, you'll need to update go-steam to provide it with new steam cm server list. you can either try and grab it yourself you steamre/steamkit (a few lines of c# will do the trick) or grab it from here :)
go-steam/servers.go, replace all the servers with those:
"146.66.155.38:27017",
"155.133.248.38:27017",
"162.254.198.44:27017",
"162.254.197.39:27017",
"155.133.226.76:27017",

finally, you are ready to write your dota client.
we will go through creating a lobby.

first of all, we will need to initialize or steam client (e.g. login into our bot account)

func main() { loginInfo := &steam.LogOnDetails(){ Username: "username", Password: "password", } }

then, we will need to connect to the steam network and log in:

(don't mind the infinite time.Sleep, i just like to overthink of stuff)

so, basically, we created a loop that gets all the new events related to the steam network from the events channel, so we can handle those events as we see fit.

first, we need to handle steam.ConnectedEvent. we do that by logging in to our account and going on.

after we get steam.LoggedOnEvent (that singals that we have logged on successfully), we can proceed to working with the dota client. (don't mind the setpersonastate, just wanted to make sure it works)

in the seperate goroutine, we call createDotaLobby function after waiting for 10 seconds before steam client fully initializes (unnecessary)

there is not much to explain, as we're just initializing the dota2 logger (without it, segfault will happen cause dota2 clients likes to log stuff), initializing the dota2 client itself with our steam client and our dota2 logger, inform steam network that we are now playing the game and finally, we inform the dota2 server that our connection state must be initialized now by SayHello() function.

after that, we are ready to proceed with creating the lobby object.

here, we just declare a bunch of variables and use them in CreateLobby function when creating a lobby. it's that simple.

after that, we are ready to.. wait for another 3 seconds before steam processes our request and invite the members. if you did everything correctly, this is what you will end up with:

by the way, I made a fork of go-dota2 with updated protobufs (as of dota 7.38b).
until (and if) it will be merged into the main repo of go-dota2, feel free to use it as you see fit.

the original library is now updated and will work with the newest dota version!
thanks to paralin.

will be writing a documentation for this library if I will have time

[paralin]

the IP address list is now up to date, and you don't need to regen the protos anymore (they are also up to date). :)

[secoldPrivate]

How safe is something like this to use, in terms of VACBANs, (if we're just automating joining parties etc.)

also; Can i use this to download replays by getting the salt etc given a matchID?

[paralin]

I have never heard of anyone getting a VAC ban without connecting to a game server. If you're just interacting with the game coordinator you may be IP banned, steam account banned, or rate limited if abusing the privilege. But if you're just doing normal non abusive things at a reasonable rate it shouldn't be a problem.

[secoldPrivate]

Any advice/note on what the actual rate limits are?
I'm in need to download a fairly large amount of replays, what is possible with a single steam account on a single IP?
How do large players like dotabuff and Stratz do it?

Also: is there an IP based lock, for multiple steam accounts connecting to the GC? ie; I have one EC2 instance with 20 of these, each with a different steam account, querying ~100 games a day?