Implementation of parties

[m-bo-one]

• update find_proto function with EGCBaseMsg enum;
• invite to party;
• kick from party;
• respond party invite;
• leave party;
• set party leader;
• set party coach;
• update rich presence when in a party
• joining party channel (need to implement channels first)
• update docs and add usage examples

[m-bo-one]

#7

[rossengeorgiev]

Parties now work on the party branch. client.party is set when in a party.

[m-bo-one]

@rossengeorgiev, so what I need to do:

Complete this:

• update rich presence when in a party
• joining party channel (need to implement channels first)
• update docs and add usage examples

and after make new PR?
May I current PR close now?

[rossengeorgiev]

Whichever way you like. You can continue using the current PR. You will have to set the tip of your party branch to the tip of my party branch

git checkout party
git fetch https://github.com/ValvePython/dota2.git party
git reset --hard FETCH_HEAD

[rossengeorgiev]

Everything up to this point has been merged fromparty branch into master and released in v0.2.3

[m-bo-one]

Okey, I will close my pr. What did you mean 'update rich presence' ?

[rossengeorgiev]

When you join a lobby the client updates rich presence. That is the fancy text your friends see in their friend list. Hero you are playing, lobby details, etc.