they usually do their patching Tuesdays or Wednesdays...
See: bold and large.Quote:
- DO NOT CUSTOMIZE YOUR UI (yet) - just to be safe. at the moment, it detects your world map on the bottom right corner, so i may change the detection mechanism to allow you to change your UI around, but thats a maybe. besides, youre botting, not playing, so just keep it default for now.
2000ms (2 seconds) is VERY LARGE (it literally should be +-100ms, or even less) and i advise that you find a better sync image to use as there is possibly multiple occasions where the same event can get matched, such as drexel40/sullust40 where the 6 ships come in, and more ships come in from the same positions - mismatching can cause the script to start on THE WRONG SET of ships and pretty much break the runQuote:
Any suggestion on how to synchronize it properly, i tried both event synch (i also created the images, 4x4 bitmaps) and timer synch but still it's always off by a few seconds. Even adjusting the delay doesn't help, as it is off randomly +-2000ms. Since you get such a high success rate there's something i'm doing wrong.
fresh resets usually help for loading time/lag issuesQuote:
I seem to have an issue where my loading time to get into the mission is all over the place and it never stays constant so would this be better to use the timer option? I have gotten this bot to work for me before but I have never had such nonregular load times for the missions. Its very strange.
missions are all preset difficulties, so just get the appropriate upgrades when needed (the .zip has some files to let you know what to get them)Quote:
Switched to the other mission, now it works perfectly. Once i get to 44 i'll subscribe, so pretty soon.. it's close to 100% success rate on republic34Pakuni. Using the default event synch, then i recorded the mission once, has been running smoothly. Don't even need to upgrade the ship until then i guess (or do missions scale with my level ?).
deathcheck should pick this up, make sure its running in the 'background' in admin mode (when it picks up a fail/death, it sends the 'E'/stop command to the main module)Quote:
Ok, well this game is too easy even for a bot i guess untzbot gets bored from time to time. One thing i noticed, and that's probably not me doing something wrong (or is it ?) the bot does not detect mission failures, ie when you die, get to the end of the mission but didn't complete the objective (usually happens if i accidentally move the mouse while checking on the bot), then it will just get stuck.
Ok will try in admin mode, also i worded that wrong, i meant when you don't die but fail, it gets stuck. Any way to have multiple (virtual) mouse devices work with this ? And i mean, on the same machine, without using vms.Quote:
deathcheck should pick this up, make sure its running in the 'background' in admin mode (when it picks up a fail/death, it sends the 'E'/stop command to the main module)
so, while doing the crewbot stuff, a mission ended, then the 'drag down' to 5th member blew up the script?Quote:
Issue with Crewbot. When mission ended while crewbot routine in progress - character turn away from galaxy map. Mission result message in left side of screen and mouse trying to srcoll crew window to 5th crewmemer.
It was more often for me on level 5 scavenging - missions are short, and have same duration. 4 times in 6 hours.Quote:
so, while doing the crewbot stuff, a mission ended, then the 'drag down' to 5th member blew up the script?
VERY rare but possible