[Open Source] Lucky's Spacebot

[Cystacae]

All donators will get a couple of rare fringe benefits just to let you donators know. I will inform you in the future what those fringe benefits are and when you have them available. I am doing this as a thank you to donators and not an encouragement to get more donators. I just want to make sure your contribution is properly addressed and rewarded. Maybe preview access to 6.0 before anyone else has it (except coders and documentation team) as well as some personalization within the ui of the bot itself done by me. Those are only some random ideas, may not reflect what is really available.

[vapor311]

You can bring him into the documentation of the software/new docs. Just know together you guys should be able to make a killer Documentation and help file/Q&A. I know how it is to be busy. I am a single dad with a son and a girl friend with three other kids. Plus I am preparing for two trips back to back and find a new apartment in the meantime as I can no longer stay here for my own sanity. I will leave requests of what you ask of Vaelis up to you, I will just hand out what I would like so you and Vaelis can work together on things.

Vaelis you have AIm? Easy to communicate there.

Cy: Projects.
Read Me
Eula
Feature functionality
Q&A

These are where I am focused.
Piecing together rough drafts of those.

[vapor311]

3 page eula uploaded into files. This is a standard Eula from legal docs. It needs to be modified to fit what you want but it is a full blow software legalized eula.

[Cystacae]

3 page eula uploaded into files. This is a standard Eula from legal docs. It needs to be modified to fit what you want but it is a full blow software legalized eula.

Read that EULA it is for commercial software that doesn't provide source. Look through this link and find something that fits our open source and acceptance of modifications as long as they don't sell their product or call it something else. Also, it needs to cover our asses as it is "educational" to see if we can do these things like automation. Just so we can't get sued by someone. Also one that doesn't give any type of warranty. Various Licenses and Comments about Them - GNU Project - Free Software Foundation (FSF)

[phagotron]

Didnt work, tried different Aero themes and even the basic one with no success.

Here's the sys info:

Lucky's Spacebot v5.35psx (preview R29)

System details: X64 CPU, WIN_7(X64) Service Pack 1
RAM total:7 GB,free:3 GB, used:62 %
Desktop dimensions: 1920x1080(32bpp, 60Hz)

SWTOR Client is running with 1024x766
SWTOR Window:0,0 Win size:1040x804

On Target Time=49
Missile Delay=333
Timer Skew =+50
IMG Tolerance=100
HD Status=0
Timing override=4
Mission bonus=1
PSX OTT enabled=1
PSX DBG enabled=4
Last mission=
Win / Loss 0 / 0


HD mode for some reason detects the mission 20 seconds after the start and then it instantly tries to exit the mission.

Your settings seem to be ok, calibration says nominal? If so and it wont even detect the pixels in HD mode this is quite strange indeed. It def looks as if your desktop isnt Aero. Maybe try another mission...

[vapor311]

Read that EULA it is for commercial software that doesn't provide source. Look through this link and find something that fits our open source and acceptance of modifications as long as they don't sell their product or call it something else. Also, it needs to cover our asses as it is "educational" to see if we can do these things like automation. Just so we can't get sued by someone. Also one that doesn't give any type of warranty. Various Licenses and Comments about Them - GNU Project - Free Software Foundation (FSF)

Alrighty. Ill give it a look.

[vapor311]

See if the upploaded EULA suits your fancy.

[TMichael]

HD mode for some reason detects the mission 20 seconds after the start and then it instantly tries to exit the mission.

I just wanted to explain why I think this is happening and what I have in mind to remedy the problem.

There are two searches performed at the start of a mission. The first will display "scanning for mission start image (HD mode)" in HD mode or "scanning for mission start image" in normal mode. Yesterday, a second color check was added here to increase the success chance of the HD search. Fingers crossed, more testing needed.

The second search will display "scanning for mission timer init", and this seems to be where many users are having an issue. This part of the script waits to match the green time remaining numbers on the upper right of your user interface with an image in the pictures folder so the mission can be properly synchronized. The problem we sometimes see is that the efficiency of ImageSearch (as well as its AutoIt cousin, PixelSearch) varies from system to system because the function is reading colors directly from your display. And display quality can vary. This is why the tolerance was added, but of course that's not always enough.

Our current collection of timer pics seems to include a mixture of both faded and brighter images. Later today, I'll go through them and make sure we have two or three versions of each one - from faded to crisp and bright - after which I'll update the script to check for each image type during the mission timer initialization.

I'll post here once the update is complete. Again, fingers crossed.

[phagotron]

I just wanted to explain why I think this is happening and what I have in mind to remedy the problem.

There are two searches performed at the start of a mission. The first will display "scanning for mission start image (HD mode)" in HD mode or "scanning for mission start image" in normal mode. Yesterday, a second color check was added here to increase the success chance of the HD search. Fingers crossed, more testing needed.

