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:Stone

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 157: Line 157:
  
 
::I think it would look better in a separate section specifically dedicated to that purpose rather than added onto that table. It really doesn't seem like it's going to fit nicely. [[User:VengefulDonut|VengefulDonut]] 23:41, 10 August 2009 (UTC)
 
::I think it would look better in a separate section specifically dedicated to that purpose rather than added onto that table. It really doesn't seem like it's going to fit nicely. [[User:VengefulDonut|VengefulDonut]] 23:41, 10 August 2009 (UTC)
::Actually, I'm not entirely sure what we want out of something like that. The gem locations we can already see in one place. There is one dedicated to ores as well. What exactly is the goal here? Could it instead be accomplished by copying over those tables to here? (Or perhaps linking them?) [[User:VengefulDonut|VengefulDonut]] 23:48, 10 August 2009 (UTC)
+
::Actually, I'm not entirely sure what we want out of something like that. The gem locations we can already see in one place. There is one dedicated to ores as well. What exactly is the goal here? [[User:VengefulDonut|VengefulDonut]] 23:44, 10 August 2009 (UTC)
::: The reason I've visualized in my head is when you have your miners digging, and they hit Bauxite, and I want to know what's so unique about Bauxite, well, I can come here and see that it's the exclusive source of Rubies, Saphires, and Star Rubies and Saphires.  Yey!  Now my dorfs can hollow out the the whole bauxite cluster looking for the gems.  Otherwise I agree with you, this column doesn't make sense here, and doesn't reflect how Toady One designed the RAW files. --[[User:3lB33|3lB33]] 01:28, 11 August 2009 (UTC)
 
