The devs believe the bot is working...

Create a shortcut to Buddywing on your desktop.

RIght-click on the shortcut and go to Properties.

In this window, there should be a "Target" value. Add those options at the end. For example:

"C:\Bots\SWToR - Beta\Buddywing.exe" -noveh -nolazy

 

thank you very much, made the changes on two of 9 computers, gonna see how stable it is and report back

 

so far no crashes since my post, also the bot seems to run as good as the current version and as stable as 648.

Seems almost entirely fixed to me, how come we have to edit the properties and add that stuff, why not just incorporate it and push it into a live version? Not complaining, less people botting means more credits, meerly curious.

 

After adding those two changes I can honestly say it runs great. Only two computers experience crashes atm, one just completely closed out swtor and buddywing and didnt create any crash log (I think it was windows update in all honesty, but wont know without more time)

and the other computer got the hanging Not responding crash, but out of 5 bots I've ran 3 since I made my first post with 0 crashes and 0 issues.

The only thing that seems off or odd to me is that the bot doesn't vendor with the game minimized. Either that or I have been so lucky that every time i maximize the game to check on it im at the vendor and have just started vendoring

 

-noveh -nolazy best thing ever happend works without crahs since like 5hours... before this, the bot crashed after 1 hour everytime.

 

Why did he say use at your own risk though, is there increased risk? Also latest build doesn't set up correctly:
Unhandled exception during init: System.ComponentModel.Win32Exception (0x80004005): Only part of a ReadProcessMemory or WriteProcessMemory request was completed
at System.Diagnostics.NtProcessManager.GetModuleInfos(Int32 processId, Boolean firstModuleOnly)
at System.Diagnostics.ProcessManager.GetModuleInfos(Int32 processId)
at System.Diagnostics.Process.get_Modules()
at (Process )
at Buddywing.MainWindow.‪‏‪‎‏​​*‏‎‬​*​‎**‬**()

 

how are you keeping the bot questing for hours? every time I use a taxi or elevator it crashes me to my desktop do I need to change something or does the bot not handle taxis and elevators?

 

So does mine...but only from time to time.

 

with the noveh and nolazy changes ive been able to run a bot for 24hrs straight. Very happy with that, thank you <3

 

Thx God you came! It's made us less relogers than we were. (bow)

 

31 PCs doesn't freezes.. tested ~2 days

 

What does this mean?

[BuddyMonitor] You have enabled
BuddyMonitor but haven't entered your API key or your identifier yet! Open the configuration, set the values and restart BuddyWing.
Sell quality set to Premium.
Buddy Wing: The Old Robot is ready!

 

Not to be difficult, but for me the bot runs better and more stable with those options iow as is. When adding the arguments, it seems to mount less frequently - weird but true

Scratch all that. Works well with the arguments.

 

How about you just fucking leave it alone. the bot hasnt been working for over 3 months. Some random user comes along tells us the bot is working perfectly by putting in a couple arguments that take literally 15 seconds and now you want to fucking break it again ?

I would like to know why YOU didnt tell us how to fix it so simply.

 

.............

 

I guess you are off your meds again. The "random user" simply regurgitated what Aevitas wrote in 2 different messages (actually 3) regarding the command line arguments AND he explained WHY he was hesitant to make it permanent. So, please back off..I wanted to say f...off, but you are part of the furniture here it seems - all we can do is put you in dark a corner and hope no one sees you.