Anyones bot not moving?

normal

 

now i set diagnostic and here the log

 

That's weird. Can you create a new thread in the support section for this?

Please move you're character manually so you're in los of the quest turn in.

Then start the bot, in diagnostic mode, close the dialog and let it run for at least five minutes?

Then upload the log. Thanks ^_^

 

I think my problem has no solution

 

computers take trouble shooting...haven't exactly done much of that...you haven't even posted on the support thread so the devs can see it...

 

thanks for ur time kaihaider

the problom happen with trooper , i dont know if there other class's will get same

but now i make new trooper and done 1-10 quest's , he travel to fleet and ask me to choose spec , i choose commando , then he run to airport and travel to Coruscant , when he be there the bot ask me to restart buddywing and choose Coruscant quest

i do what he asked me and when i press start he wont move

i have other class lvl 10 and bot ask me to choose spec and i choose gunslinger , and he do what trooper do , run to airport then travel to Coruscant ,also bot ask me to restart , i do restart and choose Coruscant quest , he work fine now

the problom in trooper not my PC or Bot

before i have warrior and i reach lvl 50 by quests and grind

only trooper wont move

 

I ran a trooper yesterday and I didn't notice any problems but I was being a little flaky with the start/stops. One common problem is when you're in an area that the profile isn't expecting, so it doesn't have the conditions set up to bring you to the right part of the map. Please do what I asked you on my other post...

The log you posted ended without any errors that describe you're problem. I'm not a dev, so if you want to work through this problem with me, I'm going to need logs at least a couple more times with you doing some trouble shooting suggestions...

If the bot's having trouble reaching an objective or clicking an object, then I usually complete the next step of that profile or bring it close to the objective. Although it may be best if we follow kick's bug submitting thread so they have the data to fix the errors eventually.