[Beta] UntzBot (Space Missions Bot, recorder+player)

[thephilz]

honestly, i have no idea right now

however i can confirm that lower level missions are still pretty decent :

SUN 15/04/2012 04:23:23 - Mission Imperial20NezPeron started, Mode:Event Delay:1900
SUN 15/04/2012 04:23:44 -- Event Sync started 17426 ms after galaxy map.
SUN 15/04/2012 04:27:41 -- WIN -> 159/0

SUN 15/04/2012 03:38:54 - Mission Imperial20NezPeron started, Mode:Event Delay:1900
SUN 15/04/2012 03:39:16 -- Event Sync started 18065 ms after galaxy map.
SUN 15/04/2012 03:40:19 -- BAIL - Death Screen Found - Bails:21

from this we can see a 159/180 success rate of 88%, which can either be attributed to 'randomness' or just general lag wrecking sync, its still unknown

(and i had an earlier 80+/0 on escort10)

it might either be the bot being funky, or maybe higher missions having some 'randomness' added, but ill find out very shortly
i just botted my whole way through from 27 to 28 in the span of 10 hours just then, ill leave it overnight with level 28 going and see how it is

only once we can find the 'real reason' for failure (the i highly doubt the bot routine that has worked for how long is the reason, its most likely a ninja patch change to the missions) then i can post a definite fix

[necrodeath86]

hey. just 1 question. sorry for not reading all the pages. maybe the answer is there but there are too much. i'm trying to record my empire lvl 40 mission minefield but when i start the ship place herself on the bottom left of the screen and dont allow me to mover her. she moves after the time (30000 ms i assume) are gone but immidiately the mission is failed. any suggestion in what i'm failing at?

UPDATE: i've redone the image sync on event. now it trigger the start but after finishing the recording and i put on play the bot is totally out of sync -_-
Updat: sms that oth low lls mission a all out of syn

[Nazomi]

Can't get mine working. The bot starts, it hovers over the chair, then goes onto it's next position (just sort of bottom right of the chair?) it finds the chair, hovers over it and makes the tooltip show up, it just doesn't seem to be making the selection. Is there a fix for this?

[thephilz]

Can't get mine working. The bot starts, it hovers over the chair, then goes onto it's next position (just sort of bottom right of the chair?) it finds the chair, hovers over it and makes the tooltip show up, it just doesn't seem to be making the selection. Is there a fix for this?

make sure to run in admin mode - if you do not, it is not allowed to do mouse clicks (hence the 'hovering and not doing anything')

//

okay. so ive done a few tests and i believe there is no randomness inside the actual mission, the 'randomness' lies IN THE MISSION LOADING TIME

Is it randomness or just lag I dont know. But Aeten Sometimes starts :30 seconds into the mission and sometimes not.

compare: 1.1 vs 1.2 - you can see the ship appears FAR FURTHER IN in the 1.2 version, because it loaded a lot slower
in fact, it loads so slow, that the planet has not even loaded yet, but the ship is already that far out. thats how big the difference is in loading times.
its not really randomness, its just that the missions take a LOT LONGER TO LOAD THAN THEY USED TO, or so i have found. as far as i can tell, this has been true for level 12-28 so far, and probably all the way to 50.

for example, in the level 28 escort2 missions, the 'green moon' used to appear at the top edge of the screen for me, but now it appears maybe a quarter way down
what this means is that event sync will now fail, because it used to pick up the moon right after it passed the top edge
after making a new event sync image to around 5 seconds after, then re-recording, the mission worked perfect.

SUN 15/04/2012 11:46:53 - Mission Imperial28Taspan started, Mode:Event Delay:1800
SUN 15/04/2012 11:47:12 -- Event Sync started 15195 ms after galaxy map.
SUN 15/04/2012 11:50:40 -- WIN -> 89/1
SUN 15/04/2012 11:51:06 - Mission Imperial28Taspan started, Mode:Event Delay:1800
SUN 15/04/2012 11:51:25 -- Event Sync started 15070 ms after galaxy map.
SUN 15/04/2012 11:54:12 -- BAIL - Death Screen Found - Bails:3

at the moment im going to assume the same is true for ALL missions

