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

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

happyfriet said:
I just noticed because my bots barely ever die - with the <DisableBehavior Name="Death" /> , the bot no longer clicks Release spirit when it dies.
Click to expand...
Hm, the plugin is coded to click the "Release Spirit" menu itself.
I'm sending a tester out to see what's going on.
May have to use an alternative rather than DisableBehavior.

Edit
Here's an edit.
View attachment DeathRun.cs
The version you were using sent a code in that would replace Honorbuddy's death routine when your player died.
I'm guessing for whatever reason your bot wasn't launching the replacement code when you died.
This new version will fire the replacement code as soon as Honorbuddy is activated.
So it should be constantly active.
Also, update your SVN/ZIP/EXE, I've removed the DisableBehavior.​


mepster said:
When I start the insanity pull profile I get a message in red
"WARNING:
- You have been warned"

What does it mean?
Click to expand...
Lol, that you'll probably die running that profile.
 
Last edited:
Hmm atm with the lastest version i'm getting the old problem, where as he will teleport back right before the portal to the spirit rezzer and gets rezz sickness.
When the bot starts when the character is already dead - it will release and follow the death route.
When the character dies while the bot was running, it doesn't press release spirit.

(everything updated)
 
Here a Little updated gundrak Profile, just added a new killing Point before Boss 3, cause my bots died most often in this area.

edit: with the newer death.cs he will ressurect at Spirit healer :/
 

Attachments

Last edited:
happyfriet said:
Hmm atm with the lastest version i'm getting the old problem, where as he will teleport back right before the portal to the spirit rezzer and gets rezz sickness.
When the bot starts when the character is already dead - it will release and follow the death route.
When the character dies while the bot was running, it doesn't press release spirit.

(everything updated)
Click to expand...
Hmm, do you have the guild perk that makes you run faster while in ghost form?
 
after more testing with the latest version it seems it did it's job the last 6 deaths...
though the first time it did teleport back to the spirit rezzer and get sickness
second time it also bugged and couldn't release..

Don't understand - don't see any pattern - I did exactly the same thing
 
Last edited:
happyfriet said:
after more testing with the latest version it seems it did it's job the last 6 deaths...
though the first time it did teleport back to the spirit rezzer and get sickness
second time it also bugged and couldn't release..

Don't understand - don't see any pattern - I did exactly the same thing
Click to expand...
I'm thinking it's not properly reaching the coordinate that makes it enter the instance.
That's why I was wondering if you had the speed perk.

The coordinate may need to be more fine-tuned.
 
Not getting the release problem anymore - guess it was because I didn't restart hb the first time when reloading the profile with the death thingy removed..
 
happyfriet said:
Not getting the release problem anymore - guess it was because I didn't restart hb the first time when reloading the profile with the death thingy removed..
Click to expand...
Lol. :3
All that's left is getting it to actually enter the instance upon death. ;P
 
happyfriet said:
View attachment 134269 just when I said that - upon forcing a death while bot running it's stuck on death now.

Going beyond my understanding xD only sometimes does this.. like once in 10 deaths
Click to expand...
Hrrm... the behavior isn't picking up your death at all.
I'm looking through the code and I don't see why it would be messing up.

Do you have Skype? Or anywhere we could chat in real-time?
 
EchoTiger said:
1) The global MinFreeBagslots is -1. You cannot go under this value.
Also, the 'leave instance' code is the first thing that's executed in the profile, so it already should leave the dungeon before checking if it needs to vendor.

2) I'll have to add a code for every profile in the pack to delete the specific food/water that drops in that instance.
If it's auto-activating upon bot activation, then try just removing the plugin.
If that doesn't work, I can create a profile specific to your issue - which profile is it?
Click to expand...

Atm I run solely Botanica.

I set min bag value to 25, that's the approximate average number of slots occupied for a single run (based on my exp). I will remember to save the log whenever I happen to stuck again the same way.

Removing the plugin doesn't work, the numbers under Mail & Refreshment setting always restored whenever we restart HB.
And no... thanks a lot, I dare not to consume your time for my specific needs. But even if I do, I won't let you do it for free. Thanks again.
 
