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

[Plugin] Giles Trinity

Status
Not open for further replies.
Im not really sure if your Plugin does that but at the end of each run DB says the ammount of gold earned in the run... would it be possible to display the duration of that run aswell please ? Something like " This run lasted 45 min and earned 170k gold" for example.
 
Something must be wrong with Whirlwind barb.

Sure it pops berserker perfectly and runs sorta nicely but whenever it encounters a mob it pops whirlwind and runs in the opposit direction of where the mob is runnng like 10-15 yards in the wrong direction
It does this to all mobs even goblins and that causes it to loose the goblin and just run away continuing the run and letting goblin get away


Nop 1.4.4 didnt fix it. still does it
 
Clearly user error here.


Sounds like:

A-You aren't nearly geared well enough
B-Your spec sucks.
C-You are trying to use conflicting plugins?
A, B - gear and spec is same it was 2 days ago, when I hadn't such problems.
C - Trinity, Rads Profile Manager and UnstuckMe.
I tell you about problems in bot behaviour, it's not about gear or spec. Doesn't avoid normally, doesn't use rend when it's really needed and uses when it's not needed.
 
A, B - gear and spec is same it was 2 days ago, when I hadn't such problems.
C - Trinity, Rads Profile Manager and UnstuckMe.
I tell you about problems in bot behaviour, it's not about gear or spec. Doesn't avoid normally, doesn't use rend when it's really needed and uses when it's not needed.

Something on YOUR end is still jacked up. I have 5 barbs using this currently in act 3, and they all are working just fine; and that goes without saying that this is working at probably 95% efficiency for everyone else here with little or no issues. Remove unstuck me for starters; giles newer versions has a built in unstuck function. What is your TPS set at? What is your computer usage (%) at? Did you delete your compiled assemblies, whats your FPS on d3 set at (foreground and background), double check you are on 1.4.4, and delete your gilesconfig.cfg file before STARTING the bot?
 
A, B - gear and spec is same it was 2 days ago, when I hadn't such problems.
C - Trinity, Rads Profile Manager and UnstuckMe.
I tell you about problems in bot behaviour, it's not about gear or spec. Doesn't avoid normally, doesn't use rend when it's really needed and uses when it's not needed.
Post your build. Something sounds like it's wrong. Perhaps you have something that is fast attack yet somehow being prioritized higher than rend.

However it seriously sounds like that, despite what you say above, you haven't actually done a clean install. Close DemonBuddy, delete "CompiledAssemblies" folder in your DemonBuddy folder, and restart DB. This isn't as good as a clean install, but is the next best thing. Do you have other plugins in your plugins folder that are disabled, but still there? Are you selecting "GilesPlugin" as the combat-routine choice when you hit "Start"? Have you tried the change I suggested in this post;
[url]http://www.thebuddyforum.com/demonbuddy-forum/plugins/67705-plugin-giles-trinity-59.html#post707964[/url]

To see if that improves things at all?

Have you tried altering the Rend code manually to increase usage (personally I find mine spamming Rend almost too much, but there we go :)). Have you changed your skills while DB is already running (this is never good)? Have you tried starting DemonBuddy while on the character select screen and letting it log in and run the routine for you, rather than entering a game first before clicking start?

You're the only barbarian that has posted saying something so dramatic as to say your deaths per hour have actually dramatically INCREASED with 1.4.4 Trinity, so I can only assume that you have done something wrong, or you have an unusual skill build that most barbs don't have and one of the skills you rely on got changed for the worse in 1.4.4.
 
I double checked the ActorSNOs for both of the arcane sentrys. They are right in the code, but I'm wondering if DB is reporting their distance incorrectly? In the log window, DB reported an Arcane Sentry 23 yards away from me, but I was actually standing right next to it. Maybe someone else could check that?

Interesting. Here, a little log line to insert into the code for debugging purposes.

Find this comment line;
Code:
// Remove ice balls if the barbarian has wrath of the berserker up, and reduce health from most other SNO avoidances

