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

Rift Bot - Yet Another Rifting Profile!

legnotification said:
thank you!

i was monitoring my bot for a while but ran into a problem.

after rift guardian is down, toon goes back to town, goes back into the rift portal.
it then says rift guardian is down, so repeats this again and again infinitely.
eventually the gold inactivity thing forces him to leave.
is there a way to fix this/?
Click to expand...

Are you sure you're running latest Trinity/Quest Tools/DemonBuddy and rift profile?

Trinity 1.9.8, Quest Tools 2.0.82, DemonBuddy beta 415 or release version 362 and RiftBot revision 336?
 
Last edited:
Oksehode said:
Are you sure you're running latest Trinity/Quest Tools/DemonBuddy and rift profile?

Trinity 1.9.8, Quest Tools 2.0.82, DemonBuddy beta 415 or release version 362 and RiftBot revision 335?
Click to expand...

do i need to manually do that even with ez updater?

edit:

i just checked and everything was the right version except for riftbot revision 336.
where can i find this download?
 
Last edited:
so weird, i've been running this profile for weeks with no problems, then yesterday out of nowhere, i get hit with network disconnects by the d3 client.
loaded up my other db install, and ran ghom overnight no issues, loaded up riftbot again, and baam network disconnect errors again. Anyone know whats up with that?

I doubt it is a profile issues. i have a friend that gets the issue running ghom, but no issues running riftbot.
 
rayofsi said:
so weird, i've been running this profile for weeks with no problems, then yesterday out of nowhere, i get hit with network disconnects by the d3 client.
loaded up my other db install, and ran ghom overnight no issues, loaded up riftbot again, and baam network disconnect errors again. Anyone know whats up with that?

I doubt it is a profile issues. i have a friend that gets the issue running ghom, but no issues running riftbot.
Click to expand...

Try going into (DB folder)/Plugins/Trinity/Helpers/BotManager.cs and change these lines from:

Code: 
//BotMain.TicksPerSecond = 10;
BotMain.TicksPerSecond = Int32.MaxValue;

to

Code: 
BotMain.TicksPerSecond = 10;
//BotMain.TicksPerSecond = Int32.MaxValue;

Let me know if it fixes your DC issue.

Edit: You need to restart DemonBuddy for it to take effect.
 
legnotification said:
do i need to manually do that even with ez updater?

edit:

i just checked and everything was the right version except for riftbot revision 336.
where can i find this download?
Click to expand...

I'll upload it to the first page of this post right now.

I've updated my post with the latest revision of the profile.

It's at the bottom of the post.
 
Last edited:
Is there any good options in Trinity to make WD (pet build) run smoothly at t6?
Most of the time the char runs into elites and die miserably, almost if it was t1 :D
Just something to keep wd in range and let the pet tank?
 
I have noticed that with my bot Diablo tends to lag much more than me playing myself. Normally every 1-2 games there is a episode when for 2-3 minutes Diablo lags (toon keeps swinging away and there is no change in screen or you get the blue/black wall, while chat is still working) This hardly ever happens when I play myself. Any setting I can change to limit this? I have i7-4770K processor with 8gb memory and game is running of SSD. Intenet 50mbs comcast blast exterme package so I hardly doubt its a network/harware issue. Any advice will be great. Thanks.
 
crap no idea what i did to screw it up, but i crash in rifts now, GG to me!
 
Try going into (DB folder)/Plugins/Trinity/Helpers/BotManager.cs and change these lines from:

Code: 
//BotMain.TicksPerSecond = 10;
BotMain.TicksPerSecond = Int32.MaxValue;

to

Code: 
BotMain.TicksPerSecond = 10;
//BotMain.TicksPerSecond = Int32.MaxValue;

Let me know if it fixes your DC issue.

Edit: You need to restart DemonBuddy for it to take effect.
 
on dahlgur oasis it backtracks a lot and doesnt find the exit. changing the boxsize to 25 is working better for my current map layout and i think they are always quite similar.

also you should probably blacklist cursed chests in the a4 zerg bounties, because there are some of them in the non combat area. so its a waste of time and you probably die on higher difficulty if bounty wait option is enabled. the cursed chest bounty still works very well.

most maps are working great and only a few are left to tweak. thanks for the work.
 