i am now in the process of making new event sync images etc for all the 'default' missions, and attempting to add the 'multiple mission' thing, but nwe event syncs takes priority (no point adding multiple missions if no missions work in the first place)

please note that higher end computers will suffer a lot less than lower end computers. my brothers far superior computer noticed only a small change in loading time, but this piece of junk i use suffered maybe 5 seconds+ loading time changes, depending on the mission

[MasterM1nd]

question for you philz, I used time sync in the last version 4.x of Untz, and just got the 5.0 extracted. Do I have to re-record all of my TIME sync profiles that I had made in 4.x? Or can I get those from somewhere and copy them into the new version? Please let me know, as I had perfectly setup time sync profiles that I recorded myself for all mission levels for easy 1-50.


Thanks for all your work on this either way, cheers.

[TheDank]

question for you philz, I used time sync in the last version 4.x of Untz, and just got the 5.0 extracted. Do I have to re-record all of my TIME sync profiles that I had made in 4.x? Or can I get those from somewhere and copy them into the new version? Please let me know, as I had perfectly setup time sync profiles that I recorded myself for all mission levels for easy 1-50.


Thanks for all your work on this either way, cheers.

copy all of the folders from your 4.x to the 5.0

just overwrite the files. 5.0 reads them the same as 4.x

[bambam922]

Something weird is happening to me. I come home from work and I am finding that my client gets closed for no reason.
This happening to you guys as well?

[thephilz]

Something weird is happening to me. I come home from work and I am finding that my client gets closed for no reason.
This happening to you guys as well?

honestly i have no clue why that really happens, but im still assuming its to do with file writing conflicts, but considering i had the bot running for around 90 hours NONSTOP then im assuming its on a computer-to-computer basis

can you open log.txt and post when the bot was started, and maybe the last 5 or so results (wins/loses/bails), as it seems that closing has to do with large amount of fails/deaths

[bambam922]

honestly i have no clue why that really happens, but im still assuming its to do with file writing conflicts, but considering i had the bot running for around 90 hours NONSTOP then im assuming its on a computer-to-computer basis

can you open log.txt and post when the bot was started, and maybe the last 5 or so results (wins/loses/bails), as it seems that closing has to do with large amount of fails/deaths

Interesting that you say it has to do with fails.

SAT 14/04/2012 18:50:32 - Mission Imperial34Skaross started, Mode:Timer Delay:2000
SAT 14/04/2012 18:50:52 -- Timer Sync started 16063 ms after galaxy map.
SAT 14/04/2012 18:55:58 -- LOSS -> 15/1
SAT 14/04/2012 18:56:21 - Mission Imperial34Skaross started, Mode:Timer Delay:2000
SAT 14/04/2012 18:56:40 -- Timer Sync started 15062 ms after galaxy map.
SAT 14/04/2012 19:01:50 -- WIN  -> 16/1
SAT 14/04/2012 19:02:13 - Mission Imperial34Skaross started, Mode:Timer Delay:2000
SAT 14/04/2012 19:02:32 -- Timer Sync started 15297 ms after galaxy map.
SAT 14/04/2012 19:07:42 -- WIN  -> 17/1
SAT 14/04/2012 19:08:05 - Mission Imperial34Skaross started, Mode:Timer Delay:2000
SAT 14/04/2012 19:08:24 -- Timer Sync started 15079 ms after galaxy map.
SAT 14/04/2012 19:13:34 -- WIN  -> 18/1
SAT 14/04/2012 19:13:57 - Mission Imperial34Skaross started, Mode:Timer Delay:2000
SAT 14/04/2012 19:14:17 -- Timer Sync started 15156 ms after galaxy map.
SAT 14/04/2012 19:19:26 -- WIN  -> 19/1
SAT 14/04/2012 19:19:50 - Mission Imperial34Skaross started, Mode:Timer Delay:2000
SAT 14/04/2012 19:20:09 -- Timer Sync started 15359 ms after galaxy map.
SAT 14/04/2012 19:25:19 -- WIN  -> 20/1
SAT 14/04/2012 19:25:42 - Mission Imperial34Skaross started, Mode:Timer Delay:2000
SAT 14/04/2012 19:26:01 -- Timer Sync started 15156 ms after galaxy map.

