What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

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

spacebooger said:
hes die alot when he shouldnt, he stands there when being attacked and then maybe will start attacking. if i set it not to multi pull is doesnt do anything, if i do and i set it to one mob he still pulls a second mob and catches a 3rd and gets himself killed.

View attachment 148815
Click to expand...
When I'm reading the log I see HB loading meshes all the time (it's busy loading meshes over and over), can you try it in a other zone and see if the problem is the same there, trying to find a pattern.
 
Hello, i have problem with the botbase. I'm using it for skinning at the moment. Bot runs, kills and skins really fast but there is something making it stall after skinning the mob. I'm not sure if it tryes to loot the mob too fast after the bot skinns mobs. For me there is nothing weird in the loggs either. I even try to manually loot the mob after the kill but it just doesnt allow me to do that. This might be also issue with wow itself.
 
What CC are you using? If it's singular check if it has a skinning option in the settings and disable it there. I have chameleon users that had a similar problem with lockboxes due to singular.
 
Version: 1.1.0.5 Class: Rogue; Zone: VotFW

decided to check if I would incur in the same problem as Kalmah did, and I did as well xD
Basically I can confirm that sometimes after skinning instead of looting the skinned mob like it should it's as if it interacted with the corpse multiple times... untill i manages to loot. The fact that for whatever reason HB seems to be filtering out duplicate log entries makes it all more difficult to understand what is happening, as sometimes it interacts a lot with the skinned mob but all you see in the log is 1 entry of

Code: 
Interacting with <insert mob> (Unit Id: <insert ID>)

so the log shows a "normal" behaviour whilst it's not the case.

anyway full log attached and logmarked as usual.
Also tried with another CR and still happened.

PS: would be nice if the filtering out could be overridden by the botbase with some sort of diagnostic mode :/
 
Last edited:
Kavol said:
Version: 1.1.0.5 Class: Rogue; Zone: VotFW

decided to check if I would incur in the same problem as Kalmah did, and I did as well xD
Basically I can confirm that sometimes after skinning instead of looting the skinned mob like it should it's as if it interacted with the corpse multiple times... untill i manages to loot. The fact that for whatever reason HB seems to be filtering out duplicate log entries makes it all more difficult to understand what is happening, as sometimes it interacts a lot with the skinned mob but all you see in the log is 1 entry of

Code: 
Interacting with <insert mob> (Unit Id: <insert ID>)

so the log shows a "normal" behaviour whilst it's not the case.

anyway full log attached and logmarked as usual.
Also tried with another CR and still happened.

PS: would be nice if the filtering out could be overridden by the botbase with some sort of diagnostic mode :/
Click to expand...
Hmm... ok
I have a timer on it so it should never try to skin more than once / 1 sec (I think I have it on skinning as well... have to go through code tomorrow when I wake up), just got home from work 5.35am and too tired to look at it right now.
 
AknA said:
Hmm... ok
I have a timer on it so it should never try to skin more than once / 1 sec (I think I have it on skinning as well... have to go through code tomorrow when I wake up), just got home from work 5.35am and too tired to look at it right now.
Click to expand...

No horry. There was also no option for skinning in the singular cr so it seems there is timing issue with the botbase itself.
Keep up the good work! Cheers, Kalmah.
 
wth.webp

Still doesn't find mobs. Default keybindings ingame & it happens with any CR I try.
 
Would it be possible to add Templar and Charmeleon to robotos Tramper? These botbases would be nice to have there also. Roboto wont do it without you asking/contacting him about it.

Cheers, Kalmah
 
Kalmah said:
Would it be possible to add Templar and Charmeleon to robotos Tramper? These botbases would be nice to have there also. Roboto wont do it without you asking/contacting him about it.

Cheers, Kalmah
Click to expand...
Talking to Roboto, we'll see what we can solve.
 
Ver 1.1.0.6 is approved, let me know if you have any issues with Skinning now :)
 
AknA said:
Could you please add a full log when that happends.
Click to expand...

You just need to add support for levels 1-89, for the botbase to work. It works fine on any level 90 I run it on; but I go to use it to level my alt mage and it refuses to find targets.
 
Farix said:
You just need to add support for levels 1-89, for the botbase to work. It works fine on any level 90 I run it on; but I go to use it to level my alt mage and it refuses to find targets.
Click to expand...
I don't have any kind of level check, so that is really strange.
 
AknA said:
I don't have any kind of level check, so that is really strange.
Click to expand...

Yeah, cause the logs don't show anything special. I left it running on my 90 mage and it was still grinding this AM. It's either the botbase or HB; cause out of the 2 private mage CRs I use, both support levels 1-90; unless they have not been updated for WoD yet (pre-90).
 
Hi!
This has been performing great murder-wise, but for some reason it's not looting any corpses at all on my lvl 90 Horde Fire Mage using the Portal class profile thing.
It just goes around massacring everyone in my pull radius, am I doing something wrong?
Thanks!

EDIT: Ah, so when multi pull is off it goes around looting every corpse just fine. Probably related to multi pull then?
 
Last edited:
TheFieryTaco said:
Hi!
This has been performing great murder-wise, but for some reason it's not looting any corpses at all on my lvl 90 Horde Fire Mage using the Portal class profile thing.
It just goes around massacring everyone in my pull radius, am I doing something wrong?
Thanks!

EDIT: Ah, so when multi pull is off it goes around looting every corpse just fine. Probably related to multi pull then?
Click to expand...
How Multipull works, it will continue to pull mobs until you either drop too low on hp or until you have selected ammount of mobs targeting you, so if your dots (or whatever) kills the mobs before you reach the ammount of mobs you have selected then yes, it will just continue to pull and never loot because it doesn't reach the number of mobs you have selected.
 
AknA said:
How Multipull works, it will continue to pull mobs until you either drop too low on hp or until you have selected ammount of mobs targeting you, so if your dots (or whatever) kills the mobs before you reach the ammount of mobs you have selected then yes, it will just continue to pull and never loot because it doesn't reach the number of mobs you have selected.
Click to expand...

Ah, I see.
Well, basically I'm farming in a tiny patch of farmland surrounded by fences in hopes to drop the Black Tabby cat companion, the mobs there are lvl 20 (I'm 90) so every one of my spells oneshots them, and they pretty much instantly respawn so on multipull mode it just endlessly kills them.
Meaning I have no choice other than use single pulls right? That's not really a problem for me, but just making sure.
Thanks for your help! :)
 
Some weird issue kill the bot while the mob is pulled. So the afk timer works great, it jumps. So its not the afk timer. Its something else that kill the bot during combat ;)

[21:50:47.590 D] Changed POI to: Type: Kill, Name: Zandalari Warscout
[21:50:49.762 N] [100][0] Faerie Fire--> Zandalari Warscout
[21:50:50.812 N] [100][0] Rake--> Zandalari Warscout
[21:50:51.952 N] [79][1] Savage Roar
[21:50:52.959 N] [67][0] Rake--> Zandalari Warscout
[21:50:53.869 N] INACTIVITY TIMER TRIPPED! LOGGING OUT!
[21:50:53.881 Q] Bot stopping! Reason: Main window is closing
[21:50:53.903 N] [Templar]: Shutdown complete.
[21:50:53.903 D] Clearing POI - Reason Bot stopping

View attachment 10088 2014-11-04 14.27.txt
 
You must log in or register to reply here.
Back
Top