*ABOVE* this, insert this code, so it now looks like this;
Code:
                        // Spammy debug messages for arcanes
                        if (tmp_iThisActorSNO == 219702 || tmp_iThisActorSNO == 221225)
                        {
                            Logging.Write("Arcane Debugger. SNO=" + tmp_iThisActorSNO.ToString() + ". Distance from your character is apparently: " + tmp_fCentreDistance.ToString() +
                                ". Arcane avoidance health=" + dictAvoidanceRadius[tmp_iThisActorSNO].ToString() + ". Radius=" + dictAvoidanceRadius[tmp_iThisActorSNO].ToString() +
                                ". Your health=" + playerStatus.dCurrentHealthPct.ToString());
                        }
                        // Remove ice balls if the barbarian has wrath of the berserker up, and reduce health from most other SNO avoidances

This will spam the DB log-window (as long as logging is set to at least "normal" in the settings tab of DB) constantly whenever there are arcane objects detected - spamming their supposed distance from your character (for each object), their AOE avoidance % (decimal from 0-1), their radius, and your current health % (decimal 0-1). Have a go with that and see if it is reporting the correct data and not avoiding when it should be, or if it's NOT reporting the correct data which would explain the lack of avoidance (and might mean we can do some sort of hacky workaround to calculate a more accurate distance, if the distance isn't being centred on the *ACTUAL* middle).
 
I've implemented the logging code and will get back with you on that. In the mean time, I see this in my item stats log:

Items dropped by quality:
- Legendary: 7 [5.65 per hour] {2.3 %}
--- ilvl 61 Legendary: 7 [5.65 per hour] {2.3 %}

Items picked up by quality:
- Legendary: 1 [0.81 per hour] {9.09 %}
--- ilvl 61 Legendary: 1 [0.81 per hour] {9.09 %}


Is it possible that the plugin just reported the wrong data for the number of items dropped? I only had 1 legendary in the bag, it was a iLvl 61 staff.
 
Something on YOUR end is still jacked up. I have 5 barbs using this currently in act 3, and they all are working just fine; and that goes without saying that this is working at probably 95% efficiency for everyone else here with little or no issues. Remove unstuck me for starters; giles newer versions has a built in unstuck function. What is your TPS set at? What is your computer usage (%) at? Did you delete your compiled assemblies, whats your FPS on d3 set at (foreground and background), double check you are on 1.4.4, and delete your gilesconfig.cfg file before STARTING the bot?
Giles unstucker doesn't help me in some places in Act 3, so I have to use UnstuckMe. I didn't enable TPS. I observe the mentioned problems in active window with 120 FPS. Firstly I've just upgraded plugin as it is said in instruction, then deleted the whole DB and reinstalled.
Post your build. Something sounds like it's wrong. Perhaps you have something that is fast attack yet somehow being prioritized higher than rend.

However it seriously sounds like that, despite what you say above, you haven't actually done a clean install. Close DemonBuddy, delete "CompiledAssemblies" folder in your DemonBuddy folder, and restart DB. This isn't as good as a clean install, but is the next best thing. Do you have other plugins in your plugins folder that are disabled, but still there? Are you selecting "GilesPlugin" as the combat-routine choice when you hit "Start"? Have you tried the change I suggested in this post;
[url]http://www.thebuddyforum.com/demonbuddy-forum/plugins/67705-plugin-giles-trinity-59.html#post707964[/url]

To see if that improves things at all?

Have you tried altering the Rend code manually to increase usage (personally I find mine spamming Rend almost too much, but there we go :)). Have you changed your skills while DB is already running (this is never good)? Have you tried starting DemonBuddy while on the character select screen and letting it log in and run the routine for you, rather than entering a game first before clicking start?