It stopped here.

This is the start

SAT 14/04/2012 17:21:55 ----- Bot Session Started
SAT 14/04/2012 17:22:31 - Mission Imperial34Skaross started, Mode:Timer Delay:2000
SAT 14/04/2012 17:22:50 -- Timer Sync started 15219 ms after galaxy map.

1 loss the entire time it was running

Before the update I was able to keep it running forever.

[copyleft]

I'm having the same issue also. It's happening on 2 different computers, a laptop and a desktop.

I don't think it has anything to do with fails, since my sync images and recordings are near perfect. Under 1% loss. Here is the log from my laptop, swtor crashed at 2:30 AM and I started it again at 8AM.

SUN 15/04/2012 01:58:39 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 01:58:51 -- Event Sync started 8315 ms after galaxy map.
SUN 15/04/2012 02:04:07 -- WIN -> 50/0
SUN 15/04/2012 02:04:30 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 02:04:43 -- Event Sync started 8299 ms after galaxy map.
SUN 15/04/2012 02:09:59 -- WIN -> 51/0
SUN 15/04/2012 02:10:22 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 02:10:35 -- Event Sync started 8456 ms after galaxy map.
SUN 15/04/2012 02:15:51 -- WIN -> 52/0
SUN 15/04/2012 02:16:14 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 02:16:27 -- Event Sync started 8377 ms after galaxy map.
SUN 15/04/2012 02:21:43 -- WIN -> 53/0
SUN 15/04/2012 02:22:06 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 02:22:18 -- Event Sync started 8331 ms after galaxy map.
SUN 15/04/2012 02:27:35 -- WIN -> 54/0
SUN 15/04/2012 02:27:58 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 02:28:10 -- Event Sync started 8361 ms after galaxy map.
SUN 15/04/2012 02:33:27 -- WIN -> 55/0
SUN 15/04/2012 02:33:50 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 02:34:02 -- Event Sync started 8502 ms after galaxy map.
SUN 15/04/2012 08:00:34
SUN 15/04/2012 08:00:34 ----- Bot Session Started
SUN 15/04/2012 08:01:01 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 08:01:13 -- Event Sync started 8174 ms after galaxy map.
SUN 15/04/2012 08:06:29 -- WIN -> 1/0
SUN 15/04/2012 08:06:52 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 08:07:04 -- Event Sync started 8174 ms after galaxy map.
SUN 15/04/2012 08:12:21 -- WIN -> 2/0
SUN 15/04/2012 08:12:44 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 08:12:56 -- Event Sync started 8237 ms after galaxy map.
SUN 15/04/2012 08:18:12 -- WIN -> 3/0

[azza]

honestly i have no clue why that really happens, but im still assuming its to do with file writing conflicts, but considering i had the bot running for around 90 hours NONSTOP then im assuming its on a computer-to-computer basis

can you open log.txt and post when the bot was started, and maybe the last 5 or so results (wins/loses/bails), as it seems that closing has to do with large amount of fails/deaths

heres mine it did 100 this morning before it failed.

