It was working awesomely until at the end of any act where QuestTools failed trying to click the OK button at the change act dialog. Any idea, anyone?
Using beta version: 1.0.1145.67
Had issues with game starting this morning. Fresh install , 3rd account, 3rd computer. The resume game xml was on nightmare. Got it to work by putting the start game on normal and starting from the very beginning of act 2
LOGS
1 run nightmare with belphegor.
He doesn't click the blood in voa. No log this time pc fucked up sry!
Can you zip and attach your full log please? Also, did you see the confirmation dialog box pop at least? Are you using any other plugins?
Someone else had this problem between acts 2-3, but, for me it works 100% every time. I'd like to know why.
Are you using an English client or other language?
Noticed weird bug today. I use DB BETA 67 and you plugin pack, nothing else.
Bot was running from one pedestal to another and stucking sometimes. Both pedestals were down and unclickable, the quest door was opened, however the quest message beneath the minimap said that only 1/2 is down.
I manually entered the temple nad there were no mobs (at least regular mobs, hadnt checked quest skeleton), start/stoppped the bot, but it didnt work. I went back through the quest door and made this screenshot.
Then I left the game and recreated a new one. With some manual help (i manually clicked on pedestals and lead him to quest door) bot was able to continue.
View attachment 65165
View attachment 65166
Noticed weird bug today. I use DB BETA 67 and you plugin pack, nothing else.
Bot was running from one pedestal to another and stucking sometimes. Both pedestals were down and unclickable, the quest door was opened, however the quest message beneath the minimap said that only 1/2 is down.
I manually entered the temple nad there were no mobs (at least regular mobs, hadnt checked quest skeleton), start/stoppped the bot, but it didnt work. I went back through the quest door and made this screenshot.
Then I left the game and recreated a new one. With some manual help (i manually clicked on pedestals and lead him to quest door) bot was able to continue.
View attachment 65165
View attachment 65166
Current Changelog
- Minimap markers is now being properly read from the client and should no longer cause problems.
- Demonbuddy now uses the loadbalancer to divide auth requests evenly among our servers.
- Added "leaveGame" attribute in LoadProfile tag, setting this to "True" makes Demonbuddy leave the game once the profile is loaded.
- Added attribute "ignoreGridReset" to the ExploreArea tag if set to true it will ignore resetting the segmentation grid when the tag starts and finish, can be usefull if you use 2 explore area tags in a row to avoid re-exploring already explored areas.
- Added the following methods to the ConditionParser:
bool HasStashedItem(int itemId) example usage: <If condition="HasStashedItem(1234)"> ... </If>
bool HasBackpackItem(int itemId) example usage: <If condition="HasBackpackItem(1234)"> ... </If>
int GetStashedItemCount(int itemId) example usage: <If condition="GetStashedItemCount(1234) >= 5"> ... </If>
int GetBackpackItemCount(int itemId) example usage: <If condition="GetBackpackItemCount(1234) >= 5"> ... </If>- Added a1dun_caves_Neph_WaterBridge_A to the door blacklist, ( bridge near drowned temple )
- Added a log message when the bot attempts to cast a town portal.
- Should always destroy barricades now if possible.