tagban / invigoration Goto Github PK

Apparently there is a defect in the connection process. I had named BNLS AND 
BNET server the same item, so it was borking the login process. Working on a 
fix for 1.2.5

Goal is to get War3x and D2x connections working again. Currently, I can make 
the bot think its happening, but it doesn't really send the Expansion key. So 
this is a goal.

At least 3 packets need to be recoded:
 - Clan Handling (Accept/Decline invites, perhaps Clan Creation)
 - Email Registration (Sending email to Battle.net to register account, currently the Config option doesn't even save to the config file due to lack of the packet working)
 - BNLS Connectivity. - Currently, the bot sends ALL data thru BNLS. The goal is to eventually limit what BNLS sees and possibly allow hashing down the road. One thing we were thinking about doing was using BNCS, however BNCS isn't updated and could become incompatible should they change anything with existing Battle.net connections.

As above, should be fixed in next version. its not a functionality defect, so 
its a low priority.

When using this message, it doesn't update after the first send. Basically just 
needs to be set to pull new uptime # after each send.

- Tagban

When putting in a larger number, the bot crashes with run-time error.