mrbubbel said:
on dahlgur oasis it backtracks a lot and doesnt find the exit. changing the boxsize to 25 is working better for my current map layout and i think they are always quite similar.

also you should probably blacklist cursed chests in the a4 zerg bounties, because there are some of them in the non combat area. so its a waste of time and you probably die on higher difficulty if bounty wait option is enabled. the cursed chest bounty still works very well.

most maps are working great and only a few are left to tweak. thanks for the work.
Click to expand...

I've changed alot of boxes these last two days. Try revision 347 of the profile.
 
Oksehode said:
Try going into (DB folder)/Plugins/Trinity/Helpers/BotManager.cs and change these lines from:

Code: 
//BotMain.TicksPerSecond = 10;
BotMain.TicksPerSecond = Int32.MaxValue;

to

Code: 
BotMain.TicksPerSecond = 10;
//BotMain.TicksPerSecond = Int32.MaxValue;

Let me know if it fixes your DC issue.

Edit: You need to restart DemonBuddy for it to take effect.
Click to expand...

narrowed my crashing down to rifts now, i havent tried your fix yet, but i appear to be getting that error that was happening just as 2.05 hit. Randomly getting the game closed with a error entering a rift usually.
 
mrbubbel said:
yep, i saw that. have been at 344. oasis didnt change in 347 though.
Click to expand...

Thanks for letting me know. I will keep tweaking the boxes until they work. Let me know if you come across similar issues on other maps.
 
Oksehode, out of curiosity, would there be any reason for rifts to crash and not bounties? My bounties have been running 12 hrs straight, runs perfect. Rifts i've seen it crash upon first load, i've seen it run 2 rifts, then crash upon entering the 3rd. Could it be a problem with the diablo 3 install? I will try a clean d3 install as well tonight. I am using the latest beta with your latest compilation.

The crash looks very similar to the crash everyone first got when 2.05 was first released. I'm sitting on a brick ton of rift fragments because the bounties work perfect, but not the rifts!
 
rayofsi said:
Oksehode, out of curiosity, would there be any reason for rifts to crash and not bounties? My bounties have been running 12 hrs straight, runs perfect. Rifts i've seen it crash upon first load, i've seen it run 2 rifts, then crash upon entering the 3rd. Could it be a problem with the diablo 3 install? I will try a clean d3 install as well tonight. I am using the latest beta with your latest compilation.

The crash looks very similar to the crash everyone first got when 2.05 was first released. I'm sitting on a brick ton of rift fragments because the bounties work perfect, but not the rifts!
Click to expand...

Did you try what I posted? It could be that your TPS is to high.
 
Oksehode said:
Did you try what I posted? It could be that your TPS is to high.
Click to expand...

will try again when i get home, it was late and i figured with bounties working, all was well. I get 27 TPS in bounties. Previous DB /Trinity versions i had maybe 15 TPS
Will keep a eye on it to see if the TPS goes higher then that in Rifts. 27 TPS seems stable in bounties.
There were no changes in bot setup etc prior, Out of nowhere it just started with network disconnects from d3 servers. Then bounties wouldn't run either and had network disconnects. The old install and the new install would both rift entry crashes.

Old install had db 410 (crashed) updated to 415 (still crashed) trinity 1.97 and quest tools 2.076.

New install has your prior compilation (340) with db 415. Will try your posted possibly fix as soon as i get to access the computer later. The weirdest thing is that this happened after i tried using simple follow /db that were in different db folders. Not sure if running simplefollow screwed something up hah. Thanks for your quick replies.
 
Last edited:
Oksehode said:
Try going into (DB folder)/Plugins/Trinity/Helpers/BotManager.cs and change these lines from:

Code: 
//BotMain.TicksPerSecond = 10;
BotMain.TicksPerSecond = Int32.MaxValue;

to

Code: 
BotMain.TicksPerSecond = 10;
//BotMain.TicksPerSecond = Int32.MaxValue;

Let me know if it fixes your DC issue.

Edit: You need to restart DemonBuddy for it to take effect.
Click to expand...

Mine BotManager.cs had BotMain.TicksPerSecond = 15 (DB 415) made the change you suggested and changed it to 10. It was running stable for 20 mins this AM. Left it on will see what happens when I return. Why does high TPS lead to crashes? Any advantage of an high TPS?
 
You must log in or register to reply here.
Back
Top