SVN Update Rev 61: 1) Added a failsafe to the failsafe so that you can failsafe while you failsafe. Seriously though, shouldn't leave the game if you killed the boss anymore. 2) Added a check to the moving to Rift Guardians to see if it even exists before attempting it, that way it won't sit around doing nothing forever after the boss is dead. As a side note, if the bot doesn't head for the Rift Boss after it spawns, or say "Found Rift Guardian!" then you can probably bet the boss isn't supported, and you should get the ActorID for me to add support for it. To get the ActorID, stop the bot and get close to the Rift Boss. Go to the QuestTools tab on DB and hit "Dump Actor Attribs" that will take a second and fill your log with a ton of information. You want to look for something that starts with the name "XR_L1_Boss" or something like that. Copy that full line and paste it here please. Update and let me know how things go now.
SVN Update Rev 61: 1) Added a failsafe to the failsafe so that you can failsafe while you failsafe. Seriously though, shouldn't leave the game if you killed the boss anymore. 2) Added a check to the moving to Rift Guardians to see if it even exists before attempting it, that way it won't sit around doing nothing forever after the boss is dead. As a side note, if the bot doesn't head for the Rift Boss after it spawns, or say "Found Rift Guardian!" then you can probably bet the boss isn't supported, and you should get the ActorID for me to add support for it. To get the ActorID, stop the bot and get close to the Rift Boss. Go to the QuestTools tab on DB and hit "Dump Actor Attribs" that will take a second and fill your log with a ton of information. You want to look for something that starts with the name "XR_L1_Boss" or something like that. Copy that full line and paste it here please. Update and let me know how things go now.
SVN Update Rev 61: 1) Added a failsafe to the failsafe so that you can failsafe while you failsafe. Seriously though, shouldn't leave the game if you killed the boss anymore. 2) Added a check to the moving to Rift Guardians to see if it even exists before attempting it, that way it won't sit around doing nothing forever after the boss is dead. As a side note, if the bot doesn't head for the Rift Boss after it spawns, or say "Found Rift Guardian!" then you can probably bet the boss isn't supported, and you should get the ActorID for me to add support for it. To get the ActorID, stop the bot and get close to the Rift Boss. Go to the QuestTools tab on DB and hit "Dump Actor Attribs" that will take a second and fill your log with a ton of information. You want to look for something that starts with the name "XR_L1_Boss" or something like that. Copy that full line and paste it here please. Update and let me know how things go now.
It seems that you are not using the latest release. Now the logic is like this: while (no boss) while (no stone) explore/fight/etc endwhile well, logout and repeat endwhile This works like a charm to me.
This Profile is good now The problem is exploring need to be better. The character sometimes run back I don't know why
SVN Update Rev 61: 1) Added a failsafe to the failsafe so that you can failsafe while you failsafe. Seriously though, shouldn't leave the game if you killed the boss anymore. 2) Added a check to the moving to Rift Guardians to see if it even exists before attempting it, that way it won't sit around doing nothing forever after the boss is dead. As a side note, if the bot doesn't head for the Rift Boss after it spawns, or say "Found Rift Guardian!" then you can probably bet the boss isn't supported, and you should get the ActorID for me to add support for it. To get the ActorID, stop the bot and get close to the Rift Boss. Go to the QuestTools tab on DB and hit "Dump Actor Attribs" that will take a second and fill your log with a ton of information. You want to look for something that starts with the name "XR_L1_Boss" or something like that. Copy that full line and paste it here please. Update and let me know how things go now.
Good thing that you started a new thread! Loving this profile. Was able to afk it while I slept yesturday and was still running when I woke up. Just found a little thing that may break the continuity of the bot. If you have 500 bs it will stay there trying to pick up that "strange" thing from the ground until the end of time. It will try to TP but will cancel the tp. DB gives this error: [Trinity] Invalid Item Link color={c:ffc236ff} internalName=HoradricRelic-18449 name=Blood Shard gameBalanceId=-1691237125
Would it be possible for the bot to run a circle around the rift boss's corpse or whatever after killing it? As a melee (monk) I've observed the bot (core) kill the rift boss then immediately TP out without picking the blood shards up if there's no loot dropped that matches my particular settings (nothing but legendaries).
i never post but this needs to be said. thanks for your work and keep it up. the average joe like me really appreciates it. your contribution to the community really means alot. ok enough mr. nice guy. listen jackoff...when using demon hunter, the bot acts funny. it runs back and forth, tries to shoot through walls, ...just doesnt seem right. i am going to try using barb. 850k dps w/77% lightning- 11m toughness. do you have a recommended build for any certain class? thanks in advance
Excellent work Sir. Might I ask, can you put perferred Trinity Settings in the original post? (I've watched the bot run back and forth sometimes randomly, not sure if it might be a DB issue, but i've gone over my trin settings don't think its anything causing this, however if you let me mimic your perferred trinity settings I can confirm if it was the issue) Keep up the good work mate!
SVN Update Rev 62: 1) Box sizes adjusted. 2) Added check around failing boss. 3) Added if exists check around moving to boss. Been running with that Rev for 3 hours now on normal (for speed) it's failed 2 games (was unable to kill boss) and got stuck 3 times, 2 of which unstucker was able to correct itself, the other time it hit gold inactivity and reset the game. So in other words, it's totally afkable. This is out of like 25ish games if I had to guess.
I have 400 keys farmed up, so i'll be leaving you some good feedback on Exp/Gold/Legs - Per hour~ Running extended.xml
Just some stats: (WitchDoctor, Thunderfury + 700k damage, 4mil toughness, running T1) Enchantress (Maximus + 300k Damage)
diff r62 with r61: boxsizes changed from 35 to 25. added a {boss not exist} check around logout handling. added a {boss do exist} check around moveto boss.
Either way one of the whiles needs to be removed, there is no idea order. With town stone inside, the bot stops once it finds it (used to). With town stone outside it will continue to kill even after boss is dead because the town stone will have a higher priority, which makes it another extended script. I already know how to fix this I just haven't implemented it yet because I want to think it through fully. Thanks! I believe that is an issue with Trinity, Rrrix has a lot of things to update and work on and I'm sure it will be fixed sooner or later. I don't really know a preferred build for every class though, sorry. DB doesn't support Blood Shards yet, so it never picks them up unless it walks over them trying to pick something else up. So no loot settings = no blood shards right now. Try the newest update, I think I adjusted box sizes. It may back track a tiny bit more then it did but it gets stuck less often, and when it does it can usually correct itself.
I apologize if this is a noob question, but I've used dozens of profiles here and had good luck generally. When loading Rifter I get this error: Loaded profile Rifter - A Bot for Rifts! Chose Trinity as your combat routine Loaded profile Rifter - A Bot for Rifts! Chose Trinity as your combat routine [Trinity] Bot Starting Loaded profile Rifter - A Bot for Rifts! GameChanged. Clearing actors [Trinity] New Game - resetting everything ProfileOrderManager.OnGameJoined, Reloading profile. [Trinity] New Game - resetting everything Loaded profile Rifter - A Bot for Rifts! Game joined, Resetting profile caches. ToggleTargeting, new values: Looting:True LootRadius:100 Combat:True KillRadius:80 [Trinity] Starting up Generic Cache Manage thread [Trinity] Starting up Generic Blacklist Manager thread ProfileOrderManager.OnGameJoined, Reloading profile. [Trinity] New Game - resetting everything Loaded profile Rifter - A Bot for Rifts! Game joined, Resetting profile caches. ToggleTargeting, new values: Looting:True LootRadius:100 Combat:True KillRadius:80 ProfileOrderManager.OnGameJoined, Reloading profile. [Trinity] New Game - resetting everything Loaded profile Rifter - A Bot for Rifts! Game joined, Resetting profile caches. ToggleTargeting, new values: Looting:True LootRadius:100 Combat:True KillRadius:80 ProfileOrderManager.OnGameJoined, Reloading profile. [Trinity] New Game - resetting everything Loaded profile Rifter - A Bot for Rifts! Game joined, Resetting profile caches. ToggleTargeting, new values: Looting:True LootRadius:100 Combat:True KillRadius:80 ProfileOrderManager.OnGameJoined, Reloading profile. [Trinity] New Game - resetting everything Loaded profile Rifter - A Bot for Rifts! Game joined, Resetting profile caches. ToggleTargeting, new values: Looting:True LootRadius:100 Combat:True KillRadius:80 ProfileOrderManager.OnGameJoined, Reloading profile. [Trinity] New Game - resetting everything Loaded profile Rifter - A Bot for Rifts! My character just runs and opens a rift, and buffs himself repeatedly forever. I generally use TurboHUD while using DemonBuddy. I should mention that while it's bugging out like this, D3 becomes horrifically laggy.
I do. edit: I just restarted everything and the bot immediately ported to A5, went to the rift opener, clicked it for a second, cancelled and ran south immediately and stood there. I forced a new rift to open and restarted the profile and bot went in and began clearing. I'll report back after it starts a new game to see if any issues arise. I'm not being hostile I want to help refine the profile with my own experiences.
