Yep. I totally forgot that not the whole world uses English WoW client. The fix could be pretty... straightforward, I hope. Let me look into it. Thank you. Doc is on the way. I can probably add some explanations right to the GUI too.
Amazing work. Wanted to give it try and ended up level my first pet to 25 and now making a good level 25 pets army. Btw, if some of you got the pet from last Blizzcon (Grommloc), i had to edit a file for him to work. Prostak maybe you could update your file so next SVN update doesnt remove my fix Under \Bots\Prosto_Pets\Pets, file Humanoid.cs add this line 166 : Code: //////////////////- // MISCELLANEOUS // //////////////////- ;else if(petName == "Grommloc" ) humanoid_abilities = new List<AandC>() { new AandC( "Giant's Blood", () => ! buff("Attack Boost") || hp < 0.6), // Slot 3 new AandC( "Vicious Slice" ), // Slot 1 new AandC( "Smash" ), // Slot 1 new AandC( "Clobber" ), // Slot 2 new AandC( "Mighty Charge" ), // Slot 2 new AandC( "Takedown" ), // Slot 3 } This will add support for Grommloc and i also added the logic to self buff him (which also includes a heal) Cheers! PS: I also think it would need some better details on some options.
Added, thank you! (Can't test it though, which I hate ) Will do. That's my first GUI since 1995 ("Do people even live that long?"), was a bit struggling with making absolutely necessary things first.
I don't see my reply, so I'll repeat it. I really, really would love to see the log of UI crash. And yes, it can do nasty things. Probably need to add some exception catches there.
Version 0.9.6: - text on Min Health corrected; - Humanoid/Grommlok support added (thanks Misanthrope)
I will probably contribute some tactics as I have a fairly large established collection... From the descriptions, (and I've also looked at mypetbattle code /botbase and petzilla code a few times ) It looks good on paper so far, will give this a go and pick up where there's some slack.
Ah yeah. Setting up the names of pets as externals, would only require using the npcid for the critter (the wowunit that targeting uses to select pets) and using the petid instead of the name when storing data or selecting pets from the UI. Logging and the UI can just use the "safe name" of the pet which uses the localised names. This way there's no real problems with storage of Unicode or string conversion. As long as the UI knows which "cat" is the right one, it can be referred by the unique pet id (local for each player/account) or the pet id (global for all pets) and the player just sees "cat", where the code is using the numeric data instead. It might require farming the npc and pet numbers and data from other sources, like wowhead, and some changes to data storage/logging, but not too much.
Absolutely need a "Blacklist" Section i am stucking with legendary pets most of time Blacklist abilty doubles the value of bot i think.
I'm using your bot and its working fine. The only problem is, that the bot levels more than 3 pets, I only want to level my 3 certain pets. But if I lock them, the first slot doesnt change and it only levels the first Pet and not the other both. I'm doing it with relative, any idea what I could do?
i would like to know if this botbase can do "legendary pet brawler" win 5000 pvp pets battle by doing tag and fight thanks you in advance
Added to the wish list. Capture mode is more of a placeholder right now, have not given it much thought, so all suggestions are welcome.
I've stepped on Elites a couple of times myself. For Black/White lists I need to look at the proper GUI elements and how to work with them. But I can throw in "Ignore Elites" checkbox pretty fast, I think.
I forgot to say "Thank you" for this, but this is very interesting and valuable info. Was returning to look at it many times already. If you do not object I'll copy it in the FAQ post.
I'd suggest you use "Favs Only" mode instead of blocking. This way the pets will be changed in position when the first one gains a level.
That would be very nice. Good tactics can speed up a battle considerably (2 times?) not saying it get a win instead of a loss. And thanks for your suggestions re languages. Not sure if I've understand them completely, but I'll return to the topic closer to the implementation.