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

Current state of post 2.1.2 db, post here issues and working stuff !

Bertrand

Bertrand

Active Member
Joined
Aug 8, 2012
Messages
1,249
Reaction score
9
Will update this as i observe further:

n1 on the list to do: https://www.thebuddyforum.com/demon...legendaries-misc-items-rules.html#post1825452

Working stuff:
Good thing yar rift profile is working, so is the act 1 adventure profiles:

yar: https://www.thebuddyforum.com/demon...profiles/160808-rift-bot-rifting-profile.html

act 1-5 bounties: Bounties - Copy.rar :: Free File Hosting - File Dropper: File Host for Mp3, Videos, Music, Documents.


The bad stuff


- Bot sells crafting mats, and i cant find an option in trinity to enable/disable it.
more to come.

- Bot gets stuck at that bloodshards goblin when gets full, even with pickup bloodshards disabled.

--- BIG ISSUE---
The bot gets filled with bloodshards and after disconnecting from game when stuck with the bloodshards tp issue, he is in town, and requesting a town run due to being full on shards. This create infinite loop for the bot where he just recreates games trying to do a town run when already in town.

solution: previously was at 400 bshards for town run, set it at 500 seems to visited kadala after the first game reset.

]- Other issues with kadala, fails to po purchase items sometimes. --> after game restarts bot thinkgs he is standing next to kadala, doesnt move from starting location but tries to open kadala window, without moving to her.
 
Last edited:
The whole trinity need a huge rework , tested it on dh and monk i mean it is working but the efficeny is terrible , there is also a problem with bot sometimes selling random stuff from stash , crafting mats, key fragments. The rest is mostly all ok but since trinity is like the most important thing of this bot it need the most work for sure.
 
Diablo 3 crashes when Trinity attempts to open the stash sometimes (I think it has to do with salvaged white/grey items)
 
Sometimes bot sells rift keys. It sold like 5 k of my rift keys. First from this one i had in backpack then he took each stack of 100 from chest and sold it and looped it until he was out of keys. Also he sold bottomless potion for me only wings left. Not a big deal but need to farm keys again.
 
