[Azyul Project] Dungeon Farming, Gold Farming, Mount Farming, Transmog Farming, and more!

An empty profile won't get you banned because there's no algorithm to detect.
As soon as you vector anything that'll be repeated for an increased amount of time, you instantly are a target no matter how elaborate it is.

As far as the 'little profile' - this process wouldn't be any different from what's setup now.
It'll still be using the same calculation methods as the current Randomizers.
Me making a profile to randomize profiles would be like me making separate dungeon farms for Horde and Alliance. xD

 

All the code looks correct, I don't see why it would be selling your greens.
The bot will vendor first, but the <SellGreens>False</SellGreens> code should protect them regardless.

Do you have a log I could look at? If this is actually a technical issue, it'll need to be pushed the core developers.

 

Like I said, it's all semantics.
Semantics being the potential millions of variables that go into the "mysterious ban-calculation system."
From repetitive hotspot hit detection, to player reports.

It doesn't matter how random the bot is. Even with pickpocketing - you're staying in specific area(S) and repeating a process over and over.
Being stealth does nothing but keep you out of site from other players - not out of sight of Warden.

Of course, randomization *can* decrease your chance of getting banned - but the risk is always there regardless - no matter how random the bot is.
People get banned for simply using combat bots, and the only thing they're designed to do is do a rotation for you while you control your character.

As far as an alternative Randomizer - I don't know of any.
You'll have to browse the forums and hope that there's one that randomizes the dungeon to your exact specifications until I can make one.

 

Gundrak was having constant issues with the entering CTM coordinate - regardless of how much it was fine-tuned so I had to set it as a behavior instead...
Now you see why I don't use behaviors to enter instances. xD

If your bot doesn't enter the instance within 15 seconds, the behavior will terminate the profile. There is a setting to increase the wait timer from 15seconds to X, I just haven't done it because it didn't seem like anyone would need that much time to load.

I'll probably end up increasing it in a future update to prevent this issue.

 

Try this edit?

View attachment [RunAll]Randomizer.xml ​

 

Your attachment for the picture is invalid.

But, the log should be enough. :3
Your Z coordinate drops significantly as the first coordinate of the last pull is being executed - which that would only happen if the bot fell off of the rotary center-piece.
The only potential cause of the bot falling off would be a knockback from one of the Rhinos.

Unfortunately, something like this is completely RNG and is almost impossible to prevent.
The only way I could reduce the chance of it happening is to make sure the bot is directly facing the Rhinos before pulling so that the Rhino will only knock the player directly back - or directly forward instead of from the sides.

 

If we could execute synchronous events in the profiles, yes. :3

But if the bot falls - it'll most likely fall while the pull behavior is running.
Once the pull behavior starts, Honorbuddy will only want to complete it before executing anything else.
So it won't bother to look for if its fallen or not.

 

New features are coming!

I'm planning on giving you guys an easier solution modifying the profile(s) without touching the profile code.
And no, it's not a plugin or program - but instead this method will be completely integrated into the profile code!

Some modifications will include:

• Min Bag Slot before vendoring.
• Min Bag Slot before mailing.
• Dungeon Difficulty.
• Vendor Method. (Custom LUA or Honorbuddy, item protection - etc)
• Use Mobile Bank.
• Use mobile vending item (Jeeves, Repair Bot, etc)
• Use mobile mount.

All of these modifications will be changeable while the profile is running and will take immediate effect so no restarts will be required.
This will be a new foothold in Honorbuddy profile innovation.​

Update(s)!

Update 1: Gundrak has won the poll - therefore it will be the first dungeon that will use this new feature!

Update 2: This 'new feature' has been named AMS (Azyul Management System) or AM for short.

Update 3: The very first profile to use the AMS as been released to the SVN and ZIP.

[AM - Alpha] Gundrak​

Here's a screenshot!





Please Note!
This is a Alpha design of the Azyul Manager. More features will be added to it soon.

I understand a lot of people may have concerns over detection risks when using something like this.
I've discussed this with a few of the Honorbuddy core developers and we came to the conclusion that using LUA to do 'things' like this will not put you at any risk.

When the Azyul Manager is loaded into your game - it operates just as a regular WoW addon.
At this point, it has no association with Honorbuddy.

The Azyul Manager also does not communicate with Honorbuddy in any way.
When you make changes on the Azyul Manager, it simply stores a binary value which would be the same as you typing: /run hello = 1 in-game.​

​

Small Announcement! (July, 10)

About 24 hours ago a [AM - Alpha] release of Gundrak was sent out to the SVN and ZIP since it was the highest voted choice during the StrawPoll.

If you don't know, AM is short for Azyul Manager. (aka AMS, Azyul Management System) It's an in-game menu that allows you to control how the profile is ran.
It allows you to modify how big your pulls are, the dungeon difficulty, minimum bagslots before selling, what to deposit in your bank, etc.

Since The Botanica was the second highest voted choice, I've created a [AM] version of it also, which has just been released and can be found in the Outlands folder on both the SVN and ZIP.

Keep in mind, these profiles have been thoroughly tested - however they're still considered in the Alpha stage.
The [AMS] is still being developed. New designs and features are yet to come.​

Also, on a side note:

Documentation has been added inside of the [AM] profiles.
This documentation explains how you can modify the 'default settings' of [AM] so that anytime you load the profile - the settings you want are already loaded in there.
This should help with reloggers.​

 

Great. ^^
Glad you managed to get it!