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

[cartoonchikn]

it's weird. im doin the imperial28 mission Ezran. Ive made multiple perfect recordings. All main and side missions complete. I run my recording and it works flawless the first run, but after that it bombs out. Then later down the road it will run flawless again. The success rate is very low at the moment. I let it run for about 2 hrs and went 4-6-8

[JMcGean]

I've tried everything to get this to work on any of the Imperial side missions and it just doesn't want to work, with any recordings, or anything. Oh well, it was fun while it lasted!

[Ganondorf7]

Ok so that's why i'm getting these weird results. Was trying to record imperial28ezran, and both event and timer synch weren't working, waiting for a fix before i go and record it again.

[syz666]

I'm using 5.0 and I didn't notice any change from the recent patch, Zosha was running and got me 163/3 on event sync.

[thephilz]

Originally Posted by syz666

I'm using 5.0 and I didn't notice any change from the recent patch, Zosha was running and got me 163/3 on event sync.

as stated, the loading times differed on your computer specs

also, some missions were uneffected with event sync (like zosha) and some were (like the 28escort missions)

and others were just affected in unknown ways in general
for example, here is the same mission pre-patch and post-patch

pre-patch
TUE 24/04/2012 16:47:05 - Mission Republic20Makem started, Mode:Event Delay:1800
TUE 24/04/2012 16:47:30 -- Event Sync started 20186 ms after galaxy map.
TUE 24/04/2012 16:52:01 -- WIN -> 98/0
TUE 24/04/2012 16:52:25 - Mission Republic20Makem started, Mode:Event Delay:1800
TUE 24/04/2012 16:52:40 -- Event Sync started 10655 ms after galaxy map.
TUE 24/04/2012 16:56:41 -- BAIL - Death Screen Found - Bails:20

post-patch
WED 25/04/2012 22:16:29 - Mission Republic20Makem started, Mode:Event Delay:1800
WED 25/04/2012 22:17:05 -- Event Sync started 31980 ms after galaxy map.
WED 25/04/2012 22:21:36 -- WIN -> 138/4
(0 bails)

either my computer decided to love me a little more, or there was a slight undetected but obvious change in the mission - and knowing bioware, im going for the latter

in any case, im doing re-recording of event sync and hopefully will have the quick route done before the weekend starts

and yes, i ran republic20makem that many times to brute force my way from 27-28 because i couldnt be bothered doing my class quests, lol.

[jgoines]

@thephilz

As always, thank you for your efforts and your time.


I don't think it is as simple as changing the timer image. At least not on the mission I am testing with right now, Imperial34Skaross.

The timer image file is set at 00, I've taken another screen shot at 00 and they appear to be the same. What I did notice is that for part of the time the timer goes over a pole/space station at 00 so perhaps it is possible that the image search is missing the 00 some of the time or maybe they moved the the timer ever so slightly?

Now here the weird part. Autofire isn't working on the record nor the playback AND pressing 1 or 2 does the animation for ship to change shields or blaster power BUT the toggle switch in the keyboard doesn't light up during playback but does during record. I'm actually not convinced that the playback has the blaster fire toggle on at all.


PS Maybe I have been staring at this screen for too long but I could have sworn that I've seen the the ship take two different routes at the start.

[joshuar56]

I'm also having timer not found issues since the patch.

[jgoines]

Originally Posted by jgoines

Using 5.0 and re-recording a script with Autofire toggled off I was able to get a good Imperial34Skaross run. I have not tried re-recording a script with 5.0x with autofire toggled off. Is there maybe an in-game setting that controls autofire and this account has it set weird? (this isnt my usual account)

I lied second run through timer not found. Sometimes the timer is found, sometimes it isn't. See paranoid theories above. Also I just noticed that while the bot is in state "Waiting for timer" it does not notice that the mission failed/you died.

[joshuar56]

Let me be more specific, I can record fine (it finds the timer) but on playback on any mission (been trying on drexel) it gets stuck "looking for timer".

Originally Posted by jgoines

I lied second run through timer not found. Sometimes the timer is found, sometimes it isn't. See paranoid theories above. Also I just noticed that while the bot is in state "Waiting for timer" it does not notice that the mission failed/you died.

Yep this is exactly what I'm getting.

[Snow28]

Hi And while I have a problem!

If the bot is running it throws me after 5 try of the game because of inactivity!

What can I do?


Hallo Leute Und zwar habe ich folgendes Problem!

Wenn der Bot läuft wirft er mich nach 5 versuchen aus dem Spiel wegen inaktivität!

Was kann ich tun ?

[Forwardsbackflip]

The problem I'm currently having is that in kalee fortification half the time the bot can't find the timer and because of that it never starts running through the mission script, I get blown up and because it's still looking for the timer it doesn't realise I've exploded & doesn't click the exit space button and just sits there with pieces of my ship just drifting off into space.

The ideal solution to the timer problem would be to have them all as png files instead of bmp that way you could trim out all of the image that is not the actual number portions way it doesn't matter about the loading times because it'll be look specifically at the numbers and not the included background

[Ganondorf7]

Any eta on the new event synch images ?

[psan]

hat jemand ne vernünfigte einstellung für Sullust oder Polith? der blöde recorder funktioniert nichtmal ansatzweiße bei den beiden und dafür noch geld bezahlt -_-

[jgoines]

@thephilz

I think for a few of our problems the fix could be as simple as the "Waiting for timer ... " function has a 2-3 minute max time to wait at which point it forces an exit of the function and then the DeathCheck or Failed mission checks can do their thing and wait for "Leave Space Combat".

I think we can all agree that Bioware is messing with us (purposely or otherwise). In my opinion an overall theme/approach to dynamism is best, one of the many reasons I prefer UntzBot. In other words it seems like the static timer idea isn't working. (that is not a criticism, I think UntzBot is awesome)

My thoughts... (mind you I not used Image Searching in AutoIt in my own scripts)
What if as part of your recording your mission a screen shot was taken. Right now this functionality is separate from UntzBot what if it was encompassed within? It might make things a lot faster. I think the trick would be everything becomes Event Sync and without description text. The code might be something like press S and an Alt+PrintScreen is done and put into a bmp then cropped to the top right corner only. This might require you to record a script twice once for the image and then once more for movement.

[rootmaster]

Originally Posted by jgoines

@thephilz

I think for a few of our problems the fix could be as simple as the "Waiting for timer ... " function has a 2-3 minute max time to wait at which point it forces an exit of the function and then the DeathCheck or Failed mission checks can do their thing and wait for "Leave Space Combat".

I think we can all agree that Bioware is messing with us (purposely or otherwise). In my opinion an overall theme/approach to dynamism is best, one of the many reasons I prefer UntzBot. In other words it seems like the static timer idea isn't working. (that is not a criticism, I think UntzBot is awesome)

My thoughts... (mind you I not used Image Searching in AutoIt in my own scripts)
What if as part of your recording your mission a screen shot was taken. Right now this functionality is separate from UntzBot what if it was encompassed within? It might make things a lot faster. I think the trick would be everything becomes Event Sync and without description text. The code might be something like press S and an Alt+PrintScreen is done and put into a bmp then cropped to the top right corner only. This might require you to record a script twice once for the image and then once more for movement.

I really do not think it is the answer

As for the peeps looking for new event synch images......

you can make them yourself, if you follow the guide in the OP.