Newly started SWTOR with newly started BW and the old problem is back I've tried it with SWTOR started through Inner Space and with SWTOR started normally, both times it's unable to attach....
Are you guys going to add a stats type thing on BuddyWing? so can watch amount of deaths, xp per hour, so on.
This is still a perpetuating problem. Running Kick's leveling profiles isn't much of a problem but as soon as I go to Ilum the bot won't do anything. I'm trying to rewrite those daily profiles (since the current quality isn't even meh) but the bot won't do anything on Ilum. *edit* Scratch that. Since a half an hour ago, I'm getting the attached error. I get this on all my systems, whether through IS or started normally.
same here stands doing nothing and when i pull manually it just runs back and forth ontop of a mob regardless of class
Any chance at an update to WingIt and/or BW today so we can get back to leveling our characters (or at least *I* can level my characters... I'm not proud I'll admit it... =P )?
Mine is workin fine besides the errors, have to force close and double tap to make sure dead errors. Restart and go on. at least with the errors make to where little picture of lightsaber, and turns it into a epic battle. Me: yes I will shut you off! bot: no I will live on, come to the dark side!
What class are you using? Any of the ones I try to use just spam errors during combat and effectively just sit there (for Agent, Sorc, Marauder). I'd love to be able to play but I can't figure out any way around it. EDIT: I'm not really upset since the Buddy team is getting sh*t on over in the DB forums by all those new users.
started up new test to see if could replicate. 2 agents lvl 1 fresh made up running [E - Dark] 1-10 Agent and Bounty Hunter - Hutta [Kick] Watching them I noticed 1 was doing good. While other would take long time to decide where to go. Eventually got stuck. When clicked Stop button on BuddyWing it didnt fully stop. I was able to get toon unstuck. Was not able to get BuddyWing started due to button still said Stop in grey. Was able to close BuddyWing after a few Unhandled Exception: Object reference not set to a reference. Closed game. Re-started game and BuddyWing. Got error was not able to find a client. Attached log from when couldnt find client. Log for 6 lvls is 82meg not able to upload. Looking through seen the ussual nav server cant get path. Problem with using object. Code: [21:20:12.455 V] [UseObject] Moving to interact with: Stolen Tribute [21:20:14.300 D] Could not use plcProp_DefaultAction, attempting basic Interact() [21:20:15.621 V] Blacklisting 1BB66404BA for 00:00:30 [21:20:15.816 D] Generating path to Stolen Tribute <-52.00552, 1.493211, 40.5127> [21:20:15.852 D] Raycast path generated. [21:20:15.852 D] Generated path to <-52.00552, 1.493211, 40.5127> (Stolen Tribute) with 1 hops. [21:20:16.278 D] Navigation reached current destination. Within 0.008434008 [21:20:16.444 D] Generating path to Stolen Tribute <-52.00552, 1.493211, 40.5127> [21:20:16.471 D] Raycast path generated. [21:20:16.471 D] Generated path to <-52.00552, 1.493211, 40.5127> (Stolen Tribute) with 1 hops. [21:20:16.587 D] Navigation reached current destination. Within 0.008434008 [21:20:16.818 D] Generating path to Stolen Tribute <-52.00552, 1.493211, 40.5127> Spammed the generated path. Spammed dictionary from [21:25:54.315 D] to [21:36:21.498 D] Object reference not set to an instance of an object. Code: [21:25:54.636 D] [HLL] Dictionary contains 0 key already. Value: 0 [21:25:54.636 D] [HLL] Dictionary contains 0 key already. Value: 9.147676E-41 [21:25:54.636 D] [HLL] Dictionary contains 0 key already. Value: 0 [21:25:54.636 D] [HLL] Dictionary contains 16711680 key already. Value: 0 [21:25:54.636 D] [HLL] Dictionary contains 0 key already. Value: 0 [21:25:54.636 D] [HLL] Dictionary contains 0 key already. Value: -3.944305E-31 [21:25:54.636 D] [HLL] Dictionary contains 0 key already. Value: 1.681558E-44 [21:25:54.636 D] [HLL] Dictionary contains 0 key already. Value: 0 [21:25:54.636 D] [HLL] Dictionary contains 0 key already. Value: NaN [21:25:54.636 D] [HLL] Dictionary contains 0 key already. Value: 0 [21:25:54.636 D] [HLL] Dictionary contains 0 key already. Value: NaN [21:25:54.636 D] [HLL] Dictionary contains 0 key already. Value: 0 [21:25:54.636 D] [HLL] Dictionary contains 0 key already. Value: -1.511157E+23 [21:25:54.637 D] [HLL] Dictionary contains 0 key already. Value: 0 [21:25:54.637 D] [HLL] Dictionary contains 0 key already. Value: -1582.25 This is clipit from when hit stop button. To where had to force close BuddyWing. Code: [22:20:54.022 D] Start/Stop Button Clicked! [22:20:54.022 D] BotMain.Stop() called [22:20:54.022 N] Stopping the bot. [22:20:54.122 D] Sleeping while waiting on execution state to be available for BotMain.Stop() [22:20:56.122 D] We slept way too long waiting for the bot thread to give control back. Aborting thread. Client may crash! [22:20:56.132 V] [Poi.Clear] Reason: Bot Stopped [22:20:56.132 D] Resetting force alignment settings. [22:20:56.132 D] QuestOrderManager.OnBotStop(). Resetting caches. [22:20:56.132 D] Resetting current behavior. [22:20:56.132 D] QuestOrderManager.OnBotStop(). Resetting caches. [22:20:56.132 D] Resetting current behavior. [22:20:56.132 D] QuestOrderManager.OnBotStop(). Resetting caches. [22:20:56.132 D] Resetting current behavior. [22:20:56.246 D] Exception while pulsing plugin Use Lockboxes: System.Threading.ThreadAbortException: Thread was being aborted. at System.Threading.WaitHandle.WaitOneNative(SafeHandle waitableSafeHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext) at System.Threading.WaitHandle.InternalWaitOne(SafeHandle waitableSafeHandle, Int64 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext) at System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean exitContext) at GreyMagic.Executor.Execute() at ...ctor() at Buddy.Swtor.Objects.TorItem.get_Name() at Buddywing.Plugins.OpenLockboxesPlugin.OnPulse() in c:\swtor bot\BuddyWing 1\Plugins\OpenLockboxes\OpenLockboxesPlugin.cs:line 54 at Buddy.Common.Plugins.PluginManager.PulsePlugin(IPlugin plugin) [22:20:56.256 D] Bot Thread Aborted Thread was being aborted. [22:22:32.154 N] SW:TOR Process exited. Uh oh... Had to shut down both Clients, reboot to restart.
After a clean install of Windows, SWTOR and BW I'm still getting this error. The only things I can think of now is that it's either something in my network (it isn't the simplest of home network configurations but it would still be weird that it would b0rk on that) or something in BW isn't quite right yet.
Well there certainly is something "not right" going on... Since other people are able to bot... And I'm able to bot until I hit the 10-11 range and switch over to an advanced CC and it then all implodes. I've been trying to replicate your issue, Croga, and can't... So there is a possibility that our setups may be causing the issue... Still doesn't change the fact that it sucks that we're unable to bot right now. =/
I have an army of level 10's cause of this bot, im gonna dominate my server muhahahahaaha!!!!!!!!!!!!!!!!!!
That is quite epic... I'm tempted to do the same but I was hoping to open up a Legacy so I could work on getting some Empire races over on the Alliance side before playing them.
I'm currently not in my own country and wont be for the next 2 weeks so I rlly dunno whats going on. The only thing that u could try would be to disable the plugins. And please give the devs a bit time - its not as easy as it sound to find and fix an error
Plugins have been disabled as far as I can tell. I noted over in the WingIt thread that you're gone for a few weeks, so I get that. I also get that they just released DB and are furiously working on staying ahead of that tidal wave since I'm sure the number of purchases on DB far outstrips the number on BW. It just sucks that everything was working, then you left, then they put out a version, then DB came out... And now we're sorta SOL until things sort themselves out... It's the perfect storm of what you don't want to have to a product when it is working. I'm still going to do what I can to try and help those that are able to get things to work... But until then there's not much we can do but twiddle our thumbs when we're loosing days on our product that is only sold in 1 year increments... If they had a lifetime option like HB or DB then I would care even less as I know that the lost days wouldn't mean much. So it is a bad situation all the way around... Not much I can do about it. So I think I'm going to assault some people with a two handed purple dildo in Saints Row The Third.
So it is a bad situation all the way around... Not much I can do about it. So I think I'm going to assault some people with a two handed purple dildo in Saints Row The Third.[/QUOTE] I just cant wait to have a fully functioning bot and profiles..this bot has the potential to be amazing. I have 4 other guildmates waiting for me to give the green flag to buy it but i can't approve it yet as their GM because there will be chaos.....Devs please make buddwing a priority someday!!!
i can't get buddywing to work, i have .net framework installed, visual c++ installed on a laptop running win7x64 here is the log [20:18:43.166 N] Starting Buddy Wing v1.0.841.253 [20:18:43.698 D] The type initializer for 'Buddy.CommonBot.BotMain' threw an exception. [20:18:43.701 D] at Buddy.CommonBot.BotMain.get_StatusText() at Buddywing.MainWindow.() at System.Threading.ThreadHelper.ThreadStart_Context(Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() help please! i can't even enter my auth code it crashes! should i expect no help until someone is back in the country?
The person out of the country is the one working on the combat classes for the bot, not any of the main developers. So you should get some sort of a response from someone on this. I would recommend that you attach your full log file and not just the log snippit just so they can see the whole thing.