[Beta] Demonbuddy beta builds

[mrbigsexy]

clicking this is doing nothing since the last beta update

It actually does work. Click EZ updater - config - update and it works. Really unfortunate since it now updated a bunch of profiles to new revisions that have problems. New updates = more headaches. Nice to not use EZupdater so that I let other people have issues first while my stuff is still running smooth

 

[Nesox]

The .24 bundled with the latest build works now, .394

 

[checkthis]

The .24 bundled with the latest build works now, .394

still getting this error:
Failed to load profile: Element TrinityExploreDungeon is not supported. Please check your XML and try again. (<TrinityExploreDungeon questId="1" stepId="2" until="ObjectFound" objectDistance="150" actorId="210763" boxTolerance="0.7" boxSize="10" pathPrecision="40" ignoreMarkers="False" stayAfterBounty="False">
<PrioritizeScenes>
<PriorityScene sceneName="Exit" />
</PrioritizeScenes>
<IgnoreScenes>
<IgnoreScene sceneName="_N_0" />
<IgnoreScene sceneName="_S_0" />
<IgnoreScene sceneName="_E_0" />
<IgnoreScene sceneName="_W_0" />
</IgnoreScenes>
</TrinityExploreDungeon>) Line 16
System.Exception: Element TrinityExploreDungeon is not supported. Please check your XML and try again. (<TrinityExploreDungeon questId="1" stepId="2" until="ObjectFound" objectDistance="150" actorId="210763" boxTolerance="0.7" boxSize="10" pathPrecision="40" ignoreMarkers="False" stayAfterBounty="False">
<PrioritizeScenes>
<PriorityScene sceneName="Exit" />
</PrioritizeScenes>
<IgnoreScenes>
<IgnoreScene sceneName="_N_0" />
<IgnoreScene sceneName="_S_0" />
<IgnoreScene sceneName="_E_0" />
<IgnoreScene sceneName="_W_0" />
</IgnoreScenes>
</TrinityExploreDungeon>) Line 16
at ..
(PropertyInfo , XElement , Object )
at Zeta.XmlEngine.XmlEngine.Load(Object obj, XElement element)
at ..
(XElement , Type )
at ..
.
(XElement )
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at ..
(XElement , PropertyInfo )
at ..
(PropertyInfo , XElement , Object )
at Zeta.XmlEngine.XmlEngine.Load(Object obj, XElement element)
at Zeta.Bot.Profile.Profile.Load(XElement element, String path)
at Zeta.Bot.Profile.Profile.Load(String path)
at Zeta.Bot.ProfileManager.Load(String profilePath, Boolean rememberPath)

 

[Umed]

Same for me, still getting the Error

 

[checkthis]

It actually does work. Click EZ updater - config - update and it works. Really unfortunate since it now updated a bunch of profiles to new revisions that have problems. New updates = more headaches. Nice to not use EZupdater so that I let other people have issues first while my stuff is still running smooth

it does not for me. nothing happens by clicking the update button. worked yesterday though!

 

[mrbigsexy]

Delete trinity from the plugins folder, delete EZ updater and go get a fresh install of EZ Updater. This should download the newest trinity into the plugin folder and it should work.

I have no clue about .394 DB Beta. I refuse to exit and upgrade again after what happened last time. I am on .393 and it is finally working (running 3 musketeers profile- haven't tried rift or bounty)

 

[wild19]

Now getting the following error when trying to save settings within Trinity.

DemonbuddyBETA v1.1.1816.394 started
Logging in...
Flashing window
[Trinity] Initialized v1.8.24
[RiftBot] RiftBot 0.0.4 Initialized.
[QuestTools] Plugin v1.5.21 Enabled
[Trinity] OnEnable start
Setting up Trinity Logging
[Trinity] Loading BattleTag Settings
[Trinity] Configuration file loaded
[Trinity] ENABLED: Trinity v1.8.24 now in action!
[RiftBot] RiftBot 0.0.4 Enabled.
[Trinity] Saving Config file
[Trinity] Exception in UI SaveCommand
[Trinity] Saving Config file
[Trinity] Exception in UI SaveCommand

NVM above error, upon restarting demonbuddy settings that were changed actually saved, but Trinitys window would not close as normal upon clicking save.

 

[banme]

DB Freezes when pressing stop, has to be ended through task manager. Logfile attached.

 

[taskmanager]

?? i dont controll those!

 

[zept0r]

Where can I set up, that the bot picks up Arcane Dust(the blues stuff for crafting)?

 

[Nerx]

Where can I set up, that the bot picks up Arcane Dust(the blues stuff for crafting)?

Under Item>Pickup there is a "Misc item level" change it to common+ or Magic+ if you dont want the white crafting material

 

[zept0r]

Thanks mate!

 

[SomeGeek]

DB doesn't recognize trinity plugin after update... help!!

 

[Karls]

I get "Object reference not set to an instance of an object" error in a popup when I try to start a profile in .394 (after updating all plugins) and then log shows:

Error while starting botSystem.NullReferenceException: Object reference not set to an instance of an object.
at Trinity.Trinity.ReplaceTreeHooks() in d:\...\Plugins\Trinity\Helpers\BotManager.cs:line 26
at Trinity.Trinity.TrinityBotStart(IBot bot) in d:\...\Plugins\Trinity\Helpers\GameEvents.cs:line 69
at Zeta.Bot.BotEvent.Invoke(IBot bot)
at Zeta.Bot.BotMain.Start()
at Demonbuddy.MainWindow.HandleStartStopBot()

And rolled back to .391 for now

 

[FrenchBot]

Would it be possible to add support for %damage of items (such as elemental and skill damages), so that we can get working itemrules ?

 

[lightn1ng]

DB doesn't recognize trinity plugin after update... help!!

Same, how do I roll back to prior version?

 

[fps2299]

opening horadric cache is not working with the newest DB beta version (813.393)

 

[Stalker27]

DB doesn't recognize trinity plugin after update... help!!

Use EZupdater and update trinity (delete Trinity before update) and it works again...

 

[firerebel]

Tried all of the posted solutions.. fresh install on every version of trinity I can find.. fresh install of .393 + delete trinity + fresh ez updater, doesn't show up in plugins list
fresh install of .394 + delete trinity + fresh ez updater doesn't show up in plugins list = cant update..

please post .391 or lower.....

edit: nevermind was installing ezupdater wrong...

 

[nop]

The problem persists with map exploration after bounties are complete.