You're the only barbarian that has posted saying something so dramatic as to say your deaths per hour have actually dramatically INCREASED with 1.4.4 Trinity, so I can only assume that you have done something wrong, or you have an unusual skill build that most barbs don't have and one of the skills you rely on got changed for the worse in 1.4.4.
Thanks for reply. I reinstalled DB and all plugins to a new folder. I haven't got any plugins except Trinity, Rads and UnstuckMe. I'm selecting "GilesPlugin" as combat routine. I will try what you suggested in those links now.
I haven't tried to alter Rend code, I'll try it now. I haven't changed skills ever. I'm starting DB from the character select screen.
My build is: WotB (thrive on chaos), War Cry (Impumnity), Battle Rage (Maradeurs Rage), Revenge (Provocation), Frenzy (Maniac), Rend (Blood lust).
Due to the other comments I see that's mostly my problem, I'll try to experiment how to fix it. Great thanks Giles.
 
Giles unstucker doesn't help me in some places in Act 3, so I have to use UnstuckMe. I didn't enable TPS. I observe the mentioned problems in active window with 120 FPS. Firstly I've just upgraded plugin as it is said in instruction, then deleted the whole DB and reinstalled.

Thanks for reply. I reinstalled DB and all plugins to a new folder. I haven't got any plugins except Trinity, Rads and UnstuckMe. I'm selecting "GilesPlugin" as combat routine. I will try what you suggested in those links now.
I haven't tried to alter Rend code, I'll try it now. I haven't changed skills ever. I'm starting DB from the character select screen.
My build is: WotB (thrive on chaos), War Cry (Impumnity), Battle Rage (Maradeurs Rage), Revenge (Provocation), Frenzy (Maniac), Rend (Blood lust).
Due to the other comments I see that's mostly my problem, I'll try to experiment how to fix it. Great thanks Giles.

You're build is pretty standard, so that shouldn't be an issue.

Does it look like your guy is "laggy" or anything? How are your stats?
 
I've implemented the logging code and will get back with you on that. In the mean time, I see this in my item stats log:
Items dropped by quality:
- Legendary: 7 [5.65 per hour] {2.3 %}
--- ilvl 61 Legendary: 7 [5.65 per hour] {2.3 %}
Items picked up by quality:
- Legendary: 1 [0.81 per hour] {9.09 %}
--- ilvl 61 Legendary: 1 [0.81 per hour] {9.09 %}
Is it possible that the plugin just reported the wrong data for the number of items dropped? I only had 1 legendary in the bag, it was a iLvl 61 staff.

Yeah the stats being wrong is more likely that 6 legendaries dropping every hour :P I've been playing with using different "unique keys" for items for the stat tracking, there's quite a few variables possible (from dynamic id, to ractorguid, to acdguid), I haven't yet worked out if certain variables get "re-used" by other objects or not.
 
Giles. I absolutely love the plugin.
I've been meaning to come mention that for quite some time.

Lately the barb has been doing this odd twitching stuck thing, but I've turned off all open container and backtracking in order to fix that and things seem fine.
It would be nice to be able to turn those back on, but hey, the whole "gift horse mouth" thing you know. lol.


So many props for all this work, you're a wonderful programmer.
Not enough people show you the love you deserve.
 
Yeah the stats being wrong is more likely that 6 legendaries dropping every hour :P I've been playing with using different "unique keys" for items for the stat tracking, there's quite a few variables possible (from dynamic id, to ractorguid, to acdguid), I haven't yet worked out if certain variables get "re-used" by other objects or not.


After implementing the logging code, I've ran into several packs with arcane, and it doesn't appear to log anything to the DB window, or the actual logfile. Here's the log of this session, the last arcane pack I run into happens at [18:14:18.109].

edit; just to mention my logging is set to Diagnostic in the DB settings.
 

Attachments

Last edited:
to those picking up more than 30 rares per hour:
Can you post your stats?
Rares/hour:
DPS (unbuffed):
Resists:
Armor:
Life:
Deaths/hour:
Strength:
LoH:
LifeLeech:
Crit%:
CritDMG%:
Block%:
Movespeed%:
Build:


