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

[Beta] Demonbuddy beta builds

Status
Not open for further replies.
i'm going to sleep and if i don't see a build tomorrow that's gonna be compatible with .28 trinity i'm going to raise hell. good night all :rolleyes:
 
upgraded to 410, happy that the QJ problem is resolved, very unhappy that i have to use the newest trinity that doesn't do townruns properly.
 
does any one have 408 beta demonbuddy i can download if possiable?

I'm not sure it's allowed to re-post honorbuddy i have 408/406 and 404 but not willing to get a ban over reposting (as they can't verify the exe hasn't been tampered with which is the reason oskehode got a temp iirc)
 
Yeah Kaz i feel yah, When i posted i rolled back a ver i got 4 pm's asking me for it, ignored them =/ I don't want DB to get force closed
 
Clean install of 410 BETA.
I'm not using Belphegor I'm just reporting the compile error :)

Code:
12:21:04.624 DEBUG MainWindow Start/Stop Button Clicked!
12:21:04.699 DEBUG AssemblyLoader`1 Reloading AssemblyLoader<Zeta.Bot.ICombat> - RoutineManager.Reload
12:21:05.146 INFO  AssemblyLoader`1 Compiler Error: d:\Buddy\410_1\Routines\Belphegor\Routines\Monk.cs(245,52) : error CS0117: 'Zeta.Game.Internals.Actors.SNOPower' does not contain a definition for 'Monk_DashingStrike'
12:21:09.374 INFO  RoutineManager Chose Trinity as your combat routine
 
Clean install of 410 BETA.
I'm not using Belphegor I'm just reporting the compile error :)

Code:
12:21:04.624 DEBUG MainWindow Start/Stop Button Clicked!
12:21:04.699 DEBUG AssemblyLoader`1 Reloading AssemblyLoader<Zeta.Bot.ICombat> - RoutineManager.Reload
12:21:05.146 INFO  AssemblyLoader`1 Compiler Error: d:\Buddy\410_1\Routines\Belphegor\Routines\Monk.cs(245,52) : error CS0117: 'Zeta.Game.Internals.Actors.SNOPower' does not contain a definition for 'Monk_DashingStrike'
12:21:09.374 INFO  RoutineManager Chose Trinity as your combat routine

same:(
 
I also did a fresh install of newest DB 410 + Trinity 1.9.5 + questtools 2.0.74 + EzUpdater -0.2.1
and after 5 minutes using the new version it suddenly crashs and stop working.

So i did a fresh install all over again without ezupdater
Same result, crash after 5 minutes of using.


Ps : Tried multiple profiles (not a profile probleman )
It was working fine before 410 ( 408 ), 12-16 hours straight runs without errors.



Cant revert to 408 again because i dont have the file of 408 installation.

From what i can notice several people are getting the same error/crashs, i suggest DB Team in this cases to always leave behind the download link of the previous working Beta version after a realease of a new db beta version that may work or may not work. ( this would fix everyone problemans while DB Team get the newest version to work properly.
 
I also did a fresh install of newest DB 410 + Trinity 1.9.5 + questtools 2.0.74 + EzUpdater -0.2.1
and after 5 minutes using the new version it suddenly crashs and stop working.

So i did a fresh install all over again without ezupdater
Same result, crash after 5 minutes of using.


Ps : Tried multiple profiles (not a profile probleman )
It was working fine before 410 ( 408 ), 12-16 hours straight runs without errors.



Cant revert to 408 again because i dont have the file of 408 installation.

From what i can notice several people are getting the same error/crashs, i suggest DB Team in this cases to always leave behind the download link of the previous working Beta version after a realease of a new db beta version that may work or may not work. ( this would fix everyone problemans while DB Team get the newest version to work properly.

I'm not sure if this is what you are experiencing, but I noticed that my anti-virus was quarantining some files from the main DB directory and then it started crashing. I restored the files and things worked again. Might look out for that.
 
I'm not sure if this is what you are experiencing, but I noticed that my anti-virus was quarantining some files from the main DB directory and then it started crashing. I restored the files and things worked again. Might look out for that.

I dont even use an AV, so i guess thats not the issue.
 
ye it keeps relogging DB...I tried it on my PC...on my VM...also new clean installs of DB...
 
Maybe we can request them to repost 408? That seem to be the most stable beta build.
 
Status
Not open for further replies.
Back
Top