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

trying to get it to work been away from swtor for 2 weeks because of a move. Anyways. It loads the galaxy map then then says "no seat" after its in the galaxy map.

ok just call me dumb. fraps was messing with it

Quote:

Originally Posted by swtorsneak A mission "loop" option to play all quest dailies in order would be a feature that would make me buy the pro version, since we no longer get fleet commendations for grinding the same mission.

working on it, on my priority list due to the stupid changes to fleet commendations

Haven't been able to get any version running since 1.2 patch. Getting non-array error others have reported right when trying to resize window proper in debugger or starting in the bot itself.

I tried running 4.1 and 5.0 versions, none successful so far. Tried several missions 10ish or 44ish with no luck. The bot is working but does not finish missions as recorded, I don't know what am I doing wrong - been using it since the 3.3 version and everything was fine until 1.2 hit us hard.

used 5.0 today. first time user. Level 20 mission.

Did "q"
Then reset UI to default.
Recorded Mission.
Played mission successfully.

8 out of 9 wins.

thx

Quote:

Originally Posted by slomojones Haven't been able to get any version running since 1.2 patch. Getting non-array error others have reported right when trying to resize window proper in debugger or starting in the bot itself.

i believe i packed the debugger wrong in the 5.0 version, sorry. try any other version debugger, like the one in 4.1x

Quote:

Originally Posted by syz666 I tried running 4.1 and 5.0 versions, none successful so far. Tried several missions 10ish or 44ish with no luck. The bot is working but does not finish missions as recorded, I don't know what am I doing wrong - been using it since the 3.3 version and everything was fine until 1.2 hit us hard.

its not you, explanation is below this

//

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

[Only registered and activated users can see links. Click Here To Register...]
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

alright i couldn't sleep at night and gave it a few additional runs noticed following: Imperial10Jabiim as well as Imperial44Clouds in eventsync works for me with no changes in anything at all. funny thing is before the update i couldn't get clouds to work, now i downloaded some default eventsync files you posted and everything runs fine. it flew 50-12 (losses are due to my low ship upgrades and not best record of the mission but it's no problem once i update). jabiim worked 100%.

edit: let me know if you want me to check other missions if it might save you some work i'll gladly help.

Quote:

Originally Posted by syz666 alright i couldn't sleep at night and gave it a few additional runs noticed following: Imperial10Jabiim as well as Imperial44Clouds in eventsync works for me with no changes in anything at all. funny thing is before the update i couldn't get clouds to work, now i downloaded some default eventsync files you posted and everything runs fine. it flew 50-12 (losses are due to my low ship upgrades and not best record of the mission but it's no problem once i update). jabiim worked 100%. edit: let me know if you want me to check other missions if it might save you some work i'll gladly help.

as i said, higher end computers probably have suffered less from 1.2 than lower end computers

a clear example is the green moon - the mission loads WAY too slow now for this bad computer for the default event sync (which was made using this computer) to work, but it works fine for my brothers higher end computer

with that in mind, the 'easiest overall fix' would just be shift everything forward a little bit so both lower and higher end computers are fine

also, i need to do that anyway because the 28+ missions rely on the power boost thing, which is not possible anymore until you start doing dailies

Where register to gain access??

I have a not so oustanding record of 54-34 on republic drexel, mostly because of failed event sync. So i sort of confirm about the loading times problem, it still works sometimes. A small suggestion to improve event sync: multiple events at start (also verify by reading the timer above that you found it at about the right time, sometimes it will think it found an event way later in the mission, and then proceeds to fail it) and resynchs later during the mission (mostly during small breaks in it).

a nice addition to the crew skills bot would be to allow selecting a primary and secondary skill so that if there are only say 3-4 missions but your sending out 5 guys, it goes to the secondary mission to do a skill there. Also, now that the robot can gain affection, and you can buy a sensor unit to give him boosts to the specific crew skills you have, it might be smart to select the bottom guy instead of scrolling down and selecting the guy above the bottom when you select 5 members. This would also solve the problem of selecting 5 crew members when you only have 5. I did this before getting the 6th on a char, and it wouldnt send out the 5th guy probably because of the mechanic listed above.

Nice work philz, keep it up.

##### thephilz #####

any chance you could respond to this? especially the part about sending out 5 crew members when you only have 5

my timer sync on the lvl 40 mission worked 106 out of 3 very nice !

Hey Philz, im not sure if this is just isolated to my laptop (not the greatest performance) but after going 47-26 last night (always run clouds, its the best credit-per-second) I decided to check out the log.

I'm on timer sync at it was starting anywhere between 33750ms - 3580ms after worldmap. Anything between 33750 - 34040 was a WIN, anything higher than 34040 was a LOSS. Curious if it may be possible to include a MIN and MAX value in the bot (under no circumstances start BEFORE X-afterworldmap and not AFTER x-afterworldmap...the X being the MS value and if it were to reach the AFTER ms value the bot would just start without a delay)

Or maybe you could shine some light on why my MS would vary so much :)


EDIT: or perhaps just setting an auto correct delay...for every 100MS difference in start time from recorded start the delay would respectably adjust itself up or down?
Thanks!

Quote:

Originally Posted by mindgame18 Hey Philz, im not sure if this is just isolated to my laptop (not the greatest performance) but after going 47-26 last night (always run clouds, its the best credit-per-second) I decided to check out the log. I'm on timer sync at it was starting anywhere between 33750ms - 3580ms after worldmap. Anything between 33750 - 34040 was a WIN, anything higher than 34040 was a LOSS. Curious if it may be possible to include a MIN and MAX value in the bot (under no circumstances start BEFORE X-afterworldmap and not AFTER x-afterworldmap...the X being the MS value and if it were to reach the AFTER ms value the bot would just start without a delay) Or maybe you could shine some light on why my MS would vary so much :) EDIT: or perhaps just setting an auto correct delay...for every 100MS difference in start time from recorded start the delay would respectably adjust itself up or down? Thanks!

the whole point of the log was for this very purpose, however it is not very 'clear' what the fail/pass conditions are

for example, here is one of my latest logs:

SUN 15/04/2012 09:16:35 -- Event Sync started 15179 ms after galaxy map.
SUN 15/04/2012 09:19:26 -- BAIL - Death Screen Found - Bails:2

SUN 15/04/2012 10:02:15 -- Event Sync started 15116 ms after galaxy map.
SUN 15/04/2012 10:05:42 -- WIN -> 64/1

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

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

as you can see here,

15070 = fail
15116 = win
15179 = fail
15195 = win

so its not 100% accurate. at this point in time, the log is just there for .. well, being a log, really, and seeing how the bot went over time or something (it doesnt really have a use, i just thought it was nifty)

could be different issues then. Mine seems pretty linear. I've watched the bot and all the missions that started after the threshold(it seems) the cursor was just lagging slightly behind...enough to fail.

my log doesn't have any over my 34040 that was a win