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

A5 - Siege Camp Chest Runner w/ Chest Sensing

well, for me this is working better than other profiles. still, can't pass 55gph max. and legs per hour.. depends... i had sessions of 4 hours with 3+ legs per hour or like now i'm at 3 hours mark with 0.7 legs per hour.

doing this on a wizzard and the movement spells rly works like hell (using teleport 2 yards for a chest, using diamond skin just before he needs to open something or turn around etc). but well... better than doing it manually
 
well, for me this is working better than other profiles. still, can't pass 55gph max. and legs per hour.. depends... i had sessions of 4 hours with 3+ legs per hour or like now i'm at 3 hours mark with 0.7 legs per hour.

doing this on a wizzard and the movement spells rly works like hell (using teleport 2 yards for a chest, using diamond skin just before he needs to open something or turn around etc). but well... better than doing it manually

much more efficient to run other profiles... Chest runs were nerfed long ago.
 
much more efficient to run other profiles... Chest runs were nerfed long ago.

didn't found anything else i could try on hc tbh. after i wrote the comment i got 2 legs fast bumping to 1.8 lph. i guess on a long run 10+ hours should be 2 legs per hour or so.
 
much more efficient to run other profiles... Chest runs were nerfed long ago.

They've nerfed the spawn rates, but not the drop rates afaik - this profile and the older profiles that did the same thing get almost identical LPH to three musketeers and considerably more than rifts, at least in my experience.
 
much more efficient to run other profiles... Chest runs were nerfed long ago.

Yes they did thin them out a bit but other profiles like Ghom/Kulle require you have gear to kill them quickly. On lower torment levels the legendary drop rate off the bosses is pathetic. I need more stats to calculate a good kill rate on bosses/difficulty to calculate a point where this profile no longer makes sense. One advantage those boss profiles have is you get experience on them. However, profiles like this are a great way to initially gear up. Rift/Bounty profiles are nice but still have a lot of issues and the backtracking just kills them currently in the lph department. Just watch them for a period of time and you will see them have so much trouble with figuring out where to go.

So in short if your a well geared character this profile probably doesn't make sense for you.

In other news, got the disable feature for movement working and rrrix pointed me the right direction for a better moveto method. Still updating and testing but I should have an update out within 2 hours. Stay tuned our bot is about to get a big upgrade in intelligence.
 
Last edited:
Delete TrinityMoveToSNOOrginal.cs and try again. Turns out TrinityMoveToSNO is a deprecated method that will be removed from Trinity eventually. I will try to rework using the alternative, MoveToActor. I just can't find where it is or any documentation on it. Gotta love DemonBuddy!

Would have been awesome if you posted an good FAQ on how to get the bot to work on the first page ;)
 
Would have been awesome if you posted an good FAQ on how to get the bot to work on the first page ;)

How to use:
1. Make sure the bot is stopped and the program is closed.
2. Copy "TrinityMoveToSNO.cs" into ../Demonbuddy/Plugins/Trinity/XmlTags/ and override the one that is there.
3. Copy "Chest Runner V1_1.xml" into ../Demonbuddy/Profiles/
4. Start up the bot and change Trinity's settings. Under Objects make sure to have Open Chests selected, Container Open Range down to 6, and Skip Destructibles unless Stuck is selected.
5. Make sure you have Kill Malthael quest available in campaign mode.
6. Start up the bot.

copy/past from first page :)
 
How to use:
1. Make sure the bot is stopped and the program is closed.
2. Copy "TrinityMoveToSNO.cs" into ../Demonbuddy/Plugins/Trinity/XmlTags/ and override the one that is there.
3. Copy "Chest Runner V1_1.xml" into ../Demonbuddy/Profiles/
4. Start up the bot and change Trinity's settings. Under Objects make sure to have Open Chests selected, Container Open Range down to 6, and Skip Destructibles unless Stuck is selected.
5. Make sure you have Kill Malthael quest available in campaign mode.
6. Start up the bot.

copy/past from first page :)

And that didnt work for me ;)

Thats my point.

Something else had to be done :)
 
Shouldn't the stepId in this line,

Code:
<GameParams quest="273408" step="21" act="A5" difficulty="Torment6" resumeFromSave="True" isPrivate="True" numGames="-1"/>

be 3??

so this,

Code:
<GameParams quest="273408" step="3" act="A5" difficulty="Torment6" resumeFromSave="True" isPrivate="True" numGames="-1"/>

otherwise it goes to act3
 
Shouldn't the stepId in this line,

Code:
<GameParams quest="273408" step="21" act="A5" difficulty="Torment6" resumeFromSave="True" isPrivate="True" numGames="-1"/>

be 3??

so this,

Code:
<GameParams quest="273408" step="3" act="A5" difficulty="Torment6" resumeFromSave="True" isPrivate="True" numGames="-1"/>

otherwise it goes to act3

Step 21 is the final quest to talk to Tyreal and go to credits. I am changing it to 3 in the next revision. Really just need any step that gives you siege camp waypoint. Easy enough to change if you dump the quest in DB when the bot is stopped and change it to whatever you need.
 
The profile sounds very promising. Thanks for the work :)
I'm really excited to find out chest run - I kind of downgraded it after hearing that Blizzard nerfed it.
But I sincerely agree to your point where you said people need good gears first to run for Ghoms and Kulle. Otherwise LPH or GPH are pathetically low. (T3 is my best attempt for Ghom and it's like 0.8 LPH)
I hope everyone gets a nice set of gear and be happy lol

- tested, but I found a problem that the bot TP back to town after the last chest, but TP occasionally gets cancelled on hit from one of the seize tower right next to the last chest. TP spot might need to be fixed?
 
Last edited:
pretty good, had ~3lph after 8 hour run. i did notice that the bot still gets stuck at the second chest, i just watched it miss a gem behind chest 2 after hanging around there for a bit.
 
Back
Top