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)

Templar version: Dev; Zone: Durotar/Townlong; Class: Rogue

Templar Dev with Skinning: The bot still seems to try to move away before looting, then going back sometimes, same behaviour happens now with skinning, (i.e: moves away, then goes back to skin).
It skins mobs now, but it tries to "skin them multiple times". Basically it properly skins the killed mob, then after looting the leather it tries to skin the mob again, but the already skinned mob disappears before it can be skinned a second time (obviously).

Vendors log: when bags were full the bot went to sell items, then it got stuck at the vendor after selling with vendor window open, If I try to forcefully move the bot off the vendor and close the window the bot will go back to the NPC and attempt to sell again.

3rd Party CC's: still not working, only using auto attacks.
 
Last edited:
New beta ver up :

  • Cleaned up code
  • Removed the distance check on multipull
  • Added WaitContinue on skinning to hopefully prevent the interact bug.

Try 3rd party CC again and see if it's fixed now please.
 
Templar version: Beta Version: 1.0.2.5, Classes: Rogue/Mage/Druid; CR: Tuanha Rogue/YRB2(rogue)/Portal/Stars

Alright now the bot literally doesn't do anything, it just stands there saying it can't find mobs, while around the toon there are plenty, the good news is that I forcefully put the bot in combat and Tuanha CR reacted and fought back the mobs, Portal and Stars casted as well but they felt a tad "slow" I assume it's due to Templar disabling framelock, (also I didn't disable all the stuff I wouldn't use in Portal so I suppose that had an impact as well), cause Singular was faster than Portal in reacting, good news is they're casting/attacking now tho.

YRB2 had an odd reaction, if movement is enabled it will not attack nor move to attack (first log), if I disable movement it will actually attack and fight back just a bit "slow" since framelock is disabled (second log).
I can't really say anything untill the botbase actually "sees" mobs again, because YRB2 actually moves (with movement disabled) in order to loot a dead mob, so it might move even to attack once that bug is fixed.
 
Last edited:
Regarding skinning, I killed some mobs to check if it would take over and skin them since it won't attack on its own; it successfully loots and skins mobs also spams the skinning ability less, it still seems to be doing something tho, as you can see from the log first it skins the mob and then tries once again getting the "Target is tapped" error.

[19.48.09.430 D] Interacting with Bloodtalon Taillasher
[19:48:11.532 N] (Singular) [WoWRedError] Target is tapped
[19:48:11.537 N] (Singular) error parsing Guid ''
[19:48:11.539 N] (Singular) (Singular) [CombatLog] SPELL_CAST_FAILED Skinning#8613 failure: 'Target is tapped'

One thing tho, if the skinning skill is lower than the one required to skin, the bot will still attempt to skin, not sure you want to take this scenario into account tho since this will be a problem only while a player is still in the process of levelling up the profession, but I thought I'd mention it.
 
Last edited:
Ok, thanks for all the input Kavol :)

I have a other idea how to fix the skinning issue, but don't have time to work on it tonight, I have to go to bed, starting work really early tomorrow.
And to handle if you don't have the skill to skin a mob, have to figure out a way to counteract that so it doesn't get stuck.

Glad that 3rd party cc's working now, but instead I've seemed to create a new bug (tho it didn't happen to me).
Try to delete all the Templar settings files : hb\Settings\Templar\{charname}-{servername}\ directory to see if it fixes the not moving part, did some changes to the GUI so that might be it.

We're constantly trying to improve and speed up the bot to counteract that we have to disable the framelock.
We have to disable the framelock due to that we are useing a load heavy calculation to find the nearest mob, we're using SurfaceDistance (QBCore code made by CJ).
SurfaceDistance code has been improved tho sience we started to code on Templar so in the end we might even be able to enable framelock if we can optimize the code enough, testing will tell :)
 
Templar version: Beta Version: 1.0.2.5

Np, and ok, I tried again after a fresh HB install and I'll post what I found out, so when you have time you can have a look at it tomorrow.

Class: Rogue; Zone: Durotar; CR: Singular (tried also YRB2 but didn't post any log as it's working)

log #1: the bot didn't do anything, much like the previous time

log #2: didn't change anything just restarted HB, the bot tossed an error (starting here)

- [21.45.18.327 D] System.NullReferenceException: Object reference not set to an instance of an object.

then it successfully detected a boar approached it, started to "move around it like crazy", finally killed it and went back to the start spot, saying that it couldn't find any more mobs while around there were plenty.

log #3: Before starting the bot again I enabled skinning, it went back and skinned the boar killed in log #2, then said there were no mobs again. At this point I started to enable options in the bot GUI one by one just to check, and as I enabled multi pull (I always had it disabled so far) the bot started to correctly grind every mob around, loot and skin (still "forgetting" to loot sometimes and then going back, but at least it was attacking).
When I tried to disable multi pull the bot stopped to attack once again.