SUN 15/04/2012 02:26:50 ----- Bot Session Started
SUN 15/04/2012 02:27:56 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 02:28:12 -- Event Sync started 12234 ms after galaxy map.
SUN 15/04/2012 02:33:27 -- WIN  -> 1/0
SUN 15/04/2012 02:33:50 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 02:34:06 -- Event Sync started 12125 ms after galaxy map.
SUN 15/04/2012 02:39:21 -- WIN  -> 2/0
SUN 15/04/2012 02:39:44 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 02:40:00 -- Event Sync started 12157 ms after galaxy map.
SUN 15/04/2012 02:45:15 -- WIN  -> 3/0
SUN 15/04/2012 02:45:38 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 02:45:54 -- Event Sync started 12235 ms after galaxy map.
SUN 15/04/2012 02:51:09 -- WIN  -> 4/0
SUN 15/04/2012 02:51:32 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 02:51:48 -- Event Sync started 12219 ms after galaxy map.
SUN 15/04/2012 02:57:03 -- WIN  -> 5/0
SUN 15/04/2012 02:57:26 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 02:57:42 -- Event Sync started 12344 ms after galaxy map.
SUN 15/04/2012 03:02:57 -- WIN  -> 6/0
SUN 15/04/2012 03:03:20 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 03:03:36 -- Event Sync started 12157 ms after galaxy map.
SUN 15/04/2012 03:08:51 -- WIN  -> 7/0
SUN 15/04/2012 03:09:14 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 03:09:30 -- Event Sync started 12156 ms after galaxy map.
SUN 15/04/2012 03:14:45 -- WIN  -> 8/0
SUN 15/04/2012 03:15:08 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 03:15:24 -- Event Sync started 12188 ms after galaxy map.
SUN 15/04/2012 03:20:39 -- WIN  -> 9/0
SUN 15/04/2012 03:21:02 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 03:21:18 -- Event Sync started 12219 ms after galaxy map.
SUN 15/04/2012 03:26:33 -- WIN  -> 10/0
SUN 15/04/2012 03:26:56 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 03:27:12 -- Event Sync started 12078 ms after galaxy map.
SUN 15/04/2012 03:32:27 -- WIN  -> 11/0
SUN 15/04/2012 03:32:50 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 03:33:06 -- Event Sync started 12156 ms after galaxy map.
SUN 15/04/2012 03:38:21 -- WIN  -> 12/0
SUN 15/04/2012 03:38:44 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 03:39:00 -- Event Sync started 12250 ms after galaxy map.
SUN 15/04/2012 03:44:15 -- WIN  -> 13/0
SUN 15/04/2012 03:44:38 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 03:44:54 -- Event Sync started 12234 ms after galaxy map.
SUN 15/04/2012 03:50:09 -- WIN  -> 14/0
SUN 15/04/2012 03:50:32 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 03:50:49 -- Event Sync started 12328 ms after galaxy map.
SUN 15/04/2012 03:56:03 -- WIN  -> 15/0
SUN 15/04/2012 03:56:27 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 03:56:43 -- Event Sync started 12171 ms after galaxy map.
SUN 15/04/2012 04:01:57 -- WIN  -> 16/0
SUN 15/04/2012 04:02:20 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 04:02:37 -- Event Sync started 12281 ms after galaxy map.
SUN 15/04/2012 04:07:51 -- WIN  -> 17/0
SUN 15/04/2012 04:08:15 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 04:08:31 -- Event Sync started 12218 ms after galaxy map.
SUN 15/04/2012 04:13:45 -- WIN  -> 18/0
SUN 15/04/2012 04:14:09 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 04:14:25 -- Event Sync started 12125 ms after galaxy map.
SUN 15/04/2012 04:19:39 -- WIN  -> 19/0
SUN 15/04/2012 04:20:03 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 04:20:19 -- Event Sync started 12156 ms after galaxy map.
SUN 15/04/2012 04:25:33 -- WIN  -> 20/0
SUN 15/04/2012 04:25:57 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 04:26:13 -- Event Sync started 12187 ms after galaxy map.
SUN 15/04/2012 04:31:27 -- WIN  -> 21/0
SUN 15/04/2012 04:31:51 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 04:32:07 -- Event Sync started 12438 ms after galaxy map.
SUN 15/04/2012 04:37:22 -- WIN  -> 22/0
SUN 15/04/2012 04:37:45 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 04:38:01 -- Event Sync started 12157 ms after galaxy map.
SUN 15/04/2012 04:43:16 -- WIN  -> 23/0
SUN 15/04/2012 04:43:39 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 04:43:55 -- Event Sync started 12156 ms after galaxy map.
SUN 15/04/2012 04:49:10 -- WIN  -> 24/0
SUN 15/04/2012 04:49:33 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 04:49:49 -- Event Sync started 12312 ms after galaxy map.
SUN 15/04/2012 04:55:04 -- WIN  -> 25/0
SUN 15/04/2012 04:55:27 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 04:55:43 -- Event Sync started 12313 ms after galaxy map.
SUN 15/04/2012 05:00:58 -- WIN  -> 26/0
SUN 15/04/2012 05:01:21 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 05:01:37 -- Event Sync started 12281 ms after galaxy map.
SUN 15/04/2012 05:06:52 -- WIN  -> 27/0
SUN 15/04/2012 05:07:15 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 05:07:32 -- Event Sync started 12235 ms after galaxy map.
SUN 15/04/2012 05:12:46 -- WIN  -> 28/0
SUN 15/04/2012 05:13:09 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 05:13:25 -- Event Sync started 12078 ms after galaxy map.
SUN 15/04/2012 05:18:40 -- WIN  -> 29/0
SUN 15/04/2012 05:19:03 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 05:19:20 -- Event Sync started 12265 ms after galaxy map.
SUN 15/04/2012 05:24:34 -- WIN  -> 30/0
SUN 15/04/2012 05:24:57 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 05:25:14 -- Event Sync started 12296 ms after galaxy map.
SUN 15/04/2012 05:30:28 -- WIN  -> 31/0
SUN 15/04/2012 05:30:52 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 05:31:08 -- Event Sync started 12203 ms after galaxy map.
SUN 15/04/2012 05:36:22 -- WIN  -> 32/0
SUN 15/04/2012 05:36:46 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 05:37:02 -- Event Sync started 12203 ms after galaxy map.
SUN 15/04/2012 05:42:16 -- WIN  -> 33/0
SUN 15/04/2012 05:42:40 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 05:42:56 -- Event Sync started 12235 ms after galaxy map.
SUN 15/04/2012 05:47:34 -- BAIL - Death Screen Found - Bails:1
SUN 15/04/2012 05:48:02 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 05:48:18 -- Event Sync started 12203 ms after galaxy map.
SUN 15/04/2012 05:53:32 -- WIN  -> 34/0
SUN 15/04/2012 05:53:56 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 05:54:12 -- Event Sync started 12312 ms after galaxy map.
SUN 15/04/2012 05:59:27 -- WIN  -> 35/0
SUN 15/04/2012 05:59:50 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 06:00:06 -- Event Sync started 12297 ms after galaxy map.
SUN 15/04/2012 06:05:21 -- WIN  -> 36/0
SUN 15/04/2012 06:05:44 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 06:06:00 -- Event Sync started 12328 ms after galaxy map.
SUN 15/04/2012 06:11:15 -- WIN  -> 37/0
SUN 15/04/2012 06:11:38 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 06:11:54 -- Event Sync started 12235 ms after galaxy map.
SUN 15/04/2012 06:17:09 -- WIN  -> 38/0
SUN 15/04/2012 06:17:32 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 06:17:49 -- Event Sync started 12313 ms after galaxy map.
SUN 15/04/2012 06:23:03 -- WIN  -> 39/0
SUN 15/04/2012 06:23:26 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 06:23:43 -- Event Sync started 12203 ms after galaxy map.
SUN 15/04/2012 06:28:57 -- WIN  -> 40/0
SUN 15/04/2012 06:29:20 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 06:29:37 -- Event Sync started 12203 ms after galaxy map.
SUN 15/04/2012 06:34:51 -- WIN  -> 41/0
SUN 15/04/2012 06:35:14 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 06:35:31 -- Event Sync started 12219 ms after galaxy map.
SUN 15/04/2012 06:40:45 -- WIN  -> 42/0
SUN 15/04/2012 06:41:09 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 06:41:25 -- Event Sync started 12172 ms after galaxy map.
SUN 15/04/2012 06:46:39 -- WIN  -> 43/0
SUN 15/04/2012 06:47:03 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 06:47:19 -- Event Sync started 12203 ms after galaxy map.
SUN 15/04/2012 06:52:33 -- WIN  -> 44/0
SUN 15/04/2012 06:52:57 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 06:53:13 -- Event Sync started 12125 ms after galaxy map.
SUN 15/04/2012 06:58:27 -- WIN  -> 45/0
SUN 15/04/2012 06:58:51 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 06:59:07 -- Event Sync started 12297 ms after galaxy map.
SUN 15/04/2012 07:04:21 -- WIN  -> 46/0
SUN 15/04/2012 07:04:45 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 07:05:01 -- Event Sync started 12234 ms after galaxy map.
SUN 15/04/2012 07:10:16 -- WIN  -> 47/0
SUN 15/04/2012 07:10:39 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 07:10:55 -- Event Sync started 12344 ms after galaxy map.
SUN 15/04/2012 07:16:10 -- WIN  -> 48/0
SUN 15/04/2012 07:16:33 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 07:16:49 -- Event Sync started 12266 ms after galaxy map.
SUN 15/04/2012 07:22:04 -- WIN  -> 49/0
SUN 15/04/2012 07:22:27 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 07:22:43 -- Event Sync started 12297 ms after galaxy map.
SUN 15/04/2012 07:27:58 -- WIN  -> 50/0
SUN 15/04/2012 07:28:21 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 07:28:37 -- Event Sync started 12313 ms after galaxy map.
SUN 15/04/2012 07:33:52 -- WIN  -> 51/0
SUN 15/04/2012 07:34:15 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 07:34:32 -- Event Sync started 12250 ms after galaxy map.
SUN 15/04/2012 07:39:46 -- WIN  -> 52/0
SUN 15/04/2012 07:40:09 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 07:40:26 -- Event Sync started 12297 ms after galaxy map.
SUN 15/04/2012 07:45:40 -- WIN  -> 53/0
SUN 15/04/2012 07:46:03 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 07:46:20 -- Event Sync started 12360 ms after galaxy map.
SUN 15/04/2012 07:51:34 -- WIN  -> 54/0
SUN 15/04/2012 07:51:58 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 07:52:14 -- Event Sync started 12234 ms after galaxy map.
SUN 15/04/2012 07:57:28 -- WIN  -> 55/0
SUN 15/04/2012 07:57:52 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 07:58:08 -- Event Sync started 12359 ms after galaxy map.
SUN 15/04/2012 08:03:23 -- WIN  -> 56/0
SUN 15/04/2012 08:03:46 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 08:04:02 -- Event Sync started 12297 ms after galaxy map.
SUN 15/04/2012 08:09:17 -- WIN  -> 57/0
SUN 15/04/2012 08:09:40 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 08:09:56 -- Event Sync started 12219 ms after galaxy map.
SUN 15/04/2012 08:15:11 -- WIN  -> 58/0
SUN 15/04/2012 08:15:34 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 08:15:50 -- Event Sync started 12093 ms after galaxy map.
SUN 15/04/2012 08:21:05 -- WIN  -> 59/0
SUN 15/04/2012 08:21:28 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 08:21:44 -- Event Sync started 12266 ms after galaxy map.
SUN 15/04/2012 08:26:59 -- WIN  -> 60/0
SUN 15/04/2012 08:27:22 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 08:27:38 -- Event Sync started 12187 ms after galaxy map.
SUN 15/04/2012 08:32:53 -- WIN  -> 61/0
SUN 15/04/2012 08:33:16 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 08:33:33 -- Event Sync started 12282 ms after galaxy map.
SUN 15/04/2012 08:38:47 -- WIN  -> 62/0
SUN 15/04/2012 08:39:11 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 08:39:27 -- Event Sync started 12187 ms after galaxy map.
SUN 15/04/2012 08:44:41 -- WIN  -> 63/0
SUN 15/04/2012 08:45:05 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 08:45:21 -- Event Sync started 12313 ms after galaxy map.
SUN 15/04/2012 08:50:35 -- WIN  -> 64/0
SUN 15/04/2012 08:50:59 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 08:51:15 -- Event Sync started 12313 ms after galaxy map.
SUN 15/04/2012 08:56:30 -- WIN  -> 65/0
SUN 15/04/2012 08:56:53 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 08:57:09 -- Event Sync started 12281 ms after galaxy map.
SUN 15/04/2012 09:02:24 -- WIN  -> 66/0
SUN 15/04/2012 09:02:47 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 09:03:03 -- Event Sync started 12203 ms after galaxy map.
SUN 15/04/2012 09:08:18 -- WIN  -> 67/0
SUN 15/04/2012 09:08:41 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 09:08:57 -- Event Sync started 12296 ms after galaxy map.
SUN 15/04/2012 09:14:12 -- WIN  -> 68/0
SUN 15/04/2012 09:14:35 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 09:14:51 -- Event Sync started 12312 ms after galaxy map.
SUN 15/04/2012 09:20:06 -- WIN  -> 69/0
SUN 15/04/2012 09:20:29 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 09:20:46 -- Event Sync started 12313 ms after galaxy map.
SUN 15/04/2012 09:26:00 -- WIN  -> 70/0
SUN 15/04/2012 09:26:23 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 09:26:40 -- Event Sync started 12203 ms after galaxy map.
SUN 15/04/2012 09:31:54 -- WIN  -> 71/0
SUN 15/04/2012 09:32:17 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 09:32:34 -- Event Sync started 12328 ms after galaxy map.
SUN 15/04/2012 09:37:48 -- WIN  -> 72/0
SUN 15/04/2012 09:38:12 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 09:38:28 -- Event Sync started 12375 ms after galaxy map.
SUN 15/04/2012 09:43:43 -- WIN  -> 73/0
SUN 15/04/2012 09:44:06 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 09:44:22 -- Event Sync started 12250 ms after galaxy map.
SUN 15/04/2012 09:49:37 -- WIN  -> 74/0
SUN 15/04/2012 09:50:00 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 09:50:42 -- WARNING - Event Sync reached 30000 - Bailing
SUN 15/04/2012 09:51:13 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 09:51:30 -- Event Sync started 12485 ms after galaxy map.
SUN 15/04/2012 09:56:44 -- WIN  -> 75/0
SUN 15/04/2012 09:57:07 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 09:57:24 -- Event Sync started 12187 ms after galaxy map.
SUN 15/04/2012 10:02:38 -- WIN  -> 76/0
SUN 15/04/2012 10:03:54 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 10:04:10 -- Event Sync started 12250 ms after galaxy map.
SUN 15/04/2012 10:09:25 -- WIN  -> 77/0
SUN 15/04/2012 10:09:48 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 10:10:05 -- Event Sync started 12344 ms after galaxy map.
SUN 15/04/2012 10:15:19 -- WIN  -> 78/0
SUN 15/04/2012 10:15:42 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 10:15:59 -- Event Sync started 12203 ms after galaxy map.
SUN 15/04/2012 10:21:13 -- WIN  -> 79/0
SUN 15/04/2012 10:21:36 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 10:21:53 -- Event Sync started 12360 ms after galaxy map.
SUN 15/04/2012 10:27:07 -- WIN  -> 80/0
SUN 15/04/2012 10:27:31 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 10:27:47 -- Event Sync started 12219 ms after galaxy map.
SUN 15/04/2012 10:33:01 -- WIN  -> 81/0
SUN 15/04/2012 10:33:25 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 10:33:41 -- Event Sync started 12250 ms after galaxy map.
SUN 15/04/2012 10:38:56 -- WIN  -> 82/0
SUN 15/04/2012 10:39:19 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 10:39:35 -- Event Sync started 12187 ms after galaxy map.
SUN 15/04/2012 10:44:50 -- WIN  -> 83/0
SUN 15/04/2012 10:45:13 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 10:45:29 -- Event Sync started 12234 ms after galaxy map.
SUN 15/04/2012 10:50:44 -- WIN  -> 84/0
SUN 15/04/2012 10:51:07 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 10:51:23 -- Event Sync started 12172 ms after galaxy map.
SUN 15/04/2012 10:56:38 -- WIN  -> 85/0
SUN 15/04/2012 10:57:01 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 10:57:17 -- Event Sync started 12219 ms after galaxy map.
SUN 15/04/2012 11:02:32 -- WIN  -> 86/0
SUN 15/04/2012 11:02:55 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 11:03:11 -- Event Sync started 12078 ms after galaxy map.
SUN 15/04/2012 11:08:26 -- WIN  -> 87/0
SUN 15/04/2012 11:08:49 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 11:09:05 -- Event Sync started 12313 ms after galaxy map.
SUN 15/04/2012 11:14:20 -- WIN  -> 88/0
SUN 15/04/2012 11:14:43 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 11:14:59 -- Event Sync started 12437 ms after galaxy map.
SUN 15/04/2012 11:20:14 -- WIN  -> 89/0
SUN 15/04/2012 11:20:37 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 11:20:54 -- Event Sync started 12500 ms after galaxy map.
SUN 15/04/2012 11:26:08 -- WIN  -> 90/0
SUN 15/04/2012 11:26:32 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 11:26:48 -- Event Sync started 12140 ms after galaxy map.
SUN 15/04/2012 11:32:02 -- WIN  -> 91/0
SUN 15/04/2012 11:32:26 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 11:32:42 -- Event Sync started 12359 ms after galaxy map.
SUN 15/04/2012 11:37:56 -- WIN  -> 92/0
SUN 15/04/2012 11:38:20 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 11:38:36 -- Event Sync started 12235 ms after galaxy map.
SUN 15/04/2012 11:43:51 -- WIN  -> 93/0
SUN 15/04/2012 11:44:14 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 11:44:30 -- Event Sync started 12156 ms after galaxy map.
SUN 15/04/2012 11:49:45 -- WIN  -> 94/0
SUN 15/04/2012 11:50:08 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 11:50:24 -- Event Sync started 12328 ms after galaxy map.
SUN 15/04/2012 11:55:39 -- WIN  -> 95/0
SUN 15/04/2012 11:56:02 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 11:56:18 -- Event Sync started 12297 ms after galaxy map.
SUN 15/04/2012 12:01:33 -- WIN  -> 96/0
SUN 15/04/2012 12:01:56 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 12:02:12 -- Event Sync started 12156 ms after galaxy map.
SUN 15/04/2012 12:07:27 -- WIN  -> 97/0
SUN 15/04/2012 12:07:50 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 12:08:06 -- Event Sync started 12219 ms after galaxy map.
SUN 15/04/2012 12:13:21 -- WIN  -> 98/0
SUN 15/04/2012 12:13:44 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 12:14:00 -- Event Sync started 12172 ms after galaxy map.
SUN 15/04/2012 12:19:15 -- WIN  -> 99/0
SUN 15/04/2012 12:19:38 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 12:19:54 -- Event Sync started 12203 ms after galaxy map.
SUN 15/04/2012 12:25:09 -- WIN  -> 100/0
SUN 15/04/2012 12:25:32 - Mission Imperial44Aeten started, Mode:Event Delay:2000
SUN 15/04/2012 12:25:48 -- Event Sync started 12172 ms after galaxy map.

