[Beta] Demonbuddy beta builds

After I update my DB this morning. I do not track my EXP/Hour anymore. My champion just reach level 60 and not yet level 70. Is it something I did wrong during the installation or a normal behavior.

If someone can help me out figure this out I dont know if my current run is XP productive or not. I do not care about Gold per hour and Legendary per hour until I'm level 70.

Thank you!

 

I think it not displaying exp/hour is "normal." Probably not intended behavior, but I get that as well.

 

As far as i know, it's a bug between 60-70. I have my XP/H back now when i dinged 70.

 

reinstall new fresh copy of beta from scratch

 

A1 Adventure Mode vendor coords differ from campaign mode, needs an update? (toon stuck by gate to new tristram when performing town run)

 

Can confirm, I get stuck there when doing a town run as well.

Also would still love an update on being able to (at the very least) check which quest is active in adventure mode. It always shows the same quest iirc, and does not change when you enter a zone with a quest. Makes it impossible (afaik) to make any intelligent profiles to complete bounties.

 

Hi ho,

can anyone help me?
If i start demonbuddy before i log in in there i get the message:
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.IO.IOException: Unable to read data from the transport connection
What can i do?

Thanks

 

Do you have a firewall and is it blocking it?

 

Kadala(bloodshard vendor) needs to be blacklisted as a vendor we can SELL to in adventure mode the bot will just go to her and sit there cause it cannot sell to her, only buy.

 

Issus report:
<If condition="not ZetaDia.CurrentLevelAreaId == 19954">
<UseTownPortal questId="1" />
<WaitTimer questId="1" stepId="1" waitTime="1000" />
</If>

This code can be executed in town for beta version 364.
For beta version 365, it doesn't work.

 

I am not sure if it is demonbuddy or trinity when I use custom rules for the new legendary plans it states this and will not stash it:

 

cant wait for it to read quests -.- need those bountie modes

 

Errors

Few errors i noted with latest Demonbuddy BETA 1.1.1740.365

1) Some red errors in the software itself appear
2) Very low ticks (always under 8)
3) Exp/hour and other stats disappear after each game?
4) A lot of times, if I stop DB, load a different profile and start again, DB will stop responding (Have to terminate using task manager)

My logs attached

 

anyone has loginproblem too?

 

Still not able to create games in Adventurer Mode,

<GameParams quest="101758" step="1" act="OpenWorld" resumeFromSave="False" isPrivate="True" numGames="-1" />

Tried different quests and steps and all I get is error 316611 There was a problem creating the game.

EDIT : Got it working, it was by not having the quest and the ID related to it, still it Quest ID and Step shouldn't be a requirement when creating OpenWorld games.

 

Its getting time for Adventure mode now, comon..

 

I understand that bounties can be hard to bot, you would need a specific profile for each bounty, and there are probably a total of 70ish total different bounties.

But Rifts? All you have to do is click on the object to open a Rift, explore until you reach the 100% bar, kill the boss, leave, close the Rift, and repeat.

 

They don't write the profiles, we do. The problem is, we currently CAN'T write profiles for it because the questID reported never changes (i.e. only shows it as the "open world" quest) and there is no other API that they have to expose the bounty quest IDs.

And yeah, I've been thinking about trying to write a rift profile, but the problem with that is there isn't really a good system for detecting if you have killed a specific enemy or not, especially when (I believe) the same problems happen with the questID.

 

So many people complaining no profiles for rifts or bounties are out yet, perhaps they could learn to write profiles and make some? I think they would find in the current state that we are not yet able to write a bounty profile as bounty quest ids cannot be dumped.

 

That is exactly why I'm saying this on the Beta Build thread and not on any related profile topic. I am aware it is not a profile issue.