v50 Steam/Premium information for editors
  • v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
  • Use this page to report any issues related to the migration.
This notice may be cached—the current version can be found here.

Editing 40d Talk:Exploratory mining

Jump to navigation Jump to search

Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.

You are editing a page for an older version of Dwarf Fortress ("Main" is the current version, not "40d"). Please make sure you intend to do this. If you are here by mistake, see the current page instead.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
== Rationale for article ==
+
This is a guide on how to search for valuable materials by mining.<br>
This is a guide on how to search for valuable materials by mining...
 
 
...why is there any use for it? --[[User:Savok|Savok]] 18:52, 13 March 2008 (EDT)
 
...why is there any use for it? --[[User:Savok|Savok]] 18:52, 13 March 2008 (EDT)
  
Line 157: Line 156:
 
::Hmm, however... this way, a single row of teeth (the main row and the actual teeth) reveal the two adjacent lines, the one being dug, and then the ones further than the lines adjacent to the row. This means that, in a single row, Rows reveals 3 lines, and teeth reveals 5. So, it reveals 1.66 times as much as rows... The labour required is also the same as rows, and then a third of rows for each line of teeth, so an extra 2/3rds... 1.66 times the labour. Ok, it is well past midnight where I am, and I'll give myself an excuse if my math is sloppy. But now I agree that it's not more efficient, but... Shouldn't it be just AS efficient? Perhaps, try it with a larger area?--[[User:YF-23|YF-23]] 00:26, 8 April 2009 (UTC)
 
::Hmm, however... this way, a single row of teeth (the main row and the actual teeth) reveal the two adjacent lines, the one being dug, and then the ones further than the lines adjacent to the row. This means that, in a single row, Rows reveals 3 lines, and teeth reveals 5. So, it reveals 1.66 times as much as rows... The labour required is also the same as rows, and then a third of rows for each line of teeth, so an extra 2/3rds... 1.66 times the labour. Ok, it is well past midnight where I am, and I'll give myself an excuse if my math is sloppy. But now I agree that it's not more efficient, but... Shouldn't it be just AS efficient? Perhaps, try it with a larger area?--[[User:YF-23|YF-23]] 00:26, 8 April 2009 (UTC)
 
::Wait, actually, I think I got it why there's this disrepancy. If you take a grid that's XxY, and X is even, you'll have to dig an extra square per row of teeth that you won't if X is even. So, this design is either just as good or worse than rows depending on the area you want explored, plus it takes longer to designate. Guess it's not as good as I initially thought it was.--[[User:YF-23|YF-23]] 00:35, 8 April 2009 (UTC)
 
::Wait, actually, I think I got it why there's this disrepancy. If you take a grid that's XxY, and X is even, you'll have to dig an extra square per row of teeth that you won't if X is even. So, this design is either just as good or worse than rows depending on the area you want explored, plus it takes longer to designate. Guess it's not as good as I initially thought it was.--[[User:YF-23|YF-23]] 00:35, 8 April 2009 (UTC)
:::It might have better usability then just rows, plus it makes it easier to use multiple miners then rows does.
 
Or, for purely exploratory, there are trivial improvements:<div style="font-family: monospace; white-space: pre; line-height: 126.5%"><nowiki>
 
▒▒▒▒▒▒▒▒▒
 
▒.▒▒.▒▒.▒
 
.▒..▒..▒.
 
▒.▒▒.▒▒.▒
 
▒▒▒▒▒▒▒▒▒</nowiki></div>Now, in a 3x5 repeating space, 15 squares are revealed at a cost of 4, for a labor cost of 0.26 compared to .33 for rows. Or:<div style="font-family: monospace; white-space: pre; line-height: 126.5%"><nowiki>
 
▒▒▒▒▒▒▒▒▒
 
▒.▒▒.▒▒.▒
 
.▒..▒..▒.
 
▒▒▒▒▒▒▒▒▒
 
</nowiki></div>3x4, with 3 squares, for .25 cost
 
With a slight modification:<div style="font-family: monospace; white-space: pre; line-height: 126.5%"><nowiki>
 
▒▒▒▒▒▒▒▒▒▒▒▒
 
▒.▒▒▒.▒▒▒.▒▒
 
▒..▒▒..▒▒..▒
 
▒.▒▒▒.▒▒▒.▒▒
 
.▒...▒...▒..
 
▒▒▒▒▒▒▒▒▒▒▒▒
 
</nowiki></div> We have a 12x6 space in 21 squares: .291 cost, still better then rows. And:
 
<div style="font-family: monospace; white-space: pre; line-height: 126.5%"><nowiki>
 
...▒...▒...▒
 
...▒...▒...▒
 
...▒...▒...▒
 
▒.▒▒▒.▒▒▒.▒▒
 
.▒...▒...▒..
 
▒▒▒▒▒▒▒▒▒▒▒▒
 
</nowiki></div>It can become workshops or bedrooms, with no constructed walls.
 
[[User:Decius|Decius]] 23:02, 21 May 2009 (UTC)
 
 
== large clusters = no other stones? ==
 
 
When a 48x48 block has a large cluster, there are no small clusters or veins in there.
 
Not perfectly accurate.  I've seen chromite veins (with diamantoid) around olivine large clusters, and platinum veins extending out of magnetite.  And, of course, raw adamantine does whateverthehell it wants, large clusters or no.--[[User:Albedo|Albedo]] 15:45, 13 June 2009 (UTC)
 
 
== How do I find ores to mine? ==
 
02:00, 4 December 2007 [[User:Freakazoid]]
 
 
The simple answer is, [[mine]]. Mine until you can't mine anymore. You'll run into something eventually.
 
 
A more appropriate answer is that finding [[ores]], specifically finding ores you want, cannot be easily done without [[cheating]]. The best you can do is look up all the info in your chosen [[location]] and, based on the rock layers, can expect a certain range of ores to be present.
 
 
Once you have a fort running and you want to look for ore, a good method to look for veins of ore is to mine in a grid-like fashion. For each [[z-axis]] level full of stone, mine out an outer edge square of your choice in size. Repeat this square shape over and over until you've made your current layer into something like graph paper.
 
 
The size of your square is up to you. A large square will not keep your [[miner]]s too busy, but you may miss a couple veins. A small square will keep your miners occupied for seasons after seasons, hitting every vein but taking forever to explore another level. Making an 8x8 square is probably as small as you want to go, as veins are actually quite long and unless you're looking for [[gems]], you'll spend forever on one level, wasting time hitting previously discovered veins.
 
 
A quick way to get an early supply of available ore is to look across the area. Along rock faces and the edges of lakes and rivers, you can see what the rocks are made of. Once in a while, a vein of something will stick out. That's your clue that there is some more of it waiting behind.
 
 
As a reminder, your miners' starting [[skill]] in mining cannot be grater than proficient. Going after ore you've spotted on the surface with these dwarves will result in some loss, as they aren't skilled enough to leave usable ore behind each dig. At best, you'll get half of the ore as you mine it out. Waiting until your dwarves are more skilled will yield much more ore.
 

Please note that all contributions to Dwarf Fortress Wiki are considered to be released under the GFDL & MIT (see Dwarf Fortress Wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

Please sign comments with ~~~~

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)