still getting a ton of Trinity errors when starting the bot:
Code: 
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemWrapper.cs(12,18) : warning CS0660: 'Trinity.Items.ItemWrapper' defines operator == or operator != but does not override Object.Equals(object o)
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(102,45) : error CS1061: 'Trinity.Config.Loot.PickupSetting' does not contain a definition for 'CraftTomes' and no extension method 'CraftTomes' accepting a first argument of type 'Trinity.Config.Loot.PickupSetting' could be found (are you missing a using directive or an assembly reference?)
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(125,46) : error CS1061: 'Trinity.Config.Loot.PickupSetting' does not contain a definition for 'LegendaryLevel' and no extension method 'LegendaryLevel' accepting a first argument of type 'Trinity.Config.Loot.PickupSetting' could be found (are you missing a using directive or an assembly reference?)
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(125,104) : error CS1061: 'Trinity.Config.Loot.PickupSetting' does not contain a definition for 'LegendaryLevel' and no extension method 'LegendaryLevel' accepting a first argument of type 'Trinity.Config.Loot.PickupSetting' could be found (are you missing a using directive or an assembly reference?)
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(125,143) : error CS1061: 'Trinity.Config.Loot.PickupSetting' does not contain a definition for 'LegendaryLevel' and no extension method 'LegendaryLevel' accepting a first argument of type 'Trinity.Config.Loot.PickupSetting' could be found (are you missing a using directive or an assembly reference?)
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(138,98) : error CS1061: 'Trinity.Config.Loot.PickupSetting' does not contain a definition for 'WeaponBlueLevel' and no extension method 'WeaponBlueLevel' accepting a first argument of type 'Trinity.Config.Loot.PickupSetting' could be found (are you missing a using directive or an assembly reference?)
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(138,136) : error CS1061: 'Trinity.Config.Loot.PickupSetting' does not contain a definition for 'WeaponYellowLevel' and no extension method 'WeaponYellowLevel' accepting a first argument of type 'Trinity.Config.Loot.PickupSetting' could be found (are you missing a using directive or an assembly reference?)
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(141,98) : error CS1061: 'Trinity.Config.Loot.PickupSetting' does not contain a definition for 'ArmorBlueLevel' and no extension method 'ArmorBlueLevel' accepting a first argument of type 'Trinity.Config.Loot.PickupSetting' could be found (are you missing a using directive or an assembly reference?)
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(141,135) : error CS1061: 'Trinity.Config.Loot.PickupSetting' does not contain a definition for 'ArmorYellowLevel' and no extension method 'ArmorYellowLevel' accepting a first argument of type 'Trinity.Config.Loot.PickupSetting' could be found (are you missing a using directive or an assembly reference?)
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(143,98) : error CS1061: 'Trinity.Config.Loot.PickupSetting' does not contain a definition for 'JewelryBlueLevel' and no extension method 'JewelryBlueLevel' accepting a first argument of type 'Trinity.Config.Loot.PickupSetting' could be found (are you missing a using directive or an assembly reference?)
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(143,137) : error CS1061: 'Trinity.Config.Loot.PickupSetting' does not contain a definition for 'JewelryYellowLevel' and no extension method 'JewelryYellowLevel' accepting a first argument of type 'Trinity.Config.Loot.PickupSetting' could be found (are you missing a using directive or an assembly reference?)
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(157,94) : error CS0103: The name 'TrinityGemType' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(158,97) : error CS0103: The name 'TrinityGemType' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(159,98) : error CS0103: The name 'TrinityGemType' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(160,95) : error CS0103: The name 'TrinityGemType' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(161,97) : error CS0103: The name 'TrinityGemType' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(570,29) : error CS0103: The name 'TownRun' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(571,25) : error CS0103: The name 'TownRun' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(603,25) : error CS0103: The name 'TownRun' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(608,25) : error CS0103: The name 'TownRun' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(687,21) : error CS0103: The name 'Level' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(688,21) : error CS0103: The name 'ParagonLevel' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(691,31) : error CS0103: The name 'TotalXP' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(691,47) : error CS0103: The name 'LastXP' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(691,62) : error CS0103: The name 'NextLevelXP' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(693,33) : error CS0103: The name 'LastXP' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(695,33) : error CS0103: The name 'TotalXP' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(695,44) : error CS0103: The name 'NextLevelXP' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(699,33) : error CS0103: The name 'TotalXP' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(699,75) : error CS0103: The name 'LastXP' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(702,25) : error CS0103: The name 'LastXP' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(703,25) : error CS0103: The name 'NextLevelXP' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(707,31) : error CS0103: The name 'TotalXP' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(707,47) : error CS0103: The name 'LastXP' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(707,62) : error CS0103: The name 'NextLevelXP' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(710,33) : error CS0103: The name 'NextLevelXP' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(712,33) : error CS0103: The name 'TotalXP' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(712,44) : error CS0103: The name 'NextLevelXP' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(716,33) : error CS0103: The name 'TotalXP' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(716,44) : error CS0103: The name 'NextLevelXP' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(719,25) : error CS0103: The name 'LastXP' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(720,25) : error CS0103: The name 'NextLevelXP' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(724,21) : error CS0103: The name 'PersistentOutputReport' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(725,74) : error CS0103: The name 'ItemStatsWhenStartedBot' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(755,82) : error CS0103: The name 'TotalXP' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(755,150) : error CS0103: The name 'TotalXP' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(756,33) : error CS0103: The name 'LastGold' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(758,33) : error CS0103: The name 'LastGold' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(760,50) : error CS0103: The name 'LastGold' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(762,33) : error CS0103: The name 'LastGold' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(766,33) : error CS0103: The name 'TotalGold' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(766,63) : error CS0103: The name 'LastGold' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(767,33) : error CS0103: The name 'LastGold' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(769,84) : error CS0103: The name 'TotalGold' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(769,152) : error CS0103: The name 'TotalGold' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(774,33) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(777,79) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(778,48) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(781,41) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(782,102) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(783,56) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(784,57) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(784,102) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(789,41) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(791,68) : error CS0103: The name 'ItemQualityTypeStrings' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(791,114) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(791,193) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(791,317) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(791,367) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(793,49) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(794,112) : error CS0103: The name 'ItemQualityTypeStrings' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(794,158) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(794,246) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(794,379) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(794,438) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(807,33) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(810,70) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(810,129) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(813,41) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(815,68) : error CS0103: The name 'GemTypeStrings' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(815,106) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(815,181) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(815,301) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(815,347) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(817,49) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(818,112) : error CS0103: The name 'GemTypeStrings' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(818,150) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(818,237) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(818,369) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(818,427) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(830,33) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(833,70) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(833,137) : error CS0103: The name 'ItemsDroppedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(842,33) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(845,81) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(845,135) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(848,41) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(849,102) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(849,175) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(849,293) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(849,337) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(854,41) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(856,68) : error CS0103: The name 'ItemQualityTypeStrings' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(856,114) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(856,192) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(856,315) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(856,364) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(858,49) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(859,112) : error CS0103: The name 'ItemQualityTypeStrings' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(859,158) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(859,245) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(859,377) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(859,435) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(867,37) : error CS0103: The name 'totalFollowerItemsIgnored' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(869,71) : error CS0103: The name 'totalFollowerItemsIgnored' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(875,33) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(878,70) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(878,128) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(881,41) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(883,68) : error CS0103: The name 'GemTypeStrings' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(883,106) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(883,180) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(883,299) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(883,344) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(885,49) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(886,112) : error CS0103: The name 'GemTypeStrings' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(886,150) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(886,236) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(886,367) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(886,424) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(898,33) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(901,70) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\Items\ItemHandling.cs(901,136) : error CS0103: The name 'ItemsPickedStats' does not exist in the current context
Compiler Error: c:\Demonbuddy\Plugins\Trinity\GearSwap\TownRun.cs(11,20) : error CS0103: The name 'TownRun' does not exist in the current context
 