Howcome it doesnt mail, using gundrak/draktharon profile? I have mail set in settings , my bags just fill up with frostweave
 
after running my and my friends accs there (bot acc on different PC's) - got banned 72h . was running 12-14 hours a day (3days long). both of us 72h ban
 
<If Condition="(Me.FreeBagSlots &lt;= 10)" >
<CustomBehavior File="Message" Text="\nYou're still under 10 bagslots after selling.\nExecuting mail routine.\n\nIf you do not have a MailTo set, you may want to set one now." LogColor="Red" />
<CustomBehavior File="FlyTo" X="5546.134" Y="-3194.041" Z="440.3812" />
<CustomBehavior File="FlyTo" X="5525.695" Y="-2623.592" Z="319.2954" />
<RunTo X="5490.855" Y="-2640.885" Z="305.896" />
<CustomBehavior File="RunMacro" Macro="/dismount" />
<SetMailbox>
<Mailboxes>
<Mailbox X="5417.155" Y="-2620.26" Z="307.0088" />
</Mailboxes>
Do i just change that to be a higher value
 
dutamulia said:
Atm I run solely Botanica.

I set min bag value to 25, that's the approximate average number of slots occupied for a single run (based on my exp). I will remember to save the log whenever I happen to stuck again the same way.

Removing the plugin doesn't work, the numbers under Mail & Refreshment setting always restored whenever we restart HB.
And no... thanks a lot, I dare not to consume your time for my specific needs. But even if I do, I won't let you do it for free. Thanks again.
Click to expand...
removing the plugin ( not turning off ) THEN removing the numbers WONT make them come back - tested that plenty..
They ARE restored when you have the refreshments plugin still active in your folder.
 
Last edited:
dutamulia said:
Atm I run solely Botanica.

I set min bag value to 25, that's the approximate average number of slots occupied for a single run (based on my exp). I will remember to save the log whenever I happen to stuck again the same way.

Removing the plugin doesn't work, the numbers under Mail & Refreshment setting always restored whenever we restart HB.
And no... thanks a lot, I dare not to consume your time for my specific needs. But even if I do, I won't let you do it for free. Thanks again.
Click to expand...
The header tag of <MinFreeBagslots> shouldn't be altered.
It's set to -1 so that Honorbuddy's automatic 'seek vendor' code won't kick in. If it kicks in at any point - issues will occur.

If you want the bot to sell at a lower/higher bagslot, you will need to edit the conditioning codes.


MadDog said:
<If Condition="(Me.FreeBagSlots <= 10)" >
<CustomBehavior File="Message" Text="\nYou're still under 10 bagslots after selling.\nExecuting mail routine.\n\nIf you do not have a MailTo set, you may want to set one now." LogColor="Red" />
<CustomBehavior File="FlyTo" X="5546.134" Y="-3194.041" Z="440.3812" />
<CustomBehavior File="FlyTo" X="5525.695" Y="-2623.592" Z="319.2954" />
<RunTo X="5490.855" Y="-2640.885" Z="305.896" />
<CustomBehavior File="RunMacro" Macro="/dismount" />
<SetMailbox>
<Mailboxes>
<Mailbox X="5417.155" Y="-2620.26" Z="307.0088" />
</Mailboxes>
Do i just change that to be a higher value
Click to expand...
Changing this one will only tell the bot to check for a higher bagslot minimum only after the player has vendored and is *then* going to mail.
In order to assign a minimum for the entire vendoring routine - you will need to change the others.
The dungeon code should be wrapped in a "While bagslots are greater than" and the vendor code should be wrapped in "While bagslots are less than."
 
realdeee said:
jep my 30 accs got 72h too at 20:46 ^^
Click to expand...

30 accs and only 72h ? mine was 8, 20h/day, banned after 2 days, and the next army, 5 toons, banned after 8 hours dungeons (but for this case, i think it was the vepen that triggered it)

but still, worth it :D really big thanks for your kickass profiles EchoTiger!
 
You must log in or register to reply here.
Back
Top