[PAID] Templar (a profile-free grind bot)

Is fishing profitable for time spent in comparison to grinding?

 

Beta testing is now done and it's open to the public in the buddy store, everyone get a 1 day free trial.

 

We are pleased to announce that the initial release of Templar is now available in the Buddy Store at 10€. Everyone is welcome to try out the botbase before they buy it with the one day trial. We look forward to hearing feedback from the community about our newest product.

 

We are going to push beta releases to test new features, if you own the product and want to help with beta testing, send me a pm with your buddy auth name and I will add you to the beta testing team, when you start honorbuddy you will then be able to select if you want to use the release or the beta version.

 

after a trial i found some issues
1） I set the mob threshold 8，after a pull and kill,my hunter is still in combat for some reason i don't know. in this state the bot just stand still forever. i tried to use feign death to be out of combat,then the bot go on pull
2) sometimes my hunter pull mobs more then 8 at once(add), for example he pulls 10 mobs, after kill 7 or 8 mobs,he stand still again even there are some mobs attacking him...he just stands still don't defend. maybe this is because the bot is trying to loot after each pull(8 mobs)but he is in still in combat so he just waits?, Because some times I loot mobs by my hand the bot goes on to defend and pull the nest stacks of mob
maybe you could let the bot to loot after each pull and kill even in combat, i used combat looter plugin to go with the bot , but it is not so good for remote classes...
sorry for my bad english, it is not my native language. i hope i made u understand what i mean.

 

• If you're not fighting anything and still in combat, the bot will continue to pull after 45 seconds. (It's a fix we have in case of combat bug).
• You can accidently pull more than the set ammount as we are calculating how many mobs your have on you by checking how many mobs have you targeted, I discovered this during testing that it happends sometimes but it's not a big issue as you can just lower the ammount of mobs you pull if it causes problems.
  • I'm guessing you're using Singular as your CC and sometimes Singular wants to blacklist mobs (this is a false possitive of a struck mob) and sadly it's nothing we can do to prevent this, it's a Singular problem and not caused by Templar.

 

How do to reset the starting location?

 

Stop the bot and start it again.

 

We are in need of beta testers for our new features, if you currently own the product and want to help with beta testing, please send me a pm with your buddyauth name and I will add you to the testing team

 

OK, just bought this and I see a big hole in the bot. It does not skin mobs. One of the main reasons I bought it was for ad hoc killing and skinning mobs in an area. I have only tried it for 30 min but it performs well clearing an area and pulling multiple mobs. I will keep the bot but adding a skinning feature would be nice. I checked skin and ninja skin in settings and tool yet the bot ignores this.

 

Skinning and other professions is the next thing on the list
We will add support for Skinning / Disenchanting etc for those that have the professions.

 

seems 3rd party CRs not supported even i opened auto move.
getting stuck when it muti - pull .
add target function not supported in other language

 

Could you please add your full log so I can see what is happening ?

 

Templar beta, as requested I'm reporting what I found out so far.
Zone: Wintergrasp; Class: Rogue, CR: Singular,

WG testing #1:
Sometimes it kills a target and then instead of looting briefly moves to the next target, then it "remembers" it has to loot and goes back to do so before moving to the next mob (nothing major tho), I have logmarked these occurencies, other than that grinding went without a hitch.
- [08.41.51.070 N] [Singular] LOGMARK # 1 at 10:41:51.069
- [08.42.33.798 N] [Singular] LOGMARK # 2 at 10:42:33.798
- [08.43.05.898 N] [Singular] LOGMARK # 3 at 10:43:05.898
At the end of the log you can see it got "stuck" in the water after killing Glacial Spirit, it then couldn't get out for a bit and tried to mount up, finally managed to mount up (on the flying mount) in the end and then couldn't proceed to kill mobs anymore cause it kept dismounting immediatly, you can observe this behaviour various times:
-[08:45:02.152 N] (Singular) Dismounting... Reason: Pulling


WG testing #2:
Did a fresh HB install this time, it went without a hitch (still "forgetting" to loot and then going back sometimes) untill it had to mount up and try to get to the starting spot after mobs were all killed, the dismounting behaviour appeared again, (however there were no mobs around to be pulled as it killed everything) you can observe it at the end of the log:
-[08.54.45.570 N] [Templar]: Can't find any nearby mobs.
-[08.54.45.598 N] [Singular] *Stealth on Me @ 100.0%
-[08.54.46.216 N] Mounting: Green Wind Rider
-[08:54:48.391 N] (Singular) Dismounting... Reason: Pulling

WG testing #3:
Mainly to check if BoS/stealth were the cause of the mounting/dismounting, I disabled those it still seemed to occur

Mail got stuck:
The bot correctly went to the nearest mailbox and proceeded to mail the items to the correct toon, however it didn't mail the purple items from the timeless isle I had in the bags (I suppose it's cause they are BoA? sorry couldn't test with anything else as I had no other purple), then it proceeded to spam the other toon with empty emails. It never initiated the vendor behaviour as it got stuck there mailing items.
The bot mailed protected items (reporting although not sure wether protected items are for vendor behaviour only).

 

here is the fresh log:
View attachment 176 2014-09-02 18.02.txt

 

Templar beta; Class: Rogue

YRB2 and Tuanha Rogue logs.
Adding my logs to joe_ss' logs as I am encountering troubles with 3rd party CR's as well, the bot seems to auto attack only, or sometimes use a spell to open, then autoattacking only.

Vendors logs:
Forced the vendor behaviour by disabling mailing items, the bot correctly identified vendors in both Klaxxi'vess and Townlong Steppes, however in Klaxxi'vess the vendor also has a repeatable quest http://www.wowhead.com/quest=31603 , so an additional dialogue option is available when interacting with the NPC, and the bot got stuck there, unable to pick between options and sell items.

In Townlong Steppes (normal vendor log), the bot manages to sell items, however it did sell protected items.

 

I see that Singular is throwing a lot of errors, I'm moving stuff around to see if I can get it fixed.

When there is no mobs to kill it should mount up and fly back to the start location, that's intended.
I have to look up why looting check seem to be a bit slow to react.

Yeah, I have to look at the mail behavior (I blame Wigglez for this one ), think he might have forgot to set a check if we have items to mail.

 

• I hope that the issue we have with Singular throwing errors is the same thing that's causing 3rd party cc's to not work proparly, I've hopefully made a fix for that.
• I have to blacklist vendors that don't open the vendor page once you interact with them or if I can find a solution to make bot select vendoring.
• About the protected item, was that perhaps a grey item you had set as protected item ? Because botbase will allways sell all grey items (who wants to save any grey item ?)

 

Apologies I should have been more clear when reporting that.
What I meant is that it kept mounting up to go to the start location as intended then immediatly dismounting to pull (no mobs around to pull tho) then remounting and dismounting stuck in a loop, obviously not being able to reach the start location.

Yes it was grey item in the vendor case, I'm trying again with a not grey item now.

EDIT: It correctly doesn't sell protected items Also, saw you pushed new beta version updates, gonna try again with 3rd Party CC's and getting Skinning to test it as well

 

A new beta is up that will hopefully handle skinning.
Hopefully this also fix the 3rd party cc's.
I know there is a issue with multipulling, that once you're below the treashhold it keeps pulling more (even tho you have reached the treashhold earlier)