Yes, but that only applies 10% towards legendary drops. So even using subpar gear in order to hit the MF cap, you only end up with 30% more legendaries than normal. I would assume that in most cases the better gear is more valuable since it lets you clear the runs faster (or on a higher torment, which also increases legendary chances by some undisclosed amount).
I ran this profile on Torment 1 for 20 hours, Torment 2 for 20 hours and Normal for 12+ hours. So far, I've gotten a little less than 1 legendary per hour (.7 to .9) on either Torment difficulty. I currently have 1.91 legendaries per hour on Normal, and there isn't any sign of this stopping. It could very well be the case that putting on 300% mf gear and cruising through normal is exactly what you should do.
would ignoring elites and doing t6 be better or should i do like t3?? and which profile , FAST, ONLY, FULL?
tbf im ignoring pretty much all elites unless i notice their half dead due to all the aoe then i will finish them off, otherwise its trash packs and skip/run away from the elites. They just dont seem a viable use of time, along with the rewards. All my upgrades and legs so far have come from trash. Even when i was clearing by hand etc
its a bug of old version - if you donk finish quest with last version - you doing smthing wrong - no bugs to me
Man I have such back luck with this profile. I ran for 20 hours on normal, get less legs than doing COTA T6. Very nice profile though, but my bad luck! Guess time to go back to your cota profile.
okay well then i would benefit more from running t6 and just ignore elites and kill the trash and stuff?? im going for purely leg, im running a wizard currently.. im geared very well ..paragon 320. anyways just was curious about this i noticed most was from trash as well..
at the legacy of cain part the bot runs loops...wtf Oô http://www.thebuddyforum.com/demonb...totally-given-up-weird-bug-3.html#post1436176 fixed?
hey guys.. just to let you know that my game crashed twice since I started using this profile. I'm using the lastest Demonbuddy and Trinity builds.
I'm just saying.. I played for a year without demonbuddy, never crashed. Started using Demonbuddy 2 days ago and tried 2 other profiles without issues. I started using this one yesterday and it froze the game once and I woke up this morning with both applications closed and a Blizzard error message. Your profile works great, i'm just giving feedbacks in case someone already saw this kind of issue.
just let you know - there is an old bug, when bot stashing maths after salvaging, the d3 can crash, it happens time to time and devs confirm that long time ago but cant fix you can turn off salvaging at all and you will see
This is an excellent profile Spacey However at what triggerrange should i put for trash mobs ? I've seen the bot run all the way pass Sarkoth's home, and then almost run back to the bridge - i figure this is because it chases mobs that are close... I have it currently set to 40.... J.
Thanks a million! Been running this profile for 36 hours now, without any stucks or disconnects. 3-4 leg/hour and 350 mil xp/hour.
hi, i'm now getting this? Code: Failed to load profile: Element TrinityMoveTo is not supported. Please check your XML and try again. (<TrinityMoveTo questId="1" x="2906.414" y="2797.841" z="24" pathPrecision="8" />) Line 29 System.Exception: Element TrinityMoveTo is not supported. Please check your XML and try again. (<TrinityMoveTo questId="1" x="2906.414" y="2797.841" z="24" pathPrecision="8" />) Line 29 at ..(PropertyInfo , XElement , Object ) at Zeta.XmlEngine.XmlEngine.Load(Object obj, XElement element) at ..(XElement , Type ) at ...(XElement ) at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext() at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection) at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source) at ..(XElement , PropertyInfo ) at ..(PropertyInfo , XElement , Object ) at Zeta.XmlEngine.XmlEngine.Load(Object obj, XElement element) at Zeta.Bot.Profile.Profile.Load(XElement element, String path) at Zeta.Bot.Profile.Profile.Load(String path) at Zeta.Bot.ProfileManager.Load(String profilePath, Boolean rememberPath) might have been the plugin updater breaking stuff..
