Originally Posted by
Cystacae
To TMichael (TM):
I copied, renamed, and edited your impossible mission to the Ascendancy Barrier to replace the non working mission file and it directly works with some changes due to the fact it needs to be changed to Ascendancy by name and inside by changing Impossible to Ascendancy. Works like an absolute charm! Would it be possible for you to go over Phago's work in the mission files and see if you can optimize them like you did this mission? I mean that file is huge but it is just amazing and I do appreciate the work you put into it. I also would like Phago to be focusing on features and enhancements if he has no qualms with this.
To Phago:
If TMichael (TM) will take lead in the mission files I would like you to focus on features and enhancements. I know we have a few enhancements requested. I know not all of them we are fully interested in but I would like you to go over things and see what you can come up with. I do know one enhancement I am interested in knowing if we can and that is Bonus Mission successes. If you can find a way to get that to report that would be an interesting feature and I know one that people would appreciate. Also the focussed mission based tolerances/tweaks is a useful feature too and we have that one tab of Mission Tuning that is empty. I have a report and a mail coming where another forum goer modified the UI some and also did some changes to the crew skills they state so I am going to look it over and see if it is good to go. They say they spent 80+ hours on the UI and the code. I will also post it to a folder off the trunk for you to analyze along with me. Also my project for you which is I would consider a primary is to try to find with me a way to create an emulated mouse so people can use their own mouse to web browse while the bot operates.
To all you forum discussion peeps:
x64 Spacebot works, there is one issue with it in the hibernation it seems. Where the bot should be hibernating due to a swtor program/disconnect/shutdown problem it doesn't hibernate and instead will crash also. At least this is what I am seeing, I have been wrong though. This doesn't change the effectiveness of the bot only a feature isn't working as intended. I will run the bot more to analyze and investigate further.
Sounds great! Would it be easier for Phago and I to work off the same trunk, or should we keep them separate? I worry about changing things that might break what he's working on, and visa versa.
@Phago: Per bonus mission success, I was actually tinkering with that problem last night - I was curious to see how often the new IS mission would complete its bonus.
I came up with a working solution using IS as a test bed, but the same functionality should be applicable to the others. The method involves checking for bonus mission text during the last few seconds of a mission.
I added this function to the end of the IS script, but it should probably be integrated into misc.au3 with parameters for the image name. I suppose the coordinates used would not have to change if the search area is expanded a little to cover all potential bonus mission text.
Code:
Func BonusCheck() ; Call this to check for Bonus text on screen, up to 6 checks, lasts 1800 ms
$waitnum = 0
Do
$waitnum += 1
If $waitnum > 6 Then ; check 6 times before returning
$bonusdone = 1
Return
EndIf
Sleep(300)
Until _Imagesearcharea("pictures/IS_Tenders.png", 1, 830, 50, 940, 205, $xb, $yb, $img_tolerance)
$bonusdone = 0
EndFunc
Near the end of the mission, the call
Code:
; Check for bonus mission text, takes up to 1800 ms
BonusCheck()
which would probably look something like this after changes:
Code:
; Check for bonus mission text, takes up to 1800 ms
BonusCheck($image)
And then, in the main script, this can go wherever it will see daylight after every mission run (for testing, I put it at the beginning of Loop2). The vars $bonusdone and $bonuscount were declared as globals and initialized to zero.
Code:
If $bonusdone = 1 Then
$bonusdone = 0
$bonuscount += 1
GUICtrlSetData($BonusTotalLabel, "Bonus Wins: " & $bonuscount)
EndIf
Then it just needs some update to the UI to display the bonus data. I was thinking it might be cool to have a Won, Loss, and Bonus (W L and B?) column on each side next to the mission buttons, which would also involve a mission check in the last bit of code.
Anyway, that's as far as I got.
Per attack type integration in the mmove function: Is this going to be implemented with a new parameter in the mmove function call? If so, I can put those changes into the mission coding. I would just need to know what the call will be for each attack type (like 1, default, for the standard attack, either 2 or 3 for the attack style used in IS, etc).