This is my customized Drexel code of Nadademais' edit. I have a 100% success rate with it using level 41 upgrades on a Jedi Knight on version 4.22 of the bot.
What I did was add a few custom barrel roll triggers as well as a 7-second delay after the first encounter with the star destroyer. This should get your shields back up to about 70% before the large wave of ships in the event that you are hit by a torpedo or laser fire during the star destroyer encounter.
You will need to run Drexel with barrel roll disabled. If this doesn't work, I'd suggest adding barrel roll during the large wave of fighters as well. I have no idea if this will work for you or anyone else for that matter so PLEASE make a back-up of your current script or compiled exe.
Uploaded the compiled exe and the modified code if you want to compile it yourself. Also included the 45sec that needs to go in your pictures folder if you didn't already have it.
I don't think some people realize it, but you can do Pakuuni/Skaross up to level 41 and receive full experience. I find that to be the best way to guarantee success with Drexel and Sullust.
basically it may show 1280x1024 wich is a 4:3 aspect but because of the wide screen it stretches it into a 16:9 the only way i am able to get my laptop to display in 4:3 is useing an old external monuitor for botting
.
you can tell if your wide screen is displaying 1280x1024 correctly on a widescreen as there will be "black strips" around your display and the actually viewable area will be more or less square
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.
Yes i was able to enable the black areas around my screen. through the ATI control panel but still I have to manualy move the crewskills window further to the left for the bot to be able to start it , and like i said it goes good for 1-2 then it auto opens up the mission log and hangs. :-(
Untrack all your missions so there isn't a list of them on the right aide of screen.
Press l then click the circles beside each mission so they are hollow.
Sounds like the bot is checking for pending and finding your mission list maybe.
Sent from my HTC Incredible S using Tapatalk 2
Did timing or something change for Drexel with last night's patch?
Yesterday, I was maybe 90% success / 10% fail with Nadademais' edited Drexel code.
Today, so far, I am maybe 30% success / 70% fail.
I cannot watch the bot right now and see why it is failing more often, but anyone else see decreased success rate after last night's patch?
I wonder if anyone is able to post a brief idea on what is required to program the missing missions?
I have a very basic understanding of autoit but definatley have the time to do anything to assist.
Id imagine we would need to find the starting coords for each one
pixel color for the specific mission
mission time
?
Surely the BW devs are not ignorant about the spacebots, and I'm sure they are purposely "breaking" the bots by changing timing. I'm going to see if I can fix my own copy when I get home - if I can fix my copy, I'll post results and lines to fix if I can get it to work.
Last edited by Ichiboo; 05-01-2012 at 11:53 AM.
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.
Last edited by vancejohnson; 05-01-2012 at 11:51 AM.
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