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!

bot does nothing at all

prolly ur routine.. only one tht rlly work sis joes. and even then tht one is very botish. so yah. im actually thinking about asking for a refund. lol i shoulda bought 1day trial instead. oh well.
 
changing the combat rotine did nto change anything. Bot does not move but fight if attacked.

Devs, what is this shit?
 
Last edited:
according to Aevitas giving it more restarts should fix it,try it and let me know
 
same is happening to me, im a level 4 inquisitor and when i click start on kicks 1-10 inquisitor and warrior, it just stands there and in the bot is just says equipping companions! like 20 times, i've restarted about 50 times, any help, if not ill probably ask for a refund
 
yes restarting several times, lol what is this? support?

i have already done this getting more disappointed.

Next thing is making refund for sure, what a piece of.....
Stick to the things you can do, which is hb and stick to it. it horrible. never ever again.
 
its not tht they cant do it. its just they dont work on it. because bw is not where the demand is. no onebuys bw. which is why i've said idk why they r selling it if they cant afford to support it 100%
 
Draganos said:
yes restarting several times, lol what is this? support?

i have already done this getting more disappointed.

Next thing is making refund for sure, what a piece of.....
Stick to the things you can do, which is hb and stick to it. it horrible. never ever again.
Click to expand...

yes,you are right

i will check it again with Aevitas
 
Thing is, I can't fix it. It's an intermittend bug in our code that communicates with the SWTOR client. I'll forward this to the appropriate person, but I really can't promise when it'll be fixed.
 
Aevitas said:
Thing is, I can't fix it. It's an intermittend bug in our code that communicates with the SWTOR client. I'll forward this to the appropriate person, but I really can't promise when it'll be fixed.
Click to expand...

Hi Aevitas,

Just to confirm what they're saying, the bot does seem to have more issues of this sort since the last update. In fact, two or three issues seem to be happening the most. Firstly:

[17:54:21.196 D] Generated path to <-24.7753, 0.992226, -85.86086> () with 1 hops.
[17:54:24.076 D] Generating path to <-24.75581, 0.992226, -85.88036>
[17:54:24.116 D] Raycast path generated.
[17:54:24.116 D] Generated path to <-24.75581, 0.992226, -85.88036> () with 1 hops.
[17:54:28.011 D] Generating path to <-24.82746, 0.992226, -85.80871>
[17:54:28.053 D] Raycast path generated.
[17:54:28.053 D] Generated path to <-24.82746, 0.992226, -85.80871> () with 1 hops.
[17:54:32.412 D] Generating path to <-24.77533, 0.992226, -85.86083>
[17:54:32.450 D] Raycast path generated.
[17:54:32.450 D] Generated path to <-24.77533, 0.992226, -85.86083> () with 1 hops.
[17:54:36.251 D] Generating path to <-24.75605, 0.992226, -85.88013>
[17:54:36.291 D] Raycast path generated.

Repeated until bot is stopped...
Click to expand...

and this:

[17:42:02.852 D] Object reference not set to an instance of an object.
[17:42:02.852 D] at Buddy.Swtor.Objects.TorObject.()
at ..()
at ..[](UInt64 , HeroType )
at Buddy.Swtor.Objects.TorObject.GetField[T](DomFieldIds field, HeroType forcedType)
at Buddy.Swtor.Objects.TorCharacter.get_Health()
at Buddy.Swtor.Objects.TorCharacter.get_IsDead()
at Buddy.Swtor.Objects.TorNpc.get_IsLootable()
at Buddy.CommonBot.DefaultLootTargetingProvider.(TorNpc )
at System.Linq.Enumerable.<>c__DisplayClassf`1.<CombinePredicates>b__e(TSource x)
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at Buddy.CommonBot.DefaultLootTargetingProvider.GetObjectsByWeight()
at Buddy.CommonBot.Targeting.Pulse()
at Buddy.CommonBot.Logic.BrainBehavior.()
[17:42:11.388 D] Object reference not set to an instance of an object.

Repeated until bot is stopped...
Click to expand...

and this one, similar to the error shown in the thread's earlier log:

[17:53:25.820 D] Field statHealth does not exist.
[17:53:25.820 D] at ..[](UInt64 , HeroType )
at Buddy.Swtor.Objects.TorObject.GetField[T](DomFieldIds field, HeroType forcedType)
at Buddy.Swtor.Objects.TorCharacter.get_Health()
at Buddy.Swtor.Objects.TorCharacter.get_IsDead()
at Buddy.CommonBot.Logic.BrainBehavior.(Object )
at Buddy.BehaviorTree.Decorator.CanRun(Object context)
at Buddy.BehaviorTree.Decorator..()
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.BehaviorTree.PrioritySelector..()
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.BehaviorTree.Decorator..()
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.BehaviorTree.PrioritySelector..()
at Buddy.BehaviorTree.Composite.Tick(Object context)
at Buddy.CommonBot.BotMain.()

Repeated until the bot is stopped...
Click to expand...

These issues were not nearly so frequent in the last BW update. Given how much better this ran (at least for me) in the previous version, is it possible that these issues are simply related to the memory locations being read in 981.373?
 
Just to reinforce what Dev is saying, the bot ran better for me previous patch as well, and even better the patch before that.
 
Aevitas said:
Thing is, I can't fix it. It's an intermittend bug in our code that communicates with the SWTOR client. I'll forward this to the appropriate person, but I really can't promise when it'll be fixed.
Click to expand...


This is also due to the hero engine. It works very different than most MMOs and the coding is just shit. Bioware each update breaks and fixes random bits of this code and it breaks certain things. These memory leaks may never be fixed since its just the swtor client. You can not blame buddy wing for being this way 100%.
 
walter said:
This is also due to the hero engine. It works very different than most MMOs and the coding is just shit. Bioware each update breaks and fixes random bits of this code and it breaks certain things. These memory leaks may never be fixed since its just the swtor client. You can not blame buddy wing for being this way 100%.
Click to expand...

That's true sadly, their HeroEngine stuff is just pure rubbish and tends to break at random. However, I have just released a patch which updates the DOM, and should make those "Field doe not exist" exceptions a lot less frequent or solves them altogether. Let me know how it works out.
 
Ah, this is just what the doctor ordered. Thanks for the time spent on this! So far, the new version is running well.

Cheers,
-D
 
You must log in or register to reply here.
Back
Top