I'm curious if the devs are using this bot so they can see with their own eyes that the but is full of bugs, or they are just patching it so the bot can "work" with with the newest patch. Out of 15 bots, 1 or 2 are working acceptable (sometimes on those I get 8h unattended), but on the rest if I can get 1-2 hours its great... Same spec on all of my computers, (clean windows /swtor install, only the programs needed for the bot are installed on those systems) same swtor class, same grind profile on all.
I'm curious, what combat routine are you using? I noticed a massive stability increase when I switched from wingit to joes.
I tried default, wing and joe's , joe's 2.0 Wing it seems to be the most stable for my sniper imperial agents.
Wish I could help with snipers I don't have one so I'm not sure what would work best. Maybe give the new Joe's 2.0 build a try... that project has been making a lot of progress... maybe it'll work better. Not much help, but hopefully that'll help. Best of luck!
I have the same issues on 12 snipers , 1 trooper, 1 sith warrior , and 1 sith assasin (this one isn't working with any cc. ). so this isn't a cc issue. I'm updating the cc everyday if there's an update available.
Please post a log for me of what happens to your sniper? It may just be a rotation and sleep cycle thread not set correctly since 2.0 some things have changed. I am currently going to bot sniper from ground up and will be super tweaking it to make it work correctly. But logs I would love you since data data data!
I have a trooper and can honestly say that I never had a problem with trooper. Once I upgraded to Commando I got into a shit-load of trouble, but all that has been fixed since Joe's 2.0. Well, almost all of it, but certainly stable and working much better than it was.
Seems that the latest test joe 2.0 works better than previous versions. I went afk for 3 hours, and when I came back only 2 bots were stopped . this is great ) 1 was dead . the bot didn't click on resurrect to x the second one sith assasin was disconnected due to inactivity . In order to start the bot again I had to restart the computer. deleting the compiled assemblies didn't fix the error in the second related log. (happens quite often) I attached the logs for these 2 toons. I will post more when they will bug out. the logs were too big to upload here. https://www.dropbox.com/sh/5aykl43qsytub6y/Ort2EIIuHl . I will post more logs today
What class was first bot? So I can address in routine.(realize its sniper lolololololool) I am telling everyone that the bot is fine just the routine and the profiles need some love. Well after I get some meshes updated things will be like the promise land.
All my snipers have the marksmanship spec. The profiles are fine. I watched them closely . They will get stuck in a single spot .(same thing as in front of imperial agent trainer in the starting area; bugged mesh, the toon will get stuck, being unable to move (I have to use the teleport thing to unstuck it)). Starting now all of my bots, so I should be able to provide more logs soon .
Yea when I mean the routine I am not talking the rotation. I am talking about changes I made to the main code of this combat routine. I have changed quite a bit and the bot has been great ever since. Please go to that point use extra spammy and give me log of location so mesh can be fixed. Thanks!
I added more logs in the folder "closed all" https://www.dropbox.com/sh/5aykl43qsytub6y/Ort2EIIuHl . Same thing on all my snipers. They are still closing down every 1-3 hours. The swtor toons will get disconected due to inactivity. and Buddywing is spamming something, or just frozen.
Due to age and neglect of this bot soon after launch maybe everyone should turn the extra spammy logs on. A few times I try and start the bot it gives a freek error, I start the bot again and it looks fine but in game it acts screwy. I exit the game and bot and start them both back up and it works fine for awhile. Now if someone can come up with a fix to the client priority and directing cores by hand I would forever be grateful.
Added more logs from about 6 toons that closed down overnight. The logs are from 40 mb to 200 mb. Here are the spammy logs: https://www.dropbox.com/sh/5aykl43qsytub6y/ZbOeCrsThm/!spammy closed all
