where it is correct?
Not sure, what you mean?
what attack did u switch out? hungering arrow or multi shot?
I did not switch any out of my skill, since I only used Hungering arrow and multi shot
I just changed the way giles uses the shots.
where it is correct?
what attack did u switch out? hungering arrow or multi shot?
Requesting fix for teh above stated issue
the DH just stands there shooting in the direction that the mobs will spawn ... but wont spawn until you move abit closer ..
Dont know if it would be possible to set some kind of option that is like "if X mobs, be in 30yard range when killing" ish
Thanks in advance
**Update**
fixed it myself... its a very very dirty and quick fix ....
Basicly i edited the trinity file so that it will only use multishot and hungering arrow (the 2 skills i use) if there is any mobs in a 50 feet radius (default is 69f)
And since my kill radius is set to 50 its fine for me
That solved it for me...
Hungering arrow:
in line 7737 i changed the "69f" to 50f
So the line will look like this
return new GilesPower(SNOPower.DemonHunter_HungeringArrow, 50f, vNullLocation, -1, targetCurrent.iThisACDGUID, 0, 0, USE_SLOWLY);
Multi shot
Changed line 7637 to 7639 to this
(iElitesWithinRange[RANGE_40] >= 1 || iAnythingWithinRange[RANGE_40] >= 2 || ((targetCurrent.bThisEliteRareUnique || targetCurrent.bThisTreasureGoblin || targetCurrent.bThisBoss) && targetCurrent.fRadiusDistance <= 50f)))
{
return new GilesPower(SNOPower.DemonHunter_Multishot, 50f, targetCurrent.vThisPosition, iCurrentWorldID, -1, 1, 1, USE_SLOWLY);
So now it should only use thoes 2 skills to mobs within a 50 feet radius of the char...
I'm not a specialist, so i'm not sure what this does 100% , but it seems to have fixed the problems with the winged dicks... and to my understanding it will also only shoot at goblins if they are closer then 50 feets.
USE IT AT YOUR OWN RISK!
oh and btw
Its working as it was coded, so its not broken...
Its not very useful, but definitely not broken![]()
Thank you, it works now. do i have to keep changing the cs file every time their is a new trinity update? seeing as how it has been said that the plugin is working as intended.
so, shareI have made a little modification too and want to share, if you have some gear to do in nightmare with mp and no problems i suggest that change values of the use of rain of vengeance to use it all the time because it will kill monsters for you and don't stop the bot.
kill monsters that were beyond the normal range at which AI is triggered - this is especially true for DXWe've recently issued several rounds of account bans for cheating in Diablo III. In each of these cases players used a hack program for exploitive purposes, for example to zoom out their game view and kill monsters that were beyond the normal range at which AI is triggered. As we do with all Blizzard games, we will continue to monitor Diablo III for cheating and take action as needed.
As a reminder, we don't permit the use of hacks or other third-party software in conjunction with Diablo III. Most of the programs out there that are intended for use with the game are actually cheat programs and automation programs ("bots") that exploit Diablo III's mechanics and provide players with an unfair advantage. However, "third-party software" also refers to any file or program that attempts to:
- Obtain information about Diablo III that's not normally available to the player
- Transmit or modify the Diablo III game files
- Provide access to features or abilities beyond what is allowed by the game's design
- Change how Diablo III interacts with Battle.net
In addition to undermining the spirit of fair play, this type of software can cause nasty technical problems, game-related bugs, and stability and performance issues with Battle.net. All of which can put a demon-sized damper on your gaming experience.
As we've said in the past, playing Diablo III legitimately means playing with an unaltered game client. We strongly recommend that you avoid using any third-party software which interacts with Diablo III—even if you are accessing that software from a reputable third-party site—as doing so can result in permanent ban from the game.
For more information on all of this, you can check out a copy of the related policy for Diablo III over on our Customer Support site.
Any idea how to avoid Trinity from blacklisting trash mobs? My DH seems to shoot one arrow to normal mobs and then forget about them, so sometimes as they don't die from that one shot, it just carries a bunch of mobs following...
I'm usually using range 40, so that is not the problem. The issue is that even mobs in range 10-15 get ignored while the DH keeps running the profile. For example in Tower of the Damned, the DH keeps running despite it has 2-3 red devil mobs (the ones that came from below and jump to the path) and doesn't even bother killing them. Once it reaches a mob group and the red devils get to melee and hit the bot, then the bot kills them.Up the trash killing range in the config
(standard is 18)
"Trigger Range for non-Elite Combat" is basicly the same as kill radius in DB.
So up that to w/e and your DH is killing stuff
Index: C:/Demonbuddy/Plugins/GilesTrinity/GilesTrinity.cs
===================================================================
--- C:/Demonbuddy/Plugins/GilesTrinity/GilesTrinity.cs (revision 31)
+++ C:/Demonbuddy/Plugins/GilesTrinity/GilesTrinity.cs (revision 32)
@@ -17195,6 +17195,8 @@
if (GilesTrinity.hashPowerHotbarAbilities.Contains(SNOPower.DemonHunter_Vault) && !bTooMuchZChange &&
DateTime.Now.Subtract(GilesTrinity.dictAbilityLastUse[SNOPower.DemonHunter_Vault]).TotalMilliseconds >= GilesTrinity.settings.iDHVaultMovementDelay &&
fDistanceFromTarget >= 18f &&
+ ZetaDia.Me.CurrentSecondaryResource >= 28 && // We can afford the discipline
+ (!GilesTrinity.hashPowerHotbarAbilities.Contains(SNOPower.DemonHunter_Preparation) || PowerManager.CanCast(SNOPower.DemonHunter_Preparation)) && // Preparation is not on cooldown
PowerManager.CanCast(SNOPower.DemonHunter_Vault) && !ShrinesInArea(vMoveToTarget))
{
Vector3 vThisTarget = vMoveToTarget;