Bot update for bugs in the bot

How easily you forget the nav server dieing almost every fucking day for the past nearly 2 years or the nav server not being able to handle all the connections it had and dumping people so it was a lottery if your bot worked 5 minutes after you turned it on. Or the nav server being left to rot in a crashed status for DAYS AT A FUCKING TIME until someone could be fucking bothered to restart it.

Other bots work fucking fantastic with local nav meshes for other mmo's, buddy has to move away from this nav server bullshit and move forward with local nav meshes like all the other bots in existence.

P.S. Sorry for the harsh words, but blind praise for the shit fucking service we have had over the past two years takes a while to wash away. Things are definitely better but for a service we fucking pay for, this fucking thing should be worked on daily, Not with the attitude aaahhh fuck it, maybe one day every 6 months we will put in a few hours to fix 1 minor thing and everyone will suck our dick for it.

 

However, you then have the chicken/egg problem. To have the correct profiles, you need the people and to have the people, you need the profiles. A few of us are working on them slowly but I doubt it will ever be extensive as HB profiles.

 

If youre edited quest profiles are running peachy, may i ask which you have edited and do you want to share them?
I will take them in with my revised quest profiles, so the community gets more profiles now. You can also PM me about this if you want.

Secondly, you should have issues with Mesh, UseItem and UseObject. Did you encounter any of these?

If you are actively editing these files, please join me

 

Thank you for expressing how I felt about that post, lol.

I'm still having terrible nav mesh problems.

Makeb went down today... which is where all my money is made.

Please fix Makeb. This bot makes me good money and I'd like more sessions if it worked better.

You guys are awesome. Please fix it. =D

 

@Sheezle - Since the last round of re-meshing, I've been able to fix the occasion nav errors by closing the bot, deleting all files in the CompiledAssemblies folder, and then restarting the bot. Let me know if that works for you on Makeb.

Cheers,
-D

 

I tried this on 2 computers and it didn't make a difference on Makeb Westwater Settlements or on Quesh and Balmorra. Also tried this with and without any plugins enabled.
I appreciate the advice though. Might work for later troubleshooting.

Wilderness Clearing on Makeb is working now. Which is awesome!

Where you land on Hoth seems to be working great too.

Thank you Buddywing team!

 

nice info

 

Any word from the devs about the other issues?
I really would like to help where ever i can on useobject and useitem...
If these could get fixed questing shouldnt give anymore issues, apart from the torobject and gethealth bug.

 

If framelocking is used in a routine it can prevent some of these "bugs". Its more or less how some routines are made. So not all these issues are buddywing issues but more of how custom combat's are designed. I used some frame locking on my routine but other parts are not. I learned about frame locking towards the end of when I was working on it a lot and never went though to redo it all. I just don't have the time like I did when I was in college since my current job requires lots of traveling.

 

Thanks for the reply...

I know your time is limited but are you going to update your routine? Or did you abandoned it?
Still the bugs im talking about happends with all routines, so it has to be something about the coding inside the bot.
And then we are not talking about any other issues / questions i got, where NO ONE answers...

Heck even the torobject, cant read memory and Hero 'bugs' could be 'fixed' by creating a dumb BW reboot process.
For example if Torobject gets spammed like 10 times in 10 secs, reboot and carry on.

But yeah some issues are hard, but in my oppinion something like should be hard to implement...

 

None of the routines are framelocked. I was the only person to ever do it for buddywing. People are not programming stuff in correct treesharp. You have to realize that PureSWTOR is just a copy of a wow routine with buddywing commands in it. Was never all done by ama and because of this issues are all over. I am not going to go into someone else's hard word and talk it down but its not correct. Thus the issues you see.

Also in my routine I already have a reset to prevent those errors its why my routine last longer than most when botting.

I will get around to updating it when the free time comes up. I just have lost interest in swtor and moved on sadly from playing MMOs as much.

 

Fully understandable... Have reached that point some times, but got back also many times

Anyways it still aint the routines only and Hawker was going to look into the matter, so i was wondering, what is Bossland GmbH planning or not with this bot...
Can we expect some improvements over time or not?

 

Bot does have a few issues but lots of these issues are from bad CC take my word for it. You can tell me its not all day long you think its buddywing but lots of these issues are from the routines not being done in treesharp correctly and no frame locking. They look into many issues and have fixed some but its hard to invest money and time into a bot that has not even half the users of other products here at bossland. Not saying buddywing isn't important but not as profitable as other products since more users. You can compare the forums to see for your self.

 

Ok understandable.
May i ask how far you came along befor pausing your work on the CC?
Is it possible that maybe you code the base of the routine and i code in the rotations and possibly quest specifics?

Dont feel obligated, all im doing is asking, what we can expect, nothing more nothing less.

 

Something I will be getting back to over the summer. Rotations are the easy part . The is just testing and debugging stuff as I go along. I really haven't sat down and did anything major on my routine in a while. Just lots of other projects I work on for side work and my job as a biomedical programmer. I would love to spend all the time in the world on my routine just not enough hours in the day .

 

True true

 

There was an issue i was having earlier about Forcing interact. it would sit there, in a corner of a map and just try to interact with someone who was 50m away by continuiously casting un-natural might, or just sporadically activating the healing power, for absolutely no reason, im not sure if thats a profile bug or an actual bug with the bot, so i figured id post it here.

 

Meh i think its more a profile issue.
Best to create an own thread in support and post a log.

 

Oh, the indirect references....

1. No, my code isn't 'Proper C#.' In the beginning, I was just trying to get the damn thing to WORK, period. So sorry for the ugly and improper code. And as a side-note, I had NO EXPERIENCE with C# going into this (and I'm sure it shows).
2. Frame-locking: Finally sunk-in about 6 weeks back that all of the errors were due to shifting pointers, and at that point I added it all over the place.
3. Questing: Yes, with the GC I set up, it did, MANY, MANY, TIMES, mess up questing (and for that I've since added a Profile Reload Block - otherwise it's Object-Reference-Errors Galore since the object reference isn't checked apparently inside of BrainBehavior, within the .exe).

If you're not referring (repeatedly) to Joe's, forgive the above. I just keep reading this again and again, and have to reply if it's directed at ME.

Joe

 

Directed at no one. Not assaulting anyone but just letting people know what causing issues. I mean pure swtor is just clone of the WOW CC. Ama changed nothing really in the code but doesn't bother me. People can use the bot and if some one wants to invest the time to do everything in treesharp and framelock would fix some issues is what I was conveying. I was in the same boat as you being clueless to what all of this was. You have done a great job at everything joe!