The second search will display "scanning for mission timer init", and this seems to be where many users are having an issue. This part of the script waits to match the green time remaining numbers on the upper right of your user interface with an image in the pictures folder so the mission can be properly synchronized. The problem we sometimes see is that the efficiency of ImageSearch (as well as its AutoIt cousin, PixelSearch) varies from system to system because the function is reading colors directly from your display. And display quality can vary. This is why the tolerance was added, but of course that's not always enough.

Our current collection of timer pics seems to include a mixture of both faded and brighter images. Later today, I'll go through them and make sure we have two or three versions of each one - from faded to crisp and bright - after which I'll update the script to check for each image type during the mission timer initialization.

I'll post here once the update is complete. Again, fingers crossed.

Thanx TM, would be great to have another pic set available. Please put them into a separate folder like set2 with same name. Im awaiting an alt set where the sec is very close behind the numbers, seems as if this is another tor trick ... so selecting an alt set or searching more than one img might help us for some time. Even if with tolerance around 100 slight differences of brightness should not matter that much.

It seems to be time to get hands on imgsearch, maybe there is a way to improve it.

[TMichael]

Thanx TM, would be great to have another pic set available. Please put them into a separate folder like set2 with same name. Im awaiting an alt set where the sec is very close behind the numbers, seems as if this is another tor trick ... so selecting an alt set or searching more than one img might help us for some time. Even if with tolerance around 100 slight differences of brightness should not matter that much.

It seems to be time to get hands on imgsearch, maybe there is a way to improve it.

Welcome!

No worries, I was planning on keeping the new set separate for testing. I'd like to standardize the naming scheme for the timer images to something straightforward as well. Once the images are ready (along with the alt set you're getting) I figure we can update and test each mission. I envision something along the lines of:

Func WaitForMissionTimerInit($mission, $image1, $image2, $image3, $ms)

   Local $script_start = TimerInit()
   Local $result = 0
   Local $x=0
   Local $y=0
  
   dmsg($mission & ": scanning for mission timer init (tolerance: " & $img_tolerance & ")")

   Switch
      Case FileExists($image1) = 0
         dmsg($mission & " Error: " & $image1 & " doesnt exist or isnt readable.")
         sleep(3000)
         Return 0
      Case FileExists($image2) = 0
         dmsg($mission & " Error: " & $image2 & " doesnt exist or isnt readable.")
         sleep(3000)
         Return 0
      Case FileExists($image3) = 0
         dmsg($mission & " Error: " & $image3 & " doesnt exist or isnt readable.")
         sleep(3000)
         Return 0
   EndSwitch

   Do
      Sleep(50)
      $result1 = _Imagesearcharea($image1, 1, 825, 40, 930, 80, $x, $y, $img_tolerance)
      $result2 = _Imagesearcharea($image2, 1, 825 ,40, 930, 80, $x, $y, $img_tolerance)
      $result3 = _Imagesearcharea($image3, 1, 825, 40, 930, 80, $x, $y, $img_tolerance)
   Until $result1 = 1 Or $result2 = 1 Or $result3 = 1 Or TimerDiff( $script_start ) > $ms

   If $result = 1 Then
      dmsg($mission & ": mission timer init succeeded.")
      AdlibRegister("mission_progress",250)
      MouseMove(612,390)
      Return 1
   Else
      dmsg($mission & ": mission timer init failed.")
      Return 0
   EndIf

EndFunc

and in the mission script:

If $result=WaitForMissionTimerInit($mission_name  & " 7:55 " , "pictures/55a.png", "pictures/55b.png", "pictures/55c.png", 7000) = 1 Then
   $mission_secs = 480  ; (7:55)
Else
   Send("{ESCAPE 1}")
   space_ende()
   Return 0
EndIf

[vaelis]

Vaelis you have AIm? Easy to communicate there.

Cy: Projects.
Read Me
Eula
Feature functionality
Q&A

These are where I am focused.
Piecing together rough drafts of those.

Unfortunately no AIM, am also on Aussie time so that could cause a comms issue (Email will be your best bet.)

If you like I'm happy to get started on a User / Features guide with some basic troubleshooting tips.

[vapor311]

Unfortunately no AIM, am also on Aussie time so that could cause a comms issue (Email will be your best bet.)

If you like I'm happy to get started on a User / Features guide with some basic troubleshooting tips.

Sounds like a plan and I sent you my email via pm.

[Cystacae]

See if the upploaded EULA suits your fancy.

That EULA works and covers EXACTLY what I wanted! YAY! Now if I could only find those stars cause you deserve a gold one for the wall of Cystacae's little helper list! LOL! That only thing I see an issue is the formatting as some of the sentences wrap to the next line and make it look bad. Contents are muy perfecto! thanks!

[vapor311]

That EULA works and covers EXACTLY what I wanted! YAY! Now if I could only find those stars cause you deserve a gold one for the wall of Cystacae's little helper list! LOL! That only thing I see an issue is the formatting as some of the sentences wrap to the next line and make it look bad. Contents are muy perfecto! thanks!

Ill fix that with Word. Just wanted to make sure It covered our bums. I even sounded all legal and stuff in it!

[vapor311]

Matter of fact, finished, edited and signed sealed delivered.