[For Free] Luckys Spacebot

[thegaf]

Just checked on two successive runs (didn't watch, but happened to catch the aftermath)...

It appears my ship crashed/was destroyed, so I guess rock timing, etc. changed a bit for Drexel.

My guy was at 9-16 when I stopped him.

Now I'm doing Pakuuni on another guy, hopefully it's cool.

And by the way, for anyone who is changing the codes to work for you, if you don't mind, could you post them up as you do 'em? (like Nadademais did)

Thanks Lucky, and thanks all.

EDIT... Thanks Ichiboo.

I've been running Pakuuni all morning and its not good at all. I was 5-12 at one point.. ugh

BTW for you iphone users there is an app called PC2ME that will allow you to remote desktop into your PC from your phone. Good shit, I use it all the time.

[thegaf]

Lucky,

Is there a way to add a tab or something that will allow us to change the timing between when the bot clicks accept and when the script starts without having to do it in AI3? That may solve a lot of these weekly breaks to the bot.

There probably is a way we can do this but I'm not sure what you are asking... You would like to add a variable timing for starting the next mission after accepting a mission complete reward box? Are you trying to make it quicker or slower? I use crewskills and have no problems. I do feel like there is a bug in the daily looping part.. havent had a chance to look into it.

[luckysurfcs]

Has anyone looked into modifying the Ezran code as multiple people including me have reported its way off at the moment. No worries if no-one has, i know theres more than enough changes being work through by certain people already

If there's anyone who's not gettin problems with ezran can u say so? as far as i know its a problem for everyone at the moment.

For the record im a level 28 imp.

[Ichiboo]

There probably is a way we can do this but I'm not sure what you are asking... You would like to add a variable timing for starting the next mission after accepting a mission complete reward box? Are you trying to make it quicker or slower? I use crewskills and have no problems. I do feel like there is a bug in the daily looping part.. havent had a chance to look into it.

Earlier in the thread, it was suggested to change a line in version 4.2 to fix the offset in timing we were experiencing.

for aeten i changed line 2985 from 30000 to 49000 just a quick dirty fix aeten is running fine for me again after i recompiled

nexy33 was referring to this (line is bolded and red):

Func Aeten_Main()
   
$x1 = 0
$y1 = 0
$x2 = 0
$y2 = 0
$x3 = 0
$y3 = 0
   
                  Sleep(1000)
                  Send("{SPACE 1}")
                  Sleep(1000)
                  MouseMove(518, 600) ; Stuhl
			      Sleep(1200)
                  Sleep(300)
                  MouseClick("right")
                  Sleep(300)
                  MouseClick("right")
                  Sleep(5000)
                  MouseMove(380, 269) ; Galaxiekarte
				  Sleep(500)
                  MouseClick("left") 
				  MouseClick("left")
                  Sleep(2000)
                  MouseMove(571, 377) ; Aeten
                  Sleep(2000)
                  MouseClick("left") 
				  MouseClick("left") 
			      MouseMove(861, 674) ; Jetzt Reisen
                  Sleep(2000)
                  MouseClick("left") 
				  MouseClick("left") 
                  MouseMove(475, 445) ; Ja
			      Sleep(1000)
                  MouseClick("left") 
				  Sleep(30000)
			  	  Sleep(3000)

The bolded/red line is what seemed to adjust the timing adjustment between when you would load Aeten, and it would start to search for targets. It also seemed to make a global adjustment to the mission of when the bot would go from shooting to passive with the shield on.

I've been using the 4.2 au3 file up to this point making adjustments to that particular line (as well as the similar lines for the other missions). Since all I've had to do to this point is make adjustments to that line, I was hoping for another tab with an input field to adjust that line.

I may be totally off the mark since this bot is my first experience with AutoIt.

[DjVandal]

Has anyone looked into modifying the Ezran code as multiple people including me have reported its way off at the moment. No worries if no-one has, i know theres more than enough changes being work through by certain people already

If there's anyone who's not gettin problems with ezran can u say so? as far as i know its a problem for everyone at the moment.

For the record im a level 28 imp.

you need the level 29 upgrade for ezran even though it is available at 28

[DjVandal]

You are correct on the basics.

The "mission start" coords are pretty easy to program, autoit comes with a tool to find them.
I would suggest looking for a mission similar to the one you are trying to program and use the colors from it.
get some basic timing information I think a good way to do this is Fraps then watch the replay and take notes on when you need to dodge, fire what weapons, look for what targets ect...
lay out the code and try a run. Then adjust and try again.
the pro way to do it would to be to make sure you are using the gear for the level of the mission. This will insure that it will be usable for everyone.

GL

Thank you for the pointers ill start playing around to see what i can contribute

[thegaf]

Earlier in the thread, it was suggested to change a line in version 4.2 to fix the offset in timing we were experiencing.



nexy33 was referring to this (line is bolded and red):

Func Aeten_Main()
   
$x1 = 0
$y1 = 0
$x2 = 0
$y2 = 0
$x3 = 0
$y3 = 0
   
                  Sleep(1000)
                  Send("{SPACE 1}")
                  Sleep(1000)
                  MouseMove(518, 600) ; Stuhl
			      Sleep(1200)
                  Sleep(300)
                  MouseClick("right")
                  Sleep(300)
                  MouseClick("right")
                  Sleep(5000)
                  MouseMove(380, 269) ; Galaxiekarte
				  Sleep(500)
                  MouseClick("left") 
				  MouseClick("left")
                  Sleep(2000)
                  MouseMove(571, 377) ; Aeten
                  Sleep(2000)
                  MouseClick("left") 
				  MouseClick("left") 
			      MouseMove(861, 674) ; Jetzt Reisen
                  Sleep(2000)
                  MouseClick("left") 
				  MouseClick("left") 
                  MouseMove(475, 445) ; Ja
			      Sleep(1000)
                  MouseClick("left") 
				  Sleep(30000)
			  	  Sleep(3000)

The bolded/red line is what seemed to adjust the timing adjustment between when you would load Aeten, and it would start to search for targets. It also seemed to make a global adjustment to the mission of when the bot would go from shooting to passive with the shield on.

I've been using the 4.2 au3 file up to this point making adjustments to that particular line (as well as the similar lines for the other missions). Since all I've had to do to this point is make adjustments to that line, I was hoping for another tab with an input field to adjust that line.

I may be totally off the mark since this bot is my first experience with AutoIt.

Yeah I see where that would cause problems. A variable would be easy to program but a better option would to be what nada did and pick a time on the counter and image search to start the shooting part. This would make any load time a nonissue.

[gcn1595]

Has anyone gotten Sullust to work in 4.22?

[Ichiboo]

Yeah I see where that would cause problems. A variable would be easy to program but a better option would to be what nada did and pick a time on the counter and image search to start the shooting part. This would make any load time a nonissue.

Ahh, I've not been keeping up on the thread and didn't realize this matter had been resolved. I'm also trying to learn this stuff as I go, so thanks for keeping your reply constructive I'll be able to contribute one of these days.

[Slemkeft]

Right now neither Aeten or Sullust is working for me, using 4.22 or 5.1.

[pikachu83]

amen, need it fixing, dying without this automatic leveling :P

[thegaf]

Right now neither Aeten or Sullust is working for me, using 4.22 or 5.1.

I dont have an imp so I can't help you.. sorry guys.

I have a patch for Pakuuni.

			      MouseMove(861, 674) ; Jetzt Reisen
                  Sleep(2000)
                  MouseClick("left") 
				  MouseClick("left") 
                  MouseMove(475, 445) ; Ja
			      Sleep(1000)
                  MouseClick("left") 
				  Sleep(43000)
			  	  Sleep(3000)

change that to Sleep(42000) and delete the other sleep.

I'll be releasing this later tonight after I gather up any other changes.

GL
Gaf

[Slemkeft]

I tried changing those two lines around back and forth on the Aeten mission and I literally saw NO difference. Tried understanding the rest of the code but it's alot and it's late.

Edit: If you could tell me sort of step-by-step what you are doing to fix the Republic missions - what timing are you looking for, and when you found an offset, what you do to fix it - perhaps I could do the same to the Empire missions.

[thegaf]

I tried changing those two lines around back and forth on the Aeten mission and I literally saw NO difference. Tried understanding the rest of the code but it's alot and it's late.

Edit: If you could tell me sort of step-by-step what you are doing to fix the Republic missions - what timing are you looking for, and when you found an offset, what you do to fix it - perhaps I could do the same to the Empire missions.

So pakuuni was easy.. I wasnt getting enough kills. The first time it fired the weapons 3 targets had passed. I figured it need to start sooner and looked in the code where first firing happens and shaved off a few seconds.

What issues are you having?

[Slemkeft]

So pakuuni was easy.. I wasnt getting enough kills. The first time it fired the weapons 3 targets had passed. I figured it need to start sooner and looked in the code where first firing happens and shaved off a few seconds.

What issues are you having?

So it's basically switching between shield recharging and shooting mode at really weird places, nothing close to optimal. I end up dying at ~1:30 left and about 20 kills to go. I tried changing the Sleep(x) lines as I said, but it didn't change a thing.