It does work for me. It does happen, though, that the session was killed quicker than I could log on to buddyauth
Well it doesn't even show my keys or anything when I log in (used the same email I did previously as far as I am aware).
i wasent asking for it for free, i was asking if we had to buy it, because it was free the other day, and i didnt know i asked you, i thought i was asking the dev, and i didnt use the diablo one to know, so keep your opinion to yourself
An interesting byproduct of the stuck code. If Seethe is used for more then 2 seconds it goes into "I must be stuck mode" whenever it is finished self-healing. The end result is that after every Seethe the bot will run backwards and then to the left or right after every use. Looks a bit fishy.
Works for me. There might be small delay if multiple keys are purchased. Eventually new keys should show up under the Inactive/Unused Table.
Cheers for the suggestion! Deleted the two lines for pickupquest and subquest and the bot continued from the next quest!
First of all I am very excited that you decided to make a bot for SWTOR seeing as I have been a user of Honorbuddy and Gatherbuddy for years now and when I quit WoW Honorbuddy was capable of a great number of things if you sat down and spent some time with it. However. I am not sure if this is limited to me or if it is due to how the SWTOR client works or what not, but the game has alot of micro freezes whenever I run the bot and I have zero issues whenever I am not running it leading me to believe that its something to do with the way the bot interacts with the client. I remember having similar lag before they fixed it with casting channeled abilities while on a mount not sure if that could point you in any direction in terms of how fast it casts/moves or whatever I am not a programmer. Neither CPU or GPU is working at full capacity when the freezes happen so I doubt its a hardware limitation. Anyone else experiencing something similar or is it just me?
I get those micro freezes too, so it's not just you For me this bot is very much still a beta, but I paid for it and knowing the developers, I will give them the benefit of the doubt. It does though require constant supervision and user intevention, but that said - I am excited about future progres.
The "micro freezes" is the period before DirectX releases the frame and BuddyWing works its magic, it's normal, though I hardly experience any on my machine (i7 3770k / HD7970) so it might be a bit dependent on hardware. It's a bit more technical than that, but that's the gist of it pretty much.
i had that exact same problem with the beta, but with the release it's running smooth on my main comp, but it's having those micro freezing on my laptop tho...so i'm also thinking it's a hardware prob :/
Following up on the "Targeting X with 0% health" bug, it seems the issue may be tied into something with WingIt. Perhaps its trying to perform something as a mob is dying, not sure, but this error occurs right before the issue starts:
Managed to get it to occur two times in a row, theres a few other errors in there too. Here's the log. View attachment 2012-06-08.txt
I get microfreezes too, very rarely, only when I start launching other applications while botting in the background. Seems it's a CPU (non)issue.
dont realy care about the micro freezes its barley noticeable on my laptop bot work prety good for the most part cant wait for the 10+ profiles to be officaly realsed corasant leveling kind of sucks at the moment nocked off a few dailys on my main just wish their was a profile for the correlia security cheast run need the creds for my alts too busy to do it my self right now
New problem just surfaced today (after I'd ran the bot for a couple of hours today) when starting.... I've used my usual routine of: - Checking "run as admin" on SWTOR - Starting SWTOR - Logging into the game - Logging on to the character - Waiting for character to fully load - Checking "Run as admin" on BW - Starting BW - Logging on to BW I've also tried: - Rebooting - Reinstalling BW from scratch - Using the test version Hawker sent me yesterday The end result in all cases is: