A long time honorbuddy user, I came across WRobot in a search for a bot that works on private servers.  I set up my own personal (non public) server and tested WRobot out, I find that the profiles are quite quirky (the ones that I have tested, and haven't had much success with anything close to AFK, which may be my noobness or problems with the profiles themselves).  I decided to purchase WRobot anyhow as I am very intrigued by it and the best part of botting is making the bot do what you want it to do.

I have been searching around and I am not finding much in the way of documentation.  I am wondering if there is any actual documentation (for writing profiles and stuff), other than the basic tutorials / videos that show introductory creation of profiles.

*Currently* what I am looking for is simply information on 'if' parameters in the easy profiles creator and what "Wowclass" is used for in the xml file.  I am trying to detect if a quest has already been completed (possibly in a previous run/session), and if the quest is for a specific class (ie hunter, shaman, etc).  Of course this is just the beginning, I just started with this today, so I am sure the more I play with it the more questions I will come across.

That said, I am fully capable of digging through current profiles as examples, and hunt and dig through the forums if necessary, but what I am really wondering is if there is any documentation available for developers that want to create this stuff or is it just bits and pieces here and there and muddle your way through it?

Thanks

netlynx

http://ilspy.net/

Decompile wrobot dll files and look inside. You will get all posible functions etc. To edit use visual studio ( bloaty laggy stuff ) or use notepad++ with plugin cs script.

13 minutes ago, forerun said:

http://ilspy.net/

Decompile wrobot dll files and look inside. You will get all posible functions etc. To edit use visual studio ( bloaty laggy stuff ) or use notepad++ with plugin cs script.

That's a good suggestion (probably would have eventually thought of after I started getting extremely frustrated during a dig).  I was really hoping for some good (or at least attempted documentation).  That said the 'current detection' stuff that I was looking for from the original post was answered (along with a few hints for other things I have not yet gotten to) here: 

I really am looking forward to this, was just hoping that there was some better documentation.  Maybe down the road I will piece something together once I get a better grip on how it all works.

Thanks again for the suggestion, that's a great tip!

/netlynx