:::: Well, unless you are searching for specific gems, I don't see the point to this column. Even more since there's some information already in the [[Gem#Precious|precious gem]] section of the wiki. For the [[bauxite]] example, it's already listed in the article that's the only stone containing rubies and sapphires. If a new player saw this table, he might miss the part about the bauxite being the only magman proof stone. --[[User:Karl|Karl]] 01:42, 11 August 2009 (UTC)
 
 
 
I don't see the point to this column
 
 
 
It was originally a compromise for stones that were not perfectly generic.
 
Which is to say, that column was intended to cover information that set some few stones apart from truly "generic" ones (like, say, microcline) without needing their own page, which would all be stubs and even more offensive.  If a stone has only a couple minor details that make it stand out, that single column covers them all nicely and completely - and in a single glance.  --[[User:Albedo|Albedo]] 03:33, 11 August 2009 (UTC)
 
 
 
::Telling someone why the column was created is not relevant when they are asking what the point of the column is. ("Why was is created" vs. "Why do I want it here"). Also, I would find individual stone stubs to be less offensive than the current arrangement. Can you really tell me you find the thing aesthetically pleasing? The framework for putting the stone infobars together is already set up and since they are almost all generic most of them wont need any special treatment. Probably a 15-30 min copy/past job. [[User:VengefulDonut|VengefulDonut]] 08:22, 11 August 2009 (UTC)
 
 
 
:::If you *really* have a problem with it, make the pages yourself. As it stands now, most of the people that like it this way are the only people that might make a bunch of individual pages for the stone, unless you actually have plan to create them. Complaining about the way it is when it's okay as it is and you have no plans to change anything really doesn't do anything unless you can find someone that will do something. We've got it looking good enough right now and to some it is pleasing to look at.[[User:Shardok|Shardok]] 08:27, 11 August 2009 (UTC)
 
 
 
:::: First, by most of the people, you are speaking of the 4-5 peoples out of hundred who wrote here ? The fact is, this column serve no real purpose, the information is easily available elsewhere. An old timer would know this information already or know where he might find it, a new player might not even care to find some specific gems. 7 of the 40 entries are not empty, of these 7, 4 already have articles with the information available. And after a quick glance at the ores and gems articles I don't see how we could add more information to this column. I would rather create the 3 missing articles, remove the column and add an asterisk or some markup to the specific articles so we can better see that they are not link to wikipedia. There's already this little bit of text, upside of the table : ''The types of stone listed here that do not link to their own article are generic.'' (I'll not do it right now, since we are discussing about it... that's the point of a talk page. It's just a suggestion that will remove the ''ugliness'' of the table, without really removing the "information" part) --[[User:Karl|Karl]] 11:45, 11 August 2009 (UTC)
 
 
 
:Well, actually, I may have been unclear here. I meant should I put in what ores are found specifically in certain stones. Which, I noticed afterward was already stated (Platinum being the only one). [[User:Shardok|Shardok]] 04:00, 11 August 2009 (UTC)
 
 
 
"Why was is created" vs. "Why do I want it here"
 
The diff is subtle - "Why it was created" is the reason why ''some'' wanted it here; whether that's seen as a valid reason by all is not my job to intuit.  If "some" users found it useful, then by definition it's ''useful'', whether or not it's useful to you or me.
 
I would find individual stone stubs to be less offensive than the current arrangement.
 
(You realize that is the ''exact opposite'' from your stance from your view on the [[Olivine]] article, which, if you recall, was the spark that led to this column in the first place.  Currently, the only stone articles with minimal text are ones for individual [[layer]] stones, which is the only reason those exist.  Views change, all good - just saying.)
 
I would rather create the 3 missing articles
 
And they would say ''"this is a stone, and it has this one quirk."''  Meh, personally, I dislike having to go to a separate page for each stone just to find that out, when I can see all that and more at a glance on a table.
 
you are speaking of the 4-5 peoples out of hundred who wrote here
 
We are speaking of the people who are vocal here and now, which is all we can speak of (besides keeping to the guidelines and existing style of this wiki.)
 
An old timer would know this information already<br />a new player might not even care to find some specific gems
 
With that philosophy we can delete 90% of the wiki, leaving only "advanced but not too advanced" stuff- but based on ''who's'' perspective?  <br />
 
The wiki starts at square 1 and goes as deep as the users care to offer.  Having info on different pages is not always the best plan.  The column looks odd because most stones ''are'' generic - it's the few exceptions that it addresses, and it covers them well - aesthetics aside, it does the job from a functional perspective.  In the end, that is the large part of what we're talking about - style and personal preference.  The only functional distinction is whether that information is better served scattered on several articles, or living in this one table.--[[User:Albedo|Albedo]] 18:09, 11 August 2009 (UTC)
 
 
 
::I have always been a proponent for having individual articles for every stone. This is how the wiki ended up with so many stone articles despite occasional opposition (look at the histories :). If you reread the arguments on the olivine page carefully, you will find that I have never said I oppose such a plan. [[User:VengefulDonut|VengefulDonut]] 03:15, 13 August 2009 (UTC)
 
 
 
: Quote to quote is somehow annoying, anyway. Should we edit the other table to add a special row for the granite to see that it's the only stone where you can find bismuthinite? It's redundant information and goes against the R policy ''Redundancy: Before creating a new page, do a search to find out if the topic is already discussed in detail somewhere else. If you find that redundant pages already exist, merge their content and have one redirect to the other. '''This rule also refers to redundant material inside pages'''. '' We basically duplicate information already available in this wiki. It's not like it's hard to click a link, except if the person is '''lazy''' :p --[[User:Karl|Karl]] 23:32, 11 August 2009 (UTC)
 
 
 
::Redundancy is not evil if done correctly. [[User:VengefulDonut|VengefulDonut]] 03:15, 13 August 2009 (UTC)
 
::: True enough, but in this case it's better served by this article ; [[The_Non-Dwarf's_Guide_to_Rock]]. Not only is it good looking, but it list every type of rock, not only the "other rocks". --[[User:Karl|Karl]] 10:57, 13 August 2009 (UTC)
 
 
 
::: I removed the last column of the table, added the 3 missing link... 2 of them were created, the third one already existed... which is odd, since the table linked to the wiki article. Like I said, it's duplicated information, you have it inside 5 of the 7 stones articles, 2 of them where created instead. It's possible to find this information, and a lot more inside the non-dwarf guide, and AFAIK, if someone struck a new stone he didn't know or remember, is first move, if he ever come here, will be to search for the stone name, not for the "other stone" article. So by having articles for specific stone, we actually help them navigate this wiki.
 
 
 
::: Semantically, a table with a lot of duplicate or repetitive information doesn't really serve it purpose, either. --[[User:Karl|Karl]] 00:55, 16 August 2009 (UTC)
 
  
 
== Alluvial ==
 
== Alluvial ==
Line 201: Line 163:
  
 
:Alluvial = soil, at least in DF. [[User:VengefulDonut|VengefulDonut]] 23:45, 10 August 2009 (UTC)
 
:Alluvial = soil, at least in DF. [[User:VengefulDonut|VengefulDonut]] 23:45, 10 August 2009 (UTC)
::Actually, alluvial is '''not''' soil, at least in 40d - all of the gems and minerals stated to appear in ALLUVIAL layers never actually show up in soil. If I change all instances of ENVIRONMENT:ALLUVIAL to ENVIRONMENT:SOIL in the raws, then I end up with soil layers containing small clusters of gold, cassiterite, and tons of gems. The [ALLUVIAL] tag itself doesn't seem to have any effect. --[[User:Quietust|Quietust]] 19:59, 10 September 2009 (UTC)
 
I'd have to guess it's another of T's over-plotting elements, one that (as yet) has not been developed.  And, yes, from the evidence it seems that "alluvial" is not "soil", not by DF definitions anyway.--[[User:Albedo|Albedo]] 21:56, 10 September 2009 (UTC)
 
 
== Dorfen nuke? ==
 
 
Has anyone figured out how to crack the secret of pitchblende?
 
 
Well, for that matter, a while I was keeping blocks of brimstone, saltpeter, and coke/charcoal next to the alchemist's shop in case someone had a ''really'' strange mood, but despite the suggestive materials I don't know if anything is implemented. [[User:Dorf and Dumb|Dorf and Dumb]] 07:12, 16 September 2009 (UTC)
 
 
== Actual pictures ==
 
 
I've been thinking about adding pictures of the actual stones to the pages, is this okay? ([[User:Justyn|Justyn]] 07:44, 23 September 2009 (UTC))
 
 
:The general rule I've been told is to just do things, rather than wait for some force to give you permission (provided you respect the stylistic choices of the site). In this case, I think adding it to the "DF Geology and real-world Geology" section would be fine. -- [[User:RomeoFalling|RomeoFalling]] 08:00, 23 September 2009 (UTC)
 
 
:: I was asking to see if there were any ''objections'' rather than asking permission, I should have said that flat out. ([[User:Justyn|Justyn]] 09:21, 23 September 2009 (UTC))
 
 
== If you can't move a rock ==
 
This is for DF beginners as well as a question.  If you reclaim a fortress and destroy a pre-existing wall, suddenly the rock you destroyed cannot move.  That is because it is, like everything else you reclaim, set to "forbidden", in order to fix this you need to "claim" the rock before your dwarves will move it.  Also, if you are building a large wall on top of pre-existing rock sometimes your dwarves will try to build the wall but say something is blocking the way, this is because the rock you want to build with is not the one the dwarves will try to pick up (instead of using the rock "0 spaces away" they will try to use the one next to it, and when they try to build the one next to it they will encounter the same problem).  To avoid that you should build the walls one segment at a time (1x1, not 1x10 as usual).
 
 
Now for the question.  I have a few rocks in my reclaimed fortress that are not forbidden but simply will NOT move.  I cannot get dwarves to dump them, I cannot get dwarves to haul them off to a "Rock storage pile" I cannot get my dwarves to do anything with them but they are in the middle of my supply piles and my dwarves will not put supplies where these rocks are.  Any ideas?
 
:Known issue - anything which is '''T'''a'''SK'''ed at the time of abandon will be impossible to interact with unless you force the object to be moved by some other means (such as flowing water, cave-in dust, or simply channeling the floor out from underneath it). Also, please sign your comments. --[[User:Quietust|Quietust]] 04:54, 21 February 2010 (UTC)
 
 
== Layer 'main' link issue ==
 
 
The 'Main: Layer' thing at Layer section points to the newest version, instead of 40d. I would fix it myself, but alas I can't get it working, no matter what I do. Can someone better at wiki-formattomg fix that? --[[User:Haspen|Haspen]] 10:42, 5 May 2010 (UTC)
 
:Hrmph.  Well, since <nowiki>{{L|Layer}}</nowiki> doesn't interact properly with the <nowiki>{{main}}</nowiki> template... I just hardcoded it to the 40d version.  Shouldn't be a problem unless the community abruptly decides to redesignate the 40d-version pages to something else entirely. [[User:DeMatt|DeMatt]] 11:05, 11 May 2010 (UTC)
 

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)

Templates used on this page: