[Questing][N]BigStud - Val'Sharah - Skinning, Mining, Herbing Pack

Thank you for the reply Wolfman. I believe I have the incorrect SpellIDs issue fixed in version 1.0.1 which I am posting right now. Feel free to update and let me know how it works!

 

[InteractWith-Intera(warning)] Shoot is not usable, yet. (cooldown remaining: 0s)
[InteractWith-Intera(warning)] Exceeded our maximum count(7) at attempted interactions--blacklisting Gleamhoof Stag for 30s
[InteractWith-Intera(warning)] Shoot is not usable, yet. (cooldown remaining: 0s)
[InteractWith-Intera(warning)] Exceeded our maximum count(7) at attempted interactions--blacklisting Gleamhoof Doe for 30s
Stopping the bot!


This is the new error i get with priest, it wont use any spells just wants to use shoot... but i dont have that enabled, so i assume its the profile since other profiles its using singular rotation like it should...?

 

thanks

 

Same for me, trying to use "shoot"

 

yeah id say really gr8 effort to help the community but not so much on the support =/. If you can get this working from a "just press start" point of view, you'd get alot of donations !

 

so it works now in anyway?

 

I also changed the Hunter Interact SpellID 3044 to Cobra Shot and It's working fine. I would guess the old 3044 is for auto attack, but Cobra Shot works well enough.

It was still 3044 in the 1.0.1 release.

 

Had to change the spell ID on Havoc Demon Hunter. I changed it to Throw Glaive (185123). The profile seems to preform so-so. There a lot of dead Wild Dreamrunners and whatnot that get's target, resulting in the bot wasting a lot of time until it blacklists the mob. And the blacklisting doesn't work that great. On my Demon Hunter it circled around a few dead Wild Dreamrunners and kept targeting them over and over.

 

I have been trying to find a custom behavior work around for this. Honor Buddy is the cause of the issue not the profile. I've tried several different variations to get it to black list a mob that can't be skinned to no avail. I have submitted a bug report to the Dev's in hopes of either getting a fix, or finding a potential work around.

 

Unfortunately I do not have all classes to level 100+ yet so I am trying to find a spellID that works for all classes using wowhead. If you could post the Spec and the Spell ID that works for you that would be great.

 

tell me how to find it and i will =P. Its a Shadow Priest, and a better spell to use would be shadow word pain in place of shoot.

 

Google the spell, and the ID is after /spell= in wowhead URLs.

 

NOTICE: Hey Everyone check the original post. I've added in quite a few new features that where requested AND streamlined the profile. Check out version 1.0.6 released today!!!

 

Hey studdy.
Started this on my lvl 100 resto druid, and clicked skinning only (have mining but doesn't use it).
All it does is run between undiscovered flightpaths, and occasionally attack bears. When it does, it applies moonfire, and stands there renewing moonfire when it ticks out.
Otherwise it just heals itself and doesn't do any other types of damage (wrath / sunfire).

Does this script support dps and tank builds only, or is that my CC that's wrong?

 

yoyo!

Going to try it out, best location to start it on?

 

Started this at the Lorlathil camp. Playing a lvl 110 Outlaw Rogue.

Got this error.

[DoWhen-DoWhen(error)] PROFILE ERROR: ItemId, SpellId, and ActivityName attributes are mutually exclusive.
[Ref: "[Questing][N]BigStud - Val'Sharah - Skinning Mining OR Herbing 01 - ver. 1.0.6" @line 137]
[DoWhen-DoWhen(error) @line 137]: Stopping Honorbuddy. Please repair the profile!

 

[DoWhen-DoWhen(error)] PROFILE ERROR: ItemId, SpellId, and ActivityName attributes are mutually exclusive.
[Ref: "[Questing][N]BigStud - Val'Sharah - Skinning Mining OR Herbing 01 - ver. 1.0.6" @line 137]
[DoWhen-DoWhen(error) @line 137]: Stopping Honorbuddy. Please repair the profile!
Bot stopping! Reason: Profile has too many errors

 

Can you both please attach a log so I can see what the issue was?

 

First time uploading a log, hope I did it right.

 

Worked out great thanx. I found the issue, I had an error in the new implementation of the Crystal of Instanity use. It should be fixed in version 1.0.7 which I am uploading now!