Is the Zip download not visible on the first post?Hey how do I download the profiles? I used to use the ZIP file.
Is the Zip download not visible on the first post?
It's a known issue at the moment for browsers like Internet Explorer or Edge that the graphics don't properly show up.
Here's what it should look like:
![]()
sure.I sent a tester to the location, and it was able to use the Traveler's Mammoth without issue.
Can you post a log of your bots not using it?
For some reason, images attached in the forum weren't showing up for other browsers.Thanks for the reply! I have tried I.E, Firefox and Chrome and I still don't see the links.
For some reason, images attached in the forum weren't showing up for other browsers.
I've ported the images to an external site - so it should work now.
A few people had been reporting this issue and I hadn't got around to fixing it.Echo Tiger, first just wanted to thank you for all of your time building and maintaining these profiles!
My question is specifically on Halls of Lightning Suicide. I am using a fully optimized feral druid everything runs smooth.
Is there a way to have it still use part (or all of) the timer when going to vendor. Here's what I have noticed from my many hours of optimizing. Feral druids typically have ~30-40 secs "wait time" inside instance once it has finished before resetting. But on the times where it "skips" the wait time to vendor, and I will add that I have the Travelers mount to vendor/repair, it simply finishes much too quickly and looks very bottish for 20ish seconds as it tries to re-enter instance getting the "Too Many Instances Entered Recently" error because the bot will keep trying to enter.
Is there a way I could manually edit file or something to have it wait a tad bit longer on "vendor runs" so that this does not happen?
Thank you in advance!!
A few people had been reporting this issue and I hadn't got around to fixing it.
I'll push an update in about 20minutes that will make the bot not skip the wait timer if your character has the Mammoth/Yak mounts.
Edit: The update should be live now.
A few people had been reporting this issue and I hadn't got around to fixing it.
I'll push an update in about 20minutes that will make the bot not skip the wait timer if your character has the Mammoth/Yak mounts.
Edit: The update should be live now.
Nothing was changed in the mount code.The problem I am having now is that it is not using the Mammoth/Yak to vendor it wants to "move to vendor"
It did however wait the full timer before it did this.
Any chance you think what the problem may be?
Nothing was changed in the mount code.
Do you have a log of it?
Ah, I see.Here is an attached log.
Ah, I see.
When the 'mass edit' executed, it also changed some things in the actual mounting logic that I wasn't aware of.
Should be fixed on the latest update.
Do you mean: Stealth while its outside of the dungeon so people can't see you?Greetings. And someone tell me whether it is possible to do something to the character used prowl just before the entrance to the dungeon and to exit from it? So he went in and out in stealth to avoid the attack of rouges. Thanks![]()
Do you mean: Stealth while its outside of the dungeon so people can't see you?
That should be fairly easy.
Open the profile up, and CTRL+F (find text) for the words: Exit Dungeon
Above the first result of the find text, add this line:
<CustomBehavior File="RunCode" Code="SpellManager.Cast(5215);" />
Your result should look similar to this:
![]()
This isn't an issue with the profile - something else you're using is causing this to happen or it's a bug in the bot.Hi there,
Getting an intermittent issue where bot will stand still for extended period of time with log spamming:
[12:46:15.277 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedIf.
[12:46:15.277 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedIf.
[12:46:15.277 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedIf.
[12:46:15.277 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedIf.
[12:46:15.277 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedIf.
Eventually it fixes itself and runs something like:
[12:46:15.384 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedMoveTo.
[12:46:15.517 V] Loading Northrend_34_14
[12:46:15.540 D] Successfully generated path from {9175.68, -1378.8, 1103.57} to {9184.104, -1386.851, 1110.216} in 152 milliseconds
[12:46:15.540 D] Goal: Moving to <9184.104, -1386.851, 1110.216> [Ref: "MoveTo" @line 485]
Full log attached, can see issue occurring relatively close to bottom.