Last edited by a moderator:
for those with problems,use support issues section plz
 
I don't know about you guys or if you have it setup like this already, but I keep protected inventory slots just so this doesn't happen. And anything in protected slot has never been accidentally sold or anything, The bot did sell 2 caches the other day but thats fixed afaik. I keep 1 of each marquise gem, 1 stack of crystals/dust/breath/parts/souls. and they are all checked green in the protect box on the bot settings. same for rift fragments(i usually stack about 300). It does take up a good portion of space, but its well worth doing. I keep mine on the bottom right hand side, so all the new items start from the left as looted. Matter of fact I have my goldwrap/kymbos boon amulet and shit all protected on the right side. It still allows for plenty of room if I ever want to pickup blues or yellows, but I only pickup Legendary and with the new goblins and updated mats dropping by the 40-200s at a time theres no reason to pickup yellows/blues anymore.

The biggest issue I have is with trying to gamble, Kadalaspree worked great before one of the updates a few patches ago. Now its on and off again problems, For instance since the new release of .392 and .397 it was working flawless, gambling no issues 24/7 as I ran through 200 fragments. Now all of a sudden my bot started looping, trying to gamble with 50 shards when its set to gamble at a minimum of 275(had to lower it from 375 cuz blood goblins and even then sometimes bot might lose 20-80 shards depending on if the bot is a few shards shy of the gamble number, or lower. with the current buff for double goblins thats ~630-660 shards per gob double pack. It works about 50/50 of the time to gamble and take portal back, then get shards and keep going or go and gamble again. I am afraid to even change the settings on kadalaspree in fear of it breaking again. Getting stuck at 500 shards, or not being able to spend them sucks badly. I wish blizz had the cap higher, would eliminate alot of issues. But at the same time, I wish I knew how to improve kadalaspree or make a better working gamble plugin that I can rely on(no offense to the author, I am thankful for it but it doesn't alway work, maybe 75% of the time and when it bugs out it REALLY bugs out)

bad bug out example:
bot loops gambling, 500 shards capped cuz goblins. opens kadala window but never actually gambles anything, just walks back and forth from a1 stash to kadala over and over til inactivity, rinse repeat. To top it off, I paused the bot, spent the shards myself. exitted the bot(This was the only reason to get rid of the kadala loop bug once it started before, because of reasons your about to read) upon new DB start up, loaded my rift bot common profile, I had 0 shards. Bot instantly wants to gamble, despite settings still the same. It is like it had cached memory of what it was doing even though it had been exited out and a new DB opened.


//// most recent issue since 2.1.2 patch ////
bot will sit there and take a beating despite the DB in the bottom left bar you can see it saying like attacktarget=morlu_B power=demonhunter.clusterarrow and it will switch through multiple targets(the name changes if there are diff monsters in the pack so you can tell its TRYING to attack or whatever but it doesn't) It also does this occasionally with rift guardians, and ive seen my bot timeout because the only thing hitting it is my pets/templar and either my bot is moving around exploring the map still while a RG is up and following him around(on some occasions, once the RG attacks the bot enough the bot will finally engage the boss but other times he will keep trying to explore the map, if the RG moves fast and can keep up he usually dies because my DH sentries are firing rockets that accidentally shoot the RG too)
I remember there was an issue last release that caused every class/bot to sometimes just sit near elites and do nothing, charge head on into them and iirc unchecking the 'give priority to healthglobes' box worked to fix it for the most part. but the latest trinity has that unchecked by default. Anyone else noticing this, or any clues how to fix it if it is indeed the same old bug?
 
Last edited:
Syn-Ack said:
The biggest issue I have is with trying to gamble, Kadalaspree worked great before one of the updates a few patches ago. Now its on and off again problems, For instance since the new release of .392 and .397 it was working flawless, gambling no issues 24/7 as I ran through 200 fragments. Now all of a sudden my bot started looping, trying to gamble with 50 shards when its set to gamble at a minimum of 275(had to lower it from 375 cuz blood goblins and even then sometimes bot might lose 20-80 shards depending on if the bot is a few shards shy of the gamble number, or lower. with the current buff for double goblins thats ~630-660 shards per gob double pack. It works about 50/50 of the time to gamble and take portal back, then get shards and keep going or go and gamble again. I am afraid to even change the settings on kadalaspree in fear of it breaking again. Getting stuck at 500 shards, or not being able to spend them sucks badly. I wish blizz had the cap higher, would eliminate alot of issues. But at the same time, I wish I knew how to improve kadalaspree or make a better working gamble plugin that I can rely on(no offense to the author, I am thankful for it but it doesn't alway work, maybe 75% of the time and when it bugs out it REALLY bugs out)

bad bug out example:
bot loops gambling, 500 shards capped cuz goblins. opens kadala window but never actually gambles anything, just walks back and forth from a1 stash to kadala over and over til inactivity, rinse repeat. To top it off, I paused the bot, spent the shards myself. exitted the bot(This was the only reason to get rid of the kadala loop bug once it started before, because of reasons your about to read) upon new DB start up, loaded my rift bot common profile, I had 0 shards. Bot instantly wants to gamble, despite settings still the same. It is like it had cached memory of what it was doing even though it had been exited out and a new DB opened.
Click to expand...

I have seen it do the run back and forth thing and i have also seen it use the map to go act1 after portalling back to dungeon after a town run. Arcanum also has some issues now after the patch as does Questools, Trinity and i don't even want to think about the community bounties.

Sometimes it is bugs and bad coding but i see these sort of posts a lot and i think people need to have a bit more patience and understanding - this is not like coding a normal application where you have control over all of the moving parts.

DB changes underneath us so anything you write is based on a moving target. Sometimes things just stop working entirely or start working a different way.

DBs ability to read Diablo3's memory is unreliable and prone to mistakes - its the nature of the beast, so even if you line everything up perfectly - it will still go wrong sometimes.

Take a look at DiaCollector for example, rrrix wanted to catelog all the items but found that DB will randomly have the wrong values for pretty much every attribute.

Also, the community and Diablo3 interest as a whole has declined dramatically. I'm sure you've noticed a few key people spending less and less time working on the bot and honestly people bitching all the time doesn't encourage people to volunteer their free time. Something to think about.

What you can do to help is provide as much detailed information about an issue you've found as possible. If you can document a detailed sequence of events to reliably reproduce an issue it makes it infinitely easier for people to fix, and so more likely to get fixed.
 
Last edited:
Bot spams mantra for monk even when "Disable mantra spam" is checked and drains spirit, when the taeguk gem is equipt. Possible to apply a SW spam in future update or just take taeguk spamming away entirely?
 
Yeah xzjv, Sorry I am not trying to be rude or inconsiderate to you or the other people working on this stuff. I don't blame anyone, It is mostly just frustration from myself. I know it takes a great deal of time and effort to perfect things. I can understand the part about people bitching about this and that being a turn off for devs to have any motivation to work harder to improve upon things. If there are any extra logging boxes I should have enabled for the bugs I have no problem just uploading or saving them with a simple description of what happened etc in case it can be looked at in the future.

Community bounty seems to be working fine, for A1 and A4 atleast. assuming its the same one I am thinking of, the only thing is sometimes the bot will not attack the growths and wont recognize them as targets(I remember this being an issue, the bot considered them elites and bot would pop all the cooldowns as if it were facing one) but for the most part thats a very small bug and act 4 bounty works great 95% of the time.
 
You must log in or register to reply here.
Back
Top