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

The devs believe the bot is working...

B

Blimey

New Member
Joined
Jul 4, 2014
Messages
78
Reaction score
0
So after the bot not working at all and now only running for an hour to an hour and a half I was told that the bot is working how it should be. I used to run the bot for up to 4 days at a time before it was broken and it definitely does not work the way it used to.

Is anyone else experiencing problems like mine ? I made this new thread to see how many are being affected and to bring it to the attention of the developers.

I made sure I ran buddywizard to check I had everything installed correctly and I do. Below is the log from the last kill the bot made and shit itself.

[06:43:34.078 N] [DefaultCombat] >> Casting << Weaken Mind
[06:43:34.471 N] [DefaultCombat] >> Casting << Mental Alacrity
[06:43:35.257 N] [DefaultCombat] >> Casting << Weaken Mind
[06:43:39.211 D] [POI Set] Type: Kill
[06:43:41.581 N] [DefaultCombat] >> Casting << Weaken Mind
[06:43:42.888 N] [DefaultCombat] >> Casting << Turbulence
[06:43:45.025 N] [DefaultCombat] >> Casting << Mind Crush
[06:43:47.644 N] [DefaultCombat] >> Casting << Telekinetic Gust
[06:43:48.952 D] Function GetEffectName does not exist.
[06:43:48.952 D] at ​‏‪‏***‬*‪‪*‏*‏*​‎​**‏​**.**‬*‏*‏​​*‫**‪‪‏*‫‪**‬‫‫*‬​‎​**.‪‪‬****‬‬**‎‬‏**‫​*‫‏‫*[](Boolean , String , Object[] )
at Buddy.Swtor.Objects.TorObject.CallScript[T](Boolean hasReturnValue, String function, Object[] args)
at Buddy.Swtor.Objects.TorEffect.get_Name()
at DefaultCombat.Helpers.Extensions.<IsCrowdControlled>b__15(TorEffect d)
at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source, Func`2 predicate)
at DefaultCombat.Helpers.Extensions.IsCrowdControlled(TorCharacter torCharacter)
at DefaultCombat.Helpers.Extensions.IsValidTarget(TorCharacter c)
at DefaultCombat.Core.Targeting.<get_ScanTargets>b__0(Object param0)
at Buddy.BehaviorTree.Action.RunAction(Object context)
at Buddy.BehaviorTree.Action.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.BehaviorTree.PrioritySelector.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at DefaultCombat.Core.LockSelector.Tick(Object context)
at Buddy.BehaviorTree.Decorator.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.BehaviorTree.PrioritySelector.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.Common.HookExecutor.Run(Object context)
at Buddy.BehaviorTree.Action.RunAction(Object context)
at Buddy.BehaviorTree.Action.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.BehaviorTree.PrioritySelector.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.BehaviorTree.Decorator.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.BehaviorTree.PrioritySelector.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.BehaviorTree.Decorator.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.BehaviorTree.PrioritySelector.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.BehaviorTree.Decorator.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.BehaviorTree.PrioritySelector.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.CommonBot.BotMain.**‎*‪​***‏‫‏‫‏​***‏****​‎‏‏*()
[06:43:49.247 N] [DefaultCombat] >> Casting << Telekinetic Burst
[06:43:50.289 V] [Poi.Clear] Reason: I'm in combat, but POI isn't. Clearing POI and picking up a new target.
[06:43:50.472 D] Combat: Set POI to Kill.
[06:43:50.473 D] [POI Set] Type: Kill
[06:43:50.474 N] Killing ********** with 84.24292% health at 20.65 meters
[06:43:50.697 N] [DefaultCombat] >> Casting << Weaken Mind
[06:43:52.233 N] [DefaultCombat] >> Casting << Turbulence
[06:43:55.104 N] [DefaultCombat] >> Casting << Telekinetic Wave
[06:43:55.111 D] Injection resulted in a process exception with error code 0xc0000005
[06:43:55.111 D] at GreyMagic.Executor.**‬‏‪‫*‪‬‏‪​‬****‪‫*‎*‏‏**(Int32 )
at GreyMagic.Executor.​‎*‪‎‏​**‪*‬*‏‪‏*‫‬*‎‏‫‏*(Int32 )
at GreyMagic.Executor.Execute(Int32 timeout)
at Buddy.Swtor.BuddyTor.‬*‪‫‎*‪‫‪*‫‎‪*‪**‫*‪​**‪‏**[](UInt64 , ‫‏*​‪‏**‎*‬​​*‪‎‬**​‏‪​​*‏** , Boolean , Object[] )
at ​‏‪‏***‬*‪‪*‏*‏*​‎​**‏​**.**‬*‏*‏​​*‫**‪‪‏*‫‪**‬‫‫*‬​‎​**.‪‪‬****‬‬**‎‬‏**‫​*‫‏‫*[](Boolean , String , Object[] )
at Buddy.Swtor.Objects.TorObject.CallScript[T](Boolean hasReturnValue, String function, Object[] args)
at Buddy.Swtor.Objects.TorPlayer.AbilityActivate(TorAbility ability, TorCharacter character, EffectResult& er)
at Buddy.CommonBot.AbilityManager.Cast(String name, TorCharacter onCharacter)
at DefaultCombat.Core.Spell.<>c__DisplayClass9.<Cast>b__8(Object ret)
at Buddy.BehaviorTree.Action.RunAction(Object context)
at Buddy.BehaviorTree.Action.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.BehaviorTree.PrioritySelector.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.BehaviorTree.Decorator.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.BehaviorTree.PrioritySelector.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at DefaultCombat.Core.LockSelector.Tick(Object context)
at Buddy.BehaviorTree.PrioritySelector.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at DefaultCombat.Core.LockSelector.Tick(Object context)
at Buddy.BehaviorTree.Decorator.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.BehaviorTree.PrioritySelector.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.Common.HookExecutor.Run(Object context)
at Buddy.BehaviorTree.Action.RunAction(Object context)
at Buddy.BehaviorTree.Action.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.BehaviorTree.PrioritySelector.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.BehaviorTree.Decorator.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.BehaviorTree.PrioritySelector.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.BehaviorTree.Decorator.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.BehaviorTree.PrioritySelector.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.BehaviorTree.Decorator.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.BehaviorTree.PrioritySelector.**‎​*​‏*‎‫**‏‬*‫‎‪*​‫*‬*.MoveNext()
at (IEnumerator )
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.CommonBot.BotMain.**‎*‪​***‏‫‏‫‏​***‏****​‎‏‏*()
[06:43:57.890 N] [DefaultCombat] >> Casting << Telekinetic Wave
[06:44:01.511 V] [Poi.Clear] Reason: Targeted unit is dead, clearing Poi and carrying on!
[06:44:03.636 N] Moving to Mercenary Bruiser at 1.132698 meters.
[06:44:03.636 D] [POI Set] Type: Loot
[06:44:03.641 D] Object reference not set to an instance of an object.
[06:44:03.641 D] at Buddy.Swtor.ObjectManager.‪‬*‪**‫**‏*‎‫​‏*‫‏***‬‏**(KeyValuePair`2 )
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at (IEnumerator )
at Buddy.Swtor.ObjectManager.Update()
at Buddy.CommonBot.Pulsator.‎*‬*‬*​‪*‫‏‎*‎​‫‎‬‎‪‫‬*​‬‏‎‪*()
at Buddy.CommonBot.BotMain.**‎*‪​***‏‫‏‫‏​***‏****​‎‏‏*()
[06:44:03.710 D] Object reference not set to an instance of an object.
[06:44:03.710 D] at Buddy.Swtor.ObjectManager.‪‬*‪**‫**‏*‎‫​‏*‫‏***‬‏**(KeyValuePair`2 )
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at (IEnumerator )
at Buddy.Swtor.ObjectManager.Update()
at Buddy.CommonBot.Pulsator.‎*‬*‬*​‪*‫‏‎*‎​‫‎‬‎‪‫‬*​‬‏‎‪*()
at Buddy.CommonBot.BotMain.**‎*‪​***‏‫‏‫‏​***‏****​‎‏‏*()
[06:44:03.714 D] Object reference not set to an instance of an object.
[06:44:03.714 D] at Buddy.Swtor.ObjectManager.‪‬*‪**‫**‏*‎‫​‏*‫‏***‬‏**(KeyValuePair`2 )
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at (IEnumerator )
at Buddy.Swtor.ObjectManager.Update()
at Buddy.CommonBot.Pulsator.‎*‬*‬*​‪*‫‏‎*‎​‫‎‬‎‪‫‬*​‬‏‎‪*()
at Buddy.CommonBot.BotMain.**‎*‪​***‏‫‏‫‏​***‏****​‎‏‏*()
[06:44:03.783 D] Object reference not set to an instance of an object.
[06:44:03.783 D] at Buddy.Swtor.ObjectManager.‪‬*‪**‫**‏*‎‫​‏*‫‏***‬‏**(KeyValuePair`2 )
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at (IEnumerator )
at Buddy.Swtor.ObjectManager.Update()
at Buddy.CommonBot.Pulsator.‎*‬*‬*​‪*‫‏‎*‎​‫‎‬‎‪‫‬*​‬‏‎‪*()
at Buddy.CommonBot.BotMain.**‎*‪​***‏‫‏‫‏​***‏****​‎‏‏*()
[06:44:03.787 D] Object reference not set to an instance of an object.
[06:44:03.787 D] at Buddy.Swtor.ObjectManager.‪‬*‪**‫**‏*‎‫​‏*‫‏***‬‏**(KeyValuePair`2 )
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at (IEnumerator )
at Buddy.Swtor.ObjectManager.Update()
at Buddy.CommonBot.Pulsator.‎*‬*‬*​‪*‫‏‎*‎​‫‎‬‎‪‫‬*​‬‏‎‪*()
at Buddy.CommonBot.BotMain.**‎*‪​***‏‫‏‫‏​***‏****​‎‏‏*()
[06:44:03.856 D] Object reference not set to an instance of an object.
[06:44:03.856 D] at Buddy.Swtor.ObjectManager.‪‬*‪**‫**‏*‎‫​‏*‫‏***‬‏**(KeyValuePair`2 )
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at (IEnumerator )
at Buddy.Swtor.ObjectManager.Update()
at Buddy.CommonBot.Pulsator.‎*‬*‬*​‪*‫‏‎*‎​‫‎‬‎‪‫‬*​‬‏‎‪*()
at Buddy.CommonBot.BotMain.**‎*‪​***‏‫‏‫‏​***‏****​‎‏‏*()
[06:44:03.860 D] Object reference not set to an instance of an object.
[06:44:03.860 D] at Buddy.Swtor.ObjectManager.‪‬*‪**‫**‏*‎‫​‏*‫‏***‬‏**(KeyValuePair`2 )
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at (IEnumerator )
at Buddy.Swtor.ObjectManager.Update()
at Buddy.CommonBot.Pulsator.‎*‬*‬*​‪*‫‏‎*‎​‫‎‬‎‪‫‬*​‬‏‎‪*()
at Buddy.CommonBot.BotMain.**‎*‪​***‏‫‏‫‏​***‏****​‎‏‏*()
[06:44:03.929 D] Object reference not set to an instance of an object.
[06:44:03.929 D] at Buddy.Swtor.ObjectManager.‪‬*‪**‫**‏*‎‫​‏*‫‏***‬‏**(KeyValuePair`2 )
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at (IEnumerator )
at Buddy.Swtor.ObjectManager.Update()
at Buddy.CommonBot.Pulsator.‎*‬*‬*​‪*‫‏‎*‎​‫‎‬‎‪‫‬*​‬‏‎‪*()
at Buddy.CommonBot.BotMain.**‎*‪​***‏‫‏‫‏​***‏****​‎‏‏*()

It continues to loop this message for another 17 meg. Does anyone know what may be causing this ?
 
I'm not sure exactly what it is, but I have had issues where the bot appears to be running but the game is frozen. When I close out SWTOR and reopen my toon is dead. The bot is running and looping the same garble-dee-dook.
 
It is still broken, I don't believe anyone would say that it is working as intended currently. In the main thread when they newest release was pushed (past 648) everyone said that 648 was more stable, but ran slower. I ran 648 for days straight now I can't last more than a few hours without it crashing.

Though if 648 was stable, it will be stable again. It has been broken for many months now, we just gotta wait not much more we can say or do.
 
I'm just glad that questing is working now ... though must profiles are probably in need of a major overhaul for them to work well again, or maybe I just expect too much when wishing for it to be able like honorbuddy in WoW.
 
Altard said:
It is still broken, I don't believe anyone would say that it is working as intended currently. In the main thread when they newest release was pushed (past 648) everyone said that 648 was more stable, but ran slower. I ran 648 for days straight now I can't last more than a few hours without it crashing.

Though if 648 was stable, it will be stable again. It has been broken for many months now, we just gotta wait not much more we can say or do.
Click to expand...


Below is an email from Tony the support guy...

Tony (Bossland GmbH)
Jun 4, 12:15

the report from our devs is that bot working as it should tho

Moderator Tony
Honorbuddy Gatherbuddy
Demonbuddy Buddy Wing Tankleader Exilebuddy
Winterbuddy


So it seems the DEVs themselves think the bot is fine...
 
Blimey said:
Below is an email from Tony the support guy...

Tony (Bossland GmbH)
Jun 4, 12:15

the report from our devs is that bot working as it should tho

Moderator Tony
Honorbuddy Gatherbuddy
Demonbuddy Buddy Wing Tankleader Exilebuddy
Winterbuddy


So it seems the DEVs themselves think the bot is fine...
Click to expand...

He isnt the Dev, he's support. Until the sticky "the current state of the bot" becomes unstickied I wouldnt call the bot fixed.

In the very first sentence of that sticky Aevitas says the bot is broken. I don't think if it was fully operational they would leave the sticky up which definitely deters some customers

Aevitas said:
As you are all probably aware, BuddyWing is still facing crashing issues when attempting to interact with objects, picking up quests and a handful of other actions.

[*]The bot will be fixed, we currently have no plans of retiring it
Click to expand...

I honestly can't explain why Tony said it was fixed or working when Aevitas has not publically stated it is fixed or working and the sticky thread is still there saying that the bot is broken and they are fixing it. I guess just simple miscommunication
 
Lets hope so, because that so far it is the latest from anyone from Buddywing on the subject.
 
From my use of the bot with questing, it can run for hours. I've never gotten it to crash during questing, actually.

I HAVE had it stop working properly in various, forcing me to restart it. Not sure if that's related to the quest profile (seems to be though).
 
The bot runs for about an hr and freezes, this is on every pc i own.

IT IS NOT FIXED
 
Yep there is another freeze after 25 mins

THIS BOT IS NOT FIXED, its happening on multiple computers, so its not the pc, its the program

fix this please
 
I think that the problem is all the same. Bot runs about an hour. Then when looting disappearing blue rays pointing to loot. Bot freezing and it should be restarted. I am sure that the developers know it. I have it on 5 computers in three different classes. About the fact that the bot does not run on win8 also discussed.
 
nosfi said:
About the fact that the bot does not run on win8 also discussed.
Click to expand...

I agree with the freezing and crashes (not always attributed to bot, but often is), but do not understand why you say BW does not run on Win8? It runs on 8.1, so I just assumed it would run on 8.0 as well? Why would you want to run Win 8.0 OS though? Is there some secret benefit to Win 8.0 above 8.1? :)
Not sure about 10 though...Is
 
Last edited:
strepie said:
I agree with the freezing and crashes (not always attributed to bot, but often is), but do not understand why you say BW does not run on Win8? It runs on 8.1, so I just assumed it would run on 8.0 as well? Why would you want to run Win 8.0 OS though? Is there some secret benefit to Win 8.0 above 8.1? :)
Not sure about 10 though...Is
Click to expand...

currently no bots are supported on 10 by gambitsoft, or so they've said on honorbuddy.

I have windows 7 and 8.1 and it runs the same on both OS for me, same length before crash, same type of crashes etc
 
Altard said:
currently no bots are supported on 10 by gambitsoft, or so they've said on honorbuddy.

I have windows 7 and 8.1 and it runs the same on both OS for me, same length before crash, same type of crashes etc
Click to expand...

Must remind myself not to install 10 then. :)
Thx for the heads up. I did notice a little icon in my task-bar lately telling me to "get windows 10".
haha..maybe the bot will only run on Kali :P
 
Altard said:
He isnt the Dev, he's support. Until the sticky "the current state of the bot" becomes unstickied I wouldnt call the bot fixed.

In the very first sentence of that sticky Aevitas says the bot is broken. I don't think if it was fully operational they would leave the sticky up which definitely deters some customers

I honestly can't explain why Tony said it was fixed or working when Aevitas has not publically stated it is fixed or working and the sticky thread is still there saying that the bot is broken and they are fixing it. I guess just simple miscommunication
Click to expand...

Because I told him it was. And fixed in that context was whether or not we'll be extending keys for free for another month, which we didn't beyond the two months when the bot was completely unusable.

Currently, the bot is as stable as we can get it with a broken game engine. The game freezing after a certain period of time doesn't have anything to do with a bug in the bot itself - the game corrupts its own memory while lazily instantiating certain objects every once in a while. The game itself chokes on this as well, but manages to recover fully from it. We've implemented mechanics that handle these exceptions, and then run code to allow continued execution of both the game and the bot. This works 99% of the time, with the 1% being the freezes or crashes you're experiencing. These mechanics are extremely complicated in nature, and take time to write and perfect.

Fortunately, these crashes and/or freezes are still completely random and you're at the game's mercy with them - some of my testers have reported running bots for days on end without them crashing. Myself, I've been running a quest bot for the better part of a working day (about 10 hours) straight, without any crashes.

I'll be pushing a release shortly which allows you to mimic the behaviour of 648 if you so desire by setting two command line options, -noveh and -nolazy. When running under those command line arguments, the game may crash whenever it sicks all over itself, but at least you have the choice.
 
Oh man, thanks for the update Aevitas but could you drop in a little more frequently and provide us with this type of information please ?

Maybe you could make a post for users to submit their observations and possibly help you in some way ?

How long will the 648 clone be ready ?
 
Blimey said:
Oh man, thanks for the update Aevitas but could you drop in a little more frequently and provide us with this type of information please ?

Maybe you could make a post for users to submit their observations and possibly help you in some way ?

How long will the 648 clone be ready ?
Click to expand...

Well to be fair it's been posted quite a few times. We've been running with a group of testers who have been giving feedback on the bot and have helped us getting it back to where it is now - not crashing after 2 minutes anymore. To me, people running the bots for hours or in some cases even days is far better than them running it for mere minutes. Sure, the bot needs some babysitting now but it's not unworkable like it used to be.

The update's just been released, and if you want to start a thread in which actual useful feedback is given, such as problematic classes, actions the bot was carrying out when the game froze, stuff that will actually help us track down further issues then I'm all for it. Random crashes are extremely painful to analyze, obviously because they can not consistently be reproduced, but also because they differ per machine. Anything that helps with it is greatly appreciated.
 
Aevitas said:
Because I told him it was. And fixed in that context was whether or not we'll be extending keys for free for another month, which we didn't beyond the two months when the bot was completely unusable.

Currently, the bot is as stable as we can get it with a broken game engine. The game freezing after a certain period of time doesn't have anything to do with a bug in the bot itself - the game corrupts its own memory while lazily instantiating certain objects every once in a while. The game itself chokes on this as well, but manages to recover fully from it. We've implemented mechanics that handle these exceptions, and then run code to allow continued execution of both the game and the bot. This works 99% of the time, with the 1% being the freezes or crashes you're experiencing. These mechanics are extremely complicated in nature, and take time to write and perfect.

Fortunately, these crashes and/or freezes are still completely random and you're at the game's mercy with them - some of my testers have reported running bots for days on end without them crashing. Myself, I've been running a quest bot for the better part of a working day (about 10 hours) straight, without any crashes.

I'll be pushing a release shortly which allows you to mimic the behaviour of 648 if you so desire by setting two command line options, -noveh and -nolazy. When running under those command line arguments, the game may crash whenever it sicks all over itself, but at least you have the choice.
Click to expand...

Hi Aevitas,

Would you be willing to tell us which quest profile you are running and what class? Just curious what you can get to run that long :-)
 
Aevitas said:
Because I told him it was. And fixed in that context was whether or not we'll be extending keys for free for another month, which we didn't beyond the two months when the bot was completely unusable.

Currently, the bot is as stable as we can get it with a broken game engine. The game freezing after a certain period of time doesn't have anything to do with a bug in the bot itself - the game corrupts its own memory while lazily instantiating certain objects every once in a while. The game itself chokes on this as well, but manages to recover fully from it. We've implemented mechanics that handle these exceptions, and then run code to allow continued execution of both the game and the bot. This works 99% of the time, with the 1% being the freezes or crashes you're experiencing. These mechanics are extremely complicated in nature, and take time to write and perfect.

Fortunately, these crashes and/or freezes are still completely random and you're at the game's mercy with them - some of my testers have reported running bots for days on end without them crashing. Myself, I've been running a quest bot for the better part of a working day (about 10 hours) straight, without any crashes.

I'll be pushing a release shortly which allows you to mimic the behaviour of 648 if you so desire by setting two command line options, -noveh and -nolazy. When running under those command line arguments, the game may crash whenever it sicks all over itself, but at least you have the choice.
Click to expand...

Can you make a post about how to set those two -noveh and -nolazy command line options up?

648 was extremely stable and was friggen awesome.

I haven't the foggiest where to put those two command options in for Buddywing though
 
Aevitas, Question any idea why the bot stops working. like no error or anything. just the bot stop doing the rotations. Usually happens in the middle of FP. Any way I can give a log or something for you to see?
 
You must log in or register to reply here.
Back
Top