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

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

[Beta] Demonbuddy beta builds

Status
Not open for further replies.
i did several clean installs now, if i add trinity 20 to DBBeta 384, trinity will not show up in the plugin tab.

only error that shows up in DB on startup:

Compiler Error: d:\apps\DemonbuddyBETA 1.1.1786.384\Plugins\Trinity\Combat\Abilities\Wizard.cs(230,122) : error CS1026: ) expected
 
I don't know if you're reading these posts Nesox, but if you do It would be appreciated if you could acknowledge them some way or another. I don't think that is an unreasonable request.
 
Oksehode said:
I don't know if you're reading these posts Nesox, but if you do It would be appreciated if you could acknowledge them some way or another. I don't think that is an unreasonable request.
Click to expand...

Nesox reads and investigates every post where errors/bad performance are being caused by the DB client. If your error isn't related to DB and is something wrong with your PC he won't look into it. Honestly I don't think it would be time efficient for Nesox to respond to every error/problem saying that it's being looked in to. That's how most scripts/profiles/whatever start (look at any of the popular ones), but after awhile the dev just goes through unread posts and writes down any of the common errors. Just assume he looks at your post. If you have an error that doesn't get solved after a couple patches, gather convincing evidence that it's something wrong with DB, and post on the support forums.
 
_Steve_ said:
Nesox reads and investigates every post where errors/bad performance are being caused by the DB client. If your error isn't related to DB and is something wrong with your PC he won't look into it. Honestly I don't think it would be time efficient for Nesox to respond to every error/problem saying that it's being looked in to. That's how most scripts/profiles/whatever start (look at any of the popular ones), but after awhile the dev just goes through unread posts and writes down any of the common errors. Just assume he looks at your post. If you have an error that doesn't get solved after a couple patches, gather convincing evidence that it's something wrong with DB, and post on the support forums.
Click to expand...

I know for sure it's DB and not my computer because it worked fine for days end before 2.0.4 and beta 380 of DB. There is many other people with the same problem. There is a memoryleak in DB that makes Diablo run like a slideshow after 2-3 hours and the second i pause the bot, everything is fine. When Demonbuddy.exe exceeds 1.3/1.4gb of memory, this happens. I have lots of extra memory to spare.

And making a post now and again that the issue is being looked at is better than not hearing anything at all. It doesn't take long and its reassuring to the customers of DB. I'm sure the longtime users of DB is fine with things like they are now, but there is a lot of new users everyday that don't like being kept in the dark with no knowledge if the issue is under investigation.
 
Last edited:
New beta up.

Changelog 388
  • General
    • Vendoring in Act 1 adventure mode works again.
    • Bounty/Quest API improved and partially rewritten.
    • QuestInfo pointers should no longer get tained after a while.
    • Now closes bounty reward dialogs whenever a bounty is completed.
    • Should no longer attempt to stash 2 square items in the last row on the fourth page of the stash.
    • No longer attempts to update profile behaviors during town runs.
  • API Changes
    • ConditionParser.IsActiveQuest now works with bountes.
    • ConditionParser.HasQuest added.
 
Last edited:
Nesox said:
New beta up.

Changelog 387
  • General
    • Vendoring in Act 1 adventure mode works again.
    • Bounty/Quest API improved and partially rewritten.
    • QuestInfo pointers should no longer get tained after a while.
    • Now closes bounty reward dialogs whenever a bounty is completed.
    • Should no longer attempt to stash 2 square items in the last row on the fourth page of the stash.
    • No longer attempts to update profile behaviors during town runs.
  • API Changes
    • ConditionParser.IsActiveQuest now works with bountes.
    • ConditionParser.HasQuest added.
Click to expand...

Code: 
Compiler Error: c:\Users\Stonga\Desktop\DB\Plugins\Trinity\Combat\TargetCheck.cs(136,46) : error CS0103: The name 'Composites' does not exist in the current context
Compiler Error: c:\Users\Stonga\Desktop\DB\Plugins\Trinity\Helpers\BotManager.cs(30,25) : error CS0234: The type or namespace name 'Composites' does not exist in the namespace 'Trinity.Helpers' (are you missing an assembly reference?)
 
Hitori said:
Is there any fix for when using townrun in Act1? Atm it just run against the fence and stands there.
Click to expand...
Tomas2209 said:
i checked the behavior why it happens that the bot gets stuck at the gate in act 1 and its during a shop routine it leaves 1+ items in the inventory during the selling which causes the bot to go nuts. if i sell the item manually the bot continues normally by taking the tp
Click to expand...
Oksehode said:
Code: 
Compiler Error: c:\Users\Stonga\Desktop\DB\Plugins\Trinity\Combat\TargetCheck.cs(136,46) : error CS0103: The name 'Composites' does not exist in the current context
Compiler Error: c:\Users\Stonga\Desktop\DB\Plugins\Trinity\Helpers\BotManager.cs(30,25) : error CS0234: The type or namespace name 'Composites' does not exist in the namespace 'Trinity.Helpers' (are you missing an assembly reference?)
Click to expand...

New beta up again, forgot some stuff for Trinity.
 
Getting this exception.

Using Waypoint. Number:42
Using Waypoint. Number:42
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 00000198, Size: 12
at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
at GreyMagic.MemoryBase.Read[T](IntPtr addr)
at Zeta.Game.Internals.Actors.DiaObject.get_Position()
at Zeta.Bot.InactivityDetector.(Object , EventArgs )
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Reflection.RuntimeMethodInfo.UnsafeInvoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at System.Delegate.DynamicInvoke(Object[] args)
at Zeta.Bot.Pulsator.(Delegate , Object[] )
 
I've noticed that increasing the waitTime in profiles helps with this problem. If the waitTime is to low, it keeps spamming the waypoint and that's what generate this error I think.
 
beta 388 with trinity 21 do nothing. bot just stay at oneplace. fresh install doesn't help
release version works fine
 
Last edited:
Okay, it seems Trinity install is the problem... Either DELETE Trinity in Plugins and download manually, or go inside the Trinity Folder and drag the shit inside the Source Folder. EZUpdater seems to be screwing shit up with updating Trinity.

"Trinity\trunk\Sources" <-- The proper files are in there. So just copy them back out to Trinity.

Apparently it is the same if you use EZUpdater for all your shit too. Like QuestTools, etc... So... yeah!
 
Last edited:
Status
Not open for further replies.
Back
Top