[Plugin] Giles Trinity
- Thread starter GilesSmith
- Start date
- Status
Nudge
New Member
- Joined
- Jun 16, 2012
- Messages
- 44
- Reaction score
- 0
It's leaving after 2 deaths due to your settings in Rads profile manager. Go to its config and change the settings.
How can I set the plugin to set a very high priority to kill Fallen Prophets? He just stands there constantly killing the revived grunts and cannot kill them fast enough to move onto killing the Prophets. This dramatically slows my runs down especially if there is a few Prophets in one spot and they revive faster then I can kill.
Last edited:
Ok ive been using Trinity v1.1 since its been the smoothest for me even without the avoidance. i seem to only die in nasty packs. i just reverted to v1.3.1 and with a bit of tweaking the avoidance seems to be OK, im leaving it overnight and ill check back and report what i see once i read the logs.
In the meantime, these are issues that I currently see with v1.3.1:
1) Bot does not pickup Health globes % hp specified nor does it pick them up or use the skill in a timely manner. I changed the heal globe % down to 35% and it seems to wait til its about 20% before trying to get one, sometimes it doesnt even try.
2) The bot no longer attacks smoothly, especially with Frenzy. When there 2 or more units within melee distance, it would attack once, wait 1 second then attack again, like hit pause hit pause ..etc. I increased the ticker to 15 max. and still the same issue.
3) After walking away and targeting mobs once loot hits the floor, in v1.1 he would ALWAYS go back and pickup what was left behind, in v1.3.1 it seems that it only venture to a certain distance before continue on its path. I had set my loot radius to 150 just in case and its still happens.
4) Azmodan fight, when running away from the pool, as soon as he pops WOTB, he would go back to fight him ignoring the pools til he dies. also once on azmo, if he uses the pot once or attempt to pickup a health globe, it would not use it again even though the cooldown is fine.
In the meantime, these are issues that I currently see with v1.3.1:
1) Bot does not pickup Health globes % hp specified nor does it pick them up or use the skill in a timely manner. I changed the heal globe % down to 35% and it seems to wait til its about 20% before trying to get one, sometimes it doesnt even try.
2) The bot no longer attacks smoothly, especially with Frenzy. When there 2 or more units within melee distance, it would attack once, wait 1 second then attack again, like hit pause hit pause ..etc. I increased the ticker to 15 max. and still the same issue.
3) After walking away and targeting mobs once loot hits the floor, in v1.1 he would ALWAYS go back and pickup what was left behind, in v1.3.1 it seems that it only venture to a certain distance before continue on its path. I had set my loot radius to 150 just in case and its still happens.
4) Azmodan fight, when running away from the pool, as soon as he pops WOTB, he would go back to fight him ignoring the pools til he dies. also once on azmo, if he uses the pot once or attempt to pickup a health globe, it would not use it again even though the cooldown is fine.
Last edited:
Roflologist
New Member
- Joined
- Jul 11, 2012
- Messages
- 46
- Reaction score
- 0
is the act3 stash timeout is fixed with this trinity version? or is it te profile that causing it?
bombastic
New Member
- Joined
- Jun 18, 2012
- Messages
- 430
- Reaction score
- 3
Giles,
There are some serious issues regarding how priority is being handling on 1.3.1.
Now on several occasions the bot stop attacking Fallen Shaman to attack everything else, like their grunts or random mobs. And is not a body block issue, because the bot don't go on shamans if a grunt 7 feet away shows up. See the bot chase a shaman now (with mobs nearby) is almost impossible now, on 1.3.1.
The same thing happens with elites. Previously on giles (and belphegor) the bot never stop to attack elites to attack grey mobs (unless on a body block case). Now the bot is trying to clear other mobs first, and only then, attack elites. I saw that happened a lot of times -- and the first time was when I migrated to 1.3.1.
With goblins the same thing is happening. Bot stop to attack the goblin on several occasions, randomly changing target to mobs 5-7 feet away, and is NOT a body block issue, like all cases above.
Finally, rend is still being cast too far away from targets. When the bot is going to attack a mob, even a non-running mob, my barb cast rend before reaching the mob. Most of the time is casted wrong, actually (if barb is on the move). It's only being casted right if my barb is stading still attacking a mob within melee range.
There are some serious issues regarding how priority is being handling on 1.3.1.
Now on several occasions the bot stop attacking Fallen Shaman to attack everything else, like their grunts or random mobs. And is not a body block issue, because the bot don't go on shamans if a grunt 7 feet away shows up. See the bot chase a shaman now (with mobs nearby) is almost impossible now, on 1.3.1.
The same thing happens with elites. Previously on giles (and belphegor) the bot never stop to attack elites to attack grey mobs (unless on a body block case). Now the bot is trying to clear other mobs first, and only then, attack elites. I saw that happened a lot of times -- and the first time was when I migrated to 1.3.1.
With goblins the same thing is happening. Bot stop to attack the goblin on several occasions, randomly changing target to mobs 5-7 feet away, and is NOT a body block issue, like all cases above.
Finally, rend is still being cast too far away from targets. When the bot is going to attack a mob, even a non-running mob, my barb cast rend before reaching the mob. Most of the time is casted wrong, actually (if barb is on the move). It's only being casted right if my barb is stading still attacking a mob within melee range.
A setting to even prioritize Shamans/Prophets over any other monster including even elites would be awesome(except Gobs maybe) This would make fighting elites so much easier as the bot wont run frantically all over the place instead of focusing the elites. Say there are x3 Shamans next to an elite pack. It should go Boom boom boom shamans down then rape the Elites. Would make things so much smoother.
MrWizard516
Member
- Joined
- Jan 18, 2011
- Messages
- 586
- Reaction score
- 5
Giles, thanks again for all your hard work. It is much appreciated by all. I was wondering if it would be possible for you to add in the ability to keep items based on stats we choose rather then just by weight. Something simliar to the way you can filter items in the AH. Of course only filter main stats not class specfic stats. Something like this would be awesome. I for one have seen the the bot keep items that wont sell in the AH because they only had high GF or MF on them. Once again thanks for all your hard work. I can't wait to see what you come up with next.
I'm getting this too. Frenzy attacks at less than half of what it could be, but not in all areas and not all the time. Don't know what causes it.
Last edited:
Sorry, I'm just quoting my initial question as I have another issue to add to it.
I have noticed that the inventory window (most of the time) does not close down after selling items and then leaving town, so the bot is running around the battlefield with an open inventory window. Is there any way to prevent this from happening? Not too sure of Blizz could pick up on this as a bot feature, because after all, who runs around fighting with an open inventory.
stanle_98
New Member
- Joined
- Aug 27, 2012
- Messages
- 3
- Reaction score
- 0
CCCComboBreaker
New Member
- Joined
- Jun 25, 2012
- Messages
- 56
- Reaction score
- 0
It stays in the menu after 2-3 runs, with this message in the status bar: Town run: salvage routind started
- Status