In the end it seems that it attacks only if I leave multi pull enabled, however you will be happy to know that it's working with YRB2, although it's very "slow" (again I guess it's framelock being disabled that causes this) movement in the CR is enabled now, and if I disable movement the bot correctly doesn't move (not the other way round like earlier lol.

EDIT:

I did some further testing - Class: DK; Zone Kun-Lai Summit; CR: Singular/YRB2

Singular log: all went well untill the bags were full, then it entered mailing behavior, it basically couldn't find a mailbox and got stuck there (you can see this at the end of the log), it however defended itself when attacked.

YRB2: slower than singular, but went ok, at some point it started to swap target like a maniac between two (2) yak, but I think that had something to do with the CR logic to select a target.
 
Last edited:
oh, doh, I know why single pulling isn't working, I made a dodo there and forgot to test it myself before I released this beta.
Things to do when I get home from work.
  • Fix single pulling (know how to fix it)
  • Fix skinning (I have an idea)
  • Go though mailing code again (and ignore mailing incase we don't find a mailbox and go for vendor)
 
Does/will it support mixed mode? Can i use it for leveling mixing with dungeonbuddy?
 
AknA said:
oh, doh, I know why single pulling isn't working, I made a dodo there and forgot to test it myself before I released this beta.
Things to do when I get home from work.
  • Fix single pulling (know how to fix it)
  • Fix skinning (I have an idea)
  • Go though mailing code again (and ignore mailing incase we don't find a mailbox and go for vendor)
Click to expand...

Ah ok .. just see the skinning problem :) would be nice to see a fix
 
Sorry, I don't have time to code today :(
Left for work 6am this morning and came home at 9pm and have to go to work at 5am tomorrow.
Hopefully I have some time after work tomorrow.
 
Templar version: Beta Version: 1.0.2.5

This is more of a feature suggestion as I don't know if it is implemented yet, so haven't got a log (can post one in case).
The bot isn't opening the "Strange Bloated Stomach" item ( http://www.wowhead.com/item=67495/strange-bloated-stomach ) that it gets from skinning Cataclysm mobs, not sure if this is impemented and it just didn't open, but if not implemented would be a nice addition also for the MoP items: "Plump Intestines" (http://www.wowhead.com/item=72201/plump-intestines ).
The bot did open the lockboxes I pickpocketed on my rogue and I had left in my bags tho! That was nice to see :)
 
Last edited:
Kavol said:
This is more of a feature suggestion as I don't know if it is implemented yet, so haven't got a log (can post one in case).
The bot isn't opening the "Strange Bloated Stomach" item ( http://www.wowhead.com/item=67495/strange-bloated-stomach ) that it gets from skinning Cataclysm mobs, not sure if this is impemented and it just didn't open, but if not implemented would be a nice addition also for the MoP items: "Plump Intestines" (http://www.wowhead.com/item=72201/plump-intestines ).
The bot did open the lockboxes I pickpocketed on my rogue and I had left in my bags tho! That was nice to see :)
Click to expand...
Just home quickly for lunch.
I guess it was Singular that opened the lockbox (I know there is a feature in Singular for that atleast).
And we're going to add features to keep your inventory as clean as possible so you can grind longer.
 
This botbase is great but for some reason its not skinning mobs and its skipping looting and just continuously pulling mobs is this right?
 
mansellboi said:
This botbase is great but for some reason its not skinning mobs and its skipping looting and just continuously pulling mobs is this right?
Click to expand...
Skinning is in beta atm it will come when all bugs have been sorted out.
Looting should work for the public release.
 
a 3 or 7 day trial for the premium would be nice....maybe something to consider
 
New beta ver up :

  • Cleaned up code.
  • Fixed Single Pulling.
  • Hopefully fixed Skinning double interact.
  • Checking if 0 mobs is targeting us instead of not in combat to pull new mob to prevent stuck in combat bug (could cause double pulling in single pulling mode, please report if it happends too often).

Didn't have time to check on mailing code yet so that's still bugged.
 
healzzz said:
a 3 or 7 day trial for the premium would be nice....maybe something to consider
Click to expand...
Why would you need a 7 day trial to see if a grinding botbase do what it should ? or even a 3 day one ?
For now it's staying as a 1 day trial, as we implement more features it might be higher, but not needed atm.
 
Templar version: Beta Version: 1.0.2.6.1; Classes: Rogue and Hunter; Zones: Durotar and Krasarang; CR: Singular

Skinning stuck: The bot correctly worked with single pull, moved towards the raptor and killed it, still seemed to "forget" to loot (reporting this as not sure if the clean up of the code was aimed to fix this or not, not knowing it I prefer to add additional information instead of leaving out details), then went back and looted mob, the bot tried to interact to skin it but nothing happened, it didn't skin and got stuck there, not pulling additional mobs even after the 45 seconds passed, it however targetted a new raptor.

Hunter single pull: the bot killed the mob, then looted and managed to skin, but it got stuck there like the rogue.
Hunter multi pull: same as single pull log, the bot got stuck after killing and looting the mobs, this time I waited 45 seconds, it didn't try to pull more mobs.

General note: it seems the bot now interacts multiple times while trying to loot, similar behavior to the multi-skinning attempts.
The good news is the single pulling is working again! :)
 
Kavol said:
Templar version: Beta Version: 1.0.2.6.1; Classes: Rogue and Hunter; Zones: Durotar and Krasarang; CR: Singular

Skinning stuck: The bot correctly worked with single pull, moved towards the raptor and killed it, still seemed to "forget" to loot (reporting this as not sure if the clean up of the code was aimed to fix this or not, not knowing it I prefer to add additional information instead of leaving out details), then went back and looted mob, the bot tried to interact to skin it but nothing happened, it didn't skin and got stuck there, not pulling additional mobs even after the 45 seconds passed, it however targetted a new raptor.

Hunter single pull: the bot killed the mob, then looted and managed to skin, but it got stuck there like the rogue.
Hunter multi pull: same as single pull log, the bot got stuck after killing and looting the mobs, this time I waited 45 seconds, it didn't try to pull more mobs.

General note: it seems the bot now interacts multiple times while trying to loot, similar behavior to the multi-skinning attempts.
The good news is the single pulling is working again! :)
Click to expand...
Excellent reporting once again Kavol :)
So that attempt to fix skinning didn't work either, damn it :(
 
Ok, Skinning is somewhat working now, I have to rewrite alot of logic on when to loot/skin/pull to prevent that it tries to do everything at once :P
 
You must log in or register to reply here.
Back
Top