Is there a change some1 makes a relogger for BW, I mean with a relogger the crashing problem woudnt be such a big problem like it is now.
i believe i made a small macro for it while it didn't work well. (no chance this will work for you) i could see if i could make something user friendly that's not shit.... (make a macro that targets the programs instead of careless clicking around.) or others could, its really not that hard a skilled person (not myself) could do this in 10-15 mins. i'll take a look at it ones i return from buying new Ram to my computer (they're causing crashes so not very easy to play a shitty optimized game like swtor) basically my computer crashes if i hit 3,95 of 4 gb ram ^_^....i needed some extra ram anyway.
playing around with it, cant seem to get around login as it seems its detecting my macro inputs in password field. it plainly refuses to move past "Initializing" i can do the exact same as what it's doing and its works fine. also found out i cant image search on the launcher. (how strange). i'll continue an other day.
cant make an 100% afk relogger, still interested? tried masking the script in an exe format but seems AHK is still giving off trackable traces as simply having it paused in the background causes you to be unable to log in...its bothersome. if anyone know some other script program that might work, ill give it a try but for now i'll give up ...
i'm guessing nobody cares about relogger anyway, i will abandon work in this subject. my conclusion however is that in order to macro the launcher you need to perfectly mask the macro. talked around and the only way i found out was if you use some completely unknown macro program or use VMware (have the game and bot inside VMware and have the macro OUTSIDE VMware)ultimately seperating the macro from detection. however who knows it might even detect VMware like Eve Online. good luck to those who attempts.
i think the way of solving it is to find a macro program that Swtor does not recognize as it does not black virtual keyboards and/or virtual mouse. it simply refuses to work if it detects an active macro process. i cant be bothered tho.