[thephilz]

whelps, then i honestly have no clue. theres no code telling swtor to close, and apart from key presses/mouse click, the bot only resizes the swtor window, so yeah.
im still saying its to do with file writing, but im not sure

its actually been somewhat of a persisting problem, but i really have no clue what is causing it

the other thing i noticed is that the deathcheck program is closed and the bot wont close its responding but wont close.

this may be helpful, ill look into deathcheck as well

[wollyboy]

well , its just weird it runs great for 3 or 4 missions then gets out of sync badly, totally exhausted, so ill wait for an update

BTW thephilz, you do rock tho!!!

[blinky57]

well , its just weird it runs great for 3 or 4 missions then gets out of sync badly, totally exhausted, so ill wait for an update

BTW thephilz, you do rock tho!!!

having the same issue.

@thephilz: at later levels you will see there are certain ships who do not spawn in the same positions/move along the same path. i first noticed on mugaar ice fields when one of the "elite" ships (has more HP then the others, does more damage + can shoot you even if your behind it) follows 2 different paths with ~2 inch different paths. i noticed this because i had made my own path, set it for the night and returned with 20/21 :: success/fail. confused i went to watch it for about an hour and noticed that every time it would fail, my ship would hit everything BUT that 1 ship, which is was missing by a MASSIVE margin, causing it to eventually get killed by said ship.

i've noticed the same phenominon on other missions (polith has the same ships aswell) but i can live through missing them, so its not a huge deal

[azza]

whelps, then i honestly have no clue. theres no code telling swtor to close, and apart from key presses/mouse click, the bot only resizes the swtor window, so yeah.
im still saying its to do with file writing, but im not sure

its actually been somewhat of a persisting problem, but i really have no clue what is causing it


this may be helpful, ill look into deathcheck as well

i should also mention that problem has happened a few times before 5.0 but it happens alot more now with 5.0 also when mine failed this morning deathcheck was still open,