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

Quote:

Originally Posted by eqip I dont get any mission to work, i have tryed everything that the guides says. Only thing that works is the timersync not event. And still there is realy bad. Any advice? Im using english client. Payed user!

If you are using a naga mouse or some sort of custom keybinds disable them, they are taking priority over the physical 1,2,3,4 keys.

i use a naga mouse and i have no problems with the bot at all. well besides some disconnects and logging back into the wrong server. but other then that i have gotten 2 lvl 50s and 2 white 41 expertise crystals from this bot. well worth the 10$

Quote:

Confirmed, Taspan mission is the only one that doesn't work.

Same with Republic40Hydian - "looking for Left Edge of Sun" till time run out. Switched to timer sync. Settings on "low".

Bei mir kommt ein line error ;o

For the past day or so since starting on running Syvris, I can only make about 30-40 runs tops before my client just crashes. I'm never around when it does happen, but SWToR is gone and the bot/deathcheck is still up.

I thought it was due to my screensaver, so I disabled that but it still happens. Most recently, it was after 37 wins.

Is there a log or something to look at as to what causes this? I never had this happen before this mission. Fondor easily ran 140+ times twice with no crashing.

Edit: Just happened again only after 5 wins. Unfortunately only heard the noise from the game stop to notice.

Curious question:

I tried using the same recording on an alt that uses a different starship and the timing does not work properly, but works when testing on my first character just fine right after I try on my alt. Do I really need to make recordings for EVERY character I use, in a separate UntzBot folder? O_o

Hey guys -

I've been using the bot successfully on two different characters for awhile now. My bounty hunter reached level 47 today, and so I attempted to record a level 44 mission. The issue is that neither of the level 44 missions are selected correctly by the bot. The bot opens the world map, clicks into the appropriate space region, and then attempts to click on the space mission but this final click is about 5-10 pixels off from where it should be. On Aeten it is off to the right, on Clouds to the left.

Just tried using another character, with the same result. This character has successfully botted these missions before. Tried both timer/event sync (though doubt that is relevant here).

Any ideas? Thanks!

EDIT: Fixed this issue by upping my OS resolution from 1024 x 768 to 1600 x 1900. This is somewhat unfortunate because it's easier to record missions on the lower resolution (larger window size).

yeah okay. i just found something out: apparently 'low' settings default to turning off BLOOM

however, the images provided match the settings with BLOOM turned ON
this means that only in a recent patch, did they change it so low = (bloom=off)

so yes, unless you turn to low and then turn bloom back on, the bot will 'malfunction', as MANY of you have noticed so far (myself included)

i will attempt to address this later

//

also, because game update 1.2 will change the crew skills, i will hold off a bit on the crew bot updates until it comes around or else itll render everything i do obsolete

in 1.2, apparently you can change your UI
this obviously means that if you change the UI enough, the bot will break pretty badly. please dont do so until i try to figure out some workarounds when 1.2 goes live.
if its impossible to do so, then you will be forced to stick with the default UI in order to bot - but i will try my best to allow it to work on different UIs

Bot is working pretty good, still trying to master recording. Only about 20% failure rate. Couple questions and a suggestion?

1. Can the recording sync multiple times through the space mission? Some places get lag and throw off sync, be nice to have 4 spots to re-sync?

2. Any tips for consistent recording? Should I start with cursor center window and end center window? Should I wait after delay before moving mouse on recording?

Suggestion.. On one of my recordings at the end my UI was not clickable , and the bot failed to click mission reward , could you set it up that it can reset the UI as a failover and try again before it stops ( CTRL+U twice.


Thanks

I am running in to a little problem. When I start the bot and record and then run the recording it works great. Ran it all night and I had 80 kills 1 death. However, when I turn off the game and bot for the day. When I go to start it that night my guy is not finishing the missions. The mouse is missing it targets. so what I am having to do is every time I want to start the bot I have to record the mission again then watch it to make sure it works. Can anyone help?

Quote:

Originally Posted by adoronron I am running in to a little problem. When I start the bot and record and then run the recording it works great. Ran it all night and I had 80 kills 1 death. However, when I turn off the game and bot for the day. When I go to start it that night my guy is not finishing the missions. The mouse is missing it targets. so what I am having to do is every time I want to start the bot I have to record the mission again then watch it to make sure it works. Can anyone help?

I know I am not the best example, but I have been making the habit before I record everything:

Re-boot pc
Launch game
Set game the standard resolution I play at
Launch bot and run to allow it to resize
Close bot
Launch bot ,
(set record mod)
Run bot
End

Then every time after I run I follow the same pattern except I don't record.
Seems tedious but extra few minutes worth it.

Hallo

Ich habe den Bot gerade getestet aber leider willer bei mir nicht so recht es leuft zwar alles super nur wen er in einer mission ist Schiesst er immer daneben.

Quote:

Originally Posted by hanna9999 Hallo Ich habe den Bot gerade getestet aber leider willer bei mir nicht so recht es leuft zwar alles super nur wen er in einer mission ist Schiesst er immer daneben.

Versuch mal am Delay etwas zu zu ändern.

Try to change the Delay.

Earlier today, I crashed on running Kovor first after 20 missions, and second time after 2 missions. Again, I'm never around when it stops but the SWToR client closes and the bot/deathchecker remain up.

Out of curiosity I recently switched to timer sync from event sync and ran 52:2 w:l throughout the day. I'm going to set it before going to sleep and hopefully end up closer to 40 uninterrupted.

Hallo

Wenn ich den DeathCheck41x.exe starte bekomme ich immer eine Error meldung "File does not exist : imagesDE/login4.bmp".