===== Misc Statistics =====
Total tracking time: 4h 37m 34s
Total deaths: 30 [6.48 per hour]


Items picked up by quality:
- Magic: 42 [9.16 per hour] {21.32 %}
--- ilvl 60 Magic: 11 [2.4 per hour] {5.58 %}
--- ilvl 61 Magic: 5 [1.09 per hour] {2.54 %}
--- ilvl 62 Magic: 4 [0.87 per hour] {2.03 %}
--- ilvl 63 Magic: 22 [4.8 per hour] {11.17 %}
- Rare: 152 [33.16 per hour] {77.16 %}
--- ilvl 60 Rare: 6 [1.31 per hour] {3.05 %}
--- ilvl 61 Rare: 77 [16.8 per hour] {39.09 %}
--- ilvl 62 Rare: 46 [10.04 per hour] {23.35 %}
--- ilvl 63 Rare: 23 [5.02 per hour] {11.68 %}
- Legendary: 3 [0.65 per hour] {1.52 %}
--- ilvl 52 Legendary: 1 [0.22 per hour] {0.51 %}
--- ilvl 62 Legendary: 1 [0.22 per hour] {0.51 %}
--- ilvl 63 Legendary: 1 [0.22 per hour] {0.51 %}


Lots of deaths i know but the rewards far outweigh the run back...im running with some MF gear on, so thats why...
DPS :unbuffed 46k, 55k buffed
resists : 905 - buffed
armor : 7k <-- low which is probably why i die alot...
deahts p/h : 7-ish
strength : 1600
LoH : 1800
Lifesteal : 2.9
crit : 44
crit dmg : 350
WW barb, no block
Movespeed : 72% w/wotb lol 24%without
build skill/rune : bash/instigation, WW/hurricane, sprint/run like wind, wotb/thrive on chaos, battle rage/into the fray, warcry/impunity.



(wow thats sad i know all myskills without alt-tabbing back to look at them, just realized i did....)

ITS ALL NOT POSSIBLE WITHOUT GILES, WE LOVE YOU BRO! NO HOMO! <---even though its plurpl lol
 
Guys, I've solved my problems.
I'm not totally sure, but it seems that setting TPS to 15 made bot reacting and fighting much faster.
I also have changed if (iLoopsSinceLastTargetUpdate > 8) to 4 and tried to force more frequent rend casting. Also set % of hp in avoidance settings to 55-60 in most cases.
Now I have again not more 2 deaths per hour.

Btw is it normal to have 8 FPS in background mode? How can I improve it? All graphic setting are at minimum.
Also it seems to me that health globes picking is not prioritized as it should be.
 
Hey Giles,

is there a chance to put in something like "let inventory always open?"

i wanna see the loot, but everytime i must press I on every window :/

is there chance for this little option? ^.^
 
my bot isnt using sweeping winds at all, no matter how many monsters are around and no matter if he used blind or theres elites. not sure why

if anyone has a fix please tell me

(EDIT: restarted bot and it works now, could be cuz of my relogger i guess???)
 
Hey Giles,

is there a chance to put in something like "let inventory always open?"

i wanna see the loot, but everytime i must press I on every window :/

is there chance for this little option? ^.^

Yeah that's really important !
Soon people are gonna ask for the plugin to make them a sandwich :D
 
Guys, I've solved my problems.
I'm not totally sure, but it seems that setting TPS to 15 made bot reacting and fighting much faster.
I also have changed if (iLoopsSinceLastTargetUpdate > 8) to 4 and tried to force more frequent rend casting. Also set % of hp in avoidance settings to 55-60 in most cases.
Now I have again not more 2 deaths per hour.

Btw is it normal to have 8 FPS in background mode? How can I improve it? All graphic setting are at minimum.
Also it seems to me that health globes picking is not prioritized as it should be.

In Menu>Options>Video, did you uncheck/increase max background fps? Not sure if that's what caused your problem in the first place.
 
Status
Not open for further replies.
Back
Top