As you might have noticed, there is now a cool site finder utility on the DF embark screen. The only problem is, that you still have to manually generate world after world and run it through the site finder.
Don't despair, for you'll be given the brand new and oh-so-great DF Auto Site Locator:
http://www.geocities.com/qrphome/asl_v0.2.zipWell, it's actually just an AutoIt script that generates a bunch of worlds and scans them using DF's above mentioned built-in site finder. You can let it run over the weekend, or during the night, if you are hunting for this very special location that can only be found in 1% of all worlds...
INSTRUCTIONS
1. Download and install
AutoIt2. Download
Dwarf Fortress and unpack it to a new location
3. Change the default embark rectangle in data/init/init.txt to values of your liking (this will be used during the scan). DON'T CHANGE ANY FULLSCREEN SETTINGS!
4. Configure the world_gen.txt file. Make sure to change the right section (all world sizes have an own section, make sure you modify the values of the correct one)
5. Download the
DF_ASL script and unpack it to the newly created DF location
6. Change to the asl folder in the newly created DF location and edit the DF_ASL_bla.au3
7. Start dwarf fortress in windowed mode
8. Run the DF_ASL_bla.au3 script. You can abort it anytime with ctrl + c. Try not to hit any other keys during the scan, or the script might get confused.
9. After the scan, make sure to close DF and delete all data/save/regionX folders (or move them to another folder). This is important, because if you start the whole process on an unclean DF instance, the output in DF_ASL_locations.txt will be wrong.
If the script never leaves the start screen, the pattern files provided with the script don't work on your computer. There is another script called DF_ASL_Pattern_Utility.au3 you can run that tries to create patterns in an interactive way. Also, if the script behaves strange, you can try to increase the menu_delay and key_delay values in the script. They are responsible for the small pauses during script execution, and if your computer is slow, they might be too short, and the script might send keys to DF when it's not yet on the proper screen. I suggest doubling both values until the script behaves as expected (though it probably doesn't make much sense to go over 10000 for menu_delay and 2000 for key_delay).
Old version:
http://www.geocities.com/qrphome/asl_v0.1.zip