Search results

and I'm pretty sure you're trolling at this point, because that is pure nonsense. I will ask once more, politely, that if you want to discuss such significant (and in my opinion, terrible) variations in the build to open your own thread for it, so as to not take the discussion off topic.

Do you understand the line of code you are talking about is checked about 10 times a second? it isn't one "moment of cast bombardment". As long as you are moving at some point during the window that is several seconds long, it will cast it

let's do the same calculation for Hexing pants: let's even assume you have perfect rolled hexing pants, so the -dmg when not moving is just 20%. Assume that Akkarat champion is up (which means hexing pants do less), and 30% bombardment damage. Let X be the damage a normal cast of...

I didn't have any problems with this on .44, or least it wasn't nearly as noticable as it was with the latest SVN version

Nope. Your scenario is iron skin delayed 2-3 seconds right? Let's do the math for 3 seconds delay: Let X be the damage a normal cast of bombardment does. No wait: casts bomb 1.5 seconds before phys phase starts, bombs overlap phys perfectly: X*3 dmg Wait for iron skin: casts bomb...

You need to replace the 4 files this isn't included in new Trinity. Yes make sure run nephalim rift if no key is turned on. With those stats 70 will for sure be better than 71, and 69 will probably be better than 70.

Problems like that with items is a known issue in Trinity for a while now, there are many posts on this in their forums, and it's unrelated to this setup. They are working on a new townrun that will solve this I think

This isn't correct, Do you understand the line of code you are talking about is checked about 10 times a second? The checks aren't there to PREVENT casting bomb, they are there to DELAY casting it until optimal conditions. reading your third scenario I think you don't understand how iron...

This is a trinity bug in the newest version. Use an older version that worked fine instead of gutting bot logic to work better with a bug that will soon be fixed

Thanks, looks like that was indeed the problem :) For anyone else experiencing this issue, turning off everything in Trinity settings in "Advanced->TrinityLogs Directory" worked

It was based on your opinion of truth, which you are presenting as fact. The truth is you are just not noticing the huge loss of damage that is happening constantly because it's not as obvious as missed casts which happen very rarely

His suggestion to turn off movement speed check is terrible. The suggestion to ignore CoE when power pylon is a close call I think, but I still don't think it's correct. The pros: - cast "first" bombardment sooner. - (depending on how much cooldown reduction you run), you can bomb every...

Unless something weird is happening, the bot should barely ever not cast bombardment at all. If there is a bug present for you that isn't for others, solve it, don't insist on drastically changing the way the bot casts its most important ability, which is potentially extremely bad. I strongly...

Thanks for the quick reply. Weird, Im using your files exactly. perhaps it is clashing with other trinity item settings we have different

That's not how the code works, if it had time to cast bombardment, it had time to cast iron skin, since iron skin has a much lower cooldown.

Thanks Recklessness. One question though, are you also experiencing bot freezing for a few seconds before gambling/salvaging after changing to this?

I know what bug you are talking about with the pylons. I dont remember what version of trinity introduced it. I recommend getting tortoise svn so you can always get whatever version you want (right click->"tortioise svn"->"update to revision..") Here is .44 in any case see if that helps you...

This isn't supposed to be happening, bot is very very rarely supposed to be standing still.

Removing iron skin check means sometimes 1) you get 1/4 dmg instead of 0 dmg. 2) you get 1/4 dmg instead of 4/4 dmg. you are correct that (1) is a gain but you completely disregard the bigger loss in (2). I suspect this is because it is very clear visually when (1) happens but not when (2)...

This is a very important check, removing it is wrong. For every time where the bot wouldn't have cast bombardment at all there are 10 times where this check stopped it from casting a no hexing pants bomb, and cast a full dmg bomb 1 second later.