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

[Release] Demonbuddy - Sunny Monday build (#227)

Status
Not open for further replies.
Sorry if this sounds stupid but can we take this as mainly a fix to the chars entering cellars and zones and not doing anything? Or are there stability (the recent crashes) fixes in there too
 
Bazingaw said:
Sorry if this sounds stupid but can we take this as mainly a fix to the chars entering cellars and zones and not doing anything? Or are there stability (the recent crashes) fixes in there too
Click to expand...

It's for both, should fix when it stops doing anything after zoning/taking portals and we had to disable closing db when diablo craches so we can see what function it's trying to run when diablo crashes.
 
marko001 said:
Noway, it crashes randomly (hmm faster then with .217?)
Click to expand...
No such thing as crashing randomly. Get the devs some data so they can find the problem.

Edit: well, I guess maybe you could have a random number generator that controlled when you enter a buggy section of code, but we all know there's no such thing as that either, right?
 
Im using SWOL profile running Sarkoth+Wretch queen right now. does this help stop botting at entrance like you talking about? coz my bot does stopped at sakorth. so I also install Giles and some other Plugin around like 6-7 should it be ok? or its too many Plugging?
 
Here's my log. Crashes after about 2-3 minutes.

Keeps spamming something about "Rule matched Gold by name" and "Rule has no stats to match, assuming base types were defined and returning a successful match!".

Not sure if that's caused by any plugin? Probably Giles' stash replacer if any.
 

Attachments

Terek said:
Here's my log. Crashes after about 2-3 minutes.
Keeps spamming something about "Rule matched Gold by name" and "Rule has no stats to match, assuming base types were defined and returning a successful match!".
Not sure if that's caused by any plugin? Probably Giles' stash replacer if any.
Click to expand...

You need to go into world object handler config and tick "Disable Loot Rule Filtering". Those item rule matches are caused by DB trying to match item rules, which if you're using the item rules with stash replacer, match EVERYTHING. Always be sure to read a plugin's install instructions carefully :)
 
GilesSmith said:
You need to go into world object handler config and tick "Disable Loot Rule Filtering". Those item rule matches are caused by DB trying to match item rules, which if you're using the item rules with stash replacer, match EVERYTHING. Always be sure to read a plugin's install instructions carefully :)
Click to expand...

Oh thanks Giles. I did that before, but after updating to 217, all my plugin settings were gone :/ But thanks for reminding me :)
 
Nesox said:
It's for both, should fix when it stops doing anything after zoning/taking portals and we had to disable closing db when diablo craches so we can see what function it's trying to run when diablo crashes.
Click to expand...

Nesox - the new actor manager also seems to cause some issues with monsters - for example the large wood wraiths in act 1, frequently bots were getting stuck trying to hump their legs - as if a waypoint was stuck inside the tree that the bot wanted to reach, so it wouldn't do anything to them until the follower killed the tree/you got knocked back - usually if the tree had just spawned from inside an obstacle-clump (but was "active" and able to attack you) - #220 this problem vanishes again, which suggested the new actor manager has other issues besides causing stucks after entering zones/portals? Was it not reading the radius of objects correctly perhaps, or not reading their location (it did feel like the new DB versions were not updating positions as frequently...)?
 
GilesSmith said:
Nesox - the new actor manager also seems to cause some issues with monsters - for example the large wood wraiths in act 1, frequently bots were getting stuck trying to hump their legs - as if a waypoint was stuck inside the tree that the bot wanted to reach, so it wouldn't do anything to them until the follower killed the tree/you got knocked back - usually if the tree had just spawned from inside an obstacle-clump (but was "active" and able to attack you) - #220 this problem vanishes again, which suggested the new actor manager has other issues besides causing stucks after entering zones/portals? Was it not reading the radius of objects correctly perhaps, or not reading their location (it did feel like the new DB versions were not updating positions as frequently...)?
Click to expand...

It doesn't read the position of anything or something like that. It simply maintains a list of all ingame and out of game objects, also provides a few nice methods for retrieving objects.
We rewrote it because it's a little slow apparently we need to do some more private testing until it's deemed ready for the public, we got a few testers that usually test new builds.
 
Is there any way for me to check if there is a nav server connection issue between me and the db server? Because i just had my bots pause again on 220. They just stopped doing anything, both at the same time and a few minutes later they just kept going again, without me interacting. Inactivity timer didn't trip as i had set it to 1 minute.
 
The recent few builds have been significantly laggier/more jerky than the build before 1.04 was out.
 
Nesox said:
It doesn't read the position of anything or something like that. It simply maintains a list of all ingame and out of game objects, also provides a few nice methods for retrieving objects.
We rewrote it because it's a little slow apparently we need to do some more private testing until it's deemed ready for the public, we got a few testers that usually test new builds.
Click to expand...

Quoted for anyone that missed it. DB will continue to be slow and buggy till the next update. Thanks for the hard work Nesox
 
Status
Not open for further replies.
Back
Top