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

nergoza

New Member
Joined
Aug 13, 2012
Messages
72
Reaction score
0
In GR - the bot attacks the rift guarding for a few times and that's it - he just standing still and let the boss kill him all over till he closes the game due to many deaths.
The bot as a wizard always uses teleport for unknown reason even though teleport OOC is not selected.

What you did to the bot to make him this bad?
 
I'm doing GR74 without any issues - when bot meets the RG and waste all the time left by dying because he dont fight..
 
have to agree wich is why most are using old versions of trinity and adventirer and last timei dl the bot it didnt even come with the new trinity.
 
All of these people with issues should try a completely fresh install. I am farming keys with my wiz and running 75s on my crusader with no issues with the newest beta.
 
I've got a hilarious issue with my 4 crusaders using the latest SVN version with a custom weighting.cs so that it doesn't skip 50%+ elites. I used .31 before and I didn't have the issue back then. Basically what happens at the Rift Guardian is that the bots keeps moving away from the guardian and only the guy who has the guardian chasing him is really fighting. It's like the bots are waiting to kite the boss but since he is going for another player they just stand there waiting... and waiting... =P
 
In GR - the bot attacks the rift guarding for a few times and that's it - he just standing still and let the boss kill him all over till he closes the game due to many deaths.
The bot as a wizard always uses teleport for unknown reason even though teleport OOC is not selected.

What you did to the bot to make him this bad?
I'm sorry to hear that, but you forgot to mention what build you're running.
 
I've got a hilarious issue with my 4 crusaders using the latest SVN version with a custom weighting.cs so that it doesn't skip 50%+ elites. I used .31 before and I didn't have the issue back then. Basically what happens at the Rift Guardian is that the bots keeps moving away from the guardian and only the guy who has the guardian chasing him is really fighting. It's like the bots are waiting to kite the boss but since he is going for another player they just stand there waiting... and waiting... =P
What custom weighting? Can I see it? Sounds like they're trying to avoid. Have you tried turning avoidance off?
 
What custom weighting? Can I see it? Sounds like they're trying to avoid. Have you tried turning avoidance off?

I was at .31 and stuff seemed okay, modified autofollow so that my followers use steed and then I decided to use the svn version of Trinity yesterday night. It started skipping A LOT, basically half of the packs left untouched then I remembered a thread and I replaced my weighting.cs with the one from the post. It started doing quite ok after that.

https://www.thebuddyforum.com/demon...skips-elites-progress-globes.html#post2155405

Haven't been messing with avoidances at all really myself, just used the "All In One" guide for LoN, pasted in the combat section of his xml to mine.
 
I'm surprised you like that version better. It has a lot of old bugs that have been fixed since. The only thing I noticed there that would be doing anything with regards to elites is that he jacked the elite weights up by a lot. I guess the only way this would work is if there's something somewhere that's outweighting elites with trinity's standard weight, in which case it's just a matter of finding out what and lowering it.
 
I can't say it's doing bad atm, 70s in 5-7min. Without the file it skipped so much that it went to 10-12min.

Here's a screenshot of the settings I've been using, same for both weighting files.
trin.webp
 
That default cluster radius is too small honestly. I'm going to have to change the default for that. Can you try increasing it to 40~45 and try the old weighting again?
 
That default cluster radius is too small honestly. I'm going to have to change the default for that. Can you try increasing it to 40~45 and try the old weighting again?

Yep that seems to be the issue, I'll keep trying it a bit though.

Got the newest trinity with the newest weighting from the svn and set it to 45, not a single Elite skipped for 80% of a rift and then I decided to change it back to 15. Skipped the last two half dead ghosts of a blue pack instantly.
 
Increasing the radius seems to make them target trash a bit too much tho, even increasing the minimum trash to 15 doesn't help. Something is making that increased weight of the EliteFormula function really help a lot since you can run reduced radius.
 
You said you're using the latest version from SVN right? Turn off 'Attack Mobs When Blocked' and the trash slider should work properly again. Also, great to hear that it got better! Can you keep running it like that to see if it works reliably?

By the way, I feel like I should mention this: there are some enemies that alone have a 15 yard radius, so you should really never run with a cluster radius that small unless you only want to attack small enemies or something like that.
 
Last edited:
I've had that setting turned off since it said so in the comment of the commit =)

I tried like 5 rifts or something with the 45 radius and original weighting but it's around 20-30% slower than changing all of those eliteformula values to 45000d for me (I changed them in the svn weighting.cs now). One thing that does seem to happen at least is that with the original values the crusaders are spreading out way more instead of focusing on the elite. But ye with the higher radius it doesn't skip elites at least...
 
I've had that setting turned off since it said so in the comment of the commit =)

I tried like 5 rifts or something with the 45 radius and original weighting but it's around 20-30% slower than changing all of those eliteformula values to 45000d for me (I changed them in the svn weighting.cs now). One thing that does seem to happen at least is that with the original values the crusaders are spreading out way more instead of focusing on the elite. But ye with the higher radius it doesn't skip elites at least...
Here's the thing. I'm strongly against using weighting values that high. We went down that road before and we ended up in a really nasty place. Everything was either max weight or ignored because everyone wanted higher priority for something else because we kept 'fixing' it like this new weighting file does. So I really want to find something else that works here.

What's your 'Always ignore below %' set to? And how about 'Always kill clusters with a total value above %'? I recommend somethign like .2 and 10, respectively. Can you try that? If it doesn't work I guess I could even increase the max value for the trash slider from 15 to 20.
 
All of these people with issues should try a completely fresh install. I am farming keys with my wiz and running 75s on my crusader with no issues with the newest beta.

Seriously! This!

I've had this same problem many times before. The bot stops doing anything smart. Sometimes settings get corrupted, and there is nothing you can do. Make a note of your settings, export what you can, and start over from a fresh install. It helps!!
 
That default cluster radius is too small honestly. I'm going to have to change the default for that. Can you try increasing it to 40~45 and try the old weighting again?
that fixed my issues of skipping elites lol, for some reason mine was at 15 aswell.
 
Back
Top