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

since friday my swtor client crashes without an error message after a few runs when running the bot, (the bot doesnt crash) someone having the same issue?

Quote:

Originally Posted by SETH3003 since friday my swtor client crashes without an error message after a few runs when running the bot, (the bot doesnt crash) someone having the same issue?

I had this issue starting on Republic34Kovor missions and later. It seemed switching to Timer Sync from Event Sync solved the problem.

I had my first "client crash" earlier this morning with Timer Sync (after having ran 500+ games without interruption) due my router resetting, thus bumping me off SWToR.

Quote:

my swtor client crashes without an error message after a few runs when running the bot, (the bot doesnt crash) someone having the same issue?

I have the same problem. I'm playing Syvris on timer sync. It will repeat from 5-50 times and then the game window closes, leaving the 2 bot windows open. Also when this happens and I left-click anything on the desktop, a menu pops up as if I had right clicked it.

Quote:

Originally Posted by slomojones I had this issue starting on Republic34Kovor missions and later. It seemed switching to Timer Sync from Event Sync solved the problem. I had my first "client crash" earlier this morning with Timer Sync (after having ran 500+ games without interruption) due my router resetting, thus bumping me off SWToR.

Problem here is that i always play with timer sync.
It worked on thursday but since friday i get the crashes.

having a problem here, its saying no world map found after clicking the seat. i reset game client. it worked once. now its saying could not find map

i got an update : swtor didnt crash tonight but i got 1% of sucessful missions with timer sync. maybe they changed sthg. I will try to make a new script and test that.

warum wird bei mir bei dem scheiß programm jedesmal immer nur looking or worldmap angeziegt ?

Das Programm ist nicht scheiß, wird ein Bedienerfehler sein...

Kann der Bot auch die lvl 40 mission ?

okay also ich hab es so verstanden es ist egal wo man auf der brücke steht man drückt im aktiven bot fenster Q und es soll gehen bei mir steht allerdings immer nur das mit looking bla bla auflösungg hab ich 1920 x 1080 im fenster modus grafik is hoch xD ich bräuchte bitte hilfe :)

I think they made a hotfix patch tonight where they fixed the XP for winning space missions. Im lvl 27 and still need to do Makem but im just getting 5xp for getting the mission done, so i think i need to level to 28 and then try to follow the route. Anyone else have the same problem? Or maybe have a fix?

Quote:

Originally Posted by eqip I think they made a hotfix patch tonight where they fixed the XP for winning space missions. Im lvl 27 and still need to do Makem but im just getting 5xp for getting the mission done, so i think i need to level to 28 and then try to follow the route. Anyone else have the same problem? Or maybe have a fix?

nah, thats normal

27 to 28 is the only level where space missions only give 5 exp/mission, because the level 20 mission only gives 5 exp at 27 and the next mission up is available at level 28

i recommend doing your class quests - by the time you finish tatooine you should be 28 and can continue botting

I Found a bug at Crew Bot!
Crew skill 3 hits he crewskill 2 i beleave you switched the coords and the Crewskill Spots.

I never got the crew bot to work.. it is always clicking in the wrong spot

Quote:

Originally Posted by [ShiizoPhreN]™ okay also ich hab es so verstanden es ist egal wo man auf der brücke steht man drückt im aktiven bot fenster Q und es soll gehen bei mir steht allerdings immer nur das mit looking bla bla auflösungg hab ich 1920 x 1080 im fenster modus grafik is hoch xD ich bräuchte bitte hilfe :)

Tja du hast es falsch verstanden.
Der Fehler dieses "scheiss Programms" sitzt 20cm vorm Bildschirm.


Auflösung (des game Clients): 800x600
Auf der Brücke in den Captain Stuhl setzen und die world map verlassen.
Dann Q drücken.

Siehe Post #1.