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

A glitch causing a 15 second loot delay for in-geom monks.

Flebar

New Member
Joined
Sep 22, 2015
Messages
25
Reaction score
0
Hi, as I said, there is a glitch causing the bot to repeatedly dash towards loot lying on the ground until the dash is on cd, which if you're an in-geom monk, can cause a 15 second loot delay after killing Elites some of the time.
Here's what demonbuddy says during the event.
[Trinity 2.13.35] Dash towards: at x="426" y="428" z="0" dist=10, charges=2
[Trinity 2.13.35] Dash towards: at x="426" y="428" z="0" dist=27, charges=2
[Trinity 2.13.35] Dash towards: at x="402" y="391" z="0" dist=47, charges=2
[Trinity 2.13.35] Dash towards: at x="239" y="455" z="0" dist=93, charges=2
[Trinity 2.13.35] Dash towards: at x="333" y="495" z="0" dist=74, charges=2
[Trinity 2.13.35] Dash towards: at x="333" y="495" z="0" dist=99, charges=2
[Trinity 2.13.35] Dash towards: at x="333" y="495" z="0" dist=84, charges=2
[Trinity 2.13.35] Dash towards: at x="333" y="495" z="0" dist=101, charges=2
[Trinity 2.13.35] Dash towards: at x="333" y="495" z="0" dist=112, charges=2
[Trinity 2.13.35] Dash towards: at x="242" y="444" z="0" dist=20, charges=2
[Trinity 2.13.35] Dash towards: at x="242" y="444" z="0" dist=2, charges=2
[Trinity 2.13.35] Dash towards: at x="244" y="457" z="0" dist=0, charges=2
[Trinity 2.13.35] Dash towards: at x="244" y="457" z="0" dist=6, charges=2
[Trinity 2.13.35] Dash towards: at x="244" y="457" z="0" dist=11, charges=2
[Trinity 2.13.35] Dash towards: at x="244" y="457" z="0" dist=6, charges=2
[Trinity 2.13.35] Dash towards: at x="244" y="457" z="0" dist=11, charges=2
[Trinity 2.13.35] Dash towards: at x="244" y="457" z="0" dist=6, charges=2
[Trinity 2.13.35] Dash towards: at x="244" y="457" z="0" dist=11, charges=2
[Trinity 2.13.35] Dash towards: at x="244" y="457" z="0" dist=6, charges=2
[Trinity 2.13.35] Dash towards: at x="244" y="457" z="0" dist=11, charges=2
[Trinity 2.13.35] Dash towards: at x="244" y="457" z="0" dist=6, charges=2
[Trinity 2.13.35] Dash towards: at x="244" y="457" z="0" dist=11, charges=2
[Trinity 2.13.35] Dash towards: at x="244" y="457" z="0" dist=6, charges=2
[Trinity 2.13.35] Dash towards: at x="244" y="457" z="0" dist=0, charges=2
[Trinity 2.13.35] Dash towards: at x="244" y="457" z="0" dist=6, charges=2
[Trinity 2.13.35] Dash towards: at x="244" y="457" z="0" dist=11, charges=2
[Trinity 2.13.35] Dash towards: at x="244" y="457" z="0" dist=6, charges=2
[Trinity 2.13.35] Dash towards: at x="244" y="457" z="0" dist=11, charges=2
[Trinity 2.13.35] Dash towards: at x="244" y="457" z="0" dist=6, charges=2
[Trinity 2.13.35] Dash towards: at x="244" y="457" z="0" dist=2, charges=2

It just keeps on dashing until it gets on cooldown.
 
This is most likely a DB/Trinity issue, i've encountered this many times with different profiles, bot starts dashin and if path is blocked it will keep dasing until dashing strike has a CD again (same happens if you get channeling pylon)
 
Back
Top