Dwarf Fortress Wiki - User contributions [en]

Talk:Animal person

2023-01-17T09:58:41Z

Jan: /* .50 updates */

== FEATURE_ATTACK_GROUP ==

These are no longer tagged as animal person:
'''Amphibian man''', '''Antman''', Bat man, Cave fish man, Cave swallow man, Olm man, '''Reptile man''', '''Rodent man''', '''Serpent man'''

Instead they have some new tags, including 'FEATURE_ATTACK_GROUP' any notion what that mean? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 22:04, 29 December 2022 (UTC)

: ...I take it the explanation as it stands in the tag definition ([https://dwarffortresswiki.org/index.php/Creature_token#FEATURE_ATTACK_GROUP]) is not enough? [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 22:14, 29 December 2022 (UTC)
:: I am interested in what makes them special, why they are the only ones tagged like that? so I can figure out whether just remove them from the list of animal people or also add them somewhere else too. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 22:26, 29 December 2022 (UTC)

== .50 updates ==

This page is currently out of date for .50. The lists of races of possible subterranean animal people civs is missing a bunch of races that I've seen spawn (maybe that's related to FEATURE_ATTACK_GROUP?), animal people show up in other civs now (I've seen cardinal men in human sieges), and subterranean animal people civs show up in the list of civs on the civ screen now (albeit always as friendly, even if they're inherently hostile).

I would just update this myself but I'm only half-sure about some of these things, and don't want to accidentally add misinfo. If nothing else, this is a note to myself to do some research and get around to fixing this at some point. [[User:Desistance|Desistance]] ([[User talk:Desistance|talk]]) 01:24, 16 January 2023 (UTC)

Related to this, [[Creature#Tribesmen]] does have an AFAICT complete list of underground animal people that form tribes. [[User:Desistance|Desistance]] ([[User talk:Desistance|talk]]) 02:11, 16 January 2023 (UTC)

: I [https://dwarffortresswiki.org/index.php?title=Animal_person&type=revision&diff=280281&oldid=276248 recently removed] them. Reasoning is that every creature on this page have the <code>[APPLY_CREATURE_VARIATION:ANIMAL_PERSON]</code> except those, though it might have been premature as upon second look that have been the case in previous version as well.
:Quick notes: The removed subterranean animal people are uniquely tagged as <code>[FEATURE_ATTACK_GROUP]</code>, and all subterranean creature_man are uniqly in that they form a <code>[ENTITY:SUBTERRANEAN_ANIMAL_PEOPLES]</code>. I believe lore wise they suppose to be 'tribes' but I am unclear what gameplay affect these tags have in v50 compared to other subterranean creatures like "stupid" Troglodyte. Also even if animal people are shown as 'Intelligent Wilderness Creature' they do not have the {{token|INTELLIGENT|c}} in raws.
: Your observation seem more current then mine, enjoy the research and revert\update the entry as neccessary.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 09:58, 17 January 2023 (UTC)

Dwarf Fortress Wiki talk:Versions

2023-01-10T10:38:18Z

Jan: /* Creature List Now Supports Graphics! */ reply

{{archive|
# [[DF Talk:Versions/Archive 1|Page 1]]}}

== Version 0.31.19 starts a new DF generation? ==

My reading of Toady's comments on the release of 0.31.19 is that it came out basically because he felt it would take too long to get DF all the way to 0.32. With the ore changes, the sitefinder changes, the addition of grazing and several different industries, there's a lot of changes between 31.18 and 31.19. So I'm thinking it might be a good idea to call it the first release of DF2011 - and what we refer to as "DF2010" would then become 0.31.18.

Thoughts? --[[User:DeMatt|DeMatt]] 07:06, 28 February 2011 (UTC)

==Revisiting Redirects==
I wasn't around when the redirect policy was created, and I'm having trouble understanding the rationale. The example claims that linking [[Main:Cheese]] to [[cv:Cheese maker]] is problematic...but mainspace only ever redirects to the current version. If the best target in the current version is cheese maker, why not link to it directly? (It's not, at least for Cheese, since [[DF2012:Cheese]] exists now.) The explanation seems to be claiming that 40d articles that link to Cheese will follow the Mainspace link--but that hasn't been the case for a long while now. Articles in 40d automatically link against other articles in 40d, so that version remains internally consistent no matter where mainspace links to in the current version. For a current example, what do we gain by linking [[Main:Mead]] to [[cv:Mead]] and linking [[DF2012:Mead]] to [[DF2012:Alcohol]]?

If this really is just an outdated procedure, I recommend we drop the mummery and allow mainspace to link to cv:(best target). Double redirects ''may'' work (sometimes, but [[Main:Mead]] demonstrates a common problem where automatic redirection fails), but if they are unnecessary I think they should be avoided, partly because of problems like [[Main:Mead]] and partly because of the effort required to protect double redirects from users who believe they are problematic.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:16, 8 January 2014 (UTC)

:I was just thinking that. I'm currently attempting to write a basic extension to eliminate the need for mainspace redirects entirely, although Mediawiki's class structure may make this more difficult than I had hoped (the only method I've found for resolving redirects takes the ''article text'' instead of a title, e.g. "#REDIRECT ..."). I do agree that the current situation with redirects isn't ideal, so I'm hoping this will work better (once I get it to work). --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:42, 8 January 2014 (UTC)

Okay, that wasn't quite as clear as I meant it to be. In general, I think this is a tricky situation. Mediawiki wasn't designed to have five content namespaces, and certainly not chains of redirects between them. The problem that was pointed out in the [[DF:REDIR|policy]] is the fact that with:
Main:Foo -> cv:Bar
pages in the cv: namespace can't use [[<nowiki/>foo]], since the namespace links modification causes it to be treated as [[<nowiki/>cv:foo]] instead, which doesn't exist. The current suggested solution is this:
Main:Foo -> cv:Foo -> cv:Bar
This fixes the problem of [[<nowiki/>foo]] not working on cv pages, but creates issues with double redirects not always working. Another solution, which is more intuitive to new editors, is:
Main:Foo -> cv:Bar
cv:Foo -> cv:Bar
Both require creating two redirects. The first method has the advantage of ''ensuring'' that the cv redirect exists (otherwise, main:foo would be a redlink), while the second has the advantage of working more reliably in a couple cases.

What I'm trying to do is make main:Foo "jump" to cv:Foo when cv:foo exists, ''even if main:foo doesn't exist'' (basically it would treat all mainspace pages as redirects to cv pages, but only if the cv page exists and not the mainspace page). I had main:Bar jumping to cv:Bar fine, but if cv:Foo redirected to cv:Bar, accessing main:Foo would mysteriously stop at cv:Foo even if I increased the redirect limit. What I'm trying to do now is follow the redirects internally, without relying on Mediawiki to do it automatically - unfortunately, that has proved to be harder than I had hoped (and I sent my web server into an infinite loop while trying). I will try to work on this some more when I get a chance, although I'm not sure when that'll be yet :(. For now, feel free to fix broken double mainspace redirects as necessary, as long as redirects in the DF2012 namespace stay pointing to the right page (and new mainspace redirects get added in the DF2012 namespace too). --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:21, 9 January 2014 (UTC)

:You're treating cv like a namespace--it's not. It is simply shorthand for "fill in the current version here". [http://dwarffortresswiki.org/index.php?title=User_talk:Briess&diff=182404&oldid=181281 As I discovered a long time ago on a server not far away], linking from Main:Foo to cv:Foo tends to break redirection chains. If, instead of linking to cv:Foo, you link to DF2012:Foo, it might just work. It would, of course, be better if your patch could evaluate cv itself, but even if you have to hardcode the current version it's a single point of maintenance that requires update very infrequently. (For that matter, we could probably dispense with the cv hack entirely and just have a bot update mainspace links from DF2012 to DF201X when we switch to a new version.)--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:05, 9 January 2014 (UTC)
::I know cv isn't a namespace - I was just trying to avoid future confusion when the DF2012 namespace changes. It's interesting that changing "cv" to "DF2012" fixes some broken redirects, although I've found that simply making an edit to a broken redirect can usually fix it as well. I've actually had the most problems with double redirects when the second one (in the DF2012 namespace) doesn't use the DF2012 prefix (e.g. main:Foo containing <nowiki>[[cv:Foo]] and DF2012:Foo containing [[Bar]]</nowiki>). I'd rather keep the cv alias even if it isn't necessary for mainspace redirects when I get the patch to work, since it makes it easier to refer to the current version of the page (for example, several MDF articles contain links to a vanilla page for things that don't change in the mod).
::Also, using aliases like "cv" is supported by Mediawiki; in fact, several WMF wikis use them (for example, "[[wikipedia:WP:Redirects|WP:Redirects]]" on Wikipedia). It's quite likely that Mediawiki isn't processing double redirects using aliases correctly, though, since that's uncommon on most wikis. --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:35, 9 January 2014 (UTC)

In light of the lack of support for the current redirect policy, I propose we replace the current redirect section with:

:Mainspace article pages should use the cv: alias when redirecting to a versioned page, which will automatically update the link when a new version is released. For example, page "Main:Foo" should redirect to page "cv:Bar" (where "Bar" is the page that best describes the topic Foo in the current version).

:Pages in mainspace should only redirect to an older versioned page if that content no longer exists in the current version of the game (e.g. [[Cave river]], [[Chunk]]). In these cases the cv: alias cannot be used.

:Pages inside a versioned namespace should not use the cv: alias. Instead, they should redirect to the best page within that versioned namespace (e.g. [[DF2012:Dodging]], [[v0.31:Drink]]).

:Due to limitations of the wiki software, double redirects should be avoided if possible. When fixing double redirects in mainspace, please make sure to use the cv: alias as appropriate.

If no one objects, I will make this change in a few days.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:21, 15 January 2014 (UTC)

:Okay with me. It may be worth mentioning that double redirects only really need to be changed when they don't work (since changing a lot of redirects that work isn't necessary), but I think it's clearer and more relevant than the current policy. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:26, 16 January 2014 (UTC)

Done.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:55, 22 January 2014 (UTC)

I was finally able to get my extension to work after being motivated by one too many malfunctioning redirects. It now causes nonexistent pages in the main namespace to behave exactly like redirects to their DF2012 counterparts (when linked to, accessed directly, and transcluded). Double redirects also work (up to 100, in fact, although that was a temporary safety measure that I'll probably change). This means we'll be able to safely get rid of all mainspace redirects (redirects that redirect to something other than "cv" will still function if not deleted). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:20, 14 March 2014 (UTC)
:What about articles which don't exist in the current version but do exist in older versions? Will those still need mainspace redirects, or will your extension be able to automatically redirect them to v0.31/40d/23a? --[[User:Quietust|Quietust]] ([[User talk:Quietust|talk]]) 01:29, 14 March 2014 (UTC)
::It ignores all mainspace pages that actually have content, including redirects, so pages like [[masons guild]] won't be affected (unless deleted). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:47, 14 March 2014 (UTC)

Done and deployed. [[Cat]] is still treated as a redirect, even though I just deleted it (try clicking on the "redirected from" link). Pages that exist are ignored, so [[Masons guild]] and [[History of Dwarf Fortress]] still function normally (as a redirect to a 23a page and a non-redirect, respectively). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 18:57, 14 April 2014 (UTC)

I'm sending around a bot right now to delete all redirects of the format "foo -> cv:foo" (a surprising number don't fit this format, so I'm leaving them alone for now). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:43, 14 April 2014 (UTC)

:I'm confused. Do we use double redirects or not? Is there a single place we define our linking policy (including redirects), and is it updated?
:I had trouble linking to [[Consolidated_development]] in [[v0.34:Dragon]]. It kept pointing to v0.34:Consolidated_development, which does not exist. I ended up linking to Main:Consolidated_development to make it work. --[[User:Nahno|Nahno]] ([[User talk:Nahno|talk]]) 10:18, 1 July 2014 (UTC)

::That's a separate problem altogether - links in the versioned namespaces (v0.34, v0.31, 40d, 23a) automatically link to pages within their namespace. I may be able to set up a fallback to mainspace once I'm able to deploy again, but for now the "main:" alias is the intended solution. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 11:36, 1 July 2014 (UTC)

== Google often directs people to the 0.31 page ==

I've noticed a couple of times that finding a wiki page from an external search will often drop me onto a page from an older version. Is it possible to mitigate this somehow for new players? I could imagine something like redirecting old:Bar -> cv:Bar unless the user has come from old:Foo; no idea if that would actually work though. [[User:PeridexisErrant|PeridexisErrant]] ([[User talk:PeridexisErrant|talk]]) 11:48, 4 May 2014 (UTC)

:As a temporary solution, I could write a script that displays a banner of some kind if the user came from an external site. I'll ask Briess if he can do anything on the server level to increase the weighting of the current version's pages. (Obviously there are situations where people are looking for old pages, like [[23a:dungeon master]], so we don't want to disable indexing entirely on old pages.) —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:03, 4 May 2014 (UTC)

== DF2014? ==

As Toady [http://www.bay12games.com/dwarves/ draws closer to a new release], it might be worthwhile to discuss the addition of a new version to the wiki. The upcoming release covers two years of changes and introduces a number of new plants, foods, drinks, multi-tile trees, climbing, jumping, etc., so it is likely to have significant changes from the current DF2012. To avoid having people start new pages (and lose all the effort spent refining the prior version's page), I think it would be best to have a bot automatically copy over the DF2012 pages as a starting point for DF2014. I would suggest that these copied pages include a noticebox template mentioning that the content may be outdated, so that we can easily track which pages have been reviewed. I think either the {{tl|version check}} or {{tl|old}} template would work. --[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 19:43, 5 May 2014 (UTC)

:This is what [[User:QuietBot]] did after the 0.34 release, so it's certainly possible to use the same script to migrate to DF2014. I would like a way of tagging migrated pages, since inaccuracies in some pages went unnoticed for months after they were migrated. Since {{tl|old}} is already in use, {{tl|version check}} may be a better solution (it can be reworded slightly, or we can make a separate template for DF2014 migration). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:23, 1 June 2014 (UTC)
:Made [[Template:DF2014 migrated]] as an example. Any thoughts? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:32, 1 June 2014 (UTC)

== Redirects inconsistency ==

Following a redirect is supposed to be exactly the same as going straight to the page it redirects to, but this actually isn't the case:
* Go to [[Seeds]] and you get [[v0.34:Seed]] (outdated)
* Go to http://dwarffortresswiki.org/index.php?title=Seeds&redirect=no and click on the link and you get to [[DF2014:Seed]] (current)
So if you search for "seed", the top result is the DF2014 version. But search for "seeds" and you get the redirect, which sends you to the outdated page instead. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 23:22, 22 February 2015 (UTC)

While I'm talking about redirects, it seems redirects to sections don't work: see [[DF2014:How do I manage my seeds and crops]]. I know MediaWiki is capable of this trick because Wikipedia does it. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 23:32, 22 February 2015 (UTC)

:I have absolutely no idea why [[seeds]] redirects to a v0.34 page - it could be a Mediawiki bug. The section links issue is due to a known issue in the redirect extension we use, which has yet to be fixed. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:01, 23 February 2015 (UTC)
:It looks like deleting both [[Seeds]] and [[DF2014:Seeds]] fixed things (by allowing AutoRedirect to handle the redirects instead). Feel free to tag any others with {{tl|bad redirect}}. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:03, 23 February 2015 (UTC)
::It gets stranger. [[Vial]] redirects explicitly to [[cv:Flask]] which displays (when you look at it with &redirect=no) as [[DF2014:Flask]], but still goes to the v0.34 version. It seems redirects interpret the cv: pseudo-namespace (or whatever it's called) in an outdated way. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 18:08, 23 February 2015 (UTC)
::I've added a note to this page about this issue. If it gets resolved, the note should be removed. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 21:04, 23 February 2015 (UTC)

==Reorganizing versions==

The internet deals with moved content... poorly. Google is still linking to v0.34 pages more than a year after the switch to "DF2014", and even the wiki software still has cached links pointing to the old version pages.

I propose reorganizing versions on the wiki to avoid moving content whenever possible. Instead of having a temporary "current version" namespace that changes occasionally, all the current information gets promoted to the Main namespace. When the next version split occurs, the Main articles as of a certain revision number can be copied to the newly-created permanent "old version" namespace, while all the current information remains in Main. This not only fixes the link rot issue, but it has a few other benefits as well: fewer administrative tasks, no lockdown (a historical version of the Main pages can be copied at any point, even if the Main articles are already modified for the new version), almost all the article history is maintained in the Main article (instead of being spread unevenly across multiple versions), no "temporary" namespaces are needed, fewer problematic long redirect chains, and hopefully less user confusion (since Main gets priority in search results, etc.).

As an example, today we would not have a DF2014 namespace (which is good because "temporary" namespaces historically disappear anyway). If you ran a search for [[seed]] you'd end up at Main:seed, which would have all the current information on seeds. The version box at the top of the page would still link to the older versions of the seed article. When a new version is released, an admin would choose a revision number and copy the Main:seed article as it exists at that revision number to v0.40:seed. That's it. One historical copy that needs little to no new editing, and zero redirections/moves.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 19:02, 27 July 2015 (UTC)

:Makes sense to me. It would involve a lot of work, though (e.g. fixing templates and categories to account for the current version being in mainspace), although that should be doable thanks to {{tl|category}}, {{tl|version switch}}, etc.. A bot could be set up to copy revisions from before a release date as well, which would be more difficult (and maybe slower) than a direct copy, but not severely. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:24, 30 July 2015 (UTC)

:Actually, there are a few issues with that, namely that there wouldn't be an easy way to distinguish between versioned and non-versioned mainspace pages. There are ways to resolve Google search priority (we can exclude pages from older versions from search engine results if there are newer versions of those pages available, for example). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:47, 6 August 2015 (UTC)

::There aren't very many non-versioned mainspace pages, and determining if a page is versioned is as simple as looking for the version template and/or categories added by the version template (e.g. copy [http://dwarffortresswiki.org/index.php/Category:Current this category] instead of Main:*). The problem with "suggesting" newer pages to Google is that they obviously aren't crawling our wiki regularly (if they were, the fact that the mainspace redirects point to new pages would automatically be picked up). Even if your Google hints worked they wouldn't do anything for all the other broken links out on the 'net.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:35, 6 August 2015 (UTC)

::: Google actually crawls the wiki constantly - we probably get crawl hits from google for a continuous block of 2-3 hours per day, each and every day. Why they are slow to update is beyond me though. I can't remember why we didn't do this initially, but there was a technical limitation involved if I remember correctly. --[[User:Briess|Briess]] ([[User talk:Briess|talk]]) 22:05, 6 August 2015 (UTC)

::: There are <meta> tags that can be used to hide pages from search results (for search engines that recognize them, that is). Searching for {{tl|av}} or [[:Category:Current]] might work, although we'd have to make sure all of the DF2014 pages include that (some pages don't, particularly some disambiguation pages, although all of them should). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:53, 6 August 2015 (UTC)

:Is there a particular reason main and current are separate to begin with?—[[User:CLA|CLA]] ([[User talk:CLA|talk]]) 00:17, 7 August 2015 (UTC)

::It's mostly intended to distinguish between versioned and non-versioned pages and make version-related templates simpler to work with, since every versioned page has a namespace. I wasn't active here in 2010 when this system was created, so Briess and Emi would know more.
::Another issue I just thought of with Loci's suggestion is categories - currently, categories like [[:Category:Animals]] are used to organize the versioned sub-categories. Sure, we can change {{tl|Category}} to categorize mainspace pages in [[:Category:v0.40:Animals]] or [[:Category:DF2014:Animals]], but that would be less straightforward because there wouldn't be a namespace with that name (until pages are migrated when a newer major version is released). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 13:05, 7 August 2015 (UTC)

:Moving current pages to the main namespace sounds like a great idea. -[[User:Jecowa|Jecowa]] ([[User talk:Jecowa|talk]]) 20:47, 4 January 2018 (UTC)

Another thought: dealing with migrating redirects could be difficult with this proposal - specifically, determining which redirects should be migrated to a versioned namespace. Redirects can't contain {{tl|av}}, at least not before ``#REDIRECT``. I ''think'' it would be possible to copy pages in two stages, though - all non-redirects first, then all redirects whose targets were also copied. Thoughts? Anything I'm missing? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:41, 27 June 2019 (UTC)

Some subpages (particularly /raw and /Edit notice) also deliberately lack {{tl|av}}, although those shouldn't be too hard to handle. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:35, 9 July 2019 (UTC)

:Redirect pages (and all other edge cases I've looked at) can be included in categories (like [[:Category:Current]]) to determine whether or not they should be copied into an archival version. But if the redirects are "properly qualified" then they can all be copied over blindly. Mainspace redirects pointing to versioned information should use a blank namespace (which will be automatically constrained to the archival namespace); mainspace redirects pointing to unversioned information should use an explicit "Main" (which will automatically link back to the unversioned page). Then, when [[[[Toady]]]] gets copied to [[[[v0.4x:Toady]]]] it will point back to [[[[Main:Toady One]]]]. Meanwhile, [[[[Beer]]]], copied to [[[[v0.4x:Beer]]]], will properly point to [[[[v0.4x:Alcohol]]]].--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:00, 14 July 2019 (UTC)

::I think qualifying redirects is the best solution here - categorizing redirects manually is another possible source of errors, since categories (or a lack thereof) would only be visible on the redirect page itself, and [[:Category:Current]] is a hidden category. Copying over mainspace redirects into versioned namespaces would also resolve some issues that have come up due to those not reliably existing currently. I should be able to set up a bot script to add "main:" to current mainspace redirects (and it shouldn't break anything, since those redirects go to other mainspace pages anyway). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:57, 14 July 2019 (UTC)

(Note: I wrote all of this without noticing the previous discussion above.) I was wondering, when the wiki creates a new namespace for a major release again, if it is possible to ''not'' create a namespace for the next current version (e.g. "DF202x") and instead have the mainspace articles (which are currently redirects) become the new cv and move the content there. Therefore, [[cv:Cat]] would just be "[[Cat]]" (or [[Main:Cat]]).

Certain namespace-related templates like [[Template:Ns/0]] would need to be changed, though nothing significant as far as I know. For most cases, any "DF2014" would be replaced with "Main" or even blank. There's also multiple extensions handling the current namespace system and they may need to be modified too, though I'm not sure if or how much. I'm guessing based on the discussions above that it will change stuff up.

My reason is the current namespace is increasingly becoming more anachronistic. "DF2014" could be misinterpreted as "this page is about the 2014 version of the game" or "this page was last updated in 2014", which I've seen a few people in forums mention. Granted that [[Template:Av]] is on the top of very article, I still think the namespace is inconsistent with the recentness of the article. But how is this related to what I'm asking for? Let's say we continue the current system: if we happen to do a new namespace change this year and create DF2020, the next major release (after graphics/UI) will be mythgen, which is estimated to take several years to develop (the Big Wait), and so the anachronism will start over again. The proposed way will prevent this from occurring for the next major release and every release thereafter.

I think the confusion with having a namespace that becomes old-fashioned overtime supersedes the confusion with not marking current versioned articles with a namespace. Most users just search "Cat" on the search bar and naturally expect to get information about the latest release of DF. So if users go a page that's just titled "Cat", they won't expect outdated info about cats from a previous release. That's how the current system works anyways. We'll be skipping the two-step process that we have now. It'll make several wiki tasks much simpler as well. Editors can create new articles for current versions without remembering to add a namespace. It'll fix any existing issues with (double) redirects; instead of [[Main:Kitten]] redirecting to [[cv:Kitten]], which goes to [[DF2014:Kitten]], which then redirects to [[DF2014:Cat]], [[Main:Kitten]] would just redirect to [[Main:Cat]]. And the cv: alias will no longer be necessary since "cv:" = "Main:" and will be forever.

There's no need to differentiate the current version and previous versions with a namespace for the current version is what I'm saying. Articles of previous versions will retain their respective namespaces. Users will still type "40d:Cat" to go to the 40d version of the article, but if they want the current version, they'll just type "Cat" (like now). The mainspace containing the "live" version of an article is natural and would create no uncertainty when browsing the wiki. And it would simplify the wiki somewhat and future-proof this anachronism problem. As a bonus, this change will also prevent web search engines from showing previous version pages when typing "DF cat" or something. (This isn't happening right now as DF2014 has been the current namespace for ~6 years, but it'll happen again when everything moves to a new namespace.)

This is the gist of it, and I may have ignored most of the problems with this proposal. I have personally wished for the whole version namespacing be made less complicated and have been seeking for a solution, and I feel like this is the best way to go about in the future. – [[User:Doorkeeper|Doorkeeper]] 21:27, 14 August 2020 (UTC)

:<s>Whoops, looks like Loci already proposed this exact thing long ago. I definitely missed that discussion and should have checked first. My apologies. I'll move my text to that section and remove this one. – [[User:Doorkeeper|Doorkeeper]] 21:36, 14 August 2020 (UTC)</s> Done. – [[User:Doorkeeper|Doorkeeper]] 21:40, 14 August 2020 (UTC)

:The main issue I have with that is that putting pages about the current version in a namespace also differentiates between those pages and pages not about ''any'' version (for example, [[Toady One]] does not need a 40d or v0.34 page). Yes, we can use {{tl|av}} to mark versioned pages, but people often forget to add that to new pages. The current system also allows determining whether a page is versioned or not from its title, which makes migrations a lot faster. Relying on {{tl|av}} would require either reading the content of every page (which would slow scripts down significantly) or cross-checking with the list of all pages including the template (feasible, but a bit more complicated, and still susceptible to missing templates). I suppose that manually fixing and migrating pages missing {{tl|av}} later wouldn't be too much work, though.
:I am definitely in favor of changing "DF2014" (or a new namespace) to "Current", though. I was in favor of "DF2014" in 2014, but I don't think it makes sense anymore, and "Current" seemed to be a popular alternative in both the DF2012 and DF2014 discussions on the matter. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:02, 16 August 2020 (UTC)

== Weird redirect behaviour ==

[[Pump stack]] redirects to [[cv:Screw pump#Pump stack]]. If you look at the redirect itself it says it redirects to DF2014 namespace, which is correct. But if you actually follow the redirect, it goes to v0.34 namespace. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 16:10, 20 August 2018 (UTC)
:Yeah, that's part of the issue described in the above section (the wiki caching part, not on Google's end.) —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 15:00, 21 August 2018 (UTC)

== v50 organization ==

Some wiki admins have had a talk on Discord and decided that the most sustainable path forward is to put content for all future versions of DF in the main namespace. We will be working on a bot to do this in the next few days. Feel free to chime in with suggestions here. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:56, 14 December 2022 (UTC)

:Is it maybe possible to do backwards-namespacing? Like we have a "Main" namespace, which people are free to update, and whenever there's a new version of DF the "Main" namespace is copied into a namespace for the then old version, much like how you'd branch a stable branch from a development branch when working with a git-project? [[User:Therahedwig|Therahedwig]] ([[User talk:Therahedwig|talk]]) 23:13, 14 December 2022 (UTC)

::Yeah, we could do that if we decide to. We were talking about doing that for v50, actually, and might still do something similar to preserve edit history if it doesn't end up being too hard to automate. Our hope is that we will not introduce new namespaces for v50 -> v5x, unless there is a serious breaking change (and hopefully there isn't one). But if we change our mind, one advantage of the type of migration you mentioned is that it can be done retroactively - we can copy historical revisions that were current at the time of the release, and would only lose some typo fixes made after the release that apply to earlier versions as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:11, 15 December 2022 (UTC)

ETA is < 24 hours. Doing some final checks on a migration script. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 07:08, 19 December 2022 (UTC)

: We should really have a task list as there are many things that change and need updating. Including but not limited to:
:* Most templates that used the previous namespace convention broke, including nav templates.
:* Many game files changed locations and their pages need to be updated.
:* Raws need to be updated.
:* Various features added, changed, removed.
:* UI has been changed -- though I am more inclined to wait for classic release to avoid extra work --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 06:56, 20 December 2022 (UTC)

"''Raws need to be updated.''" Including applying text wraparound where necessary, I suppose - more than a few of them have proven to be that special kind of...''difficult'' to navigate otherwise, shall we say? [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 12:52, 20 December 2022 (UTC)

:There is already a task list in the [[#v50 migration|section below]] that includes templates and raws, with an explanation. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:25, 20 December 2022 (UTC)

== v50 migration ==

The initial migration script is done. New content is in the '''main''' namespace, e.g. [[Cat]]. Old content is still at [[DF2014:Cat]]. History was migrated to the ''new'' (main namespace) articles.

I know several things are broken still. Please reply if you find any others:
<div style="border-left: 2px solid red">
* <s>Versioned templates haven't been migrated yet (e.g. {{tl|vermin}} on [[Ant]])</s>
** Fixed. Most were migrated by a bot.
* <s>Raws are missing on all pages that use them.</s>
** This also affects sidebars, such as on [[Cat]] and [[Microcline]].
** Update: The DFRawFunctions extension has been upgraded to include v50 raws, using the "v50:" prefix for filenames instead of "DF2014:". <s>I haven't finished a migration script to create the /raw pages themselves, but they can typically be created manually by copying the DF2014 /raw pages and changing "DF2014" to "v50" everywhere.</s> —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:20, 1 January 2023 (UTC)
** Update 2: Raws have been added for all pages! They were copied from the "DF2014" pages and had "DF2014" replaced with "v50", which appears to have worked from a spot-check, but let me know if you find any problems. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:57, 4 January 2023 (UTC)
* Some pages where the DF2014 page was a redirect to a main namespace page that contained content were migrated incorrectly.
** In this case, the main namespace page is usually a redirect to itself. This can be fixed by undoing LethosorBot's edit to the main namespace page, then copying the content to the DF2014 page.
** Update: most seem to have been fixed manually - thanks! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:41, 21 December 2022 (UTC)
* <s>Some main-namespace talk pages redirect to DF2014 talk pages. Some of these redirects work, and some (usually older ones) do not.</s>
** Fixed with a bot. Some redirects from talk pages to other deleted talk pages are now broken, e.g. [[Talk:Above_ground]] (exists) -> [[Talk:Tile attributes]] (redlink). I am leaving them like that because they redirect to where the talk page should be created, but I'm also fine with people deleting them if they really want to. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:41, 21 December 2022 (UTC)
* {{tl|quality}} for new articles is disabled (see below)
* Some links from DF2014 to Main weren't working: e.g. the version selector [[DF2014:Mason's workshop]] was linking to [[DF2014:Main:Mason's workshop]] instead of [[Main:Mason's workshop]]. I'm not sure exactly why, but I fixed it with a change to the NamespaceLinks extension. Let me know if you spot similar broken links. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:19, 21 December 2022 (UTC)
</div>

—[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:54, 20 December 2022 (UTC)
:The quality levels of the 50.03 pages seem to be missing. I'm not sure if that's covered under that first point. [[User:Trainzack|Trainzack]] ([[User talk:Trainzack|talk]]) 06:47, 20 December 2022 (UTC)
::If the the [[Dwarf Fortress Wiki:Quality]] feature can be made to work with namespace scheme change, I suggest to automatically assign the lowest quality rating to all pages, alternately add the {{tl|old}} to all pages. Otherwise there will be a lot of pages that will fall through the cracks. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 09:12, 20 December 2022 (UTC)
:::I disabled {{tl|quality}} in the main namespace because it would require some rework to make the rating script and the template work properly there. Feel free to take a stab at the template. I will see what can be done on the extension side. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:14, 20 December 2022 (UTC)
::::What needs to be done on the template side? I'm not sure I see too big of an issue leaving pages as "unknown-quality" for now (or just change the default to tattered) until we get the rating script working. Is that script up anywhere, anything that could be helped with? [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 11:10, 2 January 2023 (UTC)
:::::They're already marked as unknown. Really the only issue I know of with the template is that it doesn't show up with some of the newer skins we added, and that can be fixed by getting rid of the absolute positioning. As for the script, it can be found at https://github.com/DF-Wiki/QualityRatings, and the issue is really only with the configuration system not recognizing the main namespace as valid. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:29, 3 January 2023 (UTC)
::::::Great, I started having a crack at fixing the template with different themes. Is the preference to get some CSS going and then include it in the global stylesheet (i.e different styles per theme) or to try and get a "one size fits all" fix? —[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 08:14, 3 January 2023 (UTC)
:::::::I would rather avoid custom site-wide CSS if we can. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:29, 4 January 2023 (UTC)
::::::::I appreciate that, I think it's the simplest solution to add a few lines to common.css though. Unless there is a way to attach CSS specifically to a template, I saw a few extensions that allowed that but I'm not sure if any are present in the wiki at the moment. Regardless there already exists a class `div.topicon` that is specifically for the quality ratings, is there an issue with expanding this class to accommodate the themes? The list of themes where the quality rating display is broken/invisible: Citizen, MinervaNeue, MonoBook. —[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 21:48, 4 January 2023 (UTC)
:::::::::What do you think of moving the template out of the topicon entirely and just placing it in a div? It would take up a (hopefully) small amount of vertical space in the article. [[User:Lethosor/Sandbox/Quality_test]] is an example. Unfortunately it isn't possible to prevent other templates from displaying above the quality this way ([https://dwarffortresswiki.org/index.php?title=User:Lethosor/Sandbox/Quality_test&oldid=283883]). So maybe we do need some custom CSS after all if we want that. I'm open to trying out whatever you propose. I'm a bit worried about future-proofing against skins we add later (particularly a mobile skin) but at least MediaWiki supports skin-specific global CSS as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:33, 5 January 2023 (UTC)
::::::::::I would rather we avoid taking any more vertical space in the article. The growing block pyramid at the top, starting with version template, is annoying. If you end up placing it inside the article space please use a slim box 100% wide that would include both.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 01:19, 5 January 2023 (UTC)
:::::::::::Agreed with you Jan, however I see that as two different tasks (ArticleVersion template changes, getting quality back on pages). I made a test adjustment to the quality and it takes up a negligable amount of extra space. See [[User:Vallode/sandbox#Page_quality]] for the example, we'd be able to completely remove "topicon" (unless it is used somewhere else?) and then potentially move on to making the ArticleVersion template into a slim version on the left-hand-side instead of a large box? Let me know what you think. --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 17:35, 5 January 2023 (UTC)
:::::::::::: Sorry, I just noticed this, I hope you weren't waiting on me. I haven't looked into how it works. All I can say that it would be nice if it shows on main, it is annoying that it shows on discussion and history. And otherwise I think that those negligible spaces adds up when you have multiple notice, redirection etc templates and would prefer if you can [https://ibb.co/X7X7SjL condense all of it] somehow. I also had [https://dwarffortresswiki.org/index.php/User:Jan/sandbox#Misc_variants couple of ideas] on that front, but as dev designer you probably can come up with something more refined if this is direction you choose. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 00:50, 10 January 2023 (UTC)

It appears some pages are redirecting recursively and never resolving correctly, like the [[https://dwarffortresswiki.org/index.php?title=Character_table&redirect=no|character table]] and [[tileset repository]] 07:35, 20 December 2022 (UTC)
: Indeed, these can be caught here: [[Special:DoubleRedirects]] --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:51, 20 December 2022 (UTC)

It might be useful to change the notice title to "release information '''for editors'''" --[[Special:Contributions/142.59.195.176|142.59.195.176]] 10:26, 20 December 2022 (UTC)
:Can do. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)
::New here, hello. Should we set a date where we remove/only show the banner for logged in users. There are (some) pages that have 4 different notices about the upgrade. [[Engraving]] is one such page, the top banner states "information for editors", we then have the "this page was migrated" banner, a version selection which warns the article might be inaccurate, and a smaller banner saying the page might need to be updated. Quite a lot of screen space, I think we can start to slowly reduce the amount of warnings this coming month? [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 10:07, 2 January 2023 (UTC)
:::Unfortunately, only showing info to logged-in users is difficult with how MediaWiki caching works. In terms of reducing warnings, there is a discussion [[Template_talk:ArticleVersion#.22Note_that_some_content_may_still_need_to_be_updated..22|here]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:43, 4 January 2023 (UTC)
:::As for [[Engraving]] specifically, the {{tl|old}} banner was actually present on [[DF2014:Engraving]] as well and got carried over with the migration. I removed it, and agree that it was redundant. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:46, 4 January 2023 (UTC)

Main talkpages seem to redirect to DF2014 talk. Not sure if it is intentional but I like it, though we should pay attention when creating new discussion relating to v50 ending up there.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 14:18, 20 December 2022 (UTC)
:That's unintentional. I specifically wrote the migration script to not move talk pages, but that has the side-effect of leaving any previously-created "Talk -> DF2014 talk" redirects intact. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)

Yo Lethosor, are we adding graphic sprites for the pages in some way? Or are we waiting for you to add some sort of new template or something? I'm sure you don't need me to tell you that the current templates don't allow that. Not sure if I'm allowed to change/create any templates either, as I don't want to break things for hundreds of pages. Edit: And IF the icons are allowed, should they be left alone, or 2×-3× sized like how the Minecraft wiki does it? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 14:29, 20 December 2022 (UTC)
:Depends on which templates you mean. There are copyright concerns with uploading a premium sprite sheet, for instance. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)
::I'm not talking about uploading an entire sprite sheet. I'm just talking about individual icons for each respective page. One image for cows, one for horses, one for werebeasts, etc. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 16:50, 20 December 2022 (UTC)
:::If we do that for every creature in the sprite sheet, that's not much different (in terms of copyright) from uploading the entire sprite sheet. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:09, 20 December 2022 (UTC)
::::Is there someone we can talk to about that? We finally get this new game with graphics, and then we can't use the very graphics of the game? No matter what the rules are, I'd say that would be the stupidest thing ever. I know I'm infamous here when it comes to copyright and images and stuff, but about 80% of game wikis out there are completely unofficial, and use game file images like no one's business. I can't imagine anyone's door being knocked on if we used the game's sprites, but I won't add any here until we have a go-ahead. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 17:14, 20 December 2022 (UTC)

:::::...I've made noise in Mayday's direction on this matter, at least (prob an incorrect maneuver, ''but'').[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 17:55, 20 December 2022 (UTC)
:::::: I hope some sort of arrangement can be made so we can use the new sprites with permission/limits, just as we are using the raw files. Otherwise we are all (devs and editors alike) shooting ourselves in the foot here.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 21:07, 20 December 2022 (UTC)

:::::::I just thought of something. We're supposedly not allowed to upload entire sprite sheets, right? What if - for the time being - we just use a few of them for the purpose of testing out new infoboxes? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 21:46, 20 December 2022 (UTC)
::::::::I don't know. If someone could ask Kitfox and post the response here, that would be great. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:47, 20 December 2022 (UTC)

:::::::::I've reached out to Alexandra, but she hasn't answered yet. Until then I found these old approvals from the previous community manager, Feeona: ([http://www.bay12forums.com/smf/index.php?topic=173474.msg8243633#msg8243633 link1], [http://www.bay12forums.com/smf/index.php?topic=176640.msg8243642#msg8243642 link2]). Waiting for a newer response until we begin mass uploads is probably the politer option, but like Zippy said, it is also standard for wikis to use game sprites with less approval. I second their idea of trying it out with a few images to test the infoboxes. On the extreme off-chance (and I do think it is) Kitfox protests we can always remove these few. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 22:19, 20 December 2022 (UTC)
:::::::::And here is a third, more official statement: ([http://www.bay12forums.com/smf/index.php?topic=173474.msg8249718#msg8249718 link3]). Perhaps that address of info@kitfoxgames.com is the better channel to ask for a confirmation, rather than Discord DMs, but I will be going to bed, so it is best if someone else does that. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 22:29, 20 December 2022 (UTC)
::::::::::Thanks for tracking this down! Ok, sprites should be fine, but let's avoid uploading the entire premium tileset as a single image, for instance (as the forum thread says, "use common sense"). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:21, 21 December 2022 (UTC)
::::::::::: Looks good, permission is always preferable over fairuse, I think it is a win win for all involved. I agree that we shouldn't upload entire sprite sheets (e.g. there is no reason to upload the windmill from every direction or whole construction phase for workshops) and that there are a lot of details that needs to be ironed out through testing. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 05:07, 21 December 2022 (UTC)
:::::::::We have a green light on uploading all and any sprites. Their response to me can be seen [https://i.imgur.com/BhmHjzC.png here]. I'm sure someone else confirmed it before me. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 19:00, 21 December 2022 (UTC)

Shifting temporarily to a new issue, is the documentation of [[Template:ArticleVersion]] outdated? It would seem so to me, since the current version no longer has its own namespace, with the templates needing updating being different ones. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 18:30, 20 December 2022 (UTC)
:I think it is still accurate enough. We left open the possibility of making another namespace in the future, albeit with a different migration strategy - see [[#v50 organization|above]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:52, 20 December 2022 (UTC)

Some Changes to infoboxes might be needed. Too bad [[User:Doorkeeper]] isn't around. He did a great work with navbox project--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:52, 21 December 2022 (UTC)

I just realized that raw files aren't stored as regular wiki pages but loaded via the DFRawFunctions extension (hence the need to update). Good news it's going to be handled in bulk, consistently and relatively easy to updated. Even better it's Lethosor problem ;) Also I just realized that all the "raw files" (txt files in the new vanilla folder) are released into the public domain. Both are probably not news to the vets but I'll leave it here for those who less up to date like myself. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:35, 22 December 2022 (UTC)

: I noticed that some templates aren't working properly in the new namespace, e.g. [[Basalt]] entry had its raw updated manually but the infobox fail to show any details. Cursory look suggest {{t|layerlookup/0}} need a minor tweak. This should do the work
:: Replace: <nowiki>{{layerlookup/aux|{{{{FULLPAGENAME}}/raw}}|uses={{{uses|}}}|wiki={{{wiki|}}}}}</nowiki>
:: With___: <nowiki>{{layerlookup/aux|{{</nowiki>:<nowiki>{{FULLPAGENAME}}/raw}}|uses={{{uses|}}}|wiki={{{wiki|}}}}}</nowiki>
: Not sure what the plan and ETA with raws update so I didn't touch this high usage template for now. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 08:11, 24 December 2022 (UTC)

::Please do feel free to make this update. I am still working on a script to create the <code>/raw</code> pages themselves. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:12, 1 January 2023 (UTC)

Wouldn't it be an idea to add to the Sitenotice to remove the {{tl|migrated article}} tag when an article has been fully updated? I see many articles that seem to be updated still have the tag. And/or advise to make use of the {{tl|verify}} for sections still in need of checking? --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 10:12, 2 January 2023 (UTC)
:Probably a good shout. The "see this page" link does include the detail on removing but we should more explicitly encourage removing the banner once a page has at least been looked over. [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 11:01, 2 January 2023 (UTC)

== v50 specific issues ==
=== Graphics===
Follow up on the use of game sprites and the need to trying it out with a few images to test the infoboxes. First sprite [[:File:Beds v50.png]] was uploaded and used on [[Bed]] entry. Any thoughts? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:06, 21 December 2022 (UTC)
:Seems like it should be rearranged to be horizontal. Also, has there been a serious discussion about copyright? Full screenshots are 100% fine, but you start going into a grey area when you upload pieces of a spritesheet. I'm of the opinion that it's all fine as long as it's inconvenient to reconstruct the full sheet from the individual images. Maybe a further restriction could be you shouldn't upload any of the art unless it's used in an infobox (maybe an exception for pieces of the UI). And one more restriction could be you shouldn't show everything, like in your bed example, maybe just the wooden bed is good enough, leave out the stone and metal, especially since those can only be made from strange moods. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:43, 21 December 2022 (UTC)
::Actually, your bed image is kinda bad for showing off what a bed looks like because it doesn't show the pillow/blankets. That might point to cropped screenshots being the best path, although less convenient for the uploader, as you don't get details left out. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:46, 21 December 2022 (UTC)
::I created a new license template [[Template:Copyright game]], based it on the way the RimWorld wiki does things. Call it a prototype, but it's probably how your bed image should be labelled. Indeed, I added it to it already. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]])

::: I agree that the horizontal arrangement would suit better here and that we should strive to represent how things look in-game. Otherwise, I am not too concerned about people being able to reconstruct anything (lets just say that ''anyone'' interested in that can get the real thing from the game files), also it seem we have permission to use the sprits on top of fairuse. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 19:55, 21 December 2022 (UTC)

::: Modifying the existing template to allow the inclusion of the new sprites is easy (Something like [https://ibb.co/zFXCrjd this]?) The big question is the matter of consistency is there any exceptions that will break the format (size wise with variant bloat for example), the sprite naming format, etc --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:44, 21 December 2022 (UTC)
::: If we are going to show a variant for each material type, then maybe these should be added as separate images so we can add a tooltip for each image. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:49, 21 December 2022 (UTC)

:I've got another prototype going here and here: [[User:Brightgalrs/vector.css]] and [[User:Brightgalrs/Sandbox]]. (You'll need to add the css stuff to your own /vector.css). Basically it's a way to recolor images using css classes. No idea if there's a better way. Also, the real implementation would require a change to [[MediaWiki:Common.css]]. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 22:41, 21 December 2022 (UTC)
:Should mention, there ''is'' a different way, just upload each image 16 times, one for each coloring. But maybe that's not very elegant. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 22:45, 21 December 2022 (UTC)

: It should be noted that soon the classic edition will be released, hence one should plan to have both the Premium and classic alongside in that little space --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 03:14, 22 December 2022 (UTC)
::I'm looking into a tab extension to potentially support this in infoboxes. Perhaps [https://www.mediawiki.org/wiki/Extension:Tabs Extension:Tabs]? I tried [https://www.mediawiki.org/wiki/Extension:TabberNeue Extension:TabberNeue], but it displays a placeholder if JavaScript is disabled, which isn't great. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:22, 22 December 2022 (UTC)
::: The Neue Tabber seem to works pretty much like the old one (which fandom [https://coding-help.fandom.com/wiki/Tabber#Adding_images_into_tabbers still use]) defaulting to showing the first tab only. Quick look suggest that neue work the same, plus the notice that 'Tabber requires Javascript to function' warning? if so, and if it is a bother, then you should be able to edit out the tabberneue-noscript string in code. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 06:29, 22 December 2022 (UTC)
::: I much prefer your tabber solution, but if that fails we can also use the gallery slideshow mode. If so, beware it has no way to control image size so the images have to be maliciously uploaded using the exact same size. example:
<gallery mode="slideshow">
File:SteelSample.png
File:TinSample.png
File:ZincSample.png
File:GoldSample.png
</gallery> --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 10:19, 22 December 2022 (UTC)

==== adding premium set to Infobox ====
I am unclear where are we going with this? 
1) Will (A) tabs be implemented, (B) we be using mediawiki toggle [[Template_talk:V50_workshop|example]] for premium and classic/blocked, (c) put images side by side, or (d) something else? 
2) Also [[silver]] and [[Pig iron]] use very different image style for example. 
3) Anything else you want ? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 12:32, 30 December 2022 (UTC)

: Personally, I would love tabs to be implemented, but I think that side by side might be best for most. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 12:32, 30 December 2022 (UTC)
: Here is rough layout we can use. It should fit most buildings given the default sprite size. There is also a different floor plan for both (inspired by reddit)

{|
|- valign=top
|
{| style="width:200px; background-color:#eaecf0; border-collapse: collapse; "
|+ 5×5
|- style="border-bottom:2px solid #3366cc; "
|<div class="mw-customtoggle-infoboxtab mw-ui-button mw-ui-progressive" style="border-top-right-radius: 10px; border-top-left-radius:10px;">toggle</div>
|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|- valign=top
|colspan=2|<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">
[[File:Siege workshop.png|center|160px]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab"">
{|
|rowspan=2 style="width:50%; font-size: 125%;"|<center>{{Template:Picture Siege workshop}}</center>
|style="line-height: 1em; font-size: 125%;"|
{| style="border-spacing:4px;"
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|}
|
{| style="width:200px; background-color:#eaecf0; border-collapse: collapse; "
|+ 3×3
|- style="border-bottom:2px solid #3366cc; "
|colspan=2 style="text-align: right;"|<div class="mw-customtoggle-infoboxtab mw-ui-button mw-ui-progressive" style="float:left; border-top-right-radius: 10px; border-top-left-radius:10px;">toggle</div>{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|- valign=top
|rowspan=2 style="width:50%;"|
<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">[[File:Carpenter's workshop.png]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab""><center>
{| style="font-size: 175%; border-spacing: 0; background-color: black; border: 2px solid black"
|- 
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"| {{Raw Tile|"|7:0:0}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|{{=}}|6:0:0}}
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"|
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|]|0:0:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
|}</center></div>
|
{| style="border-spacing:5px;"
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|
{| style="width:200px; height:100px; padding:10px; background-color:#eaecf0; border-collapse: collapse;"
|+ 1×1
|- style="border-bottom:2px solid #3366cc;"
| colspan=3 style="text-align:center;"|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|-
| style="border-right: 1px dotted #545557;"|[[File:Screw_press.png|32px|center|link=]]
| style="font-size:125%;"|<center>{{Template:Picture Screw press}}</center>
| style="border-left: 1px dotted #545557;"|<center>{{Template:Floor Plan Screw press}}</center>
|}
|
{| style="width:200px; height:100px; padding:10px; background-color:#eaecf0; border-collapse: collapse;"
|+ 1×3
|- style="border-bottom:2px solid #3366cc;"
| colspan=3 style="text-align:center;"|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|-
| style="border-right: 1px dotted #545557;"|[[File:water_wheel.png|32px|center|link=]]
| style="font-size:125%;"|<center>{{Template:Picture Water wheel}}</center>
| style="border-left: 1px dotted #545557;line-height:normal;"|<center>{{Template:Floor Plan Water wheel}}</center>
|}
|}
:Any thoughts on the direction and or any and all of its elements? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 10:16, 31 December 2022 (UTC)

::I kind of like side-by-side, if it fits. If anyone wants to implement a toggle button or tabs, I would ask that that be implemented in a template for now, so that e.g. we could change a toggle button to tabs in a single place if we decide to install an extension to support that. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:14, 1 January 2023 (UTC)

::: I noticed a comment saying that [[impassable tile]] are no longer used in v50, is that true for all constructions? If so, floor plans are no longer needed, making things much easier as we can fit everything in except the 5v5 constructions like trade depot (and even these can be placed one above the other if so desired). If not, any thought on the alternative floor plan design? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:46, 1 January 2023 (UTC)

:::: None of the constructions have blocking tiles any more from my experience playing. I haven't tested siege weaponry with that stuff, but none of the workshops have it, nor does any furniture. (walls and fortifications will of course obstruct movement [[User:AndrielChaoti|AndrielChaoti]] ([[User talk:AndrielChaoti|talk]]) 18:47, 1 January 2023 (UTC)
::::: Ok, I have removed them from v50. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 23:48, 1 January 2023 (UTC)

I have added a basic side by side variant to [[Template:V50 workshop]] and [[Template:Building]] for testing, let us know if there any issues. Few notes:
* The default image naming scheme of <code>workshop-name.png</code> will likely conflict with existing images here or on commons, maybe another naming scheme should be used like <code>v50 workshop-name.png</code> as it is with ascii pictures.
* There is inconsistency in image size. If you want to use large zoomed images then toggle is best, otherwise they need to be all in native size (96px for 3x3).
* In the current version the code roughly centers the images and if there is a big image like with [[Siege workshop]] it drops to a new line --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 23:48, 1 January 2023 (UTC)

How about combining shortcut keys and the new menu icons:
<div style="color:white; font-size: large; text-shadow: -1px -1px 0 #000, 1px -1px 0 #000, -1px 1px 0 #000, 1px 1px 0 #000;">[[File:Ui b.png]]<div style="position: absolute; bottom:-14px; right:3px;">b</div>[[File:Ui bo.png]]<div style="position: absolute; bottom:-14px; right:3px;">o</div>[[File:Ui bol.png]]<div style="position: absolute; bottom:-14px; right:3px;">l</div>[[File:Ui boll.png]]<div style="position: absolute; bottom:-14px; right:3px;">l</div></div>
--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 02:24, 3 January 2023 (UTC)

:I worry that this is difficult to read (I read it as "boil" at first). I would rather use something like {{tl|k}} with a known background. What about something like this? [[File:Ui boll.png]]<div style="position: absolute; bottom:-14px; right:0px;">{{k|l}}</div> or, alternatively, using flexbox without any overlap: [[File:Ui boll.png]]{{k|l}} —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:37, 3 January 2023 (UTC)
:: Same, but that is the best I came up with. We can use the key or maybe someone can help improve the design. Also 'l' is hard to read even with {{t|key}}.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 03:05, 3 January 2023 (UTC)
:: I added a {{t|Menu icon}} to start things so others can have a go with it. Also any thoughts on the icon naming convention (their shortcut sequence), is there easier/better way? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 09:36, 3 January 2023 (UTC)
::[[User:BarelyCreative]] updated the template: {{Menu icon|b|o|l|y}}. I think it looks good, thoughts? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:40, 3 January 2023 (UTC)
:::I like that, yeah. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:29, 4 January 2023 (UTC)
::::There were some places where it didn't make sense so display every icon all the time (like step-by-step guides), so I changed it slightly to allow display of fewer icons using "num" and counting from the end: <nowiki>{{Menu icon|b|o|l|y|sep=-;|num=2}}</nowiki> {{Menu icon|b|o|l|y|sep=-|num=2}} [[User:BarelyCreative|BarelyCreative]] ([[User talk:BarelyCreative|talk]]) 09:05, 4 January 2023 (UTC)

==== Bizarre palette-swapping idea/prototype ====
No idea if this is a good idea, since it takes a bit of time to set up, and there might be some performance issues... and maybe display issues?

But take a look at this:
{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock|palette-name=amber}}

It's way to swap palettes on an image, although the image itself is a table, with each cell representing a pixel. The template itself looks like this:
<code><nowiki>{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock|palette-name=saffron}}</nowiki></code>
Input the pattern and desired palette name.

I've got a larger showcase here: [[User:Brightgalrs/Sandbox/PaletteSwapShowcase]]. Only did a rock pattern so far, but all palettes are implemented.
The major use for this would be on each stone, metal, wood, etc. type's page. The palette could be read directly from the raws. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 03:22, 24 December 2022 (UTC)

:From a technical perspective, my primary concern is indeed performance. Both on the server side and client side, a large number of tables that large (in terms of markup and cell count, that is) tend to be resource-intensive to generate and render. I saw your image-filtering experiments on [[User:Brightgalrs/vector.css]], and while that strikes me as a newer and less-backwards-compatible approach, it would probably be more resource-friendly.
:Is this color adjustment something the game is doing natively? i.e. does this accurately match what the game displays? I bet we could slap together an image-filtering extension (or find an existing one?) that can do this if needed. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:49, 24 December 2022 (UTC)
::Yeah that's what I suspected. The images the template creates are spot on, checked it against a screenshot I took of some mica rocks in-game. The css stuff is unfortunately totally incorrect, was cool to learn about it though, so not a complete waste of my time :p. The premium, in-game graphics are true sprites, basically patterns of indexed colors. Each of the in-game colors (which are significantly expanded over the 16 ascii colors, there's 116/117) there is a palette defined in "\Dwarf Fortress\data\vanilla\vanilla_descriptors_graphics\graphics\images\palettes.png". Each indexed color of the sprite is swapped for the corresponding color in the palette. Because of that, the css stuff doesn't work since it's doing the hue/saturation/brightness changes to the entire sprite.
::I've looked into an existing mediawiki extension, couldn't find anything. One thing I did't really look at is some type of lua script/module that would basically emulate what the game is doing. So some function that takes in the base image as well as the desired palette, and based on that finds and replaces each color. No idea what mediawiki's capabilities are on that front. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 05:31, 24 December 2022 (UTC)
:::We do have Scribunto installed now, so it's totally possible to do something in Lua too - forgot about that. I can add you to the group that grants access to edit the Module namespace if you want to give that a shot. If we use an extension, we'd probably need a custom one, similar to DFDiagram (or perhaps DFDiagram could be extended - it's in dire need of a rewrite anyway). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:43, 24 December 2022 (UTC)
::::I asked around on the mediawiki irc, I think scribunto/lua is a deadend, at least for taking an uploaded image and doing stuff to it with a lua script. However I did come up with this even more bizarre solution, using block elements. [[User:Brightgalrs/Sandbox/PaletteSwapShowcase2]], maybe less resource intensive? Definitely displays a lot worse though, probably unusable.
::::{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock2|palette-name=saffron}}
::::I dunno, maybe none of this is worth it and we should just write some external program to put all the images together offline, and then just mass upload. It wouldn't be ''that'' many... [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 06:37, 24 December 2022 (UTC)

====Is there an easy way to just paste images from the clipboard?====

I use KDE spectacle to take screenshots straight to the clipboard (after cropping) -- is there an easy way to just paste (and auto-upload) an image into an article? It would make it a lot easier to contribute images. [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 23:35, 1 January 2023 (UTC)
:Unfortunately there is not. I would be open to a MediaWiki extension to support this if someone finds one. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:32, 2 January 2023 (UTC)
:: Looks like this could do it, but I haven't used it before: https://www.mediawiki.org/wiki/Extension:SimpleBatchUpload [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 19:41, 2 January 2023 (UTC)
::: It won't solve paste-from-clipboard, but this would be great for making uploading sprites much easier (auto-cutup spritesheet, rename, bulk upload). Could you add this, Lethosor? [[User:OddballJoe|OddballJoe]] ([[User talk:OddballJoe|talk]]) 21:47, 6 January 2023 (UTC)

====Standards for adding graphical version screenshots and images====

Hello, new user looking into adding imagery from the new version. Is there a standard for quality of new screenshots or images? I noticed that at a certain zoom level (2 zooms in from the furthest zoomed-out view), the graphics appear crisp and 1:1 pixel scaled, and I would propose that all images be taken at this scale whenever possible. If they need to be displayed larger, they should be nearest neighbor scaled in a photo editing program at 100% increments (Microsoft Paint will do this if you first select the image rather than directly scaling the whole canvas). I would also propose that images should be cropped to conform to the 32x32 pixel grid when possible, though this could be problematic with so many new graphical elements exceeding the bounds of their tiles. I would say the best practice for capturing artwork for items, furniture etc. ought to be done in a 3x3 open area to avoid shadows from nearby walls, or else extracted from the raw files (if this doesn't run afoul of being able to re-create the graphical version using those assets).

I know that perfect is the enemy of good, and any documentation is better than none, but just thought I'd ask about this, and see if/where something like this ought to be posted. [[User:Unclesporky|Unclesporky]] ([[User talk:Unclesporky|talk]]) 13:58, 3 January 2023 (UTC)
:It has been stated in [[Template:V50 workshop]] that <q>screenshots should be at the "native" resolution</q> but someone could edit the [[Screenshot]] page for best practice for the steam version. Or post some examples in [[Talk:Screenshot]] to find out what is best? --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 14:21, 3 January 2023 (UTC)

====How would I/should I go about putting creature sprites on their pages?====

Howdy. New player and wiki user here. I wanted to try and help update the wiki to the Steam release of DF, so I figured I'd chip in by putting each creature's sprites on their respective page, since I'll often look up a creature I have yet to see in game only to be met by a blue J, or whatever. I found all of the game's creature sprites in C:\Program Files (x86)\Steam\steamapps\common\Dwarf Fortress\data\vanilla\vanilla_creatures_graphics\graphics\images, so I figured I could just chop those up in Photoshop and stick them on here no problem, but the programming syntax/whatever it is on this site is incredibly confusing, I don't know how I'd actually go about doing it. I figured I'd just find the spot on the page where the little letter is and replace that with the image code, but it seems the pages are built using heavily nested templates that I can't even begin to understand. Any help?--[[User:Treese|Treese]] ([[User talk:Treese|talk]]) 03:07, 5 January 2023 (UTC)
:Based on [[User:Zippy|Zippy]]'s work at {{tl|Creaturelookup_b}}, I added an "image" parameter to {{tl|creaturelookup/0}}, which is what creature pages should all be using. See [[Dwarf]] and [[Cow]] for examples. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:37, 5 January 2023 (UTC)

=== Hotkeys/Menu navigation ===
Most key bindings and menus have changed. Should the article reflect a) only the old version, b) only the GUI version or c) both? For example, [[Bridge|bridges]] used to be built via {{k|b}} -> {{k|g}}, but now it's in Place strucutures {{k|b}} -> Constructions {{k|n}} -> Bridge {{k|b}}. What should be written in the article? Currently, it's {{k|b}} -> {{k|g}}. I ''think'' it should be only b), but I am not sure if there will be differences regarding hotkeys or menus between the premium version and the free version and then, c) would be the most appropriate option. --[[User:Prometherus|Prometherus]] ([[User talk:Prometherus|talk]]) 10:16, 22 December 2022 (UTC)

: Not sure. I wish the classic release soon --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 16:45, 22 December 2022 (UTC)
:: Are you Toady's herald? Looks like it was just released! [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:18, 22 December 2022 (UTC)
:: And our questions are answered, the old hotkeys seem to have been thrown out. Part of me is disappointed (useless muscle memory) but also relieved (unified UI for both versions is good in general and for the wiki). [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:25, 22 December 2022 (UTC)
::: According to info, in a sort of 'demo version' at that. I'll wait a little while longer, for myself.[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 18:22, 22 December 2022 (UTC)
::::It's unlikely that keybindings in it will change significantly. My vote is that we should include information for both premium and classic, everywhere. Hopefully the keybindings are not different between versions. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 18:26, 22 December 2022 (UTC)
:::Shouldn't it be based on the 50 or what verion the article is written for? [[User:Dominick|Dominick]] [[User_talk:dominick|(TALK)]] 18:42, 22 December 2022 (UTC)
:::: The keybindings seem to be consistent between versions, (haven't checked exhausitvely, but since the menu layout is the same I think it is a good assumption). Should also keep in mind/consider that not all actions have keybindings. An option would be write 'Click on the <Example Text> icon or press {{k|E}}' [[User:Koos|Koos]] ([[User talk:Koos|talk]]) 23:14, 23 December 2022 (UTC)

=== Removed features & concepts ===

Since they're removed concepts, I've set [[Room]] to be a redirect for [[DF2014:Room]] and created [[Template:Activity zones]] for the nav bar bedrooms, etc, and made the necessary changes to [[Bedroom]] for it. Is this the correct approach, before I go on much further? (also a note, if it is, then [[Template:v50_rooms]] probably needs to be deleted) I also imagine that considering the number of changes in the interface, that things like [[Adventure mode]] and related pages might best be truncated to "not in 50.03" and when it does make it across, being more deliberately brought over in pieces? [[User:HawkOwl|HawkOwl]] ([[User talk:HawkOwl|talk]]) 06:23, 23 December 2022 (UTC)

:Usually it is marked with [[Template:Removed_feature]]. For example: [[Dipscript]] or [[Party]]. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:45, 23 December 2022 (UTC)

:: Ah, that's fair. Should that be mentioned in [[Dwarf_Fortress_Wiki:Versions#Redirects]]? [[User:HawkOwl|HawkOwl]] ([[User talk:HawkOwl|talk]]) 10:03, 23 December 2022 (UTC)

:::I think the redirect policy mostly had in mind things that were removed a ''long'' time ago, like [[Tax collector]] and [[Economy]] (and the latter actually has a stub page as well). I guess we could clarify. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:34, 23 December 2022 (UTC)

:::: The "current" redirects also cause the version box to incorrectly show that the current version has a page - e.g. [[23a:Cave_river]] shows a v50.04 version, but it's just a redirect back to that version. Similarly, what should happen to redirects like [[Clothes maker]], where a concept has evolved? It currently goes to [[23a:Clothes maker]] - that's correct if the user is trying to look up a very old concept, but if a new user is looking for "how to make clothes", they should be directed to [[Clothier]]. --[[User:Danny252|Danny252]] ([[User talk:Danny252|talk]]) 12:16, 26 December 2022 (UTC)

:::: One should be careful with cv redirects. Most that were recently adjusted were unused plural forms (that should probably be deleted) but few like [[Crown]] needed that for backward compatibility. Removing the [https://dwarffortresswiki.org/index.php?title=Crown&type=revision&diff=279966&oldid=219482 cv part] means the the link on [[v0.31:Tilesets]] is now broken. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 22:30, 26 December 2022 (UTC)

:::::If [[v0.31:Tilesets]] is about v0.31, it should not be using "main:" in its links - ''all'' of those links are going to pages about v50, not v0.31, regardless of whether the target is a redirect or not. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:37, 26 December 2022 (UTC)
:::::: You right, I removed it. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 17:55, 27 December 2022 (UTC)

Crown cv redir issue is now fixed, I believe. As goes with such cases where one can simply revert the troublesome edit, unless I've mistepped, myself? [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 23:52, 26 December 2022 (UTC)
:Both [https://dwarffortresswiki.org/index.php?title=Crown&diff=prev&oldid=280026] and [https://dwarffortresswiki.org/index.php?title=Crown&diff=prev&oldid=279966] should not have had any effect, because "cv" is an alias to the main namespace now, just like "main". Proof: [[Crown]], [[cv:Crown]], [[main:Crown]]. It's possible caching is coming into play here, although I purged the redirect cache after making that alias change earlier this month... —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:02, 27 December 2022 (UTC)

I think there have been some changes not captured, but as a newb, I'm afraid to edit the page(s). A good example is Strawberry. I'm playing the Steam version right now and Strawberry plants are "not relevant to brewing" in Labor > kitchen > veg / fruit / leaves. Unless I'm mistaken and need to process them? Another example is the trade caravan = it seems the 3 square pathing no longer happens; it's just yak(s). 12:31, 28 December 2022 (UTC) 12:29, 28 December 2022 (UTC)
:Strawberries should be brewable according to the Raws.
:Trade wagons has been modified in v50. The first wagons will arrive at the same time your fort is becoming a barony. Until then, it's only pack animals and stairs are indeed fine. The [[Trading]] page needs a huge rework anyway... I'll try to do that next week. --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 13:40, 2 January 2023 (UTC)

<s>As far as I can tell, none of the workshop buildings in v50 have blocking tiles any more. There's a comment to the like in data/vanilla/vanilla_buildings/objects/building_custom.txt that says this "[BLOCK:1:0:0:0] workbenches no longer block". Hesitant to update that template as I'm not sure if it's referenced for all of the old versions too. </s> [[User:AndrielChaoti|AndrielChaoti]] ([[User talk:AndrielChaoti|talk]]) 05:54, 29 December 2022 (UTC)
: A new template has been created: {{tl|V50 workshop}} --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 13:40, 2 January 2023 (UTC)
::Thanks! In general, I would like to delegate the switching responsibility to the template (like how {{tl|creaturelookup/0}} works), but in cases where the parameters diverge significantly like with workshops, it could make sense to make an entirely new template. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:40, 3 January 2023 (UTC)

=== creature infobox prototype (moved) ===

Check it out, I made a temporary template and added it to the [[cow]]s page. Now it shows the sprites (but not the zombified versions yet). I wanted to show everyone a prototype of what v50 creature infoboxes should look like. Or at least something similar to it. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 19:11, 27 December 2022 (UTC)
:Hi, I'm new to editing wikis but I have done a bit of work with sprite sheets and I've been going through the DF data files to find the different graphics hoping to help with the animal pages. I've thrown together a template with grass and a few nature sprites (plants, a tree, and a rock) for size reference but I'm unsure how large the 'display' tiles in the middle of the template should be to suit all animals. I can see in the sprite sheets that some land animals have an adult and child sprite, so two tiles. Others have a male, female, and child, but after seeing you include the zombie cows I'm unsure if I should make it twice the size to add them too. Alternatively, I could grab some tiles from the haunted biomes for the zombie animals and make a separate template for a side-by-side comparison. Either way, let me know if this helps. I'd like to help with other graphics too as we add the premium tilesets but the animals seemed the easiest to tackle with me being new to wiki editing. ~~[[User:UristTheSeventh|UristTheSeventh]] ([[User talk:UristTheSeventh|talk]])
::@Zippy, I am a bit perplexed about the purple cows. Why do we need a zombified version of creatures on every page?
::@UristTheSeventh, we can use all the help. Maybe post an example, so that we can have something to compare and contrast.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 11:49, 3 January 2023 (UTC)
:::@Jan Here are the examples:
:::[[File:Creature template.png]] [[File:Armadillo.png]] [[File:Seagull.png]]
:::It'll need to be wider or arranged differently for different creatures with more that two sprites or for multi-tile creatures. I can also do an aquatic and air themed template for swimming and flying creatures. ~~[[User:UristTheSeventh|UristTheSeventh]] ([[User talk:UristTheSeventh|talk]])
::::Looks nice, like the metal template. There are several people working on updating the graphics you should talk more among yourselves. Best I can offer is that I width wise I am hoping to go up to 200px for infoboxes.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 01:13, 5 January 2023 (UTC)
:::: We don't exactly ''need'' a zombie sprite on each page. I added it because it was... there. I was also hoping to get some opinions on it anyway since that infobox is a visual prototype, and not a final choice. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 03:28, 6 January 2023 (UTC)

===Furniture Infobox===
{{Quality|Unrated}}
{{v50_furniture|name=Bed
|graphic=[[File:bed_sprite_prototype.png]]
|tile=Θ|col=6:0:0
|wood=y
|rooms=
* [[Bedroom]]
* [[Barracks]]
* [[Dormitory]]
|value=10}}
I made a v50 furniture template prototype. I tested this on Firefox, Chrome and Microsoft Edge/Internet Explorer and it looks fine on all of them. I hope this is good enough to be the official thing, unless I'm missing something. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 03:28, 6 January 2023 (UTC)
{{clear}}

=== When do we remove the migration note on specific pages? ===

At what point can we remove the "this page was auto migrated from v47" warning? There are a bunch of small pages that are more or less accurate, if I've reviewed them, can I go ahead and remove the warning? [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 23:33, 1 January 2023 (UTC)
:Yes, feel free to remove it if you think all content is accurate. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:31, 2 January 2023 (UTC)

=== Any info on fixing "creature description not found?" ===

I see this issue on most creature pages, it seems to be due to a lookup that's not currently functioning? Cows interestingly doesn't have this issue but I couldn't figure out how to recreate whatever fix it's editor did. --[[User:Yallendallis|Yallendallis]] ([[User talk:Yallendallis|talk]]) 00:22, 3 January 2023 (UTC)
:That is the missing raws issue described above. Cow was fixed by the addition of [[cow/raw]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:28, 3 January 2023 (UTC)
::Ah makes sense, not fully used to the language of wikis yet so I read over it while looking. To put this bit of questioning to rest for any future readers, is it correct that it's fine to update any raws manually, though it will be done automatically at some point? --[[User:Yallendallis|Yallendallis]] ([[User talk:Yallendallis|talk]]) 07:48, 3 January 2023 (UTC)
:::Yes. I'm circling back to work on a script right now, so not much point in doing it if you're reading this. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:57, 4 January 2023 (UTC)
:::This should be fixed now. If you continue to see pages with problems, you can try [https://www.mediawiki.org/wiki/Manual:Purge purging the cache]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:59, 4 January 2023 (UTC)

=== Adventurer Mode related sections ===

The topic has already been discussed [[#Removed features & concepts|above]], but I don't see a clear line on what to do with article sections that mention Adventurer Mode. Like for example in [[Butcher#Adventurer_mode|Butcher]].

'''a) Truncate''' or '''b) leave in place with a mention''' that the mode is not yet present IG but will be added in a future update?

Personally I think option b) is better, because I think it's silly to undo some work just to reintroduce it a few weeks later, with the necessary corrections. Even if a copy/paste of a previous version takes ~15 seconds, considering the number of articles that need to be corrected, it would be a bit of a waste of time.--[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 14:22, 3 January 2023 (UTC)

== Toggleable image ==

Any objections/comments to using this template for now for toggling between classic and premium images? I'd probably rename it to "Template:Premium-classic thumb image". I'm sure someone can come up with a better UI eventually, but should be easy to migrate at that point. I also think we should use the same customtoggle class for this and for the infobox. [[User:NiftyManiac|NiftyManiac]] ([[User talk:NiftyManiac|talk]]) 23:12, 1 January 2023 (UTC)

{{User:NiftyManiac/Sandbox/TemplateDualImage|
premium=File:Quickstart-finder.png|
classic=File:Quickstart-finder-partial.png
}}

{{User:NiftyManiac/Sandbox/TemplateDualImage|
premium=File:Quickstart-finder.png|
classic=File:Quickstart-finder-partial.png|
caption=My caption|
width=100px
}}

:This looks nice to me! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:30, 2 January 2023 (UTC)

: Good initiative. From the top of my head:
:* I suggest using a shorthand, no one wants to type 'Premium-classic thumb image'.
:* If we end up using toggle for infoboxes (not sure where we headed there), then I agree definitely same custom toggle class should be used for all, thus allowing to switch premium-classic view on the whole page at a click.
:* The button part on a separate row isn't pretty, creating a lot of dead space that can be used by the text. Are we set on the label 'toggle ascii'? Classic isn't Ascii per se, maybe we can use a 'toggle' with a tooltip {{tooltip|for example|does bla bla bla}}, or maybe we can get rid of the text and have a smaller icon button ([[User:Jan/sandbox#Metal_example|two examples]]).
: I hope that helps. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 11:21, 2 January 2023 (UTC)

:: I added [[Template:Dual image]] with some of your suggestions. Agree that it's not super pretty, feel free to try something different.

::* I put the toggle in the caption mostly because I gave up on trying to make a more sophisticated replacement for the default thumb image behavior, I'm sure someone with better wiki-fu could put together something more intelligent.
::* I cut the text down to just "Toggle"; I think the best solution would be a small graphic showing the old and new dwarf icons with arrows between them. [[User:NiftyManiac|NiftyManiac]] ([[User talk:NiftyManiac|talk]]) 19:21, 2 January 2023 (UTC)

{{Dual image|
premium=File:DFwiki5by53by3farm.png|
classic=File:Quickstart_layout_3.png|
width=100px|
caption=A 5x5 room with a 3x3 farm plot
}}
::: I updated the layout, now it should look just like a regular image thumb. I didn't had time to test it, if it doesn't work for you or you don't like it just revert the last change. cheers. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 21:46, 2 January 2023 (UTC)
::::I don't know which part of this talk page to put this, but I added the ability to add icons to the v50 workshops template. Leaving the icon part blank will not break the template in any way. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 09:47, 3 January 2023 (UTC)
{{clear}}
==Creature List Now Supports Graphics!==
I wasn't easy, but I made new templates so the [[Creature]]s page now supports both graphics sprites ''and'' ASCII tiles. Allow me to show you:

{{v50_creaturecurrent_table_head}}
{{v50_creaturecurrent table row|graphic=[[File:dwarf_sprite.png]]|name=[[Dwarf]]|symbol=☺|color=3:0:0|playable=Fort, Adv|hostile=No|food=No|size=60,000|value=Not tameable|biome=[[Mountain halls]], [[Fortress|dwarf fortress]]es, [[hillock]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:elf_sprite.png]]|name=[[Elf]]|symbol=e|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=60,000|value=Not tameable|biome=[[Forest retreat]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:human_sprite.png]]|name=[[Human]]|symbol=U|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=70,000|value=Not tameable|biome=[[Town]]s and cities|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:goblin_sprite.png]]|name=[[Goblin]]|symbol=g|color=7:0:0|playable=Adv|hostile=Usually1|food=No|size=60,000|value=Not tameable|biome=[[Dark fortress]]es and [[dark pit]]s|note=Snatchers2}}
{{v50_creaturecurrent table row|graphic=[[File:kobold_sprite.png]]|name=[[Kobold]]|symbol=k|color=6:0:0|playable=Adv|hostile=Usually1|food=No|size=20,000|value=Not tameable|biome=Caves|note=Skulking race}}
|}

Oh wait, there's a bonus. You can also modify the background color of the box the sprites go in. I added that to make possibly-hard-to-see-otherwise sprites more easy to see - depending on the colors it has. Allow me to demonstrate.

{{v50_creaturecurrent_table_head}}
{{v50_creaturecurrent table row|graphic=[[File:dwarf_sprite.png]]|bgcolor=#829ccc|name=[[Dwarf]]|symbol=☺|color=3:0:0|playable=Fort, Adv|hostile=No|food=No|size=60,000|value=Not tameable|biome=[[Mountain halls]], [[Fortress|dwarf fortress]]es, [[hillock]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:elf_sprite.png]]|bgcolor=#c7dfc0|name=[[Elf]]|symbol=e|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=60,000|value=Not tameable|biome=[[Forest retreat]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:human_sprite.png]]|bgcolor=#c7dfc0|name=[[Human]]|symbol=U|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=70,000|value=Not tameable|biome=[[Town]]s and cities|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:goblin_sprite.png]]|bgcolor=#dfc0c0|name=[[Goblin]]|symbol=g|color=7:0:0|playable=Adv|hostile=Usually1|food=No|size=60,000|value=Not tameable|biome=[[Dark fortress]]es and [[dark pit]]s|note=Snatchers2}}
{{v50_creaturecurrent table row|graphic=[[File:kobold_sprite.png]]|bgcolor=#dfc0c0|name=[[Kobold]]|symbol=k|color=6:0:0|playable=Adv|hostile=Usually1|food=No|size=20,000|value=Not tameable|biome=Caves|note=Skulking race}}
|}

To change the background color, add <code><nowiki>|bgcolor=COLOR</nowiki></code> segment after the <code><nowiki>|graphic</nowiki></code> part. You can use color names or HTML hex color codes. I added this to the v50 creatures page, but at this time, I only added the first five creatures I just displayed. It's gonna take a while to find ALL of those creature sprites. I hope a lot of people help out on that one. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 05:29, 5 January 2023 (UTC)

:Thanks, looks nice! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:44, 5 January 2023 (UTC)
:Nice stuff, took the quick liberty to change the padding-left -> text-align to make all the sprites center aligned relative to each other :) Sweet work --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 17:41, 5 January 2023 (UTC)
:: Good work indeed. One minor issue, is that all the sprites have different sizes, which sometimes create slight variation in table row height. Consider using capping the image size vertically for example <code><nowiki>[[File:dwarf_sprite.png|x32px]]</nowiki></code>--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:15, 5 January 2023 (UTC)
:: Also often in such tables people want to click on the image to go for the specific entry, and often will try to click on the very first thing they see in line the thumb image, but currently that will take them to the file page. Consider adding link parameter for example: <code><nowiki>[[File:dwarf_sprite.png|x32px|link=dwarf]]</nowiki></code> [[File:dwarf_sprite.png|x32px|link=dwarf]] or no link at all <code><nowiki>[[File:dwarf_sprite.png|x32px|link=]]</nowiki></code> [[File:dwarf_sprite.png|x32px|link=]] --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:24, 5 January 2023 (UTC)
::: I mean... Yeah, I could do that. I think that lessens the quality of the sprite a bit because it makes edges blurry, but either way is fine. I could have sworn I added a link for all those images the first time. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 03:23, 6 January 2023 (UTC)
::::Since we are adding pixel art sprites to the website it might be convincing to add a global class like .sprite or .pixel-image that uses the CSS attribute `image-rendering: pixelated;` in order to prevent blurryness when scaling the image up/down. Just a thought --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 09:40, 6 January 2023 (UTC)
:::::Are we able to attach classes directly to images? If so, we can probably attach inline styles directly as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:52, 6 January 2023 (UTC)
::::::Looks like (without an extension) MediaWiki only supports classes on images: [[File:dwarf_sprite.png|x32px|class=pixelated]] and not styles: [[File:dwarf_sprite.png|x32px|style="image-rendering: pixelated;"]] it just treats it as alt text it looks like? Wrapping it in a div works and demonstrates the difference: <div style="image-rendering: pixelated;display:inline;">[[File:dwarf_sprite.png|64px]]</div> [[File:dwarf_sprite.png|64px|inline]]. Speaking from experience, however, image-rendering needs a browser specific prefix in certain browsers (safari, for example) in order to work properly. I'm not entirely sure what the best "MediaWiki" practice is for adding something like this but I would assume it's a simple class in common.css for now. --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 17:17, 6 January 2023 (UTC)
:::::::Ah, yeah, you are correct, I should have checked https://www.mediawiki.org/wiki/Help:Images. I'd be fine adding a class like that to common.css. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:27, 6 January 2023 (UTC)
::::::::Great, in that case if no one is opposed we can add `.game-sprite` or something like that? See below for the CSS, the order of the attributes is relevant. --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 18:23, 6 January 2023 (UTC)
<pre>/* Used for pixel-art images from the game so they can be resized and maintain crisp pixel edges. */
.game-sprite {
image-rendering: -webkit-optimize-contrast;
image-rendering: crisp-edges;
image-rendering: pixelated;
}</pre>
:::::::::So... you guys think each creature page should show the main sprite(s) alone, or should it show the baby versions alongside them? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 08:37, 8 January 2023 (UTC)
::::::::::I think adult + baby is sensible, the adult + baby + zombie was not, in retrospect. So yeah adult + baby (if there is one) from now on would be my vote. --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 23:27, 8 January 2023 (UTC)
{{outdent}}
Well then, there's a TON of creatures to go - and I mean both the [[creature]]s page and the individual creature pages. I really hope everyone can pull their weight on that those images. The spritesheets are easy to find, and if you know how to read the .txt files near them, finding sprites on certain rows and columns should be a breeze. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 00:47, 9 January 2023 (UTC)
:Zippy, are you doing all of this by hand? That seems quite tedious. Cutting up the spritesheets can be done automatically. Renaming and updating the table could be done with a script and/or chatgpt. We'd need Lethosor to add the [https://www.mediawiki.org/wiki/Extension:SimpleBatchUpload batch upload extension] though. Maybe some manual work in updating names to match article names rather than raws. [[User:OddballJoe|OddballJoe]] ([[User talk:OddballJoe|talk]]) 06:55, 9 January 2023 (UTC)
{{clear}}
::So did the graphic people gained insights and reached some sort of consensus? are we using big up scaled images + toggle? multiple images to(adult + baby)? anything else? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 00:32, 10 January 2023 (UTC)
:::I noticed that someone blew up the size of the previews in infoboxes. Was that you Jan that did that? Whoever did that enlarged the DFtext tile as well. Don't know if that was intentional or not. I'd prefer if the sprites were either left alone or at double-sized max (or however they look in-game at 1:1 - not zoomed in or out), though that's just me. It looks like maybe they're triple-sized or something.

:::@OddballJoe - It's not all by hand, I have some Photoshop scripts that cut my work time in half, or even by a third. Lethosor said something about us not uploading entire spritesheets. If we did it the entire spritesheet way, one update to the sheet could misalign everything and screw up many pages. For example, let's say Kitfox slipped in an extra couple rows of creatures in an image file, that means the other rows under it would be misaligned and pages would show the wrong creatures. Know what I mean? I'd still prefer if other people jumped in and added sprites, though. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 00:51, 10 January 2023 (UTC)

:::: Lethosor introduced the changes, using the image-rendering stuff. I am just waiting for any sort of consensus to do anything, same as with workshops I am not clear on the size people want to go for [[:File:Carpenter%27s_workshop.png|original]] or [[:File:Ashery.png|big]] --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 01:17, 10 January 2023 (UTC)

::::: I'm no graphics artist but I'm not sure I understand why global consensus needs to be achieved... We're dealing with pixel art, why wouldn't we just upload the pixel-perfect versions from the spritesheets for all images that we need? The display size can be discussed on the appropriate template pages and adjusted in the templates or css. I also tend to think that if we want to maintain something like 1k images that may change in the future, it'd be worth automating most of the work. Zippy, as far as I can tell the raws give all the coordinates needed to cut out and label each sprite, so I was thinking one script could parse the raws, make and label the cutouts, and upload. [[User:OddballJoe|OddballJoe]] ([[User talk:OddballJoe|talk]]) 04:49, 10 January 2023 (UTC)

::::: Likewise I think the image names should be standardized so we can just change the creature infobox template to look up the image rather than editing a gazillion pages by hand. Though I suppose at some point the pages will need review to remove the migration banner anyway. [[User:OddballJoe|OddballJoe]] ([[User talk:OddballJoe|talk]]) 04:51, 10 January 2023 (UTC)

::::: Looks like you answered your own question, standardization. Initially, it is best to try different things and figure out all the odd quirks that doesn't fit. But eventually, it is best if we all work toward the same goal, saving everyone time and making the result more consistent in terms of naming convention, parameter name, resolution, use of scaling (in-game or otherwise), use of sprites or screenshots (like for layered workshops), use of templates, amount of images planned or whatever else was mentioned above. I think that discussion of the desired outcome goes well in hand here. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 10:38, 10 January 2023 (UTC)

=== Graphics in Skill Infoboxes ===
{{v50_skill
| color = 7:0
| graphic = [[File:miner_sprite_icon.png]]
| skill = Miner
| profession = Miner
| job name = [[Mining]]
| tasks =
* [[Dig]]
| attributes =
* Strength
* Toughness
* Endurance
* Willpower
* Spatial Sense
* Kinesthetic Sense}}I've made yet another visual prototype for skills. In other words, we can put sprites of matching dwarves (and possibly humans, elves, goblins, etc.) at the top of infoboxes. If multiple images are put up there, that can mess up the alignment, but don't worry, Zippy thought of that. <code><nowiki>|graphicmargin</nowiki></code> can added, and a percentage or a "px" number can be placed in that parameter to fix it. If you leave said parameter out, the alignment will default to about 42% from the left. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 06:06, 7 January 2023 (UTC)
<pre><nowiki>
{{v50_skill
| color = 7:0
| graphic = [[File:miner_sprite_icon.png]]
| graphicmargin = (OPTIONAL)
| skill = Miner
| profession = Miner
| job name = [[Mining]]
| tasks =
* [[Dig]]
| attributes =
* Strength
* Toughness
* Endurance
* Willpower
* Spatial Sense
* Kinesthetic Sense}}
</nowiki></pre>
::Not sure I understand the alignment issue, can you not put text-align: center on the parent table element instead of messing with explicit margins? As another sidenote, should we continue to be naming all of these templates v50_x, I find that a bit confusing. Why not just edit the main templates with the additional information. Loving all the new templates though nice work Zippy :) --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 11:43, 7 January 2023 (UTC)
:::No, text-align doesn't work with images and divs. That just works for text. When it comes to images, you got to put a little "finesse" on the CSS with those. As for editing the classic templates with the new info, it doesn't always work that way with ''every'' template. Lethosor I think ''did'' update the creature infobox template in the way you mentioned. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 08:37, 8 January 2023 (UTC)
:::: You can use something like this to automatically handle that--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 08:56, 8 January 2023 (UTC)
{|
|-
|<div style="width:200px; display:flex; background-color:#eaecf0;">
[[File:miner_sprite_icon.png|center]]
<div>
|<div style="width:200px; display:flex; background-color:#eaecf0;">
[[File:miner_sprite_icon.png|center]] [[File:miner_sprite_icon.png|center]]
<div>
|<div style="width:200px; display:flex; background-color:#eaecf0;">
[[File:miner_sprite_icon.png|center]] [[File:miner_sprite_icon.png|center]] [[File:miner_sprite_icon.png|center]]
<div>
|}
:::::Hah I am very familar with the CSS finese :P Can you show me an example of a multi-sprite job infobox? I said what I said because I tested my proposed solution and it worked fine :)

Dwarf Fortress Wiki talk:Versions

2023-01-10T01:17:21Z

Jan: /* Creature List Now Supports Graphics! */

{{archive|
# [[DF Talk:Versions/Archive 1|Page 1]]}}

== Version 0.31.19 starts a new DF generation? ==

My reading of Toady's comments on the release of 0.31.19 is that it came out basically because he felt it would take too long to get DF all the way to 0.32. With the ore changes, the sitefinder changes, the addition of grazing and several different industries, there's a lot of changes between 31.18 and 31.19. So I'm thinking it might be a good idea to call it the first release of DF2011 - and what we refer to as "DF2010" would then become 0.31.18.

Thoughts? --[[User:DeMatt|DeMatt]] 07:06, 28 February 2011 (UTC)

==Revisiting Redirects==
I wasn't around when the redirect policy was created, and I'm having trouble understanding the rationale. The example claims that linking [[Main:Cheese]] to [[cv:Cheese maker]] is problematic...but mainspace only ever redirects to the current version. If the best target in the current version is cheese maker, why not link to it directly? (It's not, at least for Cheese, since [[DF2012:Cheese]] exists now.) The explanation seems to be claiming that 40d articles that link to Cheese will follow the Mainspace link--but that hasn't been the case for a long while now. Articles in 40d automatically link against other articles in 40d, so that version remains internally consistent no matter where mainspace links to in the current version. For a current example, what do we gain by linking [[Main:Mead]] to [[cv:Mead]] and linking [[DF2012:Mead]] to [[DF2012:Alcohol]]?

If this really is just an outdated procedure, I recommend we drop the mummery and allow mainspace to link to cv:(best target). Double redirects ''may'' work (sometimes, but [[Main:Mead]] demonstrates a common problem where automatic redirection fails), but if they are unnecessary I think they should be avoided, partly because of problems like [[Main:Mead]] and partly because of the effort required to protect double redirects from users who believe they are problematic.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:16, 8 January 2014 (UTC)

:I was just thinking that. I'm currently attempting to write a basic extension to eliminate the need for mainspace redirects entirely, although Mediawiki's class structure may make this more difficult than I had hoped (the only method I've found for resolving redirects takes the ''article text'' instead of a title, e.g. "#REDIRECT ..."). I do agree that the current situation with redirects isn't ideal, so I'm hoping this will work better (once I get it to work). --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:42, 8 January 2014 (UTC)

Okay, that wasn't quite as clear as I meant it to be. In general, I think this is a tricky situation. Mediawiki wasn't designed to have five content namespaces, and certainly not chains of redirects between them. The problem that was pointed out in the [[DF:REDIR|policy]] is the fact that with:
Main:Foo -> cv:Bar
pages in the cv: namespace can't use [[<nowiki/>foo]], since the namespace links modification causes it to be treated as [[<nowiki/>cv:foo]] instead, which doesn't exist. The current suggested solution is this:
Main:Foo -> cv:Foo -> cv:Bar
This fixes the problem of [[<nowiki/>foo]] not working on cv pages, but creates issues with double redirects not always working. Another solution, which is more intuitive to new editors, is:
Main:Foo -> cv:Bar
cv:Foo -> cv:Bar
Both require creating two redirects. The first method has the advantage of ''ensuring'' that the cv redirect exists (otherwise, main:foo would be a redlink), while the second has the advantage of working more reliably in a couple cases.

What I'm trying to do is make main:Foo "jump" to cv:Foo when cv:foo exists, ''even if main:foo doesn't exist'' (basically it would treat all mainspace pages as redirects to cv pages, but only if the cv page exists and not the mainspace page). I had main:Bar jumping to cv:Bar fine, but if cv:Foo redirected to cv:Bar, accessing main:Foo would mysteriously stop at cv:Foo even if I increased the redirect limit. What I'm trying to do now is follow the redirects internally, without relying on Mediawiki to do it automatically - unfortunately, that has proved to be harder than I had hoped (and I sent my web server into an infinite loop while trying). I will try to work on this some more when I get a chance, although I'm not sure when that'll be yet :(. For now, feel free to fix broken double mainspace redirects as necessary, as long as redirects in the DF2012 namespace stay pointing to the right page (and new mainspace redirects get added in the DF2012 namespace too). --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:21, 9 January 2014 (UTC)

:You're treating cv like a namespace--it's not. It is simply shorthand for "fill in the current version here". [http://dwarffortresswiki.org/index.php?title=User_talk:Briess&diff=182404&oldid=181281 As I discovered a long time ago on a server not far away], linking from Main:Foo to cv:Foo tends to break redirection chains. If, instead of linking to cv:Foo, you link to DF2012:Foo, it might just work. It would, of course, be better if your patch could evaluate cv itself, but even if you have to hardcode the current version it's a single point of maintenance that requires update very infrequently. (For that matter, we could probably dispense with the cv hack entirely and just have a bot update mainspace links from DF2012 to DF201X when we switch to a new version.)--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:05, 9 January 2014 (UTC)
::I know cv isn't a namespace - I was just trying to avoid future confusion when the DF2012 namespace changes. It's interesting that changing "cv" to "DF2012" fixes some broken redirects, although I've found that simply making an edit to a broken redirect can usually fix it as well. I've actually had the most problems with double redirects when the second one (in the DF2012 namespace) doesn't use the DF2012 prefix (e.g. main:Foo containing <nowiki>[[cv:Foo]] and DF2012:Foo containing [[Bar]]</nowiki>). I'd rather keep the cv alias even if it isn't necessary for mainspace redirects when I get the patch to work, since it makes it easier to refer to the current version of the page (for example, several MDF articles contain links to a vanilla page for things that don't change in the mod).
::Also, using aliases like "cv" is supported by Mediawiki; in fact, several WMF wikis use them (for example, "[[wikipedia:WP:Redirects|WP:Redirects]]" on Wikipedia). It's quite likely that Mediawiki isn't processing double redirects using aliases correctly, though, since that's uncommon on most wikis. --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:35, 9 January 2014 (UTC)

In light of the lack of support for the current redirect policy, I propose we replace the current redirect section with:

:Mainspace article pages should use the cv: alias when redirecting to a versioned page, which will automatically update the link when a new version is released. For example, page "Main:Foo" should redirect to page "cv:Bar" (where "Bar" is the page that best describes the topic Foo in the current version).

:Pages in mainspace should only redirect to an older versioned page if that content no longer exists in the current version of the game (e.g. [[Cave river]], [[Chunk]]). In these cases the cv: alias cannot be used.

:Pages inside a versioned namespace should not use the cv: alias. Instead, they should redirect to the best page within that versioned namespace (e.g. [[DF2012:Dodging]], [[v0.31:Drink]]).

:Due to limitations of the wiki software, double redirects should be avoided if possible. When fixing double redirects in mainspace, please make sure to use the cv: alias as appropriate.

If no one objects, I will make this change in a few days.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:21, 15 January 2014 (UTC)

:Okay with me. It may be worth mentioning that double redirects only really need to be changed when they don't work (since changing a lot of redirects that work isn't necessary), but I think it's clearer and more relevant than the current policy. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:26, 16 January 2014 (UTC)

Done.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:55, 22 January 2014 (UTC)

I was finally able to get my extension to work after being motivated by one too many malfunctioning redirects. It now causes nonexistent pages in the main namespace to behave exactly like redirects to their DF2012 counterparts (when linked to, accessed directly, and transcluded). Double redirects also work (up to 100, in fact, although that was a temporary safety measure that I'll probably change). This means we'll be able to safely get rid of all mainspace redirects (redirects that redirect to something other than "cv" will still function if not deleted). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:20, 14 March 2014 (UTC)
:What about articles which don't exist in the current version but do exist in older versions? Will those still need mainspace redirects, or will your extension be able to automatically redirect them to v0.31/40d/23a? --[[User:Quietust|Quietust]] ([[User talk:Quietust|talk]]) 01:29, 14 March 2014 (UTC)
::It ignores all mainspace pages that actually have content, including redirects, so pages like [[masons guild]] won't be affected (unless deleted). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:47, 14 March 2014 (UTC)

Done and deployed. [[Cat]] is still treated as a redirect, even though I just deleted it (try clicking on the "redirected from" link). Pages that exist are ignored, so [[Masons guild]] and [[History of Dwarf Fortress]] still function normally (as a redirect to a 23a page and a non-redirect, respectively). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 18:57, 14 April 2014 (UTC)

I'm sending around a bot right now to delete all redirects of the format "foo -> cv:foo" (a surprising number don't fit this format, so I'm leaving them alone for now). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:43, 14 April 2014 (UTC)

:I'm confused. Do we use double redirects or not? Is there a single place we define our linking policy (including redirects), and is it updated?
:I had trouble linking to [[Consolidated_development]] in [[v0.34:Dragon]]. It kept pointing to v0.34:Consolidated_development, which does not exist. I ended up linking to Main:Consolidated_development to make it work. --[[User:Nahno|Nahno]] ([[User talk:Nahno|talk]]) 10:18, 1 July 2014 (UTC)

::That's a separate problem altogether - links in the versioned namespaces (v0.34, v0.31, 40d, 23a) automatically link to pages within their namespace. I may be able to set up a fallback to mainspace once I'm able to deploy again, but for now the "main:" alias is the intended solution. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 11:36, 1 July 2014 (UTC)

== Google often directs people to the 0.31 page ==

I've noticed a couple of times that finding a wiki page from an external search will often drop me onto a page from an older version. Is it possible to mitigate this somehow for new players? I could imagine something like redirecting old:Bar -> cv:Bar unless the user has come from old:Foo; no idea if that would actually work though. [[User:PeridexisErrant|PeridexisErrant]] ([[User talk:PeridexisErrant|talk]]) 11:48, 4 May 2014 (UTC)

:As a temporary solution, I could write a script that displays a banner of some kind if the user came from an external site. I'll ask Briess if he can do anything on the server level to increase the weighting of the current version's pages. (Obviously there are situations where people are looking for old pages, like [[23a:dungeon master]], so we don't want to disable indexing entirely on old pages.) —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:03, 4 May 2014 (UTC)

== DF2014? ==

As Toady [http://www.bay12games.com/dwarves/ draws closer to a new release], it might be worthwhile to discuss the addition of a new version to the wiki. The upcoming release covers two years of changes and introduces a number of new plants, foods, drinks, multi-tile trees, climbing, jumping, etc., so it is likely to have significant changes from the current DF2012. To avoid having people start new pages (and lose all the effort spent refining the prior version's page), I think it would be best to have a bot automatically copy over the DF2012 pages as a starting point for DF2014. I would suggest that these copied pages include a noticebox template mentioning that the content may be outdated, so that we can easily track which pages have been reviewed. I think either the {{tl|version check}} or {{tl|old}} template would work. --[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 19:43, 5 May 2014 (UTC)

:This is what [[User:QuietBot]] did after the 0.34 release, so it's certainly possible to use the same script to migrate to DF2014. I would like a way of tagging migrated pages, since inaccuracies in some pages went unnoticed for months after they were migrated. Since {{tl|old}} is already in use, {{tl|version check}} may be a better solution (it can be reworded slightly, or we can make a separate template for DF2014 migration). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:23, 1 June 2014 (UTC)
:Made [[Template:DF2014 migrated]] as an example. Any thoughts? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:32, 1 June 2014 (UTC)

== Redirects inconsistency ==

Following a redirect is supposed to be exactly the same as going straight to the page it redirects to, but this actually isn't the case:
* Go to [[Seeds]] and you get [[v0.34:Seed]] (outdated)
* Go to http://dwarffortresswiki.org/index.php?title=Seeds&redirect=no and click on the link and you get to [[DF2014:Seed]] (current)
So if you search for "seed", the top result is the DF2014 version. But search for "seeds" and you get the redirect, which sends you to the outdated page instead. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 23:22, 22 February 2015 (UTC)

While I'm talking about redirects, it seems redirects to sections don't work: see [[DF2014:How do I manage my seeds and crops]]. I know MediaWiki is capable of this trick because Wikipedia does it. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 23:32, 22 February 2015 (UTC)

:I have absolutely no idea why [[seeds]] redirects to a v0.34 page - it could be a Mediawiki bug. The section links issue is due to a known issue in the redirect extension we use, which has yet to be fixed. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:01, 23 February 2015 (UTC)
:It looks like deleting both [[Seeds]] and [[DF2014:Seeds]] fixed things (by allowing AutoRedirect to handle the redirects instead). Feel free to tag any others with {{tl|bad redirect}}. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:03, 23 February 2015 (UTC)
::It gets stranger. [[Vial]] redirects explicitly to [[cv:Flask]] which displays (when you look at it with &redirect=no) as [[DF2014:Flask]], but still goes to the v0.34 version. It seems redirects interpret the cv: pseudo-namespace (or whatever it's called) in an outdated way. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 18:08, 23 February 2015 (UTC)
::I've added a note to this page about this issue. If it gets resolved, the note should be removed. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 21:04, 23 February 2015 (UTC)

==Reorganizing versions==

The internet deals with moved content... poorly. Google is still linking to v0.34 pages more than a year after the switch to "DF2014", and even the wiki software still has cached links pointing to the old version pages.

I propose reorganizing versions on the wiki to avoid moving content whenever possible. Instead of having a temporary "current version" namespace that changes occasionally, all the current information gets promoted to the Main namespace. When the next version split occurs, the Main articles as of a certain revision number can be copied to the newly-created permanent "old version" namespace, while all the current information remains in Main. This not only fixes the link rot issue, but it has a few other benefits as well: fewer administrative tasks, no lockdown (a historical version of the Main pages can be copied at any point, even if the Main articles are already modified for the new version), almost all the article history is maintained in the Main article (instead of being spread unevenly across multiple versions), no "temporary" namespaces are needed, fewer problematic long redirect chains, and hopefully less user confusion (since Main gets priority in search results, etc.).

As an example, today we would not have a DF2014 namespace (which is good because "temporary" namespaces historically disappear anyway). If you ran a search for [[seed]] you'd end up at Main:seed, which would have all the current information on seeds. The version box at the top of the page would still link to the older versions of the seed article. When a new version is released, an admin would choose a revision number and copy the Main:seed article as it exists at that revision number to v0.40:seed. That's it. One historical copy that needs little to no new editing, and zero redirections/moves.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 19:02, 27 July 2015 (UTC)

:Makes sense to me. It would involve a lot of work, though (e.g. fixing templates and categories to account for the current version being in mainspace), although that should be doable thanks to {{tl|category}}, {{tl|version switch}}, etc.. A bot could be set up to copy revisions from before a release date as well, which would be more difficult (and maybe slower) than a direct copy, but not severely. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:24, 30 July 2015 (UTC)

:Actually, there are a few issues with that, namely that there wouldn't be an easy way to distinguish between versioned and non-versioned mainspace pages. There are ways to resolve Google search priority (we can exclude pages from older versions from search engine results if there are newer versions of those pages available, for example). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:47, 6 August 2015 (UTC)

::There aren't very many non-versioned mainspace pages, and determining if a page is versioned is as simple as looking for the version template and/or categories added by the version template (e.g. copy [http://dwarffortresswiki.org/index.php/Category:Current this category] instead of Main:*). The problem with "suggesting" newer pages to Google is that they obviously aren't crawling our wiki regularly (if they were, the fact that the mainspace redirects point to new pages would automatically be picked up). Even if your Google hints worked they wouldn't do anything for all the other broken links out on the 'net.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:35, 6 August 2015 (UTC)

::: Google actually crawls the wiki constantly - we probably get crawl hits from google for a continuous block of 2-3 hours per day, each and every day. Why they are slow to update is beyond me though. I can't remember why we didn't do this initially, but there was a technical limitation involved if I remember correctly. --[[User:Briess|Briess]] ([[User talk:Briess|talk]]) 22:05, 6 August 2015 (UTC)

::: There are <meta> tags that can be used to hide pages from search results (for search engines that recognize them, that is). Searching for {{tl|av}} or [[:Category:Current]] might work, although we'd have to make sure all of the DF2014 pages include that (some pages don't, particularly some disambiguation pages, although all of them should). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:53, 6 August 2015 (UTC)

:Is there a particular reason main and current are separate to begin with?—[[User:CLA|CLA]] ([[User talk:CLA|talk]]) 00:17, 7 August 2015 (UTC)

::It's mostly intended to distinguish between versioned and non-versioned pages and make version-related templates simpler to work with, since every versioned page has a namespace. I wasn't active here in 2010 when this system was created, so Briess and Emi would know more.
::Another issue I just thought of with Loci's suggestion is categories - currently, categories like [[:Category:Animals]] are used to organize the versioned sub-categories. Sure, we can change {{tl|Category}} to categorize mainspace pages in [[:Category:v0.40:Animals]] or [[:Category:DF2014:Animals]], but that would be less straightforward because there wouldn't be a namespace with that name (until pages are migrated when a newer major version is released). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 13:05, 7 August 2015 (UTC)

:Moving current pages to the main namespace sounds like a great idea. -[[User:Jecowa|Jecowa]] ([[User talk:Jecowa|talk]]) 20:47, 4 January 2018 (UTC)

Another thought: dealing with migrating redirects could be difficult with this proposal - specifically, determining which redirects should be migrated to a versioned namespace. Redirects can't contain {{tl|av}}, at least not before ``#REDIRECT``. I ''think'' it would be possible to copy pages in two stages, though - all non-redirects first, then all redirects whose targets were also copied. Thoughts? Anything I'm missing? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:41, 27 June 2019 (UTC)

Some subpages (particularly /raw and /Edit notice) also deliberately lack {{tl|av}}, although those shouldn't be too hard to handle. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:35, 9 July 2019 (UTC)

:Redirect pages (and all other edge cases I've looked at) can be included in categories (like [[:Category:Current]]) to determine whether or not they should be copied into an archival version. But if the redirects are "properly qualified" then they can all be copied over blindly. Mainspace redirects pointing to versioned information should use a blank namespace (which will be automatically constrained to the archival namespace); mainspace redirects pointing to unversioned information should use an explicit "Main" (which will automatically link back to the unversioned page). Then, when [[[[Toady]]]] gets copied to [[[[v0.4x:Toady]]]] it will point back to [[[[Main:Toady One]]]]. Meanwhile, [[[[Beer]]]], copied to [[[[v0.4x:Beer]]]], will properly point to [[[[v0.4x:Alcohol]]]].--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:00, 14 July 2019 (UTC)

::I think qualifying redirects is the best solution here - categorizing redirects manually is another possible source of errors, since categories (or a lack thereof) would only be visible on the redirect page itself, and [[:Category:Current]] is a hidden category. Copying over mainspace redirects into versioned namespaces would also resolve some issues that have come up due to those not reliably existing currently. I should be able to set up a bot script to add "main:" to current mainspace redirects (and it shouldn't break anything, since those redirects go to other mainspace pages anyway). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:57, 14 July 2019 (UTC)

(Note: I wrote all of this without noticing the previous discussion above.) I was wondering, when the wiki creates a new namespace for a major release again, if it is possible to ''not'' create a namespace for the next current version (e.g. "DF202x") and instead have the mainspace articles (which are currently redirects) become the new cv and move the content there. Therefore, [[cv:Cat]] would just be "[[Cat]]" (or [[Main:Cat]]).

Certain namespace-related templates like [[Template:Ns/0]] would need to be changed, though nothing significant as far as I know. For most cases, any "DF2014" would be replaced with "Main" or even blank. There's also multiple extensions handling the current namespace system and they may need to be modified too, though I'm not sure if or how much. I'm guessing based on the discussions above that it will change stuff up.

My reason is the current namespace is increasingly becoming more anachronistic. "DF2014" could be misinterpreted as "this page is about the 2014 version of the game" or "this page was last updated in 2014", which I've seen a few people in forums mention. Granted that [[Template:Av]] is on the top of very article, I still think the namespace is inconsistent with the recentness of the article. But how is this related to what I'm asking for? Let's say we continue the current system: if we happen to do a new namespace change this year and create DF2020, the next major release (after graphics/UI) will be mythgen, which is estimated to take several years to develop (the Big Wait), and so the anachronism will start over again. The proposed way will prevent this from occurring for the next major release and every release thereafter.

I think the confusion with having a namespace that becomes old-fashioned overtime supersedes the confusion with not marking current versioned articles with a namespace. Most users just search "Cat" on the search bar and naturally expect to get information about the latest release of DF. So if users go a page that's just titled "Cat", they won't expect outdated info about cats from a previous release. That's how the current system works anyways. We'll be skipping the two-step process that we have now. It'll make several wiki tasks much simpler as well. Editors can create new articles for current versions without remembering to add a namespace. It'll fix any existing issues with (double) redirects; instead of [[Main:Kitten]] redirecting to [[cv:Kitten]], which goes to [[DF2014:Kitten]], which then redirects to [[DF2014:Cat]], [[Main:Kitten]] would just redirect to [[Main:Cat]]. And the cv: alias will no longer be necessary since "cv:" = "Main:" and will be forever.

There's no need to differentiate the current version and previous versions with a namespace for the current version is what I'm saying. Articles of previous versions will retain their respective namespaces. Users will still type "40d:Cat" to go to the 40d version of the article, but if they want the current version, they'll just type "Cat" (like now). The mainspace containing the "live" version of an article is natural and would create no uncertainty when browsing the wiki. And it would simplify the wiki somewhat and future-proof this anachronism problem. As a bonus, this change will also prevent web search engines from showing previous version pages when typing "DF cat" or something. (This isn't happening right now as DF2014 has been the current namespace for ~6 years, but it'll happen again when everything moves to a new namespace.)

This is the gist of it, and I may have ignored most of the problems with this proposal. I have personally wished for the whole version namespacing be made less complicated and have been seeking for a solution, and I feel like this is the best way to go about in the future. – [[User:Doorkeeper|Doorkeeper]] 21:27, 14 August 2020 (UTC)

:<s>Whoops, looks like Loci already proposed this exact thing long ago. I definitely missed that discussion and should have checked first. My apologies. I'll move my text to that section and remove this one. – [[User:Doorkeeper|Doorkeeper]] 21:36, 14 August 2020 (UTC)</s> Done. – [[User:Doorkeeper|Doorkeeper]] 21:40, 14 August 2020 (UTC)

:The main issue I have with that is that putting pages about the current version in a namespace also differentiates between those pages and pages not about ''any'' version (for example, [[Toady One]] does not need a 40d or v0.34 page). Yes, we can use {{tl|av}} to mark versioned pages, but people often forget to add that to new pages. The current system also allows determining whether a page is versioned or not from its title, which makes migrations a lot faster. Relying on {{tl|av}} would require either reading the content of every page (which would slow scripts down significantly) or cross-checking with the list of all pages including the template (feasible, but a bit more complicated, and still susceptible to missing templates). I suppose that manually fixing and migrating pages missing {{tl|av}} later wouldn't be too much work, though.
:I am definitely in favor of changing "DF2014" (or a new namespace) to "Current", though. I was in favor of "DF2014" in 2014, but I don't think it makes sense anymore, and "Current" seemed to be a popular alternative in both the DF2012 and DF2014 discussions on the matter. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:02, 16 August 2020 (UTC)

== Weird redirect behaviour ==

[[Pump stack]] redirects to [[cv:Screw pump#Pump stack]]. If you look at the redirect itself it says it redirects to DF2014 namespace, which is correct. But if you actually follow the redirect, it goes to v0.34 namespace. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 16:10, 20 August 2018 (UTC)
:Yeah, that's part of the issue described in the above section (the wiki caching part, not on Google's end.) —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 15:00, 21 August 2018 (UTC)

== v50 organization ==

Some wiki admins have had a talk on Discord and decided that the most sustainable path forward is to put content for all future versions of DF in the main namespace. We will be working on a bot to do this in the next few days. Feel free to chime in with suggestions here. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:56, 14 December 2022 (UTC)

:Is it maybe possible to do backwards-namespacing? Like we have a "Main" namespace, which people are free to update, and whenever there's a new version of DF the "Main" namespace is copied into a namespace for the then old version, much like how you'd branch a stable branch from a development branch when working with a git-project? [[User:Therahedwig|Therahedwig]] ([[User talk:Therahedwig|talk]]) 23:13, 14 December 2022 (UTC)

::Yeah, we could do that if we decide to. We were talking about doing that for v50, actually, and might still do something similar to preserve edit history if it doesn't end up being too hard to automate. Our hope is that we will not introduce new namespaces for v50 -> v5x, unless there is a serious breaking change (and hopefully there isn't one). But if we change our mind, one advantage of the type of migration you mentioned is that it can be done retroactively - we can copy historical revisions that were current at the time of the release, and would only lose some typo fixes made after the release that apply to earlier versions as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:11, 15 December 2022 (UTC)

ETA is < 24 hours. Doing some final checks on a migration script. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 07:08, 19 December 2022 (UTC)

: We should really have a task list as there are many things that change and need updating. Including but not limited to:
:* Most templates that used the previous namespace convention broke, including nav templates.
:* Many game files changed locations and their pages need to be updated.
:* Raws need to be updated.
:* Various features added, changed, removed.
:* UI has been changed -- though I am more inclined to wait for classic release to avoid extra work --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 06:56, 20 December 2022 (UTC)

"''Raws need to be updated.''" Including applying text wraparound where necessary, I suppose - more than a few of them have proven to be that special kind of...''difficult'' to navigate otherwise, shall we say? [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 12:52, 20 December 2022 (UTC)

:There is already a task list in the [[#v50 migration|section below]] that includes templates and raws, with an explanation. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:25, 20 December 2022 (UTC)

== v50 migration ==

The initial migration script is done. New content is in the '''main''' namespace, e.g. [[Cat]]. Old content is still at [[DF2014:Cat]]. History was migrated to the ''new'' (main namespace) articles.

I know several things are broken still. Please reply if you find any others:
<div style="border-left: 2px solid red">
* <s>Versioned templates haven't been migrated yet (e.g. {{tl|vermin}} on [[Ant]])</s>
** Fixed. Most were migrated by a bot.
* <s>Raws are missing on all pages that use them.</s>
** This also affects sidebars, such as on [[Cat]] and [[Microcline]].
** Update: The DFRawFunctions extension has been upgraded to include v50 raws, using the "v50:" prefix for filenames instead of "DF2014:". <s>I haven't finished a migration script to create the /raw pages themselves, but they can typically be created manually by copying the DF2014 /raw pages and changing "DF2014" to "v50" everywhere.</s> —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:20, 1 January 2023 (UTC)
** Update 2: Raws have been added for all pages! They were copied from the "DF2014" pages and had "DF2014" replaced with "v50", which appears to have worked from a spot-check, but let me know if you find any problems. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:57, 4 January 2023 (UTC)
* Some pages where the DF2014 page was a redirect to a main namespace page that contained content were migrated incorrectly.
** In this case, the main namespace page is usually a redirect to itself. This can be fixed by undoing LethosorBot's edit to the main namespace page, then copying the content to the DF2014 page.
** Update: most seem to have been fixed manually - thanks! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:41, 21 December 2022 (UTC)
* <s>Some main-namespace talk pages redirect to DF2014 talk pages. Some of these redirects work, and some (usually older ones) do not.</s>
** Fixed with a bot. Some redirects from talk pages to other deleted talk pages are now broken, e.g. [[Talk:Above_ground]] (exists) -> [[Talk:Tile attributes]] (redlink). I am leaving them like that because they redirect to where the talk page should be created, but I'm also fine with people deleting them if they really want to. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:41, 21 December 2022 (UTC)
* {{tl|quality}} for new articles is disabled (see below)
* Some links from DF2014 to Main weren't working: e.g. the version selector [[DF2014:Mason's workshop]] was linking to [[DF2014:Main:Mason's workshop]] instead of [[Main:Mason's workshop]]. I'm not sure exactly why, but I fixed it with a change to the NamespaceLinks extension. Let me know if you spot similar broken links. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:19, 21 December 2022 (UTC)
</div>

—[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:54, 20 December 2022 (UTC)
:The quality levels of the 50.03 pages seem to be missing. I'm not sure if that's covered under that first point. [[User:Trainzack|Trainzack]] ([[User talk:Trainzack|talk]]) 06:47, 20 December 2022 (UTC)
::If the the [[Dwarf Fortress Wiki:Quality]] feature can be made to work with namespace scheme change, I suggest to automatically assign the lowest quality rating to all pages, alternately add the {{tl|old}} to all pages. Otherwise there will be a lot of pages that will fall through the cracks. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 09:12, 20 December 2022 (UTC)
:::I disabled {{tl|quality}} in the main namespace because it would require some rework to make the rating script and the template work properly there. Feel free to take a stab at the template. I will see what can be done on the extension side. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:14, 20 December 2022 (UTC)
::::What needs to be done on the template side? I'm not sure I see too big of an issue leaving pages as "unknown-quality" for now (or just change the default to tattered) until we get the rating script working. Is that script up anywhere, anything that could be helped with? [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 11:10, 2 January 2023 (UTC)
:::::They're already marked as unknown. Really the only issue I know of with the template is that it doesn't show up with some of the newer skins we added, and that can be fixed by getting rid of the absolute positioning. As for the script, it can be found at https://github.com/DF-Wiki/QualityRatings, and the issue is really only with the configuration system not recognizing the main namespace as valid. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:29, 3 January 2023 (UTC)
::::::Great, I started having a crack at fixing the template with different themes. Is the preference to get some CSS going and then include it in the global stylesheet (i.e different styles per theme) or to try and get a "one size fits all" fix? —[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 08:14, 3 January 2023 (UTC)
:::::::I would rather avoid custom site-wide CSS if we can. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:29, 4 January 2023 (UTC)
::::::::I appreciate that, I think it's the simplest solution to add a few lines to common.css though. Unless there is a way to attach CSS specifically to a template, I saw a few extensions that allowed that but I'm not sure if any are present in the wiki at the moment. Regardless there already exists a class `div.topicon` that is specifically for the quality ratings, is there an issue with expanding this class to accommodate the themes? The list of themes where the quality rating display is broken/invisible: Citizen, MinervaNeue, MonoBook. —[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 21:48, 4 January 2023 (UTC)
:::::::::What do you think of moving the template out of the topicon entirely and just placing it in a div? It would take up a (hopefully) small amount of vertical space in the article. [[User:Lethosor/Sandbox/Quality_test]] is an example. Unfortunately it isn't possible to prevent other templates from displaying above the quality this way ([https://dwarffortresswiki.org/index.php?title=User:Lethosor/Sandbox/Quality_test&oldid=283883]). So maybe we do need some custom CSS after all if we want that. I'm open to trying out whatever you propose. I'm a bit worried about future-proofing against skins we add later (particularly a mobile skin) but at least MediaWiki supports skin-specific global CSS as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:33, 5 January 2023 (UTC)
::::::::::I would rather we avoid taking any more vertical space in the article. The growing block pyramid at the top, starting with version template, is annoying. If you end up placing it inside the article space please use a slim box 100% wide that would include both.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 01:19, 5 January 2023 (UTC)
:::::::::::Agreed with you Jan, however I see that as two different tasks (ArticleVersion template changes, getting quality back on pages). I made a test adjustment to the quality and it takes up a negligable amount of extra space. See [[User:Vallode/sandbox#Page_quality]] for the example, we'd be able to completely remove "topicon" (unless it is used somewhere else?) and then potentially move on to making the ArticleVersion template into a slim version on the left-hand-side instead of a large box? Let me know what you think. --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 17:35, 5 January 2023 (UTC)
:::::::::::: Sorry, I just noticed this, I hope you weren't waiting on me. I haven't looked into how it works. All I can say that it would be nice if it shows on main, it is annoying that it shows on discussion and history. And otherwise I think that those negligible spaces adds up when you have multiple notice, redirection etc templates and would prefer if you can [https://ibb.co/X7X7SjL condense all of it] somehow. I also had [https://dwarffortresswiki.org/index.php/User:Jan/sandbox#Misc_variants couple of ideas] on that front, but as dev designer you probably can come up with something more refined if this is direction you choose. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 00:50, 10 January 2023 (UTC)

It appears some pages are redirecting recursively and never resolving correctly, like the [[https://dwarffortresswiki.org/index.php?title=Character_table&redirect=no|character table]] and [[tileset repository]] 07:35, 20 December 2022 (UTC)
: Indeed, these can be caught here: [[Special:DoubleRedirects]] --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:51, 20 December 2022 (UTC)

It might be useful to change the notice title to "release information '''for editors'''" --[[Special:Contributions/142.59.195.176|142.59.195.176]] 10:26, 20 December 2022 (UTC)
:Can do. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)
::New here, hello. Should we set a date where we remove/only show the banner for logged in users. There are (some) pages that have 4 different notices about the upgrade. [[Engraving]] is one such page, the top banner states "information for editors", we then have the "this page was migrated" banner, a version selection which warns the article might be inaccurate, and a smaller banner saying the page might need to be updated. Quite a lot of screen space, I think we can start to slowly reduce the amount of warnings this coming month? [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 10:07, 2 January 2023 (UTC)
:::Unfortunately, only showing info to logged-in users is difficult with how MediaWiki caching works. In terms of reducing warnings, there is a discussion [[Template_talk:ArticleVersion#.22Note_that_some_content_may_still_need_to_be_updated..22|here]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:43, 4 January 2023 (UTC)
:::As for [[Engraving]] specifically, the {{tl|old}} banner was actually present on [[DF2014:Engraving]] as well and got carried over with the migration. I removed it, and agree that it was redundant. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:46, 4 January 2023 (UTC)

Main talkpages seem to redirect to DF2014 talk. Not sure if it is intentional but I like it, though we should pay attention when creating new discussion relating to v50 ending up there.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 14:18, 20 December 2022 (UTC)
:That's unintentional. I specifically wrote the migration script to not move talk pages, but that has the side-effect of leaving any previously-created "Talk -> DF2014 talk" redirects intact. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)

Yo Lethosor, are we adding graphic sprites for the pages in some way? Or are we waiting for you to add some sort of new template or something? I'm sure you don't need me to tell you that the current templates don't allow that. Not sure if I'm allowed to change/create any templates either, as I don't want to break things for hundreds of pages. Edit: And IF the icons are allowed, should they be left alone, or 2×-3× sized like how the Minecraft wiki does it? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 14:29, 20 December 2022 (UTC)
:Depends on which templates you mean. There are copyright concerns with uploading a premium sprite sheet, for instance. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)
::I'm not talking about uploading an entire sprite sheet. I'm just talking about individual icons for each respective page. One image for cows, one for horses, one for werebeasts, etc. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 16:50, 20 December 2022 (UTC)
:::If we do that for every creature in the sprite sheet, that's not much different (in terms of copyright) from uploading the entire sprite sheet. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:09, 20 December 2022 (UTC)
::::Is there someone we can talk to about that? We finally get this new game with graphics, and then we can't use the very graphics of the game? No matter what the rules are, I'd say that would be the stupidest thing ever. I know I'm infamous here when it comes to copyright and images and stuff, but about 80% of game wikis out there are completely unofficial, and use game file images like no one's business. I can't imagine anyone's door being knocked on if we used the game's sprites, but I won't add any here until we have a go-ahead. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 17:14, 20 December 2022 (UTC)

:::::...I've made noise in Mayday's direction on this matter, at least (prob an incorrect maneuver, ''but'').[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 17:55, 20 December 2022 (UTC)
:::::: I hope some sort of arrangement can be made so we can use the new sprites with permission/limits, just as we are using the raw files. Otherwise we are all (devs and editors alike) shooting ourselves in the foot here.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 21:07, 20 December 2022 (UTC)

:::::::I just thought of something. We're supposedly not allowed to upload entire sprite sheets, right? What if - for the time being - we just use a few of them for the purpose of testing out new infoboxes? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 21:46, 20 December 2022 (UTC)
::::::::I don't know. If someone could ask Kitfox and post the response here, that would be great. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:47, 20 December 2022 (UTC)

:::::::::I've reached out to Alexandra, but she hasn't answered yet. Until then I found these old approvals from the previous community manager, Feeona: ([http://www.bay12forums.com/smf/index.php?topic=173474.msg8243633#msg8243633 link1], [http://www.bay12forums.com/smf/index.php?topic=176640.msg8243642#msg8243642 link2]). Waiting for a newer response until we begin mass uploads is probably the politer option, but like Zippy said, it is also standard for wikis to use game sprites with less approval. I second their idea of trying it out with a few images to test the infoboxes. On the extreme off-chance (and I do think it is) Kitfox protests we can always remove these few. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 22:19, 20 December 2022 (UTC)
:::::::::And here is a third, more official statement: ([http://www.bay12forums.com/smf/index.php?topic=173474.msg8249718#msg8249718 link3]). Perhaps that address of info@kitfoxgames.com is the better channel to ask for a confirmation, rather than Discord DMs, but I will be going to bed, so it is best if someone else does that. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 22:29, 20 December 2022 (UTC)
::::::::::Thanks for tracking this down! Ok, sprites should be fine, but let's avoid uploading the entire premium tileset as a single image, for instance (as the forum thread says, "use common sense"). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:21, 21 December 2022 (UTC)
::::::::::: Looks good, permission is always preferable over fairuse, I think it is a win win for all involved. I agree that we shouldn't upload entire sprite sheets (e.g. there is no reason to upload the windmill from every direction or whole construction phase for workshops) and that there are a lot of details that needs to be ironed out through testing. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 05:07, 21 December 2022 (UTC)
:::::::::We have a green light on uploading all and any sprites. Their response to me can be seen [https://i.imgur.com/BhmHjzC.png here]. I'm sure someone else confirmed it before me. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 19:00, 21 December 2022 (UTC)

Shifting temporarily to a new issue, is the documentation of [[Template:ArticleVersion]] outdated? It would seem so to me, since the current version no longer has its own namespace, with the templates needing updating being different ones. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 18:30, 20 December 2022 (UTC)
:I think it is still accurate enough. We left open the possibility of making another namespace in the future, albeit with a different migration strategy - see [[#v50 organization|above]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:52, 20 December 2022 (UTC)

Some Changes to infoboxes might be needed. Too bad [[User:Doorkeeper]] isn't around. He did a great work with navbox project--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:52, 21 December 2022 (UTC)

I just realized that raw files aren't stored as regular wiki pages but loaded via the DFRawFunctions extension (hence the need to update). Good news it's going to be handled in bulk, consistently and relatively easy to updated. Even better it's Lethosor problem ;) Also I just realized that all the "raw files" (txt files in the new vanilla folder) are released into the public domain. Both are probably not news to the vets but I'll leave it here for those who less up to date like myself. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:35, 22 December 2022 (UTC)

: I noticed that some templates aren't working properly in the new namespace, e.g. [[Basalt]] entry had its raw updated manually but the infobox fail to show any details. Cursory look suggest {{t|layerlookup/0}} need a minor tweak. This should do the work
:: Replace: <nowiki>{{layerlookup/aux|{{{{FULLPAGENAME}}/raw}}|uses={{{uses|}}}|wiki={{{wiki|}}}}}</nowiki>
:: With___: <nowiki>{{layerlookup/aux|{{</nowiki>:<nowiki>{{FULLPAGENAME}}/raw}}|uses={{{uses|}}}|wiki={{{wiki|}}}}}</nowiki>
: Not sure what the plan and ETA with raws update so I didn't touch this high usage template for now. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 08:11, 24 December 2022 (UTC)

::Please do feel free to make this update. I am still working on a script to create the <code>/raw</code> pages themselves. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:12, 1 January 2023 (UTC)

Wouldn't it be an idea to add to the Sitenotice to remove the {{tl|migrated article}} tag when an article has been fully updated? I see many articles that seem to be updated still have the tag. And/or advise to make use of the {{tl|verify}} for sections still in need of checking? --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 10:12, 2 January 2023 (UTC)
:Probably a good shout. The "see this page" link does include the detail on removing but we should more explicitly encourage removing the banner once a page has at least been looked over. [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 11:01, 2 January 2023 (UTC)

== v50 specific issues ==
=== Graphics===
Follow up on the use of game sprites and the need to trying it out with a few images to test the infoboxes. First sprite [[:File:Beds v50.png]] was uploaded and used on [[Bed]] entry. Any thoughts? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:06, 21 December 2022 (UTC)
:Seems like it should be rearranged to be horizontal. Also, has there been a serious discussion about copyright? Full screenshots are 100% fine, but you start going into a grey area when you upload pieces of a spritesheet. I'm of the opinion that it's all fine as long as it's inconvenient to reconstruct the full sheet from the individual images. Maybe a further restriction could be you shouldn't upload any of the art unless it's used in an infobox (maybe an exception for pieces of the UI). And one more restriction could be you shouldn't show everything, like in your bed example, maybe just the wooden bed is good enough, leave out the stone and metal, especially since those can only be made from strange moods. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:43, 21 December 2022 (UTC)
::Actually, your bed image is kinda bad for showing off what a bed looks like because it doesn't show the pillow/blankets. That might point to cropped screenshots being the best path, although less convenient for the uploader, as you don't get details left out. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:46, 21 December 2022 (UTC)
::I created a new license template [[Template:Copyright game]], based it on the way the RimWorld wiki does things. Call it a prototype, but it's probably how your bed image should be labelled. Indeed, I added it to it already. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]])

::: I agree that the horizontal arrangement would suit better here and that we should strive to represent how things look in-game. Otherwise, I am not too concerned about people being able to reconstruct anything (lets just say that ''anyone'' interested in that can get the real thing from the game files), also it seem we have permission to use the sprits on top of fairuse. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 19:55, 21 December 2022 (UTC)

::: Modifying the existing template to allow the inclusion of the new sprites is easy (Something like [https://ibb.co/zFXCrjd this]?) The big question is the matter of consistency is there any exceptions that will break the format (size wise with variant bloat for example), the sprite naming format, etc --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:44, 21 December 2022 (UTC)
::: If we are going to show a variant for each material type, then maybe these should be added as separate images so we can add a tooltip for each image. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:49, 21 December 2022 (UTC)

:I've got another prototype going here and here: [[User:Brightgalrs/vector.css]] and [[User:Brightgalrs/Sandbox]]. (You'll need to add the css stuff to your own /vector.css). Basically it's a way to recolor images using css classes. No idea if there's a better way. Also, the real implementation would require a change to [[MediaWiki:Common.css]]. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 22:41, 21 December 2022 (UTC)
:Should mention, there ''is'' a different way, just upload each image 16 times, one for each coloring. But maybe that's not very elegant. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 22:45, 21 December 2022 (UTC)

: It should be noted that soon the classic edition will be released, hence one should plan to have both the Premium and classic alongside in that little space --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 03:14, 22 December 2022 (UTC)
::I'm looking into a tab extension to potentially support this in infoboxes. Perhaps [https://www.mediawiki.org/wiki/Extension:Tabs Extension:Tabs]? I tried [https://www.mediawiki.org/wiki/Extension:TabberNeue Extension:TabberNeue], but it displays a placeholder if JavaScript is disabled, which isn't great. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:22, 22 December 2022 (UTC)
::: The Neue Tabber seem to works pretty much like the old one (which fandom [https://coding-help.fandom.com/wiki/Tabber#Adding_images_into_tabbers still use]) defaulting to showing the first tab only. Quick look suggest that neue work the same, plus the notice that 'Tabber requires Javascript to function' warning? if so, and if it is a bother, then you should be able to edit out the tabberneue-noscript string in code. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 06:29, 22 December 2022 (UTC)
::: I much prefer your tabber solution, but if that fails we can also use the gallery slideshow mode. If so, beware it has no way to control image size so the images have to be maliciously uploaded using the exact same size. example:
<gallery mode="slideshow">
File:SteelSample.png
File:TinSample.png
File:ZincSample.png
File:GoldSample.png
</gallery> --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 10:19, 22 December 2022 (UTC)

==== adding premium set to Infobox ====
I am unclear where are we going with this? 
1) Will (A) tabs be implemented, (B) we be using mediawiki toggle [[Template_talk:V50_workshop|example]] for premium and classic/blocked, (c) put images side by side, or (d) something else? 
2) Also [[silver]] and [[Pig iron]] use very different image style for example. 
3) Anything else you want ? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 12:32, 30 December 2022 (UTC)

: Personally, I would love tabs to be implemented, but I think that side by side might be best for most. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 12:32, 30 December 2022 (UTC)
: Here is rough layout we can use. It should fit most buildings given the default sprite size. There is also a different floor plan for both (inspired by reddit)

{|
|- valign=top
|
{| style="width:200px; background-color:#eaecf0; border-collapse: collapse; "
|+ 5×5
|- style="border-bottom:2px solid #3366cc; "
|<div class="mw-customtoggle-infoboxtab mw-ui-button mw-ui-progressive" style="border-top-right-radius: 10px; border-top-left-radius:10px;">toggle</div>
|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|- valign=top
|colspan=2|<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">
[[File:Siege workshop.png|center|160px]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab"">
{|
|rowspan=2 style="width:50%; font-size: 125%;"|<center>{{Template:Picture Siege workshop}}</center>
|style="line-height: 1em; font-size: 125%;"|
{| style="border-spacing:4px;"
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|}
|
{| style="width:200px; background-color:#eaecf0; border-collapse: collapse; "
|+ 3×3
|- style="border-bottom:2px solid #3366cc; "
|colspan=2 style="text-align: right;"|<div class="mw-customtoggle-infoboxtab mw-ui-button mw-ui-progressive" style="float:left; border-top-right-radius: 10px; border-top-left-radius:10px;">toggle</div>{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|- valign=top
|rowspan=2 style="width:50%;"|
<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">[[File:Carpenter's workshop.png]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab""><center>
{| style="font-size: 175%; border-spacing: 0; background-color: black; border: 2px solid black"
|- 
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"| {{Raw Tile|"|7:0:0}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|{{=}}|6:0:0}}
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"|
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|]|0:0:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
|}</center></div>
|
{| style="border-spacing:5px;"
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|
{| style="width:200px; height:100px; padding:10px; background-color:#eaecf0; border-collapse: collapse;"
|+ 1×1
|- style="border-bottom:2px solid #3366cc;"
| colspan=3 style="text-align:center;"|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|-
| style="border-right: 1px dotted #545557;"|[[File:Screw_press.png|32px|center|link=]]
| style="font-size:125%;"|<center>{{Template:Picture Screw press}}</center>
| style="border-left: 1px dotted #545557;"|<center>{{Template:Floor Plan Screw press}}</center>
|}
|
{| style="width:200px; height:100px; padding:10px; background-color:#eaecf0; border-collapse: collapse;"
|+ 1×3
|- style="border-bottom:2px solid #3366cc;"
| colspan=3 style="text-align:center;"|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|-
| style="border-right: 1px dotted #545557;"|[[File:water_wheel.png|32px|center|link=]]
| style="font-size:125%;"|<center>{{Template:Picture Water wheel}}</center>
| style="border-left: 1px dotted #545557;line-height:normal;"|<center>{{Template:Floor Plan Water wheel}}</center>
|}
|}
:Any thoughts on the direction and or any and all of its elements? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 10:16, 31 December 2022 (UTC)

::I kind of like side-by-side, if it fits. If anyone wants to implement a toggle button or tabs, I would ask that that be implemented in a template for now, so that e.g. we could change a toggle button to tabs in a single place if we decide to install an extension to support that. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:14, 1 January 2023 (UTC)

::: I noticed a comment saying that [[impassable tile]] are no longer used in v50, is that true for all constructions? If so, floor plans are no longer needed, making things much easier as we can fit everything in except the 5v5 constructions like trade depot (and even these can be placed one above the other if so desired). If not, any thought on the alternative floor plan design? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:46, 1 January 2023 (UTC)

:::: None of the constructions have blocking tiles any more from my experience playing. I haven't tested siege weaponry with that stuff, but none of the workshops have it, nor does any furniture. (walls and fortifications will of course obstruct movement [[User:AndrielChaoti|AndrielChaoti]] ([[User talk:AndrielChaoti|talk]]) 18:47, 1 January 2023 (UTC)
::::: Ok, I have removed them from v50. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 23:48, 1 January 2023 (UTC)

I have added a basic side by side variant to [[Template:V50 workshop]] and [[Template:Building]] for testing, let us know if there any issues. Few notes:
* The default image naming scheme of <code>workshop-name.png</code> will likely conflict with existing images here or on commons, maybe another naming scheme should be used like <code>v50 workshop-name.png</code> as it is with ascii pictures.
* There is inconsistency in image size. If you want to use large zoomed images then toggle is best, otherwise they need to be all in native size (96px for 3x3).
* In the current version the code roughly centers the images and if there is a big image like with [[Siege workshop]] it drops to a new line --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 23:48, 1 January 2023 (UTC)

How about combining shortcut keys and the new menu icons:
<div style="color:white; font-size: large; text-shadow: -1px -1px 0 #000, 1px -1px 0 #000, -1px 1px 0 #000, 1px 1px 0 #000;">[[File:Ui b.png]]<div style="position: absolute; bottom:-14px; right:3px;">b</div>[[File:Ui bo.png]]<div style="position: absolute; bottom:-14px; right:3px;">o</div>[[File:Ui bol.png]]<div style="position: absolute; bottom:-14px; right:3px;">l</div>[[File:Ui boll.png]]<div style="position: absolute; bottom:-14px; right:3px;">l</div></div>
--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 02:24, 3 January 2023 (UTC)

:I worry that this is difficult to read (I read it as "boil" at first). I would rather use something like {{tl|k}} with a known background. What about something like this? [[File:Ui boll.png]]<div style="position: absolute; bottom:-14px; right:0px;">{{k|l}}</div> or, alternatively, using flexbox without any overlap: [[File:Ui boll.png]]{{k|l}} —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:37, 3 January 2023 (UTC)
:: Same, but that is the best I came up with. We can use the key or maybe someone can help improve the design. Also 'l' is hard to read even with {{t|key}}.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 03:05, 3 January 2023 (UTC)
:: I added a {{t|Menu icon}} to start things so others can have a go with it. Also any thoughts on the icon naming convention (their shortcut sequence), is there easier/better way? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 09:36, 3 January 2023 (UTC)
::[[User:BarelyCreative]] updated the template: {{Menu icon|b|o|l|y}}. I think it looks good, thoughts? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:40, 3 January 2023 (UTC)
:::I like that, yeah. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:29, 4 January 2023 (UTC)
::::There were some places where it didn't make sense so display every icon all the time (like step-by-step guides), so I changed it slightly to allow display of fewer icons using "num" and counting from the end: <nowiki>{{Menu icon|b|o|l|y|sep=-;|num=2}}</nowiki> {{Menu icon|b|o|l|y|sep=-|num=2}} [[User:BarelyCreative|BarelyCreative]] ([[User talk:BarelyCreative|talk]]) 09:05, 4 January 2023 (UTC)

==== Bizarre palette-swapping idea/prototype ====
No idea if this is a good idea, since it takes a bit of time to set up, and there might be some performance issues... and maybe display issues?

But take a look at this:
{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock|palette-name=amber}}

It's way to swap palettes on an image, although the image itself is a table, with each cell representing a pixel. The template itself looks like this:
<code><nowiki>{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock|palette-name=saffron}}</nowiki></code>
Input the pattern and desired palette name.

I've got a larger showcase here: [[User:Brightgalrs/Sandbox/PaletteSwapShowcase]]. Only did a rock pattern so far, but all palettes are implemented.
The major use for this would be on each stone, metal, wood, etc. type's page. The palette could be read directly from the raws. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 03:22, 24 December 2022 (UTC)

:From a technical perspective, my primary concern is indeed performance. Both on the server side and client side, a large number of tables that large (in terms of markup and cell count, that is) tend to be resource-intensive to generate and render. I saw your image-filtering experiments on [[User:Brightgalrs/vector.css]], and while that strikes me as a newer and less-backwards-compatible approach, it would probably be more resource-friendly.
:Is this color adjustment something the game is doing natively? i.e. does this accurately match what the game displays? I bet we could slap together an image-filtering extension (or find an existing one?) that can do this if needed. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:49, 24 December 2022 (UTC)
::Yeah that's what I suspected. The images the template creates are spot on, checked it against a screenshot I took of some mica rocks in-game. The css stuff is unfortunately totally incorrect, was cool to learn about it though, so not a complete waste of my time :p. The premium, in-game graphics are true sprites, basically patterns of indexed colors. Each of the in-game colors (which are significantly expanded over the 16 ascii colors, there's 116/117) there is a palette defined in "\Dwarf Fortress\data\vanilla\vanilla_descriptors_graphics\graphics\images\palettes.png". Each indexed color of the sprite is swapped for the corresponding color in the palette. Because of that, the css stuff doesn't work since it's doing the hue/saturation/brightness changes to the entire sprite.
::I've looked into an existing mediawiki extension, couldn't find anything. One thing I did't really look at is some type of lua script/module that would basically emulate what the game is doing. So some function that takes in the base image as well as the desired palette, and based on that finds and replaces each color. No idea what mediawiki's capabilities are on that front. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 05:31, 24 December 2022 (UTC)
:::We do have Scribunto installed now, so it's totally possible to do something in Lua too - forgot about that. I can add you to the group that grants access to edit the Module namespace if you want to give that a shot. If we use an extension, we'd probably need a custom one, similar to DFDiagram (or perhaps DFDiagram could be extended - it's in dire need of a rewrite anyway). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:43, 24 December 2022 (UTC)
::::I asked around on the mediawiki irc, I think scribunto/lua is a deadend, at least for taking an uploaded image and doing stuff to it with a lua script. However I did come up with this even more bizarre solution, using block elements. [[User:Brightgalrs/Sandbox/PaletteSwapShowcase2]], maybe less resource intensive? Definitely displays a lot worse though, probably unusable.
::::{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock2|palette-name=saffron}}
::::I dunno, maybe none of this is worth it and we should just write some external program to put all the images together offline, and then just mass upload. It wouldn't be ''that'' many... [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 06:37, 24 December 2022 (UTC)

====Is there an easy way to just paste images from the clipboard?====

I use KDE spectacle to take screenshots straight to the clipboard (after cropping) -- is there an easy way to just paste (and auto-upload) an image into an article? It would make it a lot easier to contribute images. [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 23:35, 1 January 2023 (UTC)
:Unfortunately there is not. I would be open to a MediaWiki extension to support this if someone finds one. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:32, 2 January 2023 (UTC)
:: Looks like this could do it, but I haven't used it before: https://www.mediawiki.org/wiki/Extension:SimpleBatchUpload [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 19:41, 2 January 2023 (UTC)
::: It won't solve paste-from-clipboard, but this would be great for making uploading sprites much easier (auto-cutup spritesheet, rename, bulk upload). Could you add this, Lethosor? [[User:OddballJoe|OddballJoe]] ([[User talk:OddballJoe|talk]]) 21:47, 6 January 2023 (UTC)

====Standards for adding graphical version screenshots and images====

Hello, new user looking into adding imagery from the new version. Is there a standard for quality of new screenshots or images? I noticed that at a certain zoom level (2 zooms in from the furthest zoomed-out view), the graphics appear crisp and 1:1 pixel scaled, and I would propose that all images be taken at this scale whenever possible. If they need to be displayed larger, they should be nearest neighbor scaled in a photo editing program at 100% increments (Microsoft Paint will do this if you first select the image rather than directly scaling the whole canvas). I would also propose that images should be cropped to conform to the 32x32 pixel grid when possible, though this could be problematic with so many new graphical elements exceeding the bounds of their tiles. I would say the best practice for capturing artwork for items, furniture etc. ought to be done in a 3x3 open area to avoid shadows from nearby walls, or else extracted from the raw files (if this doesn't run afoul of being able to re-create the graphical version using those assets).

I know that perfect is the enemy of good, and any documentation is better than none, but just thought I'd ask about this, and see if/where something like this ought to be posted. [[User:Unclesporky|Unclesporky]] ([[User talk:Unclesporky|talk]]) 13:58, 3 January 2023 (UTC)
:It has been stated in [[Template:V50 workshop]] that <q>screenshots should be at the "native" resolution</q> but someone could edit the [[Screenshot]] page for best practice for the steam version. Or post some examples in [[Talk:Screenshot]] to find out what is best? --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 14:21, 3 January 2023 (UTC)

====How would I/should I go about putting creature sprites on their pages?====

Howdy. New player and wiki user here. I wanted to try and help update the wiki to the Steam release of DF, so I figured I'd chip in by putting each creature's sprites on their respective page, since I'll often look up a creature I have yet to see in game only to be met by a blue J, or whatever. I found all of the game's creature sprites in C:\Program Files (x86)\Steam\steamapps\common\Dwarf Fortress\data\vanilla\vanilla_creatures_graphics\graphics\images, so I figured I could just chop those up in Photoshop and stick them on here no problem, but the programming syntax/whatever it is on this site is incredibly confusing, I don't know how I'd actually go about doing it. I figured I'd just find the spot on the page where the little letter is and replace that with the image code, but it seems the pages are built using heavily nested templates that I can't even begin to understand. Any help?--[[User:Treese|Treese]] ([[User talk:Treese|talk]]) 03:07, 5 January 2023 (UTC)
:Based on [[User:Zippy|Zippy]]'s work at {{tl|Creaturelookup_b}}, I added an "image" parameter to {{tl|creaturelookup/0}}, which is what creature pages should all be using. See [[Dwarf]] and [[Cow]] for examples. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:37, 5 January 2023 (UTC)

=== Hotkeys/Menu navigation ===
Most key bindings and menus have changed. Should the article reflect a) only the old version, b) only the GUI version or c) both? For example, [[Bridge|bridges]] used to be built via {{k|b}} -> {{k|g}}, but now it's in Place strucutures {{k|b}} -> Constructions {{k|n}} -> Bridge {{k|b}}. What should be written in the article? Currently, it's {{k|b}} -> {{k|g}}. I ''think'' it should be only b), but I am not sure if there will be differences regarding hotkeys or menus between the premium version and the free version and then, c) would be the most appropriate option. --[[User:Prometherus|Prometherus]] ([[User talk:Prometherus|talk]]) 10:16, 22 December 2022 (UTC)

: Not sure. I wish the classic release soon --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 16:45, 22 December 2022 (UTC)
:: Are you Toady's herald? Looks like it was just released! [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:18, 22 December 2022 (UTC)
:: And our questions are answered, the old hotkeys seem to have been thrown out. Part of me is disappointed (useless muscle memory) but also relieved (unified UI for both versions is good in general and for the wiki). [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:25, 22 December 2022 (UTC)
::: According to info, in a sort of 'demo version' at that. I'll wait a little while longer, for myself.[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 18:22, 22 December 2022 (UTC)
::::It's unlikely that keybindings in it will change significantly. My vote is that we should include information for both premium and classic, everywhere. Hopefully the keybindings are not different between versions. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 18:26, 22 December 2022 (UTC)
:::Shouldn't it be based on the 50 or what verion the article is written for? [[User:Dominick|Dominick]] [[User_talk:dominick|(TALK)]] 18:42, 22 December 2022 (UTC)
:::: The keybindings seem to be consistent between versions, (haven't checked exhausitvely, but since the menu layout is the same I think it is a good assumption). Should also keep in mind/consider that not all actions have keybindings. An option would be write 'Click on the <Example Text> icon or press {{k|E}}' [[User:Koos|Koos]] ([[User talk:Koos|talk]]) 23:14, 23 December 2022 (UTC)

=== Removed features & concepts ===

Since they're removed concepts, I've set [[Room]] to be a redirect for [[DF2014:Room]] and created [[Template:Activity zones]] for the nav bar bedrooms, etc, and made the necessary changes to [[Bedroom]] for it. Is this the correct approach, before I go on much further? (also a note, if it is, then [[Template:v50_rooms]] probably needs to be deleted) I also imagine that considering the number of changes in the interface, that things like [[Adventure mode]] and related pages might best be truncated to "not in 50.03" and when it does make it across, being more deliberately brought over in pieces? [[User:HawkOwl|HawkOwl]] ([[User talk:HawkOwl|talk]]) 06:23, 23 December 2022 (UTC)

:Usually it is marked with [[Template:Removed_feature]]. For example: [[Dipscript]] or [[Party]]. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:45, 23 December 2022 (UTC)

:: Ah, that's fair. Should that be mentioned in [[Dwarf_Fortress_Wiki:Versions#Redirects]]? [[User:HawkOwl|HawkOwl]] ([[User talk:HawkOwl|talk]]) 10:03, 23 December 2022 (UTC)

:::I think the redirect policy mostly had in mind things that were removed a ''long'' time ago, like [[Tax collector]] and [[Economy]] (and the latter actually has a stub page as well). I guess we could clarify. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:34, 23 December 2022 (UTC)

:::: The "current" redirects also cause the version box to incorrectly show that the current version has a page - e.g. [[23a:Cave_river]] shows a v50.04 version, but it's just a redirect back to that version. Similarly, what should happen to redirects like [[Clothes maker]], where a concept has evolved? It currently goes to [[23a:Clothes maker]] - that's correct if the user is trying to look up a very old concept, but if a new user is looking for "how to make clothes", they should be directed to [[Clothier]]. --[[User:Danny252|Danny252]] ([[User talk:Danny252|talk]]) 12:16, 26 December 2022 (UTC)

:::: One should be careful with cv redirects. Most that were recently adjusted were unused plural forms (that should probably be deleted) but few like [[Crown]] needed that for backward compatibility. Removing the [https://dwarffortresswiki.org/index.php?title=Crown&type=revision&diff=279966&oldid=219482 cv part] means the the link on [[v0.31:Tilesets]] is now broken. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 22:30, 26 December 2022 (UTC)

:::::If [[v0.31:Tilesets]] is about v0.31, it should not be using "main:" in its links - ''all'' of those links are going to pages about v50, not v0.31, regardless of whether the target is a redirect or not. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:37, 26 December 2022 (UTC)
:::::: You right, I removed it. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 17:55, 27 December 2022 (UTC)

Crown cv redir issue is now fixed, I believe. As goes with such cases where one can simply revert the troublesome edit, unless I've mistepped, myself? [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 23:52, 26 December 2022 (UTC)
:Both [https://dwarffortresswiki.org/index.php?title=Crown&diff=prev&oldid=280026] and [https://dwarffortresswiki.org/index.php?title=Crown&diff=prev&oldid=279966] should not have had any effect, because "cv" is an alias to the main namespace now, just like "main". Proof: [[Crown]], [[cv:Crown]], [[main:Crown]]. It's possible caching is coming into play here, although I purged the redirect cache after making that alias change earlier this month... —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:02, 27 December 2022 (UTC)

I think there have been some changes not captured, but as a newb, I'm afraid to edit the page(s). A good example is Strawberry. I'm playing the Steam version right now and Strawberry plants are "not relevant to brewing" in Labor > kitchen > veg / fruit / leaves. Unless I'm mistaken and need to process them? Another example is the trade caravan = it seems the 3 square pathing no longer happens; it's just yak(s). 12:31, 28 December 2022 (UTC) 12:29, 28 December 2022 (UTC)
:Strawberries should be brewable according to the Raws.
:Trade wagons has been modified in v50. The first wagons will arrive at the same time your fort is becoming a barony. Until then, it's only pack animals and stairs are indeed fine. The [[Trading]] page needs a huge rework anyway... I'll try to do that next week. --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 13:40, 2 January 2023 (UTC)

<s>As far as I can tell, none of the workshop buildings in v50 have blocking tiles any more. There's a comment to the like in data/vanilla/vanilla_buildings/objects/building_custom.txt that says this "[BLOCK:1:0:0:0] workbenches no longer block". Hesitant to update that template as I'm not sure if it's referenced for all of the old versions too. </s> [[User:AndrielChaoti|AndrielChaoti]] ([[User talk:AndrielChaoti|talk]]) 05:54, 29 December 2022 (UTC)
: A new template has been created: {{tl|V50 workshop}} --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 13:40, 2 January 2023 (UTC)
::Thanks! In general, I would like to delegate the switching responsibility to the template (like how {{tl|creaturelookup/0}} works), but in cases where the parameters diverge significantly like with workshops, it could make sense to make an entirely new template. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:40, 3 January 2023 (UTC)

=== creature infobox prototype (moved) ===

Check it out, I made a temporary template and added it to the [[cow]]s page. Now it shows the sprites (but not the zombified versions yet). I wanted to show everyone a prototype of what v50 creature infoboxes should look like. Or at least something similar to it. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 19:11, 27 December 2022 (UTC)
:Hi, I'm new to editing wikis but I have done a bit of work with sprite sheets and I've been going through the DF data files to find the different graphics hoping to help with the animal pages. I've thrown together a template with grass and a few nature sprites (plants, a tree, and a rock) for size reference but I'm unsure how large the 'display' tiles in the middle of the template should be to suit all animals. I can see in the sprite sheets that some land animals have an adult and child sprite, so two tiles. Others have a male, female, and child, but after seeing you include the zombie cows I'm unsure if I should make it twice the size to add them too. Alternatively, I could grab some tiles from the haunted biomes for the zombie animals and make a separate template for a side-by-side comparison. Either way, let me know if this helps. I'd like to help with other graphics too as we add the premium tilesets but the animals seemed the easiest to tackle with me being new to wiki editing. ~~[[User:UristTheSeventh|UristTheSeventh]] ([[User talk:UristTheSeventh|talk]])
::@Zippy, I am a bit perplexed about the purple cows. Why do we need a zombified version of creatures on every page?
::@UristTheSeventh, we can use all the help. Maybe post an example, so that we can have something to compare and contrast.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 11:49, 3 January 2023 (UTC)
:::@Jan Here are the examples:
:::[[File:Creature template.png]] [[File:Armadillo.png]] [[File:Seagull.png]]
:::It'll need to be wider or arranged differently for different creatures with more that two sprites or for multi-tile creatures. I can also do an aquatic and air themed template for swimming and flying creatures. ~~[[User:UristTheSeventh|UristTheSeventh]] ([[User talk:UristTheSeventh|talk]])
::::Looks nice, like the metal template. There are several people working on updating the graphics you should talk more among yourselves. Best I can offer is that I width wise I am hoping to go up to 200px for infoboxes.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 01:13, 5 January 2023 (UTC)
:::: We don't exactly ''need'' a zombie sprite on each page. I added it because it was... there. I was also hoping to get some opinions on it anyway since that infobox is a visual prototype, and not a final choice. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 03:28, 6 January 2023 (UTC)

===Furniture Infobox===
{{Quality|Unrated}}
{{v50_furniture|name=Bed
|graphic=[[File:bed_sprite_prototype.png]]
|tile=Θ|col=6:0:0
|wood=y
|rooms=
* [[Bedroom]]
* [[Barracks]]
* [[Dormitory]]
|value=10}}
I made a v50 furniture template prototype. I tested this on Firefox, Chrome and Microsoft Edge/Internet Explorer and it looks fine on all of them. I hope this is good enough to be the official thing, unless I'm missing something. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 03:28, 6 January 2023 (UTC)
{{clear}}

=== When do we remove the migration note on specific pages? ===

At what point can we remove the "this page was auto migrated from v47" warning? There are a bunch of small pages that are more or less accurate, if I've reviewed them, can I go ahead and remove the warning? [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 23:33, 1 January 2023 (UTC)
:Yes, feel free to remove it if you think all content is accurate. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:31, 2 January 2023 (UTC)

=== Any info on fixing "creature description not found?" ===

I see this issue on most creature pages, it seems to be due to a lookup that's not currently functioning? Cows interestingly doesn't have this issue but I couldn't figure out how to recreate whatever fix it's editor did. --[[User:Yallendallis|Yallendallis]] ([[User talk:Yallendallis|talk]]) 00:22, 3 January 2023 (UTC)
:That is the missing raws issue described above. Cow was fixed by the addition of [[cow/raw]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:28, 3 January 2023 (UTC)
::Ah makes sense, not fully used to the language of wikis yet so I read over it while looking. To put this bit of questioning to rest for any future readers, is it correct that it's fine to update any raws manually, though it will be done automatically at some point? --[[User:Yallendallis|Yallendallis]] ([[User talk:Yallendallis|talk]]) 07:48, 3 January 2023 (UTC)
:::Yes. I'm circling back to work on a script right now, so not much point in doing it if you're reading this. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:57, 4 January 2023 (UTC)
:::This should be fixed now. If you continue to see pages with problems, you can try [https://www.mediawiki.org/wiki/Manual:Purge purging the cache]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:59, 4 January 2023 (UTC)

=== Adventurer Mode related sections ===

The topic has already been discussed [[#Removed features & concepts|above]], but I don't see a clear line on what to do with article sections that mention Adventurer Mode. Like for example in [[Butcher#Adventurer_mode|Butcher]].

'''a) Truncate''' or '''b) leave in place with a mention''' that the mode is not yet present IG but will be added in a future update?

Personally I think option b) is better, because I think it's silly to undo some work just to reintroduce it a few weeks later, with the necessary corrections. Even if a copy/paste of a previous version takes ~15 seconds, considering the number of articles that need to be corrected, it would be a bit of a waste of time.--[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 14:22, 3 January 2023 (UTC)

== Toggleable image ==

Any objections/comments to using this template for now for toggling between classic and premium images? I'd probably rename it to "Template:Premium-classic thumb image". I'm sure someone can come up with a better UI eventually, but should be easy to migrate at that point. I also think we should use the same customtoggle class for this and for the infobox. [[User:NiftyManiac|NiftyManiac]] ([[User talk:NiftyManiac|talk]]) 23:12, 1 January 2023 (UTC)

{{User:NiftyManiac/Sandbox/TemplateDualImage|
premium=File:Quickstart-finder.png|
classic=File:Quickstart-finder-partial.png
}}

{{User:NiftyManiac/Sandbox/TemplateDualImage|
premium=File:Quickstart-finder.png|
classic=File:Quickstart-finder-partial.png|
caption=My caption|
width=100px
}}

:This looks nice to me! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:30, 2 January 2023 (UTC)

: Good initiative. From the top of my head:
:* I suggest using a shorthand, no one wants to type 'Premium-classic thumb image'.
:* If we end up using toggle for infoboxes (not sure where we headed there), then I agree definitely same custom toggle class should be used for all, thus allowing to switch premium-classic view on the whole page at a click.
:* The button part on a separate row isn't pretty, creating a lot of dead space that can be used by the text. Are we set on the label 'toggle ascii'? Classic isn't Ascii per se, maybe we can use a 'toggle' with a tooltip {{tooltip|for example|does bla bla bla}}, or maybe we can get rid of the text and have a smaller icon button ([[User:Jan/sandbox#Metal_example|two examples]]).
: I hope that helps. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 11:21, 2 January 2023 (UTC)

:: I added [[Template:Dual image]] with some of your suggestions. Agree that it's not super pretty, feel free to try something different.

::* I put the toggle in the caption mostly because I gave up on trying to make a more sophisticated replacement for the default thumb image behavior, I'm sure someone with better wiki-fu could put together something more intelligent.
::* I cut the text down to just "Toggle"; I think the best solution would be a small graphic showing the old and new dwarf icons with arrows between them. [[User:NiftyManiac|NiftyManiac]] ([[User talk:NiftyManiac|talk]]) 19:21, 2 January 2023 (UTC)

{{Dual image|
premium=File:DFwiki5by53by3farm.png|
classic=File:Quickstart_layout_3.png|
width=100px|
caption=A 5x5 room with a 3x3 farm plot
}}
::: I updated the layout, now it should look just like a regular image thumb. I didn't had time to test it, if it doesn't work for you or you don't like it just revert the last change. cheers. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 21:46, 2 January 2023 (UTC)
::::I don't know which part of this talk page to put this, but I added the ability to add icons to the v50 workshops template. Leaving the icon part blank will not break the template in any way. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 09:47, 3 January 2023 (UTC)
{{clear}}
==Creature List Now Supports Graphics!==
I wasn't easy, but I made new templates so the [[Creature]]s page now supports both graphics sprites ''and'' ASCII tiles. Allow me to show you:

{{v50_creaturecurrent_table_head}}
{{v50_creaturecurrent table row|graphic=[[File:dwarf_sprite.png]]|name=[[Dwarf]]|symbol=☺|color=3:0:0|playable=Fort, Adv|hostile=No|food=No|size=60,000|value=Not tameable|biome=[[Mountain halls]], [[Fortress|dwarf fortress]]es, [[hillock]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:elf_sprite.png]]|name=[[Elf]]|symbol=e|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=60,000|value=Not tameable|biome=[[Forest retreat]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:human_sprite.png]]|name=[[Human]]|symbol=U|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=70,000|value=Not tameable|biome=[[Town]]s and cities|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:goblin_sprite.png]]|name=[[Goblin]]|symbol=g|color=7:0:0|playable=Adv|hostile=Usually1|food=No|size=60,000|value=Not tameable|biome=[[Dark fortress]]es and [[dark pit]]s|note=Snatchers2}}
{{v50_creaturecurrent table row|graphic=[[File:kobold_sprite.png]]|name=[[Kobold]]|symbol=k|color=6:0:0|playable=Adv|hostile=Usually1|food=No|size=20,000|value=Not tameable|biome=Caves|note=Skulking race}}
|}

Oh wait, there's a bonus. You can also modify the background color of the box the sprites go in. I added that to make possibly-hard-to-see-otherwise sprites more easy to see - depending on the colors it has. Allow me to demonstrate.

{{v50_creaturecurrent_table_head}}
{{v50_creaturecurrent table row|graphic=[[File:dwarf_sprite.png]]|bgcolor=#829ccc|name=[[Dwarf]]|symbol=☺|color=3:0:0|playable=Fort, Adv|hostile=No|food=No|size=60,000|value=Not tameable|biome=[[Mountain halls]], [[Fortress|dwarf fortress]]es, [[hillock]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:elf_sprite.png]]|bgcolor=#c7dfc0|name=[[Elf]]|symbol=e|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=60,000|value=Not tameable|biome=[[Forest retreat]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:human_sprite.png]]|bgcolor=#c7dfc0|name=[[Human]]|symbol=U|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=70,000|value=Not tameable|biome=[[Town]]s and cities|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:goblin_sprite.png]]|bgcolor=#dfc0c0|name=[[Goblin]]|symbol=g|color=7:0:0|playable=Adv|hostile=Usually1|food=No|size=60,000|value=Not tameable|biome=[[Dark fortress]]es and [[dark pit]]s|note=Snatchers2}}
{{v50_creaturecurrent table row|graphic=[[File:kobold_sprite.png]]|bgcolor=#dfc0c0|name=[[Kobold]]|symbol=k|color=6:0:0|playable=Adv|hostile=Usually1|food=No|size=20,000|value=Not tameable|biome=Caves|note=Skulking race}}
|}

To change the background color, add <code><nowiki>|bgcolor=COLOR</nowiki></code> segment after the <code><nowiki>|graphic</nowiki></code> part. You can use color names or HTML hex color codes. I added this to the v50 creatures page, but at this time, I only added the first five creatures I just displayed. It's gonna take a while to find ALL of those creature sprites. I hope a lot of people help out on that one. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 05:29, 5 January 2023 (UTC)

:Thanks, looks nice! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:44, 5 January 2023 (UTC)
:Nice stuff, took the quick liberty to change the padding-left -> text-align to make all the sprites center aligned relative to each other :) Sweet work --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 17:41, 5 January 2023 (UTC)
:: Good work indeed. One minor issue, is that all the sprites have different sizes, which sometimes create slight variation in table row height. Consider using capping the image size vertically for example <code><nowiki>[[File:dwarf_sprite.png|x32px]]</nowiki></code>--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:15, 5 January 2023 (UTC)
:: Also often in such tables people want to click on the image to go for the specific entry, and often will try to click on the very first thing they see in line the thumb image, but currently that will take them to the file page. Consider adding link parameter for example: <code><nowiki>[[File:dwarf_sprite.png|x32px|link=dwarf]]</nowiki></code> [[File:dwarf_sprite.png|x32px|link=dwarf]] or no link at all <code><nowiki>[[File:dwarf_sprite.png|x32px|link=]]</nowiki></code> [[File:dwarf_sprite.png|x32px|link=]] --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:24, 5 January 2023 (UTC)
::: I mean... Yeah, I could do that. I think that lessens the quality of the sprite a bit because it makes edges blurry, but either way is fine. I could have sworn I added a link for all those images the first time. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 03:23, 6 January 2023 (UTC)
::::Since we are adding pixel art sprites to the website it might be convincing to add a global class like .sprite or .pixel-image that uses the CSS attribute `image-rendering: pixelated;` in order to prevent blurryness when scaling the image up/down. Just a thought --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 09:40, 6 January 2023 (UTC)
:::::Are we able to attach classes directly to images? If so, we can probably attach inline styles directly as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:52, 6 January 2023 (UTC)
::::::Looks like (without an extension) MediaWiki only supports classes on images: [[File:dwarf_sprite.png|x32px|class=pixelated]] and not styles: [[File:dwarf_sprite.png|x32px|style="image-rendering: pixelated;"]] it just treats it as alt text it looks like? Wrapping it in a div works and demonstrates the difference: <div style="image-rendering: pixelated;display:inline;">[[File:dwarf_sprite.png|64px]]</div> [[File:dwarf_sprite.png|64px|inline]]. Speaking from experience, however, image-rendering needs a browser specific prefix in certain browsers (safari, for example) in order to work properly. I'm not entirely sure what the best "MediaWiki" practice is for adding something like this but I would assume it's a simple class in common.css for now. --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 17:17, 6 January 2023 (UTC)
:::::::Ah, yeah, you are correct, I should have checked https://www.mediawiki.org/wiki/Help:Images. I'd be fine adding a class like that to common.css. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:27, 6 January 2023 (UTC)
::::::::Great, in that case if no one is opposed we can add `.game-sprite` or something like that? See below for the CSS, the order of the attributes is relevant. --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 18:23, 6 January 2023 (UTC)
<pre>/* Used for pixel-art images from the game so they can be resized and maintain crisp pixel edges. */
.game-sprite {
image-rendering: -webkit-optimize-contrast;
image-rendering: crisp-edges;
image-rendering: pixelated;
}</pre>
:::::::::So... you guys think each creature page should show the main sprite(s) alone, or should it show the baby versions alongside them? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 08:37, 8 January 2023 (UTC)
::::::::::I think adult + baby is sensible, the adult + baby + zombie was not, in retrospect. So yeah adult + baby (if there is one) from now on would be my vote. --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 23:27, 8 January 2023 (UTC)
{{outdent}}
Well then, there's a TON of creatures to go - and I mean both the [[creature]]s page and the individual creature pages. I really hope everyone can pull their weight on that those images. The spritesheets are easy to find, and if you know how to read the .txt files near them, finding sprites on certain rows and columns should be a breeze. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 00:47, 9 January 2023 (UTC)
:Zippy, are you doing all of this by hand? That seems quite tedious. Cutting up the spritesheets can be done automatically. Renaming and updating the table could be done with a script and/or chatgpt. We'd need Lethosor to add the [https://www.mediawiki.org/wiki/Extension:SimpleBatchUpload batch upload extension] though. Maybe some manual work in updating names to match article names rather than raws. [[User:OddballJoe|OddballJoe]] ([[User talk:OddballJoe|talk]]) 06:55, 9 January 2023 (UTC)
{{clear}}
::So did the graphic people gained insights and reached some sort of consensus? are we using big up scaled images + toggle? multiple images to(adult + baby)? anything else? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 00:32, 10 January 2023 (UTC)
:::I noticed that someone blew up the size of the previews in infoboxes. Was that you Jan that did that? Whoever did that enlarged the DFtext tile as well. Don't know if that was intentional or not. I'd prefer if the sprites were either left alone or at double-sized max (or however they look in-game at 1:1 - not zoomed in or out), though that's just me. It looks like maybe they're triple-sized or something.

:::@OddballJoe - It's not all by hand, I have some Photoshop scripts that cut my work time in half, or even by a third. Lethosor said something about us not uploading entire spritesheets. If we did it the entire spritesheet way, one update to the sheet could misalign everything and screw up many pages. For example, let's say Kitfox slipped in an extra couple rows of creatures in an image file, that means the other rows under it would be misaligned and pages would show the wrong creatures. Know what I mean? I'd still prefer if other people jumped in and added sprites, though. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 00:51, 10 January 2023 (UTC)

:::: Lethosor introduced the changes, using the image-rendering stuff. I am just waiting for any sort of consensus to do anything, same as with workshops I am not clear on the size people want to go for [[:File:Carpenter%27s_workshop.png|original]] or [[:File:Ashery.png|big]] --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 01:17, 10 January 2023 (UTC)

=== Graphics in Skill Infoboxes ===
{{v50_skill
| color = 7:0
| graphic = [[File:miner_sprite_icon.png]]
| skill = Miner
| profession = Miner
| job name = [[Mining]]
| tasks =
* [[Dig]]
| attributes =
* Strength
* Toughness
* Endurance
* Willpower
* Spatial Sense
* Kinesthetic Sense}}I've made yet another visual prototype for skills. In other words, we can put sprites of matching dwarves (and possibly humans, elves, goblins, etc.) at the top of infoboxes. If multiple images are put up there, that can mess up the alignment, but don't worry, Zippy thought of that. <code><nowiki>|graphicmargin</nowiki></code> can added, and a percentage or a "px" number can be placed in that parameter to fix it. If you leave said parameter out, the alignment will default to about 42% from the left. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 06:06, 7 January 2023 (UTC)
<pre><nowiki>
{{v50_skill
| color = 7:0
| graphic = [[File:miner_sprite_icon.png]]
| graphicmargin = (OPTIONAL)
| skill = Miner
| profession = Miner
| job name = [[Mining]]
| tasks =
* [[Dig]]
| attributes =
* Strength
* Toughness
* Endurance
* Willpower
* Spatial Sense
* Kinesthetic Sense}}
</nowiki></pre>
::Not sure I understand the alignment issue, can you not put text-align: center on the parent table element instead of messing with explicit margins? As another sidenote, should we continue to be naming all of these templates v50_x, I find that a bit confusing. Why not just edit the main templates with the additional information. Loving all the new templates though nice work Zippy :) --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 11:43, 7 January 2023 (UTC)
:::No, text-align doesn't work with images and divs. That just works for text. When it comes to images, you got to put a little "finesse" on the CSS with those. As for editing the classic templates with the new info, it doesn't always work that way with ''every'' template. Lethosor I think ''did'' update the creature infobox template in the way you mentioned. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 08:37, 8 January 2023 (UTC)
:::: You can use something like this to automatically handle that--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 08:56, 8 January 2023 (UTC)
{|
|-
|<div style="width:200px; display:flex; background-color:#eaecf0;">
[[File:miner_sprite_icon.png|center]]
<div>
|<div style="width:200px; display:flex; background-color:#eaecf0;">
[[File:miner_sprite_icon.png|center]] [[File:miner_sprite_icon.png|center]]
<div>
|<div style="width:200px; display:flex; background-color:#eaecf0;">
[[File:miner_sprite_icon.png|center]] [[File:miner_sprite_icon.png|center]] [[File:miner_sprite_icon.png|center]]
<div>
|}
:::::Hah I am very familar with the CSS finese :P Can you show me an example of a multi-sprite job infobox? I said what I said because I tested my proposed solution and it worked fine :)

Dwarf Fortress Wiki talk:Versions

2023-01-10T00:50:48Z

Jan: /* v50 migration */ quality

{{archive|
# [[DF Talk:Versions/Archive 1|Page 1]]}}

== Version 0.31.19 starts a new DF generation? ==

My reading of Toady's comments on the release of 0.31.19 is that it came out basically because he felt it would take too long to get DF all the way to 0.32. With the ore changes, the sitefinder changes, the addition of grazing and several different industries, there's a lot of changes between 31.18 and 31.19. So I'm thinking it might be a good idea to call it the first release of DF2011 - and what we refer to as "DF2010" would then become 0.31.18.

Thoughts? --[[User:DeMatt|DeMatt]] 07:06, 28 February 2011 (UTC)

==Revisiting Redirects==
I wasn't around when the redirect policy was created, and I'm having trouble understanding the rationale. The example claims that linking [[Main:Cheese]] to [[cv:Cheese maker]] is problematic...but mainspace only ever redirects to the current version. If the best target in the current version is cheese maker, why not link to it directly? (It's not, at least for Cheese, since [[DF2012:Cheese]] exists now.) The explanation seems to be claiming that 40d articles that link to Cheese will follow the Mainspace link--but that hasn't been the case for a long while now. Articles in 40d automatically link against other articles in 40d, so that version remains internally consistent no matter where mainspace links to in the current version. For a current example, what do we gain by linking [[Main:Mead]] to [[cv:Mead]] and linking [[DF2012:Mead]] to [[DF2012:Alcohol]]?

If this really is just an outdated procedure, I recommend we drop the mummery and allow mainspace to link to cv:(best target). Double redirects ''may'' work (sometimes, but [[Main:Mead]] demonstrates a common problem where automatic redirection fails), but if they are unnecessary I think they should be avoided, partly because of problems like [[Main:Mead]] and partly because of the effort required to protect double redirects from users who believe they are problematic.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:16, 8 January 2014 (UTC)

:I was just thinking that. I'm currently attempting to write a basic extension to eliminate the need for mainspace redirects entirely, although Mediawiki's class structure may make this more difficult than I had hoped (the only method I've found for resolving redirects takes the ''article text'' instead of a title, e.g. "#REDIRECT ..."). I do agree that the current situation with redirects isn't ideal, so I'm hoping this will work better (once I get it to work). --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:42, 8 January 2014 (UTC)

Okay, that wasn't quite as clear as I meant it to be. In general, I think this is a tricky situation. Mediawiki wasn't designed to have five content namespaces, and certainly not chains of redirects between them. The problem that was pointed out in the [[DF:REDIR|policy]] is the fact that with:
Main:Foo -> cv:Bar
pages in the cv: namespace can't use [[<nowiki/>foo]], since the namespace links modification causes it to be treated as [[<nowiki/>cv:foo]] instead, which doesn't exist. The current suggested solution is this:
Main:Foo -> cv:Foo -> cv:Bar
This fixes the problem of [[<nowiki/>foo]] not working on cv pages, but creates issues with double redirects not always working. Another solution, which is more intuitive to new editors, is:
Main:Foo -> cv:Bar
cv:Foo -> cv:Bar
Both require creating two redirects. The first method has the advantage of ''ensuring'' that the cv redirect exists (otherwise, main:foo would be a redlink), while the second has the advantage of working more reliably in a couple cases.

What I'm trying to do is make main:Foo "jump" to cv:Foo when cv:foo exists, ''even if main:foo doesn't exist'' (basically it would treat all mainspace pages as redirects to cv pages, but only if the cv page exists and not the mainspace page). I had main:Bar jumping to cv:Bar fine, but if cv:Foo redirected to cv:Bar, accessing main:Foo would mysteriously stop at cv:Foo even if I increased the redirect limit. What I'm trying to do now is follow the redirects internally, without relying on Mediawiki to do it automatically - unfortunately, that has proved to be harder than I had hoped (and I sent my web server into an infinite loop while trying). I will try to work on this some more when I get a chance, although I'm not sure when that'll be yet :(. For now, feel free to fix broken double mainspace redirects as necessary, as long as redirects in the DF2012 namespace stay pointing to the right page (and new mainspace redirects get added in the DF2012 namespace too). --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:21, 9 January 2014 (UTC)

:You're treating cv like a namespace--it's not. It is simply shorthand for "fill in the current version here". [http://dwarffortresswiki.org/index.php?title=User_talk:Briess&diff=182404&oldid=181281 As I discovered a long time ago on a server not far away], linking from Main:Foo to cv:Foo tends to break redirection chains. If, instead of linking to cv:Foo, you link to DF2012:Foo, it might just work. It would, of course, be better if your patch could evaluate cv itself, but even if you have to hardcode the current version it's a single point of maintenance that requires update very infrequently. (For that matter, we could probably dispense with the cv hack entirely and just have a bot update mainspace links from DF2012 to DF201X when we switch to a new version.)--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:05, 9 January 2014 (UTC)
::I know cv isn't a namespace - I was just trying to avoid future confusion when the DF2012 namespace changes. It's interesting that changing "cv" to "DF2012" fixes some broken redirects, although I've found that simply making an edit to a broken redirect can usually fix it as well. I've actually had the most problems with double redirects when the second one (in the DF2012 namespace) doesn't use the DF2012 prefix (e.g. main:Foo containing <nowiki>[[cv:Foo]] and DF2012:Foo containing [[Bar]]</nowiki>). I'd rather keep the cv alias even if it isn't necessary for mainspace redirects when I get the patch to work, since it makes it easier to refer to the current version of the page (for example, several MDF articles contain links to a vanilla page for things that don't change in the mod).
::Also, using aliases like "cv" is supported by Mediawiki; in fact, several WMF wikis use them (for example, "[[wikipedia:WP:Redirects|WP:Redirects]]" on Wikipedia). It's quite likely that Mediawiki isn't processing double redirects using aliases correctly, though, since that's uncommon on most wikis. --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:35, 9 January 2014 (UTC)

In light of the lack of support for the current redirect policy, I propose we replace the current redirect section with:

:Mainspace article pages should use the cv: alias when redirecting to a versioned page, which will automatically update the link when a new version is released. For example, page "Main:Foo" should redirect to page "cv:Bar" (where "Bar" is the page that best describes the topic Foo in the current version).

:Pages in mainspace should only redirect to an older versioned page if that content no longer exists in the current version of the game (e.g. [[Cave river]], [[Chunk]]). In these cases the cv: alias cannot be used.

:Pages inside a versioned namespace should not use the cv: alias. Instead, they should redirect to the best page within that versioned namespace (e.g. [[DF2012:Dodging]], [[v0.31:Drink]]).

:Due to limitations of the wiki software, double redirects should be avoided if possible. When fixing double redirects in mainspace, please make sure to use the cv: alias as appropriate.

If no one objects, I will make this change in a few days.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:21, 15 January 2014 (UTC)

:Okay with me. It may be worth mentioning that double redirects only really need to be changed when they don't work (since changing a lot of redirects that work isn't necessary), but I think it's clearer and more relevant than the current policy. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:26, 16 January 2014 (UTC)

Done.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:55, 22 January 2014 (UTC)

I was finally able to get my extension to work after being motivated by one too many malfunctioning redirects. It now causes nonexistent pages in the main namespace to behave exactly like redirects to their DF2012 counterparts (when linked to, accessed directly, and transcluded). Double redirects also work (up to 100, in fact, although that was a temporary safety measure that I'll probably change). This means we'll be able to safely get rid of all mainspace redirects (redirects that redirect to something other than "cv" will still function if not deleted). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:20, 14 March 2014 (UTC)
:What about articles which don't exist in the current version but do exist in older versions? Will those still need mainspace redirects, or will your extension be able to automatically redirect them to v0.31/40d/23a? --[[User:Quietust|Quietust]] ([[User talk:Quietust|talk]]) 01:29, 14 March 2014 (UTC)
::It ignores all mainspace pages that actually have content, including redirects, so pages like [[masons guild]] won't be affected (unless deleted). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:47, 14 March 2014 (UTC)

Done and deployed. [[Cat]] is still treated as a redirect, even though I just deleted it (try clicking on the "redirected from" link). Pages that exist are ignored, so [[Masons guild]] and [[History of Dwarf Fortress]] still function normally (as a redirect to a 23a page and a non-redirect, respectively). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 18:57, 14 April 2014 (UTC)

I'm sending around a bot right now to delete all redirects of the format "foo -> cv:foo" (a surprising number don't fit this format, so I'm leaving them alone for now). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:43, 14 April 2014 (UTC)

:I'm confused. Do we use double redirects or not? Is there a single place we define our linking policy (including redirects), and is it updated?
:I had trouble linking to [[Consolidated_development]] in [[v0.34:Dragon]]. It kept pointing to v0.34:Consolidated_development, which does not exist. I ended up linking to Main:Consolidated_development to make it work. --[[User:Nahno|Nahno]] ([[User talk:Nahno|talk]]) 10:18, 1 July 2014 (UTC)

::That's a separate problem altogether - links in the versioned namespaces (v0.34, v0.31, 40d, 23a) automatically link to pages within their namespace. I may be able to set up a fallback to mainspace once I'm able to deploy again, but for now the "main:" alias is the intended solution. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 11:36, 1 July 2014 (UTC)

== Google often directs people to the 0.31 page ==

I've noticed a couple of times that finding a wiki page from an external search will often drop me onto a page from an older version. Is it possible to mitigate this somehow for new players? I could imagine something like redirecting old:Bar -> cv:Bar unless the user has come from old:Foo; no idea if that would actually work though. [[User:PeridexisErrant|PeridexisErrant]] ([[User talk:PeridexisErrant|talk]]) 11:48, 4 May 2014 (UTC)

:As a temporary solution, I could write a script that displays a banner of some kind if the user came from an external site. I'll ask Briess if he can do anything on the server level to increase the weighting of the current version's pages. (Obviously there are situations where people are looking for old pages, like [[23a:dungeon master]], so we don't want to disable indexing entirely on old pages.) —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:03, 4 May 2014 (UTC)

== DF2014? ==

As Toady [http://www.bay12games.com/dwarves/ draws closer to a new release], it might be worthwhile to discuss the addition of a new version to the wiki. The upcoming release covers two years of changes and introduces a number of new plants, foods, drinks, multi-tile trees, climbing, jumping, etc., so it is likely to have significant changes from the current DF2012. To avoid having people start new pages (and lose all the effort spent refining the prior version's page), I think it would be best to have a bot automatically copy over the DF2012 pages as a starting point for DF2014. I would suggest that these copied pages include a noticebox template mentioning that the content may be outdated, so that we can easily track which pages have been reviewed. I think either the {{tl|version check}} or {{tl|old}} template would work. --[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 19:43, 5 May 2014 (UTC)

:This is what [[User:QuietBot]] did after the 0.34 release, so it's certainly possible to use the same script to migrate to DF2014. I would like a way of tagging migrated pages, since inaccuracies in some pages went unnoticed for months after they were migrated. Since {{tl|old}} is already in use, {{tl|version check}} may be a better solution (it can be reworded slightly, or we can make a separate template for DF2014 migration). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:23, 1 June 2014 (UTC)
:Made [[Template:DF2014 migrated]] as an example. Any thoughts? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:32, 1 June 2014 (UTC)

== Redirects inconsistency ==

Following a redirect is supposed to be exactly the same as going straight to the page it redirects to, but this actually isn't the case:
* Go to [[Seeds]] and you get [[v0.34:Seed]] (outdated)
* Go to http://dwarffortresswiki.org/index.php?title=Seeds&redirect=no and click on the link and you get to [[DF2014:Seed]] (current)
So if you search for "seed", the top result is the DF2014 version. But search for "seeds" and you get the redirect, which sends you to the outdated page instead. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 23:22, 22 February 2015 (UTC)

While I'm talking about redirects, it seems redirects to sections don't work: see [[DF2014:How do I manage my seeds and crops]]. I know MediaWiki is capable of this trick because Wikipedia does it. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 23:32, 22 February 2015 (UTC)

:I have absolutely no idea why [[seeds]] redirects to a v0.34 page - it could be a Mediawiki bug. The section links issue is due to a known issue in the redirect extension we use, which has yet to be fixed. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:01, 23 February 2015 (UTC)
:It looks like deleting both [[Seeds]] and [[DF2014:Seeds]] fixed things (by allowing AutoRedirect to handle the redirects instead). Feel free to tag any others with {{tl|bad redirect}}. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:03, 23 February 2015 (UTC)
::It gets stranger. [[Vial]] redirects explicitly to [[cv:Flask]] which displays (when you look at it with &redirect=no) as [[DF2014:Flask]], but still goes to the v0.34 version. It seems redirects interpret the cv: pseudo-namespace (or whatever it's called) in an outdated way. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 18:08, 23 February 2015 (UTC)
::I've added a note to this page about this issue. If it gets resolved, the note should be removed. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 21:04, 23 February 2015 (UTC)

==Reorganizing versions==

The internet deals with moved content... poorly. Google is still linking to v0.34 pages more than a year after the switch to "DF2014", and even the wiki software still has cached links pointing to the old version pages.

I propose reorganizing versions on the wiki to avoid moving content whenever possible. Instead of having a temporary "current version" namespace that changes occasionally, all the current information gets promoted to the Main namespace. When the next version split occurs, the Main articles as of a certain revision number can be copied to the newly-created permanent "old version" namespace, while all the current information remains in Main. This not only fixes the link rot issue, but it has a few other benefits as well: fewer administrative tasks, no lockdown (a historical version of the Main pages can be copied at any point, even if the Main articles are already modified for the new version), almost all the article history is maintained in the Main article (instead of being spread unevenly across multiple versions), no "temporary" namespaces are needed, fewer problematic long redirect chains, and hopefully less user confusion (since Main gets priority in search results, etc.).

As an example, today we would not have a DF2014 namespace (which is good because "temporary" namespaces historically disappear anyway). If you ran a search for [[seed]] you'd end up at Main:seed, which would have all the current information on seeds. The version box at the top of the page would still link to the older versions of the seed article. When a new version is released, an admin would choose a revision number and copy the Main:seed article as it exists at that revision number to v0.40:seed. That's it. One historical copy that needs little to no new editing, and zero redirections/moves.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 19:02, 27 July 2015 (UTC)

:Makes sense to me. It would involve a lot of work, though (e.g. fixing templates and categories to account for the current version being in mainspace), although that should be doable thanks to {{tl|category}}, {{tl|version switch}}, etc.. A bot could be set up to copy revisions from before a release date as well, which would be more difficult (and maybe slower) than a direct copy, but not severely. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:24, 30 July 2015 (UTC)

:Actually, there are a few issues with that, namely that there wouldn't be an easy way to distinguish between versioned and non-versioned mainspace pages. There are ways to resolve Google search priority (we can exclude pages from older versions from search engine results if there are newer versions of those pages available, for example). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:47, 6 August 2015 (UTC)

::There aren't very many non-versioned mainspace pages, and determining if a page is versioned is as simple as looking for the version template and/or categories added by the version template (e.g. copy [http://dwarffortresswiki.org/index.php/Category:Current this category] instead of Main:*). The problem with "suggesting" newer pages to Google is that they obviously aren't crawling our wiki regularly (if they were, the fact that the mainspace redirects point to new pages would automatically be picked up). Even if your Google hints worked they wouldn't do anything for all the other broken links out on the 'net.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:35, 6 August 2015 (UTC)

::: Google actually crawls the wiki constantly - we probably get crawl hits from google for a continuous block of 2-3 hours per day, each and every day. Why they are slow to update is beyond me though. I can't remember why we didn't do this initially, but there was a technical limitation involved if I remember correctly. --[[User:Briess|Briess]] ([[User talk:Briess|talk]]) 22:05, 6 August 2015 (UTC)

::: There are <meta> tags that can be used to hide pages from search results (for search engines that recognize them, that is). Searching for {{tl|av}} or [[:Category:Current]] might work, although we'd have to make sure all of the DF2014 pages include that (some pages don't, particularly some disambiguation pages, although all of them should). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:53, 6 August 2015 (UTC)

:Is there a particular reason main and current are separate to begin with?—[[User:CLA|CLA]] ([[User talk:CLA|talk]]) 00:17, 7 August 2015 (UTC)

::It's mostly intended to distinguish between versioned and non-versioned pages and make version-related templates simpler to work with, since every versioned page has a namespace. I wasn't active here in 2010 when this system was created, so Briess and Emi would know more.
::Another issue I just thought of with Loci's suggestion is categories - currently, categories like [[:Category:Animals]] are used to organize the versioned sub-categories. Sure, we can change {{tl|Category}} to categorize mainspace pages in [[:Category:v0.40:Animals]] or [[:Category:DF2014:Animals]], but that would be less straightforward because there wouldn't be a namespace with that name (until pages are migrated when a newer major version is released). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 13:05, 7 August 2015 (UTC)

:Moving current pages to the main namespace sounds like a great idea. -[[User:Jecowa|Jecowa]] ([[User talk:Jecowa|talk]]) 20:47, 4 January 2018 (UTC)

Another thought: dealing with migrating redirects could be difficult with this proposal - specifically, determining which redirects should be migrated to a versioned namespace. Redirects can't contain {{tl|av}}, at least not before ``#REDIRECT``. I ''think'' it would be possible to copy pages in two stages, though - all non-redirects first, then all redirects whose targets were also copied. Thoughts? Anything I'm missing? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:41, 27 June 2019 (UTC)

Some subpages (particularly /raw and /Edit notice) also deliberately lack {{tl|av}}, although those shouldn't be too hard to handle. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:35, 9 July 2019 (UTC)

:Redirect pages (and all other edge cases I've looked at) can be included in categories (like [[:Category:Current]]) to determine whether or not they should be copied into an archival version. But if the redirects are "properly qualified" then they can all be copied over blindly. Mainspace redirects pointing to versioned information should use a blank namespace (which will be automatically constrained to the archival namespace); mainspace redirects pointing to unversioned information should use an explicit "Main" (which will automatically link back to the unversioned page). Then, when [[[[Toady]]]] gets copied to [[[[v0.4x:Toady]]]] it will point back to [[[[Main:Toady One]]]]. Meanwhile, [[[[Beer]]]], copied to [[[[v0.4x:Beer]]]], will properly point to [[[[v0.4x:Alcohol]]]].--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:00, 14 July 2019 (UTC)

::I think qualifying redirects is the best solution here - categorizing redirects manually is another possible source of errors, since categories (or a lack thereof) would only be visible on the redirect page itself, and [[:Category:Current]] is a hidden category. Copying over mainspace redirects into versioned namespaces would also resolve some issues that have come up due to those not reliably existing currently. I should be able to set up a bot script to add "main:" to current mainspace redirects (and it shouldn't break anything, since those redirects go to other mainspace pages anyway). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:57, 14 July 2019 (UTC)

(Note: I wrote all of this without noticing the previous discussion above.) I was wondering, when the wiki creates a new namespace for a major release again, if it is possible to ''not'' create a namespace for the next current version (e.g. "DF202x") and instead have the mainspace articles (which are currently redirects) become the new cv and move the content there. Therefore, [[cv:Cat]] would just be "[[Cat]]" (or [[Main:Cat]]).

Certain namespace-related templates like [[Template:Ns/0]] would need to be changed, though nothing significant as far as I know. For most cases, any "DF2014" would be replaced with "Main" or even blank. There's also multiple extensions handling the current namespace system and they may need to be modified too, though I'm not sure if or how much. I'm guessing based on the discussions above that it will change stuff up.

My reason is the current namespace is increasingly becoming more anachronistic. "DF2014" could be misinterpreted as "this page is about the 2014 version of the game" or "this page was last updated in 2014", which I've seen a few people in forums mention. Granted that [[Template:Av]] is on the top of very article, I still think the namespace is inconsistent with the recentness of the article. But how is this related to what I'm asking for? Let's say we continue the current system: if we happen to do a new namespace change this year and create DF2020, the next major release (after graphics/UI) will be mythgen, which is estimated to take several years to develop (the Big Wait), and so the anachronism will start over again. The proposed way will prevent this from occurring for the next major release and every release thereafter.

I think the confusion with having a namespace that becomes old-fashioned overtime supersedes the confusion with not marking current versioned articles with a namespace. Most users just search "Cat" on the search bar and naturally expect to get information about the latest release of DF. So if users go a page that's just titled "Cat", they won't expect outdated info about cats from a previous release. That's how the current system works anyways. We'll be skipping the two-step process that we have now. It'll make several wiki tasks much simpler as well. Editors can create new articles for current versions without remembering to add a namespace. It'll fix any existing issues with (double) redirects; instead of [[Main:Kitten]] redirecting to [[cv:Kitten]], which goes to [[DF2014:Kitten]], which then redirects to [[DF2014:Cat]], [[Main:Kitten]] would just redirect to [[Main:Cat]]. And the cv: alias will no longer be necessary since "cv:" = "Main:" and will be forever.

There's no need to differentiate the current version and previous versions with a namespace for the current version is what I'm saying. Articles of previous versions will retain their respective namespaces. Users will still type "40d:Cat" to go to the 40d version of the article, but if they want the current version, they'll just type "Cat" (like now). The mainspace containing the "live" version of an article is natural and would create no uncertainty when browsing the wiki. And it would simplify the wiki somewhat and future-proof this anachronism problem. As a bonus, this change will also prevent web search engines from showing previous version pages when typing "DF cat" or something. (This isn't happening right now as DF2014 has been the current namespace for ~6 years, but it'll happen again when everything moves to a new namespace.)

This is the gist of it, and I may have ignored most of the problems with this proposal. I have personally wished for the whole version namespacing be made less complicated and have been seeking for a solution, and I feel like this is the best way to go about in the future. – [[User:Doorkeeper|Doorkeeper]] 21:27, 14 August 2020 (UTC)

:<s>Whoops, looks like Loci already proposed this exact thing long ago. I definitely missed that discussion and should have checked first. My apologies. I'll move my text to that section and remove this one. – [[User:Doorkeeper|Doorkeeper]] 21:36, 14 August 2020 (UTC)</s> Done. – [[User:Doorkeeper|Doorkeeper]] 21:40, 14 August 2020 (UTC)

:The main issue I have with that is that putting pages about the current version in a namespace also differentiates between those pages and pages not about ''any'' version (for example, [[Toady One]] does not need a 40d or v0.34 page). Yes, we can use {{tl|av}} to mark versioned pages, but people often forget to add that to new pages. The current system also allows determining whether a page is versioned or not from its title, which makes migrations a lot faster. Relying on {{tl|av}} would require either reading the content of every page (which would slow scripts down significantly) or cross-checking with the list of all pages including the template (feasible, but a bit more complicated, and still susceptible to missing templates). I suppose that manually fixing and migrating pages missing {{tl|av}} later wouldn't be too much work, though.
:I am definitely in favor of changing "DF2014" (or a new namespace) to "Current", though. I was in favor of "DF2014" in 2014, but I don't think it makes sense anymore, and "Current" seemed to be a popular alternative in both the DF2012 and DF2014 discussions on the matter. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:02, 16 August 2020 (UTC)

== Weird redirect behaviour ==

[[Pump stack]] redirects to [[cv:Screw pump#Pump stack]]. If you look at the redirect itself it says it redirects to DF2014 namespace, which is correct. But if you actually follow the redirect, it goes to v0.34 namespace. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 16:10, 20 August 2018 (UTC)
:Yeah, that's part of the issue described in the above section (the wiki caching part, not on Google's end.) —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 15:00, 21 August 2018 (UTC)

== v50 organization ==

Some wiki admins have had a talk on Discord and decided that the most sustainable path forward is to put content for all future versions of DF in the main namespace. We will be working on a bot to do this in the next few days. Feel free to chime in with suggestions here. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:56, 14 December 2022 (UTC)

:Is it maybe possible to do backwards-namespacing? Like we have a "Main" namespace, which people are free to update, and whenever there's a new version of DF the "Main" namespace is copied into a namespace for the then old version, much like how you'd branch a stable branch from a development branch when working with a git-project? [[User:Therahedwig|Therahedwig]] ([[User talk:Therahedwig|talk]]) 23:13, 14 December 2022 (UTC)

::Yeah, we could do that if we decide to. We were talking about doing that for v50, actually, and might still do something similar to preserve edit history if it doesn't end up being too hard to automate. Our hope is that we will not introduce new namespaces for v50 -> v5x, unless there is a serious breaking change (and hopefully there isn't one). But if we change our mind, one advantage of the type of migration you mentioned is that it can be done retroactively - we can copy historical revisions that were current at the time of the release, and would only lose some typo fixes made after the release that apply to earlier versions as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:11, 15 December 2022 (UTC)

ETA is < 24 hours. Doing some final checks on a migration script. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 07:08, 19 December 2022 (UTC)

: We should really have a task list as there are many things that change and need updating. Including but not limited to:
:* Most templates that used the previous namespace convention broke, including nav templates.
:* Many game files changed locations and their pages need to be updated.
:* Raws need to be updated.
:* Various features added, changed, removed.
:* UI has been changed -- though I am more inclined to wait for classic release to avoid extra work --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 06:56, 20 December 2022 (UTC)

"''Raws need to be updated.''" Including applying text wraparound where necessary, I suppose - more than a few of them have proven to be that special kind of...''difficult'' to navigate otherwise, shall we say? [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 12:52, 20 December 2022 (UTC)

:There is already a task list in the [[#v50 migration|section below]] that includes templates and raws, with an explanation. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:25, 20 December 2022 (UTC)

== v50 migration ==

The initial migration script is done. New content is in the '''main''' namespace, e.g. [[Cat]]. Old content is still at [[DF2014:Cat]]. History was migrated to the ''new'' (main namespace) articles.

I know several things are broken still. Please reply if you find any others:
<div style="border-left: 2px solid red">
* <s>Versioned templates haven't been migrated yet (e.g. {{tl|vermin}} on [[Ant]])</s>
** Fixed. Most were migrated by a bot.
* <s>Raws are missing on all pages that use them.</s>
** This also affects sidebars, such as on [[Cat]] and [[Microcline]].
** Update: The DFRawFunctions extension has been upgraded to include v50 raws, using the "v50:" prefix for filenames instead of "DF2014:". <s>I haven't finished a migration script to create the /raw pages themselves, but they can typically be created manually by copying the DF2014 /raw pages and changing "DF2014" to "v50" everywhere.</s> —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:20, 1 January 2023 (UTC)
** Update 2: Raws have been added for all pages! They were copied from the "DF2014" pages and had "DF2014" replaced with "v50", which appears to have worked from a spot-check, but let me know if you find any problems. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:57, 4 January 2023 (UTC)
* Some pages where the DF2014 page was a redirect to a main namespace page that contained content were migrated incorrectly.
** In this case, the main namespace page is usually a redirect to itself. This can be fixed by undoing LethosorBot's edit to the main namespace page, then copying the content to the DF2014 page.
** Update: most seem to have been fixed manually - thanks! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:41, 21 December 2022 (UTC)
* <s>Some main-namespace talk pages redirect to DF2014 talk pages. Some of these redirects work, and some (usually older ones) do not.</s>
** Fixed with a bot. Some redirects from talk pages to other deleted talk pages are now broken, e.g. [[Talk:Above_ground]] (exists) -> [[Talk:Tile attributes]] (redlink). I am leaving them like that because they redirect to where the talk page should be created, but I'm also fine with people deleting them if they really want to. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:41, 21 December 2022 (UTC)
* {{tl|quality}} for new articles is disabled (see below)
* Some links from DF2014 to Main weren't working: e.g. the version selector [[DF2014:Mason's workshop]] was linking to [[DF2014:Main:Mason's workshop]] instead of [[Main:Mason's workshop]]. I'm not sure exactly why, but I fixed it with a change to the NamespaceLinks extension. Let me know if you spot similar broken links. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:19, 21 December 2022 (UTC)
</div>

—[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:54, 20 December 2022 (UTC)
:The quality levels of the 50.03 pages seem to be missing. I'm not sure if that's covered under that first point. [[User:Trainzack|Trainzack]] ([[User talk:Trainzack|talk]]) 06:47, 20 December 2022 (UTC)
::If the the [[Dwarf Fortress Wiki:Quality]] feature can be made to work with namespace scheme change, I suggest to automatically assign the lowest quality rating to all pages, alternately add the {{tl|old}} to all pages. Otherwise there will be a lot of pages that will fall through the cracks. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 09:12, 20 December 2022 (UTC)
:::I disabled {{tl|quality}} in the main namespace because it would require some rework to make the rating script and the template work properly there. Feel free to take a stab at the template. I will see what can be done on the extension side. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:14, 20 December 2022 (UTC)
::::What needs to be done on the template side? I'm not sure I see too big of an issue leaving pages as "unknown-quality" for now (or just change the default to tattered) until we get the rating script working. Is that script up anywhere, anything that could be helped with? [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 11:10, 2 January 2023 (UTC)
:::::They're already marked as unknown. Really the only issue I know of with the template is that it doesn't show up with some of the newer skins we added, and that can be fixed by getting rid of the absolute positioning. As for the script, it can be found at https://github.com/DF-Wiki/QualityRatings, and the issue is really only with the configuration system not recognizing the main namespace as valid. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:29, 3 January 2023 (UTC)
::::::Great, I started having a crack at fixing the template with different themes. Is the preference to get some CSS going and then include it in the global stylesheet (i.e different styles per theme) or to try and get a "one size fits all" fix? —[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 08:14, 3 January 2023 (UTC)
:::::::I would rather avoid custom site-wide CSS if we can. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:29, 4 January 2023 (UTC)
::::::::I appreciate that, I think it's the simplest solution to add a few lines to common.css though. Unless there is a way to attach CSS specifically to a template, I saw a few extensions that allowed that but I'm not sure if any are present in the wiki at the moment. Regardless there already exists a class `div.topicon` that is specifically for the quality ratings, is there an issue with expanding this class to accommodate the themes? The list of themes where the quality rating display is broken/invisible: Citizen, MinervaNeue, MonoBook. —[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 21:48, 4 January 2023 (UTC)
:::::::::What do you think of moving the template out of the topicon entirely and just placing it in a div? It would take up a (hopefully) small amount of vertical space in the article. [[User:Lethosor/Sandbox/Quality_test]] is an example. Unfortunately it isn't possible to prevent other templates from displaying above the quality this way ([https://dwarffortresswiki.org/index.php?title=User:Lethosor/Sandbox/Quality_test&oldid=283883]). So maybe we do need some custom CSS after all if we want that. I'm open to trying out whatever you propose. I'm a bit worried about future-proofing against skins we add later (particularly a mobile skin) but at least MediaWiki supports skin-specific global CSS as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:33, 5 January 2023 (UTC)
::::::::::I would rather we avoid taking any more vertical space in the article. The growing block pyramid at the top, starting with version template, is annoying. If you end up placing it inside the article space please use a slim box 100% wide that would include both.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 01:19, 5 January 2023 (UTC)
:::::::::::Agreed with you Jan, however I see that as two different tasks (ArticleVersion template changes, getting quality back on pages). I made a test adjustment to the quality and it takes up a negligable amount of extra space. See [[User:Vallode/sandbox#Page_quality]] for the example, we'd be able to completely remove "topicon" (unless it is used somewhere else?) and then potentially move on to making the ArticleVersion template into a slim version on the left-hand-side instead of a large box? Let me know what you think. --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 17:35, 5 January 2023 (UTC)
:::::::::::: Sorry, I just noticed this, I hope you weren't waiting on me. I haven't looked into how it works. All I can say that it would be nice if it shows on main, it is annoying that it shows on discussion and history. And otherwise I think that those negligible spaces adds up when you have multiple notice, redirection etc templates and would prefer if you can [https://ibb.co/X7X7SjL condense all of it] somehow. I also had [https://dwarffortresswiki.org/index.php/User:Jan/sandbox#Misc_variants couple of ideas] on that front, but as dev designer you probably can come up with something more refined if this is direction you choose. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 00:50, 10 January 2023 (UTC)

It appears some pages are redirecting recursively and never resolving correctly, like the [[https://dwarffortresswiki.org/index.php?title=Character_table&redirect=no|character table]] and [[tileset repository]] 07:35, 20 December 2022 (UTC)
: Indeed, these can be caught here: [[Special:DoubleRedirects]] --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:51, 20 December 2022 (UTC)

It might be useful to change the notice title to "release information '''for editors'''" --[[Special:Contributions/142.59.195.176|142.59.195.176]] 10:26, 20 December 2022 (UTC)
:Can do. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)
::New here, hello. Should we set a date where we remove/only show the banner for logged in users. There are (some) pages that have 4 different notices about the upgrade. [[Engraving]] is one such page, the top banner states "information for editors", we then have the "this page was migrated" banner, a version selection which warns the article might be inaccurate, and a smaller banner saying the page might need to be updated. Quite a lot of screen space, I think we can start to slowly reduce the amount of warnings this coming month? [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 10:07, 2 January 2023 (UTC)
:::Unfortunately, only showing info to logged-in users is difficult with how MediaWiki caching works. In terms of reducing warnings, there is a discussion [[Template_talk:ArticleVersion#.22Note_that_some_content_may_still_need_to_be_updated..22|here]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:43, 4 January 2023 (UTC)
:::As for [[Engraving]] specifically, the {{tl|old}} banner was actually present on [[DF2014:Engraving]] as well and got carried over with the migration. I removed it, and agree that it was redundant. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:46, 4 January 2023 (UTC)

Main talkpages seem to redirect to DF2014 talk. Not sure if it is intentional but I like it, though we should pay attention when creating new discussion relating to v50 ending up there.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 14:18, 20 December 2022 (UTC)
:That's unintentional. I specifically wrote the migration script to not move talk pages, but that has the side-effect of leaving any previously-created "Talk -> DF2014 talk" redirects intact. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)

Yo Lethosor, are we adding graphic sprites for the pages in some way? Or are we waiting for you to add some sort of new template or something? I'm sure you don't need me to tell you that the current templates don't allow that. Not sure if I'm allowed to change/create any templates either, as I don't want to break things for hundreds of pages. Edit: And IF the icons are allowed, should they be left alone, or 2×-3× sized like how the Minecraft wiki does it? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 14:29, 20 December 2022 (UTC)
:Depends on which templates you mean. There are copyright concerns with uploading a premium sprite sheet, for instance. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)
::I'm not talking about uploading an entire sprite sheet. I'm just talking about individual icons for each respective page. One image for cows, one for horses, one for werebeasts, etc. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 16:50, 20 December 2022 (UTC)
:::If we do that for every creature in the sprite sheet, that's not much different (in terms of copyright) from uploading the entire sprite sheet. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:09, 20 December 2022 (UTC)
::::Is there someone we can talk to about that? We finally get this new game with graphics, and then we can't use the very graphics of the game? No matter what the rules are, I'd say that would be the stupidest thing ever. I know I'm infamous here when it comes to copyright and images and stuff, but about 80% of game wikis out there are completely unofficial, and use game file images like no one's business. I can't imagine anyone's door being knocked on if we used the game's sprites, but I won't add any here until we have a go-ahead. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 17:14, 20 December 2022 (UTC)

:::::...I've made noise in Mayday's direction on this matter, at least (prob an incorrect maneuver, ''but'').[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 17:55, 20 December 2022 (UTC)
:::::: I hope some sort of arrangement can be made so we can use the new sprites with permission/limits, just as we are using the raw files. Otherwise we are all (devs and editors alike) shooting ourselves in the foot here.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 21:07, 20 December 2022 (UTC)

:::::::I just thought of something. We're supposedly not allowed to upload entire sprite sheets, right? What if - for the time being - we just use a few of them for the purpose of testing out new infoboxes? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 21:46, 20 December 2022 (UTC)
::::::::I don't know. If someone could ask Kitfox and post the response here, that would be great. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:47, 20 December 2022 (UTC)

:::::::::I've reached out to Alexandra, but she hasn't answered yet. Until then I found these old approvals from the previous community manager, Feeona: ([http://www.bay12forums.com/smf/index.php?topic=173474.msg8243633#msg8243633 link1], [http://www.bay12forums.com/smf/index.php?topic=176640.msg8243642#msg8243642 link2]). Waiting for a newer response until we begin mass uploads is probably the politer option, but like Zippy said, it is also standard for wikis to use game sprites with less approval. I second their idea of trying it out with a few images to test the infoboxes. On the extreme off-chance (and I do think it is) Kitfox protests we can always remove these few. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 22:19, 20 December 2022 (UTC)
:::::::::And here is a third, more official statement: ([http://www.bay12forums.com/smf/index.php?topic=173474.msg8249718#msg8249718 link3]). Perhaps that address of info@kitfoxgames.com is the better channel to ask for a confirmation, rather than Discord DMs, but I will be going to bed, so it is best if someone else does that. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 22:29, 20 December 2022 (UTC)
::::::::::Thanks for tracking this down! Ok, sprites should be fine, but let's avoid uploading the entire premium tileset as a single image, for instance (as the forum thread says, "use common sense"). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:21, 21 December 2022 (UTC)
::::::::::: Looks good, permission is always preferable over fairuse, I think it is a win win for all involved. I agree that we shouldn't upload entire sprite sheets (e.g. there is no reason to upload the windmill from every direction or whole construction phase for workshops) and that there are a lot of details that needs to be ironed out through testing. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 05:07, 21 December 2022 (UTC)
:::::::::We have a green light on uploading all and any sprites. Their response to me can be seen [https://i.imgur.com/BhmHjzC.png here]. I'm sure someone else confirmed it before me. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 19:00, 21 December 2022 (UTC)

Shifting temporarily to a new issue, is the documentation of [[Template:ArticleVersion]] outdated? It would seem so to me, since the current version no longer has its own namespace, with the templates needing updating being different ones. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 18:30, 20 December 2022 (UTC)
:I think it is still accurate enough. We left open the possibility of making another namespace in the future, albeit with a different migration strategy - see [[#v50 organization|above]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:52, 20 December 2022 (UTC)

Some Changes to infoboxes might be needed. Too bad [[User:Doorkeeper]] isn't around. He did a great work with navbox project--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:52, 21 December 2022 (UTC)

I just realized that raw files aren't stored as regular wiki pages but loaded via the DFRawFunctions extension (hence the need to update). Good news it's going to be handled in bulk, consistently and relatively easy to updated. Even better it's Lethosor problem ;) Also I just realized that all the "raw files" (txt files in the new vanilla folder) are released into the public domain. Both are probably not news to the vets but I'll leave it here for those who less up to date like myself. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:35, 22 December 2022 (UTC)

: I noticed that some templates aren't working properly in the new namespace, e.g. [[Basalt]] entry had its raw updated manually but the infobox fail to show any details. Cursory look suggest {{t|layerlookup/0}} need a minor tweak. This should do the work
:: Replace: <nowiki>{{layerlookup/aux|{{{{FULLPAGENAME}}/raw}}|uses={{{uses|}}}|wiki={{{wiki|}}}}}</nowiki>
:: With___: <nowiki>{{layerlookup/aux|{{</nowiki>:<nowiki>{{FULLPAGENAME}}/raw}}|uses={{{uses|}}}|wiki={{{wiki|}}}}}</nowiki>
: Not sure what the plan and ETA with raws update so I didn't touch this high usage template for now. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 08:11, 24 December 2022 (UTC)

::Please do feel free to make this update. I am still working on a script to create the <code>/raw</code> pages themselves. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:12, 1 January 2023 (UTC)

Wouldn't it be an idea to add to the Sitenotice to remove the {{tl|migrated article}} tag when an article has been fully updated? I see many articles that seem to be updated still have the tag. And/or advise to make use of the {{tl|verify}} for sections still in need of checking? --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 10:12, 2 January 2023 (UTC)
:Probably a good shout. The "see this page" link does include the detail on removing but we should more explicitly encourage removing the banner once a page has at least been looked over. [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 11:01, 2 January 2023 (UTC)

== v50 specific issues ==
=== Graphics===
Follow up on the use of game sprites and the need to trying it out with a few images to test the infoboxes. First sprite [[:File:Beds v50.png]] was uploaded and used on [[Bed]] entry. Any thoughts? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:06, 21 December 2022 (UTC)
:Seems like it should be rearranged to be horizontal. Also, has there been a serious discussion about copyright? Full screenshots are 100% fine, but you start going into a grey area when you upload pieces of a spritesheet. I'm of the opinion that it's all fine as long as it's inconvenient to reconstruct the full sheet from the individual images. Maybe a further restriction could be you shouldn't upload any of the art unless it's used in an infobox (maybe an exception for pieces of the UI). And one more restriction could be you shouldn't show everything, like in your bed example, maybe just the wooden bed is good enough, leave out the stone and metal, especially since those can only be made from strange moods. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:43, 21 December 2022 (UTC)
::Actually, your bed image is kinda bad for showing off what a bed looks like because it doesn't show the pillow/blankets. That might point to cropped screenshots being the best path, although less convenient for the uploader, as you don't get details left out. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:46, 21 December 2022 (UTC)
::I created a new license template [[Template:Copyright game]], based it on the way the RimWorld wiki does things. Call it a prototype, but it's probably how your bed image should be labelled. Indeed, I added it to it already. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]])

::: I agree that the horizontal arrangement would suit better here and that we should strive to represent how things look in-game. Otherwise, I am not too concerned about people being able to reconstruct anything (lets just say that ''anyone'' interested in that can get the real thing from the game files), also it seem we have permission to use the sprits on top of fairuse. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 19:55, 21 December 2022 (UTC)

::: Modifying the existing template to allow the inclusion of the new sprites is easy (Something like [https://ibb.co/zFXCrjd this]?) The big question is the matter of consistency is there any exceptions that will break the format (size wise with variant bloat for example), the sprite naming format, etc --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:44, 21 December 2022 (UTC)
::: If we are going to show a variant for each material type, then maybe these should be added as separate images so we can add a tooltip for each image. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:49, 21 December 2022 (UTC)

:I've got another prototype going here and here: [[User:Brightgalrs/vector.css]] and [[User:Brightgalrs/Sandbox]]. (You'll need to add the css stuff to your own /vector.css). Basically it's a way to recolor images using css classes. No idea if there's a better way. Also, the real implementation would require a change to [[MediaWiki:Common.css]]. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 22:41, 21 December 2022 (UTC)
:Should mention, there ''is'' a different way, just upload each image 16 times, one for each coloring. But maybe that's not very elegant. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 22:45, 21 December 2022 (UTC)

: It should be noted that soon the classic edition will be released, hence one should plan to have both the Premium and classic alongside in that little space --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 03:14, 22 December 2022 (UTC)
::I'm looking into a tab extension to potentially support this in infoboxes. Perhaps [https://www.mediawiki.org/wiki/Extension:Tabs Extension:Tabs]? I tried [https://www.mediawiki.org/wiki/Extension:TabberNeue Extension:TabberNeue], but it displays a placeholder if JavaScript is disabled, which isn't great. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:22, 22 December 2022 (UTC)
::: The Neue Tabber seem to works pretty much like the old one (which fandom [https://coding-help.fandom.com/wiki/Tabber#Adding_images_into_tabbers still use]) defaulting to showing the first tab only. Quick look suggest that neue work the same, plus the notice that 'Tabber requires Javascript to function' warning? if so, and if it is a bother, then you should be able to edit out the tabberneue-noscript string in code. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 06:29, 22 December 2022 (UTC)
::: I much prefer your tabber solution, but if that fails we can also use the gallery slideshow mode. If so, beware it has no way to control image size so the images have to be maliciously uploaded using the exact same size. example:
<gallery mode="slideshow">
File:SteelSample.png
File:TinSample.png
File:ZincSample.png
File:GoldSample.png
</gallery> --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 10:19, 22 December 2022 (UTC)

==== adding premium set to Infobox ====
I am unclear where are we going with this? 
1) Will (A) tabs be implemented, (B) we be using mediawiki toggle [[Template_talk:V50_workshop|example]] for premium and classic/blocked, (c) put images side by side, or (d) something else? 
2) Also [[silver]] and [[Pig iron]] use very different image style for example. 
3) Anything else you want ? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 12:32, 30 December 2022 (UTC)

: Personally, I would love tabs to be implemented, but I think that side by side might be best for most. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 12:32, 30 December 2022 (UTC)
: Here is rough layout we can use. It should fit most buildings given the default sprite size. There is also a different floor plan for both (inspired by reddit)

{|
|- valign=top
|
{| style="width:200px; background-color:#eaecf0; border-collapse: collapse; "
|+ 5×5
|- style="border-bottom:2px solid #3366cc; "
|<div class="mw-customtoggle-infoboxtab mw-ui-button mw-ui-progressive" style="border-top-right-radius: 10px; border-top-left-radius:10px;">toggle</div>
|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|- valign=top
|colspan=2|<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">
[[File:Siege workshop.png|center|160px]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab"">
{|
|rowspan=2 style="width:50%; font-size: 125%;"|<center>{{Template:Picture Siege workshop}}</center>
|style="line-height: 1em; font-size: 125%;"|
{| style="border-spacing:4px;"
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|}
|
{| style="width:200px; background-color:#eaecf0; border-collapse: collapse; "
|+ 3×3
|- style="border-bottom:2px solid #3366cc; "
|colspan=2 style="text-align: right;"|<div class="mw-customtoggle-infoboxtab mw-ui-button mw-ui-progressive" style="float:left; border-top-right-radius: 10px; border-top-left-radius:10px;">toggle</div>{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|- valign=top
|rowspan=2 style="width:50%;"|
<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">[[File:Carpenter's workshop.png]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab""><center>
{| style="font-size: 175%; border-spacing: 0; background-color: black; border: 2px solid black"
|- 
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"| {{Raw Tile|"|7:0:0}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|{{=}}|6:0:0}}
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"|
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|]|0:0:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
|}</center></div>
|
{| style="border-spacing:5px;"
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|
{| style="width:200px; height:100px; padding:10px; background-color:#eaecf0; border-collapse: collapse;"
|+ 1×1
|- style="border-bottom:2px solid #3366cc;"
| colspan=3 style="text-align:center;"|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|-
| style="border-right: 1px dotted #545557;"|[[File:Screw_press.png|32px|center|link=]]
| style="font-size:125%;"|<center>{{Template:Picture Screw press}}</center>
| style="border-left: 1px dotted #545557;"|<center>{{Template:Floor Plan Screw press}}</center>
|}
|
{| style="width:200px; height:100px; padding:10px; background-color:#eaecf0; border-collapse: collapse;"
|+ 1×3
|- style="border-bottom:2px solid #3366cc;"
| colspan=3 style="text-align:center;"|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|-
| style="border-right: 1px dotted #545557;"|[[File:water_wheel.png|32px|center|link=]]
| style="font-size:125%;"|<center>{{Template:Picture Water wheel}}</center>
| style="border-left: 1px dotted #545557;line-height:normal;"|<center>{{Template:Floor Plan Water wheel}}</center>
|}
|}
:Any thoughts on the direction and or any and all of its elements? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 10:16, 31 December 2022 (UTC)

::I kind of like side-by-side, if it fits. If anyone wants to implement a toggle button or tabs, I would ask that that be implemented in a template for now, so that e.g. we could change a toggle button to tabs in a single place if we decide to install an extension to support that. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:14, 1 January 2023 (UTC)

::: I noticed a comment saying that [[impassable tile]] are no longer used in v50, is that true for all constructions? If so, floor plans are no longer needed, making things much easier as we can fit everything in except the 5v5 constructions like trade depot (and even these can be placed one above the other if so desired). If not, any thought on the alternative floor plan design? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:46, 1 January 2023 (UTC)

:::: None of the constructions have blocking tiles any more from my experience playing. I haven't tested siege weaponry with that stuff, but none of the workshops have it, nor does any furniture. (walls and fortifications will of course obstruct movement [[User:AndrielChaoti|AndrielChaoti]] ([[User talk:AndrielChaoti|talk]]) 18:47, 1 January 2023 (UTC)
::::: Ok, I have removed them from v50. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 23:48, 1 January 2023 (UTC)

I have added a basic side by side variant to [[Template:V50 workshop]] and [[Template:Building]] for testing, let us know if there any issues. Few notes:
* The default image naming scheme of <code>workshop-name.png</code> will likely conflict with existing images here or on commons, maybe another naming scheme should be used like <code>v50 workshop-name.png</code> as it is with ascii pictures.
* There is inconsistency in image size. If you want to use large zoomed images then toggle is best, otherwise they need to be all in native size (96px for 3x3).
* In the current version the code roughly centers the images and if there is a big image like with [[Siege workshop]] it drops to a new line --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 23:48, 1 January 2023 (UTC)

How about combining shortcut keys and the new menu icons:
<div style="color:white; font-size: large; text-shadow: -1px -1px 0 #000, 1px -1px 0 #000, -1px 1px 0 #000, 1px 1px 0 #000;">[[File:Ui b.png]]<div style="position: absolute; bottom:-14px; right:3px;">b</div>[[File:Ui bo.png]]<div style="position: absolute; bottom:-14px; right:3px;">o</div>[[File:Ui bol.png]]<div style="position: absolute; bottom:-14px; right:3px;">l</div>[[File:Ui boll.png]]<div style="position: absolute; bottom:-14px; right:3px;">l</div></div>
--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 02:24, 3 January 2023 (UTC)

:I worry that this is difficult to read (I read it as "boil" at first). I would rather use something like {{tl|k}} with a known background. What about something like this? [[File:Ui boll.png]]<div style="position: absolute; bottom:-14px; right:0px;">{{k|l}}</div> or, alternatively, using flexbox without any overlap: [[File:Ui boll.png]]{{k|l}} —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:37, 3 January 2023 (UTC)
:: Same, but that is the best I came up with. We can use the key or maybe someone can help improve the design. Also 'l' is hard to read even with {{t|key}}.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 03:05, 3 January 2023 (UTC)
:: I added a {{t|Menu icon}} to start things so others can have a go with it. Also any thoughts on the icon naming convention (their shortcut sequence), is there easier/better way? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 09:36, 3 January 2023 (UTC)
::[[User:BarelyCreative]] updated the template: {{Menu icon|b|o|l|y}}. I think it looks good, thoughts? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:40, 3 January 2023 (UTC)
:::I like that, yeah. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:29, 4 January 2023 (UTC)
::::There were some places where it didn't make sense so display every icon all the time (like step-by-step guides), so I changed it slightly to allow display of fewer icons using "num" and counting from the end: <nowiki>{{Menu icon|b|o|l|y|sep=-;|num=2}}</nowiki> {{Menu icon|b|o|l|y|sep=-|num=2}} [[User:BarelyCreative|BarelyCreative]] ([[User talk:BarelyCreative|talk]]) 09:05, 4 January 2023 (UTC)

==== Bizarre palette-swapping idea/prototype ====
No idea if this is a good idea, since it takes a bit of time to set up, and there might be some performance issues... and maybe display issues?

But take a look at this:
{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock|palette-name=amber}}

It's way to swap palettes on an image, although the image itself is a table, with each cell representing a pixel. The template itself looks like this:
<code><nowiki>{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock|palette-name=saffron}}</nowiki></code>
Input the pattern and desired palette name.

I've got a larger showcase here: [[User:Brightgalrs/Sandbox/PaletteSwapShowcase]]. Only did a rock pattern so far, but all palettes are implemented.
The major use for this would be on each stone, metal, wood, etc. type's page. The palette could be read directly from the raws. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 03:22, 24 December 2022 (UTC)

:From a technical perspective, my primary concern is indeed performance. Both on the server side and client side, a large number of tables that large (in terms of markup and cell count, that is) tend to be resource-intensive to generate and render. I saw your image-filtering experiments on [[User:Brightgalrs/vector.css]], and while that strikes me as a newer and less-backwards-compatible approach, it would probably be more resource-friendly.
:Is this color adjustment something the game is doing natively? i.e. does this accurately match what the game displays? I bet we could slap together an image-filtering extension (or find an existing one?) that can do this if needed. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:49, 24 December 2022 (UTC)
::Yeah that's what I suspected. The images the template creates are spot on, checked it against a screenshot I took of some mica rocks in-game. The css stuff is unfortunately totally incorrect, was cool to learn about it though, so not a complete waste of my time :p. The premium, in-game graphics are true sprites, basically patterns of indexed colors. Each of the in-game colors (which are significantly expanded over the 16 ascii colors, there's 116/117) there is a palette defined in "\Dwarf Fortress\data\vanilla\vanilla_descriptors_graphics\graphics\images\palettes.png". Each indexed color of the sprite is swapped for the corresponding color in the palette. Because of that, the css stuff doesn't work since it's doing the hue/saturation/brightness changes to the entire sprite.
::I've looked into an existing mediawiki extension, couldn't find anything. One thing I did't really look at is some type of lua script/module that would basically emulate what the game is doing. So some function that takes in the base image as well as the desired palette, and based on that finds and replaces each color. No idea what mediawiki's capabilities are on that front. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 05:31, 24 December 2022 (UTC)
:::We do have Scribunto installed now, so it's totally possible to do something in Lua too - forgot about that. I can add you to the group that grants access to edit the Module namespace if you want to give that a shot. If we use an extension, we'd probably need a custom one, similar to DFDiagram (or perhaps DFDiagram could be extended - it's in dire need of a rewrite anyway). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:43, 24 December 2022 (UTC)
::::I asked around on the mediawiki irc, I think scribunto/lua is a deadend, at least for taking an uploaded image and doing stuff to it with a lua script. However I did come up with this even more bizarre solution, using block elements. [[User:Brightgalrs/Sandbox/PaletteSwapShowcase2]], maybe less resource intensive? Definitely displays a lot worse though, probably unusable.
::::{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock2|palette-name=saffron}}
::::I dunno, maybe none of this is worth it and we should just write some external program to put all the images together offline, and then just mass upload. It wouldn't be ''that'' many... [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 06:37, 24 December 2022 (UTC)

====Is there an easy way to just paste images from the clipboard?====

I use KDE spectacle to take screenshots straight to the clipboard (after cropping) -- is there an easy way to just paste (and auto-upload) an image into an article? It would make it a lot easier to contribute images. [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 23:35, 1 January 2023 (UTC)
:Unfortunately there is not. I would be open to a MediaWiki extension to support this if someone finds one. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:32, 2 January 2023 (UTC)
:: Looks like this could do it, but I haven't used it before: https://www.mediawiki.org/wiki/Extension:SimpleBatchUpload [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 19:41, 2 January 2023 (UTC)
::: It won't solve paste-from-clipboard, but this would be great for making uploading sprites much easier (auto-cutup spritesheet, rename, bulk upload). Could you add this, Lethosor? [[User:OddballJoe|OddballJoe]] ([[User talk:OddballJoe|talk]]) 21:47, 6 January 2023 (UTC)

====Standards for adding graphical version screenshots and images====

Hello, new user looking into adding imagery from the new version. Is there a standard for quality of new screenshots or images? I noticed that at a certain zoom level (2 zooms in from the furthest zoomed-out view), the graphics appear crisp and 1:1 pixel scaled, and I would propose that all images be taken at this scale whenever possible. If they need to be displayed larger, they should be nearest neighbor scaled in a photo editing program at 100% increments (Microsoft Paint will do this if you first select the image rather than directly scaling the whole canvas). I would also propose that images should be cropped to conform to the 32x32 pixel grid when possible, though this could be problematic with so many new graphical elements exceeding the bounds of their tiles. I would say the best practice for capturing artwork for items, furniture etc. ought to be done in a 3x3 open area to avoid shadows from nearby walls, or else extracted from the raw files (if this doesn't run afoul of being able to re-create the graphical version using those assets).

I know that perfect is the enemy of good, and any documentation is better than none, but just thought I'd ask about this, and see if/where something like this ought to be posted. [[User:Unclesporky|Unclesporky]] ([[User talk:Unclesporky|talk]]) 13:58, 3 January 2023 (UTC)
:It has been stated in [[Template:V50 workshop]] that <q>screenshots should be at the "native" resolution</q> but someone could edit the [[Screenshot]] page for best practice for the steam version. Or post some examples in [[Talk:Screenshot]] to find out what is best? --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 14:21, 3 January 2023 (UTC)

====How would I/should I go about putting creature sprites on their pages?====

Howdy. New player and wiki user here. I wanted to try and help update the wiki to the Steam release of DF, so I figured I'd chip in by putting each creature's sprites on their respective page, since I'll often look up a creature I have yet to see in game only to be met by a blue J, or whatever. I found all of the game's creature sprites in C:\Program Files (x86)\Steam\steamapps\common\Dwarf Fortress\data\vanilla\vanilla_creatures_graphics\graphics\images, so I figured I could just chop those up in Photoshop and stick them on here no problem, but the programming syntax/whatever it is on this site is incredibly confusing, I don't know how I'd actually go about doing it. I figured I'd just find the spot on the page where the little letter is and replace that with the image code, but it seems the pages are built using heavily nested templates that I can't even begin to understand. Any help?--[[User:Treese|Treese]] ([[User talk:Treese|talk]]) 03:07, 5 January 2023 (UTC)
:Based on [[User:Zippy|Zippy]]'s work at {{tl|Creaturelookup_b}}, I added an "image" parameter to {{tl|creaturelookup/0}}, which is what creature pages should all be using. See [[Dwarf]] and [[Cow]] for examples. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:37, 5 January 2023 (UTC)

=== Hotkeys/Menu navigation ===
Most key bindings and menus have changed. Should the article reflect a) only the old version, b) only the GUI version or c) both? For example, [[Bridge|bridges]] used to be built via {{k|b}} -> {{k|g}}, but now it's in Place strucutures {{k|b}} -> Constructions {{k|n}} -> Bridge {{k|b}}. What should be written in the article? Currently, it's {{k|b}} -> {{k|g}}. I ''think'' it should be only b), but I am not sure if there will be differences regarding hotkeys or menus between the premium version and the free version and then, c) would be the most appropriate option. --[[User:Prometherus|Prometherus]] ([[User talk:Prometherus|talk]]) 10:16, 22 December 2022 (UTC)

: Not sure. I wish the classic release soon --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 16:45, 22 December 2022 (UTC)
:: Are you Toady's herald? Looks like it was just released! [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:18, 22 December 2022 (UTC)
:: And our questions are answered, the old hotkeys seem to have been thrown out. Part of me is disappointed (useless muscle memory) but also relieved (unified UI for both versions is good in general and for the wiki). [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:25, 22 December 2022 (UTC)
::: According to info, in a sort of 'demo version' at that. I'll wait a little while longer, for myself.[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 18:22, 22 December 2022 (UTC)
::::It's unlikely that keybindings in it will change significantly. My vote is that we should include information for both premium and classic, everywhere. Hopefully the keybindings are not different between versions. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 18:26, 22 December 2022 (UTC)
:::Shouldn't it be based on the 50 or what verion the article is written for? [[User:Dominick|Dominick]] [[User_talk:dominick|(TALK)]] 18:42, 22 December 2022 (UTC)
:::: The keybindings seem to be consistent between versions, (haven't checked exhausitvely, but since the menu layout is the same I think it is a good assumption). Should also keep in mind/consider that not all actions have keybindings. An option would be write 'Click on the <Example Text> icon or press {{k|E}}' [[User:Koos|Koos]] ([[User talk:Koos|talk]]) 23:14, 23 December 2022 (UTC)

=== Removed features & concepts ===

Since they're removed concepts, I've set [[Room]] to be a redirect for [[DF2014:Room]] and created [[Template:Activity zones]] for the nav bar bedrooms, etc, and made the necessary changes to [[Bedroom]] for it. Is this the correct approach, before I go on much further? (also a note, if it is, then [[Template:v50_rooms]] probably needs to be deleted) I also imagine that considering the number of changes in the interface, that things like [[Adventure mode]] and related pages might best be truncated to "not in 50.03" and when it does make it across, being more deliberately brought over in pieces? [[User:HawkOwl|HawkOwl]] ([[User talk:HawkOwl|talk]]) 06:23, 23 December 2022 (UTC)

:Usually it is marked with [[Template:Removed_feature]]. For example: [[Dipscript]] or [[Party]]. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:45, 23 December 2022 (UTC)

:: Ah, that's fair. Should that be mentioned in [[Dwarf_Fortress_Wiki:Versions#Redirects]]? [[User:HawkOwl|HawkOwl]] ([[User talk:HawkOwl|talk]]) 10:03, 23 December 2022 (UTC)

:::I think the redirect policy mostly had in mind things that were removed a ''long'' time ago, like [[Tax collector]] and [[Economy]] (and the latter actually has a stub page as well). I guess we could clarify. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:34, 23 December 2022 (UTC)

:::: The "current" redirects also cause the version box to incorrectly show that the current version has a page - e.g. [[23a:Cave_river]] shows a v50.04 version, but it's just a redirect back to that version. Similarly, what should happen to redirects like [[Clothes maker]], where a concept has evolved? It currently goes to [[23a:Clothes maker]] - that's correct if the user is trying to look up a very old concept, but if a new user is looking for "how to make clothes", they should be directed to [[Clothier]]. --[[User:Danny252|Danny252]] ([[User talk:Danny252|talk]]) 12:16, 26 December 2022 (UTC)

:::: One should be careful with cv redirects. Most that were recently adjusted were unused plural forms (that should probably be deleted) but few like [[Crown]] needed that for backward compatibility. Removing the [https://dwarffortresswiki.org/index.php?title=Crown&type=revision&diff=279966&oldid=219482 cv part] means the the link on [[v0.31:Tilesets]] is now broken. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 22:30, 26 December 2022 (UTC)

:::::If [[v0.31:Tilesets]] is about v0.31, it should not be using "main:" in its links - ''all'' of those links are going to pages about v50, not v0.31, regardless of whether the target is a redirect or not. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:37, 26 December 2022 (UTC)
:::::: You right, I removed it. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 17:55, 27 December 2022 (UTC)

Crown cv redir issue is now fixed, I believe. As goes with such cases where one can simply revert the troublesome edit, unless I've mistepped, myself? [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 23:52, 26 December 2022 (UTC)
:Both [https://dwarffortresswiki.org/index.php?title=Crown&diff=prev&oldid=280026] and [https://dwarffortresswiki.org/index.php?title=Crown&diff=prev&oldid=279966] should not have had any effect, because "cv" is an alias to the main namespace now, just like "main". Proof: [[Crown]], [[cv:Crown]], [[main:Crown]]. It's possible caching is coming into play here, although I purged the redirect cache after making that alias change earlier this month... —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:02, 27 December 2022 (UTC)

I think there have been some changes not captured, but as a newb, I'm afraid to edit the page(s). A good example is Strawberry. I'm playing the Steam version right now and Strawberry plants are "not relevant to brewing" in Labor > kitchen > veg / fruit / leaves. Unless I'm mistaken and need to process them? Another example is the trade caravan = it seems the 3 square pathing no longer happens; it's just yak(s). 12:31, 28 December 2022 (UTC) 12:29, 28 December 2022 (UTC)
:Strawberries should be brewable according to the Raws.
:Trade wagons has been modified in v50. The first wagons will arrive at the same time your fort is becoming a barony. Until then, it's only pack animals and stairs are indeed fine. The [[Trading]] page needs a huge rework anyway... I'll try to do that next week. --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 13:40, 2 January 2023 (UTC)

<s>As far as I can tell, none of the workshop buildings in v50 have blocking tiles any more. There's a comment to the like in data/vanilla/vanilla_buildings/objects/building_custom.txt that says this "[BLOCK:1:0:0:0] workbenches no longer block". Hesitant to update that template as I'm not sure if it's referenced for all of the old versions too. </s> [[User:AndrielChaoti|AndrielChaoti]] ([[User talk:AndrielChaoti|talk]]) 05:54, 29 December 2022 (UTC)
: A new template has been created: {{tl|V50 workshop}} --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 13:40, 2 January 2023 (UTC)
::Thanks! In general, I would like to delegate the switching responsibility to the template (like how {{tl|creaturelookup/0}} works), but in cases where the parameters diverge significantly like with workshops, it could make sense to make an entirely new template. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:40, 3 January 2023 (UTC)

=== creature infobox prototype (moved) ===

Check it out, I made a temporary template and added it to the [[cow]]s page. Now it shows the sprites (but not the zombified versions yet). I wanted to show everyone a prototype of what v50 creature infoboxes should look like. Or at least something similar to it. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 19:11, 27 December 2022 (UTC)
:Hi, I'm new to editing wikis but I have done a bit of work with sprite sheets and I've been going through the DF data files to find the different graphics hoping to help with the animal pages. I've thrown together a template with grass and a few nature sprites (plants, a tree, and a rock) for size reference but I'm unsure how large the 'display' tiles in the middle of the template should be to suit all animals. I can see in the sprite sheets that some land animals have an adult and child sprite, so two tiles. Others have a male, female, and child, but after seeing you include the zombie cows I'm unsure if I should make it twice the size to add them too. Alternatively, I could grab some tiles from the haunted biomes for the zombie animals and make a separate template for a side-by-side comparison. Either way, let me know if this helps. I'd like to help with other graphics too as we add the premium tilesets but the animals seemed the easiest to tackle with me being new to wiki editing. ~~[[User:UristTheSeventh|UristTheSeventh]] ([[User talk:UristTheSeventh|talk]])
::@Zippy, I am a bit perplexed about the purple cows. Why do we need a zombified version of creatures on every page?
::@UristTheSeventh, we can use all the help. Maybe post an example, so that we can have something to compare and contrast.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 11:49, 3 January 2023 (UTC)
:::@Jan Here are the examples:
:::[[File:Creature template.png]] [[File:Armadillo.png]] [[File:Seagull.png]]
:::It'll need to be wider or arranged differently for different creatures with more that two sprites or for multi-tile creatures. I can also do an aquatic and air themed template for swimming and flying creatures. ~~[[User:UristTheSeventh|UristTheSeventh]] ([[User talk:UristTheSeventh|talk]])
::::Looks nice, like the metal template. There are several people working on updating the graphics you should talk more among yourselves. Best I can offer is that I width wise I am hoping to go up to 200px for infoboxes.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 01:13, 5 January 2023 (UTC)
:::: We don't exactly ''need'' a zombie sprite on each page. I added it because it was... there. I was also hoping to get some opinions on it anyway since that infobox is a visual prototype, and not a final choice. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 03:28, 6 January 2023 (UTC)

===Furniture Infobox===
{{Quality|Unrated}}
{{v50_furniture|name=Bed
|graphic=[[File:bed_sprite_prototype.png]]
|tile=Θ|col=6:0:0
|wood=y
|rooms=
* [[Bedroom]]
* [[Barracks]]
* [[Dormitory]]
|value=10}}
I made a v50 furniture template prototype. I tested this on Firefox, Chrome and Microsoft Edge/Internet Explorer and it looks fine on all of them. I hope this is good enough to be the official thing, unless I'm missing something. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 03:28, 6 January 2023 (UTC)
{{clear}}

=== When do we remove the migration note on specific pages? ===

At what point can we remove the "this page was auto migrated from v47" warning? There are a bunch of small pages that are more or less accurate, if I've reviewed them, can I go ahead and remove the warning? [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 23:33, 1 January 2023 (UTC)
:Yes, feel free to remove it if you think all content is accurate. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:31, 2 January 2023 (UTC)

=== Any info on fixing "creature description not found?" ===

I see this issue on most creature pages, it seems to be due to a lookup that's not currently functioning? Cows interestingly doesn't have this issue but I couldn't figure out how to recreate whatever fix it's editor did. --[[User:Yallendallis|Yallendallis]] ([[User talk:Yallendallis|talk]]) 00:22, 3 January 2023 (UTC)
:That is the missing raws issue described above. Cow was fixed by the addition of [[cow/raw]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:28, 3 January 2023 (UTC)
::Ah makes sense, not fully used to the language of wikis yet so I read over it while looking. To put this bit of questioning to rest for any future readers, is it correct that it's fine to update any raws manually, though it will be done automatically at some point? --[[User:Yallendallis|Yallendallis]] ([[User talk:Yallendallis|talk]]) 07:48, 3 January 2023 (UTC)
:::Yes. I'm circling back to work on a script right now, so not much point in doing it if you're reading this. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:57, 4 January 2023 (UTC)
:::This should be fixed now. If you continue to see pages with problems, you can try [https://www.mediawiki.org/wiki/Manual:Purge purging the cache]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:59, 4 January 2023 (UTC)

=== Adventurer Mode related sections ===

The topic has already been discussed [[#Removed features & concepts|above]], but I don't see a clear line on what to do with article sections that mention Adventurer Mode. Like for example in [[Butcher#Adventurer_mode|Butcher]].

'''a) Truncate''' or '''b) leave in place with a mention''' that the mode is not yet present IG but will be added in a future update?

Personally I think option b) is better, because I think it's silly to undo some work just to reintroduce it a few weeks later, with the necessary corrections. Even if a copy/paste of a previous version takes ~15 seconds, considering the number of articles that need to be corrected, it would be a bit of a waste of time.--[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 14:22, 3 January 2023 (UTC)

== Toggleable image ==

Any objections/comments to using this template for now for toggling between classic and premium images? I'd probably rename it to "Template:Premium-classic thumb image". I'm sure someone can come up with a better UI eventually, but should be easy to migrate at that point. I also think we should use the same customtoggle class for this and for the infobox. [[User:NiftyManiac|NiftyManiac]] ([[User talk:NiftyManiac|talk]]) 23:12, 1 January 2023 (UTC)

{{User:NiftyManiac/Sandbox/TemplateDualImage|
premium=File:Quickstart-finder.png|
classic=File:Quickstart-finder-partial.png
}}

{{User:NiftyManiac/Sandbox/TemplateDualImage|
premium=File:Quickstart-finder.png|
classic=File:Quickstart-finder-partial.png|
caption=My caption|
width=100px
}}

:This looks nice to me! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:30, 2 January 2023 (UTC)

: Good initiative. From the top of my head:
:* I suggest using a shorthand, no one wants to type 'Premium-classic thumb image'.
:* If we end up using toggle for infoboxes (not sure where we headed there), then I agree definitely same custom toggle class should be used for all, thus allowing to switch premium-classic view on the whole page at a click.
:* The button part on a separate row isn't pretty, creating a lot of dead space that can be used by the text. Are we set on the label 'toggle ascii'? Classic isn't Ascii per se, maybe we can use a 'toggle' with a tooltip {{tooltip|for example|does bla bla bla}}, or maybe we can get rid of the text and have a smaller icon button ([[User:Jan/sandbox#Metal_example|two examples]]).
: I hope that helps. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 11:21, 2 January 2023 (UTC)

:: I added [[Template:Dual image]] with some of your suggestions. Agree that it's not super pretty, feel free to try something different.

::* I put the toggle in the caption mostly because I gave up on trying to make a more sophisticated replacement for the default thumb image behavior, I'm sure someone with better wiki-fu could put together something more intelligent.
::* I cut the text down to just "Toggle"; I think the best solution would be a small graphic showing the old and new dwarf icons with arrows between them. [[User:NiftyManiac|NiftyManiac]] ([[User talk:NiftyManiac|talk]]) 19:21, 2 January 2023 (UTC)

{{Dual image|
premium=File:DFwiki5by53by3farm.png|
classic=File:Quickstart_layout_3.png|
width=100px|
caption=A 5x5 room with a 3x3 farm plot
}}
::: I updated the layout, now it should look just like a regular image thumb. I didn't had time to test it, if it doesn't work for you or you don't like it just revert the last change. cheers. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 21:46, 2 January 2023 (UTC)
::::I don't know which part of this talk page to put this, but I added the ability to add icons to the v50 workshops template. Leaving the icon part blank will not break the template in any way. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 09:47, 3 January 2023 (UTC)
{{clear}}
==Creature List Now Supports Graphics!==
I wasn't easy, but I made new templates so the [[Creature]]s page now supports both graphics sprites ''and'' ASCII tiles. Allow me to show you:

{{v50_creaturecurrent_table_head}}
{{v50_creaturecurrent table row|graphic=[[File:dwarf_sprite.png]]|name=[[Dwarf]]|symbol=☺|color=3:0:0|playable=Fort, Adv|hostile=No|food=No|size=60,000|value=Not tameable|biome=[[Mountain halls]], [[Fortress|dwarf fortress]]es, [[hillock]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:elf_sprite.png]]|name=[[Elf]]|symbol=e|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=60,000|value=Not tameable|biome=[[Forest retreat]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:human_sprite.png]]|name=[[Human]]|symbol=U|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=70,000|value=Not tameable|biome=[[Town]]s and cities|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:goblin_sprite.png]]|name=[[Goblin]]|symbol=g|color=7:0:0|playable=Adv|hostile=Usually1|food=No|size=60,000|value=Not tameable|biome=[[Dark fortress]]es and [[dark pit]]s|note=Snatchers2}}
{{v50_creaturecurrent table row|graphic=[[File:kobold_sprite.png]]|name=[[Kobold]]|symbol=k|color=6:0:0|playable=Adv|hostile=Usually1|food=No|size=20,000|value=Not tameable|biome=Caves|note=Skulking race}}
|}

Oh wait, there's a bonus. You can also modify the background color of the box the sprites go in. I added that to make possibly-hard-to-see-otherwise sprites more easy to see - depending on the colors it has. Allow me to demonstrate.

{{v50_creaturecurrent_table_head}}
{{v50_creaturecurrent table row|graphic=[[File:dwarf_sprite.png]]|bgcolor=#829ccc|name=[[Dwarf]]|symbol=☺|color=3:0:0|playable=Fort, Adv|hostile=No|food=No|size=60,000|value=Not tameable|biome=[[Mountain halls]], [[Fortress|dwarf fortress]]es, [[hillock]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:elf_sprite.png]]|bgcolor=#c7dfc0|name=[[Elf]]|symbol=e|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=60,000|value=Not tameable|biome=[[Forest retreat]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:human_sprite.png]]|bgcolor=#c7dfc0|name=[[Human]]|symbol=U|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=70,000|value=Not tameable|biome=[[Town]]s and cities|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:goblin_sprite.png]]|bgcolor=#dfc0c0|name=[[Goblin]]|symbol=g|color=7:0:0|playable=Adv|hostile=Usually1|food=No|size=60,000|value=Not tameable|biome=[[Dark fortress]]es and [[dark pit]]s|note=Snatchers2}}
{{v50_creaturecurrent table row|graphic=[[File:kobold_sprite.png]]|bgcolor=#dfc0c0|name=[[Kobold]]|symbol=k|color=6:0:0|playable=Adv|hostile=Usually1|food=No|size=20,000|value=Not tameable|biome=Caves|note=Skulking race}}
|}

To change the background color, add <code><nowiki>|bgcolor=COLOR</nowiki></code> segment after the <code><nowiki>|graphic</nowiki></code> part. You can use color names or HTML hex color codes. I added this to the v50 creatures page, but at this time, I only added the first five creatures I just displayed. It's gonna take a while to find ALL of those creature sprites. I hope a lot of people help out on that one. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 05:29, 5 January 2023 (UTC)

:Thanks, looks nice! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:44, 5 January 2023 (UTC)
:Nice stuff, took the quick liberty to change the padding-left -> text-align to make all the sprites center aligned relative to each other :) Sweet work --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 17:41, 5 January 2023 (UTC)
:: Good work indeed. One minor issue, is that all the sprites have different sizes, which sometimes create slight variation in table row height. Consider using capping the image size vertically for example <code><nowiki>[[File:dwarf_sprite.png|x32px]]</nowiki></code>--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:15, 5 January 2023 (UTC)
:: Also often in such tables people want to click on the image to go for the specific entry, and often will try to click on the very first thing they see in line the thumb image, but currently that will take them to the file page. Consider adding link parameter for example: <code><nowiki>[[File:dwarf_sprite.png|x32px|link=dwarf]]</nowiki></code> [[File:dwarf_sprite.png|x32px|link=dwarf]] or no link at all <code><nowiki>[[File:dwarf_sprite.png|x32px|link=]]</nowiki></code> [[File:dwarf_sprite.png|x32px|link=]] --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:24, 5 January 2023 (UTC)
::: I mean... Yeah, I could do that. I think that lessens the quality of the sprite a bit because it makes edges blurry, but either way is fine. I could have sworn I added a link for all those images the first time. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 03:23, 6 January 2023 (UTC)
::::Since we are adding pixel art sprites to the website it might be convincing to add a global class like .sprite or .pixel-image that uses the CSS attribute `image-rendering: pixelated;` in order to prevent blurryness when scaling the image up/down. Just a thought --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 09:40, 6 January 2023 (UTC)
:::::Are we able to attach classes directly to images? If so, we can probably attach inline styles directly as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:52, 6 January 2023 (UTC)
::::::Looks like (without an extension) MediaWiki only supports classes on images: [[File:dwarf_sprite.png|x32px|class=pixelated]] and not styles: [[File:dwarf_sprite.png|x32px|style="image-rendering: pixelated;"]] it just treats it as alt text it looks like? Wrapping it in a div works and demonstrates the difference: <div style="image-rendering: pixelated;display:inline;">[[File:dwarf_sprite.png|64px]]</div> [[File:dwarf_sprite.png|64px|inline]]. Speaking from experience, however, image-rendering needs a browser specific prefix in certain browsers (safari, for example) in order to work properly. I'm not entirely sure what the best "MediaWiki" practice is for adding something like this but I would assume it's a simple class in common.css for now. --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 17:17, 6 January 2023 (UTC)
:::::::Ah, yeah, you are correct, I should have checked https://www.mediawiki.org/wiki/Help:Images. I'd be fine adding a class like that to common.css. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:27, 6 January 2023 (UTC)
::::::::Great, in that case if no one is opposed we can add `.game-sprite` or something like that? See below for the CSS, the order of the attributes is relevant. --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 18:23, 6 January 2023 (UTC)
<pre>/* Used for pixel-art images from the game so they can be resized and maintain crisp pixel edges. */
.game-sprite {
image-rendering: -webkit-optimize-contrast;
image-rendering: crisp-edges;
image-rendering: pixelated;
}</pre>
:::::::::So... you guys think each creature page should show the main sprite(s) alone, or should it show the baby versions alongside them? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 08:37, 8 January 2023 (UTC)
::::::::::I think adult + baby is sensible, the adult + baby + zombie was not, in retrospect. So yeah adult + baby (if there is one) from now on would be my vote. --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 23:27, 8 January 2023 (UTC)
{{outdent}}
Well then, there's a TON of creatures to go - and I mean both the [[creature]]s page and the individual creature pages. I really hope everyone can pull their weight on that those images. The spritesheets are easy to find, and if you know how to read the .txt files near them, finding sprites on certain rows and columns should be a breeze. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 00:47, 9 January 2023 (UTC)
:Zippy, are you doing all of this by hand? That seems quite tedious. Cutting up the spritesheets can be done automatically. Renaming and updating the table could be done with a script and/or chatgpt. We'd need Lethosor to add the [https://www.mediawiki.org/wiki/Extension:SimpleBatchUpload batch upload extension] though. Maybe some manual work in updating names to match article names rather than raws. [[User:OddballJoe|OddballJoe]] ([[User talk:OddballJoe|talk]]) 06:55, 9 January 2023 (UTC)
{{clear}}

So did the graphic people gained insights and reached some sort of consensus? are we using big up scaled images + toggle? multiple images to(adult + baby)? anything else? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 00:32, 10 January 2023 (UTC)

=== Graphics in Skill Infoboxes ===
{{v50_skill
| color = 7:0
| graphic = [[File:miner_sprite_icon.png]]
| skill = Miner
| profession = Miner
| job name = [[Mining]]
| tasks =
* [[Dig]]
| attributes =
* Strength
* Toughness
* Endurance
* Willpower
* Spatial Sense
* Kinesthetic Sense}}I've made yet another visual prototype for skills. In other words, we can put sprites of matching dwarves (and possibly humans, elves, goblins, etc.) at the top of infoboxes. If multiple images are put up there, that can mess up the alignment, but don't worry, Zippy thought of that. <code><nowiki>|graphicmargin</nowiki></code> can added, and a percentage or a "px" number can be placed in that parameter to fix it. If you leave said parameter out, the alignment will default to about 42% from the left. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 06:06, 7 January 2023 (UTC)
<pre><nowiki>
{{v50_skill
| color = 7:0
| graphic = [[File:miner_sprite_icon.png]]
| graphicmargin = (OPTIONAL)
| skill = Miner
| profession = Miner
| job name = [[Mining]]
| tasks =
* [[Dig]]
| attributes =
* Strength
* Toughness
* Endurance
* Willpower
* Spatial Sense
* Kinesthetic Sense}}
</nowiki></pre>
::Not sure I understand the alignment issue, can you not put text-align: center on the parent table element instead of messing with explicit margins? As another sidenote, should we continue to be naming all of these templates v50_x, I find that a bit confusing. Why not just edit the main templates with the additional information. Loving all the new templates though nice work Zippy :) --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 11:43, 7 January 2023 (UTC)
:::No, text-align doesn't work with images and divs. That just works for text. When it comes to images, you got to put a little "finesse" on the CSS with those. As for editing the classic templates with the new info, it doesn't always work that way with ''every'' template. Lethosor I think ''did'' update the creature infobox template in the way you mentioned. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 08:37, 8 January 2023 (UTC)
:::: You can use something like this to automatically handle that--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 08:56, 8 January 2023 (UTC)
{|
|-
|<div style="width:200px; display:flex; background-color:#eaecf0;">
[[File:miner_sprite_icon.png|center]]
<div>
|<div style="width:200px; display:flex; background-color:#eaecf0;">
[[File:miner_sprite_icon.png|center]] [[File:miner_sprite_icon.png|center]]
<div>
|<div style="width:200px; display:flex; background-color:#eaecf0;">
[[File:miner_sprite_icon.png|center]] [[File:miner_sprite_icon.png|center]] [[File:miner_sprite_icon.png|center]]
<div>
|}
:::::Hah I am very familar with the CSS finese :P Can you show me an example of a multi-sprite job infobox? I said what I said because I tested my proposed solution and it worked fine :)

Dwarf Fortress Wiki talk:Versions

2023-01-10T00:32:44Z

Jan: /* Creature List Now Supports Graphics! */

{{archive|
# [[DF Talk:Versions/Archive 1|Page 1]]}}

== Version 0.31.19 starts a new DF generation? ==

My reading of Toady's comments on the release of 0.31.19 is that it came out basically because he felt it would take too long to get DF all the way to 0.32. With the ore changes, the sitefinder changes, the addition of grazing and several different industries, there's a lot of changes between 31.18 and 31.19. So I'm thinking it might be a good idea to call it the first release of DF2011 - and what we refer to as "DF2010" would then become 0.31.18.

Thoughts? --[[User:DeMatt|DeMatt]] 07:06, 28 February 2011 (UTC)

==Revisiting Redirects==
I wasn't around when the redirect policy was created, and I'm having trouble understanding the rationale. The example claims that linking [[Main:Cheese]] to [[cv:Cheese maker]] is problematic...but mainspace only ever redirects to the current version. If the best target in the current version is cheese maker, why not link to it directly? (It's not, at least for Cheese, since [[DF2012:Cheese]] exists now.) The explanation seems to be claiming that 40d articles that link to Cheese will follow the Mainspace link--but that hasn't been the case for a long while now. Articles in 40d automatically link against other articles in 40d, so that version remains internally consistent no matter where mainspace links to in the current version. For a current example, what do we gain by linking [[Main:Mead]] to [[cv:Mead]] and linking [[DF2012:Mead]] to [[DF2012:Alcohol]]?

If this really is just an outdated procedure, I recommend we drop the mummery and allow mainspace to link to cv:(best target). Double redirects ''may'' work (sometimes, but [[Main:Mead]] demonstrates a common problem where automatic redirection fails), but if they are unnecessary I think they should be avoided, partly because of problems like [[Main:Mead]] and partly because of the effort required to protect double redirects from users who believe they are problematic.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:16, 8 January 2014 (UTC)

:I was just thinking that. I'm currently attempting to write a basic extension to eliminate the need for mainspace redirects entirely, although Mediawiki's class structure may make this more difficult than I had hoped (the only method I've found for resolving redirects takes the ''article text'' instead of a title, e.g. "#REDIRECT ..."). I do agree that the current situation with redirects isn't ideal, so I'm hoping this will work better (once I get it to work). --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:42, 8 January 2014 (UTC)

Okay, that wasn't quite as clear as I meant it to be. In general, I think this is a tricky situation. Mediawiki wasn't designed to have five content namespaces, and certainly not chains of redirects between them. The problem that was pointed out in the [[DF:REDIR|policy]] is the fact that with:
Main:Foo -> cv:Bar
pages in the cv: namespace can't use [[<nowiki/>foo]], since the namespace links modification causes it to be treated as [[<nowiki/>cv:foo]] instead, which doesn't exist. The current suggested solution is this:
Main:Foo -> cv:Foo -> cv:Bar
This fixes the problem of [[<nowiki/>foo]] not working on cv pages, but creates issues with double redirects not always working. Another solution, which is more intuitive to new editors, is:
Main:Foo -> cv:Bar
cv:Foo -> cv:Bar
Both require creating two redirects. The first method has the advantage of ''ensuring'' that the cv redirect exists (otherwise, main:foo would be a redlink), while the second has the advantage of working more reliably in a couple cases.

What I'm trying to do is make main:Foo "jump" to cv:Foo when cv:foo exists, ''even if main:foo doesn't exist'' (basically it would treat all mainspace pages as redirects to cv pages, but only if the cv page exists and not the mainspace page). I had main:Bar jumping to cv:Bar fine, but if cv:Foo redirected to cv:Bar, accessing main:Foo would mysteriously stop at cv:Foo even if I increased the redirect limit. What I'm trying to do now is follow the redirects internally, without relying on Mediawiki to do it automatically - unfortunately, that has proved to be harder than I had hoped (and I sent my web server into an infinite loop while trying). I will try to work on this some more when I get a chance, although I'm not sure when that'll be yet :(. For now, feel free to fix broken double mainspace redirects as necessary, as long as redirects in the DF2012 namespace stay pointing to the right page (and new mainspace redirects get added in the DF2012 namespace too). --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:21, 9 January 2014 (UTC)

:You're treating cv like a namespace--it's not. It is simply shorthand for "fill in the current version here". [http://dwarffortresswiki.org/index.php?title=User_talk:Briess&diff=182404&oldid=181281 As I discovered a long time ago on a server not far away], linking from Main:Foo to cv:Foo tends to break redirection chains. If, instead of linking to cv:Foo, you link to DF2012:Foo, it might just work. It would, of course, be better if your patch could evaluate cv itself, but even if you have to hardcode the current version it's a single point of maintenance that requires update very infrequently. (For that matter, we could probably dispense with the cv hack entirely and just have a bot update mainspace links from DF2012 to DF201X when we switch to a new version.)--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:05, 9 January 2014 (UTC)
::I know cv isn't a namespace - I was just trying to avoid future confusion when the DF2012 namespace changes. It's interesting that changing "cv" to "DF2012" fixes some broken redirects, although I've found that simply making an edit to a broken redirect can usually fix it as well. I've actually had the most problems with double redirects when the second one (in the DF2012 namespace) doesn't use the DF2012 prefix (e.g. main:Foo containing <nowiki>[[cv:Foo]] and DF2012:Foo containing [[Bar]]</nowiki>). I'd rather keep the cv alias even if it isn't necessary for mainspace redirects when I get the patch to work, since it makes it easier to refer to the current version of the page (for example, several MDF articles contain links to a vanilla page for things that don't change in the mod).
::Also, using aliases like "cv" is supported by Mediawiki; in fact, several WMF wikis use them (for example, "[[wikipedia:WP:Redirects|WP:Redirects]]" on Wikipedia). It's quite likely that Mediawiki isn't processing double redirects using aliases correctly, though, since that's uncommon on most wikis. --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:35, 9 January 2014 (UTC)

In light of the lack of support for the current redirect policy, I propose we replace the current redirect section with:

:Mainspace article pages should use the cv: alias when redirecting to a versioned page, which will automatically update the link when a new version is released. For example, page "Main:Foo" should redirect to page "cv:Bar" (where "Bar" is the page that best describes the topic Foo in the current version).

:Pages in mainspace should only redirect to an older versioned page if that content no longer exists in the current version of the game (e.g. [[Cave river]], [[Chunk]]). In these cases the cv: alias cannot be used.

:Pages inside a versioned namespace should not use the cv: alias. Instead, they should redirect to the best page within that versioned namespace (e.g. [[DF2012:Dodging]], [[v0.31:Drink]]).

:Due to limitations of the wiki software, double redirects should be avoided if possible. When fixing double redirects in mainspace, please make sure to use the cv: alias as appropriate.

If no one objects, I will make this change in a few days.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:21, 15 January 2014 (UTC)

:Okay with me. It may be worth mentioning that double redirects only really need to be changed when they don't work (since changing a lot of redirects that work isn't necessary), but I think it's clearer and more relevant than the current policy. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:26, 16 January 2014 (UTC)

Done.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:55, 22 January 2014 (UTC)

I was finally able to get my extension to work after being motivated by one too many malfunctioning redirects. It now causes nonexistent pages in the main namespace to behave exactly like redirects to their DF2012 counterparts (when linked to, accessed directly, and transcluded). Double redirects also work (up to 100, in fact, although that was a temporary safety measure that I'll probably change). This means we'll be able to safely get rid of all mainspace redirects (redirects that redirect to something other than "cv" will still function if not deleted). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:20, 14 March 2014 (UTC)
:What about articles which don't exist in the current version but do exist in older versions? Will those still need mainspace redirects, or will your extension be able to automatically redirect them to v0.31/40d/23a? --[[User:Quietust|Quietust]] ([[User talk:Quietust|talk]]) 01:29, 14 March 2014 (UTC)
::It ignores all mainspace pages that actually have content, including redirects, so pages like [[masons guild]] won't be affected (unless deleted). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:47, 14 March 2014 (UTC)

Done and deployed. [[Cat]] is still treated as a redirect, even though I just deleted it (try clicking on the "redirected from" link). Pages that exist are ignored, so [[Masons guild]] and [[History of Dwarf Fortress]] still function normally (as a redirect to a 23a page and a non-redirect, respectively). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 18:57, 14 April 2014 (UTC)

I'm sending around a bot right now to delete all redirects of the format "foo -> cv:foo" (a surprising number don't fit this format, so I'm leaving them alone for now). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:43, 14 April 2014 (UTC)

:I'm confused. Do we use double redirects or not? Is there a single place we define our linking policy (including redirects), and is it updated?
:I had trouble linking to [[Consolidated_development]] in [[v0.34:Dragon]]. It kept pointing to v0.34:Consolidated_development, which does not exist. I ended up linking to Main:Consolidated_development to make it work. --[[User:Nahno|Nahno]] ([[User talk:Nahno|talk]]) 10:18, 1 July 2014 (UTC)

::That's a separate problem altogether - links in the versioned namespaces (v0.34, v0.31, 40d, 23a) automatically link to pages within their namespace. I may be able to set up a fallback to mainspace once I'm able to deploy again, but for now the "main:" alias is the intended solution. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 11:36, 1 July 2014 (UTC)

== Google often directs people to the 0.31 page ==

I've noticed a couple of times that finding a wiki page from an external search will often drop me onto a page from an older version. Is it possible to mitigate this somehow for new players? I could imagine something like redirecting old:Bar -> cv:Bar unless the user has come from old:Foo; no idea if that would actually work though. [[User:PeridexisErrant|PeridexisErrant]] ([[User talk:PeridexisErrant|talk]]) 11:48, 4 May 2014 (UTC)

:As a temporary solution, I could write a script that displays a banner of some kind if the user came from an external site. I'll ask Briess if he can do anything on the server level to increase the weighting of the current version's pages. (Obviously there are situations where people are looking for old pages, like [[23a:dungeon master]], so we don't want to disable indexing entirely on old pages.) —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:03, 4 May 2014 (UTC)

== DF2014? ==

As Toady [http://www.bay12games.com/dwarves/ draws closer to a new release], it might be worthwhile to discuss the addition of a new version to the wiki. The upcoming release covers two years of changes and introduces a number of new plants, foods, drinks, multi-tile trees, climbing, jumping, etc., so it is likely to have significant changes from the current DF2012. To avoid having people start new pages (and lose all the effort spent refining the prior version's page), I think it would be best to have a bot automatically copy over the DF2012 pages as a starting point for DF2014. I would suggest that these copied pages include a noticebox template mentioning that the content may be outdated, so that we can easily track which pages have been reviewed. I think either the {{tl|version check}} or {{tl|old}} template would work. --[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 19:43, 5 May 2014 (UTC)

:This is what [[User:QuietBot]] did after the 0.34 release, so it's certainly possible to use the same script to migrate to DF2014. I would like a way of tagging migrated pages, since inaccuracies in some pages went unnoticed for months after they were migrated. Since {{tl|old}} is already in use, {{tl|version check}} may be a better solution (it can be reworded slightly, or we can make a separate template for DF2014 migration). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:23, 1 June 2014 (UTC)
:Made [[Template:DF2014 migrated]] as an example. Any thoughts? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:32, 1 June 2014 (UTC)

== Redirects inconsistency ==

Following a redirect is supposed to be exactly the same as going straight to the page it redirects to, but this actually isn't the case:
* Go to [[Seeds]] and you get [[v0.34:Seed]] (outdated)
* Go to http://dwarffortresswiki.org/index.php?title=Seeds&redirect=no and click on the link and you get to [[DF2014:Seed]] (current)
So if you search for "seed", the top result is the DF2014 version. But search for "seeds" and you get the redirect, which sends you to the outdated page instead. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 23:22, 22 February 2015 (UTC)

While I'm talking about redirects, it seems redirects to sections don't work: see [[DF2014:How do I manage my seeds and crops]]. I know MediaWiki is capable of this trick because Wikipedia does it. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 23:32, 22 February 2015 (UTC)

:I have absolutely no idea why [[seeds]] redirects to a v0.34 page - it could be a Mediawiki bug. The section links issue is due to a known issue in the redirect extension we use, which has yet to be fixed. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:01, 23 February 2015 (UTC)
:It looks like deleting both [[Seeds]] and [[DF2014:Seeds]] fixed things (by allowing AutoRedirect to handle the redirects instead). Feel free to tag any others with {{tl|bad redirect}}. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:03, 23 February 2015 (UTC)
::It gets stranger. [[Vial]] redirects explicitly to [[cv:Flask]] which displays (when you look at it with &redirect=no) as [[DF2014:Flask]], but still goes to the v0.34 version. It seems redirects interpret the cv: pseudo-namespace (or whatever it's called) in an outdated way. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 18:08, 23 February 2015 (UTC)
::I've added a note to this page about this issue. If it gets resolved, the note should be removed. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 21:04, 23 February 2015 (UTC)

==Reorganizing versions==

The internet deals with moved content... poorly. Google is still linking to v0.34 pages more than a year after the switch to "DF2014", and even the wiki software still has cached links pointing to the old version pages.

I propose reorganizing versions on the wiki to avoid moving content whenever possible. Instead of having a temporary "current version" namespace that changes occasionally, all the current information gets promoted to the Main namespace. When the next version split occurs, the Main articles as of a certain revision number can be copied to the newly-created permanent "old version" namespace, while all the current information remains in Main. This not only fixes the link rot issue, but it has a few other benefits as well: fewer administrative tasks, no lockdown (a historical version of the Main pages can be copied at any point, even if the Main articles are already modified for the new version), almost all the article history is maintained in the Main article (instead of being spread unevenly across multiple versions), no "temporary" namespaces are needed, fewer problematic long redirect chains, and hopefully less user confusion (since Main gets priority in search results, etc.).

As an example, today we would not have a DF2014 namespace (which is good because "temporary" namespaces historically disappear anyway). If you ran a search for [[seed]] you'd end up at Main:seed, which would have all the current information on seeds. The version box at the top of the page would still link to the older versions of the seed article. When a new version is released, an admin would choose a revision number and copy the Main:seed article as it exists at that revision number to v0.40:seed. That's it. One historical copy that needs little to no new editing, and zero redirections/moves.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 19:02, 27 July 2015 (UTC)

:Makes sense to me. It would involve a lot of work, though (e.g. fixing templates and categories to account for the current version being in mainspace), although that should be doable thanks to {{tl|category}}, {{tl|version switch}}, etc.. A bot could be set up to copy revisions from before a release date as well, which would be more difficult (and maybe slower) than a direct copy, but not severely. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:24, 30 July 2015 (UTC)

:Actually, there are a few issues with that, namely that there wouldn't be an easy way to distinguish between versioned and non-versioned mainspace pages. There are ways to resolve Google search priority (we can exclude pages from older versions from search engine results if there are newer versions of those pages available, for example). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:47, 6 August 2015 (UTC)

::There aren't very many non-versioned mainspace pages, and determining if a page is versioned is as simple as looking for the version template and/or categories added by the version template (e.g. copy [http://dwarffortresswiki.org/index.php/Category:Current this category] instead of Main:*). The problem with "suggesting" newer pages to Google is that they obviously aren't crawling our wiki regularly (if they were, the fact that the mainspace redirects point to new pages would automatically be picked up). Even if your Google hints worked they wouldn't do anything for all the other broken links out on the 'net.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:35, 6 August 2015 (UTC)

::: Google actually crawls the wiki constantly - we probably get crawl hits from google for a continuous block of 2-3 hours per day, each and every day. Why they are slow to update is beyond me though. I can't remember why we didn't do this initially, but there was a technical limitation involved if I remember correctly. --[[User:Briess|Briess]] ([[User talk:Briess|talk]]) 22:05, 6 August 2015 (UTC)

::: There are <meta> tags that can be used to hide pages from search results (for search engines that recognize them, that is). Searching for {{tl|av}} or [[:Category:Current]] might work, although we'd have to make sure all of the DF2014 pages include that (some pages don't, particularly some disambiguation pages, although all of them should). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:53, 6 August 2015 (UTC)

:Is there a particular reason main and current are separate to begin with?—[[User:CLA|CLA]] ([[User talk:CLA|talk]]) 00:17, 7 August 2015 (UTC)

::It's mostly intended to distinguish between versioned and non-versioned pages and make version-related templates simpler to work with, since every versioned page has a namespace. I wasn't active here in 2010 when this system was created, so Briess and Emi would know more.
::Another issue I just thought of with Loci's suggestion is categories - currently, categories like [[:Category:Animals]] are used to organize the versioned sub-categories. Sure, we can change {{tl|Category}} to categorize mainspace pages in [[:Category:v0.40:Animals]] or [[:Category:DF2014:Animals]], but that would be less straightforward because there wouldn't be a namespace with that name (until pages are migrated when a newer major version is released). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 13:05, 7 August 2015 (UTC)

:Moving current pages to the main namespace sounds like a great idea. -[[User:Jecowa|Jecowa]] ([[User talk:Jecowa|talk]]) 20:47, 4 January 2018 (UTC)

Another thought: dealing with migrating redirects could be difficult with this proposal - specifically, determining which redirects should be migrated to a versioned namespace. Redirects can't contain {{tl|av}}, at least not before ``#REDIRECT``. I ''think'' it would be possible to copy pages in two stages, though - all non-redirects first, then all redirects whose targets were also copied. Thoughts? Anything I'm missing? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:41, 27 June 2019 (UTC)

Some subpages (particularly /raw and /Edit notice) also deliberately lack {{tl|av}}, although those shouldn't be too hard to handle. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:35, 9 July 2019 (UTC)

:Redirect pages (and all other edge cases I've looked at) can be included in categories (like [[:Category:Current]]) to determine whether or not they should be copied into an archival version. But if the redirects are "properly qualified" then they can all be copied over blindly. Mainspace redirects pointing to versioned information should use a blank namespace (which will be automatically constrained to the archival namespace); mainspace redirects pointing to unversioned information should use an explicit "Main" (which will automatically link back to the unversioned page). Then, when [[[[Toady]]]] gets copied to [[[[v0.4x:Toady]]]] it will point back to [[[[Main:Toady One]]]]. Meanwhile, [[[[Beer]]]], copied to [[[[v0.4x:Beer]]]], will properly point to [[[[v0.4x:Alcohol]]]].--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:00, 14 July 2019 (UTC)

::I think qualifying redirects is the best solution here - categorizing redirects manually is another possible source of errors, since categories (or a lack thereof) would only be visible on the redirect page itself, and [[:Category:Current]] is a hidden category. Copying over mainspace redirects into versioned namespaces would also resolve some issues that have come up due to those not reliably existing currently. I should be able to set up a bot script to add "main:" to current mainspace redirects (and it shouldn't break anything, since those redirects go to other mainspace pages anyway). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:57, 14 July 2019 (UTC)

(Note: I wrote all of this without noticing the previous discussion above.) I was wondering, when the wiki creates a new namespace for a major release again, if it is possible to ''not'' create a namespace for the next current version (e.g. "DF202x") and instead have the mainspace articles (which are currently redirects) become the new cv and move the content there. Therefore, [[cv:Cat]] would just be "[[Cat]]" (or [[Main:Cat]]).

Certain namespace-related templates like [[Template:Ns/0]] would need to be changed, though nothing significant as far as I know. For most cases, any "DF2014" would be replaced with "Main" or even blank. There's also multiple extensions handling the current namespace system and they may need to be modified too, though I'm not sure if or how much. I'm guessing based on the discussions above that it will change stuff up.

My reason is the current namespace is increasingly becoming more anachronistic. "DF2014" could be misinterpreted as "this page is about the 2014 version of the game" or "this page was last updated in 2014", which I've seen a few people in forums mention. Granted that [[Template:Av]] is on the top of very article, I still think the namespace is inconsistent with the recentness of the article. But how is this related to what I'm asking for? Let's say we continue the current system: if we happen to do a new namespace change this year and create DF2020, the next major release (after graphics/UI) will be mythgen, which is estimated to take several years to develop (the Big Wait), and so the anachronism will start over again. The proposed way will prevent this from occurring for the next major release and every release thereafter.

I think the confusion with having a namespace that becomes old-fashioned overtime supersedes the confusion with not marking current versioned articles with a namespace. Most users just search "Cat" on the search bar and naturally expect to get information about the latest release of DF. So if users go a page that's just titled "Cat", they won't expect outdated info about cats from a previous release. That's how the current system works anyways. We'll be skipping the two-step process that we have now. It'll make several wiki tasks much simpler as well. Editors can create new articles for current versions without remembering to add a namespace. It'll fix any existing issues with (double) redirects; instead of [[Main:Kitten]] redirecting to [[cv:Kitten]], which goes to [[DF2014:Kitten]], which then redirects to [[DF2014:Cat]], [[Main:Kitten]] would just redirect to [[Main:Cat]]. And the cv: alias will no longer be necessary since "cv:" = "Main:" and will be forever.

There's no need to differentiate the current version and previous versions with a namespace for the current version is what I'm saying. Articles of previous versions will retain their respective namespaces. Users will still type "40d:Cat" to go to the 40d version of the article, but if they want the current version, they'll just type "Cat" (like now). The mainspace containing the "live" version of an article is natural and would create no uncertainty when browsing the wiki. And it would simplify the wiki somewhat and future-proof this anachronism problem. As a bonus, this change will also prevent web search engines from showing previous version pages when typing "DF cat" or something. (This isn't happening right now as DF2014 has been the current namespace for ~6 years, but it'll happen again when everything moves to a new namespace.)

This is the gist of it, and I may have ignored most of the problems with this proposal. I have personally wished for the whole version namespacing be made less complicated and have been seeking for a solution, and I feel like this is the best way to go about in the future. – [[User:Doorkeeper|Doorkeeper]] 21:27, 14 August 2020 (UTC)

:<s>Whoops, looks like Loci already proposed this exact thing long ago. I definitely missed that discussion and should have checked first. My apologies. I'll move my text to that section and remove this one. – [[User:Doorkeeper|Doorkeeper]] 21:36, 14 August 2020 (UTC)</s> Done. – [[User:Doorkeeper|Doorkeeper]] 21:40, 14 August 2020 (UTC)

:The main issue I have with that is that putting pages about the current version in a namespace also differentiates between those pages and pages not about ''any'' version (for example, [[Toady One]] does not need a 40d or v0.34 page). Yes, we can use {{tl|av}} to mark versioned pages, but people often forget to add that to new pages. The current system also allows determining whether a page is versioned or not from its title, which makes migrations a lot faster. Relying on {{tl|av}} would require either reading the content of every page (which would slow scripts down significantly) or cross-checking with the list of all pages including the template (feasible, but a bit more complicated, and still susceptible to missing templates). I suppose that manually fixing and migrating pages missing {{tl|av}} later wouldn't be too much work, though.
:I am definitely in favor of changing "DF2014" (or a new namespace) to "Current", though. I was in favor of "DF2014" in 2014, but I don't think it makes sense anymore, and "Current" seemed to be a popular alternative in both the DF2012 and DF2014 discussions on the matter. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:02, 16 August 2020 (UTC)

== Weird redirect behaviour ==

[[Pump stack]] redirects to [[cv:Screw pump#Pump stack]]. If you look at the redirect itself it says it redirects to DF2014 namespace, which is correct. But if you actually follow the redirect, it goes to v0.34 namespace. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 16:10, 20 August 2018 (UTC)
:Yeah, that's part of the issue described in the above section (the wiki caching part, not on Google's end.) —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 15:00, 21 August 2018 (UTC)

== v50 organization ==

Some wiki admins have had a talk on Discord and decided that the most sustainable path forward is to put content for all future versions of DF in the main namespace. We will be working on a bot to do this in the next few days. Feel free to chime in with suggestions here. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:56, 14 December 2022 (UTC)

:Is it maybe possible to do backwards-namespacing? Like we have a "Main" namespace, which people are free to update, and whenever there's a new version of DF the "Main" namespace is copied into a namespace for the then old version, much like how you'd branch a stable branch from a development branch when working with a git-project? [[User:Therahedwig|Therahedwig]] ([[User talk:Therahedwig|talk]]) 23:13, 14 December 2022 (UTC)

::Yeah, we could do that if we decide to. We were talking about doing that for v50, actually, and might still do something similar to preserve edit history if it doesn't end up being too hard to automate. Our hope is that we will not introduce new namespaces for v50 -> v5x, unless there is a serious breaking change (and hopefully there isn't one). But if we change our mind, one advantage of the type of migration you mentioned is that it can be done retroactively - we can copy historical revisions that were current at the time of the release, and would only lose some typo fixes made after the release that apply to earlier versions as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:11, 15 December 2022 (UTC)

ETA is < 24 hours. Doing some final checks on a migration script. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 07:08, 19 December 2022 (UTC)

: We should really have a task list as there are many things that change and need updating. Including but not limited to:
:* Most templates that used the previous namespace convention broke, including nav templates.
:* Many game files changed locations and their pages need to be updated.
:* Raws need to be updated.
:* Various features added, changed, removed.
:* UI has been changed -- though I am more inclined to wait for classic release to avoid extra work --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 06:56, 20 December 2022 (UTC)

"''Raws need to be updated.''" Including applying text wraparound where necessary, I suppose - more than a few of them have proven to be that special kind of...''difficult'' to navigate otherwise, shall we say? [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 12:52, 20 December 2022 (UTC)

:There is already a task list in the [[#v50 migration|section below]] that includes templates and raws, with an explanation. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:25, 20 December 2022 (UTC)

== v50 migration ==

The initial migration script is done. New content is in the '''main''' namespace, e.g. [[Cat]]. Old content is still at [[DF2014:Cat]]. History was migrated to the ''new'' (main namespace) articles.

I know several things are broken still. Please reply if you find any others:
<div style="border-left: 2px solid red">
* <s>Versioned templates haven't been migrated yet (e.g. {{tl|vermin}} on [[Ant]])</s>
** Fixed. Most were migrated by a bot.
* <s>Raws are missing on all pages that use them.</s>
** This also affects sidebars, such as on [[Cat]] and [[Microcline]].
** Update: The DFRawFunctions extension has been upgraded to include v50 raws, using the "v50:" prefix for filenames instead of "DF2014:". <s>I haven't finished a migration script to create the /raw pages themselves, but they can typically be created manually by copying the DF2014 /raw pages and changing "DF2014" to "v50" everywhere.</s> —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:20, 1 January 2023 (UTC)
** Update 2: Raws have been added for all pages! They were copied from the "DF2014" pages and had "DF2014" replaced with "v50", which appears to have worked from a spot-check, but let me know if you find any problems. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:57, 4 January 2023 (UTC)
* Some pages where the DF2014 page was a redirect to a main namespace page that contained content were migrated incorrectly.
** In this case, the main namespace page is usually a redirect to itself. This can be fixed by undoing LethosorBot's edit to the main namespace page, then copying the content to the DF2014 page.
** Update: most seem to have been fixed manually - thanks! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:41, 21 December 2022 (UTC)
* <s>Some main-namespace talk pages redirect to DF2014 talk pages. Some of these redirects work, and some (usually older ones) do not.</s>
** Fixed with a bot. Some redirects from talk pages to other deleted talk pages are now broken, e.g. [[Talk:Above_ground]] (exists) -> [[Talk:Tile attributes]] (redlink). I am leaving them like that because they redirect to where the talk page should be created, but I'm also fine with people deleting them if they really want to. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:41, 21 December 2022 (UTC)
* {{tl|quality}} for new articles is disabled (see below)
* Some links from DF2014 to Main weren't working: e.g. the version selector [[DF2014:Mason's workshop]] was linking to [[DF2014:Main:Mason's workshop]] instead of [[Main:Mason's workshop]]. I'm not sure exactly why, but I fixed it with a change to the NamespaceLinks extension. Let me know if you spot similar broken links. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:19, 21 December 2022 (UTC)
</div>

—[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:54, 20 December 2022 (UTC)
:The quality levels of the 50.03 pages seem to be missing. I'm not sure if that's covered under that first point. [[User:Trainzack|Trainzack]] ([[User talk:Trainzack|talk]]) 06:47, 20 December 2022 (UTC)
::If the the [[Dwarf Fortress Wiki:Quality]] feature can be made to work with namespace scheme change, I suggest to automatically assign the lowest quality rating to all pages, alternately add the {{tl|old}} to all pages. Otherwise there will be a lot of pages that will fall through the cracks. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 09:12, 20 December 2022 (UTC)
:::I disabled {{tl|quality}} in the main namespace because it would require some rework to make the rating script and the template work properly there. Feel free to take a stab at the template. I will see what can be done on the extension side. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:14, 20 December 2022 (UTC)
::::What needs to be done on the template side? I'm not sure I see too big of an issue leaving pages as "unknown-quality" for now (or just change the default to tattered) until we get the rating script working. Is that script up anywhere, anything that could be helped with? [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 11:10, 2 January 2023 (UTC)
:::::They're already marked as unknown. Really the only issue I know of with the template is that it doesn't show up with some of the newer skins we added, and that can be fixed by getting rid of the absolute positioning. As for the script, it can be found at https://github.com/DF-Wiki/QualityRatings, and the issue is really only with the configuration system not recognizing the main namespace as valid. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:29, 3 January 2023 (UTC)
::::::Great, I started having a crack at fixing the template with different themes. Is the preference to get some CSS going and then include it in the global stylesheet (i.e different styles per theme) or to try and get a "one size fits all" fix? —[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 08:14, 3 January 2023 (UTC)
:::::::I would rather avoid custom site-wide CSS if we can. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:29, 4 January 2023 (UTC)
::::::::I appreciate that, I think it's the simplest solution to add a few lines to common.css though. Unless there is a way to attach CSS specifically to a template, I saw a few extensions that allowed that but I'm not sure if any are present in the wiki at the moment. Regardless there already exists a class `div.topicon` that is specifically for the quality ratings, is there an issue with expanding this class to accommodate the themes? The list of themes where the quality rating display is broken/invisible: Citizen, MinervaNeue, MonoBook. —[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 21:48, 4 January 2023 (UTC)
:::::::::What do you think of moving the template out of the topicon entirely and just placing it in a div? It would take up a (hopefully) small amount of vertical space in the article. [[User:Lethosor/Sandbox/Quality_test]] is an example. Unfortunately it isn't possible to prevent other templates from displaying above the quality this way ([https://dwarffortresswiki.org/index.php?title=User:Lethosor/Sandbox/Quality_test&oldid=283883]). So maybe we do need some custom CSS after all if we want that. I'm open to trying out whatever you propose. I'm a bit worried about future-proofing against skins we add later (particularly a mobile skin) but at least MediaWiki supports skin-specific global CSS as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:33, 5 January 2023 (UTC)
::::::::::I would rather we avoid taking any more vertical space in the article. The growing block pyramid at the top, starting with version template, is annoying. If you end up placing it inside the article space please use a slim box 100% wide that would include both.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 01:19, 5 January 2023 (UTC)
:::::::::::Agreed with you Jan, however I see that as two different tasks (ArticleVersion template changes, getting quality back on pages). I made a test adjustment to the quality and it takes up a negligable amount of extra space. See [[User:Vallode/sandbox#Page_quality]] for the example, we'd be able to completely remove "topicon" (unless it is used somewhere else?) and then potentially move on to making the ArticleVersion template into a slim version on the left-hand-side instead of a large box? Let me know what you think. --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 17:35, 5 January 2023 (UTC)

It appears some pages are redirecting recursively and never resolving correctly, like the [[https://dwarffortresswiki.org/index.php?title=Character_table&redirect=no|character table]] and [[tileset repository]] 07:35, 20 December 2022 (UTC)
: Indeed, these can be caught here: [[Special:DoubleRedirects]] --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:51, 20 December 2022 (UTC)

It might be useful to change the notice title to "release information '''for editors'''" --[[Special:Contributions/142.59.195.176|142.59.195.176]] 10:26, 20 December 2022 (UTC)
:Can do. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)
::New here, hello. Should we set a date where we remove/only show the banner for logged in users. There are (some) pages that have 4 different notices about the upgrade. [[Engraving]] is one such page, the top banner states "information for editors", we then have the "this page was migrated" banner, a version selection which warns the article might be inaccurate, and a smaller banner saying the page might need to be updated. Quite a lot of screen space, I think we can start to slowly reduce the amount of warnings this coming month? [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 10:07, 2 January 2023 (UTC)
:::Unfortunately, only showing info to logged-in users is difficult with how MediaWiki caching works. In terms of reducing warnings, there is a discussion [[Template_talk:ArticleVersion#.22Note_that_some_content_may_still_need_to_be_updated..22|here]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:43, 4 January 2023 (UTC)
:::As for [[Engraving]] specifically, the {{tl|old}} banner was actually present on [[DF2014:Engraving]] as well and got carried over with the migration. I removed it, and agree that it was redundant. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:46, 4 January 2023 (UTC)

Main talkpages seem to redirect to DF2014 talk. Not sure if it is intentional but I like it, though we should pay attention when creating new discussion relating to v50 ending up there.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 14:18, 20 December 2022 (UTC)
:That's unintentional. I specifically wrote the migration script to not move talk pages, but that has the side-effect of leaving any previously-created "Talk -> DF2014 talk" redirects intact. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)

Yo Lethosor, are we adding graphic sprites for the pages in some way? Or are we waiting for you to add some sort of new template or something? I'm sure you don't need me to tell you that the current templates don't allow that. Not sure if I'm allowed to change/create any templates either, as I don't want to break things for hundreds of pages. Edit: And IF the icons are allowed, should they be left alone, or 2×-3× sized like how the Minecraft wiki does it? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 14:29, 20 December 2022 (UTC)
:Depends on which templates you mean. There are copyright concerns with uploading a premium sprite sheet, for instance. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)
::I'm not talking about uploading an entire sprite sheet. I'm just talking about individual icons for each respective page. One image for cows, one for horses, one for werebeasts, etc. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 16:50, 20 December 2022 (UTC)
:::If we do that for every creature in the sprite sheet, that's not much different (in terms of copyright) from uploading the entire sprite sheet. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:09, 20 December 2022 (UTC)
::::Is there someone we can talk to about that? We finally get this new game with graphics, and then we can't use the very graphics of the game? No matter what the rules are, I'd say that would be the stupidest thing ever. I know I'm infamous here when it comes to copyright and images and stuff, but about 80% of game wikis out there are completely unofficial, and use game file images like no one's business. I can't imagine anyone's door being knocked on if we used the game's sprites, but I won't add any here until we have a go-ahead. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 17:14, 20 December 2022 (UTC)

:::::...I've made noise in Mayday's direction on this matter, at least (prob an incorrect maneuver, ''but'').[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 17:55, 20 December 2022 (UTC)
:::::: I hope some sort of arrangement can be made so we can use the new sprites with permission/limits, just as we are using the raw files. Otherwise we are all (devs and editors alike) shooting ourselves in the foot here.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 21:07, 20 December 2022 (UTC)

:::::::I just thought of something. We're supposedly not allowed to upload entire sprite sheets, right? What if - for the time being - we just use a few of them for the purpose of testing out new infoboxes? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 21:46, 20 December 2022 (UTC)
::::::::I don't know. If someone could ask Kitfox and post the response here, that would be great. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:47, 20 December 2022 (UTC)

:::::::::I've reached out to Alexandra, but she hasn't answered yet. Until then I found these old approvals from the previous community manager, Feeona: ([http://www.bay12forums.com/smf/index.php?topic=173474.msg8243633#msg8243633 link1], [http://www.bay12forums.com/smf/index.php?topic=176640.msg8243642#msg8243642 link2]). Waiting for a newer response until we begin mass uploads is probably the politer option, but like Zippy said, it is also standard for wikis to use game sprites with less approval. I second their idea of trying it out with a few images to test the infoboxes. On the extreme off-chance (and I do think it is) Kitfox protests we can always remove these few. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 22:19, 20 December 2022 (UTC)
:::::::::And here is a third, more official statement: ([http://www.bay12forums.com/smf/index.php?topic=173474.msg8249718#msg8249718 link3]). Perhaps that address of info@kitfoxgames.com is the better channel to ask for a confirmation, rather than Discord DMs, but I will be going to bed, so it is best if someone else does that. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 22:29, 20 December 2022 (UTC)
::::::::::Thanks for tracking this down! Ok, sprites should be fine, but let's avoid uploading the entire premium tileset as a single image, for instance (as the forum thread says, "use common sense"). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:21, 21 December 2022 (UTC)
::::::::::: Looks good, permission is always preferable over fairuse, I think it is a win win for all involved. I agree that we shouldn't upload entire sprite sheets (e.g. there is no reason to upload the windmill from every direction or whole construction phase for workshops) and that there are a lot of details that needs to be ironed out through testing. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 05:07, 21 December 2022 (UTC)
:::::::::We have a green light on uploading all and any sprites. Their response to me can be seen [https://i.imgur.com/BhmHjzC.png here]. I'm sure someone else confirmed it before me. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 19:00, 21 December 2022 (UTC)

Shifting temporarily to a new issue, is the documentation of [[Template:ArticleVersion]] outdated? It would seem so to me, since the current version no longer has its own namespace, with the templates needing updating being different ones. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 18:30, 20 December 2022 (UTC)
:I think it is still accurate enough. We left open the possibility of making another namespace in the future, albeit with a different migration strategy - see [[#v50 organization|above]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:52, 20 December 2022 (UTC)

Some Changes to infoboxes might be needed. Too bad [[User:Doorkeeper]] isn't around. He did a great work with navbox project--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:52, 21 December 2022 (UTC)

I just realized that raw files aren't stored as regular wiki pages but loaded via the DFRawFunctions extension (hence the need to update). Good news it's going to be handled in bulk, consistently and relatively easy to updated. Even better it's Lethosor problem ;) Also I just realized that all the "raw files" (txt files in the new vanilla folder) are released into the public domain. Both are probably not news to the vets but I'll leave it here for those who less up to date like myself. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:35, 22 December 2022 (UTC)

: I noticed that some templates aren't working properly in the new namespace, e.g. [[Basalt]] entry had its raw updated manually but the infobox fail to show any details. Cursory look suggest {{t|layerlookup/0}} need a minor tweak. This should do the work
:: Replace: <nowiki>{{layerlookup/aux|{{{{FULLPAGENAME}}/raw}}|uses={{{uses|}}}|wiki={{{wiki|}}}}}</nowiki>
:: With___: <nowiki>{{layerlookup/aux|{{</nowiki>:<nowiki>{{FULLPAGENAME}}/raw}}|uses={{{uses|}}}|wiki={{{wiki|}}}}}</nowiki>
: Not sure what the plan and ETA with raws update so I didn't touch this high usage template for now. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 08:11, 24 December 2022 (UTC)

::Please do feel free to make this update. I am still working on a script to create the <code>/raw</code> pages themselves. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:12, 1 January 2023 (UTC)

Wouldn't it be an idea to add to the Sitenotice to remove the {{tl|migrated article}} tag when an article has been fully updated? I see many articles that seem to be updated still have the tag. And/or advise to make use of the {{tl|verify}} for sections still in need of checking? --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 10:12, 2 January 2023 (UTC)
:Probably a good shout. The "see this page" link does include the detail on removing but we should more explicitly encourage removing the banner once a page has at least been looked over. [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 11:01, 2 January 2023 (UTC)

== v50 specific issues ==
=== Graphics===
Follow up on the use of game sprites and the need to trying it out with a few images to test the infoboxes. First sprite [[:File:Beds v50.png]] was uploaded and used on [[Bed]] entry. Any thoughts? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:06, 21 December 2022 (UTC)
:Seems like it should be rearranged to be horizontal. Also, has there been a serious discussion about copyright? Full screenshots are 100% fine, but you start going into a grey area when you upload pieces of a spritesheet. I'm of the opinion that it's all fine as long as it's inconvenient to reconstruct the full sheet from the individual images. Maybe a further restriction could be you shouldn't upload any of the art unless it's used in an infobox (maybe an exception for pieces of the UI). And one more restriction could be you shouldn't show everything, like in your bed example, maybe just the wooden bed is good enough, leave out the stone and metal, especially since those can only be made from strange moods. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:43, 21 December 2022 (UTC)
::Actually, your bed image is kinda bad for showing off what a bed looks like because it doesn't show the pillow/blankets. That might point to cropped screenshots being the best path, although less convenient for the uploader, as you don't get details left out. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:46, 21 December 2022 (UTC)
::I created a new license template [[Template:Copyright game]], based it on the way the RimWorld wiki does things. Call it a prototype, but it's probably how your bed image should be labelled. Indeed, I added it to it already. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]])

::: I agree that the horizontal arrangement would suit better here and that we should strive to represent how things look in-game. Otherwise, I am not too concerned about people being able to reconstruct anything (lets just say that ''anyone'' interested in that can get the real thing from the game files), also it seem we have permission to use the sprits on top of fairuse. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 19:55, 21 December 2022 (UTC)

::: Modifying the existing template to allow the inclusion of the new sprites is easy (Something like [https://ibb.co/zFXCrjd this]?) The big question is the matter of consistency is there any exceptions that will break the format (size wise with variant bloat for example), the sprite naming format, etc --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:44, 21 December 2022 (UTC)
::: If we are going to show a variant for each material type, then maybe these should be added as separate images so we can add a tooltip for each image. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:49, 21 December 2022 (UTC)

:I've got another prototype going here and here: [[User:Brightgalrs/vector.css]] and [[User:Brightgalrs/Sandbox]]. (You'll need to add the css stuff to your own /vector.css). Basically it's a way to recolor images using css classes. No idea if there's a better way. Also, the real implementation would require a change to [[MediaWiki:Common.css]]. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 22:41, 21 December 2022 (UTC)
:Should mention, there ''is'' a different way, just upload each image 16 times, one for each coloring. But maybe that's not very elegant. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 22:45, 21 December 2022 (UTC)

: It should be noted that soon the classic edition will be released, hence one should plan to have both the Premium and classic alongside in that little space --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 03:14, 22 December 2022 (UTC)
::I'm looking into a tab extension to potentially support this in infoboxes. Perhaps [https://www.mediawiki.org/wiki/Extension:Tabs Extension:Tabs]? I tried [https://www.mediawiki.org/wiki/Extension:TabberNeue Extension:TabberNeue], but it displays a placeholder if JavaScript is disabled, which isn't great. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:22, 22 December 2022 (UTC)
::: The Neue Tabber seem to works pretty much like the old one (which fandom [https://coding-help.fandom.com/wiki/Tabber#Adding_images_into_tabbers still use]) defaulting to showing the first tab only. Quick look suggest that neue work the same, plus the notice that 'Tabber requires Javascript to function' warning? if so, and if it is a bother, then you should be able to edit out the tabberneue-noscript string in code. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 06:29, 22 December 2022 (UTC)
::: I much prefer your tabber solution, but if that fails we can also use the gallery slideshow mode. If so, beware it has no way to control image size so the images have to be maliciously uploaded using the exact same size. example:
<gallery mode="slideshow">
File:SteelSample.png
File:TinSample.png
File:ZincSample.png
File:GoldSample.png
</gallery> --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 10:19, 22 December 2022 (UTC)

==== adding premium set to Infobox ====
I am unclear where are we going with this? 
1) Will (A) tabs be implemented, (B) we be using mediawiki toggle [[Template_talk:V50_workshop|example]] for premium and classic/blocked, (c) put images side by side, or (d) something else? 
2) Also [[silver]] and [[Pig iron]] use very different image style for example. 
3) Anything else you want ? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 12:32, 30 December 2022 (UTC)

: Personally, I would love tabs to be implemented, but I think that side by side might be best for most. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 12:32, 30 December 2022 (UTC)
: Here is rough layout we can use. It should fit most buildings given the default sprite size. There is also a different floor plan for both (inspired by reddit)

{|
|- valign=top
|
{| style="width:200px; background-color:#eaecf0; border-collapse: collapse; "
|+ 5×5
|- style="border-bottom:2px solid #3366cc; "
|<div class="mw-customtoggle-infoboxtab mw-ui-button mw-ui-progressive" style="border-top-right-radius: 10px; border-top-left-radius:10px;">toggle</div>
|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|- valign=top
|colspan=2|<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">
[[File:Siege workshop.png|center|160px]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab"">
{|
|rowspan=2 style="width:50%; font-size: 125%;"|<center>{{Template:Picture Siege workshop}}</center>
|style="line-height: 1em; font-size: 125%;"|
{| style="border-spacing:4px;"
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|}
|
{| style="width:200px; background-color:#eaecf0; border-collapse: collapse; "
|+ 3×3
|- style="border-bottom:2px solid #3366cc; "
|colspan=2 style="text-align: right;"|<div class="mw-customtoggle-infoboxtab mw-ui-button mw-ui-progressive" style="float:left; border-top-right-radius: 10px; border-top-left-radius:10px;">toggle</div>{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|- valign=top
|rowspan=2 style="width:50%;"|
<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">[[File:Carpenter's workshop.png]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab""><center>
{| style="font-size: 175%; border-spacing: 0; background-color: black; border: 2px solid black"
|- 
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"| {{Raw Tile|"|7:0:0}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|{{=}}|6:0:0}}
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"|
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|]|0:0:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
|}</center></div>
|
{| style="border-spacing:5px;"
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|
{| style="width:200px; height:100px; padding:10px; background-color:#eaecf0; border-collapse: collapse;"
|+ 1×1
|- style="border-bottom:2px solid #3366cc;"
| colspan=3 style="text-align:center;"|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|-
| style="border-right: 1px dotted #545557;"|[[File:Screw_press.png|32px|center|link=]]
| style="font-size:125%;"|<center>{{Template:Picture Screw press}}</center>
| style="border-left: 1px dotted #545557;"|<center>{{Template:Floor Plan Screw press}}</center>
|}
|
{| style="width:200px; height:100px; padding:10px; background-color:#eaecf0; border-collapse: collapse;"
|+ 1×3
|- style="border-bottom:2px solid #3366cc;"
| colspan=3 style="text-align:center;"|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|-
| style="border-right: 1px dotted #545557;"|[[File:water_wheel.png|32px|center|link=]]
| style="font-size:125%;"|<center>{{Template:Picture Water wheel}}</center>
| style="border-left: 1px dotted #545557;line-height:normal;"|<center>{{Template:Floor Plan Water wheel}}</center>
|}
|}
:Any thoughts on the direction and or any and all of its elements? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 10:16, 31 December 2022 (UTC)

::I kind of like side-by-side, if it fits. If anyone wants to implement a toggle button or tabs, I would ask that that be implemented in a template for now, so that e.g. we could change a toggle button to tabs in a single place if we decide to install an extension to support that. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:14, 1 January 2023 (UTC)

::: I noticed a comment saying that [[impassable tile]] are no longer used in v50, is that true for all constructions? If so, floor plans are no longer needed, making things much easier as we can fit everything in except the 5v5 constructions like trade depot (and even these can be placed one above the other if so desired). If not, any thought on the alternative floor plan design? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:46, 1 January 2023 (UTC)

:::: None of the constructions have blocking tiles any more from my experience playing. I haven't tested siege weaponry with that stuff, but none of the workshops have it, nor does any furniture. (walls and fortifications will of course obstruct movement [[User:AndrielChaoti|AndrielChaoti]] ([[User talk:AndrielChaoti|talk]]) 18:47, 1 January 2023 (UTC)
::::: Ok, I have removed them from v50. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 23:48, 1 January 2023 (UTC)

I have added a basic side by side variant to [[Template:V50 workshop]] and [[Template:Building]] for testing, let us know if there any issues. Few notes:
* The default image naming scheme of <code>workshop-name.png</code> will likely conflict with existing images here or on commons, maybe another naming scheme should be used like <code>v50 workshop-name.png</code> as it is with ascii pictures.
* There is inconsistency in image size. If you want to use large zoomed images then toggle is best, otherwise they need to be all in native size (96px for 3x3).
* In the current version the code roughly centers the images and if there is a big image like with [[Siege workshop]] it drops to a new line --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 23:48, 1 January 2023 (UTC)

How about combining shortcut keys and the new menu icons:
<div style="color:white; font-size: large; text-shadow: -1px -1px 0 #000, 1px -1px 0 #000, -1px 1px 0 #000, 1px 1px 0 #000;">[[File:Ui b.png]]<div style="position: absolute; bottom:-14px; right:3px;">b</div>[[File:Ui bo.png]]<div style="position: absolute; bottom:-14px; right:3px;">o</div>[[File:Ui bol.png]]<div style="position: absolute; bottom:-14px; right:3px;">l</div>[[File:Ui boll.png]]<div style="position: absolute; bottom:-14px; right:3px;">l</div></div>
--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 02:24, 3 January 2023 (UTC)

:I worry that this is difficult to read (I read it as "boil" at first). I would rather use something like {{tl|k}} with a known background. What about something like this? [[File:Ui boll.png]]<div style="position: absolute; bottom:-14px; right:0px;">{{k|l}}</div> or, alternatively, using flexbox without any overlap: [[File:Ui boll.png]]{{k|l}} —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:37, 3 January 2023 (UTC)
:: Same, but that is the best I came up with. We can use the key or maybe someone can help improve the design. Also 'l' is hard to read even with {{t|key}}.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 03:05, 3 January 2023 (UTC)
:: I added a {{t|Menu icon}} to start things so others can have a go with it. Also any thoughts on the icon naming convention (their shortcut sequence), is there easier/better way? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 09:36, 3 January 2023 (UTC)
::[[User:BarelyCreative]] updated the template: {{Menu icon|b|o|l|y}}. I think it looks good, thoughts? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:40, 3 January 2023 (UTC)
:::I like that, yeah. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:29, 4 January 2023 (UTC)
::::There were some places where it didn't make sense so display every icon all the time (like step-by-step guides), so I changed it slightly to allow display of fewer icons using "num" and counting from the end: <nowiki>{{Menu icon|b|o|l|y|sep=-;|num=2}}</nowiki> {{Menu icon|b|o|l|y|sep=-|num=2}} [[User:BarelyCreative|BarelyCreative]] ([[User talk:BarelyCreative|talk]]) 09:05, 4 January 2023 (UTC)

==== Bizarre palette-swapping idea/prototype ====
No idea if this is a good idea, since it takes a bit of time to set up, and there might be some performance issues... and maybe display issues?

But take a look at this:
{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock|palette-name=amber}}

It's way to swap palettes on an image, although the image itself is a table, with each cell representing a pixel. The template itself looks like this:
<code><nowiki>{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock|palette-name=saffron}}</nowiki></code>
Input the pattern and desired palette name.

I've got a larger showcase here: [[User:Brightgalrs/Sandbox/PaletteSwapShowcase]]. Only did a rock pattern so far, but all palettes are implemented.
The major use for this would be on each stone, metal, wood, etc. type's page. The palette could be read directly from the raws. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 03:22, 24 December 2022 (UTC)

:From a technical perspective, my primary concern is indeed performance. Both on the server side and client side, a large number of tables that large (in terms of markup and cell count, that is) tend to be resource-intensive to generate and render. I saw your image-filtering experiments on [[User:Brightgalrs/vector.css]], and while that strikes me as a newer and less-backwards-compatible approach, it would probably be more resource-friendly.
:Is this color adjustment something the game is doing natively? i.e. does this accurately match what the game displays? I bet we could slap together an image-filtering extension (or find an existing one?) that can do this if needed. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:49, 24 December 2022 (UTC)
::Yeah that's what I suspected. The images the template creates are spot on, checked it against a screenshot I took of some mica rocks in-game. The css stuff is unfortunately totally incorrect, was cool to learn about it though, so not a complete waste of my time :p. The premium, in-game graphics are true sprites, basically patterns of indexed colors. Each of the in-game colors (which are significantly expanded over the 16 ascii colors, there's 116/117) there is a palette defined in "\Dwarf Fortress\data\vanilla\vanilla_descriptors_graphics\graphics\images\palettes.png". Each indexed color of the sprite is swapped for the corresponding color in the palette. Because of that, the css stuff doesn't work since it's doing the hue/saturation/brightness changes to the entire sprite.
::I've looked into an existing mediawiki extension, couldn't find anything. One thing I did't really look at is some type of lua script/module that would basically emulate what the game is doing. So some function that takes in the base image as well as the desired palette, and based on that finds and replaces each color. No idea what mediawiki's capabilities are on that front. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 05:31, 24 December 2022 (UTC)
:::We do have Scribunto installed now, so it's totally possible to do something in Lua too - forgot about that. I can add you to the group that grants access to edit the Module namespace if you want to give that a shot. If we use an extension, we'd probably need a custom one, similar to DFDiagram (or perhaps DFDiagram could be extended - it's in dire need of a rewrite anyway). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:43, 24 December 2022 (UTC)
::::I asked around on the mediawiki irc, I think scribunto/lua is a deadend, at least for taking an uploaded image and doing stuff to it with a lua script. However I did come up with this even more bizarre solution, using block elements. [[User:Brightgalrs/Sandbox/PaletteSwapShowcase2]], maybe less resource intensive? Definitely displays a lot worse though, probably unusable.
::::{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock2|palette-name=saffron}}
::::I dunno, maybe none of this is worth it and we should just write some external program to put all the images together offline, and then just mass upload. It wouldn't be ''that'' many... [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 06:37, 24 December 2022 (UTC)

====Is there an easy way to just paste images from the clipboard?====

I use KDE spectacle to take screenshots straight to the clipboard (after cropping) -- is there an easy way to just paste (and auto-upload) an image into an article? It would make it a lot easier to contribute images. [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 23:35, 1 January 2023 (UTC)
:Unfortunately there is not. I would be open to a MediaWiki extension to support this if someone finds one. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:32, 2 January 2023 (UTC)
:: Looks like this could do it, but I haven't used it before: https://www.mediawiki.org/wiki/Extension:SimpleBatchUpload [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 19:41, 2 January 2023 (UTC)
::: It won't solve paste-from-clipboard, but this would be great for making uploading sprites much easier (auto-cutup spritesheet, rename, bulk upload). Could you add this, Lethosor? [[User:OddballJoe|OddballJoe]] ([[User talk:OddballJoe|talk]]) 21:47, 6 January 2023 (UTC)

====Standards for adding graphical version screenshots and images====

Hello, new user looking into adding imagery from the new version. Is there a standard for quality of new screenshots or images? I noticed that at a certain zoom level (2 zooms in from the furthest zoomed-out view), the graphics appear crisp and 1:1 pixel scaled, and I would propose that all images be taken at this scale whenever possible. If they need to be displayed larger, they should be nearest neighbor scaled in a photo editing program at 100% increments (Microsoft Paint will do this if you first select the image rather than directly scaling the whole canvas). I would also propose that images should be cropped to conform to the 32x32 pixel grid when possible, though this could be problematic with so many new graphical elements exceeding the bounds of their tiles. I would say the best practice for capturing artwork for items, furniture etc. ought to be done in a 3x3 open area to avoid shadows from nearby walls, or else extracted from the raw files (if this doesn't run afoul of being able to re-create the graphical version using those assets).

I know that perfect is the enemy of good, and any documentation is better than none, but just thought I'd ask about this, and see if/where something like this ought to be posted. [[User:Unclesporky|Unclesporky]] ([[User talk:Unclesporky|talk]]) 13:58, 3 January 2023 (UTC)
:It has been stated in [[Template:V50 workshop]] that <q>screenshots should be at the "native" resolution</q> but someone could edit the [[Screenshot]] page for best practice for the steam version. Or post some examples in [[Talk:Screenshot]] to find out what is best? --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 14:21, 3 January 2023 (UTC)

====How would I/should I go about putting creature sprites on their pages?====

Howdy. New player and wiki user here. I wanted to try and help update the wiki to the Steam release of DF, so I figured I'd chip in by putting each creature's sprites on their respective page, since I'll often look up a creature I have yet to see in game only to be met by a blue J, or whatever. I found all of the game's creature sprites in C:\Program Files (x86)\Steam\steamapps\common\Dwarf Fortress\data\vanilla\vanilla_creatures_graphics\graphics\images, so I figured I could just chop those up in Photoshop and stick them on here no problem, but the programming syntax/whatever it is on this site is incredibly confusing, I don't know how I'd actually go about doing it. I figured I'd just find the spot on the page where the little letter is and replace that with the image code, but it seems the pages are built using heavily nested templates that I can't even begin to understand. Any help?--[[User:Treese|Treese]] ([[User talk:Treese|talk]]) 03:07, 5 January 2023 (UTC)
:Based on [[User:Zippy|Zippy]]'s work at {{tl|Creaturelookup_b}}, I added an "image" parameter to {{tl|creaturelookup/0}}, which is what creature pages should all be using. See [[Dwarf]] and [[Cow]] for examples. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:37, 5 January 2023 (UTC)

=== Hotkeys/Menu navigation ===
Most key bindings and menus have changed. Should the article reflect a) only the old version, b) only the GUI version or c) both? For example, [[Bridge|bridges]] used to be built via {{k|b}} -> {{k|g}}, but now it's in Place strucutures {{k|b}} -> Constructions {{k|n}} -> Bridge {{k|b}}. What should be written in the article? Currently, it's {{k|b}} -> {{k|g}}. I ''think'' it should be only b), but I am not sure if there will be differences regarding hotkeys or menus between the premium version and the free version and then, c) would be the most appropriate option. --[[User:Prometherus|Prometherus]] ([[User talk:Prometherus|talk]]) 10:16, 22 December 2022 (UTC)

: Not sure. I wish the classic release soon --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 16:45, 22 December 2022 (UTC)
:: Are you Toady's herald? Looks like it was just released! [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:18, 22 December 2022 (UTC)
:: And our questions are answered, the old hotkeys seem to have been thrown out. Part of me is disappointed (useless muscle memory) but also relieved (unified UI for both versions is good in general and for the wiki). [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:25, 22 December 2022 (UTC)
::: According to info, in a sort of 'demo version' at that. I'll wait a little while longer, for myself.[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 18:22, 22 December 2022 (UTC)
::::It's unlikely that keybindings in it will change significantly. My vote is that we should include information for both premium and classic, everywhere. Hopefully the keybindings are not different between versions. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 18:26, 22 December 2022 (UTC)
:::Shouldn't it be based on the 50 or what verion the article is written for? [[User:Dominick|Dominick]] [[User_talk:dominick|(TALK)]] 18:42, 22 December 2022 (UTC)
:::: The keybindings seem to be consistent between versions, (haven't checked exhausitvely, but since the menu layout is the same I think it is a good assumption). Should also keep in mind/consider that not all actions have keybindings. An option would be write 'Click on the <Example Text> icon or press {{k|E}}' [[User:Koos|Koos]] ([[User talk:Koos|talk]]) 23:14, 23 December 2022 (UTC)

=== Removed features & concepts ===

Since they're removed concepts, I've set [[Room]] to be a redirect for [[DF2014:Room]] and created [[Template:Activity zones]] for the nav bar bedrooms, etc, and made the necessary changes to [[Bedroom]] for it. Is this the correct approach, before I go on much further? (also a note, if it is, then [[Template:v50_rooms]] probably needs to be deleted) I also imagine that considering the number of changes in the interface, that things like [[Adventure mode]] and related pages might best be truncated to "not in 50.03" and when it does make it across, being more deliberately brought over in pieces? [[User:HawkOwl|HawkOwl]] ([[User talk:HawkOwl|talk]]) 06:23, 23 December 2022 (UTC)

:Usually it is marked with [[Template:Removed_feature]]. For example: [[Dipscript]] or [[Party]]. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:45, 23 December 2022 (UTC)

:: Ah, that's fair. Should that be mentioned in [[Dwarf_Fortress_Wiki:Versions#Redirects]]? [[User:HawkOwl|HawkOwl]] ([[User talk:HawkOwl|talk]]) 10:03, 23 December 2022 (UTC)

:::I think the redirect policy mostly had in mind things that were removed a ''long'' time ago, like [[Tax collector]] and [[Economy]] (and the latter actually has a stub page as well). I guess we could clarify. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:34, 23 December 2022 (UTC)

:::: The "current" redirects also cause the version box to incorrectly show that the current version has a page - e.g. [[23a:Cave_river]] shows a v50.04 version, but it's just a redirect back to that version. Similarly, what should happen to redirects like [[Clothes maker]], where a concept has evolved? It currently goes to [[23a:Clothes maker]] - that's correct if the user is trying to look up a very old concept, but if a new user is looking for "how to make clothes", they should be directed to [[Clothier]]. --[[User:Danny252|Danny252]] ([[User talk:Danny252|talk]]) 12:16, 26 December 2022 (UTC)

:::: One should be careful with cv redirects. Most that were recently adjusted were unused plural forms (that should probably be deleted) but few like [[Crown]] needed that for backward compatibility. Removing the [https://dwarffortresswiki.org/index.php?title=Crown&type=revision&diff=279966&oldid=219482 cv part] means the the link on [[v0.31:Tilesets]] is now broken. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 22:30, 26 December 2022 (UTC)

:::::If [[v0.31:Tilesets]] is about v0.31, it should not be using "main:" in its links - ''all'' of those links are going to pages about v50, not v0.31, regardless of whether the target is a redirect or not. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:37, 26 December 2022 (UTC)
:::::: You right, I removed it. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 17:55, 27 December 2022 (UTC)

Crown cv redir issue is now fixed, I believe. As goes with such cases where one can simply revert the troublesome edit, unless I've mistepped, myself? [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 23:52, 26 December 2022 (UTC)
:Both [https://dwarffortresswiki.org/index.php?title=Crown&diff=prev&oldid=280026] and [https://dwarffortresswiki.org/index.php?title=Crown&diff=prev&oldid=279966] should not have had any effect, because "cv" is an alias to the main namespace now, just like "main". Proof: [[Crown]], [[cv:Crown]], [[main:Crown]]. It's possible caching is coming into play here, although I purged the redirect cache after making that alias change earlier this month... —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:02, 27 December 2022 (UTC)

I think there have been some changes not captured, but as a newb, I'm afraid to edit the page(s). A good example is Strawberry. I'm playing the Steam version right now and Strawberry plants are "not relevant to brewing" in Labor > kitchen > veg / fruit / leaves. Unless I'm mistaken and need to process them? Another example is the trade caravan = it seems the 3 square pathing no longer happens; it's just yak(s). 12:31, 28 December 2022 (UTC) 12:29, 28 December 2022 (UTC)
:Strawberries should be brewable according to the Raws.
:Trade wagons has been modified in v50. The first wagons will arrive at the same time your fort is becoming a barony. Until then, it's only pack animals and stairs are indeed fine. The [[Trading]] page needs a huge rework anyway... I'll try to do that next week. --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 13:40, 2 January 2023 (UTC)

<s>As far as I can tell, none of the workshop buildings in v50 have blocking tiles any more. There's a comment to the like in data/vanilla/vanilla_buildings/objects/building_custom.txt that says this "[BLOCK:1:0:0:0] workbenches no longer block". Hesitant to update that template as I'm not sure if it's referenced for all of the old versions too. </s> [[User:AndrielChaoti|AndrielChaoti]] ([[User talk:AndrielChaoti|talk]]) 05:54, 29 December 2022 (UTC)
: A new template has been created: {{tl|V50 workshop}} --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 13:40, 2 January 2023 (UTC)
::Thanks! In general, I would like to delegate the switching responsibility to the template (like how {{tl|creaturelookup/0}} works), but in cases where the parameters diverge significantly like with workshops, it could make sense to make an entirely new template. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:40, 3 January 2023 (UTC)

=== creature infobox prototype (moved) ===

Check it out, I made a temporary template and added it to the [[cow]]s page. Now it shows the sprites (but not the zombified versions yet). I wanted to show everyone a prototype of what v50 creature infoboxes should look like. Or at least something similar to it. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 19:11, 27 December 2022 (UTC)
:Hi, I'm new to editing wikis but I have done a bit of work with sprite sheets and I've been going through the DF data files to find the different graphics hoping to help with the animal pages. I've thrown together a template with grass and a few nature sprites (plants, a tree, and a rock) for size reference but I'm unsure how large the 'display' tiles in the middle of the template should be to suit all animals. I can see in the sprite sheets that some land animals have an adult and child sprite, so two tiles. Others have a male, female, and child, but after seeing you include the zombie cows I'm unsure if I should make it twice the size to add them too. Alternatively, I could grab some tiles from the haunted biomes for the zombie animals and make a separate template for a side-by-side comparison. Either way, let me know if this helps. I'd like to help with other graphics too as we add the premium tilesets but the animals seemed the easiest to tackle with me being new to wiki editing. ~~[[User:UristTheSeventh|UristTheSeventh]] ([[User talk:UristTheSeventh|talk]])
::@Zippy, I am a bit perplexed about the purple cows. Why do we need a zombified version of creatures on every page?
::@UristTheSeventh, we can use all the help. Maybe post an example, so that we can have something to compare and contrast.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 11:49, 3 January 2023 (UTC)
:::@Jan Here are the examples:
:::[[File:Creature template.png]] [[File:Armadillo.png]] [[File:Seagull.png]]
:::It'll need to be wider or arranged differently for different creatures with more that two sprites or for multi-tile creatures. I can also do an aquatic and air themed template for swimming and flying creatures. ~~[[User:UristTheSeventh|UristTheSeventh]] ([[User talk:UristTheSeventh|talk]])
::::Looks nice, like the metal template. There are several people working on updating the graphics you should talk more among yourselves. Best I can offer is that I width wise I am hoping to go up to 200px for infoboxes.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 01:13, 5 January 2023 (UTC)
:::: We don't exactly ''need'' a zombie sprite on each page. I added it because it was... there. I was also hoping to get some opinions on it anyway since that infobox is a visual prototype, and not a final choice. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 03:28, 6 January 2023 (UTC)

===Furniture Infobox===
{{Quality|Unrated}}
{{v50_furniture|name=Bed
|graphic=[[File:bed_sprite_prototype.png]]
|tile=Θ|col=6:0:0
|wood=y
|rooms=
* [[Bedroom]]
* [[Barracks]]
* [[Dormitory]]
|value=10}}
I made a v50 furniture template prototype. I tested this on Firefox, Chrome and Microsoft Edge/Internet Explorer and it looks fine on all of them. I hope this is good enough to be the official thing, unless I'm missing something. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 03:28, 6 January 2023 (UTC)
{{clear}}

=== When do we remove the migration note on specific pages? ===

At what point can we remove the "this page was auto migrated from v47" warning? There are a bunch of small pages that are more or less accurate, if I've reviewed them, can I go ahead and remove the warning? [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 23:33, 1 January 2023 (UTC)
:Yes, feel free to remove it if you think all content is accurate. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:31, 2 January 2023 (UTC)

=== Any info on fixing "creature description not found?" ===

I see this issue on most creature pages, it seems to be due to a lookup that's not currently functioning? Cows interestingly doesn't have this issue but I couldn't figure out how to recreate whatever fix it's editor did. --[[User:Yallendallis|Yallendallis]] ([[User talk:Yallendallis|talk]]) 00:22, 3 January 2023 (UTC)
:That is the missing raws issue described above. Cow was fixed by the addition of [[cow/raw]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:28, 3 January 2023 (UTC)
::Ah makes sense, not fully used to the language of wikis yet so I read over it while looking. To put this bit of questioning to rest for any future readers, is it correct that it's fine to update any raws manually, though it will be done automatically at some point? --[[User:Yallendallis|Yallendallis]] ([[User talk:Yallendallis|talk]]) 07:48, 3 January 2023 (UTC)
:::Yes. I'm circling back to work on a script right now, so not much point in doing it if you're reading this. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:57, 4 January 2023 (UTC)
:::This should be fixed now. If you continue to see pages with problems, you can try [https://www.mediawiki.org/wiki/Manual:Purge purging the cache]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:59, 4 January 2023 (UTC)

=== Adventurer Mode related sections ===

The topic has already been discussed [[#Removed features & concepts|above]], but I don't see a clear line on what to do with article sections that mention Adventurer Mode. Like for example in [[Butcher#Adventurer_mode|Butcher]].

'''a) Truncate''' or '''b) leave in place with a mention''' that the mode is not yet present IG but will be added in a future update?

Personally I think option b) is better, because I think it's silly to undo some work just to reintroduce it a few weeks later, with the necessary corrections. Even if a copy/paste of a previous version takes ~15 seconds, considering the number of articles that need to be corrected, it would be a bit of a waste of time.--[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 14:22, 3 January 2023 (UTC)

== Toggleable image ==

Any objections/comments to using this template for now for toggling between classic and premium images? I'd probably rename it to "Template:Premium-classic thumb image". I'm sure someone can come up with a better UI eventually, but should be easy to migrate at that point. I also think we should use the same customtoggle class for this and for the infobox. [[User:NiftyManiac|NiftyManiac]] ([[User talk:NiftyManiac|talk]]) 23:12, 1 January 2023 (UTC)

{{User:NiftyManiac/Sandbox/TemplateDualImage|
premium=File:Quickstart-finder.png|
classic=File:Quickstart-finder-partial.png
}}

{{User:NiftyManiac/Sandbox/TemplateDualImage|
premium=File:Quickstart-finder.png|
classic=File:Quickstart-finder-partial.png|
caption=My caption|
width=100px
}}

:This looks nice to me! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:30, 2 January 2023 (UTC)

: Good initiative. From the top of my head:
:* I suggest using a shorthand, no one wants to type 'Premium-classic thumb image'.
:* If we end up using toggle for infoboxes (not sure where we headed there), then I agree definitely same custom toggle class should be used for all, thus allowing to switch premium-classic view on the whole page at a click.
:* The button part on a separate row isn't pretty, creating a lot of dead space that can be used by the text. Are we set on the label 'toggle ascii'? Classic isn't Ascii per se, maybe we can use a 'toggle' with a tooltip {{tooltip|for example|does bla bla bla}}, or maybe we can get rid of the text and have a smaller icon button ([[User:Jan/sandbox#Metal_example|two examples]]).
: I hope that helps. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 11:21, 2 January 2023 (UTC)

:: I added [[Template:Dual image]] with some of your suggestions. Agree that it's not super pretty, feel free to try something different.

::* I put the toggle in the caption mostly because I gave up on trying to make a more sophisticated replacement for the default thumb image behavior, I'm sure someone with better wiki-fu could put together something more intelligent.
::* I cut the text down to just "Toggle"; I think the best solution would be a small graphic showing the old and new dwarf icons with arrows between them. [[User:NiftyManiac|NiftyManiac]] ([[User talk:NiftyManiac|talk]]) 19:21, 2 January 2023 (UTC)

{{Dual image|
premium=File:DFwiki5by53by3farm.png|
classic=File:Quickstart_layout_3.png|
width=100px|
caption=A 5x5 room with a 3x3 farm plot
}}
::: I updated the layout, now it should look just like a regular image thumb. I didn't had time to test it, if it doesn't work for you or you don't like it just revert the last change. cheers. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 21:46, 2 January 2023 (UTC)
::::I don't know which part of this talk page to put this, but I added the ability to add icons to the v50 workshops template. Leaving the icon part blank will not break the template in any way. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 09:47, 3 January 2023 (UTC)
{{clear}}
==Creature List Now Supports Graphics!==
I wasn't easy, but I made new templates so the [[Creature]]s page now supports both graphics sprites ''and'' ASCII tiles. Allow me to show you:

{{v50_creaturecurrent_table_head}}
{{v50_creaturecurrent table row|graphic=[[File:dwarf_sprite.png]]|name=[[Dwarf]]|symbol=☺|color=3:0:0|playable=Fort, Adv|hostile=No|food=No|size=60,000|value=Not tameable|biome=[[Mountain halls]], [[Fortress|dwarf fortress]]es, [[hillock]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:elf_sprite.png]]|name=[[Elf]]|symbol=e|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=60,000|value=Not tameable|biome=[[Forest retreat]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:human_sprite.png]]|name=[[Human]]|symbol=U|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=70,000|value=Not tameable|biome=[[Town]]s and cities|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:goblin_sprite.png]]|name=[[Goblin]]|symbol=g|color=7:0:0|playable=Adv|hostile=Usually1|food=No|size=60,000|value=Not tameable|biome=[[Dark fortress]]es and [[dark pit]]s|note=Snatchers2}}
{{v50_creaturecurrent table row|graphic=[[File:kobold_sprite.png]]|name=[[Kobold]]|symbol=k|color=6:0:0|playable=Adv|hostile=Usually1|food=No|size=20,000|value=Not tameable|biome=Caves|note=Skulking race}}
|}

Oh wait, there's a bonus. You can also modify the background color of the box the sprites go in. I added that to make possibly-hard-to-see-otherwise sprites more easy to see - depending on the colors it has. Allow me to demonstrate.

{{v50_creaturecurrent_table_head}}
{{v50_creaturecurrent table row|graphic=[[File:dwarf_sprite.png]]|bgcolor=#829ccc|name=[[Dwarf]]|symbol=☺|color=3:0:0|playable=Fort, Adv|hostile=No|food=No|size=60,000|value=Not tameable|biome=[[Mountain halls]], [[Fortress|dwarf fortress]]es, [[hillock]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:elf_sprite.png]]|bgcolor=#c7dfc0|name=[[Elf]]|symbol=e|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=60,000|value=Not tameable|biome=[[Forest retreat]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:human_sprite.png]]|bgcolor=#c7dfc0|name=[[Human]]|symbol=U|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=70,000|value=Not tameable|biome=[[Town]]s and cities|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:goblin_sprite.png]]|bgcolor=#dfc0c0|name=[[Goblin]]|symbol=g|color=7:0:0|playable=Adv|hostile=Usually1|food=No|size=60,000|value=Not tameable|biome=[[Dark fortress]]es and [[dark pit]]s|note=Snatchers2}}
{{v50_creaturecurrent table row|graphic=[[File:kobold_sprite.png]]|bgcolor=#dfc0c0|name=[[Kobold]]|symbol=k|color=6:0:0|playable=Adv|hostile=Usually1|food=No|size=20,000|value=Not tameable|biome=Caves|note=Skulking race}}
|}

To change the background color, add <code><nowiki>|bgcolor=COLOR</nowiki></code> segment after the <code><nowiki>|graphic</nowiki></code> part. You can use color names or HTML hex color codes. I added this to the v50 creatures page, but at this time, I only added the first five creatures I just displayed. It's gonna take a while to find ALL of those creature sprites. I hope a lot of people help out on that one. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 05:29, 5 January 2023 (UTC)

:Thanks, looks nice! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:44, 5 January 2023 (UTC)
:Nice stuff, took the quick liberty to change the padding-left -> text-align to make all the sprites center aligned relative to each other :) Sweet work --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 17:41, 5 January 2023 (UTC)
:: Good work indeed. One minor issue, is that all the sprites have different sizes, which sometimes create slight variation in table row height. Consider using capping the image size vertically for example <code><nowiki>[[File:dwarf_sprite.png|x32px]]</nowiki></code>--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:15, 5 January 2023 (UTC)
:: Also often in such tables people want to click on the image to go for the specific entry, and often will try to click on the very first thing they see in line the thumb image, but currently that will take them to the file page. Consider adding link parameter for example: <code><nowiki>[[File:dwarf_sprite.png|x32px|link=dwarf]]</nowiki></code> [[File:dwarf_sprite.png|x32px|link=dwarf]] or no link at all <code><nowiki>[[File:dwarf_sprite.png|x32px|link=]]</nowiki></code> [[File:dwarf_sprite.png|x32px|link=]] --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:24, 5 January 2023 (UTC)
::: I mean... Yeah, I could do that. I think that lessens the quality of the sprite a bit because it makes edges blurry, but either way is fine. I could have sworn I added a link for all those images the first time. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 03:23, 6 January 2023 (UTC)
::::Since we are adding pixel art sprites to the website it might be convincing to add a global class like .sprite or .pixel-image that uses the CSS attribute `image-rendering: pixelated;` in order to prevent blurryness when scaling the image up/down. Just a thought --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 09:40, 6 January 2023 (UTC)
:::::Are we able to attach classes directly to images? If so, we can probably attach inline styles directly as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:52, 6 January 2023 (UTC)
::::::Looks like (without an extension) MediaWiki only supports classes on images: [[File:dwarf_sprite.png|x32px|class=pixelated]] and not styles: [[File:dwarf_sprite.png|x32px|style="image-rendering: pixelated;"]] it just treats it as alt text it looks like? Wrapping it in a div works and demonstrates the difference: <div style="image-rendering: pixelated;display:inline;">[[File:dwarf_sprite.png|64px]]</div> [[File:dwarf_sprite.png|64px|inline]]. Speaking from experience, however, image-rendering needs a browser specific prefix in certain browsers (safari, for example) in order to work properly. I'm not entirely sure what the best "MediaWiki" practice is for adding something like this but I would assume it's a simple class in common.css for now. --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 17:17, 6 January 2023 (UTC)
:::::::Ah, yeah, you are correct, I should have checked https://www.mediawiki.org/wiki/Help:Images. I'd be fine adding a class like that to common.css. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:27, 6 January 2023 (UTC)
::::::::Great, in that case if no one is opposed we can add `.game-sprite` or something like that? See below for the CSS, the order of the attributes is relevant. --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 18:23, 6 January 2023 (UTC)
<pre>/* Used for pixel-art images from the game so they can be resized and maintain crisp pixel edges. */
.game-sprite {
image-rendering: -webkit-optimize-contrast;
image-rendering: crisp-edges;
image-rendering: pixelated;
}</pre>
:::::::::So... you guys think each creature page should show the main sprite(s) alone, or should it show the baby versions alongside them? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 08:37, 8 January 2023 (UTC)
::::::::::I think adult + baby is sensible, the adult + baby + zombie was not, in retrospect. So yeah adult + baby (if there is one) from now on would be my vote. --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 23:27, 8 January 2023 (UTC)
{{outdent}}
Well then, there's a TON of creatures to go - and I mean both the [[creature]]s page and the individual creature pages. I really hope everyone can pull their weight on that those images. The spritesheets are easy to find, and if you know how to read the .txt files near them, finding sprites on certain rows and columns should be a breeze. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 00:47, 9 January 2023 (UTC)
:Zippy, are you doing all of this by hand? That seems quite tedious. Cutting up the spritesheets can be done automatically. Renaming and updating the table could be done with a script and/or chatgpt. We'd need Lethosor to add the [https://www.mediawiki.org/wiki/Extension:SimpleBatchUpload batch upload extension] though. Maybe some manual work in updating names to match article names rather than raws. [[User:OddballJoe|OddballJoe]] ([[User talk:OddballJoe|talk]]) 06:55, 9 January 2023 (UTC)
{{clear}}

So did the graphic people gained insights and reached some sort of consensus? are we using big up scaled images + toggle? multiple images to(adult + baby)? anything else? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 00:32, 10 January 2023 (UTC)

=== Graphics in Skill Infoboxes ===
{{v50_skill
| color = 7:0
| graphic = [[File:miner_sprite_icon.png]]
| skill = Miner
| profession = Miner
| job name = [[Mining]]
| tasks =
* [[Dig]]
| attributes =
* Strength
* Toughness
* Endurance
* Willpower
* Spatial Sense
* Kinesthetic Sense}}I've made yet another visual prototype for skills. In other words, we can put sprites of matching dwarves (and possibly humans, elves, goblins, etc.) at the top of infoboxes. If multiple images are put up there, that can mess up the alignment, but don't worry, Zippy thought of that. <code><nowiki>|graphicmargin</nowiki></code> can added, and a percentage or a "px" number can be placed in that parameter to fix it. If you leave said parameter out, the alignment will default to about 42% from the left. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 06:06, 7 January 2023 (UTC)
<pre><nowiki>
{{v50_skill
| color = 7:0
| graphic = [[File:miner_sprite_icon.png]]
| graphicmargin = (OPTIONAL)
| skill = Miner
| profession = Miner
| job name = [[Mining]]
| tasks =
* [[Dig]]
| attributes =
* Strength
* Toughness
* Endurance
* Willpower
* Spatial Sense
* Kinesthetic Sense}}
</nowiki></pre>
::Not sure I understand the alignment issue, can you not put text-align: center on the parent table element instead of messing with explicit margins? As another sidenote, should we continue to be naming all of these templates v50_x, I find that a bit confusing. Why not just edit the main templates with the additional information. Loving all the new templates though nice work Zippy :) --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 11:43, 7 January 2023 (UTC)
:::No, text-align doesn't work with images and divs. That just works for text. When it comes to images, you got to put a little "finesse" on the CSS with those. As for editing the classic templates with the new info, it doesn't always work that way with ''every'' template. Lethosor I think ''did'' update the creature infobox template in the way you mentioned. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 08:37, 8 January 2023 (UTC)
:::: You can use something like this to automatically handle that--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 08:56, 8 January 2023 (UTC)
{|
|-
|<div style="width:200px; display:flex; background-color:#eaecf0;">
[[File:miner_sprite_icon.png|center]]
<div>
|<div style="width:200px; display:flex; background-color:#eaecf0;">
[[File:miner_sprite_icon.png|center]] [[File:miner_sprite_icon.png|center]]
<div>
|<div style="width:200px; display:flex; background-color:#eaecf0;">
[[File:miner_sprite_icon.png|center]] [[File:miner_sprite_icon.png|center]] [[File:miner_sprite_icon.png|center]]
<div>
|}
:::::Hah I am very familar with the CSS finese :P Can you show me an example of a multi-sprite job infobox? I said what I said because I tested my proposed solution and it worked fine :)

Template:CreatureInfo v0.40

2023-01-10T00:27:19Z

Jan: simplified

{{infostart|{{{name}}}}}
{{infocell|style=color: {{fgcolor|{{{color|7:0:1}}}}}; background: black; text-align:center; vertical-align:middle;|1=
<div class="{{#if:{{{image|}}}|mw-collapsible mw-collapsed}}" id="mw-customcollapsible-classicimage" style="font-size:xx-large; font-weight: bold; font-family: 'Courier New', 'Quicktype Mono', 'Bitstream Vera Sans Mono', 'Lucida Console', 'Lucida Sans Typewriter', monospace; {{#if:{{{image|}}}|height: 128px; line-height: 128px;}}">{{char|{{{symbol|?}}}}}</div>
{{#if:{{{image|}}}|<div class="mw-collapsible" id="mw-customcollapsible-classicimage" style="image-rendering: pixelated; -webkit-image-rendering: pixelated; -moz-image-rendering: pixelated;">[[File:{{{image}}}|200x128px]]</div>
Toggle}}}}
{{#if:{{{pref|}}}|{{infopref|{{{pref}}}}}}}
{{infoheader|Biome}}
{{infocell|{{#if:{{{biome|}}}|{{{biome|}}}|Any location}}}}
{{#ifeq:{{{vary|no}}}|no|{{!-}}|
{{infoheader|Variations}}
{{infocell|{{{vary|unknown}}} }} }}
{{#ifexpr:{{#if:{{{alignment|}}}|1|0}} or {{#ifexpr:{{{bldgdest|0}}}>0|1|0}} or {{#if:{{{attribs|}}}|1|0}}|
{{infoheader|Attributes}}
{{#if:{{{alignment|}}}|{{inforow|Alignment:|{{{alignment}}} }}|{{!-}}}}
{{#ifexpr:{{{bldgdest|0}}}>0|{{infocell|[[Building destroyer]]: Level {{{bldgdest}}}{{Category|Building destroyer}}}}|{{!-}}}}}}
{{#if:{{{attribs|}}}|{{infocell|{{span-hide}}{{{attribs}}}{{end-span}}}}|{{!-}}}}
{{#ifexpr:{{#if:{{{pet|}}}|1|0}} or {{#if:{{{exotic|}}}|1|0}}|
{{infoheader|Tamed Attributes}}
{{inforow|Pet value|{{formatnum:{{{petvalue|0}}}}}}}
{{#if:{{{grazer|}}}|{{inforow|[[Grazer]]:|{{{grazer}}} {{Category|Grazer}}}}|{{!-}}}}
{{#if:{{{tame_attribs|}}}|{{infocell|{{span-hide}}{{{tame_attribs}}}{{end-span}}}}|{{!-}}}}
{{infocell|{{#ifexpr:{{#expr:{{{train_hunt|0}}}+{{{train_war|0}}}>0}}
|[[Animal trainer|Trainable]]:  {{#ifexpr:{{{train_hunt|0}}}>0|Hunting {{Category|Hunting animals}}|}}   {{#ifexpr:{{{train_war|0}}}>0|War {{Category|War animals}}|}}|Not hunting/war [[Animal trainer|trainable]]}}}}|{{infoheader|bg=#fbb|Cannot be tamed}}}}{{
#ifexpr:{{#expr:{{{size0|0}}}+{{{size1|0}}}+{{{size2|0}}}}}>0| 
{{infoheader|[[Size]]}}
{{infocell|{{#ifexpr:{{{size0|0}}}>0|{{inforow|'''Birth:'''|{{formatnum:{{{size0}}} cm3 }}}}
{{#ifexpr:{{{size1|0}}}>0|{{inforow|'''Mid:'''|{{formatnum:{{{size1}}} cm3 }}}}}}
|{{#ifexpr:{{{size1|0}}}>0|{{inforow|'''Birth:'''|{{formatnum:{{{size1}}} cm3 }}}}}}}}
{{#ifexpr:{{{size2|0}}}>0|{{inforow|'''Max:'''|{{formatnum:{{{size2}}} cm3 }}}}}}}}||}}
{{#if:{{{eggs|}}}|{{infoheader|[[Food|Food products]]}}
{{#if:{{{eggs|}}}|{{inforow|[[Egg]]s|{{{eggs}}}}}}}}}{{
#if:{{{childage|}}}{{{adultage|}}}{{{maxage|}}}|<nowiki/>
{{infoheader|Age}}
{{#if:{{{childage|}}}|{{inforow|Child at:|{{{childage}}}}}}}
{{inforow|Adult at:|{{{adultage}}}}}
{{inforow|Max age:|{{{maxage}}}}}}}
{{infoheader|{{#switch:{{{death|}}}
|rot=Rotting leaves
|item=Becomes after death
|nobutcher=Cannot be butchered
|butcher |#default=[[Meat industry|Butchering returns]]}}}}
{{#if:{{{valm|}}}|([[Multiply value|Value multiplier]] ×{{{valm|}}})}}
{{#ifeq:{{{death|}}}|item|{{infocell|{{{item|}}}}}|{{!-}}}}
{{#switch:{{{death|}}}
|nobutcher
|item={{!-}}
|#default={{infocell|'''Food items'''}}
{{#if:{{{meat|}}}|{{inforow|[[Meat]]|{{{meat|}}}}}|{{!-}}}}
{{#if:{{{fat|}}}|{{inforow|[[Fat]]|{{{fat|}}}}}|{{!-}}}}
{{#if:{{{brain|}}}|{{inforow|[[Brain]]|{{{brain|}}}}}|{{!-}}}}
{{#if:{{{gizzard|}}}|{{inforow|[[Gizzard]]|{{{gizzard|}}}}}|{{!-}}}}
{{#if:{{{heart|}}}|{{inforow|[[Heart]]|{{{heart|}}}}}|{{!-}}}}
{{#if:{{{lung|}}}|{{inforow|[[Lung]]s|{{{lung|}}}}}|{{!-}}}}
{{#if:{{{intestine|}}}|{{inforow|[[Intestines]]|{{{intestine|}}}}}|{{!-}}}}
{{#if:{{{liver|}}}|{{inforow|[[Liver]]|{{{liver|}}}}}|{{!-}}}}
{{#if:{{{kidney|}}}|{{inforow|[[Kidney]]s|{{{kidney|}}}}}|{{!-}}}}
{{#if:{{{tripe|}}}|{{inforow|[[Tripe]]|{{{tripe|}}}}}|{{!-}}}}
{{#if:{{{sweetbread|}}}|{{inforow|[[Sweetbread]]|{{{sweetbread|}}}}}|{{!-}}}}
{{#if:{{{eye|}}}|{{inforow|[[Eye]]s|{{{eye|}}}}}|{{!-}}}}
{{#if:{{{spleen|}}}|{{inforow|[[Spleen]]|{{{spleen|}}}}}|{{!-}}}}
{{infocell|'''Raw materials'''}}
{{#if:{{{bone|}}}|{{inforow|[[Bones]]|{{{bone|}}}}}|{{!-}}}}
{{#if:{{{skull|}}}|{{inforow|[[Skull]]|{{{skull|}}}}}|{{!-}}}}
{{#if:{{{ivory|}}}|{{inforow|[[Ivory]]|{{{ivory|}}}{{Category|Ivory}}}}|{{!-}}}}
{{#if:{{{tooth|}}}|{{inforow|[[Teeth]]|{{{tooth|}}}{{Category|Tooth}}}}|{{!-}}}}
{{#if:{{{hoof|}}}|{{inforow|[[Hooves]]|{{{hoof|}}}{{Category|Hoof}}}}|{{!-}}}}
{{#if:{{{horn|}}}|{{inforow|[[Horns]]|{{{horn|}}}{{Category|Horn}}}}|{{!-}}}}
{{#if:{{{shell|}}}|{{inforow|[[Shell]]|{{{shell|}}}}}|{{!-}}}}
{{#if:{{{skin|}}}|{{inforow|[[Skin]]|{{#switch:{{{skin|}}}|hide=Raw hide{{Category|Leather}}|scale=Scales{{Category|Scales}}|chitin=Chitin{{Category|Chitin}}|none=not skinnable|#default={{{skin|}}}{{Category|Unrecognized skin}}}}}}|{{!-}}}}
{{#if:{{{wool|}}}|{{inforow|[[Wool]]|{{{wool|}}}}}|{{!-}}}}
{{#if:{{{feather|}}}|{{inforow|[[Feather]]|{{{feather|}}}}}|{{!-}}}}
{{#if:{{{gizzard_stone|}}}|{{inforow|[[Gizzard stone]]|{{{gizzard_stone|}}}}}|{{!-}}}}
{{#ifeq:{{{contrib|}}}|no|{{!-}}|{{infocell|style=text-align:center; background-color: #eee; border-top: 1px solid #aaa|''There is too little information about this creature. Please contribute if you can!''{{Category|Incomplete butchering returns|{{PAGENAME}}}}}}|{{!-}}}}
}}
{{#ifexpr:{{#if:{{{wiki|}}}|1|0}} and {{#ifeq:{{{wiki|}}}|no|0|1}}|{{infocell|style=text-align:center; background-color: #eee; border-top: 1px solid #aaa|1=[[wikipedia:{{#ifeq:{{{wiki|}}}|yes|{{{name}}}|{{{wiki|}}}}}|Wikipedia article]]}}|{{!-}}}}
{{infoend}}<noinclude>{{documentation}}[[Category:Infobox templates]]</noinclude>

Template:CreatureInfo v0.40

2023-01-10T00:26:00Z

Jan: fix, although unnecessary param

{{infostart|{{{name}}}}}
{{infocell|style=color: {{fgcolor|{{{color|7:0:1}}}}}; background: black; text-align:center; vertical-align:middle;|1=
{{#if:{{{image|}}}|<div class="mw-collapsible" id="mw-customcollapsible-classicimage" style="image-rendering: pixelated; -webkit-image-rendering: pixelated; -moz-image-rendering: pixelated;">[[File:{{{image}}}|200x128px]]</div>}}
<div class="{{#if:{{{image|}}}|mw-collapsible mw-collapsed}}" id="mw-customcollapsible-classicimage" style="font-size:xx-large; font-weight: bold; font-family: 'Courier New', 'Quicktype Mono', 'Bitstream Vera Sans Mono', 'Lucida Console', 'Lucida Sans Typewriter', monospace; {{#if:{{{image|}}}|height: 128px; line-height: 128px;}}">{{char|{{{symbol|?}}}}}</div>
{{#if:{{{image|}}}|Toggle}}}}
{{#if:{{{pref|}}}|{{infopref|{{{pref}}}}}}}
{{infoheader|Biome}}
{{infocell|{{#if:{{{biome|}}}|{{{biome|}}}|Any location}}}}
{{#ifeq:{{{vary|no}}}|no|{{!-}}|
{{infoheader|Variations}}
{{infocell|{{{vary|unknown}}} }} }}
{{#ifexpr:{{#if:{{{alignment|}}}|1|0}} or {{#ifexpr:{{{bldgdest|0}}}>0|1|0}} or {{#if:{{{attribs|}}}|1|0}}|
{{infoheader|Attributes}}
{{#if:{{{alignment|}}}|{{inforow|Alignment:|{{{alignment}}} }}|{{!-}}}}
{{#ifexpr:{{{bldgdest|0}}}>0|{{infocell|[[Building destroyer]]: Level {{{bldgdest}}}{{Category|Building destroyer}}}}|{{!-}}}}}}
{{#if:{{{attribs|}}}|{{infocell|{{span-hide}}{{{attribs}}}{{end-span}}}}|{{!-}}}}
{{#ifexpr:{{#if:{{{pet|}}}|1|0}} or {{#if:{{{exotic|}}}|1|0}}|
{{infoheader|Tamed Attributes}}
{{inforow|Pet value|{{formatnum:{{{petvalue|0}}}}}}}
{{#if:{{{grazer|}}}|{{inforow|[[Grazer]]:|{{{grazer}}} {{Category|Grazer}}}}|{{!-}}}}
{{#if:{{{tame_attribs|}}}|{{infocell|{{span-hide}}{{{tame_attribs}}}{{end-span}}}}|{{!-}}}}
{{infocell|{{#ifexpr:{{#expr:{{{train_hunt|0}}}+{{{train_war|0}}}>0}}
|[[Animal trainer|Trainable]]:  {{#ifexpr:{{{train_hunt|0}}}>0|Hunting {{Category|Hunting animals}}|}}   {{#ifexpr:{{{train_war|0}}}>0|War {{Category|War animals}}|}}|Not hunting/war [[Animal trainer|trainable]]}}}}|{{infoheader|bg=#fbb|Cannot be tamed}}}}{{
#ifexpr:{{#expr:{{{size0|0}}}+{{{size1|0}}}+{{{size2|0}}}}}>0| 
{{infoheader|[[Size]]}}
{{infocell|{{#ifexpr:{{{size0|0}}}>0|{{inforow|'''Birth:'''|{{formatnum:{{{size0}}} cm3 }}}}
{{#ifexpr:{{{size1|0}}}>0|{{inforow|'''Mid:'''|{{formatnum:{{{size1}}} cm3 }}}}}}
|{{#ifexpr:{{{size1|0}}}>0|{{inforow|'''Birth:'''|{{formatnum:{{{size1}}} cm3 }}}}}}}}
{{#ifexpr:{{{size2|0}}}>0|{{inforow|'''Max:'''|{{formatnum:{{{size2}}} cm3 }}}}}}}}||}}
{{#if:{{{eggs|}}}|{{infoheader|[[Food|Food products]]}}
{{#if:{{{eggs|}}}|{{inforow|[[Egg]]s|{{{eggs}}}}}}}}}{{
#if:{{{childage|}}}{{{adultage|}}}{{{maxage|}}}|<nowiki/>
{{infoheader|Age}}
{{#if:{{{childage|}}}|{{inforow|Child at:|{{{childage}}}}}}}
{{inforow|Adult at:|{{{adultage}}}}}
{{inforow|Max age:|{{{maxage}}}}}}}
{{infoheader|{{#switch:{{{death|}}}
|rot=Rotting leaves
|item=Becomes after death
|nobutcher=Cannot be butchered
|butcher |#default=[[Meat industry|Butchering returns]]}}}}
{{#if:{{{valm|}}}|([[Multiply value|Value multiplier]] ×{{{valm|}}})}}
{{#ifeq:{{{death|}}}|item|{{infocell|{{{item|}}}}}|{{!-}}}}
{{#switch:{{{death|}}}
|nobutcher
|item={{!-}}
|#default={{infocell|'''Food items'''}}
{{#if:{{{meat|}}}|{{inforow|[[Meat]]|{{{meat|}}}}}|{{!-}}}}
{{#if:{{{fat|}}}|{{inforow|[[Fat]]|{{{fat|}}}}}|{{!-}}}}
{{#if:{{{brain|}}}|{{inforow|[[Brain]]|{{{brain|}}}}}|{{!-}}}}
{{#if:{{{gizzard|}}}|{{inforow|[[Gizzard]]|{{{gizzard|}}}}}|{{!-}}}}
{{#if:{{{heart|}}}|{{inforow|[[Heart]]|{{{heart|}}}}}|{{!-}}}}
{{#if:{{{lung|}}}|{{inforow|[[Lung]]s|{{{lung|}}}}}|{{!-}}}}
{{#if:{{{intestine|}}}|{{inforow|[[Intestines]]|{{{intestine|}}}}}|{{!-}}}}
{{#if:{{{liver|}}}|{{inforow|[[Liver]]|{{{liver|}}}}}|{{!-}}}}
{{#if:{{{kidney|}}}|{{inforow|[[Kidney]]s|{{{kidney|}}}}}|{{!-}}}}
{{#if:{{{tripe|}}}|{{inforow|[[Tripe]]|{{{tripe|}}}}}|{{!-}}}}
{{#if:{{{sweetbread|}}}|{{inforow|[[Sweetbread]]|{{{sweetbread|}}}}}|{{!-}}}}
{{#if:{{{eye|}}}|{{inforow|[[Eye]]s|{{{eye|}}}}}|{{!-}}}}
{{#if:{{{spleen|}}}|{{inforow|[[Spleen]]|{{{spleen|}}}}}|{{!-}}}}
{{infocell|'''Raw materials'''}}
{{#if:{{{bone|}}}|{{inforow|[[Bones]]|{{{bone|}}}}}|{{!-}}}}
{{#if:{{{skull|}}}|{{inforow|[[Skull]]|{{{skull|}}}}}|{{!-}}}}
{{#if:{{{ivory|}}}|{{inforow|[[Ivory]]|{{{ivory|}}}{{Category|Ivory}}}}|{{!-}}}}
{{#if:{{{tooth|}}}|{{inforow|[[Teeth]]|{{{tooth|}}}{{Category|Tooth}}}}|{{!-}}}}
{{#if:{{{hoof|}}}|{{inforow|[[Hooves]]|{{{hoof|}}}{{Category|Hoof}}}}|{{!-}}}}
{{#if:{{{horn|}}}|{{inforow|[[Horns]]|{{{horn|}}}{{Category|Horn}}}}|{{!-}}}}
{{#if:{{{shell|}}}|{{inforow|[[Shell]]|{{{shell|}}}}}|{{!-}}}}
{{#if:{{{skin|}}}|{{inforow|[[Skin]]|{{#switch:{{{skin|}}}|hide=Raw hide{{Category|Leather}}|scale=Scales{{Category|Scales}}|chitin=Chitin{{Category|Chitin}}|none=not skinnable|#default={{{skin|}}}{{Category|Unrecognized skin}}}}}}|{{!-}}}}
{{#if:{{{wool|}}}|{{inforow|[[Wool]]|{{{wool|}}}}}|{{!-}}}}
{{#if:{{{feather|}}}|{{inforow|[[Feather]]|{{{feather|}}}}}|{{!-}}}}
{{#if:{{{gizzard_stone|}}}|{{inforow|[[Gizzard stone]]|{{{gizzard_stone|}}}}}|{{!-}}}}
{{#ifeq:{{{contrib|}}}|no|{{!-}}|{{infocell|style=text-align:center; background-color: #eee; border-top: 1px solid #aaa|''There is too little information about this creature. Please contribute if you can!''{{Category|Incomplete butchering returns|{{PAGENAME}}}}}}|{{!-}}}}
}}
{{#ifexpr:{{#if:{{{wiki|}}}|1|0}} and {{#ifeq:{{{wiki|}}}|no|0|1}}|{{infocell|style=text-align:center; background-color: #eee; border-top: 1px solid #aaa|1=[[wikipedia:{{#ifeq:{{{wiki|}}}|yes|{{{name}}}|{{{wiki|}}}}}|Wikipedia article]]}}|{{!-}}}}
{{infoend}}<noinclude>{{documentation}}[[Category:Infobox templates]]</noinclude>

Template:CreatureInfo v0.40

2023-01-10T00:24:50Z

Jan:

{{infostart|{{{name}}}}}
{{infocell|style=color: {{fgcolor|{{{color|7:0:1}}}}}; background: black; text-align:center; vertical-align:center;|1=
{{#if:{{{image|}}}|<div class="mw-collapsible" id="mw-customcollapsible-classicimage" style="image-rendering: pixelated; -webkit-image-rendering: pixelated; -moz-image-rendering: pixelated;">[[File:{{{image}}}|200x128px]]</div>}}
<div class="{{#if:{{{image|}}}|mw-collapsible mw-collapsed}}" id="mw-customcollapsible-classicimage" style="font-size:xx-large; font-weight: bold; font-family: 'Courier New', 'Quicktype Mono', 'Bitstream Vera Sans Mono', 'Lucida Console', 'Lucida Sans Typewriter', monospace; {{#if:{{{image|}}}|height: 128px; line-height: 128px;}}">{{char|{{{symbol|?}}}}}</div>
{{#if:{{{image|}}}|Toggle}}}}
{{#if:{{{pref|}}}|{{infopref|{{{pref}}}}}}}
{{infoheader|Biome}}
{{infocell|{{#if:{{{biome|}}}|{{{biome|}}}|Any location}}}}
{{#ifeq:{{{vary|no}}}|no|{{!-}}|
{{infoheader|Variations}}
{{infocell|{{{vary|unknown}}} }} }}
{{#ifexpr:{{#if:{{{alignment|}}}|1|0}} or {{#ifexpr:{{{bldgdest|0}}}>0|1|0}} or {{#if:{{{attribs|}}}|1|0}}|
{{infoheader|Attributes}}
{{#if:{{{alignment|}}}|{{inforow|Alignment:|{{{alignment}}} }}|{{!-}}}}
{{#ifexpr:{{{bldgdest|0}}}>0|{{infocell|[[Building destroyer]]: Level {{{bldgdest}}}{{Category|Building destroyer}}}}|{{!-}}}}}}
{{#if:{{{attribs|}}}|{{infocell|{{span-hide}}{{{attribs}}}{{end-span}}}}|{{!-}}}}
{{#ifexpr:{{#if:{{{pet|}}}|1|0}} or {{#if:{{{exotic|}}}|1|0}}|
{{infoheader|Tamed Attributes}}
{{inforow|Pet value|{{formatnum:{{{petvalue|0}}}}}}}
{{#if:{{{grazer|}}}|{{inforow|[[Grazer]]:|{{{grazer}}} {{Category|Grazer}}}}|{{!-}}}}
{{#if:{{{tame_attribs|}}}|{{infocell|{{span-hide}}{{{tame_attribs}}}{{end-span}}}}|{{!-}}}}
{{infocell|{{#ifexpr:{{#expr:{{{train_hunt|0}}}+{{{train_war|0}}}>0}}
|[[Animal trainer|Trainable]]:  {{#ifexpr:{{{train_hunt|0}}}>0|Hunting {{Category|Hunting animals}}|}}   {{#ifexpr:{{{train_war|0}}}>0|War {{Category|War animals}}|}}|Not hunting/war [[Animal trainer|trainable]]}}}}|{{infoheader|bg=#fbb|Cannot be tamed}}}}{{
#ifexpr:{{#expr:{{{size0|0}}}+{{{size1|0}}}+{{{size2|0}}}}}>0| 
{{infoheader|[[Size]]}}
{{infocell|{{#ifexpr:{{{size0|0}}}>0|{{inforow|'''Birth:'''|{{formatnum:{{{size0}}} cm3 }}}}
{{#ifexpr:{{{size1|0}}}>0|{{inforow|'''Mid:'''|{{formatnum:{{{size1}}} cm3 }}}}}}
|{{#ifexpr:{{{size1|0}}}>0|{{inforow|'''Birth:'''|{{formatnum:{{{size1}}} cm3 }}}}}}}}
{{#ifexpr:{{{size2|0}}}>0|{{inforow|'''Max:'''|{{formatnum:{{{size2}}} cm3 }}}}}}}}||}}
{{#if:{{{eggs|}}}|{{infoheader|[[Food|Food products]]}}
{{#if:{{{eggs|}}}|{{inforow|[[Egg]]s|{{{eggs}}}}}}}}}{{
#if:{{{childage|}}}{{{adultage|}}}{{{maxage|}}}|<nowiki/>
{{infoheader|Age}}
{{#if:{{{childage|}}}|{{inforow|Child at:|{{{childage}}}}}}}
{{inforow|Adult at:|{{{adultage}}}}}
{{inforow|Max age:|{{{maxage}}}}}}}
{{infoheader|{{#switch:{{{death|}}}
|rot=Rotting leaves
|item=Becomes after death
|nobutcher=Cannot be butchered
|butcher |#default=[[Meat industry|Butchering returns]]}}}}
{{#if:{{{valm|}}}|([[Multiply value|Value multiplier]] ×{{{valm|}}})}}
{{#ifeq:{{{death|}}}|item|{{infocell|{{{item|}}}}}|{{!-}}}}
{{#switch:{{{death|}}}
|nobutcher
|item={{!-}}
|#default={{infocell|'''Food items'''}}
{{#if:{{{meat|}}}|{{inforow|[[Meat]]|{{{meat|}}}}}|{{!-}}}}
{{#if:{{{fat|}}}|{{inforow|[[Fat]]|{{{fat|}}}}}|{{!-}}}}
{{#if:{{{brain|}}}|{{inforow|[[Brain]]|{{{brain|}}}}}|{{!-}}}}
{{#if:{{{gizzard|}}}|{{inforow|[[Gizzard]]|{{{gizzard|}}}}}|{{!-}}}}
{{#if:{{{heart|}}}|{{inforow|[[Heart]]|{{{heart|}}}}}|{{!-}}}}
{{#if:{{{lung|}}}|{{inforow|[[Lung]]s|{{{lung|}}}}}|{{!-}}}}
{{#if:{{{intestine|}}}|{{inforow|[[Intestines]]|{{{intestine|}}}}}|{{!-}}}}
{{#if:{{{liver|}}}|{{inforow|[[Liver]]|{{{liver|}}}}}|{{!-}}}}
{{#if:{{{kidney|}}}|{{inforow|[[Kidney]]s|{{{kidney|}}}}}|{{!-}}}}
{{#if:{{{tripe|}}}|{{inforow|[[Tripe]]|{{{tripe|}}}}}|{{!-}}}}
{{#if:{{{sweetbread|}}}|{{inforow|[[Sweetbread]]|{{{sweetbread|}}}}}|{{!-}}}}
{{#if:{{{eye|}}}|{{inforow|[[Eye]]s|{{{eye|}}}}}|{{!-}}}}
{{#if:{{{spleen|}}}|{{inforow|[[Spleen]]|{{{spleen|}}}}}|{{!-}}}}
{{infocell|'''Raw materials'''}}
{{#if:{{{bone|}}}|{{inforow|[[Bones]]|{{{bone|}}}}}|{{!-}}}}
{{#if:{{{skull|}}}|{{inforow|[[Skull]]|{{{skull|}}}}}|{{!-}}}}
{{#if:{{{ivory|}}}|{{inforow|[[Ivory]]|{{{ivory|}}}{{Category|Ivory}}}}|{{!-}}}}
{{#if:{{{tooth|}}}|{{inforow|[[Teeth]]|{{{tooth|}}}{{Category|Tooth}}}}|{{!-}}}}
{{#if:{{{hoof|}}}|{{inforow|[[Hooves]]|{{{hoof|}}}{{Category|Hoof}}}}|{{!-}}}}
{{#if:{{{horn|}}}|{{inforow|[[Horns]]|{{{horn|}}}{{Category|Horn}}}}|{{!-}}}}
{{#if:{{{shell|}}}|{{inforow|[[Shell]]|{{{shell|}}}}}|{{!-}}}}
{{#if:{{{skin|}}}|{{inforow|[[Skin]]|{{#switch:{{{skin|}}}|hide=Raw hide{{Category|Leather}}|scale=Scales{{Category|Scales}}|chitin=Chitin{{Category|Chitin}}|none=not skinnable|#default={{{skin|}}}{{Category|Unrecognized skin}}}}}}|{{!-}}}}
{{#if:{{{wool|}}}|{{inforow|[[Wool]]|{{{wool|}}}}}|{{!-}}}}
{{#if:{{{feather|}}}|{{inforow|[[Feather]]|{{{feather|}}}}}|{{!-}}}}
{{#if:{{{gizzard_stone|}}}|{{inforow|[[Gizzard stone]]|{{{gizzard_stone|}}}}}|{{!-}}}}
{{#ifeq:{{{contrib|}}}|no|{{!-}}|{{infocell|style=text-align:center; background-color: #eee; border-top: 1px solid #aaa|''There is too little information about this creature. Please contribute if you can!''{{Category|Incomplete butchering returns|{{PAGENAME}}}}}}|{{!-}}}}
}}
{{#ifexpr:{{#if:{{{wiki|}}}|1|0}} and {{#ifeq:{{{wiki|}}}|no|0|1}}|{{infocell|style=text-align:center; background-color: #eee; border-top: 1px solid #aaa|1=[[wikipedia:{{#ifeq:{{{wiki|}}}|yes|{{{name}}}|{{{wiki|}}}}}|Wikipedia article]]}}|{{!-}}}}
{{infoend}}<noinclude>{{documentation}}[[Category:Infobox templates]]</noinclude>

Dwarf Fortress Wiki talk:Versions

2023-01-08T08:57:18Z

Jan: /* Graphics in Skill Infoboxes */

{{archive|
# [[DF Talk:Versions/Archive 1|Page 1]]}}

== Version 0.31.19 starts a new DF generation? ==

My reading of Toady's comments on the release of 0.31.19 is that it came out basically because he felt it would take too long to get DF all the way to 0.32. With the ore changes, the sitefinder changes, the addition of grazing and several different industries, there's a lot of changes between 31.18 and 31.19. So I'm thinking it might be a good idea to call it the first release of DF2011 - and what we refer to as "DF2010" would then become 0.31.18.

Thoughts? --[[User:DeMatt|DeMatt]] 07:06, 28 February 2011 (UTC)

==Revisiting Redirects==
I wasn't around when the redirect policy was created, and I'm having trouble understanding the rationale. The example claims that linking [[Main:Cheese]] to [[cv:Cheese maker]] is problematic...but mainspace only ever redirects to the current version. If the best target in the current version is cheese maker, why not link to it directly? (It's not, at least for Cheese, since [[DF2012:Cheese]] exists now.) The explanation seems to be claiming that 40d articles that link to Cheese will follow the Mainspace link--but that hasn't been the case for a long while now. Articles in 40d automatically link against other articles in 40d, so that version remains internally consistent no matter where mainspace links to in the current version. For a current example, what do we gain by linking [[Main:Mead]] to [[cv:Mead]] and linking [[DF2012:Mead]] to [[DF2012:Alcohol]]?

If this really is just an outdated procedure, I recommend we drop the mummery and allow mainspace to link to cv:(best target). Double redirects ''may'' work (sometimes, but [[Main:Mead]] demonstrates a common problem where automatic redirection fails), but if they are unnecessary I think they should be avoided, partly because of problems like [[Main:Mead]] and partly because of the effort required to protect double redirects from users who believe they are problematic.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:16, 8 January 2014 (UTC)

:I was just thinking that. I'm currently attempting to write a basic extension to eliminate the need for mainspace redirects entirely, although Mediawiki's class structure may make this more difficult than I had hoped (the only method I've found for resolving redirects takes the ''article text'' instead of a title, e.g. "#REDIRECT ..."). I do agree that the current situation with redirects isn't ideal, so I'm hoping this will work better (once I get it to work). --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:42, 8 January 2014 (UTC)

Okay, that wasn't quite as clear as I meant it to be. In general, I think this is a tricky situation. Mediawiki wasn't designed to have five content namespaces, and certainly not chains of redirects between them. The problem that was pointed out in the [[DF:REDIR|policy]] is the fact that with:
Main:Foo -> cv:Bar
pages in the cv: namespace can't use [[<nowiki/>foo]], since the namespace links modification causes it to be treated as [[<nowiki/>cv:foo]] instead, which doesn't exist. The current suggested solution is this:
Main:Foo -> cv:Foo -> cv:Bar
This fixes the problem of [[<nowiki/>foo]] not working on cv pages, but creates issues with double redirects not always working. Another solution, which is more intuitive to new editors, is:
Main:Foo -> cv:Bar
cv:Foo -> cv:Bar
Both require creating two redirects. The first method has the advantage of ''ensuring'' that the cv redirect exists (otherwise, main:foo would be a redlink), while the second has the advantage of working more reliably in a couple cases.

What I'm trying to do is make main:Foo "jump" to cv:Foo when cv:foo exists, ''even if main:foo doesn't exist'' (basically it would treat all mainspace pages as redirects to cv pages, but only if the cv page exists and not the mainspace page). I had main:Bar jumping to cv:Bar fine, but if cv:Foo redirected to cv:Bar, accessing main:Foo would mysteriously stop at cv:Foo even if I increased the redirect limit. What I'm trying to do now is follow the redirects internally, without relying on Mediawiki to do it automatically - unfortunately, that has proved to be harder than I had hoped (and I sent my web server into an infinite loop while trying). I will try to work on this some more when I get a chance, although I'm not sure when that'll be yet :(. For now, feel free to fix broken double mainspace redirects as necessary, as long as redirects in the DF2012 namespace stay pointing to the right page (and new mainspace redirects get added in the DF2012 namespace too). --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:21, 9 January 2014 (UTC)

:You're treating cv like a namespace--it's not. It is simply shorthand for "fill in the current version here". [http://dwarffortresswiki.org/index.php?title=User_talk:Briess&diff=182404&oldid=181281 As I discovered a long time ago on a server not far away], linking from Main:Foo to cv:Foo tends to break redirection chains. If, instead of linking to cv:Foo, you link to DF2012:Foo, it might just work. It would, of course, be better if your patch could evaluate cv itself, but even if you have to hardcode the current version it's a single point of maintenance that requires update very infrequently. (For that matter, we could probably dispense with the cv hack entirely and just have a bot update mainspace links from DF2012 to DF201X when we switch to a new version.)--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:05, 9 January 2014 (UTC)
::I know cv isn't a namespace - I was just trying to avoid future confusion when the DF2012 namespace changes. It's interesting that changing "cv" to "DF2012" fixes some broken redirects, although I've found that simply making an edit to a broken redirect can usually fix it as well. I've actually had the most problems with double redirects when the second one (in the DF2012 namespace) doesn't use the DF2012 prefix (e.g. main:Foo containing <nowiki>[[cv:Foo]] and DF2012:Foo containing [[Bar]]</nowiki>). I'd rather keep the cv alias even if it isn't necessary for mainspace redirects when I get the patch to work, since it makes it easier to refer to the current version of the page (for example, several MDF articles contain links to a vanilla page for things that don't change in the mod).
::Also, using aliases like "cv" is supported by Mediawiki; in fact, several WMF wikis use them (for example, "[[wikipedia:WP:Redirects|WP:Redirects]]" on Wikipedia). It's quite likely that Mediawiki isn't processing double redirects using aliases correctly, though, since that's uncommon on most wikis. --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:35, 9 January 2014 (UTC)

In light of the lack of support for the current redirect policy, I propose we replace the current redirect section with:

:Mainspace article pages should use the cv: alias when redirecting to a versioned page, which will automatically update the link when a new version is released. For example, page "Main:Foo" should redirect to page "cv:Bar" (where "Bar" is the page that best describes the topic Foo in the current version).

:Pages in mainspace should only redirect to an older versioned page if that content no longer exists in the current version of the game (e.g. [[Cave river]], [[Chunk]]). In these cases the cv: alias cannot be used.

:Pages inside a versioned namespace should not use the cv: alias. Instead, they should redirect to the best page within that versioned namespace (e.g. [[DF2012:Dodging]], [[v0.31:Drink]]).

:Due to limitations of the wiki software, double redirects should be avoided if possible. When fixing double redirects in mainspace, please make sure to use the cv: alias as appropriate.

If no one objects, I will make this change in a few days.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:21, 15 January 2014 (UTC)

:Okay with me. It may be worth mentioning that double redirects only really need to be changed when they don't work (since changing a lot of redirects that work isn't necessary), but I think it's clearer and more relevant than the current policy. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:26, 16 January 2014 (UTC)

Done.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:55, 22 January 2014 (UTC)

I was finally able to get my extension to work after being motivated by one too many malfunctioning redirects. It now causes nonexistent pages in the main namespace to behave exactly like redirects to their DF2012 counterparts (when linked to, accessed directly, and transcluded). Double redirects also work (up to 100, in fact, although that was a temporary safety measure that I'll probably change). This means we'll be able to safely get rid of all mainspace redirects (redirects that redirect to something other than "cv" will still function if not deleted). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:20, 14 March 2014 (UTC)
:What about articles which don't exist in the current version but do exist in older versions? Will those still need mainspace redirects, or will your extension be able to automatically redirect them to v0.31/40d/23a? --[[User:Quietust|Quietust]] ([[User talk:Quietust|talk]]) 01:29, 14 March 2014 (UTC)
::It ignores all mainspace pages that actually have content, including redirects, so pages like [[masons guild]] won't be affected (unless deleted). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:47, 14 March 2014 (UTC)

Done and deployed. [[Cat]] is still treated as a redirect, even though I just deleted it (try clicking on the "redirected from" link). Pages that exist are ignored, so [[Masons guild]] and [[History of Dwarf Fortress]] still function normally (as a redirect to a 23a page and a non-redirect, respectively). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 18:57, 14 April 2014 (UTC)

I'm sending around a bot right now to delete all redirects of the format "foo -> cv:foo" (a surprising number don't fit this format, so I'm leaving them alone for now). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:43, 14 April 2014 (UTC)

:I'm confused. Do we use double redirects or not? Is there a single place we define our linking policy (including redirects), and is it updated?
:I had trouble linking to [[Consolidated_development]] in [[v0.34:Dragon]]. It kept pointing to v0.34:Consolidated_development, which does not exist. I ended up linking to Main:Consolidated_development to make it work. --[[User:Nahno|Nahno]] ([[User talk:Nahno|talk]]) 10:18, 1 July 2014 (UTC)

::That's a separate problem altogether - links in the versioned namespaces (v0.34, v0.31, 40d, 23a) automatically link to pages within their namespace. I may be able to set up a fallback to mainspace once I'm able to deploy again, but for now the "main:" alias is the intended solution. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 11:36, 1 July 2014 (UTC)

== Google often directs people to the 0.31 page ==

I've noticed a couple of times that finding a wiki page from an external search will often drop me onto a page from an older version. Is it possible to mitigate this somehow for new players? I could imagine something like redirecting old:Bar -> cv:Bar unless the user has come from old:Foo; no idea if that would actually work though. [[User:PeridexisErrant|PeridexisErrant]] ([[User talk:PeridexisErrant|talk]]) 11:48, 4 May 2014 (UTC)

:As a temporary solution, I could write a script that displays a banner of some kind if the user came from an external site. I'll ask Briess if he can do anything on the server level to increase the weighting of the current version's pages. (Obviously there are situations where people are looking for old pages, like [[23a:dungeon master]], so we don't want to disable indexing entirely on old pages.) —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:03, 4 May 2014 (UTC)

== DF2014? ==

As Toady [http://www.bay12games.com/dwarves/ draws closer to a new release], it might be worthwhile to discuss the addition of a new version to the wiki. The upcoming release covers two years of changes and introduces a number of new plants, foods, drinks, multi-tile trees, climbing, jumping, etc., so it is likely to have significant changes from the current DF2012. To avoid having people start new pages (and lose all the effort spent refining the prior version's page), I think it would be best to have a bot automatically copy over the DF2012 pages as a starting point for DF2014. I would suggest that these copied pages include a noticebox template mentioning that the content may be outdated, so that we can easily track which pages have been reviewed. I think either the {{tl|version check}} or {{tl|old}} template would work. --[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 19:43, 5 May 2014 (UTC)

:This is what [[User:QuietBot]] did after the 0.34 release, so it's certainly possible to use the same script to migrate to DF2014. I would like a way of tagging migrated pages, since inaccuracies in some pages went unnoticed for months after they were migrated. Since {{tl|old}} is already in use, {{tl|version check}} may be a better solution (it can be reworded slightly, or we can make a separate template for DF2014 migration). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:23, 1 June 2014 (UTC)
:Made [[Template:DF2014 migrated]] as an example. Any thoughts? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:32, 1 June 2014 (UTC)

== Redirects inconsistency ==

Following a redirect is supposed to be exactly the same as going straight to the page it redirects to, but this actually isn't the case:
* Go to [[Seeds]] and you get [[v0.34:Seed]] (outdated)
* Go to http://dwarffortresswiki.org/index.php?title=Seeds&redirect=no and click on the link and you get to [[DF2014:Seed]] (current)
So if you search for "seed", the top result is the DF2014 version. But search for "seeds" and you get the redirect, which sends you to the outdated page instead. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 23:22, 22 February 2015 (UTC)

While I'm talking about redirects, it seems redirects to sections don't work: see [[DF2014:How do I manage my seeds and crops]]. I know MediaWiki is capable of this trick because Wikipedia does it. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 23:32, 22 February 2015 (UTC)

:I have absolutely no idea why [[seeds]] redirects to a v0.34 page - it could be a Mediawiki bug. The section links issue is due to a known issue in the redirect extension we use, which has yet to be fixed. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:01, 23 February 2015 (UTC)
:It looks like deleting both [[Seeds]] and [[DF2014:Seeds]] fixed things (by allowing AutoRedirect to handle the redirects instead). Feel free to tag any others with {{tl|bad redirect}}. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:03, 23 February 2015 (UTC)
::It gets stranger. [[Vial]] redirects explicitly to [[cv:Flask]] which displays (when you look at it with &redirect=no) as [[DF2014:Flask]], but still goes to the v0.34 version. It seems redirects interpret the cv: pseudo-namespace (or whatever it's called) in an outdated way. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 18:08, 23 February 2015 (UTC)
::I've added a note to this page about this issue. If it gets resolved, the note should be removed. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 21:04, 23 February 2015 (UTC)

==Reorganizing versions==

The internet deals with moved content... poorly. Google is still linking to v0.34 pages more than a year after the switch to "DF2014", and even the wiki software still has cached links pointing to the old version pages.

I propose reorganizing versions on the wiki to avoid moving content whenever possible. Instead of having a temporary "current version" namespace that changes occasionally, all the current information gets promoted to the Main namespace. When the next version split occurs, the Main articles as of a certain revision number can be copied to the newly-created permanent "old version" namespace, while all the current information remains in Main. This not only fixes the link rot issue, but it has a few other benefits as well: fewer administrative tasks, no lockdown (a historical version of the Main pages can be copied at any point, even if the Main articles are already modified for the new version), almost all the article history is maintained in the Main article (instead of being spread unevenly across multiple versions), no "temporary" namespaces are needed, fewer problematic long redirect chains, and hopefully less user confusion (since Main gets priority in search results, etc.).

As an example, today we would not have a DF2014 namespace (which is good because "temporary" namespaces historically disappear anyway). If you ran a search for [[seed]] you'd end up at Main:seed, which would have all the current information on seeds. The version box at the top of the page would still link to the older versions of the seed article. When a new version is released, an admin would choose a revision number and copy the Main:seed article as it exists at that revision number to v0.40:seed. That's it. One historical copy that needs little to no new editing, and zero redirections/moves.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 19:02, 27 July 2015 (UTC)

:Makes sense to me. It would involve a lot of work, though (e.g. fixing templates and categories to account for the current version being in mainspace), although that should be doable thanks to {{tl|category}}, {{tl|version switch}}, etc.. A bot could be set up to copy revisions from before a release date as well, which would be more difficult (and maybe slower) than a direct copy, but not severely. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:24, 30 July 2015 (UTC)

:Actually, there are a few issues with that, namely that there wouldn't be an easy way to distinguish between versioned and non-versioned mainspace pages. There are ways to resolve Google search priority (we can exclude pages from older versions from search engine results if there are newer versions of those pages available, for example). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:47, 6 August 2015 (UTC)

::There aren't very many non-versioned mainspace pages, and determining if a page is versioned is as simple as looking for the version template and/or categories added by the version template (e.g. copy [http://dwarffortresswiki.org/index.php/Category:Current this category] instead of Main:*). The problem with "suggesting" newer pages to Google is that they obviously aren't crawling our wiki regularly (if they were, the fact that the mainspace redirects point to new pages would automatically be picked up). Even if your Google hints worked they wouldn't do anything for all the other broken links out on the 'net.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:35, 6 August 2015 (UTC)

::: Google actually crawls the wiki constantly - we probably get crawl hits from google for a continuous block of 2-3 hours per day, each and every day. Why they are slow to update is beyond me though. I can't remember why we didn't do this initially, but there was a technical limitation involved if I remember correctly. --[[User:Briess|Briess]] ([[User talk:Briess|talk]]) 22:05, 6 August 2015 (UTC)

::: There are <meta> tags that can be used to hide pages from search results (for search engines that recognize them, that is). Searching for {{tl|av}} or [[:Category:Current]] might work, although we'd have to make sure all of the DF2014 pages include that (some pages don't, particularly some disambiguation pages, although all of them should). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:53, 6 August 2015 (UTC)

:Is there a particular reason main and current are separate to begin with?—[[User:CLA|CLA]] ([[User talk:CLA|talk]]) 00:17, 7 August 2015 (UTC)

::It's mostly intended to distinguish between versioned and non-versioned pages and make version-related templates simpler to work with, since every versioned page has a namespace. I wasn't active here in 2010 when this system was created, so Briess and Emi would know more.
::Another issue I just thought of with Loci's suggestion is categories - currently, categories like [[:Category:Animals]] are used to organize the versioned sub-categories. Sure, we can change {{tl|Category}} to categorize mainspace pages in [[:Category:v0.40:Animals]] or [[:Category:DF2014:Animals]], but that would be less straightforward because there wouldn't be a namespace with that name (until pages are migrated when a newer major version is released). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 13:05, 7 August 2015 (UTC)

:Moving current pages to the main namespace sounds like a great idea. -[[User:Jecowa|Jecowa]] ([[User talk:Jecowa|talk]]) 20:47, 4 January 2018 (UTC)

Another thought: dealing with migrating redirects could be difficult with this proposal - specifically, determining which redirects should be migrated to a versioned namespace. Redirects can't contain {{tl|av}}, at least not before ``#REDIRECT``. I ''think'' it would be possible to copy pages in two stages, though - all non-redirects first, then all redirects whose targets were also copied. Thoughts? Anything I'm missing? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:41, 27 June 2019 (UTC)

Some subpages (particularly /raw and /Edit notice) also deliberately lack {{tl|av}}, although those shouldn't be too hard to handle. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:35, 9 July 2019 (UTC)

:Redirect pages (and all other edge cases I've looked at) can be included in categories (like [[:Category:Current]]) to determine whether or not they should be copied into an archival version. But if the redirects are "properly qualified" then they can all be copied over blindly. Mainspace redirects pointing to versioned information should use a blank namespace (which will be automatically constrained to the archival namespace); mainspace redirects pointing to unversioned information should use an explicit "Main" (which will automatically link back to the unversioned page). Then, when [[[[Toady]]]] gets copied to [[[[v0.4x:Toady]]]] it will point back to [[[[Main:Toady One]]]]. Meanwhile, [[[[Beer]]]], copied to [[[[v0.4x:Beer]]]], will properly point to [[[[v0.4x:Alcohol]]]].--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:00, 14 July 2019 (UTC)

::I think qualifying redirects is the best solution here - categorizing redirects manually is another possible source of errors, since categories (or a lack thereof) would only be visible on the redirect page itself, and [[:Category:Current]] is a hidden category. Copying over mainspace redirects into versioned namespaces would also resolve some issues that have come up due to those not reliably existing currently. I should be able to set up a bot script to add "main:" to current mainspace redirects (and it shouldn't break anything, since those redirects go to other mainspace pages anyway). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:57, 14 July 2019 (UTC)

(Note: I wrote all of this without noticing the previous discussion above.) I was wondering, when the wiki creates a new namespace for a major release again, if it is possible to ''not'' create a namespace for the next current version (e.g. "DF202x") and instead have the mainspace articles (which are currently redirects) become the new cv and move the content there. Therefore, [[cv:Cat]] would just be "[[Cat]]" (or [[Main:Cat]]).

Certain namespace-related templates like [[Template:Ns/0]] would need to be changed, though nothing significant as far as I know. For most cases, any "DF2014" would be replaced with "Main" or even blank. There's also multiple extensions handling the current namespace system and they may need to be modified too, though I'm not sure if or how much. I'm guessing based on the discussions above that it will change stuff up.

My reason is the current namespace is increasingly becoming more anachronistic. "DF2014" could be misinterpreted as "this page is about the 2014 version of the game" or "this page was last updated in 2014", which I've seen a few people in forums mention. Granted that [[Template:Av]] is on the top of very article, I still think the namespace is inconsistent with the recentness of the article. But how is this related to what I'm asking for? Let's say we continue the current system: if we happen to do a new namespace change this year and create DF2020, the next major release (after graphics/UI) will be mythgen, which is estimated to take several years to develop (the Big Wait), and so the anachronism will start over again. The proposed way will prevent this from occurring for the next major release and every release thereafter.

I think the confusion with having a namespace that becomes old-fashioned overtime supersedes the confusion with not marking current versioned articles with a namespace. Most users just search "Cat" on the search bar and naturally expect to get information about the latest release of DF. So if users go a page that's just titled "Cat", they won't expect outdated info about cats from a previous release. That's how the current system works anyways. We'll be skipping the two-step process that we have now. It'll make several wiki tasks much simpler as well. Editors can create new articles for current versions without remembering to add a namespace. It'll fix any existing issues with (double) redirects; instead of [[Main:Kitten]] redirecting to [[cv:Kitten]], which goes to [[DF2014:Kitten]], which then redirects to [[DF2014:Cat]], [[Main:Kitten]] would just redirect to [[Main:Cat]]. And the cv: alias will no longer be necessary since "cv:" = "Main:" and will be forever.

There's no need to differentiate the current version and previous versions with a namespace for the current version is what I'm saying. Articles of previous versions will retain their respective namespaces. Users will still type "40d:Cat" to go to the 40d version of the article, but if they want the current version, they'll just type "Cat" (like now). The mainspace containing the "live" version of an article is natural and would create no uncertainty when browsing the wiki. And it would simplify the wiki somewhat and future-proof this anachronism problem. As a bonus, this change will also prevent web search engines from showing previous version pages when typing "DF cat" or something. (This isn't happening right now as DF2014 has been the current namespace for ~6 years, but it'll happen again when everything moves to a new namespace.)

This is the gist of it, and I may have ignored most of the problems with this proposal. I have personally wished for the whole version namespacing be made less complicated and have been seeking for a solution, and I feel like this is the best way to go about in the future. – [[User:Doorkeeper|Doorkeeper]] 21:27, 14 August 2020 (UTC)

:<s>Whoops, looks like Loci already proposed this exact thing long ago. I definitely missed that discussion and should have checked first. My apologies. I'll move my text to that section and remove this one. – [[User:Doorkeeper|Doorkeeper]] 21:36, 14 August 2020 (UTC)</s> Done. – [[User:Doorkeeper|Doorkeeper]] 21:40, 14 August 2020 (UTC)

:The main issue I have with that is that putting pages about the current version in a namespace also differentiates between those pages and pages not about ''any'' version (for example, [[Toady One]] does not need a 40d or v0.34 page). Yes, we can use {{tl|av}} to mark versioned pages, but people often forget to add that to new pages. The current system also allows determining whether a page is versioned or not from its title, which makes migrations a lot faster. Relying on {{tl|av}} would require either reading the content of every page (which would slow scripts down significantly) or cross-checking with the list of all pages including the template (feasible, but a bit more complicated, and still susceptible to missing templates). I suppose that manually fixing and migrating pages missing {{tl|av}} later wouldn't be too much work, though.
:I am definitely in favor of changing "DF2014" (or a new namespace) to "Current", though. I was in favor of "DF2014" in 2014, but I don't think it makes sense anymore, and "Current" seemed to be a popular alternative in both the DF2012 and DF2014 discussions on the matter. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:02, 16 August 2020 (UTC)

== Weird redirect behaviour ==

[[Pump stack]] redirects to [[cv:Screw pump#Pump stack]]. If you look at the redirect itself it says it redirects to DF2014 namespace, which is correct. But if you actually follow the redirect, it goes to v0.34 namespace. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 16:10, 20 August 2018 (UTC)
:Yeah, that's part of the issue described in the above section (the wiki caching part, not on Google's end.) —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 15:00, 21 August 2018 (UTC)

== v50 organization ==

Some wiki admins have had a talk on Discord and decided that the most sustainable path forward is to put content for all future versions of DF in the main namespace. We will be working on a bot to do this in the next few days. Feel free to chime in with suggestions here. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:56, 14 December 2022 (UTC)

:Is it maybe possible to do backwards-namespacing? Like we have a "Main" namespace, which people are free to update, and whenever there's a new version of DF the "Main" namespace is copied into a namespace for the then old version, much like how you'd branch a stable branch from a development branch when working with a git-project? [[User:Therahedwig|Therahedwig]] ([[User talk:Therahedwig|talk]]) 23:13, 14 December 2022 (UTC)

::Yeah, we could do that if we decide to. We were talking about doing that for v50, actually, and might still do something similar to preserve edit history if it doesn't end up being too hard to automate. Our hope is that we will not introduce new namespaces for v50 -> v5x, unless there is a serious breaking change (and hopefully there isn't one). But if we change our mind, one advantage of the type of migration you mentioned is that it can be done retroactively - we can copy historical revisions that were current at the time of the release, and would only lose some typo fixes made after the release that apply to earlier versions as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:11, 15 December 2022 (UTC)

ETA is < 24 hours. Doing some final checks on a migration script. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 07:08, 19 December 2022 (UTC)

: We should really have a task list as there are many things that change and need updating. Including but not limited to:
:* Most templates that used the previous namespace convention broke, including nav templates.
:* Many game files changed locations and their pages need to be updated.
:* Raws need to be updated.
:* Various features added, changed, removed.
:* UI has been changed -- though I am more inclined to wait for classic release to avoid extra work --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 06:56, 20 December 2022 (UTC)

"''Raws need to be updated.''" Including applying text wraparound where necessary, I suppose - more than a few of them have proven to be that special kind of...''difficult'' to navigate otherwise, shall we say? [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 12:52, 20 December 2022 (UTC)

:There is already a task list in the [[#v50 migration|section below]] that includes templates and raws, with an explanation. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:25, 20 December 2022 (UTC)

== v50 migration ==

The initial migration script is done. New content is in the '''main''' namespace, e.g. [[Cat]]. Old content is still at [[DF2014:Cat]]. History was migrated to the ''new'' (main namespace) articles.

I know several things are broken still. Please reply if you find any others:
<div style="border-left: 2px solid red">
* <s>Versioned templates haven't been migrated yet (e.g. {{tl|vermin}} on [[Ant]])</s>
** Fixed. Most were migrated by a bot.
* <s>Raws are missing on all pages that use them.</s>
** This also affects sidebars, such as on [[Cat]] and [[Microcline]].
** Update: The DFRawFunctions extension has been upgraded to include v50 raws, using the "v50:" prefix for filenames instead of "DF2014:". <s>I haven't finished a migration script to create the /raw pages themselves, but they can typically be created manually by copying the DF2014 /raw pages and changing "DF2014" to "v50" everywhere.</s> —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:20, 1 January 2023 (UTC)
** Update 2: Raws have been added for all pages! They were copied from the "DF2014" pages and had "DF2014" replaced with "v50", which appears to have worked from a spot-check, but let me know if you find any problems. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:57, 4 January 2023 (UTC)
* Some pages where the DF2014 page was a redirect to a main namespace page that contained content were migrated incorrectly.
** In this case, the main namespace page is usually a redirect to itself. This can be fixed by undoing LethosorBot's edit to the main namespace page, then copying the content to the DF2014 page.
** Update: most seem to have been fixed manually - thanks! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:41, 21 December 2022 (UTC)
* <s>Some main-namespace talk pages redirect to DF2014 talk pages. Some of these redirects work, and some (usually older ones) do not.</s>
** Fixed with a bot. Some redirects from talk pages to other deleted talk pages are now broken, e.g. [[Talk:Above_ground]] (exists) -> [[Talk:Tile attributes]] (redlink). I am leaving them like that because they redirect to where the talk page should be created, but I'm also fine with people deleting them if they really want to. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:41, 21 December 2022 (UTC)
* {{tl|quality}} for new articles is disabled (see below)
* Some links from DF2014 to Main weren't working: e.g. the version selector [[DF2014:Mason's workshop]] was linking to [[DF2014:Main:Mason's workshop]] instead of [[Main:Mason's workshop]]. I'm not sure exactly why, but I fixed it with a change to the NamespaceLinks extension. Let me know if you spot similar broken links. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:19, 21 December 2022 (UTC)
</div>

—[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:54, 20 December 2022 (UTC)
:The quality levels of the 50.03 pages seem to be missing. I'm not sure if that's covered under that first point. [[User:Trainzack|Trainzack]] ([[User talk:Trainzack|talk]]) 06:47, 20 December 2022 (UTC)
::If the the [[Dwarf Fortress Wiki:Quality]] feature can be made to work with namespace scheme change, I suggest to automatically assign the lowest quality rating to all pages, alternately add the {{tl|old}} to all pages. Otherwise there will be a lot of pages that will fall through the cracks. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 09:12, 20 December 2022 (UTC)
:::I disabled {{tl|quality}} in the main namespace because it would require some rework to make the rating script and the template work properly there. Feel free to take a stab at the template. I will see what can be done on the extension side. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:14, 20 December 2022 (UTC)
::::What needs to be done on the template side? I'm not sure I see too big of an issue leaving pages as "unknown-quality" for now (or just change the default to tattered) until we get the rating script working. Is that script up anywhere, anything that could be helped with? [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 11:10, 2 January 2023 (UTC)
:::::They're already marked as unknown. Really the only issue I know of with the template is that it doesn't show up with some of the newer skins we added, and that can be fixed by getting rid of the absolute positioning. As for the script, it can be found at https://github.com/DF-Wiki/QualityRatings, and the issue is really only with the configuration system not recognizing the main namespace as valid. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:29, 3 January 2023 (UTC)
::::::Great, I started having a crack at fixing the template with different themes. Is the preference to get some CSS going and then include it in the global stylesheet (i.e different styles per theme) or to try and get a "one size fits all" fix? —[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 08:14, 3 January 2023 (UTC)
:::::::I would rather avoid custom site-wide CSS if we can. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:29, 4 January 2023 (UTC)
::::::::I appreciate that, I think it's the simplest solution to add a few lines to common.css though. Unless there is a way to attach CSS specifically to a template, I saw a few extensions that allowed that but I'm not sure if any are present in the wiki at the moment. Regardless there already exists a class `div.topicon` that is specifically for the quality ratings, is there an issue with expanding this class to accommodate the themes? The list of themes where the quality rating display is broken/invisible: Citizen, MinervaNeue, MonoBook. —[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 21:48, 4 January 2023 (UTC)
:::::::::What do you think of moving the template out of the topicon entirely and just placing it in a div? It would take up a (hopefully) small amount of vertical space in the article. [[User:Lethosor/Sandbox/Quality_test]] is an example. Unfortunately it isn't possible to prevent other templates from displaying above the quality this way ([https://dwarffortresswiki.org/index.php?title=User:Lethosor/Sandbox/Quality_test&oldid=283883]). So maybe we do need some custom CSS after all if we want that. I'm open to trying out whatever you propose. I'm a bit worried about future-proofing against skins we add later (particularly a mobile skin) but at least MediaWiki supports skin-specific global CSS as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:33, 5 January 2023 (UTC)
::::::::::I would rather we avoid taking any more vertical space in the article. The growing block pyramid at the top, starting with version template, is annoying. If you end up placing it inside the article space please use a slim box 100% wide that would include both.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 01:19, 5 January 2023 (UTC)
:::::::::::Agreed with you Jan, however I see that as two different tasks (ArticleVersion template changes, getting quality back on pages). I made a test adjustment to the quality and it takes up a negligable amount of extra space. See [[User:Vallode/sandbox#Page_quality]] for the example, we'd be able to completely remove "topicon" (unless it is used somewhere else?) and then potentially move on to making the ArticleVersion template into a slim version on the left-hand-side instead of a large box? Let me know what you think. --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 17:35, 5 January 2023 (UTC)

It appears some pages are redirecting recursively and never resolving correctly, like the [[https://dwarffortresswiki.org/index.php?title=Character_table&redirect=no|character table]] and [[tileset repository]] 07:35, 20 December 2022 (UTC)
: Indeed, these can be caught here: [[Special:DoubleRedirects]] --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:51, 20 December 2022 (UTC)

It might be useful to change the notice title to "release information '''for editors'''" --[[Special:Contributions/142.59.195.176|142.59.195.176]] 10:26, 20 December 2022 (UTC)
:Can do. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)
::New here, hello. Should we set a date where we remove/only show the banner for logged in users. There are (some) pages that have 4 different notices about the upgrade. [[Engraving]] is one such page, the top banner states "information for editors", we then have the "this page was migrated" banner, a version selection which warns the article might be inaccurate, and a smaller banner saying the page might need to be updated. Quite a lot of screen space, I think we can start to slowly reduce the amount of warnings this coming month? [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 10:07, 2 January 2023 (UTC)
:::Unfortunately, only showing info to logged-in users is difficult with how MediaWiki caching works. In terms of reducing warnings, there is a discussion [[Template_talk:ArticleVersion#.22Note_that_some_content_may_still_need_to_be_updated..22|here]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:43, 4 January 2023 (UTC)
:::As for [[Engraving]] specifically, the {{tl|old}} banner was actually present on [[DF2014:Engraving]] as well and got carried over with the migration. I removed it, and agree that it was redundant. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:46, 4 January 2023 (UTC)

Main talkpages seem to redirect to DF2014 talk. Not sure if it is intentional but I like it, though we should pay attention when creating new discussion relating to v50 ending up there.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 14:18, 20 December 2022 (UTC)
:That's unintentional. I specifically wrote the migration script to not move talk pages, but that has the side-effect of leaving any previously-created "Talk -> DF2014 talk" redirects intact. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)

Yo Lethosor, are we adding graphic sprites for the pages in some way? Or are we waiting for you to add some sort of new template or something? I'm sure you don't need me to tell you that the current templates don't allow that. Not sure if I'm allowed to change/create any templates either, as I don't want to break things for hundreds of pages. Edit: And IF the icons are allowed, should they be left alone, or 2×-3× sized like how the Minecraft wiki does it? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 14:29, 20 December 2022 (UTC)
:Depends on which templates you mean. There are copyright concerns with uploading a premium sprite sheet, for instance. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)
::I'm not talking about uploading an entire sprite sheet. I'm just talking about individual icons for each respective page. One image for cows, one for horses, one for werebeasts, etc. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 16:50, 20 December 2022 (UTC)
:::If we do that for every creature in the sprite sheet, that's not much different (in terms of copyright) from uploading the entire sprite sheet. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:09, 20 December 2022 (UTC)
::::Is there someone we can talk to about that? We finally get this new game with graphics, and then we can't use the very graphics of the game? No matter what the rules are, I'd say that would be the stupidest thing ever. I know I'm infamous here when it comes to copyright and images and stuff, but about 80% of game wikis out there are completely unofficial, and use game file images like no one's business. I can't imagine anyone's door being knocked on if we used the game's sprites, but I won't add any here until we have a go-ahead. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 17:14, 20 December 2022 (UTC)

:::::...I've made noise in Mayday's direction on this matter, at least (prob an incorrect maneuver, ''but'').[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 17:55, 20 December 2022 (UTC)
:::::: I hope some sort of arrangement can be made so we can use the new sprites with permission/limits, just as we are using the raw files. Otherwise we are all (devs and editors alike) shooting ourselves in the foot here.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 21:07, 20 December 2022 (UTC)

:::::::I just thought of something. We're supposedly not allowed to upload entire sprite sheets, right? What if - for the time being - we just use a few of them for the purpose of testing out new infoboxes? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 21:46, 20 December 2022 (UTC)
::::::::I don't know. If someone could ask Kitfox and post the response here, that would be great. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:47, 20 December 2022 (UTC)

:::::::::I've reached out to Alexandra, but she hasn't answered yet. Until then I found these old approvals from the previous community manager, Feeona: ([http://www.bay12forums.com/smf/index.php?topic=173474.msg8243633#msg8243633 link1], [http://www.bay12forums.com/smf/index.php?topic=176640.msg8243642#msg8243642 link2]). Waiting for a newer response until we begin mass uploads is probably the politer option, but like Zippy said, it is also standard for wikis to use game sprites with less approval. I second their idea of trying it out with a few images to test the infoboxes. On the extreme off-chance (and I do think it is) Kitfox protests we can always remove these few. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 22:19, 20 December 2022 (UTC)
:::::::::And here is a third, more official statement: ([http://www.bay12forums.com/smf/index.php?topic=173474.msg8249718#msg8249718 link3]). Perhaps that address of info@kitfoxgames.com is the better channel to ask for a confirmation, rather than Discord DMs, but I will be going to bed, so it is best if someone else does that. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 22:29, 20 December 2022 (UTC)
::::::::::Thanks for tracking this down! Ok, sprites should be fine, but let's avoid uploading the entire premium tileset as a single image, for instance (as the forum thread says, "use common sense"). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:21, 21 December 2022 (UTC)
::::::::::: Looks good, permission is always preferable over fairuse, I think it is a win win for all involved. I agree that we shouldn't upload entire sprite sheets (e.g. there is no reason to upload the windmill from every direction or whole construction phase for workshops) and that there are a lot of details that needs to be ironed out through testing. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 05:07, 21 December 2022 (UTC)
:::::::::We have a green light on uploading all and any sprites. Their response to me can be seen [https://i.imgur.com/BhmHjzC.png here]. I'm sure someone else confirmed it before me. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 19:00, 21 December 2022 (UTC)

Shifting temporarily to a new issue, is the documentation of [[Template:ArticleVersion]] outdated? It would seem so to me, since the current version no longer has its own namespace, with the templates needing updating being different ones. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 18:30, 20 December 2022 (UTC)
:I think it is still accurate enough. We left open the possibility of making another namespace in the future, albeit with a different migration strategy - see [[#v50 organization|above]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:52, 20 December 2022 (UTC)

Some Changes to infoboxes might be needed. Too bad [[User:Doorkeeper]] isn't around. He did a great work with navbox project--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:52, 21 December 2022 (UTC)

I just realized that raw files aren't stored as regular wiki pages but loaded via the DFRawFunctions extension (hence the need to update). Good news it's going to be handled in bulk, consistently and relatively easy to updated. Even better it's Lethosor problem ;) Also I just realized that all the "raw files" (txt files in the new vanilla folder) are released into the public domain. Both are probably not news to the vets but I'll leave it here for those who less up to date like myself. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:35, 22 December 2022 (UTC)

: I noticed that some templates aren't working properly in the new namespace, e.g. [[Basalt]] entry had its raw updated manually but the infobox fail to show any details. Cursory look suggest {{t|layerlookup/0}} need a minor tweak. This should do the work
:: Replace: <nowiki>{{layerlookup/aux|{{{{FULLPAGENAME}}/raw}}|uses={{{uses|}}}|wiki={{{wiki|}}}}}</nowiki>
:: With___: <nowiki>{{layerlookup/aux|{{</nowiki>:<nowiki>{{FULLPAGENAME}}/raw}}|uses={{{uses|}}}|wiki={{{wiki|}}}}}</nowiki>
: Not sure what the plan and ETA with raws update so I didn't touch this high usage template for now. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 08:11, 24 December 2022 (UTC)

::Please do feel free to make this update. I am still working on a script to create the <code>/raw</code> pages themselves. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:12, 1 January 2023 (UTC)

Wouldn't it be an idea to add to the Sitenotice to remove the {{tl|migrated article}} tag when an article has been fully updated? I see many articles that seem to be updated still have the tag. And/or advise to make use of the {{tl|verify}} for sections still in need of checking? --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 10:12, 2 January 2023 (UTC)
:Probably a good shout. The "see this page" link does include the detail on removing but we should more explicitly encourage removing the banner once a page has at least been looked over. [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 11:01, 2 January 2023 (UTC)

== v50 specific issues ==
=== Graphics===
Follow up on the use of game sprites and the need to trying it out with a few images to test the infoboxes. First sprite [[:File:Beds v50.png]] was uploaded and used on [[Bed]] entry. Any thoughts? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:06, 21 December 2022 (UTC)
:Seems like it should be rearranged to be horizontal. Also, has there been a serious discussion about copyright? Full screenshots are 100% fine, but you start going into a grey area when you upload pieces of a spritesheet. I'm of the opinion that it's all fine as long as it's inconvenient to reconstruct the full sheet from the individual images. Maybe a further restriction could be you shouldn't upload any of the art unless it's used in an infobox (maybe an exception for pieces of the UI). And one more restriction could be you shouldn't show everything, like in your bed example, maybe just the wooden bed is good enough, leave out the stone and metal, especially since those can only be made from strange moods. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:43, 21 December 2022 (UTC)
::Actually, your bed image is kinda bad for showing off what a bed looks like because it doesn't show the pillow/blankets. That might point to cropped screenshots being the best path, although less convenient for the uploader, as you don't get details left out. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:46, 21 December 2022 (UTC)
::I created a new license template [[Template:Copyright game]], based it on the way the RimWorld wiki does things. Call it a prototype, but it's probably how your bed image should be labelled. Indeed, I added it to it already. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]])

::: I agree that the horizontal arrangement would suit better here and that we should strive to represent how things look in-game. Otherwise, I am not too concerned about people being able to reconstruct anything (lets just say that ''anyone'' interested in that can get the real thing from the game files), also it seem we have permission to use the sprits on top of fairuse. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 19:55, 21 December 2022 (UTC)

::: Modifying the existing template to allow the inclusion of the new sprites is easy (Something like [https://ibb.co/zFXCrjd this]?) The big question is the matter of consistency is there any exceptions that will break the format (size wise with variant bloat for example), the sprite naming format, etc --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:44, 21 December 2022 (UTC)
::: If we are going to show a variant for each material type, then maybe these should be added as separate images so we can add a tooltip for each image. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:49, 21 December 2022 (UTC)

:I've got another prototype going here and here: [[User:Brightgalrs/vector.css]] and [[User:Brightgalrs/Sandbox]]. (You'll need to add the css stuff to your own /vector.css). Basically it's a way to recolor images using css classes. No idea if there's a better way. Also, the real implementation would require a change to [[MediaWiki:Common.css]]. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 22:41, 21 December 2022 (UTC)
:Should mention, there ''is'' a different way, just upload each image 16 times, one for each coloring. But maybe that's not very elegant. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 22:45, 21 December 2022 (UTC)

: It should be noted that soon the classic edition will be released, hence one should plan to have both the Premium and classic alongside in that little space --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 03:14, 22 December 2022 (UTC)
::I'm looking into a tab extension to potentially support this in infoboxes. Perhaps [https://www.mediawiki.org/wiki/Extension:Tabs Extension:Tabs]? I tried [https://www.mediawiki.org/wiki/Extension:TabberNeue Extension:TabberNeue], but it displays a placeholder if JavaScript is disabled, which isn't great. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:22, 22 December 2022 (UTC)
::: The Neue Tabber seem to works pretty much like the old one (which fandom [https://coding-help.fandom.com/wiki/Tabber#Adding_images_into_tabbers still use]) defaulting to showing the first tab only. Quick look suggest that neue work the same, plus the notice that 'Tabber requires Javascript to function' warning? if so, and if it is a bother, then you should be able to edit out the tabberneue-noscript string in code. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 06:29, 22 December 2022 (UTC)
::: I much prefer your tabber solution, but if that fails we can also use the gallery slideshow mode. If so, beware it has no way to control image size so the images have to be maliciously uploaded using the exact same size. example:
<gallery mode="slideshow">
File:SteelSample.png
File:TinSample.png
File:ZincSample.png
File:GoldSample.png
</gallery> --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 10:19, 22 December 2022 (UTC)

==== adding premium set to Infobox ====
I am unclear where are we going with this? 
1) Will (A) tabs be implemented, (B) we be using mediawiki toggle [[Template_talk:V50_workshop|example]] for premium and classic/blocked, (c) put images side by side, or (d) something else? 
2) Also [[silver]] and [[Pig iron]] use very different image style for example. 
3) Anything else you want ? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 12:32, 30 December 2022 (UTC)

: Personally, I would love tabs to be implemented, but I think that side by side might be best for most. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 12:32, 30 December 2022 (UTC)
: Here is rough layout we can use. It should fit most buildings given the default sprite size. There is also a different floor plan for both (inspired by reddit)

{|
|- valign=top
|
{| style="width:200px; background-color:#eaecf0; border-collapse: collapse; "
|+ 5×5
|- style="border-bottom:2px solid #3366cc; "
|<div class="mw-customtoggle-infoboxtab mw-ui-button mw-ui-progressive" style="border-top-right-radius: 10px; border-top-left-radius:10px;">toggle</div>
|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|- valign=top
|colspan=2|<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">
[[File:Siege workshop.png|center|160px]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab"">
{|
|rowspan=2 style="width:50%; font-size: 125%;"|<center>{{Template:Picture Siege workshop}}</center>
|style="line-height: 1em; font-size: 125%;"|
{| style="border-spacing:4px;"
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|}
|
{| style="width:200px; background-color:#eaecf0; border-collapse: collapse; "
|+ 3×3
|- style="border-bottom:2px solid #3366cc; "
|colspan=2 style="text-align: right;"|<div class="mw-customtoggle-infoboxtab mw-ui-button mw-ui-progressive" style="float:left; border-top-right-radius: 10px; border-top-left-radius:10px;">toggle</div>{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|- valign=top
|rowspan=2 style="width:50%;"|
<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">[[File:Carpenter's workshop.png]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab""><center>
{| style="font-size: 175%; border-spacing: 0; background-color: black; border: 2px solid black"
|- 
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"| {{Raw Tile|"|7:0:0}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|{{=}}|6:0:0}}
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"|
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|]|0:0:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
|}</center></div>
|
{| style="border-spacing:5px;"
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|
{| style="width:200px; height:100px; padding:10px; background-color:#eaecf0; border-collapse: collapse;"
|+ 1×1
|- style="border-bottom:2px solid #3366cc;"
| colspan=3 style="text-align:center;"|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|-
| style="border-right: 1px dotted #545557;"|[[File:Screw_press.png|32px|center|link=]]
| style="font-size:125%;"|<center>{{Template:Picture Screw press}}</center>
| style="border-left: 1px dotted #545557;"|<center>{{Template:Floor Plan Screw press}}</center>
|}
|
{| style="width:200px; height:100px; padding:10px; background-color:#eaecf0; border-collapse: collapse;"
|+ 1×3
|- style="border-bottom:2px solid #3366cc;"
| colspan=3 style="text-align:center;"|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|-
| style="border-right: 1px dotted #545557;"|[[File:water_wheel.png|32px|center|link=]]
| style="font-size:125%;"|<center>{{Template:Picture Water wheel}}</center>
| style="border-left: 1px dotted #545557;line-height:normal;"|<center>{{Template:Floor Plan Water wheel}}</center>
|}
|}
:Any thoughts on the direction and or any and all of its elements? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 10:16, 31 December 2022 (UTC)

::I kind of like side-by-side, if it fits. If anyone wants to implement a toggle button or tabs, I would ask that that be implemented in a template for now, so that e.g. we could change a toggle button to tabs in a single place if we decide to install an extension to support that. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:14, 1 January 2023 (UTC)

::: I noticed a comment saying that [[impassable tile]] are no longer used in v50, is that true for all constructions? If so, floor plans are no longer needed, making things much easier as we can fit everything in except the 5v5 constructions like trade depot (and even these can be placed one above the other if so desired). If not, any thought on the alternative floor plan design? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:46, 1 January 2023 (UTC)

:::: None of the constructions have blocking tiles any more from my experience playing. I haven't tested siege weaponry with that stuff, but none of the workshops have it, nor does any furniture. (walls and fortifications will of course obstruct movement [[User:AndrielChaoti|AndrielChaoti]] ([[User talk:AndrielChaoti|talk]]) 18:47, 1 January 2023 (UTC)
::::: Ok, I have removed them from v50. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 23:48, 1 January 2023 (UTC)

I have added a basic side by side variant to [[Template:V50 workshop]] and [[Template:Building]] for testing, let us know if there any issues. Few notes:
* The default image naming scheme of <code>workshop-name.png</code> will likely conflict with existing images here or on commons, maybe another naming scheme should be used like <code>v50 workshop-name.png</code> as it is with ascii pictures.
* There is inconsistency in image size. If you want to use large zoomed images then toggle is best, otherwise they need to be all in native size (96px for 3x3).
* In the current version the code roughly centers the images and if there is a big image like with [[Siege workshop]] it drops to a new line --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 23:48, 1 January 2023 (UTC)

How about combining shortcut keys and the new menu icons:
<div style="color:white; font-size: large; text-shadow: -1px -1px 0 #000, 1px -1px 0 #000, -1px 1px 0 #000, 1px 1px 0 #000;">[[File:Ui b.png]]<div style="position: absolute; bottom:-14px; right:3px;">b</div>[[File:Ui bo.png]]<div style="position: absolute; bottom:-14px; right:3px;">o</div>[[File:Ui bol.png]]<div style="position: absolute; bottom:-14px; right:3px;">l</div>[[File:Ui boll.png]]<div style="position: absolute; bottom:-14px; right:3px;">l</div></div>
--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 02:24, 3 January 2023 (UTC)

:I worry that this is difficult to read (I read it as "boil" at first). I would rather use something like {{tl|k}} with a known background. What about something like this? [[File:Ui boll.png]]<div style="position: absolute; bottom:-14px; right:0px;">{{k|l}}</div> or, alternatively, using flexbox without any overlap: [[File:Ui boll.png]]{{k|l}} —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:37, 3 January 2023 (UTC)
:: Same, but that is the best I came up with. We can use the key or maybe someone can help improve the design. Also 'l' is hard to read even with {{t|key}}.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 03:05, 3 January 2023 (UTC)
:: I added a {{t|Menu icon}} to start things so others can have a go with it. Also any thoughts on the icon naming convention (their shortcut sequence), is there easier/better way? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 09:36, 3 January 2023 (UTC)
::[[User:BarelyCreative]] updated the template: {{Menu icon|b|o|l|y}}. I think it looks good, thoughts? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:40, 3 January 2023 (UTC)
:::I like that, yeah. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:29, 4 January 2023 (UTC)
::::There were some places where it didn't make sense so display every icon all the time (like step-by-step guides), so I changed it slightly to allow display of fewer icons using "num" and counting from the end: <nowiki>{{Menu icon|b|o|l|y|sep=-;|num=2}}</nowiki> {{Menu icon|b|o|l|y|sep=-|num=2}} [[User:BarelyCreative|BarelyCreative]] ([[User talk:BarelyCreative|talk]]) 09:05, 4 January 2023 (UTC)

==== Bizarre palette-swapping idea/prototype ====
No idea if this is a good idea, since it takes a bit of time to set up, and there might be some performance issues... and maybe display issues?

But take a look at this:
{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock|palette-name=amber}}

It's way to swap palettes on an image, although the image itself is a table, with each cell representing a pixel. The template itself looks like this:
<code><nowiki>{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock|palette-name=saffron}}</nowiki></code>
Input the pattern and desired palette name.

I've got a larger showcase here: [[User:Brightgalrs/Sandbox/PaletteSwapShowcase]]. Only did a rock pattern so far, but all palettes are implemented.
The major use for this would be on each stone, metal, wood, etc. type's page. The palette could be read directly from the raws. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 03:22, 24 December 2022 (UTC)

:From a technical perspective, my primary concern is indeed performance. Both on the server side and client side, a large number of tables that large (in terms of markup and cell count, that is) tend to be resource-intensive to generate and render. I saw your image-filtering experiments on [[User:Brightgalrs/vector.css]], and while that strikes me as a newer and less-backwards-compatible approach, it would probably be more resource-friendly.
:Is this color adjustment something the game is doing natively? i.e. does this accurately match what the game displays? I bet we could slap together an image-filtering extension (or find an existing one?) that can do this if needed. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:49, 24 December 2022 (UTC)
::Yeah that's what I suspected. The images the template creates are spot on, checked it against a screenshot I took of some mica rocks in-game. The css stuff is unfortunately totally incorrect, was cool to learn about it though, so not a complete waste of my time :p. The premium, in-game graphics are true sprites, basically patterns of indexed colors. Each of the in-game colors (which are significantly expanded over the 16 ascii colors, there's 116/117) there is a palette defined in "\Dwarf Fortress\data\vanilla\vanilla_descriptors_graphics\graphics\images\palettes.png". Each indexed color of the sprite is swapped for the corresponding color in the palette. Because of that, the css stuff doesn't work since it's doing the hue/saturation/brightness changes to the entire sprite.
::I've looked into an existing mediawiki extension, couldn't find anything. One thing I did't really look at is some type of lua script/module that would basically emulate what the game is doing. So some function that takes in the base image as well as the desired palette, and based on that finds and replaces each color. No idea what mediawiki's capabilities are on that front. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 05:31, 24 December 2022 (UTC)
:::We do have Scribunto installed now, so it's totally possible to do something in Lua too - forgot about that. I can add you to the group that grants access to edit the Module namespace if you want to give that a shot. If we use an extension, we'd probably need a custom one, similar to DFDiagram (or perhaps DFDiagram could be extended - it's in dire need of a rewrite anyway). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:43, 24 December 2022 (UTC)
::::I asked around on the mediawiki irc, I think scribunto/lua is a deadend, at least for taking an uploaded image and doing stuff to it with a lua script. However I did come up with this even more bizarre solution, using block elements. [[User:Brightgalrs/Sandbox/PaletteSwapShowcase2]], maybe less resource intensive? Definitely displays a lot worse though, probably unusable.
::::{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock2|palette-name=saffron}}
::::I dunno, maybe none of this is worth it and we should just write some external program to put all the images together offline, and then just mass upload. It wouldn't be ''that'' many... [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 06:37, 24 December 2022 (UTC)

====Is there an easy way to just paste images from the clipboard?====

I use KDE spectacle to take screenshots straight to the clipboard (after cropping) -- is there an easy way to just paste (and auto-upload) an image into an article? It would make it a lot easier to contribute images. [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 23:35, 1 January 2023 (UTC)
:Unfortunately there is not. I would be open to a MediaWiki extension to support this if someone finds one. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:32, 2 January 2023 (UTC)
:: Looks like this could do it, but I haven't used it before: https://www.mediawiki.org/wiki/Extension:SimpleBatchUpload [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 19:41, 2 January 2023 (UTC)
::: It won't solve paste-from-clipboard, but this would be great for making uploading sprites much easier (auto-cutup spritesheet, rename, bulk upload). Could you add this, Lethosor? [[User:OddballJoe|OddballJoe]] ([[User talk:OddballJoe|talk]]) 21:47, 6 January 2023 (UTC)

====Standards for adding graphical version screenshots and images====

Hello, new user looking into adding imagery from the new version. Is there a standard for quality of new screenshots or images? I noticed that at a certain zoom level (2 zooms in from the furthest zoomed-out view), the graphics appear crisp and 1:1 pixel scaled, and I would propose that all images be taken at this scale whenever possible. If they need to be displayed larger, they should be nearest neighbor scaled in a photo editing program at 100% increments (Microsoft Paint will do this if you first select the image rather than directly scaling the whole canvas). I would also propose that images should be cropped to conform to the 32x32 pixel grid when possible, though this could be problematic with so many new graphical elements exceeding the bounds of their tiles. I would say the best practice for capturing artwork for items, furniture etc. ought to be done in a 3x3 open area to avoid shadows from nearby walls, or else extracted from the raw files (if this doesn't run afoul of being able to re-create the graphical version using those assets).

I know that perfect is the enemy of good, and any documentation is better than none, but just thought I'd ask about this, and see if/where something like this ought to be posted. [[User:Unclesporky|Unclesporky]] ([[User talk:Unclesporky|talk]]) 13:58, 3 January 2023 (UTC)
:It has been stated in [[Template:V50 workshop]] that <q>screenshots should be at the "native" resolution</q> but someone could edit the [[Screenshot]] page for best practice for the steam version. Or post some examples in [[Talk:Screenshot]] to find out what is best? --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 14:21, 3 January 2023 (UTC)

====How would I/should I go about putting creature sprites on their pages?====

Howdy. New player and wiki user here. I wanted to try and help update the wiki to the Steam release of DF, so I figured I'd chip in by putting each creature's sprites on their respective page, since I'll often look up a creature I have yet to see in game only to be met by a blue J, or whatever. I found all of the game's creature sprites in C:\Program Files (x86)\Steam\steamapps\common\Dwarf Fortress\data\vanilla\vanilla_creatures_graphics\graphics\images, so I figured I could just chop those up in Photoshop and stick them on here no problem, but the programming syntax/whatever it is on this site is incredibly confusing, I don't know how I'd actually go about doing it. I figured I'd just find the spot on the page where the little letter is and replace that with the image code, but it seems the pages are built using heavily nested templates that I can't even begin to understand. Any help?--[[User:Treese|Treese]] ([[User talk:Treese|talk]]) 03:07, 5 January 2023 (UTC)
:Based on [[User:Zippy|Zippy]]'s work at {{tl|Creaturelookup_b}}, I added an "image" parameter to {{tl|creaturelookup/0}}, which is what creature pages should all be using. See [[Dwarf]] and [[Cow]] for examples. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:37, 5 January 2023 (UTC)

=== Hotkeys/Menu navigation ===
Most key bindings and menus have changed. Should the article reflect a) only the old version, b) only the GUI version or c) both? For example, [[Bridge|bridges]] used to be built via {{k|b}} -> {{k|g}}, but now it's in Place strucutures {{k|b}} -> Constructions {{k|n}} -> Bridge {{k|b}}. What should be written in the article? Currently, it's {{k|b}} -> {{k|g}}. I ''think'' it should be only b), but I am not sure if there will be differences regarding hotkeys or menus between the premium version and the free version and then, c) would be the most appropriate option. --[[User:Prometherus|Prometherus]] ([[User talk:Prometherus|talk]]) 10:16, 22 December 2022 (UTC)

: Not sure. I wish the classic release soon --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 16:45, 22 December 2022 (UTC)
:: Are you Toady's herald? Looks like it was just released! [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:18, 22 December 2022 (UTC)
:: And our questions are answered, the old hotkeys seem to have been thrown out. Part of me is disappointed (useless muscle memory) but also relieved (unified UI for both versions is good in general and for the wiki). [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:25, 22 December 2022 (UTC)
::: According to info, in a sort of 'demo version' at that. I'll wait a little while longer, for myself.[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 18:22, 22 December 2022 (UTC)
::::It's unlikely that keybindings in it will change significantly. My vote is that we should include information for both premium and classic, everywhere. Hopefully the keybindings are not different between versions. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 18:26, 22 December 2022 (UTC)
:::Shouldn't it be based on the 50 or what verion the article is written for? [[User:Dominick|Dominick]] [[User_talk:dominick|(TALK)]] 18:42, 22 December 2022 (UTC)
:::: The keybindings seem to be consistent between versions, (haven't checked exhausitvely, but since the menu layout is the same I think it is a good assumption). Should also keep in mind/consider that not all actions have keybindings. An option would be write 'Click on the <Example Text> icon or press {{k|E}}' [[User:Koos|Koos]] ([[User talk:Koos|talk]]) 23:14, 23 December 2022 (UTC)

=== Removed features & concepts ===

Since they're removed concepts, I've set [[Room]] to be a redirect for [[DF2014:Room]] and created [[Template:Activity zones]] for the nav bar bedrooms, etc, and made the necessary changes to [[Bedroom]] for it. Is this the correct approach, before I go on much further? (also a note, if it is, then [[Template:v50_rooms]] probably needs to be deleted) I also imagine that considering the number of changes in the interface, that things like [[Adventure mode]] and related pages might best be truncated to "not in 50.03" and when it does make it across, being more deliberately brought over in pieces? [[User:HawkOwl|HawkOwl]] ([[User talk:HawkOwl|talk]]) 06:23, 23 December 2022 (UTC)

:Usually it is marked with [[Template:Removed_feature]]. For example: [[Dipscript]] or [[Party]]. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:45, 23 December 2022 (UTC)

:: Ah, that's fair. Should that be mentioned in [[Dwarf_Fortress_Wiki:Versions#Redirects]]? [[User:HawkOwl|HawkOwl]] ([[User talk:HawkOwl|talk]]) 10:03, 23 December 2022 (UTC)

:::I think the redirect policy mostly had in mind things that were removed a ''long'' time ago, like [[Tax collector]] and [[Economy]] (and the latter actually has a stub page as well). I guess we could clarify. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:34, 23 December 2022 (UTC)

:::: The "current" redirects also cause the version box to incorrectly show that the current version has a page - e.g. [[23a:Cave_river]] shows a v50.04 version, but it's just a redirect back to that version. Similarly, what should happen to redirects like [[Clothes maker]], where a concept has evolved? It currently goes to [[23a:Clothes maker]] - that's correct if the user is trying to look up a very old concept, but if a new user is looking for "how to make clothes", they should be directed to [[Clothier]]. --[[User:Danny252|Danny252]] ([[User talk:Danny252|talk]]) 12:16, 26 December 2022 (UTC)

:::: One should be careful with cv redirects. Most that were recently adjusted were unused plural forms (that should probably be deleted) but few like [[Crown]] needed that for backward compatibility. Removing the [https://dwarffortresswiki.org/index.php?title=Crown&type=revision&diff=279966&oldid=219482 cv part] means the the link on [[v0.31:Tilesets]] is now broken. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 22:30, 26 December 2022 (UTC)

:::::If [[v0.31:Tilesets]] is about v0.31, it should not be using "main:" in its links - ''all'' of those links are going to pages about v50, not v0.31, regardless of whether the target is a redirect or not. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:37, 26 December 2022 (UTC)
:::::: You right, I removed it. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 17:55, 27 December 2022 (UTC)

Crown cv redir issue is now fixed, I believe. As goes with such cases where one can simply revert the troublesome edit, unless I've mistepped, myself? [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 23:52, 26 December 2022 (UTC)
:Both [https://dwarffortresswiki.org/index.php?title=Crown&diff=prev&oldid=280026] and [https://dwarffortresswiki.org/index.php?title=Crown&diff=prev&oldid=279966] should not have had any effect, because "cv" is an alias to the main namespace now, just like "main". Proof: [[Crown]], [[cv:Crown]], [[main:Crown]]. It's possible caching is coming into play here, although I purged the redirect cache after making that alias change earlier this month... —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:02, 27 December 2022 (UTC)

I think there have been some changes not captured, but as a newb, I'm afraid to edit the page(s). A good example is Strawberry. I'm playing the Steam version right now and Strawberry plants are "not relevant to brewing" in Labor > kitchen > veg / fruit / leaves. Unless I'm mistaken and need to process them? Another example is the trade caravan = it seems the 3 square pathing no longer happens; it's just yak(s). 12:31, 28 December 2022 (UTC) 12:29, 28 December 2022 (UTC)
:Strawberries should be brewable according to the Raws.
:Trade wagons has been modified in v50. The first wagons will arrive at the same time your fort is becoming a barony. Until then, it's only pack animals and stairs are indeed fine. The [[Trading]] page needs a huge rework anyway... I'll try to do that next week. --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 13:40, 2 January 2023 (UTC)

<s>As far as I can tell, none of the workshop buildings in v50 have blocking tiles any more. There's a comment to the like in data/vanilla/vanilla_buildings/objects/building_custom.txt that says this "[BLOCK:1:0:0:0] workbenches no longer block". Hesitant to update that template as I'm not sure if it's referenced for all of the old versions too. </s> [[User:AndrielChaoti|AndrielChaoti]] ([[User talk:AndrielChaoti|talk]]) 05:54, 29 December 2022 (UTC)
: A new template has been created: {{tl|V50 workshop}} --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 13:40, 2 January 2023 (UTC)
::Thanks! In general, I would like to delegate the switching responsibility to the template (like how {{tl|creaturelookup/0}} works), but in cases where the parameters diverge significantly like with workshops, it could make sense to make an entirely new template. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:40, 3 January 2023 (UTC)

=== creature infobox prototype (moved) ===

Check it out, I made a temporary template and added it to the [[cow]]s page. Now it shows the sprites (but not the zombified versions yet). I wanted to show everyone a prototype of what v50 creature infoboxes should look like. Or at least something similar to it. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 19:11, 27 December 2022 (UTC)
:Hi, I'm new to editing wikis but I have done a bit of work with sprite sheets and I've been going through the DF data files to find the different graphics hoping to help with the animal pages. I've thrown together a template with grass and a few nature sprites (plants, a tree, and a rock) for size reference but I'm unsure how large the 'display' tiles in the middle of the template should be to suit all animals. I can see in the sprite sheets that some land animals have an adult and child sprite, so two tiles. Others have a male, female, and child, but after seeing you include the zombie cows I'm unsure if I should make it twice the size to add them too. Alternatively, I could grab some tiles from the haunted biomes for the zombie animals and make a separate template for a side-by-side comparison. Either way, let me know if this helps. I'd like to help with other graphics too as we add the premium tilesets but the animals seemed the easiest to tackle with me being new to wiki editing. ~~[[User:UristTheSeventh|UristTheSeventh]] ([[User talk:UristTheSeventh|talk]])
::@Zippy, I am a bit perplexed about the purple cows. Why do we need a zombified version of creatures on every page?
::@UristTheSeventh, we can use all the help. Maybe post an example, so that we can have something to compare and contrast.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 11:49, 3 January 2023 (UTC)
:::@Jan Here are the examples:
:::[[File:Creature template.png]] [[File:Armadillo.png]] [[File:Seagull.png]]
:::It'll need to be wider or arranged differently for different creatures with more that two sprites or for multi-tile creatures. I can also do an aquatic and air themed template for swimming and flying creatures. ~~[[User:UristTheSeventh|UristTheSeventh]] ([[User talk:UristTheSeventh|talk]])
::::Looks nice, like the metal template. There are several people working on updating the graphics you should talk more among yourselves. Best I can offer is that I width wise I am hoping to go up to 200px for infoboxes.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 01:13, 5 January 2023 (UTC)
:::: We don't exactly ''need'' a zombie sprite on each page. I added it because it was... there. I was also hoping to get some opinions on it anyway since that infobox is a visual prototype, and not a final choice. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 03:28, 6 January 2023 (UTC)

===Furniture Infobox===
{{Quality|Unrated}}
{{v50_furniture|name=Bed
|graphic=[[File:bed_sprite_prototype.png]]
|tile=Θ|col=6:0:0
|wood=y
|rooms=
* [[Bedroom]]
* [[Barracks]]
* [[Dormitory]]
|value=10}}
I made a v50 furniture template prototype. I tested this on Firefox, Chrome and Microsoft Edge/Internet Explorer and it looks fine on all of them. I hope this is good enough to be the official thing, unless I'm missing something. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 03:28, 6 January 2023 (UTC)
{{clear}}

=== When do we remove the migration note on specific pages? ===

At what point can we remove the "this page was auto migrated from v47" warning? There are a bunch of small pages that are more or less accurate, if I've reviewed them, can I go ahead and remove the warning? [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 23:33, 1 January 2023 (UTC)
:Yes, feel free to remove it if you think all content is accurate. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:31, 2 January 2023 (UTC)

=== Any info on fixing "creature description not found?" ===

I see this issue on most creature pages, it seems to be due to a lookup that's not currently functioning? Cows interestingly doesn't have this issue but I couldn't figure out how to recreate whatever fix it's editor did. --[[User:Yallendallis|Yallendallis]] ([[User talk:Yallendallis|talk]]) 00:22, 3 January 2023 (UTC)
:That is the missing raws issue described above. Cow was fixed by the addition of [[cow/raw]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:28, 3 January 2023 (UTC)
::Ah makes sense, not fully used to the language of wikis yet so I read over it while looking. To put this bit of questioning to rest for any future readers, is it correct that it's fine to update any raws manually, though it will be done automatically at some point? --[[User:Yallendallis|Yallendallis]] ([[User talk:Yallendallis|talk]]) 07:48, 3 January 2023 (UTC)
:::Yes. I'm circling back to work on a script right now, so not much point in doing it if you're reading this. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:57, 4 January 2023 (UTC)
:::This should be fixed now. If you continue to see pages with problems, you can try [https://www.mediawiki.org/wiki/Manual:Purge purging the cache]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:59, 4 January 2023 (UTC)

=== Adventurer Mode related sections ===

The topic has already been discussed [[#Removed features & concepts|above]], but I don't see a clear line on what to do with article sections that mention Adventurer Mode. Like for example in [[Butcher#Adventurer_mode|Butcher]].

'''a) Truncate''' or '''b) leave in place with a mention''' that the mode is not yet present IG but will be added in a future update?

Personally I think option b) is better, because I think it's silly to undo some work just to reintroduce it a few weeks later, with the necessary corrections. Even if a copy/paste of a previous version takes ~15 seconds, considering the number of articles that need to be corrected, it would be a bit of a waste of time.--[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 14:22, 3 January 2023 (UTC)

== Toggleable image ==

Any objections/comments to using this template for now for toggling between classic and premium images? I'd probably rename it to "Template:Premium-classic thumb image". I'm sure someone can come up with a better UI eventually, but should be easy to migrate at that point. I also think we should use the same customtoggle class for this and for the infobox. [[User:NiftyManiac|NiftyManiac]] ([[User talk:NiftyManiac|talk]]) 23:12, 1 January 2023 (UTC)

{{User:NiftyManiac/Sandbox/TemplateDualImage|
premium=File:Quickstart-finder.png|
classic=File:Quickstart-finder-partial.png
}}

{{User:NiftyManiac/Sandbox/TemplateDualImage|
premium=File:Quickstart-finder.png|
classic=File:Quickstart-finder-partial.png|
caption=My caption|
width=100px
}}

:This looks nice to me! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:30, 2 January 2023 (UTC)

: Good initiative. From the top of my head:
:* I suggest using a shorthand, no one wants to type 'Premium-classic thumb image'.
:* If we end up using toggle for infoboxes (not sure where we headed there), then I agree definitely same custom toggle class should be used for all, thus allowing to switch premium-classic view on the whole page at a click.
:* The button part on a separate row isn't pretty, creating a lot of dead space that can be used by the text. Are we set on the label 'toggle ascii'? Classic isn't Ascii per se, maybe we can use a 'toggle' with a tooltip {{tooltip|for example|does bla bla bla}}, or maybe we can get rid of the text and have a smaller icon button ([[User:Jan/sandbox#Metal_example|two examples]]).
: I hope that helps. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 11:21, 2 January 2023 (UTC)

:: I added [[Template:Dual image]] with some of your suggestions. Agree that it's not super pretty, feel free to try something different.

::* I put the toggle in the caption mostly because I gave up on trying to make a more sophisticated replacement for the default thumb image behavior, I'm sure someone with better wiki-fu could put together something more intelligent.
::* I cut the text down to just "Toggle"; I think the best solution would be a small graphic showing the old and new dwarf icons with arrows between them. [[User:NiftyManiac|NiftyManiac]] ([[User talk:NiftyManiac|talk]]) 19:21, 2 January 2023 (UTC)

{{Dual image|
premium=File:DFwiki5by53by3farm.png|
classic=File:Quickstart_layout_3.png|
width=100px|
caption=A 5x5 room with a 3x3 farm plot
}}
::: I updated the layout, now it should look just like a regular image thumb. I didn't had time to test it, if it doesn't work for you or you don't like it just revert the last change. cheers. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 21:46, 2 January 2023 (UTC)
::::I don't know which part of this talk page to put this, but I added the ability to add icons to the v50 workshops template. Leaving the icon part blank will not break the template in any way. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 09:47, 3 January 2023 (UTC)
{{clear}}
==Creature List Now Supports Graphics!==
I wasn't easy, but I made new templates so the [[Creature]]s page now supports both graphics sprites ''and'' ASCII tiles. Allow me to show you:

{{v50_creaturecurrent_table_head}}
{{v50_creaturecurrent table row|graphic=[[File:dwarf_sprite.png]]|name=[[Dwarf]]|symbol=☺|color=3:0:0|playable=Fort, Adv|hostile=No|food=No|size=60,000|value=Not tameable|biome=[[Mountain halls]], [[Fortress|dwarf fortress]]es, [[hillock]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:elf_sprite.png]]|name=[[Elf]]|symbol=e|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=60,000|value=Not tameable|biome=[[Forest retreat]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:human_sprite.png]]|name=[[Human]]|symbol=U|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=70,000|value=Not tameable|biome=[[Town]]s and cities|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:goblin_sprite.png]]|name=[[Goblin]]|symbol=g|color=7:0:0|playable=Adv|hostile=Usually1|food=No|size=60,000|value=Not tameable|biome=[[Dark fortress]]es and [[dark pit]]s|note=Snatchers2}}
{{v50_creaturecurrent table row|graphic=[[File:kobold_sprite.png]]|name=[[Kobold]]|symbol=k|color=6:0:0|playable=Adv|hostile=Usually1|food=No|size=20,000|value=Not tameable|biome=Caves|note=Skulking race}}
|}

Oh wait, there's a bonus. You can also modify the background color of the box the sprites go in. I added that to make possibly-hard-to-see-otherwise sprites more easy to see - depending on the colors it has. Allow me to demonstrate.

{{v50_creaturecurrent_table_head}}
{{v50_creaturecurrent table row|graphic=[[File:dwarf_sprite.png]]|bgcolor=#829ccc|name=[[Dwarf]]|symbol=☺|color=3:0:0|playable=Fort, Adv|hostile=No|food=No|size=60,000|value=Not tameable|biome=[[Mountain halls]], [[Fortress|dwarf fortress]]es, [[hillock]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:elf_sprite.png]]|bgcolor=#c7dfc0|name=[[Elf]]|symbol=e|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=60,000|value=Not tameable|biome=[[Forest retreat]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:human_sprite.png]]|bgcolor=#c7dfc0|name=[[Human]]|symbol=U|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=70,000|value=Not tameable|biome=[[Town]]s and cities|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:goblin_sprite.png]]|bgcolor=#dfc0c0|name=[[Goblin]]|symbol=g|color=7:0:0|playable=Adv|hostile=Usually1|food=No|size=60,000|value=Not tameable|biome=[[Dark fortress]]es and [[dark pit]]s|note=Snatchers2}}
{{v50_creaturecurrent table row|graphic=[[File:kobold_sprite.png]]|bgcolor=#dfc0c0|name=[[Kobold]]|symbol=k|color=6:0:0|playable=Adv|hostile=Usually1|food=No|size=20,000|value=Not tameable|biome=Caves|note=Skulking race}}
|}

To change the background color, add <code><nowiki>|bgcolor=COLOR</nowiki></code> segment after the <code><nowiki>|graphic</nowiki></code> part. You can use color names or HTML hex color codes. I added this to the v50 creatures page, but at this time, I only added the first five creatures I just displayed. It's gonna take a while to find ALL of those creature sprites. I hope a lot of people help out on that one. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 05:29, 5 January 2023 (UTC)

:Thanks, looks nice! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:44, 5 January 2023 (UTC)
:Nice stuff, took the quick liberty to change the padding-left -> text-align to make all the sprites center aligned relative to each other :) Sweet work --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 17:41, 5 January 2023 (UTC)
:: Good work indeed. One minor issue, is that all the sprites have different sizes, which sometimes create slight variation in table row height. Consider using capping the image size vertically for example <code><nowiki>[[File:dwarf_sprite.png|x32px]]</nowiki></code>--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:15, 5 January 2023 (UTC)
:: Also often in such tables people want to click on the image to go for the specific entry, and often will try to click on the very first thing they see in line the thumb image, but currently that will take them to the file page. Consider adding link parameter for example: <code><nowiki>[[File:dwarf_sprite.png|x32px|link=dwarf]]</nowiki></code> [[File:dwarf_sprite.png|x32px|link=dwarf]] or no link at all <code><nowiki>[[File:dwarf_sprite.png|x32px|link=]]</nowiki></code> [[File:dwarf_sprite.png|x32px|link=]] --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:24, 5 January 2023 (UTC)
::: I mean... Yeah, I could do that. I think that lessens the quality of the sprite a bit because it makes edges blurry, but either way is fine. I could have sworn I added a link for all those images the first time. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 03:23, 6 January 2023 (UTC)
::::Since we are adding pixel art sprites to the website it might be convincing to add a global class like .sprite or .pixel-image that uses the CSS attribute `image-rendering: pixelated;` in order to prevent blurryness when scaling the image up/down. Just a thought --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 09:40, 6 January 2023 (UTC)
:::::Are we able to attach classes directly to images? If so, we can probably attach inline styles directly as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:52, 6 January 2023 (UTC)
::::::Looks like (without an extension) MediaWiki only supports classes on images: [[File:dwarf_sprite.png|x32px|class=pixelated]] and not styles: [[File:dwarf_sprite.png|x32px|style="image-rendering: pixelated;"]] it just treats it as alt text it looks like? Wrapping it in a div works and demonstrates the difference: <div style="image-rendering: pixelated;display:inline;">[[File:dwarf_sprite.png|64px]]</div> [[File:dwarf_sprite.png|64px|inline]]. Speaking from experience, however, image-rendering needs a browser specific prefix in certain browsers (safari, for example) in order to work properly. I'm not entirely sure what the best "MediaWiki" practice is for adding something like this but I would assume it's a simple class in common.css for now. --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 17:17, 6 January 2023 (UTC)
:::::::Ah, yeah, you are correct, I should have checked https://www.mediawiki.org/wiki/Help:Images. I'd be fine adding a class like that to common.css. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:27, 6 January 2023 (UTC)
::::::::Great, in that case if no one is opposed we can add `.game-sprite` or something like that? See below for the CSS, the order of the attributes is relevant. --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 18:23, 6 January 2023 (UTC)
<pre>/* Used for pixel-art images from the game so they can be resized and maintain crisp pixel edges. */
.game-sprite {
image-rendering: -webkit-optimize-contrast;
image-rendering: crisp-edges;
image-rendering: pixelated;
}</pre>
:::::::::So... you guys think each creature page should show the main sprite(s) alone, or should it show the baby versions alongside them? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 08:37, 8 January 2023 (UTC)
{{clear}}
=== Graphics in Skill Infoboxes ===
{{v50_skill
| color = 7:0
| graphic = [[File:miner_sprite_icon.png]]
| skill = Miner
| profession = Miner
| job name = [[Mining]]
| tasks =
* [[Dig]]
| attributes =
* Strength
* Toughness
* Endurance
* Willpower
* Spatial Sense
* Kinesthetic Sense}}I've made yet another visual prototype for skills. In other words, we can put sprites of matching dwarves (and possibly humans, elves, goblins, etc.) at the top of infoboxes. If multiple images are put up there, that can mess up the alignment, but don't worry, Zippy thought of that. <code><nowiki>|graphicmargin</nowiki></code> can added, and a percentage or a "px" number can be placed in that parameter to fix it. If you leave said parameter out, the alignment will default to about 42% from the left. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 06:06, 7 January 2023 (UTC)
<pre><nowiki>
{{v50_skill
| color = 7:0
| graphic = [[File:miner_sprite_icon.png]]
| graphicmargin = (OPTIONAL)
| skill = Miner
| profession = Miner
| job name = [[Mining]]
| tasks =
* [[Dig]]
| attributes =
* Strength
* Toughness
* Endurance
* Willpower
* Spatial Sense
* Kinesthetic Sense}}
</nowiki></pre>
::Not sure I understand the alignment issue, can you not put text-align: center on the parent table element instead of messing with explicit margins? As another sidenote, should we continue to be naming all of these templates v50_x, I find that a bit confusing. Why not just edit the main templates with the additional information. Loving all the new templates though nice work Zippy :) --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 11:43, 7 January 2023 (UTC)
:::No, text-align doesn't work with images and divs. That just works for text. When it comes to images, you got to put a little "finesse" on the CSS with those. As for editing the classic templates with the new info, it doesn't always work that way with ''every'' template. Lethosor I think ''did'' update the creature infobox template in the way you mentioned. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 08:37, 8 January 2023 (UTC)
:::: You can use something like this to automatically handle that--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 08:56, 8 January 2023 (UTC)
{|
|-
|<div style="width:200px; display:flex; background-color:#eaecf0;">
[[File:miner_sprite_icon.png|center]]
<div>
|<div style="width:200px; display:flex; background-color:#eaecf0;">
[[File:miner_sprite_icon.png|center]] [[File:miner_sprite_icon.png|center]]
<div>
|<div style="width:200px; display:flex; background-color:#eaecf0;">
[[File:miner_sprite_icon.png|center]] [[File:miner_sprite_icon.png|center]] [[File:miner_sprite_icon.png|center]]
<div>
|}

Dwarf Fortress Wiki talk:Versions

2023-01-08T08:56:58Z

Jan: /* Graphics in Skill Infoboxes */

{{archive|
# [[DF Talk:Versions/Archive 1|Page 1]]}}

== Version 0.31.19 starts a new DF generation? ==

My reading of Toady's comments on the release of 0.31.19 is that it came out basically because he felt it would take too long to get DF all the way to 0.32. With the ore changes, the sitefinder changes, the addition of grazing and several different industries, there's a lot of changes between 31.18 and 31.19. So I'm thinking it might be a good idea to call it the first release of DF2011 - and what we refer to as "DF2010" would then become 0.31.18.

Thoughts? --[[User:DeMatt|DeMatt]] 07:06, 28 February 2011 (UTC)

==Revisiting Redirects==
I wasn't around when the redirect policy was created, and I'm having trouble understanding the rationale. The example claims that linking [[Main:Cheese]] to [[cv:Cheese maker]] is problematic...but mainspace only ever redirects to the current version. If the best target in the current version is cheese maker, why not link to it directly? (It's not, at least for Cheese, since [[DF2012:Cheese]] exists now.) The explanation seems to be claiming that 40d articles that link to Cheese will follow the Mainspace link--but that hasn't been the case for a long while now. Articles in 40d automatically link against other articles in 40d, so that version remains internally consistent no matter where mainspace links to in the current version. For a current example, what do we gain by linking [[Main:Mead]] to [[cv:Mead]] and linking [[DF2012:Mead]] to [[DF2012:Alcohol]]?

If this really is just an outdated procedure, I recommend we drop the mummery and allow mainspace to link to cv:(best target). Double redirects ''may'' work (sometimes, but [[Main:Mead]] demonstrates a common problem where automatic redirection fails), but if they are unnecessary I think they should be avoided, partly because of problems like [[Main:Mead]] and partly because of the effort required to protect double redirects from users who believe they are problematic.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:16, 8 January 2014 (UTC)

:I was just thinking that. I'm currently attempting to write a basic extension to eliminate the need for mainspace redirects entirely, although Mediawiki's class structure may make this more difficult than I had hoped (the only method I've found for resolving redirects takes the ''article text'' instead of a title, e.g. "#REDIRECT ..."). I do agree that the current situation with redirects isn't ideal, so I'm hoping this will work better (once I get it to work). --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:42, 8 January 2014 (UTC)

Okay, that wasn't quite as clear as I meant it to be. In general, I think this is a tricky situation. Mediawiki wasn't designed to have five content namespaces, and certainly not chains of redirects between them. The problem that was pointed out in the [[DF:REDIR|policy]] is the fact that with:
Main:Foo -> cv:Bar
pages in the cv: namespace can't use [[<nowiki/>foo]], since the namespace links modification causes it to be treated as [[<nowiki/>cv:foo]] instead, which doesn't exist. The current suggested solution is this:
Main:Foo -> cv:Foo -> cv:Bar
This fixes the problem of [[<nowiki/>foo]] not working on cv pages, but creates issues with double redirects not always working. Another solution, which is more intuitive to new editors, is:
Main:Foo -> cv:Bar
cv:Foo -> cv:Bar
Both require creating two redirects. The first method has the advantage of ''ensuring'' that the cv redirect exists (otherwise, main:foo would be a redlink), while the second has the advantage of working more reliably in a couple cases.

What I'm trying to do is make main:Foo "jump" to cv:Foo when cv:foo exists, ''even if main:foo doesn't exist'' (basically it would treat all mainspace pages as redirects to cv pages, but only if the cv page exists and not the mainspace page). I had main:Bar jumping to cv:Bar fine, but if cv:Foo redirected to cv:Bar, accessing main:Foo would mysteriously stop at cv:Foo even if I increased the redirect limit. What I'm trying to do now is follow the redirects internally, without relying on Mediawiki to do it automatically - unfortunately, that has proved to be harder than I had hoped (and I sent my web server into an infinite loop while trying). I will try to work on this some more when I get a chance, although I'm not sure when that'll be yet :(. For now, feel free to fix broken double mainspace redirects as necessary, as long as redirects in the DF2012 namespace stay pointing to the right page (and new mainspace redirects get added in the DF2012 namespace too). --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:21, 9 January 2014 (UTC)

:You're treating cv like a namespace--it's not. It is simply shorthand for "fill in the current version here". [http://dwarffortresswiki.org/index.php?title=User_talk:Briess&diff=182404&oldid=181281 As I discovered a long time ago on a server not far away], linking from Main:Foo to cv:Foo tends to break redirection chains. If, instead of linking to cv:Foo, you link to DF2012:Foo, it might just work. It would, of course, be better if your patch could evaluate cv itself, but even if you have to hardcode the current version it's a single point of maintenance that requires update very infrequently. (For that matter, we could probably dispense with the cv hack entirely and just have a bot update mainspace links from DF2012 to DF201X when we switch to a new version.)--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:05, 9 January 2014 (UTC)
::I know cv isn't a namespace - I was just trying to avoid future confusion when the DF2012 namespace changes. It's interesting that changing "cv" to "DF2012" fixes some broken redirects, although I've found that simply making an edit to a broken redirect can usually fix it as well. I've actually had the most problems with double redirects when the second one (in the DF2012 namespace) doesn't use the DF2012 prefix (e.g. main:Foo containing <nowiki>[[cv:Foo]] and DF2012:Foo containing [[Bar]]</nowiki>). I'd rather keep the cv alias even if it isn't necessary for mainspace redirects when I get the patch to work, since it makes it easier to refer to the current version of the page (for example, several MDF articles contain links to a vanilla page for things that don't change in the mod).
::Also, using aliases like "cv" is supported by Mediawiki; in fact, several WMF wikis use them (for example, "[[wikipedia:WP:Redirects|WP:Redirects]]" on Wikipedia). It's quite likely that Mediawiki isn't processing double redirects using aliases correctly, though, since that's uncommon on most wikis. --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:35, 9 January 2014 (UTC)

In light of the lack of support for the current redirect policy, I propose we replace the current redirect section with:

:Mainspace article pages should use the cv: alias when redirecting to a versioned page, which will automatically update the link when a new version is released. For example, page "Main:Foo" should redirect to page "cv:Bar" (where "Bar" is the page that best describes the topic Foo in the current version).

:Pages in mainspace should only redirect to an older versioned page if that content no longer exists in the current version of the game (e.g. [[Cave river]], [[Chunk]]). In these cases the cv: alias cannot be used.

:Pages inside a versioned namespace should not use the cv: alias. Instead, they should redirect to the best page within that versioned namespace (e.g. [[DF2012:Dodging]], [[v0.31:Drink]]).

:Due to limitations of the wiki software, double redirects should be avoided if possible. When fixing double redirects in mainspace, please make sure to use the cv: alias as appropriate.

If no one objects, I will make this change in a few days.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:21, 15 January 2014 (UTC)

:Okay with me. It may be worth mentioning that double redirects only really need to be changed when they don't work (since changing a lot of redirects that work isn't necessary), but I think it's clearer and more relevant than the current policy. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:26, 16 January 2014 (UTC)

Done.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:55, 22 January 2014 (UTC)

I was finally able to get my extension to work after being motivated by one too many malfunctioning redirects. It now causes nonexistent pages in the main namespace to behave exactly like redirects to their DF2012 counterparts (when linked to, accessed directly, and transcluded). Double redirects also work (up to 100, in fact, although that was a temporary safety measure that I'll probably change). This means we'll be able to safely get rid of all mainspace redirects (redirects that redirect to something other than "cv" will still function if not deleted). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:20, 14 March 2014 (UTC)
:What about articles which don't exist in the current version but do exist in older versions? Will those still need mainspace redirects, or will your extension be able to automatically redirect them to v0.31/40d/23a? --[[User:Quietust|Quietust]] ([[User talk:Quietust|talk]]) 01:29, 14 March 2014 (UTC)
::It ignores all mainspace pages that actually have content, including redirects, so pages like [[masons guild]] won't be affected (unless deleted). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:47, 14 March 2014 (UTC)

Done and deployed. [[Cat]] is still treated as a redirect, even though I just deleted it (try clicking on the "redirected from" link). Pages that exist are ignored, so [[Masons guild]] and [[History of Dwarf Fortress]] still function normally (as a redirect to a 23a page and a non-redirect, respectively). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 18:57, 14 April 2014 (UTC)

I'm sending around a bot right now to delete all redirects of the format "foo -> cv:foo" (a surprising number don't fit this format, so I'm leaving them alone for now). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:43, 14 April 2014 (UTC)

:I'm confused. Do we use double redirects or not? Is there a single place we define our linking policy (including redirects), and is it updated?
:I had trouble linking to [[Consolidated_development]] in [[v0.34:Dragon]]. It kept pointing to v0.34:Consolidated_development, which does not exist. I ended up linking to Main:Consolidated_development to make it work. --[[User:Nahno|Nahno]] ([[User talk:Nahno|talk]]) 10:18, 1 July 2014 (UTC)

::That's a separate problem altogether - links in the versioned namespaces (v0.34, v0.31, 40d, 23a) automatically link to pages within their namespace. I may be able to set up a fallback to mainspace once I'm able to deploy again, but for now the "main:" alias is the intended solution. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 11:36, 1 July 2014 (UTC)

== Google often directs people to the 0.31 page ==

I've noticed a couple of times that finding a wiki page from an external search will often drop me onto a page from an older version. Is it possible to mitigate this somehow for new players? I could imagine something like redirecting old:Bar -> cv:Bar unless the user has come from old:Foo; no idea if that would actually work though. [[User:PeridexisErrant|PeridexisErrant]] ([[User talk:PeridexisErrant|talk]]) 11:48, 4 May 2014 (UTC)

:As a temporary solution, I could write a script that displays a banner of some kind if the user came from an external site. I'll ask Briess if he can do anything on the server level to increase the weighting of the current version's pages. (Obviously there are situations where people are looking for old pages, like [[23a:dungeon master]], so we don't want to disable indexing entirely on old pages.) —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:03, 4 May 2014 (UTC)

== DF2014? ==

As Toady [http://www.bay12games.com/dwarves/ draws closer to a new release], it might be worthwhile to discuss the addition of a new version to the wiki. The upcoming release covers two years of changes and introduces a number of new plants, foods, drinks, multi-tile trees, climbing, jumping, etc., so it is likely to have significant changes from the current DF2012. To avoid having people start new pages (and lose all the effort spent refining the prior version's page), I think it would be best to have a bot automatically copy over the DF2012 pages as a starting point for DF2014. I would suggest that these copied pages include a noticebox template mentioning that the content may be outdated, so that we can easily track which pages have been reviewed. I think either the {{tl|version check}} or {{tl|old}} template would work. --[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 19:43, 5 May 2014 (UTC)

:This is what [[User:QuietBot]] did after the 0.34 release, so it's certainly possible to use the same script to migrate to DF2014. I would like a way of tagging migrated pages, since inaccuracies in some pages went unnoticed for months after they were migrated. Since {{tl|old}} is already in use, {{tl|version check}} may be a better solution (it can be reworded slightly, or we can make a separate template for DF2014 migration). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:23, 1 June 2014 (UTC)
:Made [[Template:DF2014 migrated]] as an example. Any thoughts? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:32, 1 June 2014 (UTC)

== Redirects inconsistency ==

Following a redirect is supposed to be exactly the same as going straight to the page it redirects to, but this actually isn't the case:
* Go to [[Seeds]] and you get [[v0.34:Seed]] (outdated)
* Go to http://dwarffortresswiki.org/index.php?title=Seeds&redirect=no and click on the link and you get to [[DF2014:Seed]] (current)
So if you search for "seed", the top result is the DF2014 version. But search for "seeds" and you get the redirect, which sends you to the outdated page instead. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 23:22, 22 February 2015 (UTC)

While I'm talking about redirects, it seems redirects to sections don't work: see [[DF2014:How do I manage my seeds and crops]]. I know MediaWiki is capable of this trick because Wikipedia does it. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 23:32, 22 February 2015 (UTC)

:I have absolutely no idea why [[seeds]] redirects to a v0.34 page - it could be a Mediawiki bug. The section links issue is due to a known issue in the redirect extension we use, which has yet to be fixed. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:01, 23 February 2015 (UTC)
:It looks like deleting both [[Seeds]] and [[DF2014:Seeds]] fixed things (by allowing AutoRedirect to handle the redirects instead). Feel free to tag any others with {{tl|bad redirect}}. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:03, 23 February 2015 (UTC)
::It gets stranger. [[Vial]] redirects explicitly to [[cv:Flask]] which displays (when you look at it with &redirect=no) as [[DF2014:Flask]], but still goes to the v0.34 version. It seems redirects interpret the cv: pseudo-namespace (or whatever it's called) in an outdated way. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 18:08, 23 February 2015 (UTC)
::I've added a note to this page about this issue. If it gets resolved, the note should be removed. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 21:04, 23 February 2015 (UTC)

==Reorganizing versions==

The internet deals with moved content... poorly. Google is still linking to v0.34 pages more than a year after the switch to "DF2014", and even the wiki software still has cached links pointing to the old version pages.

I propose reorganizing versions on the wiki to avoid moving content whenever possible. Instead of having a temporary "current version" namespace that changes occasionally, all the current information gets promoted to the Main namespace. When the next version split occurs, the Main articles as of a certain revision number can be copied to the newly-created permanent "old version" namespace, while all the current information remains in Main. This not only fixes the link rot issue, but it has a few other benefits as well: fewer administrative tasks, no lockdown (a historical version of the Main pages can be copied at any point, even if the Main articles are already modified for the new version), almost all the article history is maintained in the Main article (instead of being spread unevenly across multiple versions), no "temporary" namespaces are needed, fewer problematic long redirect chains, and hopefully less user confusion (since Main gets priority in search results, etc.).

As an example, today we would not have a DF2014 namespace (which is good because "temporary" namespaces historically disappear anyway). If you ran a search for [[seed]] you'd end up at Main:seed, which would have all the current information on seeds. The version box at the top of the page would still link to the older versions of the seed article. When a new version is released, an admin would choose a revision number and copy the Main:seed article as it exists at that revision number to v0.40:seed. That's it. One historical copy that needs little to no new editing, and zero redirections/moves.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 19:02, 27 July 2015 (UTC)

:Makes sense to me. It would involve a lot of work, though (e.g. fixing templates and categories to account for the current version being in mainspace), although that should be doable thanks to {{tl|category}}, {{tl|version switch}}, etc.. A bot could be set up to copy revisions from before a release date as well, which would be more difficult (and maybe slower) than a direct copy, but not severely. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:24, 30 July 2015 (UTC)

:Actually, there are a few issues with that, namely that there wouldn't be an easy way to distinguish between versioned and non-versioned mainspace pages. There are ways to resolve Google search priority (we can exclude pages from older versions from search engine results if there are newer versions of those pages available, for example). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:47, 6 August 2015 (UTC)

::There aren't very many non-versioned mainspace pages, and determining if a page is versioned is as simple as looking for the version template and/or categories added by the version template (e.g. copy [http://dwarffortresswiki.org/index.php/Category:Current this category] instead of Main:*). The problem with "suggesting" newer pages to Google is that they obviously aren't crawling our wiki regularly (if they were, the fact that the mainspace redirects point to new pages would automatically be picked up). Even if your Google hints worked they wouldn't do anything for all the other broken links out on the 'net.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:35, 6 August 2015 (UTC)

::: Google actually crawls the wiki constantly - we probably get crawl hits from google for a continuous block of 2-3 hours per day, each and every day. Why they are slow to update is beyond me though. I can't remember why we didn't do this initially, but there was a technical limitation involved if I remember correctly. --[[User:Briess|Briess]] ([[User talk:Briess|talk]]) 22:05, 6 August 2015 (UTC)

::: There are <meta> tags that can be used to hide pages from search results (for search engines that recognize them, that is). Searching for {{tl|av}} or [[:Category:Current]] might work, although we'd have to make sure all of the DF2014 pages include that (some pages don't, particularly some disambiguation pages, although all of them should). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:53, 6 August 2015 (UTC)

:Is there a particular reason main and current are separate to begin with?—[[User:CLA|CLA]] ([[User talk:CLA|talk]]) 00:17, 7 August 2015 (UTC)

::It's mostly intended to distinguish between versioned and non-versioned pages and make version-related templates simpler to work with, since every versioned page has a namespace. I wasn't active here in 2010 when this system was created, so Briess and Emi would know more.
::Another issue I just thought of with Loci's suggestion is categories - currently, categories like [[:Category:Animals]] are used to organize the versioned sub-categories. Sure, we can change {{tl|Category}} to categorize mainspace pages in [[:Category:v0.40:Animals]] or [[:Category:DF2014:Animals]], but that would be less straightforward because there wouldn't be a namespace with that name (until pages are migrated when a newer major version is released). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 13:05, 7 August 2015 (UTC)

:Moving current pages to the main namespace sounds like a great idea. -[[User:Jecowa|Jecowa]] ([[User talk:Jecowa|talk]]) 20:47, 4 January 2018 (UTC)

Another thought: dealing with migrating redirects could be difficult with this proposal - specifically, determining which redirects should be migrated to a versioned namespace. Redirects can't contain {{tl|av}}, at least not before ``#REDIRECT``. I ''think'' it would be possible to copy pages in two stages, though - all non-redirects first, then all redirects whose targets were also copied. Thoughts? Anything I'm missing? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:41, 27 June 2019 (UTC)

Some subpages (particularly /raw and /Edit notice) also deliberately lack {{tl|av}}, although those shouldn't be too hard to handle. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:35, 9 July 2019 (UTC)

:Redirect pages (and all other edge cases I've looked at) can be included in categories (like [[:Category:Current]]) to determine whether or not they should be copied into an archival version. But if the redirects are "properly qualified" then they can all be copied over blindly. Mainspace redirects pointing to versioned information should use a blank namespace (which will be automatically constrained to the archival namespace); mainspace redirects pointing to unversioned information should use an explicit "Main" (which will automatically link back to the unversioned page). Then, when [[[[Toady]]]] gets copied to [[[[v0.4x:Toady]]]] it will point back to [[[[Main:Toady One]]]]. Meanwhile, [[[[Beer]]]], copied to [[[[v0.4x:Beer]]]], will properly point to [[[[v0.4x:Alcohol]]]].--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:00, 14 July 2019 (UTC)

::I think qualifying redirects is the best solution here - categorizing redirects manually is another possible source of errors, since categories (or a lack thereof) would only be visible on the redirect page itself, and [[:Category:Current]] is a hidden category. Copying over mainspace redirects into versioned namespaces would also resolve some issues that have come up due to those not reliably existing currently. I should be able to set up a bot script to add "main:" to current mainspace redirects (and it shouldn't break anything, since those redirects go to other mainspace pages anyway). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:57, 14 July 2019 (UTC)

(Note: I wrote all of this without noticing the previous discussion above.) I was wondering, when the wiki creates a new namespace for a major release again, if it is possible to ''not'' create a namespace for the next current version (e.g. "DF202x") and instead have the mainspace articles (which are currently redirects) become the new cv and move the content there. Therefore, [[cv:Cat]] would just be "[[Cat]]" (or [[Main:Cat]]).

Certain namespace-related templates like [[Template:Ns/0]] would need to be changed, though nothing significant as far as I know. For most cases, any "DF2014" would be replaced with "Main" or even blank. There's also multiple extensions handling the current namespace system and they may need to be modified too, though I'm not sure if or how much. I'm guessing based on the discussions above that it will change stuff up.

My reason is the current namespace is increasingly becoming more anachronistic. "DF2014" could be misinterpreted as "this page is about the 2014 version of the game" or "this page was last updated in 2014", which I've seen a few people in forums mention. Granted that [[Template:Av]] is on the top of very article, I still think the namespace is inconsistent with the recentness of the article. But how is this related to what I'm asking for? Let's say we continue the current system: if we happen to do a new namespace change this year and create DF2020, the next major release (after graphics/UI) will be mythgen, which is estimated to take several years to develop (the Big Wait), and so the anachronism will start over again. The proposed way will prevent this from occurring for the next major release and every release thereafter.

I think the confusion with having a namespace that becomes old-fashioned overtime supersedes the confusion with not marking current versioned articles with a namespace. Most users just search "Cat" on the search bar and naturally expect to get information about the latest release of DF. So if users go a page that's just titled "Cat", they won't expect outdated info about cats from a previous release. That's how the current system works anyways. We'll be skipping the two-step process that we have now. It'll make several wiki tasks much simpler as well. Editors can create new articles for current versions without remembering to add a namespace. It'll fix any existing issues with (double) redirects; instead of [[Main:Kitten]] redirecting to [[cv:Kitten]], which goes to [[DF2014:Kitten]], which then redirects to [[DF2014:Cat]], [[Main:Kitten]] would just redirect to [[Main:Cat]]. And the cv: alias will no longer be necessary since "cv:" = "Main:" and will be forever.

There's no need to differentiate the current version and previous versions with a namespace for the current version is what I'm saying. Articles of previous versions will retain their respective namespaces. Users will still type "40d:Cat" to go to the 40d version of the article, but if they want the current version, they'll just type "Cat" (like now). The mainspace containing the "live" version of an article is natural and would create no uncertainty when browsing the wiki. And it would simplify the wiki somewhat and future-proof this anachronism problem. As a bonus, this change will also prevent web search engines from showing previous version pages when typing "DF cat" or something. (This isn't happening right now as DF2014 has been the current namespace for ~6 years, but it'll happen again when everything moves to a new namespace.)

This is the gist of it, and I may have ignored most of the problems with this proposal. I have personally wished for the whole version namespacing be made less complicated and have been seeking for a solution, and I feel like this is the best way to go about in the future. – [[User:Doorkeeper|Doorkeeper]] 21:27, 14 August 2020 (UTC)

:<s>Whoops, looks like Loci already proposed this exact thing long ago. I definitely missed that discussion and should have checked first. My apologies. I'll move my text to that section and remove this one. – [[User:Doorkeeper|Doorkeeper]] 21:36, 14 August 2020 (UTC)</s> Done. – [[User:Doorkeeper|Doorkeeper]] 21:40, 14 August 2020 (UTC)

:The main issue I have with that is that putting pages about the current version in a namespace also differentiates between those pages and pages not about ''any'' version (for example, [[Toady One]] does not need a 40d or v0.34 page). Yes, we can use {{tl|av}} to mark versioned pages, but people often forget to add that to new pages. The current system also allows determining whether a page is versioned or not from its title, which makes migrations a lot faster. Relying on {{tl|av}} would require either reading the content of every page (which would slow scripts down significantly) or cross-checking with the list of all pages including the template (feasible, but a bit more complicated, and still susceptible to missing templates). I suppose that manually fixing and migrating pages missing {{tl|av}} later wouldn't be too much work, though.
:I am definitely in favor of changing "DF2014" (or a new namespace) to "Current", though. I was in favor of "DF2014" in 2014, but I don't think it makes sense anymore, and "Current" seemed to be a popular alternative in both the DF2012 and DF2014 discussions on the matter. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:02, 16 August 2020 (UTC)

== Weird redirect behaviour ==

[[Pump stack]] redirects to [[cv:Screw pump#Pump stack]]. If you look at the redirect itself it says it redirects to DF2014 namespace, which is correct. But if you actually follow the redirect, it goes to v0.34 namespace. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 16:10, 20 August 2018 (UTC)
:Yeah, that's part of the issue described in the above section (the wiki caching part, not on Google's end.) —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 15:00, 21 August 2018 (UTC)

== v50 organization ==

Some wiki admins have had a talk on Discord and decided that the most sustainable path forward is to put content for all future versions of DF in the main namespace. We will be working on a bot to do this in the next few days. Feel free to chime in with suggestions here. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:56, 14 December 2022 (UTC)

:Is it maybe possible to do backwards-namespacing? Like we have a "Main" namespace, which people are free to update, and whenever there's a new version of DF the "Main" namespace is copied into a namespace for the then old version, much like how you'd branch a stable branch from a development branch when working with a git-project? [[User:Therahedwig|Therahedwig]] ([[User talk:Therahedwig|talk]]) 23:13, 14 December 2022 (UTC)

::Yeah, we could do that if we decide to. We were talking about doing that for v50, actually, and might still do something similar to preserve edit history if it doesn't end up being too hard to automate. Our hope is that we will not introduce new namespaces for v50 -> v5x, unless there is a serious breaking change (and hopefully there isn't one). But if we change our mind, one advantage of the type of migration you mentioned is that it can be done retroactively - we can copy historical revisions that were current at the time of the release, and would only lose some typo fixes made after the release that apply to earlier versions as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:11, 15 December 2022 (UTC)

ETA is < 24 hours. Doing some final checks on a migration script. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 07:08, 19 December 2022 (UTC)

: We should really have a task list as there are many things that change and need updating. Including but not limited to:
:* Most templates that used the previous namespace convention broke, including nav templates.
:* Many game files changed locations and their pages need to be updated.
:* Raws need to be updated.
:* Various features added, changed, removed.
:* UI has been changed -- though I am more inclined to wait for classic release to avoid extra work --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 06:56, 20 December 2022 (UTC)

"''Raws need to be updated.''" Including applying text wraparound where necessary, I suppose - more than a few of them have proven to be that special kind of...''difficult'' to navigate otherwise, shall we say? [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 12:52, 20 December 2022 (UTC)

:There is already a task list in the [[#v50 migration|section below]] that includes templates and raws, with an explanation. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:25, 20 December 2022 (UTC)

== v50 migration ==

The initial migration script is done. New content is in the '''main''' namespace, e.g. [[Cat]]. Old content is still at [[DF2014:Cat]]. History was migrated to the ''new'' (main namespace) articles.

I know several things are broken still. Please reply if you find any others:
<div style="border-left: 2px solid red">
* <s>Versioned templates haven't been migrated yet (e.g. {{tl|vermin}} on [[Ant]])</s>
** Fixed. Most were migrated by a bot.
* <s>Raws are missing on all pages that use them.</s>
** This also affects sidebars, such as on [[Cat]] and [[Microcline]].
** Update: The DFRawFunctions extension has been upgraded to include v50 raws, using the "v50:" prefix for filenames instead of "DF2014:". <s>I haven't finished a migration script to create the /raw pages themselves, but they can typically be created manually by copying the DF2014 /raw pages and changing "DF2014" to "v50" everywhere.</s> —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:20, 1 January 2023 (UTC)
** Update 2: Raws have been added for all pages! They were copied from the "DF2014" pages and had "DF2014" replaced with "v50", which appears to have worked from a spot-check, but let me know if you find any problems. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:57, 4 January 2023 (UTC)
* Some pages where the DF2014 page was a redirect to a main namespace page that contained content were migrated incorrectly.
** In this case, the main namespace page is usually a redirect to itself. This can be fixed by undoing LethosorBot's edit to the main namespace page, then copying the content to the DF2014 page.
** Update: most seem to have been fixed manually - thanks! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:41, 21 December 2022 (UTC)
* <s>Some main-namespace talk pages redirect to DF2014 talk pages. Some of these redirects work, and some (usually older ones) do not.</s>
** Fixed with a bot. Some redirects from talk pages to other deleted talk pages are now broken, e.g. [[Talk:Above_ground]] (exists) -> [[Talk:Tile attributes]] (redlink). I am leaving them like that because they redirect to where the talk page should be created, but I'm also fine with people deleting them if they really want to. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:41, 21 December 2022 (UTC)
* {{tl|quality}} for new articles is disabled (see below)
* Some links from DF2014 to Main weren't working: e.g. the version selector [[DF2014:Mason's workshop]] was linking to [[DF2014:Main:Mason's workshop]] instead of [[Main:Mason's workshop]]. I'm not sure exactly why, but I fixed it with a change to the NamespaceLinks extension. Let me know if you spot similar broken links. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:19, 21 December 2022 (UTC)
</div>

—[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:54, 20 December 2022 (UTC)
:The quality levels of the 50.03 pages seem to be missing. I'm not sure if that's covered under that first point. [[User:Trainzack|Trainzack]] ([[User talk:Trainzack|talk]]) 06:47, 20 December 2022 (UTC)
::If the the [[Dwarf Fortress Wiki:Quality]] feature can be made to work with namespace scheme change, I suggest to automatically assign the lowest quality rating to all pages, alternately add the {{tl|old}} to all pages. Otherwise there will be a lot of pages that will fall through the cracks. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 09:12, 20 December 2022 (UTC)
:::I disabled {{tl|quality}} in the main namespace because it would require some rework to make the rating script and the template work properly there. Feel free to take a stab at the template. I will see what can be done on the extension side. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:14, 20 December 2022 (UTC)
::::What needs to be done on the template side? I'm not sure I see too big of an issue leaving pages as "unknown-quality" for now (or just change the default to tattered) until we get the rating script working. Is that script up anywhere, anything that could be helped with? [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 11:10, 2 January 2023 (UTC)
:::::They're already marked as unknown. Really the only issue I know of with the template is that it doesn't show up with some of the newer skins we added, and that can be fixed by getting rid of the absolute positioning. As for the script, it can be found at https://github.com/DF-Wiki/QualityRatings, and the issue is really only with the configuration system not recognizing the main namespace as valid. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:29, 3 January 2023 (UTC)
::::::Great, I started having a crack at fixing the template with different themes. Is the preference to get some CSS going and then include it in the global stylesheet (i.e different styles per theme) or to try and get a "one size fits all" fix? —[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 08:14, 3 January 2023 (UTC)
:::::::I would rather avoid custom site-wide CSS if we can. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:29, 4 January 2023 (UTC)
::::::::I appreciate that, I think it's the simplest solution to add a few lines to common.css though. Unless there is a way to attach CSS specifically to a template, I saw a few extensions that allowed that but I'm not sure if any are present in the wiki at the moment. Regardless there already exists a class `div.topicon` that is specifically for the quality ratings, is there an issue with expanding this class to accommodate the themes? The list of themes where the quality rating display is broken/invisible: Citizen, MinervaNeue, MonoBook. —[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 21:48, 4 January 2023 (UTC)
:::::::::What do you think of moving the template out of the topicon entirely and just placing it in a div? It would take up a (hopefully) small amount of vertical space in the article. [[User:Lethosor/Sandbox/Quality_test]] is an example. Unfortunately it isn't possible to prevent other templates from displaying above the quality this way ([https://dwarffortresswiki.org/index.php?title=User:Lethosor/Sandbox/Quality_test&oldid=283883]). So maybe we do need some custom CSS after all if we want that. I'm open to trying out whatever you propose. I'm a bit worried about future-proofing against skins we add later (particularly a mobile skin) but at least MediaWiki supports skin-specific global CSS as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:33, 5 January 2023 (UTC)
::::::::::I would rather we avoid taking any more vertical space in the article. The growing block pyramid at the top, starting with version template, is annoying. If you end up placing it inside the article space please use a slim box 100% wide that would include both.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 01:19, 5 January 2023 (UTC)
:::::::::::Agreed with you Jan, however I see that as two different tasks (ArticleVersion template changes, getting quality back on pages). I made a test adjustment to the quality and it takes up a negligable amount of extra space. See [[User:Vallode/sandbox#Page_quality]] for the example, we'd be able to completely remove "topicon" (unless it is used somewhere else?) and then potentially move on to making the ArticleVersion template into a slim version on the left-hand-side instead of a large box? Let me know what you think. --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 17:35, 5 January 2023 (UTC)

It appears some pages are redirecting recursively and never resolving correctly, like the [[https://dwarffortresswiki.org/index.php?title=Character_table&redirect=no|character table]] and [[tileset repository]] 07:35, 20 December 2022 (UTC)
: Indeed, these can be caught here: [[Special:DoubleRedirects]] --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:51, 20 December 2022 (UTC)

It might be useful to change the notice title to "release information '''for editors'''" --[[Special:Contributions/142.59.195.176|142.59.195.176]] 10:26, 20 December 2022 (UTC)
:Can do. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)
::New here, hello. Should we set a date where we remove/only show the banner for logged in users. There are (some) pages that have 4 different notices about the upgrade. [[Engraving]] is one such page, the top banner states "information for editors", we then have the "this page was migrated" banner, a version selection which warns the article might be inaccurate, and a smaller banner saying the page might need to be updated. Quite a lot of screen space, I think we can start to slowly reduce the amount of warnings this coming month? [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 10:07, 2 January 2023 (UTC)
:::Unfortunately, only showing info to logged-in users is difficult with how MediaWiki caching works. In terms of reducing warnings, there is a discussion [[Template_talk:ArticleVersion#.22Note_that_some_content_may_still_need_to_be_updated..22|here]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:43, 4 January 2023 (UTC)
:::As for [[Engraving]] specifically, the {{tl|old}} banner was actually present on [[DF2014:Engraving]] as well and got carried over with the migration. I removed it, and agree that it was redundant. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:46, 4 January 2023 (UTC)

Main talkpages seem to redirect to DF2014 talk. Not sure if it is intentional but I like it, though we should pay attention when creating new discussion relating to v50 ending up there.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 14:18, 20 December 2022 (UTC)
:That's unintentional. I specifically wrote the migration script to not move talk pages, but that has the side-effect of leaving any previously-created "Talk -> DF2014 talk" redirects intact. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)

Yo Lethosor, are we adding graphic sprites for the pages in some way? Or are we waiting for you to add some sort of new template or something? I'm sure you don't need me to tell you that the current templates don't allow that. Not sure if I'm allowed to change/create any templates either, as I don't want to break things for hundreds of pages. Edit: And IF the icons are allowed, should they be left alone, or 2×-3× sized like how the Minecraft wiki does it? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 14:29, 20 December 2022 (UTC)
:Depends on which templates you mean. There are copyright concerns with uploading a premium sprite sheet, for instance. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)
::I'm not talking about uploading an entire sprite sheet. I'm just talking about individual icons for each respective page. One image for cows, one for horses, one for werebeasts, etc. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 16:50, 20 December 2022 (UTC)
:::If we do that for every creature in the sprite sheet, that's not much different (in terms of copyright) from uploading the entire sprite sheet. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:09, 20 December 2022 (UTC)
::::Is there someone we can talk to about that? We finally get this new game with graphics, and then we can't use the very graphics of the game? No matter what the rules are, I'd say that would be the stupidest thing ever. I know I'm infamous here when it comes to copyright and images and stuff, but about 80% of game wikis out there are completely unofficial, and use game file images like no one's business. I can't imagine anyone's door being knocked on if we used the game's sprites, but I won't add any here until we have a go-ahead. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 17:14, 20 December 2022 (UTC)

:::::...I've made noise in Mayday's direction on this matter, at least (prob an incorrect maneuver, ''but'').[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 17:55, 20 December 2022 (UTC)
:::::: I hope some sort of arrangement can be made so we can use the new sprites with permission/limits, just as we are using the raw files. Otherwise we are all (devs and editors alike) shooting ourselves in the foot here.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 21:07, 20 December 2022 (UTC)

:::::::I just thought of something. We're supposedly not allowed to upload entire sprite sheets, right? What if - for the time being - we just use a few of them for the purpose of testing out new infoboxes? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 21:46, 20 December 2022 (UTC)
::::::::I don't know. If someone could ask Kitfox and post the response here, that would be great. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:47, 20 December 2022 (UTC)

:::::::::I've reached out to Alexandra, but she hasn't answered yet. Until then I found these old approvals from the previous community manager, Feeona: ([http://www.bay12forums.com/smf/index.php?topic=173474.msg8243633#msg8243633 link1], [http://www.bay12forums.com/smf/index.php?topic=176640.msg8243642#msg8243642 link2]). Waiting for a newer response until we begin mass uploads is probably the politer option, but like Zippy said, it is also standard for wikis to use game sprites with less approval. I second their idea of trying it out with a few images to test the infoboxes. On the extreme off-chance (and I do think it is) Kitfox protests we can always remove these few. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 22:19, 20 December 2022 (UTC)
:::::::::And here is a third, more official statement: ([http://www.bay12forums.com/smf/index.php?topic=173474.msg8249718#msg8249718 link3]). Perhaps that address of info@kitfoxgames.com is the better channel to ask for a confirmation, rather than Discord DMs, but I will be going to bed, so it is best if someone else does that. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 22:29, 20 December 2022 (UTC)
::::::::::Thanks for tracking this down! Ok, sprites should be fine, but let's avoid uploading the entire premium tileset as a single image, for instance (as the forum thread says, "use common sense"). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:21, 21 December 2022 (UTC)
::::::::::: Looks good, permission is always preferable over fairuse, I think it is a win win for all involved. I agree that we shouldn't upload entire sprite sheets (e.g. there is no reason to upload the windmill from every direction or whole construction phase for workshops) and that there are a lot of details that needs to be ironed out through testing. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 05:07, 21 December 2022 (UTC)
:::::::::We have a green light on uploading all and any sprites. Their response to me can be seen [https://i.imgur.com/BhmHjzC.png here]. I'm sure someone else confirmed it before me. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 19:00, 21 December 2022 (UTC)

Shifting temporarily to a new issue, is the documentation of [[Template:ArticleVersion]] outdated? It would seem so to me, since the current version no longer has its own namespace, with the templates needing updating being different ones. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 18:30, 20 December 2022 (UTC)
:I think it is still accurate enough. We left open the possibility of making another namespace in the future, albeit with a different migration strategy - see [[#v50 organization|above]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:52, 20 December 2022 (UTC)

Some Changes to infoboxes might be needed. Too bad [[User:Doorkeeper]] isn't around. He did a great work with navbox project--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:52, 21 December 2022 (UTC)

I just realized that raw files aren't stored as regular wiki pages but loaded via the DFRawFunctions extension (hence the need to update). Good news it's going to be handled in bulk, consistently and relatively easy to updated. Even better it's Lethosor problem ;) Also I just realized that all the "raw files" (txt files in the new vanilla folder) are released into the public domain. Both are probably not news to the vets but I'll leave it here for those who less up to date like myself. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:35, 22 December 2022 (UTC)

: I noticed that some templates aren't working properly in the new namespace, e.g. [[Basalt]] entry had its raw updated manually but the infobox fail to show any details. Cursory look suggest {{t|layerlookup/0}} need a minor tweak. This should do the work
:: Replace: <nowiki>{{layerlookup/aux|{{{{FULLPAGENAME}}/raw}}|uses={{{uses|}}}|wiki={{{wiki|}}}}}</nowiki>
:: With___: <nowiki>{{layerlookup/aux|{{</nowiki>:<nowiki>{{FULLPAGENAME}}/raw}}|uses={{{uses|}}}|wiki={{{wiki|}}}}}</nowiki>
: Not sure what the plan and ETA with raws update so I didn't touch this high usage template for now. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 08:11, 24 December 2022 (UTC)

::Please do feel free to make this update. I am still working on a script to create the <code>/raw</code> pages themselves. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:12, 1 January 2023 (UTC)

Wouldn't it be an idea to add to the Sitenotice to remove the {{tl|migrated article}} tag when an article has been fully updated? I see many articles that seem to be updated still have the tag. And/or advise to make use of the {{tl|verify}} for sections still in need of checking? --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 10:12, 2 January 2023 (UTC)
:Probably a good shout. The "see this page" link does include the detail on removing but we should more explicitly encourage removing the banner once a page has at least been looked over. [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 11:01, 2 January 2023 (UTC)

== v50 specific issues ==
=== Graphics===
Follow up on the use of game sprites and the need to trying it out with a few images to test the infoboxes. First sprite [[:File:Beds v50.png]] was uploaded and used on [[Bed]] entry. Any thoughts? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:06, 21 December 2022 (UTC)
:Seems like it should be rearranged to be horizontal. Also, has there been a serious discussion about copyright? Full screenshots are 100% fine, but you start going into a grey area when you upload pieces of a spritesheet. I'm of the opinion that it's all fine as long as it's inconvenient to reconstruct the full sheet from the individual images. Maybe a further restriction could be you shouldn't upload any of the art unless it's used in an infobox (maybe an exception for pieces of the UI). And one more restriction could be you shouldn't show everything, like in your bed example, maybe just the wooden bed is good enough, leave out the stone and metal, especially since those can only be made from strange moods. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:43, 21 December 2022 (UTC)
::Actually, your bed image is kinda bad for showing off what a bed looks like because it doesn't show the pillow/blankets. That might point to cropped screenshots being the best path, although less convenient for the uploader, as you don't get details left out. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:46, 21 December 2022 (UTC)
::I created a new license template [[Template:Copyright game]], based it on the way the RimWorld wiki does things. Call it a prototype, but it's probably how your bed image should be labelled. Indeed, I added it to it already. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]])

::: I agree that the horizontal arrangement would suit better here and that we should strive to represent how things look in-game. Otherwise, I am not too concerned about people being able to reconstruct anything (lets just say that ''anyone'' interested in that can get the real thing from the game files), also it seem we have permission to use the sprits on top of fairuse. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 19:55, 21 December 2022 (UTC)

::: Modifying the existing template to allow the inclusion of the new sprites is easy (Something like [https://ibb.co/zFXCrjd this]?) The big question is the matter of consistency is there any exceptions that will break the format (size wise with variant bloat for example), the sprite naming format, etc --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:44, 21 December 2022 (UTC)
::: If we are going to show a variant for each material type, then maybe these should be added as separate images so we can add a tooltip for each image. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:49, 21 December 2022 (UTC)

:I've got another prototype going here and here: [[User:Brightgalrs/vector.css]] and [[User:Brightgalrs/Sandbox]]. (You'll need to add the css stuff to your own /vector.css). Basically it's a way to recolor images using css classes. No idea if there's a better way. Also, the real implementation would require a change to [[MediaWiki:Common.css]]. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 22:41, 21 December 2022 (UTC)
:Should mention, there ''is'' a different way, just upload each image 16 times, one for each coloring. But maybe that's not very elegant. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 22:45, 21 December 2022 (UTC)

: It should be noted that soon the classic edition will be released, hence one should plan to have both the Premium and classic alongside in that little space --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 03:14, 22 December 2022 (UTC)
::I'm looking into a tab extension to potentially support this in infoboxes. Perhaps [https://www.mediawiki.org/wiki/Extension:Tabs Extension:Tabs]? I tried [https://www.mediawiki.org/wiki/Extension:TabberNeue Extension:TabberNeue], but it displays a placeholder if JavaScript is disabled, which isn't great. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:22, 22 December 2022 (UTC)
::: The Neue Tabber seem to works pretty much like the old one (which fandom [https://coding-help.fandom.com/wiki/Tabber#Adding_images_into_tabbers still use]) defaulting to showing the first tab only. Quick look suggest that neue work the same, plus the notice that 'Tabber requires Javascript to function' warning? if so, and if it is a bother, then you should be able to edit out the tabberneue-noscript string in code. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 06:29, 22 December 2022 (UTC)
::: I much prefer your tabber solution, but if that fails we can also use the gallery slideshow mode. If so, beware it has no way to control image size so the images have to be maliciously uploaded using the exact same size. example:
<gallery mode="slideshow">
File:SteelSample.png
File:TinSample.png
File:ZincSample.png
File:GoldSample.png
</gallery> --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 10:19, 22 December 2022 (UTC)

==== adding premium set to Infobox ====
I am unclear where are we going with this? 
1) Will (A) tabs be implemented, (B) we be using mediawiki toggle [[Template_talk:V50_workshop|example]] for premium and classic/blocked, (c) put images side by side, or (d) something else? 
2) Also [[silver]] and [[Pig iron]] use very different image style for example. 
3) Anything else you want ? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 12:32, 30 December 2022 (UTC)

: Personally, I would love tabs to be implemented, but I think that side by side might be best for most. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 12:32, 30 December 2022 (UTC)
: Here is rough layout we can use. It should fit most buildings given the default sprite size. There is also a different floor plan for both (inspired by reddit)

{|
|- valign=top
|
{| style="width:200px; background-color:#eaecf0; border-collapse: collapse; "
|+ 5×5
|- style="border-bottom:2px solid #3366cc; "
|<div class="mw-customtoggle-infoboxtab mw-ui-button mw-ui-progressive" style="border-top-right-radius: 10px; border-top-left-radius:10px;">toggle</div>
|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|- valign=top
|colspan=2|<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">
[[File:Siege workshop.png|center|160px]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab"">
{|
|rowspan=2 style="width:50%; font-size: 125%;"|<center>{{Template:Picture Siege workshop}}</center>
|style="line-height: 1em; font-size: 125%;"|
{| style="border-spacing:4px;"
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|}
|
{| style="width:200px; background-color:#eaecf0; border-collapse: collapse; "
|+ 3×3
|- style="border-bottom:2px solid #3366cc; "
|colspan=2 style="text-align: right;"|<div class="mw-customtoggle-infoboxtab mw-ui-button mw-ui-progressive" style="float:left; border-top-right-radius: 10px; border-top-left-radius:10px;">toggle</div>{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|- valign=top
|rowspan=2 style="width:50%;"|
<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">[[File:Carpenter's workshop.png]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab""><center>
{| style="font-size: 175%; border-spacing: 0; background-color: black; border: 2px solid black"
|- 
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"| {{Raw Tile|"|7:0:0}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|{{=}}|6:0:0}}
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"|
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|]|0:0:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
|}</center></div>
|
{| style="border-spacing:5px;"
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|
{| style="width:200px; height:100px; padding:10px; background-color:#eaecf0; border-collapse: collapse;"
|+ 1×1
|- style="border-bottom:2px solid #3366cc;"
| colspan=3 style="text-align:center;"|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|-
| style="border-right: 1px dotted #545557;"|[[File:Screw_press.png|32px|center|link=]]
| style="font-size:125%;"|<center>{{Template:Picture Screw press}}</center>
| style="border-left: 1px dotted #545557;"|<center>{{Template:Floor Plan Screw press}}</center>
|}
|
{| style="width:200px; height:100px; padding:10px; background-color:#eaecf0; border-collapse: collapse;"
|+ 1×3
|- style="border-bottom:2px solid #3366cc;"
| colspan=3 style="text-align:center;"|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|-
| style="border-right: 1px dotted #545557;"|[[File:water_wheel.png|32px|center|link=]]
| style="font-size:125%;"|<center>{{Template:Picture Water wheel}}</center>
| style="border-left: 1px dotted #545557;line-height:normal;"|<center>{{Template:Floor Plan Water wheel}}</center>
|}
|}
:Any thoughts on the direction and or any and all of its elements? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 10:16, 31 December 2022 (UTC)

::I kind of like side-by-side, if it fits. If anyone wants to implement a toggle button or tabs, I would ask that that be implemented in a template for now, so that e.g. we could change a toggle button to tabs in a single place if we decide to install an extension to support that. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:14, 1 January 2023 (UTC)

::: I noticed a comment saying that [[impassable tile]] are no longer used in v50, is that true for all constructions? If so, floor plans are no longer needed, making things much easier as we can fit everything in except the 5v5 constructions like trade depot (and even these can be placed one above the other if so desired). If not, any thought on the alternative floor plan design? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:46, 1 January 2023 (UTC)

:::: None of the constructions have blocking tiles any more from my experience playing. I haven't tested siege weaponry with that stuff, but none of the workshops have it, nor does any furniture. (walls and fortifications will of course obstruct movement [[User:AndrielChaoti|AndrielChaoti]] ([[User talk:AndrielChaoti|talk]]) 18:47, 1 January 2023 (UTC)
::::: Ok, I have removed them from v50. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 23:48, 1 January 2023 (UTC)

I have added a basic side by side variant to [[Template:V50 workshop]] and [[Template:Building]] for testing, let us know if there any issues. Few notes:
* The default image naming scheme of <code>workshop-name.png</code> will likely conflict with existing images here or on commons, maybe another naming scheme should be used like <code>v50 workshop-name.png</code> as it is with ascii pictures.
* There is inconsistency in image size. If you want to use large zoomed images then toggle is best, otherwise they need to be all in native size (96px for 3x3).
* In the current version the code roughly centers the images and if there is a big image like with [[Siege workshop]] it drops to a new line --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 23:48, 1 January 2023 (UTC)

How about combining shortcut keys and the new menu icons:
<div style="color:white; font-size: large; text-shadow: -1px -1px 0 #000, 1px -1px 0 #000, -1px 1px 0 #000, 1px 1px 0 #000;">[[File:Ui b.png]]<div style="position: absolute; bottom:-14px; right:3px;">b</div>[[File:Ui bo.png]]<div style="position: absolute; bottom:-14px; right:3px;">o</div>[[File:Ui bol.png]]<div style="position: absolute; bottom:-14px; right:3px;">l</div>[[File:Ui boll.png]]<div style="position: absolute; bottom:-14px; right:3px;">l</div></div>
--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 02:24, 3 January 2023 (UTC)

:I worry that this is difficult to read (I read it as "boil" at first). I would rather use something like {{tl|k}} with a known background. What about something like this? [[File:Ui boll.png]]<div style="position: absolute; bottom:-14px; right:0px;">{{k|l}}</div> or, alternatively, using flexbox without any overlap: [[File:Ui boll.png]]{{k|l}} —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:37, 3 January 2023 (UTC)
:: Same, but that is the best I came up with. We can use the key or maybe someone can help improve the design. Also 'l' is hard to read even with {{t|key}}.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 03:05, 3 January 2023 (UTC)
:: I added a {{t|Menu icon}} to start things so others can have a go with it. Also any thoughts on the icon naming convention (their shortcut sequence), is there easier/better way? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 09:36, 3 January 2023 (UTC)
::[[User:BarelyCreative]] updated the template: {{Menu icon|b|o|l|y}}. I think it looks good, thoughts? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:40, 3 January 2023 (UTC)
:::I like that, yeah. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:29, 4 January 2023 (UTC)
::::There were some places where it didn't make sense so display every icon all the time (like step-by-step guides), so I changed it slightly to allow display of fewer icons using "num" and counting from the end: <nowiki>{{Menu icon|b|o|l|y|sep=-;|num=2}}</nowiki> {{Menu icon|b|o|l|y|sep=-|num=2}} [[User:BarelyCreative|BarelyCreative]] ([[User talk:BarelyCreative|talk]]) 09:05, 4 January 2023 (UTC)

==== Bizarre palette-swapping idea/prototype ====
No idea if this is a good idea, since it takes a bit of time to set up, and there might be some performance issues... and maybe display issues?

But take a look at this:
{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock|palette-name=amber}}

It's way to swap palettes on an image, although the image itself is a table, with each cell representing a pixel. The template itself looks like this:
<code><nowiki>{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock|palette-name=saffron}}</nowiki></code>
Input the pattern and desired palette name.

I've got a larger showcase here: [[User:Brightgalrs/Sandbox/PaletteSwapShowcase]]. Only did a rock pattern so far, but all palettes are implemented.
The major use for this would be on each stone, metal, wood, etc. type's page. The palette could be read directly from the raws. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 03:22, 24 December 2022 (UTC)

:From a technical perspective, my primary concern is indeed performance. Both on the server side and client side, a large number of tables that large (in terms of markup and cell count, that is) tend to be resource-intensive to generate and render. I saw your image-filtering experiments on [[User:Brightgalrs/vector.css]], and while that strikes me as a newer and less-backwards-compatible approach, it would probably be more resource-friendly.
:Is this color adjustment something the game is doing natively? i.e. does this accurately match what the game displays? I bet we could slap together an image-filtering extension (or find an existing one?) that can do this if needed. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:49, 24 December 2022 (UTC)
::Yeah that's what I suspected. The images the template creates are spot on, checked it against a screenshot I took of some mica rocks in-game. The css stuff is unfortunately totally incorrect, was cool to learn about it though, so not a complete waste of my time :p. The premium, in-game graphics are true sprites, basically patterns of indexed colors. Each of the in-game colors (which are significantly expanded over the 16 ascii colors, there's 116/117) there is a palette defined in "\Dwarf Fortress\data\vanilla\vanilla_descriptors_graphics\graphics\images\palettes.png". Each indexed color of the sprite is swapped for the corresponding color in the palette. Because of that, the css stuff doesn't work since it's doing the hue/saturation/brightness changes to the entire sprite.
::I've looked into an existing mediawiki extension, couldn't find anything. One thing I did't really look at is some type of lua script/module that would basically emulate what the game is doing. So some function that takes in the base image as well as the desired palette, and based on that finds and replaces each color. No idea what mediawiki's capabilities are on that front. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 05:31, 24 December 2022 (UTC)
:::We do have Scribunto installed now, so it's totally possible to do something in Lua too - forgot about that. I can add you to the group that grants access to edit the Module namespace if you want to give that a shot. If we use an extension, we'd probably need a custom one, similar to DFDiagram (or perhaps DFDiagram could be extended - it's in dire need of a rewrite anyway). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:43, 24 December 2022 (UTC)
::::I asked around on the mediawiki irc, I think scribunto/lua is a deadend, at least for taking an uploaded image and doing stuff to it with a lua script. However I did come up with this even more bizarre solution, using block elements. [[User:Brightgalrs/Sandbox/PaletteSwapShowcase2]], maybe less resource intensive? Definitely displays a lot worse though, probably unusable.
::::{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock2|palette-name=saffron}}
::::I dunno, maybe none of this is worth it and we should just write some external program to put all the images together offline, and then just mass upload. It wouldn't be ''that'' many... [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 06:37, 24 December 2022 (UTC)

====Is there an easy way to just paste images from the clipboard?====

I use KDE spectacle to take screenshots straight to the clipboard (after cropping) -- is there an easy way to just paste (and auto-upload) an image into an article? It would make it a lot easier to contribute images. [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 23:35, 1 January 2023 (UTC)
:Unfortunately there is not. I would be open to a MediaWiki extension to support this if someone finds one. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:32, 2 January 2023 (UTC)
:: Looks like this could do it, but I haven't used it before: https://www.mediawiki.org/wiki/Extension:SimpleBatchUpload [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 19:41, 2 January 2023 (UTC)
::: It won't solve paste-from-clipboard, but this would be great for making uploading sprites much easier (auto-cutup spritesheet, rename, bulk upload). Could you add this, Lethosor? [[User:OddballJoe|OddballJoe]] ([[User talk:OddballJoe|talk]]) 21:47, 6 January 2023 (UTC)

====Standards for adding graphical version screenshots and images====

Hello, new user looking into adding imagery from the new version. Is there a standard for quality of new screenshots or images? I noticed that at a certain zoom level (2 zooms in from the furthest zoomed-out view), the graphics appear crisp and 1:1 pixel scaled, and I would propose that all images be taken at this scale whenever possible. If they need to be displayed larger, they should be nearest neighbor scaled in a photo editing program at 100% increments (Microsoft Paint will do this if you first select the image rather than directly scaling the whole canvas). I would also propose that images should be cropped to conform to the 32x32 pixel grid when possible, though this could be problematic with so many new graphical elements exceeding the bounds of their tiles. I would say the best practice for capturing artwork for items, furniture etc. ought to be done in a 3x3 open area to avoid shadows from nearby walls, or else extracted from the raw files (if this doesn't run afoul of being able to re-create the graphical version using those assets).

I know that perfect is the enemy of good, and any documentation is better than none, but just thought I'd ask about this, and see if/where something like this ought to be posted. [[User:Unclesporky|Unclesporky]] ([[User talk:Unclesporky|talk]]) 13:58, 3 January 2023 (UTC)
:It has been stated in [[Template:V50 workshop]] that <q>screenshots should be at the "native" resolution</q> but someone could edit the [[Screenshot]] page for best practice for the steam version. Or post some examples in [[Talk:Screenshot]] to find out what is best? --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 14:21, 3 January 2023 (UTC)

====How would I/should I go about putting creature sprites on their pages?====

Howdy. New player and wiki user here. I wanted to try and help update the wiki to the Steam release of DF, so I figured I'd chip in by putting each creature's sprites on their respective page, since I'll often look up a creature I have yet to see in game only to be met by a blue J, or whatever. I found all of the game's creature sprites in C:\Program Files (x86)\Steam\steamapps\common\Dwarf Fortress\data\vanilla\vanilla_creatures_graphics\graphics\images, so I figured I could just chop those up in Photoshop and stick them on here no problem, but the programming syntax/whatever it is on this site is incredibly confusing, I don't know how I'd actually go about doing it. I figured I'd just find the spot on the page where the little letter is and replace that with the image code, but it seems the pages are built using heavily nested templates that I can't even begin to understand. Any help?--[[User:Treese|Treese]] ([[User talk:Treese|talk]]) 03:07, 5 January 2023 (UTC)
:Based on [[User:Zippy|Zippy]]'s work at {{tl|Creaturelookup_b}}, I added an "image" parameter to {{tl|creaturelookup/0}}, which is what creature pages should all be using. See [[Dwarf]] and [[Cow]] for examples. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:37, 5 January 2023 (UTC)

=== Hotkeys/Menu navigation ===
Most key bindings and menus have changed. Should the article reflect a) only the old version, b) only the GUI version or c) both? For example, [[Bridge|bridges]] used to be built via {{k|b}} -> {{k|g}}, but now it's in Place strucutures {{k|b}} -> Constructions {{k|n}} -> Bridge {{k|b}}. What should be written in the article? Currently, it's {{k|b}} -> {{k|g}}. I ''think'' it should be only b), but I am not sure if there will be differences regarding hotkeys or menus between the premium version and the free version and then, c) would be the most appropriate option. --[[User:Prometherus|Prometherus]] ([[User talk:Prometherus|talk]]) 10:16, 22 December 2022 (UTC)

: Not sure. I wish the classic release soon --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 16:45, 22 December 2022 (UTC)
:: Are you Toady's herald? Looks like it was just released! [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:18, 22 December 2022 (UTC)
:: And our questions are answered, the old hotkeys seem to have been thrown out. Part of me is disappointed (useless muscle memory) but also relieved (unified UI for both versions is good in general and for the wiki). [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:25, 22 December 2022 (UTC)
::: According to info, in a sort of 'demo version' at that. I'll wait a little while longer, for myself.[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 18:22, 22 December 2022 (UTC)
::::It's unlikely that keybindings in it will change significantly. My vote is that we should include information for both premium and classic, everywhere. Hopefully the keybindings are not different between versions. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 18:26, 22 December 2022 (UTC)
:::Shouldn't it be based on the 50 or what verion the article is written for? [[User:Dominick|Dominick]] [[User_talk:dominick|(TALK)]] 18:42, 22 December 2022 (UTC)
:::: The keybindings seem to be consistent between versions, (haven't checked exhausitvely, but since the menu layout is the same I think it is a good assumption). Should also keep in mind/consider that not all actions have keybindings. An option would be write 'Click on the <Example Text> icon or press {{k|E}}' [[User:Koos|Koos]] ([[User talk:Koos|talk]]) 23:14, 23 December 2022 (UTC)

=== Removed features & concepts ===

Since they're removed concepts, I've set [[Room]] to be a redirect for [[DF2014:Room]] and created [[Template:Activity zones]] for the nav bar bedrooms, etc, and made the necessary changes to [[Bedroom]] for it. Is this the correct approach, before I go on much further? (also a note, if it is, then [[Template:v50_rooms]] probably needs to be deleted) I also imagine that considering the number of changes in the interface, that things like [[Adventure mode]] and related pages might best be truncated to "not in 50.03" and when it does make it across, being more deliberately brought over in pieces? [[User:HawkOwl|HawkOwl]] ([[User talk:HawkOwl|talk]]) 06:23, 23 December 2022 (UTC)

:Usually it is marked with [[Template:Removed_feature]]. For example: [[Dipscript]] or [[Party]]. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:45, 23 December 2022 (UTC)

:: Ah, that's fair. Should that be mentioned in [[Dwarf_Fortress_Wiki:Versions#Redirects]]? [[User:HawkOwl|HawkOwl]] ([[User talk:HawkOwl|talk]]) 10:03, 23 December 2022 (UTC)

:::I think the redirect policy mostly had in mind things that were removed a ''long'' time ago, like [[Tax collector]] and [[Economy]] (and the latter actually has a stub page as well). I guess we could clarify. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:34, 23 December 2022 (UTC)

:::: The "current" redirects also cause the version box to incorrectly show that the current version has a page - e.g. [[23a:Cave_river]] shows a v50.04 version, but it's just a redirect back to that version. Similarly, what should happen to redirects like [[Clothes maker]], where a concept has evolved? It currently goes to [[23a:Clothes maker]] - that's correct if the user is trying to look up a very old concept, but if a new user is looking for "how to make clothes", they should be directed to [[Clothier]]. --[[User:Danny252|Danny252]] ([[User talk:Danny252|talk]]) 12:16, 26 December 2022 (UTC)

:::: One should be careful with cv redirects. Most that were recently adjusted were unused plural forms (that should probably be deleted) but few like [[Crown]] needed that for backward compatibility. Removing the [https://dwarffortresswiki.org/index.php?title=Crown&type=revision&diff=279966&oldid=219482 cv part] means the the link on [[v0.31:Tilesets]] is now broken. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 22:30, 26 December 2022 (UTC)

:::::If [[v0.31:Tilesets]] is about v0.31, it should not be using "main:" in its links - ''all'' of those links are going to pages about v50, not v0.31, regardless of whether the target is a redirect or not. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:37, 26 December 2022 (UTC)
:::::: You right, I removed it. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 17:55, 27 December 2022 (UTC)

Crown cv redir issue is now fixed, I believe. As goes with such cases where one can simply revert the troublesome edit, unless I've mistepped, myself? [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 23:52, 26 December 2022 (UTC)
:Both [https://dwarffortresswiki.org/index.php?title=Crown&diff=prev&oldid=280026] and [https://dwarffortresswiki.org/index.php?title=Crown&diff=prev&oldid=279966] should not have had any effect, because "cv" is an alias to the main namespace now, just like "main". Proof: [[Crown]], [[cv:Crown]], [[main:Crown]]. It's possible caching is coming into play here, although I purged the redirect cache after making that alias change earlier this month... —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:02, 27 December 2022 (UTC)

I think there have been some changes not captured, but as a newb, I'm afraid to edit the page(s). A good example is Strawberry. I'm playing the Steam version right now and Strawberry plants are "not relevant to brewing" in Labor > kitchen > veg / fruit / leaves. Unless I'm mistaken and need to process them? Another example is the trade caravan = it seems the 3 square pathing no longer happens; it's just yak(s). 12:31, 28 December 2022 (UTC) 12:29, 28 December 2022 (UTC)
:Strawberries should be brewable according to the Raws.
:Trade wagons has been modified in v50. The first wagons will arrive at the same time your fort is becoming a barony. Until then, it's only pack animals and stairs are indeed fine. The [[Trading]] page needs a huge rework anyway... I'll try to do that next week. --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 13:40, 2 January 2023 (UTC)

<s>As far as I can tell, none of the workshop buildings in v50 have blocking tiles any more. There's a comment to the like in data/vanilla/vanilla_buildings/objects/building_custom.txt that says this "[BLOCK:1:0:0:0] workbenches no longer block". Hesitant to update that template as I'm not sure if it's referenced for all of the old versions too. </s> [[User:AndrielChaoti|AndrielChaoti]] ([[User talk:AndrielChaoti|talk]]) 05:54, 29 December 2022 (UTC)
: A new template has been created: {{tl|V50 workshop}} --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 13:40, 2 January 2023 (UTC)
::Thanks! In general, I would like to delegate the switching responsibility to the template (like how {{tl|creaturelookup/0}} works), but in cases where the parameters diverge significantly like with workshops, it could make sense to make an entirely new template. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:40, 3 January 2023 (UTC)

=== creature infobox prototype (moved) ===

Check it out, I made a temporary template and added it to the [[cow]]s page. Now it shows the sprites (but not the zombified versions yet). I wanted to show everyone a prototype of what v50 creature infoboxes should look like. Or at least something similar to it. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 19:11, 27 December 2022 (UTC)
:Hi, I'm new to editing wikis but I have done a bit of work with sprite sheets and I've been going through the DF data files to find the different graphics hoping to help with the animal pages. I've thrown together a template with grass and a few nature sprites (plants, a tree, and a rock) for size reference but I'm unsure how large the 'display' tiles in the middle of the template should be to suit all animals. I can see in the sprite sheets that some land animals have an adult and child sprite, so two tiles. Others have a male, female, and child, but after seeing you include the zombie cows I'm unsure if I should make it twice the size to add them too. Alternatively, I could grab some tiles from the haunted biomes for the zombie animals and make a separate template for a side-by-side comparison. Either way, let me know if this helps. I'd like to help with other graphics too as we add the premium tilesets but the animals seemed the easiest to tackle with me being new to wiki editing. ~~[[User:UristTheSeventh|UristTheSeventh]] ([[User talk:UristTheSeventh|talk]])
::@Zippy, I am a bit perplexed about the purple cows. Why do we need a zombified version of creatures on every page?
::@UristTheSeventh, we can use all the help. Maybe post an example, so that we can have something to compare and contrast.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 11:49, 3 January 2023 (UTC)
:::@Jan Here are the examples:
:::[[File:Creature template.png]] [[File:Armadillo.png]] [[File:Seagull.png]]
:::It'll need to be wider or arranged differently for different creatures with more that two sprites or for multi-tile creatures. I can also do an aquatic and air themed template for swimming and flying creatures. ~~[[User:UristTheSeventh|UristTheSeventh]] ([[User talk:UristTheSeventh|talk]])
::::Looks nice, like the metal template. There are several people working on updating the graphics you should talk more among yourselves. Best I can offer is that I width wise I am hoping to go up to 200px for infoboxes.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 01:13, 5 January 2023 (UTC)
:::: We don't exactly ''need'' a zombie sprite on each page. I added it because it was... there. I was also hoping to get some opinions on it anyway since that infobox is a visual prototype, and not a final choice. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 03:28, 6 January 2023 (UTC)

===Furniture Infobox===
{{Quality|Unrated}}
{{v50_furniture|name=Bed
|graphic=[[File:bed_sprite_prototype.png]]
|tile=Θ|col=6:0:0
|wood=y
|rooms=
* [[Bedroom]]
* [[Barracks]]
* [[Dormitory]]
|value=10}}
I made a v50 furniture template prototype. I tested this on Firefox, Chrome and Microsoft Edge/Internet Explorer and it looks fine on all of them. I hope this is good enough to be the official thing, unless I'm missing something. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 03:28, 6 January 2023 (UTC)
{{clear}}

=== When do we remove the migration note on specific pages? ===

At what point can we remove the "this page was auto migrated from v47" warning? There are a bunch of small pages that are more or less accurate, if I've reviewed them, can I go ahead and remove the warning? [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 23:33, 1 January 2023 (UTC)
:Yes, feel free to remove it if you think all content is accurate. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:31, 2 January 2023 (UTC)

=== Any info on fixing "creature description not found?" ===

I see this issue on most creature pages, it seems to be due to a lookup that's not currently functioning? Cows interestingly doesn't have this issue but I couldn't figure out how to recreate whatever fix it's editor did. --[[User:Yallendallis|Yallendallis]] ([[User talk:Yallendallis|talk]]) 00:22, 3 January 2023 (UTC)
:That is the missing raws issue described above. Cow was fixed by the addition of [[cow/raw]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:28, 3 January 2023 (UTC)
::Ah makes sense, not fully used to the language of wikis yet so I read over it while looking. To put this bit of questioning to rest for any future readers, is it correct that it's fine to update any raws manually, though it will be done automatically at some point? --[[User:Yallendallis|Yallendallis]] ([[User talk:Yallendallis|talk]]) 07:48, 3 January 2023 (UTC)
:::Yes. I'm circling back to work on a script right now, so not much point in doing it if you're reading this. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:57, 4 January 2023 (UTC)
:::This should be fixed now. If you continue to see pages with problems, you can try [https://www.mediawiki.org/wiki/Manual:Purge purging the cache]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:59, 4 January 2023 (UTC)

=== Adventurer Mode related sections ===

The topic has already been discussed [[#Removed features & concepts|above]], but I don't see a clear line on what to do with article sections that mention Adventurer Mode. Like for example in [[Butcher#Adventurer_mode|Butcher]].

'''a) Truncate''' or '''b) leave in place with a mention''' that the mode is not yet present IG but will be added in a future update?

Personally I think option b) is better, because I think it's silly to undo some work just to reintroduce it a few weeks later, with the necessary corrections. Even if a copy/paste of a previous version takes ~15 seconds, considering the number of articles that need to be corrected, it would be a bit of a waste of time.--[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 14:22, 3 January 2023 (UTC)

== Toggleable image ==

Any objections/comments to using this template for now for toggling between classic and premium images? I'd probably rename it to "Template:Premium-classic thumb image". I'm sure someone can come up with a better UI eventually, but should be easy to migrate at that point. I also think we should use the same customtoggle class for this and for the infobox. [[User:NiftyManiac|NiftyManiac]] ([[User talk:NiftyManiac|talk]]) 23:12, 1 January 2023 (UTC)

{{User:NiftyManiac/Sandbox/TemplateDualImage|
premium=File:Quickstart-finder.png|
classic=File:Quickstart-finder-partial.png
}}

{{User:NiftyManiac/Sandbox/TemplateDualImage|
premium=File:Quickstart-finder.png|
classic=File:Quickstart-finder-partial.png|
caption=My caption|
width=100px
}}

:This looks nice to me! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:30, 2 January 2023 (UTC)

: Good initiative. From the top of my head:
:* I suggest using a shorthand, no one wants to type 'Premium-classic thumb image'.
:* If we end up using toggle for infoboxes (not sure where we headed there), then I agree definitely same custom toggle class should be used for all, thus allowing to switch premium-classic view on the whole page at a click.
:* The button part on a separate row isn't pretty, creating a lot of dead space that can be used by the text. Are we set on the label 'toggle ascii'? Classic isn't Ascii per se, maybe we can use a 'toggle' with a tooltip {{tooltip|for example|does bla bla bla}}, or maybe we can get rid of the text and have a smaller icon button ([[User:Jan/sandbox#Metal_example|two examples]]).
: I hope that helps. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 11:21, 2 January 2023 (UTC)

:: I added [[Template:Dual image]] with some of your suggestions. Agree that it's not super pretty, feel free to try something different.

::* I put the toggle in the caption mostly because I gave up on trying to make a more sophisticated replacement for the default thumb image behavior, I'm sure someone with better wiki-fu could put together something more intelligent.
::* I cut the text down to just "Toggle"; I think the best solution would be a small graphic showing the old and new dwarf icons with arrows between them. [[User:NiftyManiac|NiftyManiac]] ([[User talk:NiftyManiac|talk]]) 19:21, 2 January 2023 (UTC)

{{Dual image|
premium=File:DFwiki5by53by3farm.png|
classic=File:Quickstart_layout_3.png|
width=100px|
caption=A 5x5 room with a 3x3 farm plot
}}
::: I updated the layout, now it should look just like a regular image thumb. I didn't had time to test it, if it doesn't work for you or you don't like it just revert the last change. cheers. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 21:46, 2 January 2023 (UTC)
::::I don't know which part of this talk page to put this, but I added the ability to add icons to the v50 workshops template. Leaving the icon part blank will not break the template in any way. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 09:47, 3 January 2023 (UTC)
{{clear}}
==Creature List Now Supports Graphics!==
I wasn't easy, but I made new templates so the [[Creature]]s page now supports both graphics sprites ''and'' ASCII tiles. Allow me to show you:

{{v50_creaturecurrent_table_head}}
{{v50_creaturecurrent table row|graphic=[[File:dwarf_sprite.png]]|name=[[Dwarf]]|symbol=☺|color=3:0:0|playable=Fort, Adv|hostile=No|food=No|size=60,000|value=Not tameable|biome=[[Mountain halls]], [[Fortress|dwarf fortress]]es, [[hillock]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:elf_sprite.png]]|name=[[Elf]]|symbol=e|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=60,000|value=Not tameable|biome=[[Forest retreat]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:human_sprite.png]]|name=[[Human]]|symbol=U|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=70,000|value=Not tameable|biome=[[Town]]s and cities|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:goblin_sprite.png]]|name=[[Goblin]]|symbol=g|color=7:0:0|playable=Adv|hostile=Usually1|food=No|size=60,000|value=Not tameable|biome=[[Dark fortress]]es and [[dark pit]]s|note=Snatchers2}}
{{v50_creaturecurrent table row|graphic=[[File:kobold_sprite.png]]|name=[[Kobold]]|symbol=k|color=6:0:0|playable=Adv|hostile=Usually1|food=No|size=20,000|value=Not tameable|biome=Caves|note=Skulking race}}
|}

Oh wait, there's a bonus. You can also modify the background color of the box the sprites go in. I added that to make possibly-hard-to-see-otherwise sprites more easy to see - depending on the colors it has. Allow me to demonstrate.

{{v50_creaturecurrent_table_head}}
{{v50_creaturecurrent table row|graphic=[[File:dwarf_sprite.png]]|bgcolor=#829ccc|name=[[Dwarf]]|symbol=☺|color=3:0:0|playable=Fort, Adv|hostile=No|food=No|size=60,000|value=Not tameable|biome=[[Mountain halls]], [[Fortress|dwarf fortress]]es, [[hillock]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:elf_sprite.png]]|bgcolor=#c7dfc0|name=[[Elf]]|symbol=e|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=60,000|value=Not tameable|biome=[[Forest retreat]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:human_sprite.png]]|bgcolor=#c7dfc0|name=[[Human]]|symbol=U|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=70,000|value=Not tameable|biome=[[Town]]s and cities|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:goblin_sprite.png]]|bgcolor=#dfc0c0|name=[[Goblin]]|symbol=g|color=7:0:0|playable=Adv|hostile=Usually1|food=No|size=60,000|value=Not tameable|biome=[[Dark fortress]]es and [[dark pit]]s|note=Snatchers2}}
{{v50_creaturecurrent table row|graphic=[[File:kobold_sprite.png]]|bgcolor=#dfc0c0|name=[[Kobold]]|symbol=k|color=6:0:0|playable=Adv|hostile=Usually1|food=No|size=20,000|value=Not tameable|biome=Caves|note=Skulking race}}
|}

To change the background color, add <code><nowiki>|bgcolor=COLOR</nowiki></code> segment after the <code><nowiki>|graphic</nowiki></code> part. You can use color names or HTML hex color codes. I added this to the v50 creatures page, but at this time, I only added the first five creatures I just displayed. It's gonna take a while to find ALL of those creature sprites. I hope a lot of people help out on that one. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 05:29, 5 January 2023 (UTC)

:Thanks, looks nice! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:44, 5 January 2023 (UTC)
:Nice stuff, took the quick liberty to change the padding-left -> text-align to make all the sprites center aligned relative to each other :) Sweet work --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 17:41, 5 January 2023 (UTC)
:: Good work indeed. One minor issue, is that all the sprites have different sizes, which sometimes create slight variation in table row height. Consider using capping the image size vertically for example <code><nowiki>[[File:dwarf_sprite.png|x32px]]</nowiki></code>--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:15, 5 January 2023 (UTC)
:: Also often in such tables people want to click on the image to go for the specific entry, and often will try to click on the very first thing they see in line the thumb image, but currently that will take them to the file page. Consider adding link parameter for example: <code><nowiki>[[File:dwarf_sprite.png|x32px|link=dwarf]]</nowiki></code> [[File:dwarf_sprite.png|x32px|link=dwarf]] or no link at all <code><nowiki>[[File:dwarf_sprite.png|x32px|link=]]</nowiki></code> [[File:dwarf_sprite.png|x32px|link=]] --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:24, 5 January 2023 (UTC)
::: I mean... Yeah, I could do that. I think that lessens the quality of the sprite a bit because it makes edges blurry, but either way is fine. I could have sworn I added a link for all those images the first time. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 03:23, 6 January 2023 (UTC)
::::Since we are adding pixel art sprites to the website it might be convincing to add a global class like .sprite or .pixel-image that uses the CSS attribute `image-rendering: pixelated;` in order to prevent blurryness when scaling the image up/down. Just a thought --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 09:40, 6 January 2023 (UTC)
:::::Are we able to attach classes directly to images? If so, we can probably attach inline styles directly as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:52, 6 January 2023 (UTC)
::::::Looks like (without an extension) MediaWiki only supports classes on images: [[File:dwarf_sprite.png|x32px|class=pixelated]] and not styles: [[File:dwarf_sprite.png|x32px|style="image-rendering: pixelated;"]] it just treats it as alt text it looks like? Wrapping it in a div works and demonstrates the difference: <div style="image-rendering: pixelated;display:inline;">[[File:dwarf_sprite.png|64px]]</div> [[File:dwarf_sprite.png|64px|inline]]. Speaking from experience, however, image-rendering needs a browser specific prefix in certain browsers (safari, for example) in order to work properly. I'm not entirely sure what the best "MediaWiki" practice is for adding something like this but I would assume it's a simple class in common.css for now. --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 17:17, 6 January 2023 (UTC)
:::::::Ah, yeah, you are correct, I should have checked https://www.mediawiki.org/wiki/Help:Images. I'd be fine adding a class like that to common.css. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:27, 6 January 2023 (UTC)
::::::::Great, in that case if no one is opposed we can add `.game-sprite` or something like that? See below for the CSS, the order of the attributes is relevant. --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 18:23, 6 January 2023 (UTC)
<pre>/* Used for pixel-art images from the game so they can be resized and maintain crisp pixel edges. */
.game-sprite {
image-rendering: -webkit-optimize-contrast;
image-rendering: crisp-edges;
image-rendering: pixelated;
}</pre>
:::::::::So... you guys think each creature page should show the main sprite(s) alone, or should it show the baby versions alongside them? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 08:37, 8 January 2023 (UTC)
{{clear}}
=== Graphics in Skill Infoboxes ===
{{v50_skill
| color = 7:0
| graphic = [[File:miner_sprite_icon.png]]
| skill = Miner
| profession = Miner
| job name = [[Mining]]
| tasks =
* [[Dig]]
| attributes =
* Strength
* Toughness
* Endurance
* Willpower
* Spatial Sense
* Kinesthetic Sense}}I've made yet another visual prototype for skills. In other words, we can put sprites of matching dwarves (and possibly humans, elves, goblins, etc.) at the top of infoboxes. If multiple images are put up there, that can mess up the alignment, but don't worry, Zippy thought of that. <code><nowiki>|graphicmargin</nowiki></code> can added, and a percentage or a "px" number can be placed in that parameter to fix it. If you leave said parameter out, the alignment will default to about 42% from the left. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 06:06, 7 January 2023 (UTC)
<pre><nowiki>
{{v50_skill
| color = 7:0
| graphic = [[File:miner_sprite_icon.png]]
| graphicmargin = (OPTIONAL)
| skill = Miner
| profession = Miner
| job name = [[Mining]]
| tasks =
* [[Dig]]
| attributes =
* Strength
* Toughness
* Endurance
* Willpower
* Spatial Sense
* Kinesthetic Sense}}
</nowiki></pre>
::Not sure I understand the alignment issue, can you not put text-align: center on the parent table element instead of messing with explicit margins? As another sidenote, should we continue to be naming all of these templates v50_x, I find that a bit confusing. Why not just edit the main templates with the additional information. Loving all the new templates though nice work Zippy :) --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 11:43, 7 January 2023 (UTC)
:::No, text-align doesn't work with images and divs. That just works for text. When it comes to images, you got to put a little "finesse" on the CSS with those. As for editing the classic templates with the new info, it doesn't always work that way with ''every'' template. Lethosor I think ''did'' update the creature infobox template in the way you mentioned. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 08:37, 8 January 2023 (UTC)
:::: You can use something like this too automatically handle that--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 08:56, 8 January 2023 (UTC)
{|
|-
|<div style="width:200px; display:flex; background-color:#eaecf0;">
[[File:miner_sprite_icon.png|center]]
<div>
|<div style="width:200px; display:flex; background-color:#eaecf0;">
[[File:miner_sprite_icon.png|center]] [[File:miner_sprite_icon.png|center]]
<div>
|<div style="width:200px; display:flex; background-color:#eaecf0;">
[[File:miner_sprite_icon.png|center]] [[File:miner_sprite_icon.png|center]] [[File:miner_sprite_icon.png|center]]
<div>
|}

User talk:BarelyCreative

2023-01-08T08:46:21Z

Jan:

== Graphic set ==

It is easy to get lost on this wiki, even after years here I still discover new dark corners I wasn't aware of ;) The way I see it, currently we have:
* [[Modding]] as general landing page.
* Beginners [[modding guide]]
* Various [[Token]] pages for in-depth parameter reference
* With various pages that provide more in-depth usage explanation like [[Reactions]].

For graphics, I believe that currently [https://dwarffortresswiki.org/index.php?title=Graphics&type=revision&diff=284350&oldid=282626 this info] might be best suited to [[Graphic set]]. Unless you choose to consolidate stuff (Personally, I welcome experimentation though it is hard to do so here due to lack of feedback) --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 11:52, 7 January 2023 (UTC)

:That's fair, I definitely am still uncertain how that information should be displayed. It seems to me that because graphics tokens are only really useful as part of a multi-line set [[Reaction]] or [[Syndrome]] would the best examples to follow for a graphics page. Additionally, feedback from other modders after I had added all that information to the [https://dwarffortresswiki.org/index.php?title=Graphics_token&oldid=284218 previous Graphics Tokens] page was that they ignored the page because its title seemed to imply it wouldn't have any instructions.
:For this reason, I don't love the idea of linking to a page like [[Graphics token]] or [[Graphic set]], the latter of which I completely overlooked even while actively editing the wiki. Although I can see how my first try to resolve this made the pages more confusing rather than less.

:I think it would be good to change [[Graphics]] into a landing page with:
:* a "for/see" to a Premium-related tokens + how-to page (maybe [[Graphics token]]).
:* some "for/see"s to the Classic-related reference pages (like [[Graphic set]], [[Tileset]]).
:* a simple explaination of what base-game graphics are.
:* how-to's for installing new graphics in both versions.
:I'll put that in the talk pages of both Graphics and Graphics token so I'm not making the decision unilaterally. --[[User:BarelyCreative|BarelyCreative]] ([[User talk:BarelyCreative|talk]]) 06:12, 8 January 2023 (UTC)

:: Seems like you given the topic some thought and it would be nice if the pages are updated by a modder.
:: The only thing I can offer is that the difference between Premium and Classic is that the former comes with an official graphic set(which is kinda a mod in it self that resides in vanilla rather than mod folder). Otherwise they both can use the exact same tokens and methods to change the visuals in game.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 08:46, 8 January 2023 (UTC)

Mod

2023-01-07T17:23:05Z

Jan: /* Updating/missing Mods */

{{For/see|using mods and their basic structure|[[modding]] about making mods}}

A '''mod''' (short for modification) is an alteration of the game and the objective of modding. Modifications can range from small tweaks to complete overhauls.

== Downloading Mods ==

Mods can be acquired using the [https://steamcommunity.com/app/975370/workshop/ steam workshop] (if using Steam version), a manual download from [[Bay 12 Forums]] or third party websites (like [https://dffd.bay12games.com/ DFFD]), or by [[Modding|creating]] one yourself.

Users of the Steam version can subscribe to mods on Steam Workshop, once the download is complete they will be available when creating a new world automatically. Otherwise, manually download the mod, then place the mod zip file or the unzipped mod folder into the Dwarf Fortress [[mod folder]] (if this folder doesn't exist, you can create it.) You can have more than one mod in the mod folder, including different version of the same mod. The game will detect all mods that are properly made in this folder and let the user select which mods to play (see bellow.)

== Enabling/Installing Mods ==
[[File:Ui-p-mod-selection.png|thumb|world generation mod menu]]

Mods are enabled per per world. When [[World generation|creating a world]] and choosing its initial parameters, if you have a mod available, there should be a '''Mods''' button at the bottom of the screen. Pressing this will let you select which mods you'd like to enable and what the load order should be. You should put mods at the end of the mod list after the vanilla objects if you don't have any further information, so that they can reference vanilla objects after those are loaded.

Something mods might depend on other mods which have to be loaded before, refer to mod description for information about that.

<div class="" style="padding: 0.8em 1em; margin: 0.5rem 0; background: #fcf8e3; border-left: 5px solid #aa6708;">
* Mods are enabled per world and can not be disabled afterwards, however, it is possibly to manually modify the game file as we did in previous versions by applying the mods directly to <code>[[Game folder|<Dwarf Fortress>]]/data/vanilla</code>. Be ware this method has the disadvantage of being a permanent change for all worlds and may break your game.

* Unlike the previous versions of Dwarf Fortress, mods no longer live inside [[save]] and must be installed on every computer where saves using those mods are going to be loaded. Once a world is created that uses mods, the game will copy the relevant mods to the <code>[[Game folder|<Dwarf Fortress>]]/data/installed_mods</code> folder. That is the version that the game actually uses. Installed mods will now show in the main menu->mods screen as 'installed'.
</div>

== Updating/missing Mods ==
[[File:mod_version_v50_prompt.png|thumb|possible update message]]
If a [[save]] is using a mod that's been updated, and is currently using an older version of that mod, the player will be prompted about this when a save is loading. When this happens, you have the choice of simply updating the mod, updating ''all'' mods at once, continuing to use the older version of the mod in question without updating, selecting the previous task but not updating ''any'' possibly outdated mods or simply returning to the title screen.

If a save is using a mod that is missing, the player will be prompted about this when a save is loading. When this happens, try to reinstall the mods. Either by manually downloading them again or in case of Steam Workshop making sure you are subscribed and if you do by unsubscribing and subscribing again.

== Modding ==

Dwarf Fortress supports mods in the form of new objects and tiles. Each mod is a zip file or unzipped folder with the required format (see below.)

=== Mod Format===

Mods contain an info.txt file and either an "objects" folder or a "graphics" folder (or both.) All of the vanilla objects in the game too use this format. Your mod folder should look something like this:

[[File:Folder-orange.svg|20px|link=]] Mod Name
├ [[File:Text-x-generic.svg|20px|link=]] info.txt
├ [[File:Text-x-generic.svg|20px|link=]] preview.png
├ [[File:Folder.svg|20px|link=]] objects
└ [[File:Folder.svg|20px|link=]] graphics

=== Mod info ===
{{main|Mod info token}}

Each mod must have a <code>info.txt</code> at the root of your mod folder. It has a few fields defining basic metadata information about the mod and can be edited using any text editor (like notepad++). See Example:

{{code|
[ID:wiki_example]
[NAME:Wiki Example Mod]
[NUMERIC_VERSION:5001]
[DISPLAYED_VERSION:50.01]
[EARLIEST_COMPATIBLE_NUMERIC_VERSION:5001]
[EARLIEST_COMPATIBLE_DISPLAYED_VERSION:50.01]
[AUTHOR:Dwarf Fortress Wiki]
[DESCRIPTION:This is an example mod. This text shows up in-game.]

[STEAM_TITLE:Wiki Example Mod]
[STEAM_DESCRIPTION:This text shows up on Steam Workshop.]
[STEAM_TAG:mod]
[STEAM_KEY_VALUE_TAG:test:stuff]
[STEAM_METADATA:metadata test]
[STEAM_CHANGELOG:Made some changes. Shown in 'Change Notes' tab.]

[STEAM_FILE_ID:#########]
}}

Only <code>ID</code> and <code>NAME</code> are required to appear in the in-game mod menu.

STEAM tags are only used by Steam.
* The <code>STEAM_FILE_ID</code> used to identify the mod in the Workshop. This is automatically managed when uploading to Steam the first time. And required if you wish to update an existing Steam Workshop mod.
* The <code>STEAM_TAG</code> and <code>STEAM_KEY_VALUE_TAG</code> are used by Steams search engine and the categorization. You can use as many entries you want, use a separate tag for each one.
* You can also create a thumbnail for your mod by creating an image called <code>preview.png</code> in the same level as your info.txt file. This image will become the thumbnail when the mod is uploaded to steam workshop. The image should be less than 1MB in size.

=== Objects and graphics folder ===

At the root of your mod folder you can have a <code>objects\</code> and <code>graphics\</code> folder, this is where all the [[raw file]]s or [[graphics]] goes (exactly the same as objects from previous versions of Dwarf Fortress) allowing you to tweak or add new content for the game. It's beyond the scope of this short guide to go into what specific tags do, but the vanilla objects and previous mods by members of the community will give you plenty of examples to work with. See: [[modding]].

The graphics filenames are not important, furthermore they can be arbitrarily nested into other sub-folders to help you organize your mod content.

== Publishing mods ==

There are two official platforms for publishing ''Dwarf Fortress'' mods, recommended because it's easy for people to find them there. These are [https://steamcommunity.com/app/975370/workshop/ Steam Workshop] and [https://dffd.bay12games.com/ the Dwarf Fortress File Depot (DFFD)].

=== Publishing on Steam Workshop ===

To upload a mod to Steam Workshop, you need to add STEAM tags to the <code>info.txt</code> file (see above.) Afterward, you put the unzipped mod folder in the "<code>mods/mod_upload</code>" folder. Then select Mods from the title menu, and upload your mods using the button you'll see there. Other Steam users will be able to subscribe to your mod immediately once it is uploaded.

Once the upload process is completed successfully, you'll find a <code>[STEAM_FILE_ID:#########]</code> appended to your info.txt. Make sure this entry is included for future uploads if you want to make changes to your mod and have it overwrite the existing entry on the workshop. Otherwise you'll create a new entry every time you upload.

=== Publishing on DFFD ===

In addition to Steam Workshop, it is recommended you upload your mod to DFFD. This allows people who play ''[[Classic|Dwarf Fortress Classic]]'', or ''[[Premium]]'' via Itch.io, to also download and play your mod. To publish/upload a file to DFFD you first need to create an account.

For legal reasons, mods that contain graphics derived from the ''Premium'' graphics should not be uploaded outside Steam Workshop. For this reason, you might want to separate your mod into two parts: the first without graphics, which is uploaded to both DFFD and Steam Workshop, and the second with ''only'' the graphics, uploaded only to Workshop. Of course, this is not an issue if your graphics are not based off the ''Premium'' ones.

[[Category:Modding]]

Mod

2023-01-07T17:22:45Z

Jan: /* Updating/missing Mods */

{{For/see|using mods and their basic structure|[[modding]] about making mods}}

A '''mod''' (short for modification) is an alteration of the game and the objective of modding. Modifications can range from small tweaks to complete overhauls.

== Downloading Mods ==

Mods can be acquired using the [https://steamcommunity.com/app/975370/workshop/ steam workshop] (if using Steam version), a manual download from [[Bay 12 Forums]] or third party websites (like [https://dffd.bay12games.com/ DFFD]), or by [[Modding|creating]] one yourself.

Users of the Steam version can subscribe to mods on Steam Workshop, once the download is complete they will be available when creating a new world automatically. Otherwise, manually download the mod, then place the mod zip file or the unzipped mod folder into the Dwarf Fortress [[mod folder]] (if this folder doesn't exist, you can create it.) You can have more than one mod in the mod folder, including different version of the same mod. The game will detect all mods that are properly made in this folder and let the user select which mods to play (see bellow.)

== Enabling/Installing Mods ==
[[File:Ui-p-mod-selection.png|thumb|world generation mod menu]]

Mods are enabled per per world. When [[World generation|creating a world]] and choosing its initial parameters, if you have a mod available, there should be a '''Mods''' button at the bottom of the screen. Pressing this will let you select which mods you'd like to enable and what the load order should be. You should put mods at the end of the mod list after the vanilla objects if you don't have any further information, so that they can reference vanilla objects after those are loaded.

Something mods might depend on other mods which have to be loaded before, refer to mod description for information about that.

<div class="" style="padding: 0.8em 1em; margin: 0.5rem 0; background: #fcf8e3; border-left: 5px solid #aa6708;">
* Mods are enabled per world and can not be disabled afterwards, however, it is possibly to manually modify the game file as we did in previous versions by applying the mods directly to <code>[[Game folder|<Dwarf Fortress>]]/data/vanilla</code>. Be ware this method has the disadvantage of being a permanent change for all worlds and may break your game.

* Unlike the previous versions of Dwarf Fortress, mods no longer live inside [[save]] and must be installed on every computer where saves using those mods are going to be loaded. Once a world is created that uses mods, the game will copy the relevant mods to the <code>[[Game folder|<Dwarf Fortress>]]/data/installed_mods</code> folder. That is the version that the game actually uses. Installed mods will now show in the main menu->mods screen as 'installed'.
</div>

== Updating/missing Mods ==
[[File:mod_version_v50_prompt.png|thumb|possible update message]]
If a world is using a mod that's been updated, and is currently using an older version of that mod, the player will be prompted about this when a save is loading. When this happens, you have the choice of simply updating the mod, updating ''all'' mods at once, continuing to use the older version of the mod in question without updating, selecting the previous task but not updating ''any'' possibly outdated mods or simply returning to the title screen.

If a world is using a mod that is missing, the player will be prompted about this when a save is loading. When this happens, try to reinstall the mods. Either by manually downloading them again or in case of Steam Workshop making sure you are subscribed and if you do by unsubscribing and subscribing again.

== Modding ==

Dwarf Fortress supports mods in the form of new objects and tiles. Each mod is a zip file or unzipped folder with the required format (see below.)

=== Mod Format===

Mods contain an info.txt file and either an "objects" folder or a "graphics" folder (or both.) All of the vanilla objects in the game too use this format. Your mod folder should look something like this:

[[File:Folder-orange.svg|20px|link=]] Mod Name
├ [[File:Text-x-generic.svg|20px|link=]] info.txt
├ [[File:Text-x-generic.svg|20px|link=]] preview.png
├ [[File:Folder.svg|20px|link=]] objects
└ [[File:Folder.svg|20px|link=]] graphics

=== Mod info ===
{{main|Mod info token}}

Each mod must have a <code>info.txt</code> at the root of your mod folder. It has a few fields defining basic metadata information about the mod and can be edited using any text editor (like notepad++). See Example:

{{code|
[ID:wiki_example]
[NAME:Wiki Example Mod]
[NUMERIC_VERSION:5001]
[DISPLAYED_VERSION:50.01]
[EARLIEST_COMPATIBLE_NUMERIC_VERSION:5001]
[EARLIEST_COMPATIBLE_DISPLAYED_VERSION:50.01]
[AUTHOR:Dwarf Fortress Wiki]
[DESCRIPTION:This is an example mod. This text shows up in-game.]

[STEAM_TITLE:Wiki Example Mod]
[STEAM_DESCRIPTION:This text shows up on Steam Workshop.]
[STEAM_TAG:mod]
[STEAM_KEY_VALUE_TAG:test:stuff]
[STEAM_METADATA:metadata test]
[STEAM_CHANGELOG:Made some changes. Shown in 'Change Notes' tab.]

[STEAM_FILE_ID:#########]
}}

Only <code>ID</code> and <code>NAME</code> are required to appear in the in-game mod menu.

STEAM tags are only used by Steam.
* The <code>STEAM_FILE_ID</code> used to identify the mod in the Workshop. This is automatically managed when uploading to Steam the first time. And required if you wish to update an existing Steam Workshop mod.
* The <code>STEAM_TAG</code> and <code>STEAM_KEY_VALUE_TAG</code> are used by Steams search engine and the categorization. You can use as many entries you want, use a separate tag for each one.
* You can also create a thumbnail for your mod by creating an image called <code>preview.png</code> in the same level as your info.txt file. This image will become the thumbnail when the mod is uploaded to steam workshop. The image should be less than 1MB in size.

=== Objects and graphics folder ===

At the root of your mod folder you can have a <code>objects\</code> and <code>graphics\</code> folder, this is where all the [[raw file]]s or [[graphics]] goes (exactly the same as objects from previous versions of Dwarf Fortress) allowing you to tweak or add new content for the game. It's beyond the scope of this short guide to go into what specific tags do, but the vanilla objects and previous mods by members of the community will give you plenty of examples to work with. See: [[modding]].

The graphics filenames are not important, furthermore they can be arbitrarily nested into other sub-folders to help you organize your mod content.

== Publishing mods ==

There are two official platforms for publishing ''Dwarf Fortress'' mods, recommended because it's easy for people to find them there. These are [https://steamcommunity.com/app/975370/workshop/ Steam Workshop] and [https://dffd.bay12games.com/ the Dwarf Fortress File Depot (DFFD)].

=== Publishing on Steam Workshop ===

To upload a mod to Steam Workshop, you need to add STEAM tags to the <code>info.txt</code> file (see above.) Afterward, you put the unzipped mod folder in the "<code>mods/mod_upload</code>" folder. Then select Mods from the title menu, and upload your mods using the button you'll see there. Other Steam users will be able to subscribe to your mod immediately once it is uploaded.

Once the upload process is completed successfully, you'll find a <code>[STEAM_FILE_ID:#########]</code> appended to your info.txt. Make sure this entry is included for future uploads if you want to make changes to your mod and have it overwrite the existing entry on the workshop. Otherwise you'll create a new entry every time you upload.

=== Publishing on DFFD ===

In addition to Steam Workshop, it is recommended you upload your mod to DFFD. This allows people who play ''[[Classic|Dwarf Fortress Classic]]'', or ''[[Premium]]'' via Itch.io, to also download and play your mod. To publish/upload a file to DFFD you first need to create an account.

For legal reasons, mods that contain graphics derived from the ''Premium'' graphics should not be uploaded outside Steam Workshop. For this reason, you might want to separate your mod into two parts: the first without graphics, which is uploaded to both DFFD and Steam Workshop, and the second with ''only'' the graphics, uploaded only to Workshop. Of course, this is not an issue if your graphics are not based off the ''Premium'' ones.

[[Category:Modding]]

Reptile man

2023-01-07T17:19:38Z

Jan: no longer an animal person. not sure if it still tribal

{{migrated article}}
{{Quality|Unrated}}
{{Creaturelookup/0
|vary=no
|death=nobutcher
|contrib=no
}}
{{av}}
{{old}}
{{creaturedesc}}
'''Reptile men''' are one of the many underworld tribal [[creature]] living on any [[cavern]] level milling around piles of [[food|meat]] and [[leather|tanned hides]]. They stand at roughly the size of an adult [[dwarf]]. Despite being described as humanoid lizards, they are a separate species from the [[lizard man]].

Approach with caution, unless the tribe is friendly. If the tribe is friendly, feel free to take advantage of them in fine imperialistic tradition and steal all their resources without compensation. To check whether a tribe of reptile men is friendly, press {{k|u}} to view the unit list. The tribe will be labeled as either hostile or friendly. Alternatively, press {{k|v}} to view one of their profiles.

Like many underground races, the danger of reptile men is not to be found in their [[wood]]en [[weapon]]s, (although they can have proper [[metal]] ones), but in the substances found smeared on them. Reptile men use many [[syndrome|poisons]], some of which can be deadly. They will launch group attacks on your fort, and have the ability to swim through your reservoirs and launch amphibious assaults on your [[fisherdwarf|fisherdwarves]]. Despite their description, they do not possess the {{token|EVIL}} token and are not anymore malevolent than any other race of animal people.

If you ssspeak to a reptile man in [[adventure mode]], they will talk like thisss, becaussse of the {{token|LISP}} token.

Some [[dwarves]] [[Preferences|like]] reptile men for their ''terrifying features''.

{{D for Dwarf}}
The dwarves do not seem to worship this creature, and no mentions of them secretly ruling the world have been found in engravings. However, they can often be found in the deepest caverns nearest to the magma sea.

[[File:reptile_man_preview.jpg|thumb|300px|center|Not always as menacing as pictured.]]
{{gamedata}}
{{gamedata|title=Entity ([[civilization]]) Raws|{{raw|v50:entity_default.txt|ENTITY|SUBTERRANEAN_ANIMAL_PEOPLES}}}}
{{Creatures}}
{{Category|Humanoids}}
{{Category|Races}}

File:Ui-p-mod-selection.png

2023-01-07T17:17:31Z

Jan: Jan uploaded a new version of File:Ui-p-mod-selection.png

== Summary ==
UI screenshot, Steam edition v50.3
== Licensing ==
{{Non-free Dwarf Fortress Screenshot}}
[[Category:Interface images]]

Mod

2023-01-07T17:17:23Z

Jan:

{{For/see|using mods and their basic structure|[[modding]] about making mods}}

A '''mod''' (short for modification) is an alteration of the game and the objective of modding. Modifications can range from small tweaks to complete overhauls.

== Downloading Mods ==

Mods can be acquired using the [https://steamcommunity.com/app/975370/workshop/ steam workshop] (if using Steam version), a manual download from [[Bay 12 Forums]] or third party websites (like [https://dffd.bay12games.com/ DFFD]), or by [[Modding|creating]] one yourself.

Users of the Steam version can subscribe to mods on Steam Workshop, once the download is complete they will be available when creating a new world automatically. Otherwise, manually download the mod, then place the mod zip file or the unzipped mod folder into the Dwarf Fortress [[mod folder]] (if this folder doesn't exist, you can create it.) You can have more than one mod in the mod folder, including different version of the same mod. The game will detect all mods that are properly made in this folder and let the user select which mods to play (see bellow.)

== Enabling/Installing Mods ==
[[File:Ui-p-mod-selection.png|thumb|world generation mod menu]]

Mods are enabled per per world. When [[World generation|creating a world]] and choosing its initial parameters, if you have a mod available, there should be a '''Mods''' button at the bottom of the screen. Pressing this will let you select which mods you'd like to enable and what the load order should be. You should put mods at the end of the mod list after the vanilla objects if you don't have any further information, so that they can reference vanilla objects after those are loaded.

Something mods might depend on other mods which have to be loaded before, refer to mod description for information about that.

<div class="" style="padding: 0.8em 1em; margin: 0.5rem 0; background: #fcf8e3; border-left: 5px solid #aa6708;">
* Mods are enabled per world and can not be disabled afterwards, however, it is possibly to manually modify the game file as we did in previous versions by applying the mods directly to <code>[[Game folder|<Dwarf Fortress>]]/data/vanilla</code>. Be ware this method has the disadvantage of being a permanent change for all worlds and may break your game.

* Unlike the previous versions of Dwarf Fortress, mods no longer live inside [[save]] and must be installed on every computer where saves using those mods are going to be loaded. Once a world is created that uses mods, the game will copy the relevant mods to the <code>[[Game folder|<Dwarf Fortress>]]/data/installed_mods</code> folder. That is the version that the game actually uses. Installed mods will now show in the main menu->mods screen as 'installed'.
</div>

== Updating/missing Mods ==
If a world is using a mod that's been updated, and is currently using an older version of that mod, the player will be prompted about this when a save is loading. Causing a message like the following to appear: 
[[File:mod_version_v50_prompt.png]]

When this happens, you have the choice of simply updating the mod, updating ''all'' mods at once, continuing to use the older version of the mod in question without updating, selecting the previous task but not updating ''any'' possibly outdated mods or simply returning to the title screen.

If a world is using a mod that is missing, the player will be prompted about this when a save is loading. When this happens, try to reinstall the mods. Either by manually downloading them again or in case of Steam Workshop making sure you are subscribed and if you do by unsubscribing and subscribing again.

== Modding ==

Dwarf Fortress supports mods in the form of new objects and tiles. Each mod is a zip file or unzipped folder with the required format (see below.)

=== Mod Format===

Mods contain an info.txt file and either an "objects" folder or a "graphics" folder (or both.) All of the vanilla objects in the game too use this format. Your mod folder should look something like this:

[[File:Folder-orange.svg|20px|link=]] Mod Name
├ [[File:Text-x-generic.svg|20px|link=]] info.txt
├ [[File:Text-x-generic.svg|20px|link=]] preview.png
├ [[File:Folder.svg|20px|link=]] objects
└ [[File:Folder.svg|20px|link=]] graphics

=== Mod info ===
{{main|Mod info token}}

Each mod must have a <code>info.txt</code> at the root of your mod folder. It has a few fields defining basic metadata information about the mod and can be edited using any text editor (like notepad++). See Example:

{{code|
[ID:wiki_example]
[NAME:Wiki Example Mod]
[NUMERIC_VERSION:5001]
[DISPLAYED_VERSION:50.01]
[EARLIEST_COMPATIBLE_NUMERIC_VERSION:5001]
[EARLIEST_COMPATIBLE_DISPLAYED_VERSION:50.01]
[AUTHOR:Dwarf Fortress Wiki]
[DESCRIPTION:This is an example mod. This text shows up in-game.]

[STEAM_TITLE:Wiki Example Mod]
[STEAM_DESCRIPTION:This text shows up on Steam Workshop.]
[STEAM_TAG:mod]
[STEAM_KEY_VALUE_TAG:test:stuff]
[STEAM_METADATA:metadata test]
[STEAM_CHANGELOG:Made some changes. Shown in 'Change Notes' tab.]

[STEAM_FILE_ID:#########]
}}

Only <code>ID</code> and <code>NAME</code> are required to appear in the in-game mod menu.

STEAM tags are only used by Steam.
* The <code>STEAM_FILE_ID</code> used to identify the mod in the Workshop. This is automatically managed when uploading to Steam the first time. And required if you wish to update an existing Steam Workshop mod.
* The <code>STEAM_TAG</code> and <code>STEAM_KEY_VALUE_TAG</code> are used by Steams search engine and the categorization. You can use as many entries you want, use a separate tag for each one.
* You can also create a thumbnail for your mod by creating an image called <code>preview.png</code> in the same level as your info.txt file. This image will become the thumbnail when the mod is uploaded to steam workshop. The image should be less than 1MB in size.

=== Objects and graphics folder ===

At the root of your mod folder you can have a <code>objects\</code> and <code>graphics\</code> folder, this is where all the [[raw file]]s or [[graphics]] goes (exactly the same as objects from previous versions of Dwarf Fortress) allowing you to tweak or add new content for the game. It's beyond the scope of this short guide to go into what specific tags do, but the vanilla objects and previous mods by members of the community will give you plenty of examples to work with. See: [[modding]].

The graphics filenames are not important, furthermore they can be arbitrarily nested into other sub-folders to help you organize your mod content.

== Publishing mods ==

There are two official platforms for publishing ''Dwarf Fortress'' mods, recommended because it's easy for people to find them there. These are [https://steamcommunity.com/app/975370/workshop/ Steam Workshop] and [https://dffd.bay12games.com/ the Dwarf Fortress File Depot (DFFD)].

=== Publishing on Steam Workshop ===

To upload a mod to Steam Workshop, you need to add STEAM tags to the <code>info.txt</code> file (see above.) Afterward, you put the unzipped mod folder in the "<code>mods/mod_upload</code>" folder. Then select Mods from the title menu, and upload your mods using the button you'll see there. Other Steam users will be able to subscribe to your mod immediately once it is uploaded.

Once the upload process is completed successfully, you'll find a <code>[STEAM_FILE_ID:#########]</code> appended to your info.txt. Make sure this entry is included for future uploads if you want to make changes to your mod and have it overwrite the existing entry on the workshop. Otherwise you'll create a new entry every time you upload.

=== Publishing on DFFD ===

In addition to Steam Workshop, it is recommended you upload your mod to DFFD. This allows people who play ''[[Classic|Dwarf Fortress Classic]]'', or ''[[Premium]]'' via Itch.io, to also download and play your mod. To publish/upload a file to DFFD you first need to create an account.

For legal reasons, mods that contain graphics derived from the ''Premium'' graphics should not be uploaded outside Steam Workshop. For this reason, you might want to separate your mod into two parts: the first without graphics, which is uploaded to both DFFD and Steam Workshop, and the second with ''only'' the graphics, uploaded only to Workshop. Of course, this is not an issue if your graphics are not based off the ''Premium'' ones.

[[Category:Modding]]

Mod

2023-01-07T16:57:46Z

Jan:

{{For/see|using mods and their basic structure|[[modding]] about making mods}}

A '''mod''' (short for modification) is an alteration of the game and the objective of modding. Modifications can range from small tweaks to complete overhauls.

== Downloading Mods ==

Mods can be acquired using the [https://steamcommunity.com/app/975370/workshop/ steam workshop] (if using Steam version), a manual download from [[Bay 12 Forums]] or third party websites (like [https://dffd.bay12games.com/ DFFD]), or by [[Modding|creating]] one yourself.

Users of the Steam version can subscribe to mods on Steam Workshop, once the download is complete they will be available when creating a new world automatically. Otherwise, manually download the mod, then place the mod zip file or the unzipped mod folder into the Dwarf Fortress [[mod folder]] (if this folder doesn't exist, you can create it.) You can have more than one mod in the mod folder, including different version of the same mod. The game will detect all mods that are properly made in this folder and let the user select which mods to play (see bellow.)

== Enabling/Installing Mods ==
[[File:Ui-p-mod-selection.png|thumb|world generation mod menu]]

Mods are enabled per per world. When [[World generation|creating a world]] and choosing its initial parameters, if you have a mod available, there should be a '''Mods''' button at the bottom of the screen. Pressing this will let you select which mods you'd like to enable and what the load order should be. You should put mods at the end of the mod list after the vanilla objects if you don't have any further information, so that they can reference vanilla objects after those are loaded.

Something something load order basic

<div class="" style="padding: 0.8em 1em; margin: 0.5rem 0; background: #fcf8e3; border-left: 5px solid #aa6708;">
* Mods are enabled per world and can not be disabled afterwards, however, it is possibly to manually modify the game file as we did in previous versions by applying the mods directly to <code>[[Game folder|<Dwarf Fortress>]]/data/vanilla</code>. Be ware this method has the disadvantage of being a permanent change for all worlds and may break your game.

* Unlike the previous versions of Dwarf Fortress, mods no longer live inside [[save]] and must be installed on every computer where saves using those mods are going to be loaded. Once a world is created that uses mods, the game will copy the relevant mods to the <code>[[Game folder|<Dwarf Fortress>]]/data/installed_mods</code> folder. That is the version that the game actually uses. Installed mods will now show in the main menu->mods screen as 'installed'.
</div>

== Updating Mods ==
If a world is using a mod that's been updated, and is currently using an older version of that mod, the player will be prompted about this when a save is loading. Causing a message like the following to appear: 
[[File:mod_version_v50_prompt.png]]

When this happens, you have the choice of simply updating the mod, updating ''all'' mods at once, continuing to use the older version of the mod in question without updating, selecting the previous task but not updating ''any'' possibly outdated mods or simply returning to the title screen.

== Modding ==

Dwarf Fortress supports mods in the form of new objects and tiles. Each mod is a zip file or unzipped folder with the required format (see below.)

=== Mod Format===

Mods contain an info.txt file and either an "objects" folder or a "graphics" folder (or both.) All of the vanilla objects in the game too use this format. Your mod folder should look something like this:

[[File:Folder-orange.svg|20px|link=]] Mod Name
├ [[File:Text-x-generic.svg|20px|link=]] info.txt
├ [[File:Text-x-generic.svg|20px|link=]] preview.png
├ [[File:Folder.svg|20px|link=]] objects
└ [[File:Folder.svg|20px|link=]] graphics

=== Mod info ===
{{main|Mod info token}}

Each mod must have a <code>info.txt</code> at the root of your mod folder. It has a few fields defining basic metadata information about the mod and can be edited using any text editor (like notepad++). See Example:

{{code|
[ID:wiki_example]
[NAME:Wiki Example Mod]
[NUMERIC_VERSION:5001]
[DISPLAYED_VERSION:50.01]
[EARLIEST_COMPATIBLE_NUMERIC_VERSION:5001]
[EARLIEST_COMPATIBLE_DISPLAYED_VERSION:50.01]
[AUTHOR:Dwarf Fortress Wiki]
[DESCRIPTION:This is an example mod. This text shows up in-game.]

[STEAM_TITLE:Wiki Example Mod]
[STEAM_DESCRIPTION:This text shows up on Steam Workshop.]
[STEAM_TAG:mod]
[STEAM_KEY_VALUE_TAG:test:stuff]
[STEAM_METADATA:metadata test]
[STEAM_CHANGELOG:Made some changes. Shown in 'Change Notes' tab.]

[STEAM_FILE_ID:#########]
}}

Only <code>ID</code> and <code>NAME</code> are required to appear in the in-game mod menu.

STEAM tags are only used by Steam.
* The <code>STEAM_FILE_ID</code> used to identify the mod in the Workshop. This is automatically managed when uploading to Steam the first time. And required if you wish to update an existing Steam Workshop mod.
* The <code>STEAM_TAG</code> and <code>STEAM_KEY_VALUE_TAG</code> are used by Steams search engine and the categorization. You can use as many entries you want, use a separate tag for each one.
* You can also create a thumbnail for your mod by creating an image called <code>preview.png</code> in the same level as your info.txt file. This image will become the thumbnail when the mod is uploaded to steam workshop. The image should be less than 1MB in size.

=== Objects and graphics folder ===

At the root of your mod folder you can have a <code>objects\</code> and <code>graphics\</code> folder, this is where all the [[raw file]]s or [[graphics]] goes (exactly the same as objects from previous versions of Dwarf Fortress) allowing you to tweak or add new content for the game. It's beyond the scope of this short guide to go into what specific tags do, but the vanilla objects and previous mods by members of the community will give you plenty of examples to work with. See: [[modding]].

The graphics filenames are not important, furthermore they can be arbitrarily nested into other sub-folders to help you organize your mod content.

== Publishing mods ==

There are two official platforms for publishing ''Dwarf Fortress'' mods, recommended because it's easy for people to find them there. These are [https://steamcommunity.com/app/975370/workshop/ Steam Workshop] and [https://dffd.bay12games.com/ the Dwarf Fortress File Depot (DFFD)].

=== Publishing on Steam Workshop ===

To upload a mod to Steam Workshop, you need to add STEAM tags to the <code>info.txt</code> file (see above.) Afterward, you put the unzipped mod folder in the "<code>mods/mod_upload</code>" folder. Then select Mods from the title menu, and upload your mods using the button you'll see there. Other Steam users will be able to subscribe to your mod immediately once it is uploaded.

Once the upload process is completed successfully, you'll find a <code>[STEAM_FILE_ID:#########]</code> appended to your info.txt. Make sure this entry is included for future uploads if you want to make changes to your mod and have it overwrite the existing entry on the workshop. Otherwise you'll create a new entry every time you upload.

=== Publishing on DFFD ===

In addition to Steam Workshop, it is recommended you upload your mod to DFFD. This allows people who play ''[[Classic|Dwarf Fortress Classic]]'', or ''[[Premium]]'' via Itch.io, to also download and play your mod. To publish/upload a file to DFFD you first need to create an account.

For legal reasons, mods that contain graphics derived from the ''Premium'' graphics should not be uploaded outside Steam Workshop. For this reason, you might want to separate your mod into two parts: the first without graphics, which is uploaded to both DFFD and Steam Workshop, and the second with ''only'' the graphics, uploaded only to Workshop. Of course, this is not an issue if your graphics are not based off the ''Premium'' ones.

[[Category:Modding]]

User talk:BarelyCreative

2023-01-07T11:52:13Z

Jan: /* Graphic set */ new section

Talk:Main Page

2023-01-07T11:32:39Z

Jan: /* New main page gallery images */

{{Archive|
# [[Talk:Main Page/archive1|Archive 1]]
# [[Talk:Main Page/archive2|Archive 2]]
# [[Talk:Main Page/archive3|Archive 3]]
}}

== How to create a new language page? ==

I've just seen one dwarf requesting a Japanese page.

If possible, I'll gladly translate this wiki into Korean. Korea is relatively a small country so the language is not that widely used, but surely there are some players, I guess.

I don't know where to ask about this :9

== Free SSL Certificate ==

If the operators want to re-enable https, they can get a free (as in beer) certificate from https://letsencrypt.org/ . Instructions are on that site and it's very easy.
:HTTPS is enabled now as of the June 2019 upgrades. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:53, 3 July 2019 (UTC)

== Re: Discord ==

I notice there's a Discord on this page. But shouldn't it be the Kitfox Games Discord, since that's the only official Discord for Dwarf Fortress?

[[User:AlastríonaCatskill|AlastríonaCatskill]] ([[User talk:AlastríonaCatskill|talk]]) 13:43, 12 February 2020 (UTC)
;I wasn't aware of it. If that is the case, then it should probably be added to the page. [[User:OluapPlayer|OluapPlayer]] ([[User talk:OluapPlayer|talk]]) 16:03, 12 February 2020 (UTC)

Yeah, the only reason there is one at all is because somebody added some random one. I changed it to the only DF discord I knew of at the time. The only way I've now been able to find it is to search for 'Kitfox Games discord'. It's not listed on the bay12 links page, a forum thread, the reddit, or the Steam pages. Anyway, I've DMed Victoria on the KitfoxGames discord to make sure they're OK with adding the invite to this page. [[User:Ziusudra|Ziusudra]] ([[User talk:Ziusudra|talk]]) 20:08, 12 February 2020 (UTC)

...Sorry, is it too late for this? I mean, while we're still discussing this, it looks like [https://dwarffortresswiki.org/index.php/Talk:Main_Page#B12G_Discord someone else got left behind as well]. Add, or not? [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 22:21, 12 February 2020 (UTC)

I'm not sure what you were trying to link to. Do you mean this: http://www.bay12forums.com/smf/index.php?topic=163555.0 Note that the thread was locked because of drama. There's a lot of red flags: the drama, despite using the name Bay12Games it never uses the word 'unofficial', the rules channel posts are from a deleted user, the announcements channel hasn't updated in well over a year, many channels haven't been active in months. I'm not so much saying no, but I am asking: should it be linked?

There's also this: http://www.bay12forums.com/smf/index.php?topic=157332.0 But that invite is invalid. [[User:Ziusudra|Ziusudra]] ([[User talk:Ziusudra|talk]]) 02:35, 13 February 2020 (UTC)

Ah, it's a ''dead'' discord. I see now. There was just no response to the April '17 topic, I stumbled across it all and got curious. No, I don't think it should be linked. Thanks for the analysis, anyway! [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 11:44, 13 February 2020 (UTC)

== [[Multithreading]] ==

Would it be OK to create [[Multithreading]] page describing why (preferably with citations)
* even perfectly implemented boost would not be significant
* multithreading is not something that can be bolted on complex program
* DF is complicated case where taking advantage of multithreading is not obvious http://www.bay12forums.com/smf/index.php?topic=34311.msg7833713#msg7833713
* DF is filled with many gamebreaking bugs unfixed for many years, multithreading bugs are unusually awful to fix
* author of DF has minimal experiences with multithreading
* writing multithreaded code is hard
* writing correct multithreaded code is awfully hard
* fixing bugs in a multithreaded code is nightmare

and multithreading is not going to happen, ever

http://www.bay12forums.com/smf/index.php?topic=34311.msg7833713#msg7833713
http://www.bay12forums.com/smf/index.php?topic=107833.0
https://bholley.net/blog/2015/must-be-this-tall-to-write-multi-threaded-code.html + “At Mozilla, there is a sign on the wall behind one of our engineer’s desks. The sign has a dark horizontal line, below which is the text, ‘You must be this tall to write multi-threaded code.’ The line is roughly nine feet off the ground. We created Rust to allow us to lower that sign.” http://www.oreilly.com/programming/free/files/why-rust.pdf

[[User:Mko|Mko]] ([[User talk:Mko|talk]]) 03:07, 28 March 2020 (UTC)
:I disagree with some of your talking points
:* In DF each AI actor makes its own decisions, the computations can be done in parallel for an ncores speedup
:* This parallelism should be built into the lowest design levels of the program, it can be done in a DF-like program
:* With training and experience a good developer can write and debug multithreaded code.
:I agree that multithreading is unlikely to be done in DF; It can not easily be bolted on and I rather see the developer spend time on game-play.
:Is it worth to create a wiki page for what is essentially a one line explanation?
:--[[User:MathFox|MathFox]] ([[User talk:MathFox|talk]]) 18:40, 31 March 2020 (UTC)
::We would essentially be writing a page about a thing that doesn't matter to Dwarf Fortress. I can't agree to the existence of a page that's basically "This subject doesn't exist in the context of the game but here's the reasons why it should or shouldn't". This is better reserved for forum discussion, not a wiki. [[User:OluapPlayer|OluapPlayer]] ([[User talk:OluapPlayer|talk]]) 12:54, 1 April 2020 (UTC)

== Re: Discord II ==

Good morning.

I was confiding with some friends, who had alerted me to the "Unofficial Bay 12 Discord" posted on this Wiki. Simply put, allegations of the use of ableist slurs were thrown, as well as screenshot evidence of using hard racist slurs against people of colour.

I feel that the Unofficial Discord should hereby be removed from the social media part of the website for the following reasons:
* No official connection to Bay 12 or the publishers [and, by extension, every non-Bay12 forum should be removed - especially dead ones]
* This unofficial Discord is actively opposed to the standpoints that Toady One and Threetoe have posted on the bay12games site over the recent days.
* This unofficial Discord uses slurs and other problematic language that actively harms the image of the Dwarf Fortress community
* This unofficial Discord will likely make it so that people steer away from the game.

I do not feel comfortable with the Wiki platforming a known racist Discord server, as that is de facto support of the messages of that server.
[[User:AlastríonaCatskill|AlastríonaCatskill]] ([[User talk:AlastríonaCatskill|talk]]) 12:02, 21 June 2020 (UTC)

Update: Apparently, this same Discord has been banned from the r/dwarffortress subreddit for as long as one of the mods can remember, and the link to it was banned on the official Kitfox Discord as well. I can post the screenshots I have of actively problematic behaviour on this Discord but I will not do it unless necessary, as the contents are alarming like that which will not be named. [[User:AlastríonaCatskill|AlastríonaCatskill]] ([[User talk:AlastríonaCatskill|talk]]) 12:10, 21 June 2020 (UTC)

:I've removed the link. Safe to say, we don't need the wiki to be associated with this sort of people. [[User:OluapPlayer|OluapPlayer]] ([[User talk:OluapPlayer|talk]]) 21:58, 21 June 2020 (UTC)

::The "Unofficial Bay 12 Discord" was already not linked on the main page - the only place it was mentioned is this talk page. Are you talking about that one or the Unofficial Dwarf Fortress Discord that is linked on the main page? The latter does have it's #elfposting channel, but that channel is initially hidden, opt-in only, and clearly labelled as a lawless zone. For an analogy, there are many very awful subreddits, but we still link to reddit - (yeah that's a little different but not much). Otherwise the unofficial DF discord is well modded and such behavior is not allowed in other channels. So, are you certain which discord/channel the screenshots came from? [[User:Ziusudra|Ziusudra]] ([[User talk:Ziusudra|talk]]) 22:29, 21 June 2020 (UTC)

Since there's some confusion, AlastríonaCatskill, could you confirm and/or provide some evidence that following the link that was on the main page (removed in [https://dwarffortresswiki.org/index.php?title=Main_Page&diff=253449&oldid=251109]) takes you to the discord that you were referring to? The only reference I can find to a discord removed from the /r/dwarffortress sidebar is for a different discord, not the one that was linked on the main page (although it's possible that just the invite link was different). I just want to make sure that we're removing the right one here. If you have anything that you don't want to share publicly, you can PM me on the forums (same username) or [[Special:EmailUser/Lethosor|email me]] through the wiki, which I think is working. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:45, 22 June 2020 (UTC)

:@Lethosor, I have emailed you the relevant images via the link you had created. The Discord that was on the main page and removed today is indeed what was being referred to, especially with the confirmation of the #elfposting channel being from said Discord. In my opinion, @Ziusudra, the inclusion of a problematic part of that community, even as opt-in, is unacceptable in my book for a community to be platformed on this Wiki. [[User:AlastríonaCatskill|AlastríonaCatskill]] ([[User talk:AlastríonaCatskill|talk]]) 03:26, 22 June 2020 (UTC)

Hello, I am the owner of the Unofficial Dwarf Fortress discord. I just want to clear a few things up and open a channel of communication.
Several years ago, the original owner of the discord left, in no small part due to all the sexism and racism and such.
After a few days of an having an interim owner, it was given to another user, who onboarded several users as admins, including me.
The new owner tried a lot to curb terrible stuff on the server, however this often lead to drama.

The r/dwarffortress delisting happened after some of that drama spawned a new discord with a more "free speech" orientation,
things spilling over to the forums and other places. Some time after that, she left the server to me, due to the amount of
stress running that place caused her. When I took over I also tried to make it a better place, but with slower and subtler
methods that wouldn't spark drama. Completely disallowing some behaviour outside of #elfposting was part of that,
and later making that channel hidden by default was another. Now, the discord is much much better to be in
than it ever was before, though it still has major flaws. I don't like #elfposting at all myself, but I don't rule with an iron fist nor
do I know what much I can do without sparking massive drama again. Since April this year I have had some plans to make the discord
quite a bit better, however some of my mods have been against it in part due to feeling it would cause bigger problems
(though, as you probably know, some of them participate in #elfposting).
With recent events, both within and outside the DF community, we have decided to move ahead, every mod on board,
with some plans including phasing out the #elfposting channel in a way which will not create large issues for moderation.
It will be fully gone within one (1) week of now.

Also, I am a tad annoyed that you posted about this here but completely neglected contacting us. In the future, could you
please contact me or one of my mods when you have any concerns about the server? I really do care about these things and we need feedback.
—[[User:Lonjil|Lonjil]] ([[User talk:Lonjil|talk]]) 10:32, 22 June 2020 (UTC)

: Thank you for replying here Lonjil. Unfortunately, I cannot trust your take on this matter for several reasons.
: # One of the moderators has an anti-semitic stereotype profile picture
: # Even if the only place of no censorship is the elfposting channel, and even if it is opt-in, the complete chaos of racist slurs allowed there is completely unacceptable for minority players and an extremely toxic environment. There have been instances of straight hate speech on the channel / server as well, suggesting to kill people of colour and LGBTQIAA+ people.
: In short, the toxicity of your Discord's community makes it not just uncomfortable, but downright dangerous for minority people playing Dwarf Fortress. As Tarn and Zach have made liberal-to-leftist political views in the past, the chances of minorities to play the game is higher - and I wouldn't want to be a person of colour signing up for a shitposting channel to only be met with over 10,000 instances of the hard-n word being used. The Discord should remain off of the Wiki until things shape up and all instances of hate speech be purged from server history. Personally I would rather all non-official channels of communication be removed from the page, period, but that is a less pressing discussion than active hatred of minorities being platformed on the Wiki via your unofficial Discord. [[User:AlastríonaCatskill|AlastríonaCatskill]] ([[User talk:AlastríonaCatskill|talk]]) 12:30, 22 June 2020 (UTC)

:: Small edit / follow-up to my previous message. My friend tells me that elfposting is the most commonly used channel, which goes to show the level of hatred allowed into the community. It may be best to remove the channel in entirety, and make a new meme channel with no hate speech allowed. [[User:AlastríonaCatskill|AlastríonaCatskill]] ([[User talk:AlastríonaCatskill|talk]]) 12:33, 22 June 2020 (UTC)

::: The admin you are referring to is a jew, who lives in Israel. I prefer to not police people of other ethnicities when it comes to negative stereotypes and such of themselves, they know what they are comfortable with far better than I ever could.

::: Elfposting is not, by any reasonable measure, the most used channel. It has fewer users than any other channel. It has a fair number of messages, but only because there is no rule against spamming in there. So, nearly all of it is spam, which was the point of the channel to begin with.

::: "It may be best to remove the channel in entirety" this is exactly what is happening, as I already said. We're giving the channel regulars a few days to hear the news, but then the channel will be gone. We already have a more pleasant meme channel from an experiment we did in April, which we are bringing back. —[[User:Lonjil|Lonjil]] ([[User talk:Lonjil|talk]]) 13:57, 22 June 2020 (UTC)

Hi all - thanks for keeping this discussion civil. I've been investigating the policies of other DF communities, and I've come to the conclusion that it would be best for the wiki to only link to the official DF Discord (Kitfox). I'll also make a pass through the other sites linked on the main page. I'm sorry to those of you working hard to maintain Discords and other unofficial communities out there - I know it's difficult, and I don't want to judge your communities without being a part of them. However, there will always be debates like these about whether a community deserves to be linked from a more "official" place, like the wiki, and no matter where we draw the line(s), people will be upset. The policy of only linking to the Kitfox Discord seems to have worked for other communities, which is why I'm applying it here. I would be happy to have a broader discussion at [[DF:Centralized Discussion]] if anyone wants to. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:48, 23 June 2020 (UTC)

== Put Chinese language wiki on other Languages ==
Found it on Internet([http://cdf.wikidot.com/start]) – [[template:unsigned|unsigned]] comment by [[User:45.58.187.66|45.58.187.66]]

:I added a link to it. I'm not sure what the process is for adding interwiki link support (support for links to pages in the sidebar, like how [[DF2014:Cat]] links to http://dfwk.ru/Cat) but I can look into that too. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:40, 19 August 2020 (UTC)
::Hello! I'm the admin of [https://dfzh.huijiwiki.com/ Chinese Dwarf Fortress wiki], and I've previous put its link on the main page. We've now enabled interwiki link from our site to English site, and we wish to get one back from English site to CN site as well. Hope that is possible, and thanks so much! The URL for our site should be: <code>https://dfzh.huijiwiki.com/wiki/$1</code> [[User:Xjtu-blacksmith|xjtu-blacksmith 黑山雁]] ([[User talk:Xjtu-blacksmith|talk]]) 11:26, 1 November 2022 (UTC)

:::Added. Prefix is "zh", for example: https://dwarffortresswiki.org/index.php?title=Main_Page&diff=266849&oldid=266730 —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:45, 28 November 2022 (UTC)

== Villains Wiki ==

To started putting some creatures on the Villains Wiki, because I want to spread the word of Dwarf Fortress around, and these creatures fit the theme of the wiki anyway. Here's an example page, and the template of all pages: 
[https://villains.fandom.com/wiki/Goblins_(Dwarf_Fortress) Villains - Goblins] 
[https://villains.fandom.com/wiki/Template:Dwarf_Fortress_Villains Villains - Template of DF Villains]

If anyone could add more info to those pages, or think more creatures should be on that wiki, please let me know. Or you could add it yourself. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 13:37, 9 January 2021 (UTC)

== Replace Chinese Wiki with the new one on Fandom ==

The previous Chinese wiki on wikidot seems to be inactive for a long time, with its main page refers to the download link of v0.44.10, and most pages are never updated even earlier than that version. Recently we are working on a new site on Fandom ([https://dwarf-fortress.fandom.com/zh]), trying to keep everything up to date. Wish to replace the links on dwarffortresswiki's main page and the sidebar link (inter-language link) with the one at Fandom, so that more people may get to the right place and join us. [[User:Xjtu-blacksmith|xjtu-blacksmith 黑山雁]] ([[User talk:Xjtu-blacksmith|talk]]) 04:16, 30 December 2021 (UTC)

:I've added the link of Fandom site onto the main page, without removing the previous one. [[User:Xjtu-blacksmith|xjtu-blacksmith 黑山雁]] ([[User talk:Xjtu-blacksmith|talk]]) 11:09, 12 May 2022 (UTC)
:We've migrated Chinese Wiki to huijiwiki.com, which is now shown on Main Page. [[User:Xjtu-blacksmith|xjtu-blacksmith 黑山雁]] ([[User talk:Xjtu-blacksmith|talk]]) 07:41, 29 May 2022 (UTC)

::Added. The "zh" prefix should work for links. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:43, 28 November 2022 (UTC)

== Kitfox Discord ==

<blockquote>
''2022-04-15 BlueManedHawk . . (8,594 bytes) (-135)‎ . . (The Kitfox Games discord server has an unethical code of law. I don't think the wiki should be supporting it.)''

''2022-04-15 Ziusudra . . (8,729 bytes) (+135)‎ . . (Undo revision 263652 by BlueManedHawk[:] please discuss changes such as this on the talk page first) (Tag: Undo)''
</blockquote>

Alright, I can do that.

The Kitfox Games discord server has a code of law that contains the following immoralities:

:- Is very vague and nebulous, allowing the moderators to exploit the vagueness to be able to do very different things in similar circumstances in alignment with their biases. (Not that they do that, but the fact that it's possible is concerning.) 
:- Contains a "These rules are subject to common sense." clause, essentially meaning that the moderators are able to do whatever they want and hide it behind the barrier of "common sense". This goes completely against the point of the concept of rules in the first place as a promise from those in power in regards to what they will and will not do. 
:- Allows for infinite punishment.

That last one could do with a bit of explaining. Let us begin with the premise that the punishment for a crime should be proportional to the severity of the crime. I think we can all agree on this. Therefore, an infinite punishment should only ever be given for an infinite crime. However, humans are not infallible. People make mistakes. And this means that if a court of law is able to administer an infinite punishment, they run the risk of accidentally giving somebody an infinite punishment that they do not deserve. This, I think we can all agree, is unnacceptable. Therefore, infinite punishment cannot every be administered ethically.

I hope that this explains why I want the link to the Kitfox games discord removed.

Regards,

—[[User:BlueManedHawk|BlueManedHawk]] ([[User talk:BlueManedHawk|talk]]) 22:29, 15 April 2022 (UTC)
:* Their rules are not vague or nebulous, they even give examples of what the rules cover. Of all the discords I am on, their rules are some of the most detailed.
:* The "''depending on the action and our judgement''" is quite similar to the "''depending on how disruptive you were and your prior history''" found in the DF forum rules, and is pretty standard social media boilerplate and is itself common sense.
:* Their rules state "''Breaking these rules will result in a warning or ban''", which is not at all "''infinite punishment''", and is again quite similar to the "''If you violate the guidelines, you will be warned, muted for a period of days, or banned completely''" on the forums. It's not like they can keep anyone from playing the game or interacting with the other communities.
: Your referring to their rules as "code of law" is hyperbolic. Their rules are quite similar to the rules of the forum. So, I disagree and think the link should stay. [[User:Ziusudra|Ziusudra]] ([[User talk:Ziusudra|talk]]) 23:13, 15 April 2022 (UTC)
::* The rules are pretty vague. Examples aren't enough. A strict, clear, unambiguous definition is necessary to prevent abuse.
::* While it is true that their clause is ''normal'', that doesn't mean it's ''right''.
::* The explanation of bans doesn't explain how long the bans will last. Since there's nothing explicitly stating that infinite punishment won't be given, and since "ban" by itself generally refers to a permanent ban, I think that it's allowing infinite punishment.
::* I'm not sure how the term "code of law" is hyperbolic. I use the term synonymously with "set of rules".
::* I can't seem to find a code of law for the forums. However, if what you said is true, then clearly we should also remove the link to the forums.
::
:: Regards,
::
:: —[[User:BlueManedHawk|BlueManedHawk]] ([[User talk:BlueManedHawk|talk]]) 02:59, 16 April 2022 (UTC)
::: http://www.bay12forums.com/smf/index.php?topic=27009 It's linked in the header at the top of every forum page, though if the header is collapsed you won't see it.
::: Unambiguous rules are technically impossible since human behavior is limitless. That's why we hav judges for actual laws - even society's strictest laws need a human adjudicator. Then, even with "permanent bans", both Kitfox and Bay12 hav public email addresses and twitter accounts which can be used to petition to hav a ban removed.
::: Finally, suggesting the removal of the links to the official forums for the game this wiki is dedicated to is unreasonable, to the point of making me wonder if you're trolling. [[User:Ziusudra|Ziusudra]] ([[User talk:Ziusudra|talk]]) 04:59, 16 April 2022 (UTC)

::::I agree with Ziusudra. More broadly, I think we should keep links to "official" DF channels, and Kitfox is a DF publisher. If a potential for "infinite punishment" warrants removing links to the offending site, then by your logic, we should remove all links to the wiki from the wiki because users here have been banned permanently. That has been done based on the best judgement of the people who volunteer their time to run the wiki and has been open to appeals, and I expect other channels are similar. I'm not interested in entertaining this argument here. If you have specific issues with a specific external site, I suggest that you get in touch with the moderators there instead. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:34, 16 April 2022 (UTC)

:::::Hello.

:::::As I mentioned below, the DFWiki is in a position of power, and by removing the link to them, we can potentially force their hand into making their code of law more moral. On the other hand, keeping the link there could potentially be seen as supporting their immoral behavior, tarnishing the reputation of the site. This is why I brought up my issues with an external site onto this one: because these issues also affect it.

:::::It is true that by my logic, the DFwiki is operating immorally. However, I would like to mention that ''you are in a position of power on the wiki'', Lethosor. I would think that you have the ability to change the Wiki's code of law to be more moral. You have the choice to make the wiki a better place, and I advise that you take it.

:::::Regards,

:::::—[[User:BlueManedHawk|BlueManedHawk]] ([[User talk:BlueManedHawk|talk]]) 06:22, 16 April 2022 (UTC)

::::Hello.

::::* I don't know which header you're referring to—wherever it is, it seems to not be there for me. Regardless, I thank you for clarifying which guidelines you were referring to.
::::* Unambiguous rules are largely impossible because nobody has yet created an unambiguous language. However, that doesn't mean that we shouldn't still seek to get as close to unambiguous as possible when constructing a code of law.
::::* Claiming that the bans are transient because it's possible to appeal them is optimistic, and while there is a place for optimism, this is not it. Any potential that a legal system has for corruption is one that we cannot assume will not be used, and often, corruption begets corruption, continuing the cycle until a revolution happens.
::::* Being a central repository of knowledge on DF, the DFwiki is in a position of power. If we do remove the link to the Kitfox discord under the condition that they make their code of law more moral, then we can theoretically force their hand, maybe. There is, of course, a risk to this, and this should be deliberated before a decision is made.
::::* I am not a troll. Why does everybody keep thinking that?

::::Regards,

::::—[[User:BlueManedHawk|BlueManedHawk]] ([[User talk:BlueManedHawk|talk]]) 06:22, 16 April 2022 (UTC)

== Advertisements problem ==

One of the full-page advertisements(a pop-up that obscures the whole page) had what looked like a "close" button, but it just tried to redirect me to another page.
Full page advertisments aren't untoward but like, web elements that say 'close' are expected to do what they say, otherwise it's intercepting clicks. – [[template:unsigned|unsigned]] comment by [[User:Eerr|Eerr]]

:Do you have a screenshot of the offending ad, or can you take one if it happens again? My understanding is that that is something we (admins) don't have control over, but we can report misleading ads to Google. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:09, 2 June 2022 (UTC)

== Kitfox Discord (again) ==

Hi. I'm again requesting the removal of the link to the Kitfox discord server for only two reasons this time: the code of law gives infinite power to the moderators, and the criminal justice system uses punishment to deal with criminals. These are obviously both immoral, and until the server fixes these issues, the DF wiki ought to remove the link so as not to seem to be promoting them. [[User:BlueManedHawk|BlueManedHawk]] ([[User talk:BlueManedHawk|talk]]) 21:45, 15 September 2022 (UTC)
:And again, I don't support removing the official publisher's discord just because you think that there is some thing wrong with their completely normal and reasonable moderation practices, none of which involves "infinite power", "punishment", "criminals", or other such hyperbole. Banning is not "punishment", it is protection of the community from those that act to harm it, nor is it "infinite power" since all it does is keep those rule breakers off one discord server and nothing else. All of which also happens on both the Bay12 Forums and this very wiki, both of which, by your logic, you should immediately stop using lest you appear to be promoting them. [[User:Ziusudra|Ziusudra]] ([[User talk:Ziusudra|talk]]) 03:45, 16 September 2022 (UTC)
::Normalizing of horribly unethical practices is not okay. I do not think it is hyperbole to use the terms "infinite power, "punishment", and "criminals". The server is a jurisdiction like any other, and it should be held to the same standards of morality as any other—this includes not using punishment as a means to deal with those who break the law. It is completely possible to protect the community without using bans—bans simply get rid of problems instead of fixing them, and are ineffective against the diligent. Infinite power is not an okay thing to give to those who govern a jurisdiction—dictatorial power structures have been shown to fail many times over throughout history.
::
::If we simply must keep any official venues for DF on the main page, regardless of morality (this includes the forums, which i agree should also be removed), then the Wiki ought to put a disclaimer of some sort clarifying that they are being listed not in support of the governance policies of the communities, but simply because they are official.
::
::[[User:BlueManedHawk|BlueManedHawk]] ([[User talk:BlueManedHawk|talk]]) 17:24, 17 September 2022 (UTC)
:::Good god, how many of these discussions are you gonna keep making? Is there anything that ''doesn't'' offend you? -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 13:14, 22 September 2022 (UTC)
::::There's no need to be rude. But to answer your question, i'm going to have as many discussions as are necessary until a concensus is reached. [[User:BlueManedHawk|BlueManedHawk]] ([[User talk:BlueManedHawk|talk]]) 21:43, 22 September 2022 (UTC)
:::::You can't keep just keep making constant requests of "guys can we please remove that and that and that and this and this because of like business and anti-competitive stuff and yeah and like" but then turn around and go "why does everyone think I'm a troll?" Can you seriously not connect those two things together? I've been part of this community for a long time, and you are the one and only person who gets all offended by things that no one else would even care to think about. This wiki is not the place for that. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 10:48, 23 September 2022 (UTC)
::::::I really don't understand why people think that i'm a troll. If you or someone else were to explain it to me in a manner that's more polite than your previous messages have been, i'd be happy to listen. [[User:BlueManedHawk|BlueManedHawk]] ([[User talk:BlueManedHawk|talk]]) 20:18, 23 September 2022 (UTC)
:::::::Hmmmmmmm, no. I'm gonna skip the "polite" thing and just speak the truth. No regrets. The fact that you can't see why people think you're a troll makes the situation even worse. You're someone who got all bent out of shape over a Minecraft diamond reference, something that no one else would ever care about. You keep saying you don't see how people think you're a troll when it was explained to you many times. All this goofy legal stuff you keep bringing up is best left elsewhere. Not here. -- [[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 13:59, 24 September 2022 (UTC)

== Wiki logo ==

The new wiki logo requires getting used to. Personally, I wouldn't mind something simpler like [[:File:Dfhack-logo.png|DFhacks]] with a more fancy version going to the mainpage. Maybe someone from the community can come up with something, here is what [https://ibb.co/26J569S my meager skill] able to come up with --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 13:20, 7 December 2022 (UTC)
:I just noticed it and I have to agree. It's like being hit in the face with a brick. It references DF relatively deep lore ([[obsidian]] and [[semi-molten rock]]) and it feels way too harsh compared to the relatively relatable and much more early-game relevant icon of a dwarf mining. --[[User:Lurker|Lurker]] ([[User talk:Lurker|talk]]) 13:01, 10 December 2022 (UTC)
:: For reference here is the [[:File:DFDefault.png|digger]] from the classic intro and bellow rendering of what steam version uses in its loading phase, as well as [https://ibb.co/mtzdLm3 this simple variant]
<diagram>
¦¦¦¦¦¦
¦ ¦
¦ ¦
¦ ¦ ¦ ¦
▒ ▒
▒▒▒▒▒▒▒▒
▒▒ ¦¦ ▒▒
▒▒▒▒▒▒
▒▒▒
▒▒
</diagram> --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 15:39, 11 December 2022 (UTC)

== steam release ==

: "''We are working on a migration that will be complete in the next few days''"
Any estimate on how long that is going to take? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 08:53, 10 December 2022 (UTC)
: Additionally, who is working on this wiki migration, and why is it a closed process? I feel like the migration could have been largely completed by now if everyone was able to help, but that sentiment may just be coming from my ignorance. [[User:Trainzack|Trainzack]] ([[User talk:Trainzack|talk]]) 00:40, 17 December 2022 (UTC)
::See thread at [[Dwarf_Fortress_Wiki_talk:Versions#v50_organization]]. Emi and I are planning to use a MediaWiki bot for this. My current ETA is 2 days from now. I've asked for help in a few places to write such a bot and have had no responses. My concern with a manual migration (e.g. if we have people copy over just some pages manually) is that it would likely result in a state that is much more complicated to finish. I'm sorry it hasn't gotten done yet. Open to help with automating this. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:39, 17 December 2022 (UTC)
:::Ah, that page completely eluded me! Thanks for pointing in that direction. I would be totally willing to help write a bot, just let me know what I can do. [[User:Trainzack|Trainzack]] ([[User talk:Trainzack|talk]]) 14:37, 17 December 2022 (UTC)
::::Thanks for offering. I actually ended up with some time today to work on the migration script. It's almost done, just need to run some final checks before setting it loose. Hopefully tomorrow. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 07:15, 19 December 2022 (UTC)

== wiki tasks ==

Dwarf old head but new account. I'm trying to do a little grunt work for migrating raws and stuff every time I browse the wiki but adding raws is gated behind the adding a page permission. Is there a honey-do list for stuff that needs editing in order to get some contributions under my belt? ☺ --[[User:Hotty gremlin|Hotty gremlin]] ([[User talk:Hotty gremlin|talk]]) 01:47, 24 December 2022 (UTC)
:This lists every page that still has the migration template on it: https://dwarffortresswiki.org/index.php/Special:WhatLinksHere/Template:Migrated_article [[User:Ziusudra|Ziusudra]] ([[User talk:Ziusudra|talk]]) 02:26, 24 December 2022 (UTC)

== New main page gallery images ==

Should we start some sort of initiative, maybe over discord as well, for people to provide a few new images from the premium version to use on the main page? --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 15:47, 6 January 2023 (UTC)
:What's stopping us from just extracting the sprites? [[User:BlueManedHawk|BlueManedHawk]] ([[User talk:BlueManedHawk|talk]]) 23:05, 6 January 2023 (UTC)
::Nothing, but I'm talking about screenshots from in-game similar to the ones in [[Main_Page/gallery]]. :) --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 09:26, 7 January 2023 (UTC)
::Same as one can do from any official screenshots or youtube videos. And lets just say that anyone who want to get their hands on the sprites will not waste time here, there are far easier/quicker alternatives so much so that I can probably make you lmgtfy link for it. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 11:32, 7 January 2023 (UTC)

Talk:Release information

2023-01-06T19:27:12Z

Jan: /* Proposed cleanup of release info */

==Proposed cleanup of release info==

I suggest streamlining release info as follows:
* Delete [[DF2014:Release information]], there's basically no info there
* Replace the contents of [[Release information]] with [[History of Dwarf Fortress#Release_History]], the goal being to provide a concise summary of all updates and major changes since the beginning. No more than a line or two per version.
* Rename [[Release information]] to [[Release history]] with a redirect.

Any objections? [[User:OddballJoe|OddballJoe]] ([[User talk:OddballJoe|talk]]) 07:11, 4 January 2023 (UTC)

iirc there is another places where there is out of date version history. I think that we should consolidate all this into one page, and that page should be 'Release information'. I also think that we should have links here to older versions. Not sure about the other specifics.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 00:25, 5 January 2023 (UTC)

The only other place I've found talking about versions was [[Dwarf Fortress#History]], and I think the top half of [[History of Dwarf Fortress]] can be merged into that.
I'm also thinking that it could be nice to include top few lines of the release history on the main page, to show off what's new, if there's an easy technical solution. [[User:OddballJoe|OddballJoe]] ([[User talk:OddballJoe|talk]]) 23:38, 5 January 2023 (UTC)

: Sorry took me a while to find it again. It is [[save compatibility#breakages]], which isn't updated regularly and is identical in function to what asterisk are used for on this page. So if release information is consolidated here, it can be used instead of that section. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 01:17, 6 January 2023 (UTC)

: I have added the contents of [[History of Dwarf Fortress#Release_History]] here to get things started.
: I added table, if it doesn't work for you simply revert. Also I noticed that the [https://www.dfwk.ru/%D0%92%D0%B5%D1%80%D1%81%D0%B8%D1%8F_%D0%B8%D0%B3%D1%80%D1%8B/50.05 Russian wiki] added version\namespace chooser for its quick link bar, we could use that as well. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 19:27, 6 January 2023 (UTC)

Release information

2023-01-06T19:20:24Z

Jan: fixed my regex mishaps

{{migrated article}}
{{Quality|Unrated}}
{{release notes}}{{av}}

The first version in this release cycle, '''DF 50.01''', was released on '''December 6, 2022'''. The latest version is '''{{current/version}}''', released on '''{{current/lastupdate}}'''. The changes in each version are listed in the sidebar to the right.

Version 50.01 was the first version of Dwarf Fortress released on [https://steamcommunity.com/app/975370/ Steam]. It was also the first version to use a new versioning scheme: the leading "0." present in all previous versions of DF was removed from the version number.

As with all major releases, version 50.01 broke [[save compatibility]] with old versions.

== Version History ==
=== Dwarf Fortress v50 ===
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[Release information/50.05|50.05]] || (2023-01-05):
| ''Bugfixes and optimizations''
|-
| [[Release information/50.04|50.04]] || (2022-12-22):
| '''Classic release''': released the free [[Classic]] version on [https://www.bay12games.com/dwarves/ bay12games.com], and enabled classic mode in the Premium version. Added ability to advance time by one frame, and assign everyone to a burrow.
|-
| [[Release information/50.03|50.03]] || (2022-12-12):
| ''Premium-only bugfixes''. Improved UX for selecting building materials.
|-
| [[Release information/50.02|50.02]] || (2022-12-08):
| ''Premium-only bugfixes''
|-
| [[Release information/50.01|50.01]] || (2022-12-06):
| '''Premium release''': launched the paid [[Premium]] version on Steam and itch.io. Introduced [[graphics]], full [[Mouse control|mouse support]], a new user [[interface]], tutorials, and new [[soundtrack|music]] and sound effects. A number of features from v0.47 were lost in 50.01 (see [[Missing features]]).
|}

=== Dwarf Fortress v0.47 ===
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[DF2014:Release information/0.47.05|0.47.05]] || (2021-01-28):
| ''Bugfix''
|-
| [[DF2014:Release information/0.47.04|0.47.04]] || (2020-02-29):
| ''Bugfix''
|-
| [[DF2014:Release information/0.47.03|0.47.03]] || (2020-02-16):
| ''Bugfix''
|-
| [[DF2014:Release information/0.47.02|0.47.02]] || (2020-02-06):
| ''Bugfix''
|-
| [[DF2014:Release information/0.47.01|0.47.01]] || (2020-01-29):
| ''Release'': introduced creation of [[guildhall]]s and [[temple]]s. Introduced [[traitor]]s and [[villain]]s.
|}

=== Dwarf Fortress v0.44 ===
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[DF2014:Release information/0.44.12|0.44.12]] || (2018-06-23):
| ''Hotfix'';
|-
| [[DF2014:Release information/0.44.11|0.44.11]] || (2018-06-23):
| Civilizations create nearby sites and associate them with your fortress, can request/send workers, long-term memories can lead to personality changes
|-
| [[DF2014:Release information/0.44.10|0.44.10]] || (2018-05-05):
| Dwarves now have short-term and long-term memories of emotional events, Adventurer mode log improved
|-
| [[DF2014:Release information/0.44.09|0.44.09]] || (2018-04-01):
| ''Hotfix'';
|-
| [[DF2014:Release information/0.44.08|0.44.08]] || (2018-03-29):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.44.07|0.44.07]] || (2018-03-12):
| ''Hotfix'';
|-
| [[DF2014:Release information/0.44.06|0.44.06]] || (2018-03-09):
| Raids can pillage/raze sites and demand tribute, will gain skills (e.g. military tactics) during missions
|-
| [[DF2014:Release information/0.44.05|0.44.05]] || (2018-01-14):
| ''Hotfix'';
|-
| [[DF2014:Release information/0.44.04|0.44.04]] || (2018-01-10):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.44.03|0.44.03]] || (2017-12-25):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.44.02|0.44.02]] || (2017-11-23):
| ''Hotfix'';
|-
| [[DF2014:Release information/0.44.01|0.44.01]] || (2017-11-22):
| ''Release''; can now send raids to other sites, build museums using pedestals and display cases, artifacts created during worldgen, civilizations can send spies to gather information on artifacts
|}

=== Dwarf Fortress v0.43 ===
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[DF2014:Release information/0.43.05|0.43.05]] || (2016-06-20):
| '''64-bit support''', bugfixes
|-
| [[DF2014:Release information/0.43.04|0.43.04]] || (2016-06-20):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.43.03|0.43.03]] || (2016-05-22):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.43.02|0.43.02]] || (2016-05-11):
| ''Hotfix'';
|-
| [[DF2014:Release information/0.43.01|0.43.01]] || (2016-05-09):
| ''Release''; Adventurers can create sites, make stone axes, fell trees, perform carpentry, and construct buildings; Fortress mode work orders can now specify start conditions, restart frequencies, and how many workshops can be used
|}

=== Dwarf Fortress v0.42 ===
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[DF2014:Release information/0.42.06|0.42.06]] || (2016-02-10):
| Can specify exact materials for jobs, make specific crafts, apply specific decorations, and even customize the details of art images; Adventurers can now do bone carving, complete with custom images
|-
| [[DF2014:Release information/0.42.05|0.42.05]] || (2016-01-17):
| Reputations for hunters and protection from bandits
|-
| [[DF2014:Release information/0.42.04|0.42.04]] || (2015-12-26):
| More varieties of [[animal people]] and giant animals, Vampire purges during worldgen, bugfixes
|-
| [[DF2014:Release information/0.42.03|0.42.03]] || (2015-12-12):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.42.02|0.42.02]] || (2015-12-05):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.42.01|0.42.01]] || (2015-12-01):
| ''Release''; introduced taverns, temples, and libraries, added new musical instruments and performance skills, introduced [[need]]s to replace dwarves going On Break, added visitors who can petition for fortress membership, scholars and historians can write books and spread knowledge, and drinking alcohol actually causes inebriation (and eventually fatal alcohol poisoning)
|}

=== Dwarf Fortress v0.40 ===
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[DF2014:Release information/0.40.24|0.40.24]] || (2015-01-07):
| ''Bugfix''; Misc. bugfixes; allowing 1x1 forts
|-
| [[DF2014:Release information/0.40.23|0.40.23]] || (2014-12-24):
| ''Bugfix''; Fixed farming job cancellations, armies camping forever, typos, and channeling bug
|-
| [[DF2014:Release information/0.40.22|0.40.22]] || (2014-12-21):
| ''Bugfix''; Fixed multi-item jobs and toggle marker tweak
|-
| [[DF2014:Release information/0.40.21|0.40.21]] || (2014-12-19):
| ''Hotfix''; Fixed a crash bug and other issues
|-
| [[DF2014:Release information/0.40.20|0.40.20]] || (2014-12-18):
| Job priorities rewrite; vein and cluster automining
|-
| [[DF2014:Release information/0.40.19|0.40.19]] || (2014-11-26):
| [[Gelding]] and related profession/skill/etc
|-
| [[DF2014:Release information/0.40.18|0.40.18]] || (2014-11-20):
| ''Hotfix''; Fixed a smelting issue on Windows
|-
| [[DF2014:Release information/0.40.17|0.40.17]] || (2014-11-19):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.16|0.40.16]] || (2014-11-12):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.15|0.40.15]] || (2014-11-05):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.14|0.40.14]] || (2014-10-25):
| Thought/emotion rewrite, stopped site invaders from always winning
|-
| [[DF2014:Release information/0.40.13|0.40.13]] || (2014-09-17):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.12|0.40.12]] || (2014-09-10):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.11|0.40.11]] || (2014-09-03):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.10|0.40.10]] || (2014-08-24):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.09|0.40.09]] || (2014-08-17):
| ''Bugfix''; Misc. bugfixes
|-
| [[DF2014:Release information/0.40.08|0.40.08]] || (2014-08-11):
| ''Hotfix''; Fixed a crash bug and issues with constructions
|-
| [[DF2014:Release information/0.40.07|0.40.07]] || (2014-08-10):
| ''Bugfix''; AI and invasion fixes
|-
| [[DF2014:Release information/0.40.06|0.40.06]] || (2014-08-03):
| ''Bugfix''; stack bugfixes.
|-
| [[DF2014:Release information/0.40.05|0.40.05]] || (2014-07-27):
| ''Bugfix''; fixed large world slowdown, decreased rampant tree growth, many old and new bugfixes.
|-
| [[DF2014:Release information/0.40.04|0.40.04]] || (2014-07-20):
| ''Bugfix''; several crash fixes, made saplings grow properly.
|-
| [[DF2014:Release information/0.40.03|0.40.03]] || (2014-07-13):
| ''Bugfix''; broke save game compatibility again due to more save corruption, several crash fixes.
|-
| [[DF2014:Release information/0.40.02|0.40.02]] || (2014-07-10):
| ''Bugfix''; broke save game compatibility due to save corruption, several crash fixes.
|-
| [[DF2014:Release information/0.40.01|0.40.01]] || (2014-07-07):
| ''Release''; Introduced world generation running in the background while fortresses and adventurers progress, un-retiring of fortresses, multiple tile trees, climbing & jumping, and more.
|}

=== Dwarf Fortress v0.34 ===
In a [http://www.bay12games.com/dwarves/index.html devlog] entry for 2011-01-30, Threetoe announced plans for a series of nine numbered releases ("Short-term Goals" on the [http://www.bay12games.com/dwarves/dev.html dev page]) to finish off the long-planned "caravan" development arc. Release 1, improving towns and introducing markets, along with a variety of supernatural creature types, was predicted to have a version number of [http://www.bay12games.com/media/df_talk_14_transcript.html#14.16 0.33 or 0.34] and was released on Valentine's Day 2012 as version 0.34.01.

{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[v0.34:Release information/0.34.11|0.34.11]] || (2012-06-04):
| ''Bugfix''
|-
| [[v0.34:Release information/0.34.10|0.34.10]] || (2012-05-21):
| ''Bugfix''
|-
| [[v0.34:Release information/0.34.09|0.34.09]] || (2012-05-17):
| ''Bugfix''
|-
| [[v0.34:Release information/0.34.08|0.34.08]] || (2012-05-14):
| Hauling overhaul - minecarts and wheelbarrows, more accurate projectiles, reduced mining yields, advanced stockpile/workshop links
|-
| [[v0.34:Release information/0.34.07|0.34.07]] || (2012-03-30):
| ''Bugfix''
|-
| [[v0.34:Release information/0.34.06|0.34.06]] || (2012-03-23):
| Updates to animal training ([[dungeon master]] removed, having been nonfunctional since 0.31.01), return of good/evil trees and shrubs
|-
| [[v0.34:Release information/0.34.05|0.34.05]] || (2012-03-06):
| ''Bugfix''
|-
| [[v0.34:Release information/0.34.04|0.34.04]] || (2012-02-29):
| ''Hotfix''
|-
| [[v0.34:Release information/0.34.03|0.34.03]] || (2012-02-28):
| ''Bugfix''
|-
| [[v0.34:Release information/0.34.02|0.34.02]] || (2012-02-18):
| ''Bugfix''; broke save compatibility due to save corruption, numerous fixes for old issues
|-
| [[v0.34:Release information/0.34.01|0.34.01]] || (2012-02-14):
| Introduction of human cities (shops, marketplaces, sewers, dungeons) and tombs, addition of [[interaction]]s ([[necromancer]]s, [[werebeast]]s, [[vampire]]s, etc.), historical migrants, truly evil regions, updated [[justice]] system,
|}

=== Dwarf Fortress v0.31 ===
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[v0.31:Release information/0.31.25|0.31.25]] || (2011-03-28):
| ''Hotfix'' -- Final update of version 0.31.
|-
| [[v0.31:Release information/0.31.24|0.31.24]] || (2011-03-27):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.23|0.31.23]] || (2011-03-26):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.22|0.31.22]] || (2011-03-24):
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.21|0.31.21]] || (2011-03-06):
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.20|0.31.20]] || (2011-03-06):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.19|0.31.19]] || (2011-02-16):
| Worldgen starvation, usually wiping out kobolds; grazing; ceramics; jugs, pots, nest boxes, beehives (and bees); site finder changes. Last major 0.31 release, and the (unnumbered) beginning of the caravan arc series.
|-
| [[v0.31:Release information/0.31.18|0.31.18]] || (2010-11-16):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.17|0.31.17]] || (2010-11-11):
| Bandits, Night Creatures, Bogeyman, Adventure mode improvements, combat aiming, castles
|-
| [[v0.31:Release information/0.31.16|0.31.16]] || (2010-10-04):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.15|0.31.15]] || (2010-10-03):
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.14|0.31.14]] || (2010-09-23):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.13|0.31.13]] || (2010-09-15):
| Entity populations, sprawl, river density tweaking, TrueType font support
|-
| [[v0.31:Release information/0.31.12|0.31.12]] || (2010-07-25):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.11|0.31.11]] || (2010-07-23):
| Art of deities
|-
| [[v0.31:Release information/0.31.10|0.31.10]] || (2010-07-11):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.09|0.31.09]] || (2010-07-10):
| Adventure mode knapping and butchery, combat improvements
|-
| [[v0.31:Release information/0.31.08|0.31.08]] || (2010-06-19):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.07|0.31.07]] || (2010-06-19):
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.06|0.31.06]] || (2010-06-09):
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.05|0.31.05]] || (2010-06-04):
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.04|0.31.04]] || (2010-05-16):
| Merge with the 40d19 branch
|-
| [[v0.31:Release information/0.31.03|0.31.03]] || (2010-04-12):
| Ability to create undead in arena
|-
| [[v0.31:Release information/0.31.02|0.31.02]] || (2010-04-08):
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.01|0.31.01]] || (2010-04-01):
| Overhaul of many aspects of the game, first 2010 release
|}

=== 3D Version (before 2010) ===
[[40d:Release information/''Branch'':|''Branch'':]] 0.28.181.40d2 thru 0.28.181.40d19: OpenGL optimizations, macros, zooming

{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[40d:Release information/0.28.181.40d|0.28.181.40d]] || (2008-09-06):
| ''Bugfix''; [[40d:Cat cancels Store Item in Stockpile: Too injured|Cat bug introduced]]
|-
| [[40d:Release information/0.28.181.40c|0.28.181.40c]] || (2008-08-21):
| ''Hotfix'', partial print now allows specifying a frame count
|-
| [[40d:Release information/0.28.181.40b|0.28.181.40b]] || (2008-08-20):
| Partial print, windowed/fullscreen gridsizes
|-
| [[40d:Release information/0.28.181.40a|0.28.181.40a]] || (2008-08-18):
| Embark profiles added, [[note]]s extended to embark map, customizable forbid [[orders]] added (used ammunition, dead creatures' possessions, etc.), and dwarves now try to store items in partially-filled containers instead of empty ones
|-
| [[40d:Release information/0.28.181.39f|0.28.181.39f]] || (2008-08-09):
| [[Custom grid]] sizes added
|-
| [[40d:Release information/0.28.181.39e|0.28.181.39e]] || (2008-07-23):
| ''Hotfix''
|-
| [[40d:Release information/0.28.181.39d|0.28.181.39d]] || (2008-07-23):
| Added [[Site finder]], can display hidden map features when choosing a site, [[Note]] support implemented, and worldgen presets added
|-
| [[40d:Release information/0.28.181.39c|0.28.181.39c]] || (2008-07-16):
| ''Hotfix''
|-
| [[40d:Release information/0.28.181.39b|0.28.181.39b]] || (2008-07-14):
| ''Hotfix''; trees in [[Elf|Elven]] forest retreats no longer have names
|-
| [[40d:Release information/0.28.181.39a|0.28.181.39a]] || (2008-07-13):
| Lots of worldgen changes, including ethics (leading to wars and conquered sites), dynamic era naming, worldgen roads/bridges/tunnels, megabeasts being killed during worldgen, megabeasts being undead; cats and trained animals are now named on adoption, human weapon stores stock more stuff (including ammo), placing [[construction]]s now destroys engravings, and flying creatures no longer give birth in mid-air
|-
| [[40d:Release information/0.27.176.38c|0.27.176.38c]] || (2008-02-24):
| ''Bugfix''
|-
| [[40d:Release information/0.27.176.38b|0.27.176.38b]] || (2008-02-23):
| First Macintosh-compatible release; Dwarves no longer carry their artifacts around, booze food no longer melts, worlds can now have custom sizes
|-
| [[40d:Release information/0.27.176.38a|0.27.176.38a]] || (2008-02-15):
| Magma pipes now refill, ZERO_RENT and BABY_CHILD_CAP init.txt options were added, strange moods no longer convert workshops, metal crossbows now made by [[weaponsmith]]s instead of [[bowyer]]s, dwarves chat and make friends/grudges and get married, unhappy thoughts from [[masterpiece]] destruction are now reduced based on the number of masterpieces the dwarf has made, and plants can now drown in deep water
|-
| [[40d:Release information/0.27.173.38a|0.27.173.38a]] || (2008-02-04):
| [[Sphere]]s added, lots of new entity tags, numerous worldgen improvements, religions implemented, undead [[ruin]]s removed
|-
| [[40d:Release information/0.27.169.33g|0.27.169.33g]] || (2007-12-21):
| Mud no longer dries up during winter, occupied cages are named according to their contents, brand new "Bring to depot" interface, [[strange mood]]s no longer require glass until you actually make some
|-
| [[40d:Release information/0.27.169.33f|0.27.169.33f]] || (2007-12-14):
| ''Bugfix''; mud and blood no longer spread, auto-[[forbid]] fired ammunition, donkey/horse foals are now named properly, graphics sets can now use custom tiles for appointed nobles, and flux stones now have a value of 2 again.
|-
| [[40d:Release information/0.27.169.33e|0.27.169.33e]] || (2007-12-08):
| ''Bugfix''; in particular, nobles no longer order themselves to be punished for failed mandates, donkeys can now breed, most types of vermin no longer have bones, and most types of fish no longer have lungs or throats
|-
| [[40d:Release information/0.27.169.33d|0.27.169.33d]] || (2007-11-30):
| ''Bugfix''
|-
| [[40d:Release information/0.27.169.33c|0.27.169.33c]] || (2007-11-23):
| Animals screen now labels war dogs and hunting dogs correctly, [[sliver barb]]s now have seeds, and process priority can now be configured in init.txt
|-
| [[40d:Release information/0.27.169.33b|0.27.169.33b]] || (2007-11-16):
| [[Carp]] and other fish no longer gain [[swimming]] skill (making them ''slightly'' less dangerous), and various ore types now properly show up as '*' when mined.
|-
| [[40d:Release information/0.27.169.33a|0.27.169.33a]] || (2007-11-01):
| added [[wood]]en [[block]]s, renamed aluminum ore to "native aluminum", [[mountain gnome]]s and [[dark gnome]]s no longer butcherable
|-
| [[40d:Release information/0.27.169.32a|0.27.169.32a]] || (2007-10-29):
| The very first fully 3D version
|}

=== 2D Version ===
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[23a:Release information/0.23.130.23a|0.23.130.23a]] || (2007-01-18):
| ''Hotfix'' - Final version
|-
| [[23a:Release information/0.23.125.23b|0.23.125.23b]] || (2007-01-16):
| ''Hotfix''
|-
| [[23a:Release information/0.23.125.23a|0.23.125.23a]] || (2007-01-16):
| Temperature support was further improved, population/FPS caps were added, coffins could now be restricted to only dwarves or only pets, and animals could now be marked for slaughter from their {{K|v}}-{{K|p}} screen. Spirits of fire also got a '''lot''' hotter. For some reason, [[horse]]s are now made of [[iron]].
|-
| [[23a:Release information/0.22.123.23a|0.22.123.23a]] || (2006-12-21):
| ''Hotfix''
|-
| [[23a:Release information/0.22.123.23a|0.22.123.23a]] || (2006-12-21):
| More workshop orders were added - auto collect webs, auto slaughter, auto butcher, auto tan; male cows are now called bulls, and whips can no longer get stuck in opponents
|-
| [[23a:Release information/0.22.121.23b|0.22.121.23b]] || (2006-12-16):
| The ability to disable temperature and weather were added (to boost FPS)
|-
| [[23a:Release information/0.22.121.23a|0.22.121.23a]] || (2006-12-14):
| Bins could now be made from metal, and the embark screen now described your biome and listed what civilizations were nearby
|-
| [[23a:Release information/0.22.120.23b|0.22.120.23b]] || (2006-12-10):
| Improved temperature support was added
|-
| [[23a:Release information/0.22.120.23a|0.22.120.23a]] || (2006-11-23):
| The ability to use custom [[graphics sets]] was added
|-
| [[23a:Release information/0.22.110.23c|0.22.110.23c]] || (2006-11-17):
| ''Hotfix''
|-
| [[23a:Release information/0.22.110.23b|0.22.110.23b]] || (2006-11-15):
| ''Hotfix''
|-
| [[23a:Release information/0.22.110.23a|0.22.110.23a]] || (2006-11-17):
| [[Dye]]s and dyeing were implemented, allowed sewing cloth/leather images into goods, as well as more detailed [[decoration|art]] (historical figures and events, special shapes); standing orders now allowed auto collecting webs and only using dyed cloth
|-
| [[23a:Release information/0.22.110.22f|0.22.110.22f]] || (2006-11-03):
| ''Bugfix''; additionally, butterflies, fireflies, and dragonflies can no longer be kept as pets. [[Boatmurdered]] began in this version.
|-
| [[23a:Release information/0.22.110.22e|0.22.110.22e]] || (2006-10-29):
| ''Hotfix''
|-
| [[23a:Release information/0.22.110.22d|0.22.110.22d]] || (2006-10-29):
| ''Hotfix''
|-
| [[23a:Release information/0.22.110.22c|0.22.110.22c]] || (2006-10-29):
| Custom [[stockpile]]s were added (previously, there were only 16 basic stockpile types; things like [[potash]] would be stored with your metal bars and you could not force [[seed]]s to be kept near the farm).
|-
| [[23a:Release information/0.22.110.22b|0.22.110.22b]] || (2006-10-21):
| ''Hotfix''
|-
| [[23a:Release information/0.22.110.22a|0.22.110.22a]] || (2006-10-21):
| Inventory system changes (most notably, gloves and boots were split into two items (left & right for gloves))
|-
| [[23a:Release information/0.22.107.21a|0.22.107.21a]] || (2006-10-02):
| Various changes to [[adventurer mode]] - guards and families, plus "." as a wait key
|-
| [[23a:Release information/0.21.105.21a|0.21.105.21a]] || (2006-09-25):
| ''Hotfix''
|-
| [[23a:Release information/0.21.104.21c|0.21.104.21c]] || (2006-09-25):
| Making potash no longer required making ashes into lye first.
|-
| [[23a:Release information/0.21.104.21b|0.21.104.21b]] || (2006-09-16):
| Workshop profiles were added, along with showing genders on the Animal status screen
|-
| [[23a:Release information/0.21.104.21a|0.21.104.21a]] || (2006-09-08):
| [[Designation|Designating]] with the mouse was added
|-
| [[23a:Release information/0.21.104.19d|0.21.104.19d]] || (2006-09-02):
| ''Bugfix''
|-
| [[23a:Release information/0.21.104.19c|0.21.104.19c]] || (2006-09-02):
| The ability to hide engravings was added, announcement consolidation (x15), seasonal blood cleanup was temporarily added (and would remain until version 0.31)
|-
| [[23a:Release information/0.21.104.19b|0.21.104.19b]] || (2006-08-27):
| ''Bugfix''
|-
| [[23a:Release information/0.21.104.19a|0.21.104.19a]] || (2006-08-27):
| The ability to "chasm" items was added (complete with attacks from chasm creatures as a result), as well as butchering cats
|-
| [[23a:Release information/0.21.102.19a|0.21.102.19a]] || (2006-08-24):
| Dwarves could now have custom nicknames and professions, fullscreen could be toggled, starting animals would have mixed genders, horses could breed
|-
| [[23a:Release information/0.21.101.19d|0.21.101.19d]] || (2006-08-21):
| ''Bugfix''
|-
| [[23a:Release information/0.21.101.19c|0.21.101.19c]] || (2006-08-20):
| ''Bugfix''
|-
| [[23a:Release information/0.21.101.19b|0.21.101.19b]] || (2006-08-20):
| ''Bugfix''
|-
| [[23a:Release information/0.21.101.19a|0.21.101.19a]] || (2006-08-19):
| Adventurers could now have custom first names
|-
| [[23a:Release information/0.21.100.19a|0.21.100.19a]] || (2006-08-16):
| Gender symbol was added to unit views, config options for disabling sound and the intro movie, command-line world generation, ability to export local map
|-
| [[23a:Release information/0.21.95.19c|0.21.95.19c]] || (2006-08-14):
| Farm plot fertilization could be controlled directly
|-
| [[23a:Release information/0.21.95.19b|0.21.95.19b]] || (2006-08-13):
| ''Bugfix''
|-
| [[23a:Release information/0.21.95.19a|0.21.95.19a]] || (2006-08-12):
| ''Bugfix''
|-
| [[23a:Release information/0.21.93.19c|0.21.93.19c]] || (2006-08-10):
| ''Bugfix''
|-
| [[23a:Release information/0.21.93.19b|0.21.93.19b]] || (2006-08-10):
| ''Bugfix''
|-
| [[23a:Release information/0.21.93.19a|0.21.93.19a]] || (2006-08-08):
| Initial public release
|}

== Bugs ==
Please report bugs on the [https://dwarffortress.mantishub.io/ official bug tracker], and optionally add them to [[Known bugs and issues]]. Please do not add them to this page.

Release information

2023-01-06T19:16:29Z

Jan: /* Version History */

{{migrated article}}
{{Quality|Unrated}}
{{release notes}}{{av}}

The first version in this release cycle, '''DF 50.01''', was released on '''December 6, 2022'''. The latest version is '''{{current/version}}''', released on '''{{current/lastupdate}}'''. The changes in each version are listed in the sidebar to the right.

Version 50.01 was the first version of Dwarf Fortress released on [https://steamcommunity.com/app/975370/ Steam]. It was also the first version to use a new versioning scheme: the leading "0." present in all previous versions of DF was removed from the version number.

As with all major releases, version 50.01 broke [[save compatibility]] with old versions.

== Version History ==
=== Dwarf Fortress v50 ===
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[Release information/50.05|50.05]] || (2023-01-05):
| ''Bugfixes and optimizations''
|-
| [[Release information/50.04|50.04]] || (2022-12-22):
| '''Classic release''': released the free [[Classic]] version on [https://www.bay12games.com/dwarves/ bay12games.com], and enabled classic mode in the Premium version. Added ability to advance time by one frame, and assign everyone to a burrow.
|-
| [[Release information/50.03|50.03]] || (2022-12-12):
| ''Premium-only bugfixes''. Improved UX for selecting building materials.
|-
| [[Release information/50.02|50.02]] || (2022-12-08):
| ''Premium-only bugfixes''
|-
| [[Release information/50.01|50.01]] || (2022-12-06):
| '''Premium release''': launched the paid [[Premium]] version on Steam and itch.io. Introduced [[graphics]], full [[Mouse control|mouse support]], a new user [[interface]], tutorials, and new [[soundtrack|music]] and sound effects. A number of features from v0.47 were lost in 50.01 (see [[Missing features]]).
|}

=== Dwarf Fortress v0.47 ===
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[DF2014:Release information/0.47.05|0.47.05]] || (2021-01-28):
| ''Bugfix''
|-
| [[DF2014:Release information/0.47.04|0.47.04]] || (2020-02-29):
| ''Bugfix''
|-
| [[DF2014:Release information/0.47.03|0.47.03]] || (2020-02-16):
| ''Bugfix''
|-
| [[DF2014:Release information/0.47.02|0.47.02]] || (2020-02-06):
| ''Bugfix''
|-
| [[DF2014:Release information/0.47.01|0.47.01]] || (2020-01-29):
| ''Release'': introduced creation of [[guildhall]]s and [[temple]]s. Introduced [[traitor]]s and [[villain]]s.
|}

=== Dwarf Fortress v0.44 ===
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[DF2014:Release information/0.44.12|0.44.12]] || (2018-06-23):
| ''Hotfix'';
|-
| [[DF2014:Release information/0.44.11|0.44.11]] || (2018-06-23):
| Civilizations create nearby sites and associate them with your fortress, can request/send workers, long-term memories can lead to personality changes
|-
| [[DF2014:Release information/0.44.10|0.44.10]] || (2018-05-05):
| Dwarves now have short-term and long-term memories of emotional events, Adventurer mode log improved
|-
| [[DF2014:Release information/0.44.09|0.44.09]] || (2018-04-01):
| ''Hotfix'';
|-
| [[DF2014:Release information/0.44.08|0.44.08]] || (2018-03-29):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.44.07|0.44.07]] || (2018-03-12):
| ''Hotfix'';
|-
| [[DF2014:Release information/0.44.06|0.44.06]] || (2018-03-09):
| Raids can pillage/raze sites and demand tribute, will gain skills (e.g. military tactics) during missions
|-
| [[DF2014:Release information/0.44.05|0.44.05]] || (2018-01-14):
| ''Hotfix'';
|-
| [[DF2014:Release information/0.44.04|0.44.04]] || (2018-01-10):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.44.03|0.44.03]] || (2017-12-25):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.44.02|0.44.02]] || (2017-11-23):
| ''Hotfix'';
|-
| [[DF2014:Release information/0.44.01|0.44.01]] || (2017-11-22):
| ''Release''; can now send raids to other sites, build museums using pedestals and display cases, artifacts created during worldgen, civilizations can send spies to gather information on artifacts
|}

=== Dwarf Fortress v0.43 ===
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[DF2014:Release information/0.43.05|0.43.05]] || (2016-06-20):
| '''64-bit support''', bugfixes
|-
| [[DF2014:Release information/0.43.04|0.43.04]] || (2016-06-20):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.43.03|0.43.03]] || (2016-05-22):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.43.02|0.43.02]] || (2016-05-11):
| ''Hotfix'';
|-
| [[DF2014:Release information/0.43.01|0.43.01]] || (2016-05-09):
| ''Release''; Adventurers can create sites, make stone axes, fell trees, perform carpentry, and construct buildings; Fortress mode work orders can now specify start conditions, restart frequencies, and how many workshops can be used
|}

=== Dwarf Fortress v0.42 ===
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[DF2014:Release information/0.42.06|0.42.06]] || (2016-02-10):
| Can specify exact materials for jobs, make specific crafts, apply specific decorations, and even customize the details of art images; Adventurers can now do bone carving, complete with custom images
|-
| [[DF2014:Release information/0.42.05|0.42.05]] || (2016-01-17):
| Reputations for hunters and protection from bandits
|-
| [[DF2014:Release information/0.42.04|0.42.04]] || (2015-12-26):
| More varieties of [[animal people]] and giant animals, Vampire purges during worldgen, bugfixes
|-
| [[DF2014:Release information/0.42.03|0.42.03]] || (2015-12-12):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.42.02|0.42.02]] || (2015-12-05):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.42.01|0.42.01]] || (2015-12-01):
| ''Release''; introduced taverns, temples, and libraries, added new musical instruments and performance skills, introduced [[need]]s to replace dwarves going On Break, added visitors who can petition for fortress membership, scholars and historians can write books and spread knowledge, and drinking alcohol actually causes inebriation (and eventually fatal alcohol poisoning)
|}

=== Dwarf Fortress v0.40 ===
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[DF2014:Release information/0.40.24|0.40.24]] || (2015-01-07):
| ''Bugfix''; Misc. bugfixes; allowing 1x1 forts
|-
| [[DF2014:Release information/0.40.23|0.40.23]] || (2014-12-24):
| ''Bugfix''; Fixed farming job cancellations, armies camping forever, typos, and channeling bug
|-
| [[DF2014:Release information/0.40.22|0.40.22]] || (2014-12-21):
| ''Bugfix''; Fixed multi-item jobs and toggle marker tweak
|-
| [[DF2014:Release information/0.40.21|0.40.21]] || (2014-12-19):
| ''Hotfix''; Fixed a crash bug and other issues
|-
| [[DF2014:Release information/0.40.20|0.40.20]] || (2014-12-18):
| Job priorities rewrite; vein and cluster automining
|-
| [[DF2014:Release information/0.40.19|0.40.19]] || (2014-11-26):
| [[Gelding]] and related profession/skill/etc
|-
| [[DF2014:Release information/0.40.18|0.40.18]] || (2014-11-20):
| ''Hotfix''; Fixed a smelting issue on Windows
|-
| [[DF2014:Release information/0.40.17|0.40.17]] || (2014-11-19):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.16|0.40.16]] || (2014-11-12):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.15|0.40.15]] || (2014-11-05):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.14|0.40.14]] || (2014-10-25):
| Thought/emotion rewrite, stopped site invaders from always winning
|-
| [[DF2014:Release information/0.40.13|0.40.13]] || (2014-09-17):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.12|0.40.12]] || (2014-09-10):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.11|0.40.11]] || (2014-09-03):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.10|0.40.10]] || (2014-08-24):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.09|0.40.09]] || (2014-08-17):
| ''Bugfix''; Misc. bugfixes
|-
| [[DF2014:Release information/0.40.08|0.40.08]] || (2014-08-11):
| ''Hotfix''; Fixed a crash bug and issues with constructions
|-
| [[DF2014:Release information/0.40.07|0.40.07]] || (2014-08-10):
| ''Bugfix''; AI and invasion fixes
|-
| [[DF2014:Release information/0.40.06|0.40.06]] || (2014-08-03):
| ''Bugfix''; stack bugfixes.
|-
| [[DF2014:Release information/0.40.05|0.40.05]] || (2014-07-27):
| ''Bugfix''; fixed large world slowdown, decreased rampant tree growth, many old and new bugfixes.
|-
| [[DF2014:Release information/0.40.04|0.40.04]] || (2014-07-20):
| ''Bugfix''; several crash fixes, made saplings grow properly.
|-
| [[DF2014:Release information/0.40.03|0.40.03]] || (2014-07-13):
| ''Bugfix''; broke save game compatibility again due to more save corruption, several crash fixes.
|-
| [[DF2014:Release information/0.40.02|0.40.02]] || (2014-07-10):
| ''Bugfix''; broke save game compatibility due to save corruption, several crash fixes.
|-
| [[DF2014:Release information/0.40.01|0.40.01]] || (2014-07-07):
| ''Release''; Introduced world generation running in the background while fortresses and adventurers progress, un-retiring of fortresses, multiple tile trees, climbing & jumping, and more.
|}

=== Dwarf Fortress v0.34 ===
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note

In a [http://www.bay12games.com/dwarves/index.html devlog] entry for 2011-01-30, Threetoe announced plans for a series of nine numbered releases ("Short-term Goals" on the [http://www.bay12games.com/dwarves/dev.html dev page]) to finish off the long-planned "caravan" development arc. Release 1, improving towns and introducing markets, along with a variety of supernatural creature types, was predicted to have a version number of [http://www.bay12games.com/media/df_talk_14_transcript.html#14.16 0.33 or 0.34] and was released on Valentine's Day 2012 as version 0.34.01.
|-
| [[v0.34:Release information/0.34.11|0.34.11]] || (2012-06-04):
| ''Bugfix''
|-
| [[v0.34:Release information/0.34.10|0.34.10]] || (2012-05-21):
| ''Bugfix''
|-
| [[v0.34:Release information/0.34.09|0.34.09]] || (2012-05-17):
| ''Bugfix''
|-
| [[v0.34:Release information/0.34.08|0.34.08]] || (2012-05-14):
| Hauling overhaul - minecarts and wheelbarrows, more accurate projectiles, reduced mining yields, advanced stockpile/workshop links
|-
| [[v0.34:Release information/0.34.07|0.34.07]] || (2012-03-30):
| ''Bugfix''
|-
| [[v0.34:Release information/0.34.06|0.34.06]] || (2012-03-23):
| Updates to animal training ([[dungeon master]] removed, having been nonfunctional since 0.31.01), return of good/evil trees and shrubs
|-
| [[v0.34:Release information/0.34.05|0.34.05]] || (2012-03-06):
| ''Bugfix''
|-
| [[v0.34:Release information/0.34.04|0.34.04]] || (2012-02-29):
| ''Hotfix''
|-
| [[v0.34:Release information/0.34.03|0.34.03]] || (2012-02-28):
| ''Bugfix''
|-
| [[v0.34:Release information/0.34.02|0.34.02]] || (2012-02-18):
| ''Bugfix''; broke save compatibility due to save corruption, numerous fixes for old issues
|-
| [[v0.34:Release information/0.34.01|0.34.01]] || (2012-02-14):
| Introduction of human cities (shops, marketplaces, sewers, dungeons) and tombs, addition of [[interaction]]s ([[necromancer]]s, [[werebeast]]s, [[vampire]]s, etc.), historical migrants, truly evil regions, updated [[justice]] system,
|}

=== Dwarf Fortress v0.31 ===
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[v0.31:Release information/0.31.25|0.31.25]] || (2011-03-28):
| ''Hotfix'' -- Final update of version 0.31.
|-
| [[v0.31:Release information/0.31.24|0.31.24]] || (2011-03-27):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.23|0.31.23]] || (2011-03-26):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.22|0.31.22]] || (2011-03-24):
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.21|0.31.21]] || (2011-03-06):
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.20|0.31.20]] || (2011-03-06):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.19|0.31.19]] || (2011-02-16):
| Worldgen starvation, usually wiping out kobolds; grazing; ceramics; jugs, pots, nest boxes, beehives (and bees); site finder changes. Last major 0.31 release, and the (unnumbered) beginning of the caravan arc series.
|-
| [[v0.31:Release information/0.31.18|0.31.18]] || (2010-11-16):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.17|0.31.17]] || (2010-11-11):
| Bandits, Night Creatures, Bogeyman, Adventure mode improvements, combat aiming, castles
|-
| [[v0.31:Release information/0.31.16|0.31.16]] || (2010-10-04):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.15|0.31.15]] || (2010-10-03):
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.14|0.31.14]] || (2010-09-23):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.13|0.31.13]] || (2010-09-15):
| Entity populations, sprawl, river density tweaking, TrueType font support
|-
| [[v0.31:Release information/0.31.12|0.31.12]] || (2010-07-25):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.11|0.31.11]] || (2010-07-23):
| Art of deities
|-
| [[v0.31:Release information/0.31.10|0.31.10]] || (2010-07-11):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.09|0.31.09]] || (2010-07-10):
| Adventure mode knapping and butchery, combat improvements
|-
| [[v0.31:Release information/0.31.08|0.31.08]] || (2010-06-19):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.07|0.31.07]] || (2010-06-19):
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.06|0.31.06]] || (2010-06-09):
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.05|0.31.05]] || (2010-06-04):
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.04|0.31.04]] || (2010-05-16):
| Merge with the 40d19 branch
|-
| [[v0.31:Release information/0.31.03|0.31.03]] || (2010-04-12):
| Ability to create undead in arena
|-
| [[v0.31:Release information/0.31.02|0.31.02]] || (2010-04-08):
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.01|0.31.01]] || (2010-04-01):
| Overhaul of many aspects of the game, first 2010 release
|}

=== 3D Version (before 2010) ===
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[40d:Release information/''Branch'':|''Branch'':]] 0.28.181.40d2 thru 0.28.181.40d19: OpenGL optimizations, macros, zooming
|-
| [[40d:Release information/0.28.181.40d|0.28.181.40d]] || (2008-09-06):
| ''Bugfix''; [[40d:Cat cancels Store Item in Stockpile: Too injured|Cat bug introduced]]
|-
| [[40d:Release information/0.28.181.40c|0.28.181.40c]] || (2008-08-21):
| ''Hotfix'', partial print now allows specifying a frame count
|-
| [[40d:Release information/0.28.181.40b|0.28.181.40b]] || (2008-08-20):
| Partial print, windowed/fullscreen gridsizes
|-
| [[40d:Release information/0.28.181.40a|0.28.181.40a]] || (2008-08-18):
| Embark profiles added, [[note]]s extended to embark map, customizable forbid [[orders]] added (used ammunition, dead creatures' possessions, etc.), and dwarves now try to store items in partially-filled containers instead of empty ones
|-
| [[40d:Release information/0.28.181.39f|0.28.181.39f]] || (2008-08-09):
| [[Custom grid]] sizes added
|-
| [[40d:Release information/0.28.181.39e|0.28.181.39e]] || (2008-07-23):
| ''Hotfix''
|-
| [[40d:Release information/0.28.181.39d|0.28.181.39d]] || (2008-07-23):
| Added [[Site finder]], can display hidden map features when choosing a site, [[Note]] support implemented, and worldgen presets added
|-
| [[40d:Release information/0.28.181.39c|0.28.181.39c]] || (2008-07-16):
| ''Hotfix''
|-
| [[40d:Release information/0.28.181.39b|0.28.181.39b]] || (2008-07-14):
| ''Hotfix''; trees in [[Elf|Elven]] forest retreats no longer have names
|-
| [[40d:Release information/0.28.181.39a|0.28.181.39a]] || (2008-07-13):
| Lots of worldgen changes, including ethics (leading to wars and conquered sites), dynamic era naming, worldgen roads/bridges/tunnels, megabeasts being killed during worldgen, megabeasts being undead; cats and trained animals are now named on adoption, human weapon stores stock more stuff (including ammo), placing [[construction]]s now destroys engravings, and flying creatures no longer give birth in mid-air
|-
| [[40d:Release information/0.27.176.38c|0.27.176.38c]] || (2008-02-24):
| ''Bugfix''
|-
| [[40d:Release information/0.27.176.38b|0.27.176.38b]] || (2008-02-23):
| First Macintosh-compatible release; Dwarves no longer carry their artifacts around, booze food no longer melts, worlds can now have custom sizes
|-
| [[40d:Release information/0.27.176.38a|0.27.176.38a]] || (2008-02-15):
| Magma pipes now refill, ZERO_RENT and BABY_CHILD_CAP init.txt options were added, strange moods no longer convert workshops, metal crossbows now made by [[weaponsmith]]s instead of [[bowyer]]s, dwarves chat and make friends/grudges and get married, unhappy thoughts from [[masterpiece]] destruction are now reduced based on the number of masterpieces the dwarf has made, and plants can now drown in deep water
|-
| [[40d:Release information/0.27.173.38a|0.27.173.38a]] || (2008-02-04):
| [[Sphere]]s added, lots of new entity tags, numerous worldgen improvements, religions implemented, undead [[ruin]]s removed
|-
| [[40d:Release information/0.27.169.33g|0.27.169.33g]] || (2007-12-21):
| Mud no longer dries up during winter, occupied cages are named according to their contents, brand new "Bring to depot" interface, [[strange mood]]s no longer require glass until you actually make some
|-
| [[40d:Release information/0.27.169.33f|0.27.169.33f]] || (2007-12-14):
| ''Bugfix''; mud and blood no longer spread, auto-[[forbid]] fired ammunition, donkey/horse foals are now named properly, graphics sets can now use custom tiles for appointed nobles, and flux stones now have a value of 2 again.
|-
| [[40d:Release information/0.27.169.33e|0.27.169.33e]] || (2007-12-08):
| ''Bugfix''; in particular, nobles no longer order themselves to be punished for failed mandates, donkeys can now breed, most types of vermin no longer have bones, and most types of fish no longer have lungs or throats
|-
| [[40d:Release information/0.27.169.33d|0.27.169.33d]] || (2007-11-30):
| ''Bugfix''
|-
| [[40d:Release information/0.27.169.33c|0.27.169.33c]] || (2007-11-23):
| Animals screen now labels war dogs and hunting dogs correctly, [[sliver barb]]s now have seeds, and process priority can now be configured in init.txt
|-
| [[40d:Release information/0.27.169.33b|0.27.169.33b]] || (2007-11-16):
| [[Carp]] and other fish no longer gain [[swimming]] skill (making them ''slightly'' less dangerous), and various ore types now properly show up as '*' when mined.
|-
| [[40d:Release information/0.27.169.33a|0.27.169.33a]] || (2007-11-01):
| added [[wood]]en [[block]]s, renamed aluminum ore to "native aluminum", [[mountain gnome]]s and [[dark gnome]]s no longer butcherable
|-
| [[40d:Release information/0.27.169.32a|0.27.169.32a]] || (2007-10-29):
| The very first fully 3D version
|}

=== 2D Version ===
{| class=wikitable
! style="width:85px"|Version
! style="width:100px"|Date of release
! Note
|-
| [[23a:Release information/0.23.130.23a|0.23.130.23a]] || (2007-01-18):
| ''Hotfix'' - Final version
|-
| [[23a:Release information/0.23.125.23b|0.23.125.23b]] || (2007-01-16):
| ''Hotfix''
|-
| [[23a:Release information/0.23.125.23a|0.23.125.23a]] || (2007-01-16):
| Temperature support was further improved, population/FPS caps were added, coffins could now be restricted to only dwarves or only pets, and animals could now be marked for slaughter from their {{K|v}}-{{K|p}} screen. Spirits of fire also got a '''lot''' hotter. For some reason, [[horse]]s are now made of [[iron]].
|-
| [[23a:Release information/0.22.123.23a|0.22.123.23a]] || (2006-12-21):
| ''Hotfix''
|-
| [[23a:Release information/0.22.123.23a|0.22.123.23a]] || (2006-12-21):
| More workshop orders were added - auto collect webs, auto slaughter, auto butcher, auto tan; male cows are now called bulls, and whips can no longer get stuck in opponents
|-
| [[23a:Release information/0.22.121.23b|0.22.121.23b]] || (2006-12-16):
| The ability to disable temperature and weather were added (to boost FPS)
|-
| [[23a:Release information/0.22.121.23a|0.22.121.23a]] || (2006-12-14):
| Bins could now be made from metal, and the embark screen now described your biome and listed what civilizations were nearby
|-
| [[23a:Release information/0.22.120.23b|0.22.120.23b]] || (2006-12-10):
| Improved temperature support was added
|-
| [[23a:Release information/0.22.120.23a|0.22.120.23a]] || (2006-11-23):
| The ability to use custom [[graphics sets]] was added
|-
| [[23a:Release information/0.22.110.23c|0.22.110.23c]] || (2006-11-17):
| ''Hotfix''
|-
| [[23a:Release information/0.22.110.23b|0.22.110.23b]] || (2006-11-15):
| ''Hotfix''
|-
| [[23a:Release information/0.22.110.23a|0.22.110.23a]] || (2006-11-17):
| [[Dye]]s and dyeing were implemented, allowed sewing cloth/leather images into goods, as well as more detailed [[decoration|art]] (historical figures and events, special shapes); standing orders now allowed auto collecting webs and only using dyed cloth
|-
| [[23a:Release information/0.22.110.22f|0.22.110.22f]] || (2006-11-03):
| ''Bugfix''; additionally, butterflies, fireflies, and dragonflies can no longer be kept as pets. [[Boatmurdered]] began in this version.
|-
| [[23a:Release information/0.22.110.22e|0.22.110.22e]] || (2006-10-29):
| ''Hotfix''
|-
| [[23a:Release information/0.22.110.22d|0.22.110.22d]] || (2006-10-29):
| ''Hotfix''
|-
| [[23a:Release information/0.22.110.22c|0.22.110.22c]] || (2006-10-29):
| Custom [[stockpile]]s were added (previously, there were only 16 basic stockpile types; things like [[potash]] would be stored with your metal bars and you could not force [[seed]]s to be kept near the farm).
|-
| [[23a:Release information/0.22.110.22b|0.22.110.22b]] || (2006-10-21):
| ''Hotfix''
|-
| [[23a:Release information/0.22.110.22a|0.22.110.22a]] || (2006-10-21):
| Inventory system changes (most notably, gloves and boots were split into two items (left & right for gloves))
|-
| [[23a:Release information/0.22.107.21a|0.22.107.21a]] || (2006-10-02):
| Various changes to [[adventurer mode]] - guards and families, plus "." as a wait key
|-
| [[23a:Release information/0.21.105.21a|0.21.105.21a]] || (2006-09-25):
| ''Hotfix''
|-
| [[23a:Release information/0.21.104.21c|0.21.104.21c]] || (2006-09-25):
| Making potash no longer required making ashes into lye first.
|-
| [[23a:Release information/0.21.104.21b|0.21.104.21b]] || (2006-09-16):
| Workshop profiles were added, along with showing genders on the Animal status screen
|-
| [[23a:Release information/0.21.104.21a|0.21.104.21a]] || (2006-09-08):
| [[Designation|Designating]] with the mouse was added
|-
| [[23a:Release information/0.21.104.19d|0.21.104.19d]] || (2006-09-02):
| ''Bugfix''
|-
| [[23a:Release information/0.21.104.19c|0.21.104.19c]] || (2006-09-02):
| The ability to hide engravings was added, announcement consolidation (x15), seasonal blood cleanup was temporarily added (and would remain until version 0.31)
|-
| [[23a:Release information/0.21.104.19b|0.21.104.19b]] || (2006-08-27):
| ''Bugfix''
|-
| [[23a:Release information/0.21.104.19a|0.21.104.19a]] || (2006-08-27):
| The ability to "chasm" items was added (complete with attacks from chasm creatures as a result), as well as butchering cats
|-
| [[23a:Release information/0.21.102.19a|0.21.102.19a]] || (2006-08-24):
| Dwarves could now have custom nicknames and professions, fullscreen could be toggled, starting animals would have mixed genders, horses could breed
|-
| [[23a:Release information/0.21.101.19d|0.21.101.19d]] || (2006-08-21):
| ''Bugfix''
|-
| [[23a:Release information/0.21.101.19c|0.21.101.19c]] || (2006-08-20):
| ''Bugfix''
|-
| [[23a:Release information/0.21.101.19b|0.21.101.19b]] || (2006-08-20):
| ''Bugfix''
|-
| [[23a:Release information/0.21.101.19a|0.21.101.19a]] || (2006-08-19):
| Adventurers could now have custom first names
|-
| [[23a:Release information/0.21.100.19a|0.21.100.19a]] || (2006-08-16):
| Gender symbol was added to unit views, config options for disabling sound and the intro movie, command-line world generation, ability to export local map
|-
| [[23a:Release information/0.21.95.19c|0.21.95.19c]] || (2006-08-14):
| Farm plot fertilization could be controlled directly
|-
| [[23a:Release information/0.21.95.19b|0.21.95.19b]] || (2006-08-13):
| ''Bugfix''
|-
| [[23a:Release information/0.21.95.19a|0.21.95.19a]] || (2006-08-12):
| ''Bugfix''
|-
| [[23a:Release information/0.21.93.19c|0.21.93.19c]] || (2006-08-10):
| ''Bugfix''
|-
| [[23a:Release information/0.21.93.19b|0.21.93.19b]] || (2006-08-10):
| ''Bugfix''
|-
| [[23a:Release information/0.21.93.19a|0.21.93.19a]] || (2006-08-08):
| Initial public release
|}

== Bugs ==
Please report bugs on the [https://dwarffortress.mantishub.io/ official bug tracker], and optionally add them to [[Known bugs and issues]]. Please do not add them to this page.

Release information

2023-01-06T19:11:12Z

Jan: /* Version History */

{{migrated article}}
{{Quality|Unrated}}
{{release notes}}{{av}}

The first version in this release cycle, '''DF 50.01''', was released on '''December 6, 2022'''. The latest version is '''{{current/version}}''', released on '''{{current/lastupdate}}'''. The changes in each version are listed in the sidebar to the right.

Version 50.01 was the first version of Dwarf Fortress released on [https://steamcommunity.com/app/975370/ Steam]. It was also the first version to use a new versioning scheme: the leading "0." present in all previous versions of DF was removed from the version number.

As with all major releases, version 50.01 broke [[save compatibility]] with old versions.

== Version History ==
=== Dwarf Fortress v50 ===
{| class=wikitable
|-
| [[Release information/50.05|50.05]] || (2023-01-05):
| ''Bugfixes and optimizations''
|-
| [[Release information/50.04|50.04]] || (2022-12-22):
| '''Classic release''': released the free [[Classic]] version on [https://www.bay12games.com/dwarves/ bay12games.com], and enabled classic mode in the Premium version. Added ability to advance time by one frame, and assign everyone to a burrow.
|-
| [[Release information/50.03|50.03]] || (2022-12-12):
| ''Premium-only bugfixes''. Improved UX for selecting building materials.
|-
| [[Release information/50.02|50.02]] || (2022-12-08):
| ''Premium-only bugfixes''
|-
| [[Release information/50.01|50.01]] || (2022-12-06):
| '''Premium release''': launched the paid [[Premium]] version on Steam and itch.io. Introduced [[graphics]], full [[Mouse control|mouse support]], a new user [[interface]], tutorials, and new [[soundtrack|music]] and sound effects. A number of features from v0.47 were lost in 50.01 (see [[Missing features]]).
|}

=== Dwarf Fortress v0.47 ===
{| class=wikitable
|-
| [[DF2014:Release information/0.47.05|0.47.05]] || (2021-01-28):
| ''Bugfix''
|-
| [[DF2014:Release information/0.47.04|0.47.04]] || (2020-02-29):
| ''Bugfix''
|-
| [[DF2014:Release information/0.47.03|0.47.03]] || (2020-02-16):
| ''Bugfix''
|-
| [[DF2014:Release information/0.47.02|0.47.02]] || (2020-02-06):
| ''Bugfix''
|-
| [[DF2014:Release information/0.47.01|0.47.01]] || (2020-01-29):
| ''Release'': introduced creation of [[guildhall]]s and [[temple]]s. Introduced [[traitor]]s and [[villain]]s.
|}

=== Dwarf Fortress v0.44 ===
{| class=wikitable
|-
| [[DF2014:Release information/0.44.12|0.44.12]] || (2018-06-23):
| ''Hotfix'';
|-
| [[DF2014:Release information/0.44.11|0.44.11]] || (2018-06-23):
| Civilizations create nearby sites and associate them with your fortress, can request/send workers, long-term memories can lead to personality changes
|-
| [[DF2014:Release information/0.44.10|0.44.10]] || (2018-05-05):
| Dwarves now have short-term and long-term memories of emotional events, Adventurer mode log improved
|-
| [[DF2014:Release information/0.44.09|0.44.09]] || (2018-04-01):
| ''Hotfix'';
|-
| [[DF2014:Release information/0.44.08|0.44.08]] || (2018-03-29):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.44.07|0.44.07]] || (2018-03-12):
| ''Hotfix'';
|-
| [[DF2014:Release information/0.44.06|0.44.06]] || (2018-03-09):
| Raids can pillage/raze sites and demand tribute, will gain skills (e.g. military tactics) during missions
|-
| [[DF2014:Release information/0.44.05|0.44.05]] || (2018-01-14):
| ''Hotfix'';
|-
| [[DF2014:Release information/0.44.04|0.44.04]] || (2018-01-10):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.44.03|0.44.03]] || (2017-12-25):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.44.02|0.44.02]] || (2017-11-23):
| ''Hotfix'';
|-
| [[DF2014:Release information/0.44.01|0.44.01]] || (2017-11-22):
| ''Release''; can now send raids to other sites, build museums using pedestals and display cases, artifacts created during worldgen, civilizations can send spies to gather information on artifacts
|}

=== Dwarf Fortress v0.43 ===
{| class=wikitable
|-
| [[DF2014:Release information/0.43.05|0.43.05]] || (2016-06-20):
| '''64-bit support''', bugfixes
|-
| [[DF2014:Release information/0.43.04|0.43.04]] || (2016-06-20):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.43.03|0.43.03]] || (2016-05-22):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.43.02|0.43.02]] || (2016-05-11):
| ''Hotfix'';
|-
| [[DF2014:Release information/0.43.01|0.43.01]] || (2016-05-09):
| ''Release''; Adventurers can create sites, make stone axes, fell trees, perform carpentry, and construct buildings; Fortress mode work orders can now specify start conditions, restart frequencies, and how many workshops can be used
|}

=== Dwarf Fortress v0.42 ===
{| class=wikitable
|-
| [[DF2014:Release information/0.42.06|0.42.06]] || (2016-02-10):
| Can specify exact materials for jobs, make specific crafts, apply specific decorations, and even customize the details of art images; Adventurers can now do bone carving, complete with custom images
|-
| [[DF2014:Release information/0.42.05|0.42.05]] || (2016-01-17):
| Reputations for hunters and protection from bandits
|-
| [[DF2014:Release information/0.42.04|0.42.04]] || (2015-12-26):
| More varieties of [[animal people]] and giant animals, Vampire purges during worldgen, bugfixes
|-
| [[DF2014:Release information/0.42.03|0.42.03]] || (2015-12-12):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.42.02|0.42.02]] || (2015-12-05):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.42.01|0.42.01]] || (2015-12-01):
| ''Release''; introduced taverns, temples, and libraries, added new musical instruments and performance skills, introduced [[need]]s to replace dwarves going On Break, added visitors who can petition for fortress membership, scholars and historians can write books and spread knowledge, and drinking alcohol actually causes inebriation (and eventually fatal alcohol poisoning)
|}

=== Dwarf Fortress v0.40 ===
{| class=wikitable
|-
| [[DF2014:Release information/0.40.24|0.40.24]] || (2015-01-07):
| ''Bugfix''; Misc. bugfixes; allowing 1x1 forts
|-
| [[DF2014:Release information/0.40.23|0.40.23]] || (2014-12-24):
| ''Bugfix''; Fixed farming job cancellations, armies camping forever, typos, and channeling bug
|-
| [[DF2014:Release information/0.40.22|0.40.22]] || (2014-12-21):
| ''Bugfix''; Fixed multi-item jobs and toggle marker tweak
|-
| [[DF2014:Release information/0.40.21|0.40.21]] || (2014-12-19):
| ''Hotfix''; Fixed a crash bug and other issues
|-
| [[DF2014:Release information/0.40.20|0.40.20]] || (2014-12-18):
| Job priorities rewrite; vein and cluster automining
|-
| [[DF2014:Release information/0.40.19|0.40.19]] || (2014-11-26):
| [[Gelding]] and related profession/skill/etc
|-
| [[DF2014:Release information/0.40.18|0.40.18]] || (2014-11-20):
| ''Hotfix''; Fixed a smelting issue on Windows
|-
| [[DF2014:Release information/0.40.17|0.40.17]] || (2014-11-19):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.16|0.40.16]] || (2014-11-12):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.15|0.40.15]] || (2014-11-05):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.14|0.40.14]] || (2014-10-25):
| Thought/emotion rewrite, stopped site invaders from always winning
|-
| [[DF2014:Release information/0.40.13|0.40.13]] || (2014-09-17):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.12|0.40.12]] || (2014-09-10):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.11|0.40.11]] || (2014-09-03):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.10|0.40.10]] || (2014-08-24):
| ''Bugfix'';
|-
| [[DF2014:Release information/0.40.09|0.40.09]] || (2014-08-17):
| ''Bugfix''; Misc. bugfixes
|-
| [[DF2014:Release information/0.40.08|0.40.08]] || (2014-08-11):
| ''Hotfix''; Fixed a crash bug and issues with constructions
|-
| [[DF2014:Release information/0.40.07|0.40.07]] || (2014-08-10):
| ''Bugfix''; AI and invasion fixes
|-
| [[DF2014:Release information/0.40.06|0.40.06]] || (2014-08-03):
| ''Bugfix''; stack bugfixes.
|-
| [[DF2014:Release information/0.40.05|0.40.05]] || (2014-07-27):
| ''Bugfix''; fixed large world slowdown, decreased rampant tree growth, many old and new bugfixes.
|-
| [[DF2014:Release information/0.40.04|0.40.04]] || (2014-07-20):
| ''Bugfix''; several crash fixes, made saplings grow properly.
|-
| [[DF2014:Release information/0.40.03|0.40.03]] || (2014-07-13):
| ''Bugfix''; broke save game compatibility again due to more save corruption, several crash fixes.
|-
| [[DF2014:Release information/0.40.02|0.40.02]] || (2014-07-10):
| ''Bugfix''; broke save game compatibility due to save corruption, several crash fixes.
|-
| [[DF2014:Release information/0.40.01|0.40.01]] || (2014-07-07):
| ''Release''; Introduced world generation running in the background while fortresses and adventurers progress, un-retiring of fortresses, multiple tile trees, climbing & jumping, and more.
|}

=== Dwarf Fortress v0.34 ===
{| class=wikitable

In a [http://www.bay12games.com/dwarves/index.html devlog] entry for 2011-01-30, Threetoe announced plans for a series of nine numbered releases ("Short-term Goals" on the [http://www.bay12games.com/dwarves/dev.html dev page]) to finish off the long-planned "caravan" development arc. Release 1, improving towns and introducing markets, along with a variety of supernatural creature types, was predicted to have a version number of [http://www.bay12games.com/media/df_talk_14_transcript.html#14.16 0.33 or 0.34] and was released on Valentine's Day 2012 as version 0.34.01.
|-
| [[v0.34:Release information/0.34.11|0.34.11]] || (2012-06-04):
| ''Bugfix''
|-
| [[v0.34:Release information/0.34.10|0.34.10]] || (2012-05-21):
| ''Bugfix''
|-
| [[v0.34:Release information/0.34.09|0.34.09]] || (2012-05-17):
| ''Bugfix''
|-
| [[v0.34:Release information/0.34.08|0.34.08]] || (2012-05-14):
| Hauling overhaul - minecarts and wheelbarrows, more accurate projectiles, reduced mining yields, advanced stockpile/workshop links
|-
| [[v0.34:Release information/0.34.07|0.34.07]] || (2012-03-30):
| ''Bugfix''
|-
| [[v0.34:Release information/0.34.06|0.34.06]] || (2012-03-23):
| Updates to animal training ([[dungeon master]] removed, having been nonfunctional since 0.31.01), return of good/evil trees and shrubs
|-
| [[v0.34:Release information/0.34.05|0.34.05]] || (2012-03-06):
| ''Bugfix''
|-
| [[v0.34:Release information/0.34.04|0.34.04]] || (2012-02-29):
| ''Hotfix''
|-
| [[v0.34:Release information/0.34.03|0.34.03]] || (2012-02-28):
| ''Bugfix''
|-
| [[v0.34:Release information/0.34.02|0.34.02]] || (2012-02-18):
| ''Bugfix''; broke save compatibility due to save corruption, numerous fixes for old issues
|-
| [[v0.34:Release information/0.34.01|0.34.01]] || (2012-02-14):
| Introduction of human cities (shops, marketplaces, sewers, dungeons) and tombs, addition of [[interaction]]s ([[necromancer]]s, [[werebeast]]s, [[vampire]]s, etc.), historical migrants, truly evil regions, updated [[justice]] system,
|}

=== Dwarf Fortress v0.31 ===
{| class=wikitable
|-
| [[v0.31:Release information/0.31.25|0.31.25]] || (2011-03-28):
| ''Hotfix'' -- Final update of version 0.31.
|-
| [[v0.31:Release information/0.31.24|0.31.24]] || (2011-03-27):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.23|0.31.23]] || (2011-03-26):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.22|0.31.22]] || (2011-03-24):
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.21|0.31.21]] || (2011-03-06):
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.20|0.31.20]] || (2011-03-06):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.19|0.31.19]] || (2011-02-16):
| Worldgen starvation, usually wiping out kobolds; grazing; ceramics; jugs, pots, nest boxes, beehives (and bees); site finder changes. Last major 0.31 release, and the (unnumbered) beginning of the caravan arc series.
|-
| [[v0.31:Release information/0.31.18|0.31.18]] || (2010-11-16):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.17|0.31.17]] || (2010-11-11):
| Bandits, Night Creatures, Bogeyman, Adventure mode improvements, combat aiming, castles
|-
| [[v0.31:Release information/0.31.16|0.31.16]] || (2010-10-04):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.15|0.31.15]] || (2010-10-03):
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.14|0.31.14]] || (2010-09-23):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.13|0.31.13]] || (2010-09-15):
| Entity populations, sprawl, river density tweaking, TrueType font support
|-
| [[v0.31:Release information/0.31.12|0.31.12]] || (2010-07-25):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.11|0.31.11]] || (2010-07-23):
| Art of deities
|-
| [[v0.31:Release information/0.31.10|0.31.10]] || (2010-07-11):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.09|0.31.09]] || (2010-07-10):
| Adventure mode knapping and butchery, combat improvements
|-
| [[v0.31:Release information/0.31.08|0.31.08]] || (2010-06-19):
| ''Hotfix''
|-
| [[v0.31:Release information/0.31.07|0.31.07]] || (2010-06-19):
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.06|0.31.06]] || (2010-06-09):
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.05|0.31.05]] || (2010-06-04):
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.04|0.31.04]] || (2010-05-16):
| Merge with the 40d19 branch
|-
| [[v0.31:Release information/0.31.03|0.31.03]] || (2010-04-12):
| Ability to create undead in arena
|-
| [[v0.31:Release information/0.31.02|0.31.02]] || (2010-04-08):
| ''Bugfix''
|-
| [[v0.31:Release information/0.31.01|0.31.01]] || (2010-04-01):
| Overhaul of many aspects of the game, first 2010 release
|}

=== 3D Version (before 2010) ===
{| class=wikitable
|-
| [[40d:Release information/''Branch'':|''Branch'':]] 0.28.181.40d2 thru 0.28.181.40d19: OpenGL optimizations, macros, zooming
|-
| [[40d:Release information/0.28.181.40d|0.28.181.40d]] || (2008-09-06):
| ''Bugfix''; [[40d:Cat cancels Store Item in Stockpile: Too injured|Cat bug introduced]]
|-
| [[40d:Release information/0.28.181.40c|0.28.181.40c]] || (2008-08-21):
| ''Hotfix'', partial print now allows specifying a frame count
|-
| [[40d:Release information/0.28.181.40b|0.28.181.40b]] || (2008-08-20):
| Partial print, windowed/fullscreen gridsizes
|-
| [[40d:Release information/0.28.181.40a|0.28.181.40a]] || (2008-08-18):
| Embark profiles added, [[note]]s extended to embark map, customizable forbid [[orders]] added (used ammunition, dead creatures' possessions, etc.), and dwarves now try to store items in partially-filled containers instead of empty ones
|-
| [[40d:Release information/0.28.181.39f|0.28.181.39f]] || (2008-08-09):
| [[Custom grid]] sizes added
|-
| [[40d:Release information/0.28.181.39e|0.28.181.39e]] || (2008-07-23):
| ''Hotfix''
|-
| [[40d:Release information/0.28.181.39d|0.28.181.39d]] || (2008-07-23):
| Added [[Site finder]], can display hidden map features when choosing a site, [[Note]] support implemented, and worldgen presets added
|-
| [[40d:Release information/0.28.181.39c|0.28.181.39c]] || (2008-07-16):
| ''Hotfix''
|-
| [[40d:Release information/0.28.181.39b|0.28.181.39b]] || (2008-07-14):
| ''Hotfix''; trees in [[Elf|Elven]] forest retreats no longer have names
|-
| [[40d:Release information/0.28.181.39a|0.28.181.39a]] || (2008-07-13):
| Lots of worldgen changes, including ethics (leading to wars and conquered sites), dynamic era naming, worldgen roads/bridges/tunnels, megabeasts being killed during worldgen, megabeasts being undead; cats and trained animals are now named on adoption, human weapon stores stock more stuff (including ammo), placing [[construction]]s now destroys engravings, and flying creatures no longer give birth in mid-air
|-
| [[40d:Release information/0.27.176.38c|0.27.176.38c]] || (2008-02-24):
| ''Bugfix''
|-
| [[40d:Release information/0.27.176.38b|0.27.176.38b]] || (2008-02-23):
| First Macintosh-compatible release; Dwarves no longer carry their artifacts around, booze food no longer melts, worlds can now have custom sizes
|-
| [[40d:Release information/0.27.176.38a|0.27.176.38a]] || (2008-02-15):
| Magma pipes now refill, ZERO_RENT and BABY_CHILD_CAP init.txt options were added, strange moods no longer convert workshops, metal crossbows now made by [[weaponsmith]]s instead of [[bowyer]]s, dwarves chat and make friends/grudges and get married, unhappy thoughts from [[masterpiece]] destruction are now reduced based on the number of masterpieces the dwarf has made, and plants can now drown in deep water
|-
| [[40d:Release information/0.27.173.38a|0.27.173.38a]] || (2008-02-04):
| [[Sphere]]s added, lots of new entity tags, numerous worldgen improvements, religions implemented, undead [[ruin]]s removed
|-
| [[40d:Release information/0.27.169.33g|0.27.169.33g]] || (2007-12-21):
| Mud no longer dries up during winter, occupied cages are named according to their contents, brand new "Bring to depot" interface, [[strange mood]]s no longer require glass until you actually make some
|-
| [[40d:Release information/0.27.169.33f|0.27.169.33f]] || (2007-12-14):
| ''Bugfix''; mud and blood no longer spread, auto-[[forbid]] fired ammunition, donkey/horse foals are now named properly, graphics sets can now use custom tiles for appointed nobles, and flux stones now have a value of 2 again.
|-
| [[40d:Release information/0.27.169.33e|0.27.169.33e]] || (2007-12-08):
| ''Bugfix''; in particular, nobles no longer order themselves to be punished for failed mandates, donkeys can now breed, most types of vermin no longer have bones, and most types of fish no longer have lungs or throats
|-
| [[40d:Release information/0.27.169.33d|0.27.169.33d]] || (2007-11-30):
| ''Bugfix''
|-
| [[40d:Release information/0.27.169.33c|0.27.169.33c]] || (2007-11-23):
| Animals screen now labels war dogs and hunting dogs correctly, [[sliver barb]]s now have seeds, and process priority can now be configured in init.txt
|-
| [[40d:Release information/0.27.169.33b|0.27.169.33b]] || (2007-11-16):
| [[Carp]] and other fish no longer gain [[swimming]] skill (making them ''slightly'' less dangerous), and various ore types now properly show up as '*' when mined.
|-
| [[40d:Release information/0.27.169.33a|0.27.169.33a]] || (2007-11-01):
| added [[wood]]en [[block]]s, renamed aluminum ore to "native aluminum", [[mountain gnome]]s and [[dark gnome]]s no longer butcherable
|-
| [[40d:Release information/0.27.169.32a|0.27.169.32a]] || (2007-10-29):
| The very first fully 3D version
|}

=== 2D Version ===
{| class=wikitable
|-
| [[23a:Release information/0.23.130.23a|0.23.130.23a]] || (2007-01-18):
| ''Hotfix'' - Final version
|-
| [[23a:Release information/0.23.125.23b|0.23.125.23b]] || (2007-01-16):
| ''Hotfix''
|-
| [[23a:Release information/0.23.125.23a|0.23.125.23a]] || (2007-01-16):
| Temperature support was further improved, population/FPS caps were added, coffins could now be restricted to only dwarves or only pets, and animals could now be marked for slaughter from their {{K|v}}-{{K|p}} screen. Spirits of fire also got a '''lot''' hotter. For some reason, [[horse]]s are now made of [[iron]].
|-
| [[23a:Release information/0.22.123.23a|0.22.123.23a]] || (2006-12-21):
| ''Hotfix''
|-
| [[23a:Release information/0.22.123.23a|0.22.123.23a]] || (2006-12-21):
| More workshop orders were added - auto collect webs, auto slaughter, auto butcher, auto tan; male cows are now called bulls, and whips can no longer get stuck in opponents
|-
| [[23a:Release information/0.22.121.23b|0.22.121.23b]] || (2006-12-16):
| The ability to disable temperature and weather were added (to boost FPS)
|-
| [[23a:Release information/0.22.121.23a|0.22.121.23a]] || (2006-12-14):
| Bins could now be made from metal, and the embark screen now described your biome and listed what civilizations were nearby
|-
| [[23a:Release information/0.22.120.23b|0.22.120.23b]] || (2006-12-10):
| Improved temperature support was added
|-
| [[23a:Release information/0.22.120.23a|0.22.120.23a]] || (2006-11-23):
| The ability to use custom [[graphics sets]] was added
|-
| [[23a:Release information/0.22.110.23c|0.22.110.23c]] || (2006-11-17):
| ''Hotfix''
|-
| [[23a:Release information/0.22.110.23b|0.22.110.23b]] || (2006-11-15):
| ''Hotfix''
|-
| [[23a:Release information/0.22.110.23a|0.22.110.23a]] || (2006-11-17):
| [[Dye]]s and dyeing were implemented, allowed sewing cloth/leather images into goods, as well as more detailed [[decoration|art]] (historical figures and events, special shapes); standing orders now allowed auto collecting webs and only using dyed cloth
|-
| [[23a:Release information/0.22.110.22f|0.22.110.22f]] || (2006-11-03):
| ''Bugfix''; additionally, butterflies, fireflies, and dragonflies can no longer be kept as pets. [[Boatmurdered]] began in this version.
|-
| [[23a:Release information/0.22.110.22e|0.22.110.22e]] || (2006-10-29):
| ''Hotfix''
|-
| [[23a:Release information/0.22.110.22d|0.22.110.22d]] || (2006-10-29):
| ''Hotfix''
|-
| [[23a:Release information/0.22.110.22c|0.22.110.22c]] || (2006-10-29):
| Custom [[stockpile]]s were added (previously, there were only 16 basic stockpile types; things like [[potash]] would be stored with your metal bars and you could not force [[seed]]s to be kept near the farm).
|-
| [[23a:Release information/0.22.110.22b|0.22.110.22b]] || (2006-10-21):
| ''Hotfix''
|-
| [[23a:Release information/0.22.110.22a|0.22.110.22a]] || (2006-10-21):
| Inventory system changes (most notably, gloves and boots were split into two items (left & right for gloves))
|-
| [[23a:Release information/0.22.107.21a|0.22.107.21a]] || (2006-10-02):
| Various changes to [[adventurer mode]] - guards and families, plus "." as a wait key
|-
| [[23a:Release information/0.21.105.21a|0.21.105.21a]] || (2006-09-25):
| ''Hotfix''
|-
| [[23a:Release information/0.21.104.21c|0.21.104.21c]] || (2006-09-25):
| Making potash no longer required making ashes into lye first.
|-
| [[23a:Release information/0.21.104.21b|0.21.104.21b]] || (2006-09-16):
| Workshop profiles were added, along with showing genders on the Animal status screen
|-
| [[23a:Release information/0.21.104.21a|0.21.104.21a]] || (2006-09-08):
| [[Designation|Designating]] with the mouse was added
|-
| [[23a:Release information/0.21.104.19d|0.21.104.19d]] || (2006-09-02):
| ''Bugfix''
|-
| [[23a:Release information/0.21.104.19c|0.21.104.19c]] || (2006-09-02):
| The ability to hide engravings was added, announcement consolidation (x15), seasonal blood cleanup was temporarily added (and would remain until version 0.31)
|-
| [[23a:Release information/0.21.104.19b|0.21.104.19b]] || (2006-08-27):
| ''Bugfix''
|-
| [[23a:Release information/0.21.104.19a|0.21.104.19a]] || (2006-08-27):
| The ability to "chasm" items was added (complete with attacks from chasm creatures as a result), as well as butchering cats
|-
| [[23a:Release information/0.21.102.19a|0.21.102.19a]] || (2006-08-24):
| Dwarves could now have custom nicknames and professions, fullscreen could be toggled, starting animals would have mixed genders, horses could breed
|-
| [[23a:Release information/0.21.101.19d|0.21.101.19d]] || (2006-08-21):
| ''Bugfix''
|-
| [[23a:Release information/0.21.101.19c|0.21.101.19c]] || (2006-08-20):
| ''Bugfix''
|-
| [[23a:Release information/0.21.101.19b|0.21.101.19b]] || (2006-08-20):
| ''Bugfix''
|-
| [[23a:Release information/0.21.101.19a|0.21.101.19a]] || (2006-08-19):
| Adventurers could now have custom first names
|-
| [[23a:Release information/0.21.100.19a|0.21.100.19a]] || (2006-08-16):
| Gender symbol was added to unit views, config options for disabling sound and the intro movie, command-line world generation, ability to export local map
|-
| [[23a:Release information/0.21.95.19c|0.21.95.19c]] || (2006-08-14):
| Farm plot fertilization could be controlled directly
|-
| [[23a:Release information/0.21.95.19b|0.21.95.19b]] || (2006-08-13):
| ''Bugfix''
|-
| [[23a:Release information/0.21.95.19a|0.21.95.19a]] || (2006-08-12):
| ''Bugfix''
|-
| [[23a:Release information/0.21.93.19c|0.21.93.19c]] || (2006-08-10):
| ''Bugfix''
|-
| [[23a:Release information/0.21.93.19b|0.21.93.19b]] || (2006-08-10):
| ''Bugfix''
|-
| [[23a:Release information/0.21.93.19a|0.21.93.19a]] || (2006-08-08):
| Initial public release
|}

== Bugs ==
Please report bugs on the [https://dwarffortress.mantishub.io/ official bug tracker], and optionally add them to [[Known bugs and issues]]. Please do not add them to this page.

Release information

2023-01-06T19:05:42Z

Jan: /* Version History */

{{migrated article}}
{{Quality|Unrated}}
{{release notes}}{{av}}

The first version in this release cycle, '''DF 50.01''', was released on '''December 6, 2022'''. The latest version is '''{{current/version}}''', released on '''{{current/lastupdate}}'''. The changes in each version are listed in the sidebar to the right.

Version 50.01 was the first version of Dwarf Fortress released on [https://steamcommunity.com/app/975370/ Steam]. It was also the first version to use a new versioning scheme: the leading "0." present in all previous versions of DF was removed from the version number.

As with all major releases, version 50.01 broke [[save compatibility]] with old versions.

== Version History ==
=== Dwarf Fortress v50 ===
* [[Release information/50.05|50.05]] (2023-01-05): ''Bugfixes and optimizations''
* [[Release information/50.04|50.04]] (2022-12-22): '''Classic release''': released the free [[Classic]] version on [https://www.bay12games.com/dwarves/ bay12games.com], and enabled classic mode in the Premium version. Added ability to advance time by one frame, and assign everyone to a burrow.
* [[Release information/50.03|50.03]] (2022-12-12): ''Premium-only bugfixes''. Improved UX for selecting building materials.
* [[Release information/50.02|50.02]] (2022-12-08): ''Premium-only bugfixes''
* [[Release information/50.01|50.01]] (2022-12-06): '''Premium release''': launched the paid [[Premium]] version on Steam and itch.io. Introduced [[graphics]], full [[Mouse control|mouse support]], a new user [[interface]], tutorials, and new [[soundtrack|music]] and sound effects. A number of features from v0.47 were lost in 50.01 (see [[Missing features]]).

=== Dwarf Fortress v0.47 ===
* [[DF2014:Release information/0.47.05|0.47.05]] (2021-01-28): ''Bugfix''
* [[DF2014:Release information/0.47.04|0.47.04]] (2020-02-29): ''Bugfix''
* [[DF2014:Release information/0.47.03|0.47.03]] (2020-02-16): ''Bugfix''
* [[DF2014:Release information/0.47.02|0.47.02]] (2020-02-06): ''Bugfix''
* [[DF2014:Release information/0.47.01|0.47.01]] (2020-01-29): ''Release'': introduced creation of [[guildhall]]s and [[temple]]s. Introduced [[traitor]]s and [[villain]]s.

=== Dwarf Fortress v0.44 ===
* [[DF2014:Release information/0.44.12|0.44.12]] (2018-06-23): ''Hotfix'';
* [[DF2014:Release information/0.44.11|0.44.11]] (2018-06-23): Civilizations create nearby sites and associate them with your fortress, can request/send workers, long-term memories can lead to personality changes
* [[DF2014:Release information/0.44.10|0.44.10]] (2018-05-05): Dwarves now have short-term and long-term memories of emotional events, Adventurer mode log improved
* [[DF2014:Release information/0.44.09|0.44.09]] (2018-04-01): ''Hotfix'';
* [[DF2014:Release information/0.44.08|0.44.08]] (2018-03-29): ''Bugfix'';
* [[DF2014:Release information/0.44.07|0.44.07]] (2018-03-12): ''Hotfix'';
* [[DF2014:Release information/0.44.06|0.44.06]] (2018-03-09): Raids can pillage/raze sites and demand tribute, will gain skills (e.g. military tactics) during missions
* [[DF2014:Release information/0.44.05|0.44.05]] (2018-01-14): ''Hotfix'';
* [[DF2014:Release information/0.44.04|0.44.04]] (2018-01-10): ''Bugfix'';
* [[DF2014:Release information/0.44.03|0.44.03]] (2017-12-25): ''Bugfix'';
* [[DF2014:Release information/0.44.02|0.44.02]] (2017-11-23): ''Hotfix'';
* [[DF2014:Release information/0.44.01|0.44.01]] (2017-11-22): ''Release''; can now send raids to other sites, build museums using pedestals and display cases, artifacts created during worldgen, civilizations can send spies to gather information on artifacts

=== Dwarf Fortress v0.43 ===
* [[DF2014:Release information/0.43.05|0.43.05]] (2016-06-20): '''64-bit support''', bugfixes
* [[DF2014:Release information/0.43.04|0.43.04]] (2016-06-20): ''Bugfix'';
* [[DF2014:Release information/0.43.03|0.43.03]] (2016-05-22): ''Bugfix'';
* [[DF2014:Release information/0.43.02|0.43.02]] (2016-05-11): ''Hotfix'';
* [[DF2014:Release information/0.43.01|0.43.01]] (2016-05-09): ''Release''; Adventurers can create sites, make stone axes, fell trees, perform carpentry, and construct buildings; Fortress mode work orders can now specify start conditions, restart frequencies, and how many workshops can be used

=== Dwarf Fortress v0.42 ===
* [[DF2014:Release information/0.42.06|0.42.06]] (2016-02-10): Can specify exact materials for jobs, make specific crafts, apply specific decorations, and even customize the details of art images; Adventurers can now do bone carving, complete with custom images
* [[DF2014:Release information/0.42.05|0.42.05]] (2016-01-17): Reputations for hunters and protection from bandits
* [[DF2014:Release information/0.42.04|0.42.04]] (2015-12-26): More varieties of [[animal people]] and giant animals, Vampire purges during worldgen, bugfixes
* [[DF2014:Release information/0.42.03|0.42.03]] (2015-12-12): ''Bugfix'';
* [[DF2014:Release information/0.42.02|0.42.02]] (2015-12-05): ''Bugfix'';
* [[DF2014:Release information/0.42.01|0.42.01]] (2015-12-01): ''Release''; introduced taverns, temples, and libraries, added new musical instruments and performance skills, introduced [[need]]s to replace dwarves going On Break, added visitors who can petition for fortress membership, scholars and historians can write books and spread knowledge, and drinking alcohol actually causes inebriation (and eventually fatal alcohol poisoning)

=== Dwarf Fortress v0.40 ===
* [[DF2014:Release information/0.40.24|0.40.24]] (2015-01-07): ''Bugfix''; Misc. bugfixes; allowing 1x1 forts
* [[DF2014:Release information/0.40.23|0.40.23]] (2014-12-24): ''Bugfix''; Fixed farming job cancellations, armies camping forever, typos, and channeling bug
* [[DF2014:Release information/0.40.22|0.40.22]] (2014-12-21): ''Bugfix''; Fixed multi-item jobs and toggle marker tweak
* [[DF2014:Release information/0.40.21|0.40.21]] (2014-12-19): ''Hotfix''; Fixed a crash bug and other issues
* [[DF2014:Release information/0.40.20|0.40.20]] (2014-12-18): Job priorities rewrite; vein and cluster automining
* [[DF2014:Release information/0.40.19|0.40.19]] (2014-11-26): [[Gelding]] and related profession/skill/etc
* [[DF2014:Release information/0.40.18|0.40.18]] (2014-11-20): ''Hotfix''; Fixed a smelting issue on Windows
* [[DF2014:Release information/0.40.17|0.40.17]] (2014-11-19): ''Bugfix'';
* [[DF2014:Release information/0.40.16|0.40.16]] (2014-11-12): ''Bugfix'';
* [[DF2014:Release information/0.40.15|0.40.15]] (2014-11-05): ''Bugfix'';
* [[DF2014:Release information/0.40.14|0.40.14]] (2014-10-25): Thought/emotion rewrite, stopped site invaders from always winning
* [[DF2014:Release information/0.40.13|0.40.13]] (2014-09-17): ''Bugfix'';
* [[DF2014:Release information/0.40.12|0.40.12]] (2014-09-10): ''Bugfix'';
* [[DF2014:Release information/0.40.11|0.40.11]] (2014-09-03): ''Bugfix'';
* [[DF2014:Release information/0.40.10|0.40.10]] (2014-08-24): ''Bugfix'';
* [[DF2014:Release information/0.40.09|0.40.09]] (2014-08-17): ''Bugfix''; Misc. bugfixes
* [[DF2014:Release information/0.40.08|0.40.08]] (2014-08-11): ''Hotfix''; Fixed a crash bug and issues with constructions
* [[DF2014:Release information/0.40.07|0.40.07]] (2014-08-10): ''Bugfix''; AI and invasion fixes
* [[DF2014:Release information/0.40.06|0.40.06]] (2014-08-03): ''Bugfix''; stack bugfixes.
* [[DF2014:Release information/0.40.05|0.40.05]] (2014-07-27): ''Bugfix''; fixed large world slowdown, decreased rampant tree growth, many old and new bugfixes.
* [[DF2014:Release information/0.40.04|0.40.04]] (2014-07-20): ''Bugfix''; several crash fixes, made saplings grow properly.
* [[DF2014:Release information/0.40.03|0.40.03]] (2014-07-13): ''Bugfix''; broke save game compatibility again due to more save corruption, several crash fixes.
* [[DF2014:Release information/0.40.02|0.40.02]] (2014-07-10): ''Bugfix''; broke save game compatibility due to save corruption, several crash fixes.
* [[DF2014:Release information/0.40.01|0.40.01]] (2014-07-07): ''Release''; Introduced world generation running in the background while fortresses and adventurers progress, un-retiring of fortresses, multiple tile trees, climbing & jumping, and more.

=== Dwarf Fortress v0.34 ===

In a [http://www.bay12games.com/dwarves/index.html devlog] entry for 2011-01-30, Threetoe announced plans for a series of nine numbered releases ("Short-term Goals" on the [http://www.bay12games.com/dwarves/dev.html dev page]) to finish off the long-planned "caravan" development arc. Release 1, improving towns and introducing markets, along with a variety of supernatural creature types, was predicted to have a version number of [http://www.bay12games.com/media/df_talk_14_transcript.html#14.16 0.33 or 0.34] and was released on Valentine's Day 2012 as version 0.34.01.

* [[v0.34:Release information/0.34.11|0.34.11]] (2012-06-04): ''Bugfix''
* [[v0.34:Release information/0.34.10|0.34.10]] (2012-05-21): ''Bugfix''
* [[v0.34:Release information/0.34.09|0.34.09]] (2012-05-17): ''Bugfix''
* [[v0.34:Release information/0.34.08|0.34.08]] (2012-05-14): Hauling overhaul - minecarts and wheelbarrows, more accurate projectiles, reduced mining yields, advanced stockpile/workshop links
* [[v0.34:Release information/0.34.07|0.34.07]] (2012-03-30): ''Bugfix''
* [[v0.34:Release information/0.34.06|0.34.06]] (2012-03-23): Updates to animal training ([[dungeon master]] removed, having been nonfunctional since 0.31.01), return of good/evil trees and shrubs
* [[v0.34:Release information/0.34.05|0.34.05]] (2012-03-06): ''Bugfix''
* [[v0.34:Release information/0.34.04|0.34.04]] (2012-02-29): ''Hotfix''
* [[v0.34:Release information/0.34.03|0.34.03]] (2012-02-28): ''Bugfix''
* [[v0.34:Release information/0.34.02|0.34.02]] (2012-02-18): ''Bugfix''; broke save compatibility due to save corruption, numerous fixes for old issues
* [[v0.34:Release information/0.34.01|0.34.01]] (2012-02-14): Introduction of human cities (shops, marketplaces, sewers, dungeons) and tombs, addition of [[interaction]]s ([[necromancer]]s, [[werebeast]]s, [[vampire]]s, etc.), historical migrants, truly evil regions, updated [[justice]] system,

=== Dwarf Fortress v0.31 ===

* [[v0.31:Release information/0.31.25|0.31.25]] (2011-03-28): ''Hotfix'' -- Final update of version 0.31.
* [[v0.31:Release information/0.31.24|0.31.24]] (2011-03-27): ''Hotfix''
* [[v0.31:Release information/0.31.23|0.31.23]] (2011-03-26): ''Hotfix''
* [[v0.31:Release information/0.31.22|0.31.22]] (2011-03-24): ''Bugfix''
* [[v0.31:Release information/0.31.21|0.31.21]] (2011-03-06): ''Bugfix''
* [[v0.31:Release information/0.31.20|0.31.20]] (2011-03-06): ''Hotfix''
* [[v0.31:Release information/0.31.19|0.31.19]] (2011-02-16): Worldgen starvation, usually wiping out kobolds; grazing; ceramics; jugs, pots, nest boxes, beehives (and bees); site finder changes. Last major 0.31 release, and the (unnumbered) beginning of the caravan arc series.
* [[v0.31:Release information/0.31.18|0.31.18]] (2010-11-16): ''Hotfix''
* [[v0.31:Release information/0.31.17|0.31.17]] (2010-11-11): Bandits, Night Creatures, Bogeyman, Adventure mode improvements, combat aiming, castles
* [[v0.31:Release information/0.31.16|0.31.16]] (2010-10-04): ''Hotfix''
* [[v0.31:Release information/0.31.15|0.31.15]] (2010-10-03): ''Bugfix''
* [[v0.31:Release information/0.31.14|0.31.14]] (2010-09-23): ''Hotfix''
* [[v0.31:Release information/0.31.13|0.31.13]] (2010-09-15): Entity populations, sprawl, river density tweaking, TrueType font support
* [[v0.31:Release information/0.31.12|0.31.12]] (2010-07-25): ''Hotfix''
* [[v0.31:Release information/0.31.11|0.31.11]] (2010-07-23): Art of deities
* [[v0.31:Release information/0.31.10|0.31.10]] (2010-07-11): ''Hotfix''
* [[v0.31:Release information/0.31.09|0.31.09]] (2010-07-10): Adventure mode knapping and butchery, combat improvements
* [[v0.31:Release information/0.31.08|0.31.08]] (2010-06-19): ''Hotfix''
* [[v0.31:Release information/0.31.07|0.31.07]] (2010-06-19): ''Bugfix''
* [[v0.31:Release information/0.31.06|0.31.06]] (2010-06-09): ''Bugfix''
* [[v0.31:Release information/0.31.05|0.31.05]] (2010-06-04): ''Bugfix''
* [[v0.31:Release information/0.31.04|0.31.04]] (2010-05-16): Merge with the 40d19 branch
* [[v0.31:Release information/0.31.03|0.31.03]] (2010-04-12): Ability to create undead in arena
* [[v0.31:Release information/0.31.02|0.31.02]] (2010-04-08): ''Bugfix''
* [[v0.31:Release information/0.31.01|0.31.01]] (2010-04-01): Overhaul of many aspects of the game, first 2010 release

=== 3D Version (before 2010) ===
* [[40d:Release information/''Branch'':|''Branch'':]] 0.28.181.40d2 thru 0.28.181.40d19: OpenGL optimizations, macros, zooming
* [[40d:Release information/0.28.181.40d|0.28.181.40d]] (2008-09-06): ''Bugfix''; [[40d:Cat cancels Store Item in Stockpile: Too injured|Cat bug introduced]]
* [[40d:Release information/0.28.181.40c|0.28.181.40c]] (2008-08-21): ''Hotfix'', partial print now allows specifying a frame count
* [[40d:Release information/0.28.181.40b|0.28.181.40b]] (2008-08-20): Partial print, windowed/fullscreen gridsizes
* [[40d:Release information/0.28.181.40a|0.28.181.40a]] (2008-08-18): Embark profiles added, [[note]]s extended to embark map, customizable forbid [[orders]] added (used ammunition, dead creatures' possessions, etc.), and dwarves now try to store items in partially-filled containers instead of empty ones
* [[40d:Release information/0.28.181.39f|0.28.181.39f]] (2008-08-09): [[Custom grid]] sizes added
* [[40d:Release information/0.28.181.39e|0.28.181.39e]] (2008-07-23): ''Hotfix''
* [[40d:Release information/0.28.181.39d|0.28.181.39d]] (2008-07-23): Added [[Site finder]], can display hidden map features when choosing a site, [[Note]] support implemented, and worldgen presets added
* [[40d:Release information/0.28.181.39c|0.28.181.39c]] (2008-07-16): ''Hotfix''
* [[40d:Release information/0.28.181.39b|0.28.181.39b]] (2008-07-14): ''Hotfix''; trees in [[Elf|Elven]] forest retreats no longer have names
* [[40d:Release information/0.28.181.39a|0.28.181.39a]] (2008-07-13): Lots of worldgen changes, including ethics (leading to wars and conquered sites), dynamic era naming, worldgen roads/bridges/tunnels, megabeasts being killed during worldgen, megabeasts being undead; cats and trained animals are now named on adoption, human weapon stores stock more stuff (including ammo), placing [[construction]]s now destroys engravings, and flying creatures no longer give birth in mid-air
* [[40d:Release information/0.27.176.38c|0.27.176.38c]] (2008-02-24): ''Bugfix''
* [[40d:Release information/0.27.176.38b|0.27.176.38b]] (2008-02-23): First Macintosh-compatible release; Dwarves no longer carry their artifacts around, booze food no longer melts, worlds can now have custom sizes
* [[40d:Release information/0.27.176.38a|0.27.176.38a]] (2008-02-15): Magma pipes now refill, ZERO_RENT and BABY_CHILD_CAP init.txt options were added, strange moods no longer convert workshops, metal crossbows now made by [[weaponsmith]]s instead of [[bowyer]]s, dwarves chat and make friends/grudges and get married, unhappy thoughts from [[masterpiece]] destruction are now reduced based on the number of masterpieces the dwarf has made, and plants can now drown in deep water
* [[40d:Release information/0.27.173.38a|0.27.173.38a]] (2008-02-04): [[Sphere]]s added, lots of new entity tags, numerous worldgen improvements, religions implemented, undead [[ruin]]s removed
* [[40d:Release information/0.27.169.33g|0.27.169.33g]] (2007-12-21): Mud no longer dries up during winter, occupied cages are named according to their contents, brand new "Bring to depot" interface, [[strange mood]]s no longer require glass until you actually make some
* [[40d:Release information/0.27.169.33f|0.27.169.33f]] (2007-12-14): ''Bugfix''; mud and blood no longer spread, auto-[[forbid]] fired ammunition, donkey/horse foals are now named properly, graphics sets can now use custom tiles for appointed nobles, and flux stones now have a value of 2 again.
* [[40d:Release information/0.27.169.33e|0.27.169.33e]] (2007-12-08): ''Bugfix''; in particular, nobles no longer order themselves to be punished for failed mandates, donkeys can now breed, most types of vermin no longer have bones, and most types of fish no longer have lungs or throats
* [[40d:Release information/0.27.169.33d|0.27.169.33d]] (2007-11-30): ''Bugfix''
* [[40d:Release information/0.27.169.33c|0.27.169.33c]] (2007-11-23): Animals screen now labels war dogs and hunting dogs correctly, [[sliver barb]]s now have seeds, and process priority can now be configured in init.txt
* [[40d:Release information/0.27.169.33b|0.27.169.33b]] (2007-11-16): [[Carp]] and other fish no longer gain [[swimming]] skill (making them ''slightly'' less dangerous), and various ore types now properly show up as '*' when mined.
* [[40d:Release information/0.27.169.33a|0.27.169.33a]] (2007-11-01): added [[wood]]en [[block]]s, renamed aluminum ore to "native aluminum", [[mountain gnome]]s and [[dark gnome]]s no longer butcherable
* [[40d:Release information/0.27.169.32a|0.27.169.32a]] (2007-10-29): The very first fully 3D version

=== 2D Version ===
* [[23a:Release information/0.23.130.23a|0.23.130.23a]] (2007-01-18): ''Hotfix'' - Final version
* [[23a:Release information/0.23.125.23b|0.23.125.23b]] (2007-01-16): ''Hotfix''
* [[23a:Release information/0.23.125.23a|0.23.125.23a]] (2007-01-16): Temperature support was further improved, population/FPS caps were added, coffins could now be restricted to only dwarves or only pets, and animals could now be marked for slaughter from their {{K|v}}-{{K|p}} screen. Spirits of fire also got a '''lot''' hotter. For some reason, [[horse]]s are now made of [[iron]].
* [[23a:Release information/0.22.123.23a|0.22.123.23a]] (2006-12-21): ''Hotfix''
* [[23a:Release information/0.22.123.23a|0.22.123.23a]] (2006-12-21): More workshop orders were added - auto collect webs, auto slaughter, auto butcher, auto tan; male cows are now called bulls, and whips can no longer get stuck in opponents
* [[23a:Release information/0.22.121.23b|0.22.121.23b]] (2006-12-16): The ability to disable temperature and weather were added (to boost FPS)
* [[23a:Release information/0.22.121.23a|0.22.121.23a]] (2006-12-14): Bins could now be made from metal, and the embark screen now described your biome and listed what civilizations were nearby
* [[23a:Release information/0.22.120.23b|0.22.120.23b]] (2006-12-10): Improved temperature support was added
* [[23a:Release information/0.22.120.23a|0.22.120.23a]] (2006-11-23): The ability to use custom [[graphics sets]] was added
* [[23a:Release information/0.22.110.23c|0.22.110.23c]] (2006-11-17): ''Hotfix''
* [[23a:Release information/0.22.110.23b|0.22.110.23b]] (2006-11-15): ''Hotfix''
* [[23a:Release information/0.22.110.23a|0.22.110.23a]] (2006-11-17): [[Dye]]s and dyeing were implemented, allowed sewing cloth/leather images into goods, as well as more detailed [[decoration|art]] (historical figures and events, special shapes); standing orders now allowed auto collecting webs and only using dyed cloth
* [[23a:Release information/0.22.110.22f|0.22.110.22f]] (2006-11-03): ''Bugfix''; additionally, butterflies, fireflies, and dragonflies can no longer be kept as pets. [[Boatmurdered]] began in this version.
* [[23a:Release information/0.22.110.22e|0.22.110.22e]] (2006-10-29): ''Hotfix''
* [[23a:Release information/0.22.110.22d|0.22.110.22d]] (2006-10-29): ''Hotfix''
* [[23a:Release information/0.22.110.22c|0.22.110.22c]] (2006-10-29): Custom [[stockpile]]s were added (previously, there were only 16 basic stockpile types; things like [[potash]] would be stored with your metal bars and you could not force [[seed]]s to be kept near the farm).
* [[23a:Release information/0.22.110.22b|0.22.110.22b]] (2006-10-21): ''Hotfix''
* [[23a:Release information/0.22.110.22a|0.22.110.22a]] (2006-10-21): Inventory system changes (most notably, gloves and boots were split into two items (left & right for gloves))
* [[23a:Release information/0.22.107.21a|0.22.107.21a]] (2006-10-02): Various changes to [[adventurer mode]] - guards and families, plus "." as a wait key
* [[23a:Release information/0.21.105.21a|0.21.105.21a]] (2006-09-25): ''Hotfix''
* [[23a:Release information/0.21.104.21c|0.21.104.21c]] (2006-09-25): Making potash no longer required making ashes into lye first.
* [[23a:Release information/0.21.104.21b|0.21.104.21b]] (2006-09-16): Workshop profiles were added, along with showing genders on the Animal status screen
* [[23a:Release information/0.21.104.21a|0.21.104.21a]] (2006-09-08): [[Designation|Designating]] with the mouse was added
* [[23a:Release information/0.21.104.19d|0.21.104.19d]] (2006-09-02): ''Bugfix''
* [[23a:Release information/0.21.104.19c|0.21.104.19c]] (2006-09-02): The ability to hide engravings was added, announcement consolidation (x15), seasonal blood cleanup was temporarily added (and would remain until version 0.31)
* [[23a:Release information/0.21.104.19b|0.21.104.19b]] (2006-08-27): ''Bugfix''
* [[23a:Release information/0.21.104.19a|0.21.104.19a]] (2006-08-27): The ability to "chasm" items was added (complete with attacks from chasm creatures as a result), as well as butchering cats
* [[23a:Release information/0.21.102.19a|0.21.102.19a]] (2006-08-24): Dwarves could now have custom nicknames and professions, fullscreen could be toggled, starting animals would have mixed genders, horses could breed
* [[23a:Release information/0.21.101.19d|0.21.101.19d]] (2006-08-21): ''Bugfix''
* [[23a:Release information/0.21.101.19c|0.21.101.19c]] (2006-08-20): ''Bugfix''
* [[23a:Release information/0.21.101.19b|0.21.101.19b]] (2006-08-20): ''Bugfix''
* [[23a:Release information/0.21.101.19a|0.21.101.19a]] (2006-08-19): Adventurers could now have custom first names
* [[23a:Release information/0.21.100.19a|0.21.100.19a]] (2006-08-16): Gender symbol was added to unit views, config options for disabling sound and the intro movie, command-line world generation, ability to export local map
* [[23a:Release information/0.21.95.19c|0.21.95.19c]] (2006-08-14): Farm plot fertilization could be controlled directly
* [[23a:Release information/0.21.95.19b|0.21.95.19b]] (2006-08-13): ''Bugfix''
* [[23a:Release information/0.21.95.19a|0.21.95.19a]] (2006-08-12): ''Bugfix''
* [[23a:Release information/0.21.93.19c|0.21.93.19c]] (2006-08-10): ''Bugfix''
* [[23a:Release information/0.21.93.19b|0.21.93.19b]] (2006-08-10): ''Bugfix''
* [[23a:Release information/0.21.93.19a|0.21.93.19a]] (2006-08-08): Initial public release

== Bugs ==
Please report bugs on the [https://dwarffortress.mantishub.io/ official bug tracker], and optionally add them to [[Known bugs and issues]]. Please do not add them to this page.

Release information

2023-01-06T19:03:36Z

Jan: /* Version History */

{{migrated article}}
{{Quality|Unrated}}
{{release notes}}{{av}}

The first version in this release cycle, '''DF 50.01''', was released on '''December 6, 2022'''. The latest version is '''{{current/version}}''', released on '''{{current/lastupdate}}'''. The changes in each version are listed in the sidebar to the right.

Version 50.01 was the first version of Dwarf Fortress released on [https://steamcommunity.com/app/975370/ Steam]. It was also the first version to use a new versioning scheme: the leading "0." present in all previous versions of DF was removed from the version number.

As with all major releases, version 50.01 broke [[save compatibility]] with old versions.

== Version History ==
=== Dwarf Fortress v50 ===
* [[Release information/50.05|50.05]] (2023-01-05): ''Bugfixes and optimizations''
* [[Release information/50.04|50.04]] (2022-12-22): '''Classic release''': released the free [[Classic]] version on [https://www.bay12games.com/dwarves/ bay12games.com], and enabled classic mode in the Premium version. Added ability to advance time by one frame, and assign everyone to a burrow.
* [[Release information/50.03|50.03]] (2022-12-12): ''Premium-only bugfixes''. Improved UX for selecting building materials.
* [[Release information/50.02|50.02]] (2022-12-08): ''Premium-only bugfixes''
* [[Release information/50.01|50.01]] (2022-12-06): '''Premium release''': launched the paid [[Premium]] version on Steam and itch.io. Introduced [[graphics]], full [[Mouse control|mouse support]], a new user [[interface]], tutorials, and new [[soundtrack|music]] and sound effects. A number of features from v0.47 were lost in 50.01 (see [[Missing features]]).

=== Dwarf Fortress v0.47 ===
* [[DF2014:Release information/0.47.05|0.47.05]] (2021-01-28): ''Bugfix''
* [[DF2014:Release information/0.47.04|0.47.04]] (2020-02-29): ''Bugfix''
* [[DF2014:Release information/0.47.03|0.47.03]] (2020-02-16): ''Bugfix''
* [[DF2014:Release information/0.47.02|0.47.02]] (2020-02-06): ''Bugfix''
* [[DF2014:Release information/0.47.01|0.47.01]] (2020-01-29): ''Release'': introduced creation of [[guildhall]]s and [[temple]]s. Introduced [[traitor]]s and [[villain]]s.

=== Dwarf Fortress v0.44 ===
* 0.44.12 (2018-06-23): ''Hotfix'';
* 0.44.11 (2018-06-23): Civilizations create nearby sites and associate them with your fortress, can request/send workers, long-term memories can lead to personality changes
* 0.44.10 (2018-05-05): Dwarves now have short-term and long-term memories of emotional events, Adventurer mode log improved
* 0.44.09 (2018-04-01): ''Hotfix'';
* 0.44.08 (2018-03-29): ''Bugfix'';
* 0.44.07 (2018-03-12): ''Hotfix'';
* 0.44.06 (2018-03-09): Raids can pillage/raze sites and demand tribute, will gain skills (e.g. military tactics) during missions
* 0.44.05 (2018-01-14): ''Hotfix'';
* 0.44.04 (2018-01-10): ''Bugfix'';
* 0.44.03 (2017-12-25): ''Bugfix'';
* 0.44.02 (2017-11-23): ''Hotfix'';
* 0.44.01 (2017-11-22): ''Release''; can now send raids to other sites, build museums using pedestals and display cases, artifacts created during worldgen, civilizations can send spies to gather information on artifacts

=== Dwarf Fortress v0.43 ===
* 0.43.05 (2016-06-20): '''64-bit support''', bugfixes
* 0.43.04 (2016-06-20): ''Bugfix'';
* 0.43.03 (2016-05-22): ''Bugfix'';
* 0.43.02 (2016-05-11): ''Hotfix'';
* 0.43.01 (2016-05-09): ''Release''; Adventurers can create sites, make stone axes, fell trees, perform carpentry, and construct buildings; Fortress mode work orders can now specify start conditions, restart frequencies, and how many workshops can be used

=== Dwarf Fortress v0.42 ===
* 0.42.06 (2016-02-10): Can specify exact materials for jobs, make specific crafts, apply specific decorations, and even customize the details of art images; Adventurers can now do bone carving, complete with custom images
* 0.42.05 (2016-01-17): Reputations for hunters and protection from bandits
* 0.42.04 (2015-12-26): More varieties of [[animal people]] and giant animals, Vampire purges during worldgen, bugfixes
* 0.42.03 (2015-12-12): ''Bugfix'';
* 0.42.02 (2015-12-05): ''Bugfix'';
* 0.42.01 (2015-12-01): ''Release''; introduced taverns, temples, and libraries, added new musical instruments and performance skills, introduced [[need]]s to replace dwarves going On Break, added visitors who can petition for fortress membership, scholars and historians can write books and spread knowledge, and drinking alcohol actually causes inebriation (and eventually fatal alcohol poisoning)

=== Dwarf Fortress v0.40 ===
* 0.40.24 (2015-01-07): ''Bugfix''; Misc. bugfixes; allowing 1x1 forts
* 0.40.23 (2014-12-24): ''Bugfix''; Fixed farming job cancellations, armies camping forever, typos, and channeling bug
* 0.40.22 (2014-12-21): ''Bugfix''; Fixed multi-item jobs and toggle marker tweak
* 0.40.21 (2014-12-19): ''Hotfix''; Fixed a crash bug and other issues
* 0.40.20 (2014-12-18): Job priorities rewrite; vein and cluster automining
* 0.40.19 (2014-11-26): [[Gelding]] and related profession/skill/etc
* 0.40.18 (2014-11-20): ''Hotfix''; Fixed a smelting issue on Windows
* 0.40.17 (2014-11-19): ''Bugfix'';
* 0.40.16 (2014-11-12): ''Bugfix'';
* 0.40.15 (2014-11-05): ''Bugfix'';
* 0.40.14 (2014-10-25): Thought/emotion rewrite, stopped site invaders from always winning
* 0.40.13 (2014-09-17): ''Bugfix'';
* 0.40.12 (2014-09-10): ''Bugfix'';
* 0.40.11 (2014-09-03): ''Bugfix'';
* 0.40.10 (2014-08-24): ''Bugfix'';
* 0.40.09 (2014-08-17): ''Bugfix''; Misc. bugfixes
* 0.40.08 (2014-08-11): ''Hotfix''; Fixed a crash bug and issues with constructions
* 0.40.07 (2014-08-10): ''Bugfix''; AI and invasion fixes
* 0.40.06 (2014-08-03): ''Bugfix''; stack bugfixes.
* 0.40.05 (2014-07-27): ''Bugfix''; fixed large world slowdown, decreased rampant tree growth, many old and new bugfixes.
* 0.40.04 (2014-07-20): ''Bugfix''; several crash fixes, made saplings grow properly.
* 0.40.03 (2014-07-13): ''Bugfix''; broke save game compatibility again due to more save corruption, several crash fixes.
* 0.40.02 (2014-07-10): ''Bugfix''; broke save game compatibility due to save corruption, several crash fixes.
* 0.40.01 (2014-07-07): ''Release''; Introduced world generation running in the background while fortresses and adventurers progress, un-retiring of fortresses, multiple tile trees, climbing & jumping, and more.

=== Dwarf Fortress v0.34 ===

In a [http://www.bay12games.com/dwarves/index.html devlog] entry for 2011-01-30, Threetoe announced plans for a series of nine numbered releases ("Short-term Goals" on the [http://www.bay12games.com/dwarves/dev.html dev page]) to finish off the long-planned "caravan" development arc. Release 1, improving towns and introducing markets, along with a variety of supernatural creature types, was predicted to have a version number of [http://www.bay12games.com/media/df_talk_14_transcript.html#14.16 0.33 or 0.34] and was released on Valentine's Day 2012 as version 0.34.01.

* [[v0.34:Release information/0.34.11|0.34.11]] (2012-06-04): ''Bugfix''
* [[v0.34:Release information/0.34.10|0.34.10]] (2012-05-21): ''Bugfix''
* [[v0.34:Release information/0.34.09|0.34.09]] (2012-05-17): ''Bugfix''
* [[v0.34:Release information/0.34.08|0.34.08]] (2012-05-14): Hauling overhaul - minecarts and wheelbarrows, more accurate projectiles, reduced mining yields, advanced stockpile/workshop links
* [[v0.34:Release information/0.34.07|0.34.07]] (2012-03-30): ''Bugfix''
* [[v0.34:Release information/0.34.06|0.34.06]] (2012-03-23): Updates to animal training ([[dungeon master]] removed, having been nonfunctional since 0.31.01), return of good/evil trees and shrubs
* [[v0.34:Release information/0.34.05|0.34.05]] (2012-03-06): ''Bugfix''
* [[v0.34:Release information/0.34.04|0.34.04]] (2012-02-29): ''Hotfix''
* [[v0.34:Release information/0.34.03|0.34.03]] (2012-02-28): ''Bugfix''
* [[v0.34:Release information/0.34.02|0.34.02]] (2012-02-18): ''Bugfix''; broke save compatibility due to save corruption, numerous fixes for old issues
* [[v0.34:Release information/0.34.01|0.34.01]] (2012-02-14): Introduction of human cities (shops, marketplaces, sewers, dungeons) and tombs, addition of [[interaction]]s ([[necromancer]]s, [[werebeast]]s, [[vampire]]s, etc.), historical migrants, truly evil regions, updated [[justice]] system,

=== Dwarf Fortress v0.31 ===

* [[v0.31:Release information/0.31.25|0.31.25]] (2011-03-28): ''Hotfix'' -- Final update of version 0.31.
* [[v0.31:Release information/0.31.24|0.31.24]] (2011-03-27): ''Hotfix''
* [[v0.31:Release information/0.31.23|0.31.23]] (2011-03-26): ''Hotfix''
* [[v0.31:Release information/0.31.22|0.31.22]] (2011-03-24): ''Bugfix''
* [[v0.31:Release information/0.31.21|0.31.21]] (2011-03-06): ''Bugfix''
* [[v0.31:Release information/0.31.20|0.31.20]] (2011-03-06): ''Hotfix''
* [[v0.31:Release information/0.31.19|0.31.19]] (2011-02-16): Worldgen starvation, usually wiping out kobolds; grazing; ceramics; jugs, pots, nest boxes, beehives (and bees); site finder changes. Last major 0.31 release, and the (unnumbered) beginning of the caravan arc series.
* [[v0.31:Release information/0.31.18|0.31.18]] (2010-11-16): ''Hotfix''
* [[v0.31:Release information/0.31.17|0.31.17]] (2010-11-11): Bandits, Night Creatures, Bogeyman, Adventure mode improvements, combat aiming, castles
* [[v0.31:Release information/0.31.16|0.31.16]] (2010-10-04): ''Hotfix''
* [[v0.31:Release information/0.31.15|0.31.15]] (2010-10-03): ''Bugfix''
* [[v0.31:Release information/0.31.14|0.31.14]] (2010-09-23): ''Hotfix''
* [[v0.31:Release information/0.31.13|0.31.13]] (2010-09-15): Entity populations, sprawl, river density tweaking, TrueType font support
* [[v0.31:Release information/0.31.12|0.31.12]] (2010-07-25): ''Hotfix''
* [[v0.31:Release information/0.31.11|0.31.11]] (2010-07-23): Art of deities
* [[v0.31:Release information/0.31.10|0.31.10]] (2010-07-11): ''Hotfix''
* [[v0.31:Release information/0.31.09|0.31.09]] (2010-07-10): Adventure mode knapping and butchery, combat improvements
* [[v0.31:Release information/0.31.08|0.31.08]] (2010-06-19): ''Hotfix''
* [[v0.31:Release information/0.31.07|0.31.07]] (2010-06-19): ''Bugfix''
* [[v0.31:Release information/0.31.06|0.31.06]] (2010-06-09): ''Bugfix''
* [[v0.31:Release information/0.31.05|0.31.05]] (2010-06-04): ''Bugfix''
* [[v0.31:Release information/0.31.04|0.31.04]] (2010-05-16): Merge with the 40d19 branch
* [[v0.31:Release information/0.31.03|0.31.03]] (2010-04-12): Ability to create undead in arena
* [[v0.31:Release information/0.31.02|0.31.02]] (2010-04-08): ''Bugfix''
* [[v0.31:Release information/0.31.01|0.31.01]] (2010-04-01): Overhaul of many aspects of the game, first 2010 release

=== 3D Version (before 2010) ===
* [[40d:Release information/''Branch'':|''Branch'':]] 0.28.181.40d2 thru 0.28.181.40d19: OpenGL optimizations, macros, zooming
* [[40d:Release information/0.28.181.40d|0.28.181.40d]] (2008-09-06): ''Bugfix''; [[40d:Cat cancels Store Item in Stockpile: Too injured|Cat bug introduced]]
* [[40d:Release information/0.28.181.40c|0.28.181.40c]] (2008-08-21): ''Hotfix'', partial print now allows specifying a frame count
* [[40d:Release information/0.28.181.40b|0.28.181.40b]] (2008-08-20): Partial print, windowed/fullscreen gridsizes
* [[40d:Release information/0.28.181.40a|0.28.181.40a]] (2008-08-18): Embark profiles added, [[note]]s extended to embark map, customizable forbid [[orders]] added (used ammunition, dead creatures' possessions, etc.), and dwarves now try to store items in partially-filled containers instead of empty ones
* [[40d:Release information/0.28.181.39f|0.28.181.39f]] (2008-08-09): [[Custom grid]] sizes added
* [[40d:Release information/0.28.181.39e|0.28.181.39e]] (2008-07-23): ''Hotfix''
* [[40d:Release information/0.28.181.39d|0.28.181.39d]] (2008-07-23): Added [[Site finder]], can display hidden map features when choosing a site, [[Note]] support implemented, and worldgen presets added
* [[40d:Release information/0.28.181.39c|0.28.181.39c]] (2008-07-16): ''Hotfix''
* [[40d:Release information/0.28.181.39b|0.28.181.39b]] (2008-07-14): ''Hotfix''; trees in [[Elf|Elven]] forest retreats no longer have names
* [[40d:Release information/0.28.181.39a|0.28.181.39a]] (2008-07-13): Lots of worldgen changes, including ethics (leading to wars and conquered sites), dynamic era naming, worldgen roads/bridges/tunnels, megabeasts being killed during worldgen, megabeasts being undead; cats and trained animals are now named on adoption, human weapon stores stock more stuff (including ammo), placing [[construction]]s now destroys engravings, and flying creatures no longer give birth in mid-air
* [[40d:Release information/0.27.176.38c|0.27.176.38c]] (2008-02-24): ''Bugfix''
* [[40d:Release information/0.27.176.38b|0.27.176.38b]] (2008-02-23): First Macintosh-compatible release; Dwarves no longer carry their artifacts around, booze food no longer melts, worlds can now have custom sizes
* [[40d:Release information/0.27.176.38a|0.27.176.38a]] (2008-02-15): Magma pipes now refill, ZERO_RENT and BABY_CHILD_CAP init.txt options were added, strange moods no longer convert workshops, metal crossbows now made by [[weaponsmith]]s instead of [[bowyer]]s, dwarves chat and make friends/grudges and get married, unhappy thoughts from [[masterpiece]] destruction are now reduced based on the number of masterpieces the dwarf has made, and plants can now drown in deep water
* [[40d:Release information/0.27.173.38a|0.27.173.38a]] (2008-02-04): [[Sphere]]s added, lots of new entity tags, numerous worldgen improvements, religions implemented, undead [[ruin]]s removed
* [[40d:Release information/0.27.169.33g|0.27.169.33g]] (2007-12-21): Mud no longer dries up during winter, occupied cages are named according to their contents, brand new "Bring to depot" interface, [[strange mood]]s no longer require glass until you actually make some
* [[40d:Release information/0.27.169.33f|0.27.169.33f]] (2007-12-14): ''Bugfix''; mud and blood no longer spread, auto-[[forbid]] fired ammunition, donkey/horse foals are now named properly, graphics sets can now use custom tiles for appointed nobles, and flux stones now have a value of 2 again.
* [[40d:Release information/0.27.169.33e|0.27.169.33e]] (2007-12-08): ''Bugfix''; in particular, nobles no longer order themselves to be punished for failed mandates, donkeys can now breed, most types of vermin no longer have bones, and most types of fish no longer have lungs or throats
* [[40d:Release information/0.27.169.33d|0.27.169.33d]] (2007-11-30): ''Bugfix''
* [[40d:Release information/0.27.169.33c|0.27.169.33c]] (2007-11-23): Animals screen now labels war dogs and hunting dogs correctly, [[sliver barb]]s now have seeds, and process priority can now be configured in init.txt
* [[40d:Release information/0.27.169.33b|0.27.169.33b]] (2007-11-16): [[Carp]] and other fish no longer gain [[swimming]] skill (making them ''slightly'' less dangerous), and various ore types now properly show up as '*' when mined.
* [[40d:Release information/0.27.169.33a|0.27.169.33a]] (2007-11-01): added [[wood]]en [[block]]s, renamed aluminum ore to "native aluminum", [[mountain gnome]]s and [[dark gnome]]s no longer butcherable
* [[40d:Release information/0.27.169.32a|0.27.169.32a]] (2007-10-29): The very first fully 3D version

=== 2D Version ===
* [[23a:Release information/0.23.130.23a|0.23.130.23a]] (2007-01-18): ''Hotfix'' - Final version
* [[23a:Release information/0.23.125.23b|0.23.125.23b]] (2007-01-16): ''Hotfix''
* [[23a:Release information/0.23.125.23a|0.23.125.23a]] (2007-01-16): Temperature support was further improved, population/FPS caps were added, coffins could now be restricted to only dwarves or only pets, and animals could now be marked for slaughter from their {{K|v}}-{{K|p}} screen. Spirits of fire also got a '''lot''' hotter. For some reason, [[horse]]s are now made of [[iron]].
* [[23a:Release information/0.22.123.23a|0.22.123.23a]] (2006-12-21): ''Hotfix''
* [[23a:Release information/0.22.123.23a|0.22.123.23a]] (2006-12-21): More workshop orders were added - auto collect webs, auto slaughter, auto butcher, auto tan; male cows are now called bulls, and whips can no longer get stuck in opponents
* [[23a:Release information/0.22.121.23b|0.22.121.23b]] (2006-12-16): The ability to disable temperature and weather were added (to boost FPS)
* [[23a:Release information/0.22.121.23a|0.22.121.23a]] (2006-12-14): Bins could now be made from metal, and the embark screen now described your biome and listed what civilizations were nearby
* [[23a:Release information/0.22.120.23b|0.22.120.23b]] (2006-12-10): Improved temperature support was added
* [[23a:Release information/0.22.120.23a|0.22.120.23a]] (2006-11-23): The ability to use custom [[graphics sets]] was added
* [[23a:Release information/0.22.110.23c|0.22.110.23c]] (2006-11-17): ''Hotfix''
* [[23a:Release information/0.22.110.23b|0.22.110.23b]] (2006-11-15): ''Hotfix''
* [[23a:Release information/0.22.110.23a|0.22.110.23a]] (2006-11-17): [[Dye]]s and dyeing were implemented, allowed sewing cloth/leather images into goods, as well as more detailed [[decoration|art]] (historical figures and events, special shapes); standing orders now allowed auto collecting webs and only using dyed cloth
* [[23a:Release information/0.22.110.22f|0.22.110.22f]] (2006-11-03): ''Bugfix''; additionally, butterflies, fireflies, and dragonflies can no longer be kept as pets. [[Boatmurdered]] began in this version.
* [[23a:Release information/0.22.110.22e|0.22.110.22e]] (2006-10-29): ''Hotfix''
* [[23a:Release information/0.22.110.22d|0.22.110.22d]] (2006-10-29): ''Hotfix''
* [[23a:Release information/0.22.110.22c|0.22.110.22c]] (2006-10-29): Custom [[stockpile]]s were added (previously, there were only 16 basic stockpile types; things like [[potash]] would be stored with your metal bars and you could not force [[seed]]s to be kept near the farm).
* [[23a:Release information/0.22.110.22b|0.22.110.22b]] (2006-10-21): ''Hotfix''
* [[23a:Release information/0.22.110.22a|0.22.110.22a]] (2006-10-21): Inventory system changes (most notably, gloves and boots were split into two items (left & right for gloves))
* [[23a:Release information/0.22.107.21a|0.22.107.21a]] (2006-10-02): Various changes to [[adventurer mode]] - guards and families, plus "." as a wait key
* [[23a:Release information/0.21.105.21a|0.21.105.21a]] (2006-09-25): ''Hotfix''
* [[23a:Release information/0.21.104.21c|0.21.104.21c]] (2006-09-25): Making potash no longer required making ashes into lye first.
* [[23a:Release information/0.21.104.21b|0.21.104.21b]] (2006-09-16): Workshop profiles were added, along with showing genders on the Animal status screen
* [[23a:Release information/0.21.104.21a|0.21.104.21a]] (2006-09-08): [[Designation|Designating]] with the mouse was added
* [[23a:Release information/0.21.104.19d|0.21.104.19d]] (2006-09-02): ''Bugfix''
* [[23a:Release information/0.21.104.19c|0.21.104.19c]] (2006-09-02): The ability to hide engravings was added, announcement consolidation (x15), seasonal blood cleanup was temporarily added (and would remain until version 0.31)
* [[23a:Release information/0.21.104.19b|0.21.104.19b]] (2006-08-27): ''Bugfix''
* [[23a:Release information/0.21.104.19a|0.21.104.19a]] (2006-08-27): The ability to "chasm" items was added (complete with attacks from chasm creatures as a result), as well as butchering cats
* [[23a:Release information/0.21.102.19a|0.21.102.19a]] (2006-08-24): Dwarves could now have custom nicknames and professions, fullscreen could be toggled, starting animals would have mixed genders, horses could breed
* [[23a:Release information/0.21.101.19d|0.21.101.19d]] (2006-08-21): ''Bugfix''
* [[23a:Release information/0.21.101.19c|0.21.101.19c]] (2006-08-20): ''Bugfix''
* [[23a:Release information/0.21.101.19b|0.21.101.19b]] (2006-08-20): ''Bugfix''
* [[23a:Release information/0.21.101.19a|0.21.101.19a]] (2006-08-19): Adventurers could now have custom first names
* [[23a:Release information/0.21.100.19a|0.21.100.19a]] (2006-08-16): Gender symbol was added to unit views, config options for disabling sound and the intro movie, command-line world generation, ability to export local map
* [[23a:Release information/0.21.95.19c|0.21.95.19c]] (2006-08-14): Farm plot fertilization could be controlled directly
* [[23a:Release information/0.21.95.19b|0.21.95.19b]] (2006-08-13): ''Bugfix''
* [[23a:Release information/0.21.95.19a|0.21.95.19a]] (2006-08-12): ''Bugfix''
* [[23a:Release information/0.21.93.19c|0.21.93.19c]] (2006-08-10): ''Bugfix''
* [[23a:Release information/0.21.93.19b|0.21.93.19b]] (2006-08-10): ''Bugfix''
* [[23a:Release information/0.21.93.19a|0.21.93.19a]] (2006-08-08): Initial public release

== Bugs ==
Please report bugs on the [https://dwarffortress.mantishub.io/ official bug tracker], and optionally add them to [[Known bugs and issues]]. Please do not add them to this page.

Release information

2023-01-06T19:00:24Z

Jan:

Mod

2023-01-06T18:50:47Z

Jan: /* Objects and graphics folder */ raw filename seem to matter

{{For/see|using mods and their basic structure|[[modding]] about making mods}}

A '''mod''' (short for modification) is an alteration of the game and the objective of modding. Modifications can range from small tweaks to complete overhauls.

== Installing Mods ==

Mods can be acquired using the [https://steamcommunity.com/app/975370/workshop/ steam workshop] (if using Steam version), a manual download from [[Bay 12 Forums]] or third party websites (like [https://dffd.bay12games.com/ DFFD]), or by [[Modding|creating]] one yourself.

Users of the Steam version can subscribe to mods on Steam Workshop, once the download is complete they will be available when creating a new world automatically. Otherwise, manually download the mod, then place the mod zip file or the unzipped mod folder into the Dwarf Fortress [[mod folder]] (if this folder doesn't exist, you can create it.) You can have more than one mod in the mod folder, including different version of the same mod. The game will detect all mods that are properly made in this folder and let the user select which mods to play (see bellow.)

== Enabling Mods ==
[[File:Ui-p-mod-selection.png|thumb|world generation mod menu]]

When [[World generation|creating a world]] and choosing its initial parameters, if you have a mod available, there should be a '''Mods''' button at the bottom of the screen. Pressing this will let you select which mods you'd like to enable and what the load order should be. You should put mods at the end of the mod list after the vanilla objects if you don't have any further information, so that they can reference vanilla objects after those are loaded.

Something something load order basic

<div class="" style="padding: 0.8em 1em; margin: 0.5rem 0; background: #fcf8e3; border-left: 5px solid #aa6708;">
* Mods are enabled per world and can not be disabled afterwards, however, it is possibly to manually modify the game file as we did in previous versions by applying the mods directly to <code>[[Game folder|<Dwarf Fortress>]]/data/vanilla</code>. Be ware this method has the disadvantage of being a permanent change for all worlds and may break your game.

* Unlike the previous versions of Dwarf Fortress, mods no longer live inside save files and must be installed on every computer where saves using those mods are going to be loaded. Once a world is created that uses mods, then the game will copy the mod to the <code>[[Game folder|<Dwarf Fortress>]]/data/installed_mods</code> folder. That is the version that the game actually uses.
</div>

== Updating Mods ==
If a world is using a mod that's been updated, and is currently using an older version of that mod, the player will be prompted about this when a save is loading. Causing a message like the following to appear: 
[[File:mod_version_v50_prompt.png]]

When this happens, you have the choice of simply updating the mod, updating ''all'' mods at once, continuing to use the older version of the mod in question without updating, selecting the previous task but not updating ''any'' possibly outdated mods or simply returning to the title screen.

== Modding ==

Dwarf Fortress supports mods in the form of new objects and tiles. Each mod is a zip file or unzipped folder with the required format (see below.)

=== Mod Format===

Mods contain an info.txt file and either an "objects" folder or a "graphics" folder (or both.) All of the vanilla objects in the game too use this format. Your mod folder should look something like this:

[[File:Folder-orange.svg|20px|link=]] Mod Name
├ [[File:Text-x-generic.svg|20px|link=]] info.txt
├ [[File:Text-x-generic.svg|20px|link=]] preview.png
├ [[File:Folder.svg|20px|link=]] objects
└ [[File:Folder.svg|20px|link=]] graphics

=== Mod info ===
{{main|Mod info token}}

Each mod must have a <code>info.txt</code> at the root of your mod folder. It has a few fields defining basic metadata information about the mod and can be edited using any text editor (like notepad++). See Example:

{{code|
[ID:wiki_example]
[NAME:Wiki Example Mod]
[NUMERIC_VERSION:5001]
[DISPLAYED_VERSION:50.01]
[EARLIEST_COMPATIBLE_NUMERIC_VERSION:5001]
[EARLIEST_COMPATIBLE_DISPLAYED_VERSION:50.01]
[AUTHOR:Dwarf Fortress Wiki]
[DESCRIPTION:This is an example mod. This text shows up in-game.]

[STEAM_TITLE:Wiki Example Mod]
[STEAM_DESCRIPTION:This text shows up on Steam Workshop.]
[STEAM_TAG:mod]
[STEAM_KEY_VALUE_TAG:test:stuff]
[STEAM_METADATA:metadata test]
[STEAM_CHANGELOG:Made some changes. Shown in 'Change Notes' tab.]

[STEAM_FILE_ID:#########]
}}

Only <code>ID</code> and <code>NAME</code> are required to appear in the in-game mod menu.

STEAM tags are only used by Steam.
* The <code>STEAM_FILE_ID</code> used to identify the mod in the Workshop. This is automatically managed when uploading to Steam the first time. And required if you wish to update an existing Steam Workshop mod.
* The <code>STEAM_TAG</code> and <code>STEAM_KEY_VALUE_TAG</code> are used by Steams search engine and the categorization. You can use as many entries you want, use a separate tag for each one.
* You can also create a thumbnail for your mod by creating an image called <code>preview.png</code> in the same level as your info.txt file. This image will become the thumbnail when the mod is uploaded to steam workshop. The image should be less than 1MB in size.

=== Objects and graphics folder ===

At the root of your mod folder you can have a <code>objects\</code> and <code>graphics\</code> folder, this is where all the [[raw file]]s or [[graphics]] goes (exactly the same as objects from previous versions of Dwarf Fortress) allowing you to tweak or add new content for the game. It's beyond the scope of this short guide to go into what specific tags do, but the vanilla objects and previous mods by members of the community will give you plenty of examples to work with. See: [[modding]].

The graphics filenames are not important, furthermore they can be arbitrarily nested into other sub-folders to help you organize your mod content.

== Publishing mods ==

There are two official platforms for publishing ''Dwarf Fortress'' mods, recommended because it's easy for people to find them there. These are [https://steamcommunity.com/app/975370/workshop/ Steam Workshop] and [https://dffd.bay12games.com/ the Dwarf Fortress File Depot (DFFD)].

=== Publishing on Steam Workshop ===

To upload a mod to Steam Workshop, you need to add STEAM tags to the <code>info.txt</code> file (see above.) Afterward, you put the unzipped mod folder in the "<code>mods/mod_upload</code>" folder. Then select Mods from the title menu, and upload your mods using the button you'll see there. Other Steam users will be able to subscribe to your mod immediately once it is uploaded.

Once the upload process is completed successfully, you'll find a <code>[STEAM_FILE_ID:#########]</code> appended to your info.txt. Make sure this entry is included for future uploads if you want to make changes to your mod and have it overwrite the existing entry on the workshop. Otherwise you'll create a new entry every time you upload.

=== Publishing on DFFD ===

In addition to Steam Workshop, it is recommended you upload your mod to DFFD. This allows people who play ''[[Classic|Dwarf Fortress Classic]]'', or ''[[Premium]]'' via Itch.io, to also download and play your mod. To publish/upload a file to DFFD you first need to create an account.

For legal reasons, mods that contain graphics derived from the ''Premium'' graphics should not be uploaded outside Steam Workshop. For this reason, you might want to separate your mod into two parts: the first without graphics, which is uploaded to both DFFD and Steam Workshop, and the second with ''only'' the graphics, uploaded only to Workshop. Of course, this is not an issue if your graphics are not based off the ''Premium'' ones.

[[Category:Modding]]

Talk:Raw file

2023-01-06T18:48:16Z

Jan: /* Parsing changes */ new section

== One object type per file? ==

iirc I seen this mentioned on the forums, if so can someone please make note of it on the page, to avoid confusion of people using multiple objects per file. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 11:13, 3 January 2023 (UTC)

== Parsing changes ==

It seems that filenames are no longer irrelevant. In my test it appears that filename must start with object name:
Filename : <Object-name>-whatever-you-want-.txt
With each raw file beginning with same file name and presumably followed by the same <code>[OBJECT:<Object-name>]</code> (I haven't tested the last) --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:48, 6 January 2023 (UTC)

Amphibian man

2023-01-06T18:36:46Z

Jan: no longer an animal person. not sure if it still tribal

{{migrated article}}
{{Quality|Unrated}}
{{Creaturelookup/0
|vary=no
|contrib=no
|death=nobutcher
}}
{{av}}
{{creaturedesc}}
'''Amphibian men''' are one of the many underworld tribal [[Creature]] that can be found on any [[cavern]] level milling around piles of [[food|meat]] and [[leather|tanned hides]]. They are equivalent in size to [[kobold]]s, but are less agile.

Approach with caution, unless the tribe is friendly. If the tribe is friendly, feel free to take advantage of them in imperialistic tradition and steal all their resources without compensation. To check whether a tribe of amphibian men is friendly, press {{k|u}} to view the unit list. The amphibian men will be labeled as either hostile or friendly. Alternatively, press {{k|v}} to view one of their profiles - if a hostile amphibian man kills a [[forgotten beast]], they will become friendly. However, they will not attack their fellow amphibian men - this is true of all underground animal man tribes.

Like many underground races, the danger of amphibian men is not to be found in their wooden weapons, but in the substances found smeared on them. Amphibian men use many [[syndrome|poisons]], some of which can be deadly. They will launch group attacks on your fort, and have the ability to swim through your reservoirs and launch amphibious assaults on your [[fisherdwarf|fisherdwarves]]. Despite their description, they do not possess the{{token|EVIL}}token and are not any more malevolent than any other race of animal people.

Some [[dwarves]] [[Preferences|like]] amphibian men for their ''terrifying features''.

[[File:amph_man_preview.jpg|thumb|230px|center|Has a very bad lisp issue.]]

{{gamedata}}
{{gamedata|title=Entity ([[civilization]]) Raws|{{raw|v50:entity_default.txt|ENTITY|SUBTERRANEAN_ANIMAL_PEOPLES}}}}
{{Creatures}}
{{Category|Humanoids}}
{{Category|Races}}

User:Jan/sandbox

2023-01-06T10:56:13Z

Jan:

__TOC__

== Misc variants ==

{| style="padding: 0.5em 0.5em 0 0.5em; margin: 0.5rem 0; background: #dff0d8; border: 2px solid #afbdaa;"
| This article is about the current version of DF.
|-
|<div style="position: relative">
<div class="mw-collapsible" id="mw-customcollapsible-version-toggle">[[File:Eo circle green white caret-double-down.svg|10px|link=]] More...</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-version-toggle">[[File:Eo circle green white caret-double-down.svg|10px|link=]] Collapsebla bla bla bla bla</div></div>
|}

[[:Release information|v50.05 ▼]] This article is about the current version of DF.
<div style="z-index: 101; position: absolute; background-color: #f8f9fa; color: #202122;">
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-111" style="padding:0.5em 1em; border: 1px solid #a2a9b1;">[[DF2014:{{PAGENAME}}|v0.47]] [[v0.34:{{PAGENAME}}|v0.34]] [[v0.31:{{PAGENAME}}|v0.31]] [[40d:{{PAGENAME}}|v0.28]] [[23a:{{PAGENAME}}|v0.23]]</div></div>

<div class="" style="padding: 0.8em 1em; margin: 0.5rem 0; border-width: 0; background-color: #E7F2F8; border-radius: 4px; font-size: 84%; line-height: 1.2em;">
This article is about the current version of DF ( v{{current/version}} | [[DF2014:{{PAGENAME}}|v0.47.05]] | [[v0.34:{{PAGENAME}}|v0.34]] | [[v0.31:{{PAGENAME}}|v0.31]] | [[40d:{{PAGENAME}}|v0.28]] | [[23a:{{PAGENAME}}|v0.23]] )
</div>

== In game==

<div style="width:100px; padding:5px; background-color: #187c36; border: 2px outset #22b14c; color:white; {{border-radius|3px}}">Start</div >
<div style="width:100px; padding:5px; background-color: #4b4b4b; border: 2px outset #786c80; color:white; {{border-radius|3px}}">Quit</div >
<div style="width:100px; padding:5px; background-color: #a40d14; border: 2px outset #ed1c24; color:white; {{border-radius|3px}}">Delete</div >

=== build shortkeys ===

:[[file:ui_b.png]]{{key|b}}Build
::[[file:ui_bo.png]]{{key|o}}Workshops
:::[[file:ui_bol.png]]{{key|l}}Clothing and Leather
::::[[file:ui_boll.png]]{{key|l}}Leather
::::[[file:ui_bolo.png]]{{key|o}}Loom
::::[[file:ui_bolk.png]]{{key|k}}Clothes
::::[[file:ui_boly.png]]{{key|y}}Dyer
:::[[file:ui_bof.png]]{{key|f}}Farming
::::[[file:ui_bofp.png]]{{key|p}}Farm plot
::::[[file:ui_bofl.png]]{{key|l}}Still
::::[[file:ui_bofb.png]]{{key|b}}
::::[[file:ui_boft.png]]{{key|t}}
::::[[file:ui_bofy.png]]{{key|y}}
::::[[file:ui_bofk.png]]{{key|k}}
::::[[file:ui_boff.png]]{{key|f}}
::::[[file:ui_bofq.png]]{{key|q}}
::::[[file:ui_bofv.png]]{{key|v}}
::::[[file:ui_bofn.png]]{{key|n}}
::::[[file:ui_bofh.png]]{{key|h}}
:::[[file:ui_bou.png]]{{key|u}}Furnaces
::::[[file:ui_boug.png]]{{key|g}}Glass Furnace
::::[[file:ui_bouk.png]]{{key|k}}Klin
::::[[file:ui_bouG.png]]{{key|G}}Magma glass Furnace
::::[[file:ui_bouK.png]]{{key|K}}
::::[[file:ui_bouL.png]]{{key|L}}
::::[[file:ui_boul.png]]{{key|l}}
::::[[file:ui_bouf.png]]{{key|f}}
:::[[file:ui_boy.png]]{{key|y}}
:::[[file:ui_bob.png]]{{key|b}}
:::[[file:ui_bop.png]]{{key|p}}
:::[[file:ui_bor.png]]{{key|r}}
:::[[file:ui_boj.png]]{{key|j}}
:::[[file:ui_boI.png]]{{key|I}}
:::[[file:ui_boh.png]]{{key|h}}
:::[[file:ui_boi.png]]{{key|i}}
:::[[file:ui_boR.png]]{{key|R}}
:::[[file:ui_bog.png]]{{key|g}}
:::[[file:ui_boP.png]]{{key|P}}
:::[[file:ui_bot.png]]{{key|t}}
::[[file:ui_bf.png]]{{key|f}}Furniture
:::[[file:ui_bfb.png]]{{key|b}}Bed
:::[[file:ui_bfr.png]]{{key|r}}Chair
:::[[file:ui_bft.png]]{{key|t}}
:::[[file:ui_bfh.png]]{{key|h}}
:::[[file:ui_bfn.png]]{{key|n}}
:::[[file:ui_bfx.png]]{{key|x}}
:::[[file:ui_bfl.png]]{{key|l}}
:::[[file:ui_bfu.png]]{{key|u}}
:::[[file:ui_bfT.png]]{{key|T}}
:::[[file:ui_bfo.png]]{{key|o}}
:::[[file:ui_bfy.png]]{{key|y}}
:::[[file:ui_bfp.png]]{{key|p}}
:::[[file:ui_bfi.png]]{{key|i}}
::[[file:ui_bp.png]]{{key|p}}Doors/Hatches
:::[[file:ui_bpr.png]]{{key|r}}
:::[[file:ui_bph.png]]{{key|h}}
::[[file:ui_bn.png]]{{key|n}}Constructions
:::[[file:ui_bnl.png]]{{key|l}}wall
:::[[file:ui_bnf.png]]{{key|f}}
:::[[file:ui_bnr.png]]{{key|r}}
:::[[file:ui_bnt.png]]{{key|t}}
:::[[file:ui_bnb.png]]{{key|b}}
:::[[file:ui_bno.png]]{{key|o}}
:::[[file:ui_bnO.png]]{{key|O}}
:::[[file:ui_bnF.png]]{{key|F}}
:::[[file:ui_bnG.png]]{{key|G}}
:::[[file:ui_bng.png]]{{key|g}}
:::[[file:ui_bnM.png]]{{key|M}}
:::[[file:ui_bnm.png]]{{key|m}}
:::[[file:ui_bny.png]]{{key|y}}
:::[[file:ui_bnY.png]]{{key|Y}}
:::[[file:ui_bnp.png]]{{key|p}}
:::[[file:ui_bnk.png]]{{key|k}}
:::[[file:ui_bnK.png]]{{key|K}}
::[[file:ui_bm.png]]{{key|m}}Machines/Fluids
:::[[file:ui_bml.png]]{{key|l}}
:::[[file:ui_bmL.png]]{{key|L}}
:::[[file:ui_bmf.png]]{{key|f}}
:::[[file:ui_bmp.png]]{{key|p}}
:::[[file:ui_bmh.png]]{{key|h}}
:::[[file:ui_bmm.png]]{{key|m}}
:::[[file:ui_bmg.png]]{{key|g}}
:::[[file:ui_bma.png]]{{key|a}}
:::[[file:ui_bmA.png]]{{key|A}}
:::[[file:ui_bmn.png]]{{key|n}}
:::[[file:ui_bmr.png]]{{key|r}}
::[[file:ui_br.png]]{{key|r}}Cages/Restraints
:::[[file:ui_brh.png]]{{key|h}}
:::[[file:ui_brg.png]]{{key|g}}
:::[[file:ui_brt.png]]{{key|t}}
::[[file:ui_bt.png]]{{key|t}}Trap
:::[[file:ui_btp.png]]{{key|p}}
:::[[file:ui_btt.png]]{{key|t}}
:::[[file:ui_bto.png]]{{key|o}}
:::[[file:ui_btg.png]]{{key|g}}
:::[[file:ui_btu.png]]{{key|u}}
::[[file:ui_by.png]]{{key|y}}Military
:::[[file:ui_byt.png]]{{key|t}}
:::[[file:ui_byr.png]]{{key|r}}
:::[[file:ui_byn.png]]{{key|n}}
:::[[file:ui_byb.png]]{{key|b}}
:::[[file:ui_byp.png]]{{key|p}}
::[[file:ui_bT.png]]{{key|T}}Trade Depot

== Metal example ==
{|
|- valign=top
|
{{infostart|{{{name|Pig iron}}}}}
{{infocell|{{{sample|[[File:PigIron Swatch.png|256px|center|frameless]]}}}}}
{{infocell|{{Metal/picture|ingredients={{#if:{{{color3|}}}|3|{{#if:{{{color2|7:0:1}}}|2|1}}}}|color={{{color|7:0:1}}}|
tile1={{{tile1|≡}}}|color1={{{color1|0:7:1}}}|
tile2={{{tile2|≡}}}|color2={{{color2|0:7:1}}}|
tile3={{{tile3|≡}}}|color3={{{color3}}}}}}}
{{infoheader|Uses}}
{{infocell|{{{uses|
* Make [[steel]] at [[smelter]]}}}
* [[Construction]]}}{{#if:{{{ore|}}}|{{infoheader|[[Ore]]}}
{{infocell|{{{ore|}}}}}}}
{{#if:{{{recipe|}}}|{{infoheader|Recipe}}
{{infocell|{{{recipe|
* 1 [[Iron]] [[bar]]
* 1 [[Flux]] [[stone]]
* 1 [[Fuel|Coal]] [[bar]]}}}}}}}
{{infoheader|Properties}}
{{infocell|{{{properties|
* [[Material value]] 10
{{firemagmasafe|yes|yes}}
* [[Melting point]] {{ct|12106}}
* [[Boiling point]] {{ct|13968}}
* [[Ignition point]] none
* [[Solid density]] 7850
* Liquid [[density]] 6980
* [[Specific heat]] 500}}}}}
{{#ifeq:{{{wiki}}}|no||{{infocell|style=text-align:center; background-color: #eee; border-top: 1px solid #aaa|1=[[wikipedia:{{#if:{{{wiki|}}}|{{{wiki}}}|{{{name|Pig iron}}}}}|Wikipedia article]]}}|{{!-}}}}
{{infoend}}
|
{{infostart|{{{name|Pig iron}}}}}
|- style="background-color:#eaecf0;"
| {{{sample|[[File:PigIron Swatch.png|100px|center|frameless]]}}}
| {{Metal/picture|ingredients={{#if:{{{color3|}}}|3|{{#if:{{{color2|}}}|2|1}}}}|color={{{color|0:7:1}}}|
tile1={{{tile1|≡}}}|color1={{{color1|0:7:1}}}|
tile2={{{tile2|≡}}}|color2={{{color2|0:7:1}}}|
tile3={{{tile3|≡}}}|color3={{{color3}}}}}
{{infoheader|Uses}}
{{infocell|{{{uses|
* Make [[steel]] at [[smelter]]}}}
* [[Construction]]}}{{#if:{{{ore|}}}|{{infoheader|[[Ore]]}}
{{infocell|{{{ore|}}}}}}}
{{#if:{{{recipe|}}}|{{infoheader|Recipe}}
{{infocell|{{{recipe|
* 1 [[Iron]] [[bar]]
* 1 [[Flux]] [[stone]]
* 1 [[Fuel|Coal]] [[bar]]}}}}}}}
{{infoheader|Properties}}
{{infocell|{{{properties|
* [[Material value]] 10
{{firemagmasafe|yes|yes}}
* [[Melting point]] {{ct|12106}}
* [[Boiling point]] {{ct|13968}}
* [[Ignition point]] none
* [[Solid density]] 7850
* Liquid [[density]] 6980
* [[Specific heat]] 500}}}}}
{{#ifeq:{{{wiki}}}|no||{{infocell|style=text-align:center; background-color: #eee; border-top: 1px solid #aaa|1=[[wikipedia:{{#if:{{{wiki|}}}|{{{wiki}}}|{{{name|Pig iron}}}}}|Wikipedia article]]}}|{{!-}}}}
{{infoend}}
|
{{infostart|{{{name|Pig iron <div class="mw-customtoggle-infoboxtab mw-ui-button mw-ui-progressive" style="float: right;">toggle</div>}}}}}
|- style="background-color:#eaecf0;"
|{{{sample|[[File:PigIron Swatch.png|100px|center|frameless]]}}}{{Metal/picture|ingredients={{#if:{{{color3|}}}|3|{{#if:{{{color2|}}}|2|1}}}}|color={{{color|0:7:1}}}|
tile1={{{tile1|≡}}}|color1={{{color1|0:7:1}}}|
tile2={{{tile2|≡}}}|color2={{{color2|0:7:1}}}|
tile3={{{tile3|≡}}}|color3={{{color3}}}}}
{{infoheader|Uses}}
{{infocell|{{{uses|
* Make [[steel]] at [[smelter]]}}}
* [[Construction]]}}{{#if:{{{ore|}}}|{{infoheader|[[Ore]]}}
{{infocell|{{{ore|}}}}}}}
{{#if:{{{recipe|}}}|{{infoheader|Recipe}}
{{infocell|{{{recipe|
* 1 [[Iron]] [[bar]]
* 1 [[Flux]] [[stone]]
* 1 [[Fuel|Coal]] [[bar]]}}}}}}}
{{infoheader|Properties}}
{{infocell|{{{properties|
* [[Material value]] 10
{{firemagmasafe|yes|yes}}
* [[Melting point]] {{ct|12106}}
* [[Boiling point]] {{ct|13968}}
* [[Ignition point]] none
* [[Solid density]] 7850
* Liquid [[density]] 6980
* [[Specific heat]] 500}}}}}
{{#ifeq:{{{wiki}}}|no||{{infocell|style=text-align:center; background-color: #eee; border-top: 1px solid #aaa|1=[[wikipedia:{{#if:{{{wiki|}}}|{{{wiki}}}|{{{name|Pig iron}}}}}|Wikipedia article]]}}|{{!-}}}}
{{infoend}}
|
{{infostart|{{{name|Pig iron}}}}}
|- style="background-color:#eaecf0;"
|[[File:OOjs UI icon eyeClosed-progressive.svg|right|30px|link=]]{{{sample|[[File:PigIron Swatch.png|100px|center|frameless]]}}}{{Metal/picture|ingredients={{#if:{{{color3|}}}|3|{{#if:{{{color2|}}}|2|1}}}}|color={{{color|0:7:1}}}|
tile1={{{tile1|≡}}}|color1={{{color1|0:7:1}}}|
tile2={{{tile2|≡}}}|color2={{{color2|0:7:1}}}|
tile3={{{tile3|≡}}}|color3={{{color3}}}}}
{{infoheader|Uses}}
{{infocell|{{{uses|
* Make [[steel]] at [[smelter]]}}}
* [[Construction]]}}{{#if:{{{ore|}}}|{{infoheader|[[Ore]]}}
{{infocell|{{{ore|}}}}}}}
{{#if:{{{recipe|}}}|{{infoheader|Recipe}}
{{infocell|{{{recipe|
* 1 [[Iron]] [[bar]]
* 1 [[Flux]] [[stone]]
* 1 [[Fuel|Coal]] [[bar]]}}}}}}}
{{infoheader|Properties}}
{{infocell|{{{properties|
* [[Material value]] 10
{{firemagmasafe|yes|yes}}
* [[Melting point]] {{ct|12106}}
* [[Boiling point]] {{ct|13968}}
* [[Ignition point]] none
* [[Solid density]] 7850
* Liquid [[density]] 6980
* [[Specific heat]] 500}}}}}
{{#ifeq:{{{wiki}}}|no||{{infocell|style=text-align:center; background-color: #eee; border-top: 1px solid #aaa|1=[[wikipedia:{{#if:{{{wiki|}}}|{{{wiki}}}|{{{name|Pig iron}}}}}|Wikipedia article]]}}|{{!-}}}}
{{infoend}}
|
{{infostart|{{{name|Pig iron}}}}}
|- style=""
|
[[File:Toggle_grey.png|right|50px|link=]]
[[File:Toggle orange.png|right|50px|link=]]
{{{sample|[[File:PigIron Swatch.png|100px|center|frameless]]}}}{{Metal/picture|ingredients={{#if:{{{color3|}}}|3|{{#if:{{{color2|}}}|2|1}}}}|color={{{color|0:7:1}}}|
tile1={{{tile1|≡}}}|color1={{{color1|0:7:1}}}|
tile2={{{tile2|≡}}}|color2={{{color2|0:7:1}}}|
tile3={{{tile3|≡}}}|color3={{{color3}}}}}
{{infoheader|Uses}}
{{infocell|{{{uses|
* Make [[steel]] at [[smelter]]}}}
* [[Construction]]}}{{#if:{{{ore|}}}|{{infoheader|[[Ore]]}}
{{infocell|{{{ore|}}}}}}}
{{#if:{{{recipe|}}}|{{infoheader|Recipe}}
{{infocell|{{{recipe|
* 1 [[Iron]] [[bar]]
* 1 [[Flux]] [[stone]]
* 1 [[Fuel|Coal]] [[bar]]}}}}}}}
{{infoheader|Properties}}
{{infocell|{{{properties|
* [[Material value]] 10
{{firemagmasafe|yes|yes}}
* [[Melting point]] {{ct|12106}}
* [[Boiling point]] {{ct|13968}}
* [[Ignition point]] none
* [[Solid density]] 7850
* Liquid [[density]] 6980
* [[Specific heat]] 500}}}}}
{{#ifeq:{{{wiki}}}|no||{{infocell|style=text-align:center; background-color: #eee; border-top: 1px solid #aaa|1=[[wikipedia:{{#if:{{{wiki|}}}|{{{wiki}}}|{{{name|Pig iron}}}}}|Wikipedia article]]}}|{{!-}}}}
{{infoend}}
|}
== Workshop example ==

* [[:File:Carpenter's workshop.png]]
[[:Category:Picture Templates]]
* [[Template:Picture Carpenter's workshop]]
[[:Category:Floor_Plan_Templates]]
* [[Template:Floor Plan Carpenter's workshop]]

* 3x3 96px 96-118py ([[Soap maker's workshop]])
* 5x5 160px 162-177py ([[Siege workshop]]
* 1x1 32px 47py ([[Screw press]])
* 2x2
* 3x1 96px 46py ([[Water wheel]])

=== All version ===
{|
|- valign=top
|
{| style="width:200px; background-color:#eaecf0;"
|+ Base
|- valign=top
|colspan=2|Change view
|-
|rowspan=2 style="width:50%;"|
<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">[[File:Carpenter's workshop.png]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab""><center>
{| style="font-size: 175%; border-spacing: 0; background-color: black; border: 2px solid black"
|- 
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"| {{Raw Tile|"|7:0:0}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|{{=}}|6:0:0}}
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"|
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|]|0:0:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
|}</center></div>
|
{| style="border-spacing:5px;"
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|
{| style="width:200px; background-color:#eaecf0; border-collapse: collapse; "
|+ 3x3
|- style="border-bottom:2px solid #3366cc; "
|colspan=2 style="text-align: right;"|<div class="mw-customtoggle-infoboxtab mw-ui-button mw-ui-progressive" style="float:left; border-top-right-radius: 10px; border-top-left-radius:10px;">toggle</div>{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|- valign=top
|rowspan=2 style="width:50%;"|
<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">[[File:Carpenter's workshop.png]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab""><center>
{| style="font-size: 175%; border-spacing: 0; background-color: black; border: 2px solid black"
|- 
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"| {{Raw Tile|"|7:0:0}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|{{=}}|6:0:0}}
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"|
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|]|0:0:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
|}</center></div>
|
{| style="border-spacing:5px;"
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|
{| style="width:200px; background-color:#eaecf0; border-collapse: collapse; "
|+ 5x5
|- style="border-bottom:2px solid #3366cc; "
|<div class="mw-customtoggle-infoboxtab mw-ui-button mw-ui-progressive" style="border-top-right-radius: 10px; border-top-left-radius:10px;">toggle</div>
|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|- valign=top
|colspan=2|<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">
[[File:Siege workshop.png|center|160px]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab"">
{|
|rowspan=2 style="width:50%; font-size: 125%;"|<center>{{Template:Picture Siege workshop}}</center>
|style="line-height: 1em; font-size: 125%;"|
{| style="border-spacing:4px;"
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|}
|
{| style="width:200px; height:100px; padding:10px; background-color:#eaecf0; border-collapse: collapse;"
|+ 1x1
|- style="border-bottom:2px solid #3366cc;"
| colspan=3 style="text-align:center;"|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|-
| style="border-right: 1px dotted #545557;"|[[File:Screw_press.png|32px|center|link=]]
| style="font-size:125%;"|<center>{{Template:Picture Screw press}}</center>
| style="border-left: 1px dotted #545557;"|<center>{{Template:Floor Plan Screw press}}</center>
|}
|
{| style="width:200px; height:100px; padding:10px; background-color:#eaecf0; border-collapse: collapse;"
|+ 1x3
|- style="border-bottom:2px solid #3366cc;"
| colspan=3 style="text-align:center;"|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|-
| style="border-right: 1px dotted #545557;"|[[File:water_wheel.png|32px|center|link=]]
| style="font-size:125%;"|<center>{{Template:Picture Water wheel}}</center>
| style="border-left: 1px dotted #545557;line-height:normal;"|<center>{{Template:Floor Plan Water wheel}}</center>
|}
|}

== Gamefolder ==

If you installed ''Dwarf Fortress'' on Arch Linux using <tt>pacman</tt>, then running <tt>dwarffortress</tt> will dump the configuration files you should edit into your home directory under <tt>.dwarffortress</tt> - editing the files under <tt>/opt/dwarffortress/data/init</tt> will ''not'' change how the game behaves.

SU by default we believe the itch.io app stores game files in `%APPDATA%/itch/apps`, at least on windows.

== Misc ==

{{User:Lethosor/header}}

[[:Category:Message_box_templates]]
{{ambox
|type=warn
|text=Welcome to the Dwarf Fortress Wiki! 
'''Please do not add content specific to v50 (the new DF premium release) yet!''' We are working on a migration that will be complete in the next few days. Adding content for v0.47 or to other pages is still encouraged.
}}

<div class="" style="padding: 0.8em 1em; margin: 0.5rem 0; background: #d9edf7; border-left: 5px solid #1b809e;">
{{:Main_Page/Quote}}
</div>
<div class="" style="padding: 0.8em 1em; margin: 0.5rem 0; background: #fcf8e3; border-left: 5px solid #aa6708;">
{{:Main_Page/Quote}}
</div>
<div class="" style="padding: 0.8em 1em; margin: 0.5rem 0; background: #dff0d8; border-left: 5px solid #3c763d;">
{{:Main_Page/Quote}}
</div>
</div>
<div class="" style="padding: 0.8em 1em; margin: 0.5rem 0; background: #f2dede; border-left: 5px solid #ce4844;">
{{:Main_Page/Quote}}
</div>

How does a dwarven light bulb looks like?

{| class="" style="width:100%; margin: 0.5rem 0; background: #d9edf7; border-left: 5px solid #1b809e;"
| style="" | [[File:BulbIcon.svg|link=]]
| Style="padding: 0.8em 1em 0.8em 0px;" | {{:Main_Page/Quote}}
|}
{| class="" style="width:100%; margin: 0.5rem 0; background: #d9edf7; border-left: 5px solid #1b809e;"
| style="" | [[File:BulbIcon.svg|75px|link=]]
| Style="padding: 0.8em 1em 0.8em 0px;" |
{{:Main_Page/Quote}}

{{:Main_Page/Quote}}

{{:Main_Page/Quote}}

{{:Main_Page/Quote}}
|}

[[File:Bulbgraph.png|18px|link=]] '''Note''': {{:Main_Page/Quote}}

-----

<gallery mode="packed-hover">
File:Dwarf head pixel.png
File:D4Dwarf.png
File:DFDefault.png
File:Dwarven science stretched.png
File:Beer mug.svg
File:Books-aj.svg
File:Forge Noun project 1044767.svg
File:36 Vikingo.svg
File:115 Nano.svg
File:Dwarf Fortress Icon.svg
File:BulbIcon.svg
File:Microsoft_Tips_icon.png
File:Eucalyp-Deus_WikiDwarf_(black).png
File:Gimli_son_of_Gloin_by_Perrie_Nicholas_Smith.jpg
</gallery>

----

{{TipBox2|float=right|titlebg=#0a0|Conserving Resources|Some things absolutely require wood (like beds and charcoal), but others can be made out of more common materials like stone. For this reason it's best, especially in the beginning, to make everything that you can out of stone. For example, you could make wood chests and barrels, but stone coffers and rock pots would let you save wood for things that require it and help you rid yourself of all that stone. And if you decide you want solid gold chests or something later when you have more resources, you can always throw out the rock coffers.}}

<div style="float:right; clear:both; width: 35%; background-color: #f9f9fb; border: 1px solid #cdcdcd; border-radius: 0.25rem; box-shadow: 0 1px 2px rgba(43,42,51,.05); margin: 2rem 0; padding: 1rem;">
<div style="font-size: 1.424rem;>Conserving Resources</div>
Some things absolutely require wood (like beds and charcoal), but others can be made out of more common materials like stone. For this reason it's best, especially in the beginning, to make everything that you can out of stone. For example, you could make wood chests and barrels, but stone coffers and rock pots would let you save wood for things that require it and help you rid yourself of all that stone. And if you decide you want solid gold chests or something later when you have more resources, you can always throw out the rock coffers.
</div>

<div style="float:right; clear:both; width: 35%; background-color: #f9f9fb; border: 1px solid #cdcdcd; border-left: 5px solid #3c763d; border-radius: 0.25rem; box-shadow: 0 1px 2px rgba(43,42,51,.05); margin: 2rem 0; padding: 1rem;">
<div style="font-size: 1.424rem;>Conserving Resources</div>
Some things absolutely require wood (like beds and charcoal), but others can be made out of more common materials like stone. For this reason it's best, especially in the beginning, to make everything that you can out of stone. For example, you could make wood chests and barrels, but stone coffers and rock pots would let you save wood for things that require it and help you rid yourself of all that stone. And if you decide you want solid gold chests or something later when you have more resources, you can always throw out the rock coffers.
</div>

<div style="float:right; clear:both; width: 35%; background-color: #f9f8f5; border: 1px solid #cdcdcd; border-left: 5px solid #cdcdcd; border-radius: 0.25rem; box-shadow: 0 1px 2px rgba(43,42,51,.05); margin: 2rem 0; padding: 1rem;">
<div style="font-size: 1.424rem;>Conserving Resources</div>
Some things absolutely require wood (like beds and charcoal), but others can be made out of more common materials like stone. For this reason it's best, especially in the beginning, to make everything that you can out of stone. For example, you could make wood chests and barrels, but stone coffers and rock pots would let you save wood for things that require it and help you rid yourself of all that stone. And if you decide you want solid gold chests or something later when you have more resources, you can always throw out the rock coffers.
</div>

<div style="float:right; clear:both; width: 35%; background-color: #fcf8e3; border: 1px solid #cdcdcd; border-left: 5px solid #aa6708; border-radius: 0.25rem; box-shadow: 0 1px 2px rgba(43,42,51,.05); margin: 2rem 0; padding: 1rem;">
<div style="position:abolute; margin-top: -50px;">[[File:Dwarf Fortress Icon.svg|right|link=]]</div>
<div style="font-size: 1.424rem;>Conserving Resources</div>

Some things absolutely require wood (like beds and charcoal), but others can be made out of more common materials like stone. For this reason it's best, especially in the beginning, to make everything that you can out of stone. For example, you could make wood chests and barrels, but stone coffers and rock pots would let you save wood for things that require it and help you rid yourself of all that stone. And if you decide you want solid gold chests or something later when you have more resources, you can always throw out the rock coffers.
</div>

{{Clear}}
----

{| style="border: none;padding:8px; border-top:1px solid #dddddd;|{{prettytable}} style="border: none;padding:8px; width:auto;"
|- style='background-color:#ddd; border: none;padding:8px;'
! style="border: none;padding:8px; border-top:1px solid #dddddd; width:20%;"|Token
! style="border: none;padding:8px; border-top:1px solid #dddddd; width:20%;"|Arguments
! style="border: none;padding:8px; border-top:1px solid #dddddd;"|Description

|- style=''
| style="border: none;padding:8px; border-top:1px solid #dddddd;|{{text anchor|NAME}}
| style="border: none;padding:8px; border-top:1px solid #dddddd;|
*name
| style="border: none;padding:8px; border-top:1px solid #dddddd;|The singular form of the plant's name as seen in-game.
|- style='background-color:#f5f5f5;'
| style="border: none;padding:8px; border-top:1px solid #dddddd;|{{text anchor|NAME_PLURAL}}
| style="border: none;padding:8px; border-top:1px solid #dddddd;|
*name
| style="border: none;padding:8px; border-top:1px solid #dddddd;|The plural form of the plant's name as seen in-game.

|- style=''
| style="border: none;padding:8px; border-top:1px solid #dddddd;|{{text anchor|ADJ}}
| style="border: none;padding:8px; border-top:1px solid #dddddd;|
*adjective
| style="border: none;padding:8px; border-top:1px solid #dddddd;|The word or phrase used to describe items made from this plant.

|- style='padding:8px !important; background-color:#f5f5f5'
| style="border: none;padding:8px; border-top:1px solid #dddddd;|{{text anchor|ALL_NAMES}}
| style="border: none;padding:8px; border-top:1px solid #dddddd;|
*name
| style="border: none;padding:8px; border-top:1px solid #dddddd;|Sets the NAME, NAME_PLURAL, and ADJ to the specified string.

|- style=''
| style="border: none;padding:8px; border-top:1px solid #dddddd;|{{text anchor|PREFSTRING}}
| style="border: none;padding:8px; border-top:1px solid #dddddd;|
*reason
| style="border: none;padding:8px; border-top:1px solid #dddddd;|What dwarves can like this object for (e.g. "Urist likes plump helmets for their rounded tops.")

|- style='padding:8px !important;background-color:#f5f5f5'
| style="border: none;padding:8px; border-top:1px solid #dddddd;|{{text anchor|MATERIAL}}
| style="border: none;padding:8px; border-top:1px solid #dddddd;|
*material_name
| style="border: none;padding:8px; border-top:1px solid #dddddd;|Starts defining a new local plant material with the given name and '''no''' properties.

|- style=''
| style="border: none;padding:8px; border-top:1px solid #dddddd;|{{text anchor|USE_MATERIAL}}
| style="border: none;padding:8px; border-top:1px solid #dddddd;|
*material_name
*old_material
| style="border: none;padding:8px; border-top:1px solid #dddddd;|Starts defining a new local plant material with the given name and using the properties of another local plant material.

|- style='padding:8px !important;background-color:#f5f5f5'
| style="border: none;padding:8px; border-top:1px solid #dddddd;|{{text anchor|USE_MATERIAL_TEMPLATE}}
| style="border: none;padding:8px; border-top:1px solid #dddddd;|
*material_name
*template_name
| style="border: none;padding:8px; border-top:1px solid #dddddd;|Starts defining a new local plant material with the given name and using the properties of the specified material template.

|- style=''
| style="border: none;padding:8px; border-top:1px solid #dddddd;|{{text anchor|BASIC_MAT}}
| style="border: none;padding:8px; border-top:1px solid #dddddd;|
* [[Material token|material]]
| style="border: none;padding:8px; border-top:1px solid #dddddd;|Sets the basic material of the plant. According to Toady, you can use other materials (for instance, iron) but the game may hiccup on plants that aren't structurally plants. For crops, said material should have [STRUCTURAL_PLANT_MAT] to permit proper stockpiling. Generally, this should be "LOCAL_PLANT_MAT:material_name", using a material defined using MATERIAL, USE_MATERIAL, or USE_MATERIAL_TEMPLATE.
|}

<pre>
.wikitable,
.prettytable{
border: none !important;
width:auto;
max-width:100%;
margin-bottom:20px;
background-color:transparent;
border-spacing:0px;
}
.wikitable tr,
.prettytable tr{
border-top:1px solid #dddddd;
}
.wikitable th,.prettytable th{
border: none !important;
text-align:left;
}
.wikitable td,.wikitable th,
.prettytable td,.prettytable th{
border: none !important;
padding:0;
}
.wikitable tr > th,
.prettytable tr > th{
padding:8px !important;
line-height:1.42857143;
vertical-align:top;
border-top:1px solid #dddddd;
border-collapse:collapse;
border-spacing:0;
text-align:center;
vertical-align:middle;
}
.wikitable tr > td,
.prettytable tr > td{
padding:8px !important;
line-height:1.42857143;
vertical-align:top;
border-top:1px solid #dddddd;
border-collapse:collapse;
border-spacing:0
}
.wikitable tbody > tr:nth-child(even),
.prettytable tbody > tr:nth-child(even){
background-color:#f5f5f5
}
.wikitable tr > th.headerSort,
.prettytable tr > th.headerSort{
padding-right:21px !important
}
/*
.wikitable tr:hover{
background: #f1f1f1;
*/
}
</pre>

== Navigation ==

User Interface:
* [[Dwarf fortress mode#Gameplay user interface]] • [[Map legend]] • [[Status icon]]
* [[Controls]] • [[Controls guide]] • [[Hotkeys]] • [[Macros and keymaps]] • [[Note]]
* [[Interface‎‎]] • [[Menu]] • [[Status|Status screen]] • [[Health screen]] • [[Nobles screen]] • [[Military interface]] • [[Thoughts and preferences]]
* • • • • •

* Gameplay settings: [[announcements.txt]] • [[d_init.txt]]
* Settings: [[init.txt]] • [[Technical tricks]] • [[interface.txt]]

* [[About]] (vs [[Dwarf Fortress]] ?)
* Download & [[Installation]] • [[System requirements]]

* [[Dwarf fortress mode]] • [[Tutorials]] • [[Frequently Asked Questions]] • [[Troubleshooting]] • [[:Category:DF2014:Errors]]
* [[Adventurer mode]] • [[Adventure mode quick start]] • [[Adventure mode quick reference]]
* [[Frames per second]]

----

* [[world generation]] • [[Embark]]
:: [[Quickstart_guide#Pre-Embark]] • [[Quickstart guide/Starting site]] • [[Site finder]] • [[Starting build]]
* [[Troubleshooting]] • [[Frequently Asked Questions]]

* [[Tutorials]] • [[Quickstart guide]] • [[:Category:DF2014:Getting_started]] • [[:Category:DF2014:Quickstart guide]]
* [[:Category:Guides]]

* [[Important advice]]

* [[Design strategies]]

* [[Race]]s • [[Creature]]s
* [[Skills]]

* [[Industry]]
* [[Farming]] • [[Trading]] [[Military]]

* [[Item]]s • [[Materials]] ( [[Material science]] • [[:Category:DF2014:Material properties]] )
* [[Armor]] • [[Weapons]]

* [[Building]] [[Workshop]] [[Furnace]]

----

* [[Biome]] • [[Surroundings]] • [[Climate]] • [[Weather]]
* [[Civilization]] • [[Site]]s •
* [[Nobles]] • [[Holding]]s •

* [[Calendar]]

----
* [[Dwarf Fortress]] [[Reception of Dwarf Fortress]] [[Community of Dwarf Fortress]] [[Legacy of Dwarf Fortress]]
* Development: [[DF2014:Release information|Release information]] • [[Dwarf Fortress Talk|Developer diaries]] • [[Dwarf Fortress Development|Roadmap]]

* [[Challenge]]: [[Playstyle challenge]] [[Megaproject]] [[Stupid dwarf trick]]
* [[:Category:Humor_and_stories]]

* [[!!SCIENCE!!]]
----

[[Modding]]:
* Documentation: [[Token]]s • [[Raw file]] • [[Reactions]] • [[syndrome]]
* [[Speech file]] • [[Dipscript]]

* [[Graphics]]: [[Tilesets]] • [[Graphic set]] • [[Color]] • [[Color scheme]] • [[Character table]]

Development:
* [[DF2014:Release information|Release information]] • [[Dwarf Fortress Talk|Developer diaries]] • [[Dwarf Fortress Development|Roadmap]]

Tools & Utilities
* [[Utilities#Modding tools]]

[[:Category:DF2014:Files|Game Files]]:
* Gameplay settings: [[announcements.txt]] • [[d_init.txt]]
* Settings: [[colors.txt]] • [[init.txt]] • [[interface.txt]]
* Log files: [[errorlog.txt]] • [[gamelog.txt]]
* [[Saved game folder]] 

----
{{Modding navbox|state=collapsed}}

* [[Interaction token|Interaction]] • [[Material token|Material]] • [[Inorganic material definition token|Inorganic material definition]] • [[Plant token|Plant]] •

--

Misc Mechanics:
* [[stress]] [[Thought]] [[Emotion]] [[personalities]] [[Preferences]]
* [[Gait]] • [[Genetics]] • [[Size]] • [[Personality trait]] • [[Attribute]] •

* [[:Category:DF2014:Material_properties]] - [[Material science]]
:* Defined: [[Item value#Material multipliers|Value]] • [[Color#Material_By_Color|Color]] • [[Density]] • [[Strain at yield]] • [[Temperature#Material values|Temperature values]]
:* Derived: [[Magma-safe|Magma safety]] • [[Fire-safe|Fire safety]]
:* Fluids: [[Depth]] • [[Flow]] • [[Pressure]]

* [[:Category:DF2014:Modding Examples]]: [[Interaction examples]] • [[Reaction examples]] • [[Creature examples]]

* [[Text viewer]](?)
* [[World token|World]] • [[Biome token|Biome]] •
* [[Syndrome token|Syndrome]] •

token nonsense testing style options
{{Navbox
| name = name1A
| title = [[Modding]] 1A
| state = no

| group1 = Documentation
| list1 = [[Raw file]] • [[Token]]s • [[Reactions]] • [[syndrome]] • [[Speech file]] • [[Dipscript]]

| group2 = [[Graphics]]
| list2 = [[Tilesets]] • [[Graphic set]] • [[Color]] • [[Color scheme]] • [[Character table]]

| below = [[Modding#Guide]] • [[Utilities#Modding tools]] • [[List of mods]] • [[Graphics set repository]] • [[:Category:DF2014:Files|Game Files]]
}}
{{Navbox
| name = name1B
| title = [[Token]]s 1B
| state = no

| group1 = General
| list1 = [[Biome token|Biome]] • [[Creature token|Creature]] • [[Entity token|Entity]] • [[Interaction token|Interaction]] • [[Material token|Material]] • [[Inorganic material definition token|Inorganic material definition]] • [[Plant token|Plant]] • [[Skill token|Skill]] • [[Syndrome token|Syndrome]] • [[World token|World]]

| group2 = Color
| list2 = [[Descriptor color token|Descriptor color]] • [[Descriptor pattern token|Descriptor pattern]] • [[Descriptor shape token|Descriptor shape]]

| group3 = [[Creature token|Creature]]
| list3 = [[Body token|Body]] • [[Body detail plan token|Body detail plan]] • [[Bodygloss]] • [[Creature variation token|Creature variation]] • [[Creature mannerism token|Creature mannerism]] • [[Creature texture token|Creature texture]] • [[Material definition token|Material definition]] • [[Tissue definition token|Tissue definition]] • [[Personality trait]]

| group4 = [[Entity token|Entity]]
| list4 = [[Position token|Position]] • [[Unit type token|Unit type]] • [[Language token|Language]] • [[Building token|Building]] • [[Ethic]]

| group5 = [[Item definition token|Item definition]]
| list5 = [[Ammo token|Ammo]] • [[Armor token|Armor]] • [[Instrument token|Instrument]] • [[Tool token|Tool]] • [[Trap component token|Trap component]] • [[Weapon token|Weapon]] • [[Item definition token|Other]]

| group6 = [[Reactions]]
| list6 = [[Item token|Item]] • [[Labor token|Labor]] • [[Skill token|Skill]]

}}

{{Navbox
| name = name2
| title = [[Modding]] 2
| state = no

| group1 = Documentation
| list1 = [[Token]]s • [[Raw file]] • [[Reactions]] • [[syndrome]] • [[Speech file]] • [[Dipscript]]

| group2 = [[Graphics]]
| list2 = [[Tilesets]] • [[Graphic set]] • [[Color]] • [[Color scheme]] • [[Character table]]

| group3 = [[Token]]s
| list3 = [[Ammo token|Ammo]] • [[Armor token|Armor]] • [[Biome token|Biome]] • [[Building token|Building]] • [[Body token|Body]] • [[Body detail plan token|Body detail plan]] • [[Bodygloss]] • [[Creature token|Creature]] • [[Creature mannerism token|Creature mannerism]] • [[Creature texture token|Creature texture]] • [[Creature variation token|Creature variation]] • [[Descriptor color token|Descriptor color]] • [[Descriptor pattern token|Descriptor pattern]] • [[Descriptor shape token|Descriptor shape]] • [[Entity token|Entity]] • [[Item token|Item]] • [[Item definition token|Item definition]] • [[Instrument token|Instrument]] • [[Interaction token|Interaction]] • [[Labor token|Labor]] • [[Language token|Language]] • [[Material token|Material]] • [[Material definition token|Material definition]] • [[Inorganic material definition token|Inorganic material definition]] • [[Personality trait]] • [[Plant token|Plant]] • [[Position token|Position]] • [[Skill token|Skill]] • [[Syndrome token|Syndrome]] • [[Tissue definition token|Tissue definition]] • [[Tool token|Tool]] • [[Trap component token|Trap component]] • [[Unit type token|Unit type]] • [[Weapon token|Weapon]] • [[World token|World]]

| below = [[Modding#Guide]] • [[Utilities#Modding tools]] • [[List of mods]] • [[Graphics set repository]] • [[:Category:DF2014:Files|Game Files]]
}}

{{Navbox
| name = name3A
| title = [[Modding]] 3A
| state = no
| bodystyle = width:100%;

| group1 = Documentation
| list1 = [[Token]]s • [[Raw file]] • [[Reactions]] • [[syndrome]] • [[Speech file]] • [[Dipscript]]

| group2 = [[Graphics]]
| list2 = [[Tilesets]] • [[Graphic set]] • [[Color]] • [[Color scheme]] • [[Character table]]

| group3 = [[Token]]s
| list3 = [[Ammo token|Ammo]] • [[Armor token|Armor]] • [[Biome token|Biome]] • [[Building token|Building]] • [[Body token|Body]] • [[Body detail plan token|Body detail plan]] • [[Bodygloss]] • [[Creature token|Creature]] • [[Creature mannerism token|Creature mannerism]] • [[Creature texture token|Creature texture]] • [[Creature variation token|Creature variation]] • [[Descriptor color token|Descriptor color]] • [[Descriptor pattern token|Descriptor pattern]] • [[Descriptor shape token|Descriptor shape]] • [[Entity token|Entity]] • [[Item token|Item]] • [[Item definition token|Item definition]] • [[Instrument token|Instrument]] • [[Interaction token|Interaction]] • [[Labor token|Labor]] • [[Language token|Language]] • [[Material token|Material]] • [[Material definition token|Material definition]] • [[Inorganic material definition token|Inorganic material definition]] • [[Personality trait]] • [[Plant token|Plant]] • [[Position token|Position]] • [[Skill token|Skill]] • [[Syndrome token|Syndrome]] • [[Tissue definition token|Tissue definition]] • [[Tool token|Tool]] • [[Trap component token|Trap component]] • [[Unit type token|Unit type]] • [[Weapon token|Weapon]] • [[World token|World]]

| below = [[Modding guide]] • [[Utilities#Modding tools]] • [[List of mods]] • [[Graphics set repository]] • [[:Category:DF2014:Files|Game Files]]
}}
{{Navbox
| name = name3B
| title = [[Modding]] 3B large list double space
| state = no
| bodystyle = width:100%;

| group1 = Documentation
| list1 = [[Token]]s • [[Raw file]] • [[Reactions]] • [[syndrome]] • [[Speech file]] • [[Dipscript]]

| group2 = [[Graphics]]
| list2 = [[Tilesets]] • [[Graphic set]] • [[Color]] • [[Color scheme]] • [[Character table]]

| group3 = [[Token]]s
| list3 = [[Ammo token|Ammo]]{{*}}[[Armor token|Armor]]{{*}}[[Biome token|Biome]]{{*}}[[Building token|Building]]{{*}}[[Body token|Body]]{{*}}[[Body detail plan token|Body detail plan]]{{*}}[[Bodygloss]]{{*}}[[Creature token|Creature]]{{*}}[[Creature mannerism token|Creature mannerism]]{{*}}[[Creature texture token|Creature texture]]{{*}}[[Creature variation token|Creature variation]]{{*}}[[Descriptor color token|Descriptor color]]{{*}}[[Descriptor pattern token|Descriptor pattern]]{{*}}[[Descriptor shape token|Descriptor shape]]{{*}}[[Entity token|Entity]]{{*}}[[Item token|Item]]{{*}}[[Item definition token|Item definition]]{{*}}[[Instrument token|Instrument]]{{*}}[[Interaction token|Interaction]]{{*}}[[Labor token|Labor]]{{*}}[[Language token|Language]]{{*}}[[Material token|Material]]{{*}}[[Material definition token|Material definition]]{{*}}[[Inorganic material definition token|Inorganic material definition]]{{*}}[[Personality trait]]{{*}}[[Plant token|Plant]]{{*}}[[Position token|Position]]{{*}}[[Skill token|Skill]]{{*}}[[Syndrome token|Syndrome]]{{*}}[[Tissue definition token|Tissue definition]]{{*}}[[Tool token|Tool]]{{*}}[[Trap component token|Trap component]]{{*}}[[Unit type token|Unit type]]{{*}}[[Weapon token|Weapon]]{{*}}[[World token|World]]

| below = [[Modding guide]] • [[Utilities#Modding tools]] • [[List of mods]] • [[Graphics set repository]] • [[:Category:DF2014:Files|Game Files]]
}}
{{Navbox
| name = name5
| title = [[Modding]] 5 large list grouping instead of sub groups - automatic with hlist
| state = no
| bodystyle = width:100%;

| group1 = Documentation
| list1 = [[Token]]s • [[Raw file]] • [[Reactions]] • [[syndrome]] • [[Speech file]] • [[Dipscript]]

| group2 = [[Graphics]]
| list2 = [[Tilesets]] • [[Graphic set]] • [[Color]] • [[Color scheme]] • [[Character table]]

| group3 = [[Token]]s
| list3 = [[Biome token|Biome]] • [[Creature token|Creature]]'''('''[[Body token|Body]] • [[Body detail plan token|Body detail plan]] • [[Bodygloss]] • [[Creature variation token|Creature variation]] • [[Creature mannerism token|Creature mannerism]] • [[Creature texture token|Creature texture]] • [[Material definition token|Material definition]] • [[Tissue definition token|Tissue definition]] • [[Personality trait]]''')''' •
Color'''('''[[Descriptor color token|Descriptor color]] • [[Descriptor pattern token|Descriptor pattern]] • [[Descriptor shape token|Descriptor shape]]''')''' • [[Entity token|Entity]]'''('''[[Position token|Position]] • [[Unit type token|Unit type]] • [[Language token|Language]] • [[Building token|Building]] • [[Ethic]]''')''' • [[Item definition token|Item definition]]'''('''[[Ammo token|Ammo]] • [[Armor token|Armor]] • [[Instrument token|Instrument]] • [[Tool token|Tool]] • [[Trap component token|Trap component]] • [[Weapon token|Weapon]] • [[Item definition token|Other]]''')''' • [[Interaction token|Interaction]] • [[Material token|Material]] • [[Inorganic material definition token|Inorganic material definition]] • [[Plant token|Plant]] • [[Reactions]]'''('''[[Item token|Item]] • [[Labor token|Labor]] • [[Skill token|Skill]]''')''' • [[Syndrome token|Syndrome]] • [[World token|World]]

| below = [[Modding guide]] • [[Utilities#Modding tools]] • [[List of mods]] • [[Graphics set repository]] • [[:Category:DF2014:Files|Game Files]]
}}
{{Navbox
| name = name5A
| title = [[Modding]] 5A - grouping, double space
| state = no
| bodystyle = width:100%;

| group1 = Documentation
| list1 = [[Token]]s • [[Raw file]] • [[Reactions]] • [[syndrome]] • [[Speech file]] • [[Dipscript]]

| group2 = [[Graphics]]
| list2 = [[Tilesets]] • [[Graphic set]] • [[Color]] • [[Color scheme]] • [[Character table]]

| group3 = [[Token]]s
| list3 = [[Biome token|Biome]]{{*}} [[Creature token|Creature]]([[Body token|Body]]{{*}}[[Body detail plan token|Body detail plan]]{{*}}[[Bodygloss]]{{*}}[[Creature variation token|Creature variation]]{{*}}[[Creature mannerism token|Creature mannerism]]{{*}}[[Creature texture token|Creature texture]]{{*}}[[Material definition token|Material definition]]{{*}}[[Tissue definition token|Tissue definition]]{{*}}[[Personality trait]]) {{*}} Color([[Descriptor color token|Descriptor color]]{{*}}[[Descriptor pattern token|Descriptor pattern]]{{*}}[[Descriptor shape token|Descriptor shape]]) {{*}} [[Entity token|Entity]]([[Position token|Position]]{{*}}[[Unit type token|Unit type]]{{*}}[[Language token|Language]]{{*}}[[Building token|Building]]{{*}}[[Ethic]]) {{*}} [[Item definition token|Item definition]]([[Ammo token|Ammo]]{{*}}[[Armor token|Armor]]{{*}}[[Instrument token|Instrument]]{{*}}[[Tool token|Tool]]{{*}}[[Trap component token|Trap component]]{{*}}[[Weapon token|Weapon]]{{*}}[[Item definition token|Other]]) {{*}}[[Interaction token|Interaction]]{{*}}[[Material token|Material]]{{*}}[[Inorganic material definition token|Inorganic material definition]]{{*}}[[Plant token|Plant]]{{*}} [[Reactions]]([[Item token|Item]]{{*}}[[Labor token|Labor]]{{*}}[[Skill token|Skill]]) {{*}}[[Syndrome token|Syndrome]]{{*}}[[World token|World]]

| below = [[Modding guide]] • [[Utilities#Modding tools]] • [[List of mods]] • [[Graphics set repository]] • [[:Category:DF2014:Files|Game Files]]
}}
{{Navbox
| name = name5B
| title = [[Modding]] 5B grouping bold, double space
| state = no
| bodystyle = width:100%;

| group1 = Documentation
| list1 = [[Token]]s • [[Raw file]] • [[Reactions]] • [[syndrome]] • [[Speech file]] • [[Dipscript]]

| group2 = [[Graphics]]
| list2 = [[Tilesets]] • [[Graphic set]] • [[Color]] • [[Color scheme]] • [[Character table]]

| group3 = [[Token]]s
| list3 = [[Biome token|Biome]]{{*}}'''[[Creature token|Creature]]'''([[Body token|Body]]{{*}}[[Body detail plan token|Body detail plan]]{{*}}[[Bodygloss]]{{*}}[[Creature variation token|Creature variation]]{{*}}[[Creature mannerism token|Creature mannerism]]{{*}}[[Creature texture token|Creature texture]]{{*}}[[Material definition token|Material definition]]{{*}}[[Tissue definition token|Tissue definition]]{{*}}[[Personality trait]]){{*}}'''Color'''([[Descriptor color token|Descriptor color]]{{*}}[[Descriptor pattern token|Descriptor pattern]]{{*}}[[Descriptor shape token|Descriptor shape]]){{*}}'''[[Entity token|Entity]]'''([[Position token|Position]]{{*}}[[Unit type token|Unit type]]{{*}}[[Language token|Language]]{{*}}[[Building token|Building]]{{*}}[[Ethic]]){{*}}'''[[Item definition token|Item definition]]'''([[Ammo token|Ammo]]{{*}}[[Armor token|Armor]]{{*}}[[Instrument token|Instrument]]{{*}}[[Tool token|Tool]]{{*}}[[Trap component token|Trap component]]{{*}}[[Weapon token|Weapon]]{{*}}[[Item definition token|Other]]){{*}}[[Interaction token|Interaction]]{{*}}[[Material token|Material]]{{*}}[[Inorganic material definition token|Inorganic material definition]]{{*}}[[Plant token|Plant]]{{*}}'''[[Reactions]]'''([[Item token|Item]]{{*}}[[Labor token|Labor]]{{*}}[[Skill token|Skill]]){{*}}[[Syndrome token|Syndrome]]{{*}}[[World token|World]]

| below = [[Modding guide]] • [[Utilities#Modding tools]] • [[List of mods]] • [[Graphics set repository]] • [[:Category:DF2014:Files|Game Files]]
}}
{{Navbox
| name = name5c
| title = [[Modding]] 5c grouping highilghted otherwise, double space
| state = no
| bodystyle = width:100%;

| group1 = Documentation
| list1 = [[Token]]s • [[Raw file]] • [[Reactions]] • [[syndrome]] • [[Speech file]] • [[Dipscript]]

| group2 = [[Graphics]]
| list2 = [[Tilesets]] • [[Graphic set]] • [[Color]] • [[Color scheme]] • [[Character table]]

| group3 = [[Token]]s
| list3 = [[Biome token|Biome]]{{*}}[[Creature token|Creature]]([[Body token|Body]]{{*}}[[Body detail plan token|Body detail plan]]{{*}}[[Bodygloss]]{{*}}[[Creature variation token|Creature variation]]{{*}}[[Creature mannerism token|Creature mannerism]]{{*}}[[Creature texture token|Creature texture]]{{*}}[[Material definition token|Material definition]]{{*}}[[Tissue definition token|Tissue definition]]{{*}}[[Personality trait]]){{*}}Color([[Descriptor color token|Descriptor color]]{{*}}[[Descriptor pattern token|Descriptor pattern]]{{*}}[[Descriptor shape token|Descriptor shape]]){{*}}[[Entity token|Entity]]([[Position token|Position]]{{*}}[[Unit type token|Unit type]]{{*}}[[Language token|Language]]{{*}}[[Building token|Building]]{{*}}[[Ethic]]){{*}}[[Item definition token|Item definition]]([[Ammo token|Ammo]]{{*}}[[Armor token|Armor]]{{*}}[[Instrument token|Instrument]]{{*}}[[Tool token|Tool]]{{*}}[[Trap component token|Trap component]]{{*}}[[Weapon token|Weapon]]{{*}}[[Item definition token|Other]]){{*}}[[Interaction token|Interaction]]{{*}}[[Material token|Material]]{{*}}[[Inorganic material definition token|Inorganic material definition]]{{*}}[[Plant token|Plant]]{{*}}[[Reactions]]([[Item token|Item]]{{*}}[[Labor token|Labor]]{{*}}[[Skill token|Skill]]){{*}}[[Syndrome token|Syndrome]]{{*}}[[World token|World]]

| below = [[Modding guide]] • [[Utilities#Modding tools]] • [[List of mods]] • [[Graphics set repository]] • [[:Category:DF2014:Files|Game Files]]
}}

=== Reference ===
{{Template:DF2014 buildings}}
{{Template:DF2014 creatures}}
{{Template:DF2014 diamonds}}
{{Template:DF2014 files}}
{{Template:DF2014 gems}}
{{Template:DF2014 labors}}
{{Template:DF2014 materials}}
{{Template:DF2014 metals}}
{{Template:DF2014 military}}
{{Template:DF2014 nobles}}
{{Template:DF2014 plants}}
{{Template:DF2014 rooms}}
{{Template:DF2014 skills}}
{{Template:DF2014 soil}}
{{Template:DF2014 stones}}
{{Template:DF2014 vermin}}
{{Template:DF2014 weapons}}
{{Template:DF2014 workshops}}
{{Template:DF2014 world}}

= Other Misc curiosities=
{{t|Columns-list}} - [https://en.wikipedia.org/wiki/Template:Div_col/styles.css css "fix"] for the annoying margin glitch that skews columns sometimes.

== Download links ==
Bay12Forum
GitHubSomething

Bay12Download
DFFDDownload
SteamDownload

{{{1|Button text}}}
Get Started Tutorial
== Files ==
Maybe merge many of the file articles stubs, and create an entry which documents all DF important files and folders.

[[File:Folder-orange.svg|20px|link=]] Dwarf Fortress
 &emsp;[[File:Folder.svg|20px|link=]] data
 &emsp;&emsp;[[File:Folder.svg|20px|link=]] art
 &emsp;&emsp;[[File:Folder.svg|20px|link=]] init
 &emsp;&emsp;[[File:Folder.svg|20px|link=]] save
 &emsp;&emsp;[[File:Folder.svg|20px|link=]] sound
 &emsp;[[File:Folder.svg|20px|link=]] raw
 &emsp;&emsp;[[File:Folder.svg|20px|link=]] graphics
 &emsp;&emsp;[[File:Folder.svg|20px|link=]] objects

[[File:Folder-orange.svg|20px|link=]] Dwarf Fortress
 &emsp;[[File:Folder.svg|20px|link=]] data
 &emsp;&emsp;[[File:Folder.svg|20px|link=]] init
 &emsp;&emsp;&emsp;[[File:Text-x-generic.svg|20px|link=]][[announcements.txt]]
 &emsp;&emsp;&emsp;[[File:Text-x-generic.svg|20px|link=]][[arena.txt]]
 &emsp;&emsp;&emsp;[[File:Text-x-generic.svg|20px|link=]][[colors.txt]]
 &emsp;&emsp;&emsp;[[File:Text-x-generic.svg|20px|link=]][[d init.txt]]
 &emsp;&emsp;&emsp;[[File:Text-x-generic.svg|20px|link=]][[embark profiles.txt]]
 &emsp;&emsp;&emsp;[[File:Text-x-generic.svg|20px|link=]][[init.txt]]
 &emsp;&emsp;&emsp;[[File:Text-x-generic.svg|20px|link=]][[interface.txt]]
 &emsp;&emsp;&emsp;[[File:Text-x-generic.svg|20px|link=]][[macros]]
 &emsp;&emsp;&emsp;[[File:Text-x-generic.svg|20px|link=]][[world gen.txt]]
 &emsp;[[File:Text-x-generic.svg|20px|link=]][[gamelog.txt]]
 &emsp;[[File:Text-x-generic.svg|20px|link=]][[errorlog.txt]]

[[File:Folder-orange.svg|20px|link=]]Dwarf Fortress \ [[File:Folder.svg|20px|link=]]data \ [[File:Folder.svg|20px|link=]]init
{| cellspacing="5" style="padding-left: 5px;"
| [[File:Text-x-generic.svg|20px|link=]] [[announcements.txt]]
| used to control the types of [[announcement]]s displayed in-game
|- style="border: 1px solid black;"
| [[File:Text-x-generic.svg|20px|link=]] [[arena.txt]]
|-
| [[File:Text-x-generic.svg|20px|link=]] [[colors.txt]]
| defines the [[color scheme]]
|-
| [[File:Text-x-generic.svg|20px|link=]] [[d init.txt]]
| contains settings that affect game features such as saving and population controls. Further detail [[Technical tricks|here]].
|-
| [[File:Text-x-generic.svg|20px|link=]] [[embark profiles.txt]]
|
|-
| [[File:Text-x-generic.svg|20px|link=]] [[init.txt]]
| contains mostly the settings pertaining to the window, rendering and sound of Dwarf Fortress. Further detail [[Technical tricks|here]].
|-
| [[File:Text-x-generic.svg|20px|link=]] [[interface.txt]]
| Manually edit Key bindings
|-
| [[File:Text-x-generic.svg|20px|link=]] [[macros]]
|
|-
| [[File:Text-x-generic.svg|20px|link=]] [[world gen.txt]]
|
|}

== Modding notes ==

* Token is catch all name for everything inside brackets
* Token pages
** Most document how to define new objects of that type.
** Some document how to reference objects and list their default parameters e.g. [[Material_token]] and [[Item_token]]
** Article naming is inconsistent
** Some Token objects aren't covered or aren't tagged as such e.g. [[Caste]].
* Documentation
** Our syntax is sometimes unclear to the uninitiated e.g. [[Creature token]] wth is caste TYPE how it differs from creature type of special?
** Our syntax is sometimes inconsistent.
** Some object names seems inconsistent as far as I understand their use here.
<pre>
[OBJECT:CREATURE]
[CREATURE:<identifier>]

Don't match
[OBJECT:DESCRIPTOR_COLOR] - match article name, never used
[COLOR:<identifier>] - what is used everwhere that I seen.
[OBJECT:DESCRIPTOR_PATTERN]
[COLOR_PATTERN:<identifier>]
[OBJECT:DESCRIPTOR_SHAPE]
[SHAPE:<identifier>]
</pre>

User:Jan/sandbox

2023-01-06T03:22:47Z

Jan: /* In game */

__TOC__

== Misc variants ==

{| style="padding: 0.5em 0.5em 0 0.5em; margin: 0.5rem 0; background: #dff0d8; border: 2px solid #afbdaa;"
| This article is about the current version of DF.
|-
|<div style="position: relative">
<div class="mw-collapsible" id="mw-customcollapsible-version-toggle">[[File:Eo circle green white caret-double-down.svg|10px|link=]] More...</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-version-toggle">[[File:Eo circle green white caret-double-down.svg|10px|link=]] Collapsebla bla bla bla bla</div></div>
|}

[[:Release information|v50.05 ▼]] This article is about the current version of DF.
<div style="z-index: 101; position: absolute; background-color: #f8f9fa; color: #202122;">
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-111" style="padding:0.5em 1em; border: 1px solid #a2a9b1;">[[DF2014:{{PAGENAME}}|v0.47]] [[v0.34:{{PAGENAME}}|v0.34]] [[v0.31:{{PAGENAME}}|v0.31]] [[40d:{{PAGENAME}}|v0.28]] [[23a:{{PAGENAME}}|v0.23]]</div></div>

<div class="" style="padding: 0.8em 1em; margin: 0.5rem 0; border-width: 0; background-color: #E7F2F8; border-radius: 4px; font-size: 84%; line-height: 1.2em;">
This article is about the current version of DF ( v{{current/version}} | [[DF2014:{{PAGENAME}}|v0.47.05]] | [[v0.34:{{PAGENAME}}|v0.34]] | [[v0.31:{{PAGENAME}}|v0.31]] | [[40d:{{PAGENAME}}|v0.28]] | [[23a:{{PAGENAME}}|v0.23]] )
</div>

== In game==

<div style="width:100px; padding:5px; background-color: #187c36; border: 2px outset #22b14c; color:white; {{border-radius|3px}}">Start</div >
<div style="width:100px; padding:5px; background-color: #4b4b4b; border: 2px outset #786c80; color:white; {{border-radius|3px}}">Quit</div >
<div style="width:100px; padding:5px; background-color: #a40d14; border: 2px outset #ed1c24; color:white; {{border-radius|3px}}">Delete</div >

=== build shortkeys ===

:[[file:ui_b.png]]{{key|b}}Build
::[[file:ui_bo.png]]{{key|o}}Workshops
:::[[file:ui_bol.png]]{{key|l}}Clothing and Leather
::::[[file:ui_boll.png]]{{key|l}}Leather
::::[[file:ui_bolo.png]]{{key|o}}Loom
::::[[file:ui_bolk.png]]{{key|k}}Clothes
::::[[file:ui_boly.png]]{{key|y}}Dyer
:::[[file:ui_bof.png]]{{key|f}}Farming
::::[[file:ui_bofp.png]]{{key|p}}Farm plot
::::[[file:ui_bofl.png]]{{key|l}}Still
::::[[file:ui_bofb.png]]{{key|b}}
::::[[file:ui_boft.png]]{{key|t}}
::::[[file:ui_bofy.png]]{{key|y}}
::::[[file:ui_bofk.png]]{{key|k}}
::::[[file:ui_boff.png]]{{key|f}}
::::[[file:ui_bofq.png]]{{key|q}}
::::[[file:ui_bofv.png]]{{key|v}}
::::[[file:ui_bofn.png]]{{key|n}}
::::[[file:ui_bofh.png]]{{key|h}}
:::[[file:ui_bou.png]]{{key|u}}Furnaces
::::[[file:ui_boug.png]]{{key|g}}Glass Furnace
::::[[file:ui_bouk.png]]{{key|k}}Klin
::::[[file:ui_bouG.png]]{{key|G}}Magma glass Furnace
::::[[file:ui_bouK.png]]{{key|K}}
::::[[file:ui_bouL.png]]{{key|L}}
::::[[file:ui_boul.png]]{{key|l}}
::::[[file:ui_bouf.png]]{{key|f}}
:::[[file:ui_boy.png]]{{key|y}}
:::[[file:ui_bob.png]]{{key|b}}
:::[[file:ui_bop.png]]{{key|p}}
:::[[file:ui_bor.png]]{{key|r}}
:::[[file:ui_boj.png]]{{key|j}}
:::[[file:ui_boI.png]]{{key|I}}
:::[[file:ui_boh.png]]{{key|h}}
:::[[file:ui_boi.png]]{{key|i}}
:::[[file:ui_boR.png]]{{key|R}}
:::[[file:ui_bog.png]]{{key|g}}
:::[[file:ui_boP.png]]{{key|P}}
:::[[file:ui_bot.png]]{{key|t}}
::[[file:ui_bf.png]]{{key|f}}Furniture
:::[[file:ui_bfb.png]]{{key|b}}Bed
:::[[file:ui_bfr.png]]{{key|r}}Chair
:::[[file:ui_bft.png]]{{key|t}}
:::[[file:ui_bfh.png]]{{key|h}}
:::[[file:ui_bfn.png]]{{key|n}}
:::[[file:ui_bfx.png]]{{key|x}}
:::[[file:ui_bfl.png]]{{key|l}}
:::[[file:ui_bfu.png]]{{key|u}}
:::[[file:ui_bfT.png]]{{key|T}}
:::[[file:ui_bfo.png]]{{key|o}}
:::[[file:ui_bfy.png]]{{key|y}}
:::[[file:ui_bfp.png]]{{key|p}}
:::[[file:ui_bfi.png]]{{key|i}}
::[[file:ui_bp.png]]{{key|p}}Doors/Hatches
:::[[file:ui_bpr.png]]{{key|r}}
:::[[file:ui_bph.png]]{{key|h}}
::[[file:ui_bn.png]]{{key|n}}Constructions
:::[[file:ui_bnl.png]]{{key|l}}wall
:::[[file:ui_bnf.png]]{{key|f}}
:::[[file:ui_bnr.png]]{{key|r}}
:::[[file:ui_bnt.png]]{{key|t}}
:::[[file:ui_bnb.png]]{{key|b}}
:::[[file:ui_bno.png]]{{key|o}}
:::[[file:ui_bnO.png]]{{key|O}}
:::[[file:ui_bnF.png]]{{key|F}}
:::[[file:ui_bnG.png]]{{key|G}}
:::[[file:ui_bng.png]]{{key|g}}
:::[[file:ui_bnM.png]]{{key|M}}
:::[[file:ui_bnm.png]]{{key|m}}
:::[[file:ui_bny.png]]{{key|y}}
:::[[file:ui_bnY.png]]{{key|Y}}
:::[[file:ui_bnp.png]]{{key|p}}
:::[[file:ui_bnk.png]]{{key|k}}
:::[[file:ui_bnK.png]]{{key|K}}
::[[file:ui_bm.png]]{{key|m}}Machines/Fluids
:::[[file:ui_bml.png]]{{key|l}}
:::[[file:ui_bmL.png]]{{key|L}}
:::[[file:ui_bmf.png]]{{key|f}}
:::[[file:ui_bmp.png]]{{key|p}}
:::[[file:ui_bmh.png]]{{key|h}}
:::[[file:ui_bmm.png]]{{key|m}}
:::[[file:ui_bmg.png]]{{key|g}}
:::[[file:ui_bma.png]]{{key|a}}
:::[[file:ui_bmA.png]]{{key|A}}
:::[[file:ui_bmn.png]]{{key|n}}
:::[[file:ui_bmr.png]]{{key|r}}
::[[file:ui_br.png]]{{key|r}}Cages/Restraints
:::[[file:ui_brh.png]]{{key|h}}
:::[[file:ui_brg.png]]{{key|g}}
:::[[file:ui_brt.png]]{{key|t}}
::[[file:ui_bt.png]]{{key|t}}Trap
:::[[file:ui_btp.png]]{{key|p}}
:::[[file:ui_btt.png]]{{key|t}}
:::[[file:ui_bto.png]]{{key|o}}
:::[[file:ui_btg.png]]{{key|g}}
:::[[file:ui_btu.png]]{{key|u}}
::[[file:ui_by.png]]{{key|y}}Military
:::[[file:ui_byt.png]]{{key|t}}
:::[[file:ui_byr.png]]{{key|r}}
:::[[file:ui_byn.png]]{{key|n}}
:::[[file:ui_byb.png]]{{key|b}}
:::[[file:ui_byp.png]]{{key|p}}
::[[file:ui_bT.png]]{{key|T}}Trade Depot

== Metal example ==
{|
|- valign=top
|
{{infostart|{{{name|Pig iron}}}}}
{{infocell|{{{sample|[[File:PigIron Swatch.png|256px|center|frameless]]}}}}}
{{infocell|{{Metal/picture|ingredients={{#if:{{{color3|}}}|3|{{#if:{{{color2|7:0:1}}}|2|1}}}}|color={{{color|7:0:1}}}|
tile1={{{tile1|≡}}}|color1={{{color1|0:7:1}}}|
tile2={{{tile2|≡}}}|color2={{{color2|0:7:1}}}|
tile3={{{tile3|≡}}}|color3={{{color3}}}}}}}
{{infoheader|Uses}}
{{infocell|{{{uses|
* Make [[steel]] at [[smelter]]}}}
* [[Construction]]}}{{#if:{{{ore|}}}|{{infoheader|[[Ore]]}}
{{infocell|{{{ore|}}}}}}}
{{#if:{{{recipe|}}}|{{infoheader|Recipe}}
{{infocell|{{{recipe|
* 1 [[Iron]] [[bar]]
* 1 [[Flux]] [[stone]]
* 1 [[Fuel|Coal]] [[bar]]}}}}}}}
{{infoheader|Properties}}
{{infocell|{{{properties|
* [[Material value]] 10
{{firemagmasafe|yes|yes}}
* [[Melting point]] {{ct|12106}}
* [[Boiling point]] {{ct|13968}}
* [[Ignition point]] none
* [[Solid density]] 7850
* Liquid [[density]] 6980
* [[Specific heat]] 500}}}}}
{{#ifeq:{{{wiki}}}|no||{{infocell|style=text-align:center; background-color: #eee; border-top: 1px solid #aaa|1=[[wikipedia:{{#if:{{{wiki|}}}|{{{wiki}}}|{{{name|Pig iron}}}}}|Wikipedia article]]}}|{{!-}}}}
{{infoend}}
|
{{infostart|{{{name|Pig iron}}}}}
|- style="background-color:#eaecf0;"
| {{{sample|[[File:PigIron Swatch.png|100px|center|frameless]]}}}
| {{Metal/picture|ingredients={{#if:{{{color3|}}}|3|{{#if:{{{color2|}}}|2|1}}}}|color={{{color|0:7:1}}}|
tile1={{{tile1|≡}}}|color1={{{color1|0:7:1}}}|
tile2={{{tile2|≡}}}|color2={{{color2|0:7:1}}}|
tile3={{{tile3|≡}}}|color3={{{color3}}}}}
{{infoheader|Uses}}
{{infocell|{{{uses|
* Make [[steel]] at [[smelter]]}}}
* [[Construction]]}}{{#if:{{{ore|}}}|{{infoheader|[[Ore]]}}
{{infocell|{{{ore|}}}}}}}
{{#if:{{{recipe|}}}|{{infoheader|Recipe}}
{{infocell|{{{recipe|
* 1 [[Iron]] [[bar]]
* 1 [[Flux]] [[stone]]
* 1 [[Fuel|Coal]] [[bar]]}}}}}}}
{{infoheader|Properties}}
{{infocell|{{{properties|
* [[Material value]] 10
{{firemagmasafe|yes|yes}}
* [[Melting point]] {{ct|12106}}
* [[Boiling point]] {{ct|13968}}
* [[Ignition point]] none
* [[Solid density]] 7850
* Liquid [[density]] 6980
* [[Specific heat]] 500}}}}}
{{#ifeq:{{{wiki}}}|no||{{infocell|style=text-align:center; background-color: #eee; border-top: 1px solid #aaa|1=[[wikipedia:{{#if:{{{wiki|}}}|{{{wiki}}}|{{{name|Pig iron}}}}}|Wikipedia article]]}}|{{!-}}}}
{{infoend}}
|
{{infostart|{{{name|Pig iron <div class="mw-customtoggle-infoboxtab mw-ui-button mw-ui-progressive" style="float: right;">toggle</div>}}}}}
|- style="background-color:#eaecf0;"
|{{{sample|[[File:PigIron Swatch.png|100px|center|frameless]]}}}{{Metal/picture|ingredients={{#if:{{{color3|}}}|3|{{#if:{{{color2|}}}|2|1}}}}|color={{{color|0:7:1}}}|
tile1={{{tile1|≡}}}|color1={{{color1|0:7:1}}}|
tile2={{{tile2|≡}}}|color2={{{color2|0:7:1}}}|
tile3={{{tile3|≡}}}|color3={{{color3}}}}}
{{infoheader|Uses}}
{{infocell|{{{uses|
* Make [[steel]] at [[smelter]]}}}
* [[Construction]]}}{{#if:{{{ore|}}}|{{infoheader|[[Ore]]}}
{{infocell|{{{ore|}}}}}}}
{{#if:{{{recipe|}}}|{{infoheader|Recipe}}
{{infocell|{{{recipe|
* 1 [[Iron]] [[bar]]
* 1 [[Flux]] [[stone]]
* 1 [[Fuel|Coal]] [[bar]]}}}}}}}
{{infoheader|Properties}}
{{infocell|{{{properties|
* [[Material value]] 10
{{firemagmasafe|yes|yes}}
* [[Melting point]] {{ct|12106}}
* [[Boiling point]] {{ct|13968}}
* [[Ignition point]] none
* [[Solid density]] 7850
* Liquid [[density]] 6980
* [[Specific heat]] 500}}}}}
{{#ifeq:{{{wiki}}}|no||{{infocell|style=text-align:center; background-color: #eee; border-top: 1px solid #aaa|1=[[wikipedia:{{#if:{{{wiki|}}}|{{{wiki}}}|{{{name|Pig iron}}}}}|Wikipedia article]]}}|{{!-}}}}
{{infoend}}
|
{{infostart|{{{name|Pig iron}}}}}
|- style="background-color:#eaecf0;"
|[[File:OOjs UI icon eyeClosed-progressive.svg|right|30px|link=]]{{{sample|[[File:PigIron Swatch.png|100px|center|frameless]]}}}{{Metal/picture|ingredients={{#if:{{{color3|}}}|3|{{#if:{{{color2|}}}|2|1}}}}|color={{{color|0:7:1}}}|
tile1={{{tile1|≡}}}|color1={{{color1|0:7:1}}}|
tile2={{{tile2|≡}}}|color2={{{color2|0:7:1}}}|
tile3={{{tile3|≡}}}|color3={{{color3}}}}}
{{infoheader|Uses}}
{{infocell|{{{uses|
* Make [[steel]] at [[smelter]]}}}
* [[Construction]]}}{{#if:{{{ore|}}}|{{infoheader|[[Ore]]}}
{{infocell|{{{ore|}}}}}}}
{{#if:{{{recipe|}}}|{{infoheader|Recipe}}
{{infocell|{{{recipe|
* 1 [[Iron]] [[bar]]
* 1 [[Flux]] [[stone]]
* 1 [[Fuel|Coal]] [[bar]]}}}}}}}
{{infoheader|Properties}}
{{infocell|{{{properties|
* [[Material value]] 10
{{firemagmasafe|yes|yes}}
* [[Melting point]] {{ct|12106}}
* [[Boiling point]] {{ct|13968}}
* [[Ignition point]] none
* [[Solid density]] 7850
* Liquid [[density]] 6980
* [[Specific heat]] 500}}}}}
{{#ifeq:{{{wiki}}}|no||{{infocell|style=text-align:center; background-color: #eee; border-top: 1px solid #aaa|1=[[wikipedia:{{#if:{{{wiki|}}}|{{{wiki}}}|{{{name|Pig iron}}}}}|Wikipedia article]]}}|{{!-}}}}
{{infoend}}
|
{{infostart|{{{name|Pig iron}}}}}
|- style=""
|
[[File:Toggle_grey.png|right|50px|link=]]
[[File:Toggle orange.png|right|50px|link=]]
{{{sample|[[File:PigIron Swatch.png|100px|center|frameless]]}}}{{Metal/picture|ingredients={{#if:{{{color3|}}}|3|{{#if:{{{color2|}}}|2|1}}}}|color={{{color|0:7:1}}}|
tile1={{{tile1|≡}}}|color1={{{color1|0:7:1}}}|
tile2={{{tile2|≡}}}|color2={{{color2|0:7:1}}}|
tile3={{{tile3|≡}}}|color3={{{color3}}}}}
{{infoheader|Uses}}
{{infocell|{{{uses|
* Make [[steel]] at [[smelter]]}}}
* [[Construction]]}}{{#if:{{{ore|}}}|{{infoheader|[[Ore]]}}
{{infocell|{{{ore|}}}}}}}
{{#if:{{{recipe|}}}|{{infoheader|Recipe}}
{{infocell|{{{recipe|
* 1 [[Iron]] [[bar]]
* 1 [[Flux]] [[stone]]
* 1 [[Fuel|Coal]] [[bar]]}}}}}}}
{{infoheader|Properties}}
{{infocell|{{{properties|
* [[Material value]] 10
{{firemagmasafe|yes|yes}}
* [[Melting point]] {{ct|12106}}
* [[Boiling point]] {{ct|13968}}
* [[Ignition point]] none
* [[Solid density]] 7850
* Liquid [[density]] 6980
* [[Specific heat]] 500}}}}}
{{#ifeq:{{{wiki}}}|no||{{infocell|style=text-align:center; background-color: #eee; border-top: 1px solid #aaa|1=[[wikipedia:{{#if:{{{wiki|}}}|{{{wiki}}}|{{{name|Pig iron}}}}}|Wikipedia article]]}}|{{!-}}}}
{{infoend}}
|}
== Workshop example ==

* [[:File:Carpenter's workshop.png]]
[[:Category:Picture Templates]]
* [[Template:Picture Carpenter's workshop]]
[[:Category:Floor_Plan_Templates]]
* [[Template:Floor Plan Carpenter's workshop]]

* 3x3 96px 96-118py ([[Soap maker's workshop]])
* 5x5 160px 162-177py ([[Siege workshop]]
* 1x1 32px 47py ([[Screw press]])
* 2x2
* 3x1 96px 46py ([[Water wheel]])

=== Minimal change option ===
{|
|- valign=top
|
{| style="width:200px; background-color:#eaecf0;"
|-
|rowspan=2|[[File:Carpenter's workshop.png|150px]]
|{{Template:Floor Plan Carpenter's workshop}}
|-
|{{Template:Picture Carpenter's workshop}}
|}
|
{| style="width:200px; background-color:#eaecf0;"
|-
|rowspan=2|[[File:Carpenter's workshop.png|130px|link=]]
| style="line-height: 1em;font-size: 135%;"|
{{Floor Plan|2:1|2:1|2:1|2:0|2:1|2:1|2:0|2:1|2:0}}
|-
|
{| style=" font-size: 135%; border-spacing: 0; background: black; border: 2px solid black"
|- 
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"| {{Raw Tile|"|7:0:0}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|{{=}}|6:0:0}}
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"|
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|]|0:0:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
|}
|}
|
{| style="width:200px; padding:10px; background-color:#eaecf0;"
|-
| [[File:Screw_press.png|32px|center|link=]]
| style="font-size:125%;"|{{Template:Picture Screw press}}
| {{Template:Floor Plan Screw press}}
|}
|}

=== "Tab" option without tabs ===
{|
|- valign=top
|
{| style="width:200px; background-color:#eaecf0;"
|Change view
<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">[[File:Carpenter's workshop.png]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab">{{Template:Picture Carpenter's workshop}}{{Template:Floor Plan Carpenter's workshop}}</div>
|}
|
{| style="width:200px; height:165px; background-color:#eaecf0;"
|- valign=top
|Change view
<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">
{|
|rowspan=2|[[File:Carpenter's workshop.png]]
|
{| style="border-spacing:5px;"
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab"">
{| style="width:100%;"
|rowspan=2 style="width:50%; padding:10px;"|<center>
{| style="font-size: 175%; border-spacing: 0; background-color: black; border: 2px solid black"
|- 
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"| {{Raw Tile|"|7:0:0}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|{{=}}|6:0:0}}
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"|
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|]|0:0:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
|}</center>
| style="padding:10px; line-height: 1em;font-size: 150%;"|
<center>{{Floor Plan|2:1|2:1|2:1|2:0|2:1|2:1|2:0|2:1|2:0}}</center>
|-
| style="text-align: center;" | Layout
|}
|}
|
{| style="width:200px; background-color:#eaecf0;"
|- valign=top
|colspan=2|Change view
|-
|rowspan=2 style="width:50%;"|
<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">[[File:Carpenter's workshop.png]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab""><center>
{| style="font-size: 175%; border-spacing: 0; background-color: black; border: 2px solid black"
|- 
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"| {{Raw Tile|"|7:0:0}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|{{=}}|6:0:0}}
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"|
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|]|0:0:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
|}</center></div>
|
{| style="border-spacing:5px;"
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|}

=== All version ===
{|
|- valign=top
|
{| style="width:200px; background-color:#eaecf0;"
|+ Base
|- valign=top
|colspan=2|Change view
|-
|rowspan=2 style="width:50%;"|
<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">[[File:Carpenter's workshop.png]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab""><center>
{| style="font-size: 175%; border-spacing: 0; background-color: black; border: 2px solid black"
|- 
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"| {{Raw Tile|"|7:0:0}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|{{=}}|6:0:0}}
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"|
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|]|0:0:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
|}</center></div>
|
{| style="border-spacing:5px;"
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|
{| style="width:200px; background-color:#eaecf0; border-collapse: collapse; "
|+ 3x3
|- style="border-bottom:2px solid #3366cc; "
|colspan=2 style="text-align: right;"|<div class="mw-customtoggle-infoboxtab mw-ui-button mw-ui-progressive" style="float:left; border-top-right-radius: 10px; border-top-left-radius:10px;">toggle</div>{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|- valign=top
|rowspan=2 style="width:50%;"|
<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">[[File:Carpenter's workshop.png]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab""><center>
{| style="font-size: 175%; border-spacing: 0; background-color: black; border: 2px solid black"
|- 
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"| {{Raw Tile|"|7:0:0}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|{{=}}|6:0:0}}
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"|
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|]|0:0:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
|}</center></div>
|
{| style="border-spacing:5px;"
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|
{| style="width:200px; background-color:#eaecf0; border-collapse: collapse; "
|+ 5x5
|- style="border-bottom:2px solid #3366cc; "
|<div class="mw-customtoggle-infoboxtab mw-ui-button mw-ui-progressive" style="border-top-right-radius: 10px; border-top-left-radius:10px;">toggle</div>
|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|- valign=top
|colspan=2|<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">
[[File:Siege workshop.png|center|160px]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab"">
{|
|rowspan=2 style="width:50%; font-size: 125%;"|<center>{{Template:Picture Siege workshop}}</center>
|style="line-height: 1em; font-size: 125%;"|
{| style="border-spacing:4px;"
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|}
|
{| style="width:200px; height:100px; padding:10px; background-color:#eaecf0; border-collapse: collapse;"
|+ 1x1
|- style="border-bottom:2px solid #3366cc;"
| colspan=3 style="text-align:center;"|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|-
| style="border-right: 1px dotted #545557;"|[[File:Screw_press.png|32px|center|link=]]
| style="font-size:125%;"|<center>{{Template:Picture Screw press}}</center>
| style="border-left: 1px dotted #545557;"|<center>{{Template:Floor Plan Screw press}}</center>
|}
|
{| style="width:200px; height:100px; padding:10px; background-color:#eaecf0; border-collapse: collapse;"
|+ 1x3
|- style="border-bottom:2px solid #3366cc;"
| colspan=3 style="text-align:center;"|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|-
| style="border-right: 1px dotted #545557;"|[[File:water_wheel.png|32px|center|link=]]
| style="font-size:125%;"|<center>{{Template:Picture Water wheel}}</center>
| style="border-left: 1px dotted #545557;line-height:normal;"|<center>{{Template:Floor Plan Water wheel}}</center>
|}
|}

== Gamefolder ==

If you installed ''Dwarf Fortress'' on Arch Linux using <tt>pacman</tt>, then running <tt>dwarffortress</tt> will dump the configuration files you should edit into your home directory under <tt>.dwarffortress</tt> - editing the files under <tt>/opt/dwarffortress/data/init</tt> will ''not'' change how the game behaves.

SU by default we believe the itch.io app stores game files in `%APPDATA%/itch/apps`, at least on windows.

== Misc ==

{{User:Lethosor/header}}

[[:Category:Message_box_templates]]
{{ambox
|type=warn
|text=Welcome to the Dwarf Fortress Wiki! 
'''Please do not add content specific to v50 (the new DF premium release) yet!''' We are working on a migration that will be complete in the next few days. Adding content for v0.47 or to other pages is still encouraged.
}}

<div class="" style="padding: 0.8em 1em; margin: 0.5rem 0; background: #d9edf7; border-left: 5px solid #1b809e;">
{{:Main_Page/Quote}}
</div>
<div class="" style="padding: 0.8em 1em; margin: 0.5rem 0; background: #fcf8e3; border-left: 5px solid #aa6708;">
{{:Main_Page/Quote}}
</div>
<div class="" style="padding: 0.8em 1em; margin: 0.5rem 0; background: #dff0d8; border-left: 5px solid #3c763d;">
{{:Main_Page/Quote}}
</div>
</div>
<div class="" style="padding: 0.8em 1em; margin: 0.5rem 0; background: #f2dede; border-left: 5px solid #ce4844;">
{{:Main_Page/Quote}}
</div>

How does a dwarven light bulb looks like?

{| class="" style="width:100%; margin: 0.5rem 0; background: #d9edf7; border-left: 5px solid #1b809e;"
| style="" | [[File:BulbIcon.svg|link=]]
| Style="padding: 0.8em 1em 0.8em 0px;" | {{:Main_Page/Quote}}
|}
{| class="" style="width:100%; margin: 0.5rem 0; background: #d9edf7; border-left: 5px solid #1b809e;"
| style="" | [[File:BulbIcon.svg|75px|link=]]
| Style="padding: 0.8em 1em 0.8em 0px;" |
{{:Main_Page/Quote}}

{{:Main_Page/Quote}}

{{:Main_Page/Quote}}

{{:Main_Page/Quote}}
|}

[[File:Bulbgraph.png|18px|link=]] '''Note''': {{:Main_Page/Quote}}

-----

<gallery mode="packed-hover">
File:Dwarf head pixel.png
File:D4Dwarf.png
File:DFDefault.png
File:Dwarven science stretched.png
File:Beer mug.svg
File:Books-aj.svg
File:Forge Noun project 1044767.svg
File:36 Vikingo.svg
File:115 Nano.svg
File:Dwarf Fortress Icon.svg
File:BulbIcon.svg
File:Microsoft_Tips_icon.png
File:Eucalyp-Deus_WikiDwarf_(black).png
File:Gimli_son_of_Gloin_by_Perrie_Nicholas_Smith.jpg
</gallery>

----

{{TipBox2|float=right|titlebg=#0a0|Conserving Resources|Some things absolutely require wood (like beds and charcoal), but others can be made out of more common materials like stone. For this reason it's best, especially in the beginning, to make everything that you can out of stone. For example, you could make wood chests and barrels, but stone coffers and rock pots would let you save wood for things that require it and help you rid yourself of all that stone. And if you decide you want solid gold chests or something later when you have more resources, you can always throw out the rock coffers.}}

<div style="float:right; clear:both; width: 35%; background-color: #f9f9fb; border: 1px solid #cdcdcd; border-radius: 0.25rem; box-shadow: 0 1px 2px rgba(43,42,51,.05); margin: 2rem 0; padding: 1rem;">
<div style="font-size: 1.424rem;>Conserving Resources</div>
Some things absolutely require wood (like beds and charcoal), but others can be made out of more common materials like stone. For this reason it's best, especially in the beginning, to make everything that you can out of stone. For example, you could make wood chests and barrels, but stone coffers and rock pots would let you save wood for things that require it and help you rid yourself of all that stone. And if you decide you want solid gold chests or something later when you have more resources, you can always throw out the rock coffers.
</div>

<div style="float:right; clear:both; width: 35%; background-color: #f9f9fb; border: 1px solid #cdcdcd; border-left: 5px solid #3c763d; border-radius: 0.25rem; box-shadow: 0 1px 2px rgba(43,42,51,.05); margin: 2rem 0; padding: 1rem;">
<div style="font-size: 1.424rem;>Conserving Resources</div>
Some things absolutely require wood (like beds and charcoal), but others can be made out of more common materials like stone. For this reason it's best, especially in the beginning, to make everything that you can out of stone. For example, you could make wood chests and barrels, but stone coffers and rock pots would let you save wood for things that require it and help you rid yourself of all that stone. And if you decide you want solid gold chests or something later when you have more resources, you can always throw out the rock coffers.
</div>

<div style="float:right; clear:both; width: 35%; background-color: #f9f8f5; border: 1px solid #cdcdcd; border-left: 5px solid #cdcdcd; border-radius: 0.25rem; box-shadow: 0 1px 2px rgba(43,42,51,.05); margin: 2rem 0; padding: 1rem;">
<div style="font-size: 1.424rem;>Conserving Resources</div>
Some things absolutely require wood (like beds and charcoal), but others can be made out of more common materials like stone. For this reason it's best, especially in the beginning, to make everything that you can out of stone. For example, you could make wood chests and barrels, but stone coffers and rock pots would let you save wood for things that require it and help you rid yourself of all that stone. And if you decide you want solid gold chests or something later when you have more resources, you can always throw out the rock coffers.
</div>

<div style="float:right; clear:both; width: 35%; background-color: #fcf8e3; border: 1px solid #cdcdcd; border-left: 5px solid #aa6708; border-radius: 0.25rem; box-shadow: 0 1px 2px rgba(43,42,51,.05); margin: 2rem 0; padding: 1rem;">
<div style="position:abolute; margin-top: -50px;">[[File:Dwarf Fortress Icon.svg|right|link=]]</div>
<div style="font-size: 1.424rem;>Conserving Resources</div>

Some things absolutely require wood (like beds and charcoal), but others can be made out of more common materials like stone. For this reason it's best, especially in the beginning, to make everything that you can out of stone. For example, you could make wood chests and barrels, but stone coffers and rock pots would let you save wood for things that require it and help you rid yourself of all that stone. And if you decide you want solid gold chests or something later when you have more resources, you can always throw out the rock coffers.
</div>

{{Clear}}
----

{| {{prettytable}}
|- style='background-color:#ddd'
! width="20%" | Token
! width="20%" | Arguments
! width="60%" | Description

|-
| {{text anchor|NAME}}
|
*name
| The singular form of the plant's name as seen in-game.

|-
| {{text anchor|NAME_PLURAL}}
|
*name
| The plural form of the plant's name as seen in-game.

|-
| {{text anchor|ADJ}}
|
*adjective
| The word or phrase used to describe items made from this plant.

|-
| {{text anchor|ALL_NAMES}}
|
*name
| Sets the NAME, NAME_PLURAL, and ADJ to the specified string.

|-
| {{text anchor|PREFSTRING}}
|
*reason
| What dwarves can like this object for (e.g. "Urist likes plump helmets for their rounded tops.")

|-
| {{text anchor|MATERIAL}}
|
*material_name
| Starts defining a new local plant material with the given name and '''no''' properties.

|-
| {{text anchor|USE_MATERIAL}}
|
*material_name
*old_material
| Starts defining a new local plant material with the given name and using the properties of another local plant material.

|-
| {{text anchor|USE_MATERIAL_TEMPLATE}}
|
*material_name
*template_name
| Starts defining a new local plant material with the given name and using the properties of the specified material template.

|-
| {{text anchor|BASIC_MAT}}
|
* [[Material token|material]]
| Sets the basic material of the plant. According to Toady, you can use other materials (for instance, iron) but the game may hiccup on plants that aren't structurally plants. For crops, said material should have [STRUCTURAL_PLANT_MAT] to permit proper stockpiling. Generally, this should be "LOCAL_PLANT_MAT:material_name", using a material defined using MATERIAL, USE_MATERIAL, or USE_MATERIAL_TEMPLATE.
|}

{| {{prettytable}}
|- style='background-color:#ddd'
! width="20%" | Token
! width="20%" | Arguments
! width="60%" | Description

|-
|{{text anchor|NAME}}
|
*name
| The singular form of the plant's name as seen in-game.
border-top:1px solid #dddddd;
|- style='background-color:#f5f5f5'
| {{text anchor|NAME_PLURAL}}
|
*name
| The plural form of the plant's name as seen in-game.

|-
| {{text anchor|ADJ}}
|
*adjective
| The word or phrase used to describe items made from this plant.

|- style='background-color:#f5f5f5'
| {{text anchor|ALL_NAMES}}
|
*name
| Sets the NAME, NAME_PLURAL, and ADJ to the specified string.

|-
| {{text anchor|PREFSTRING}}
|
*reason
| What dwarves can like this object for (e.g. "Urist likes plump helmets for their rounded tops.")

|- style='background-color:#f5f5f5'
| {{text anchor|MATERIAL}}
|
*material_name
| Starts defining a new local plant material with the given name and '''no''' properties.

|-
| {{text anchor|USE_MATERIAL}}
|
*material_name
*old_material
| Starts defining a new local plant material with the given name and using the properties of another local plant material.

|- style='background-color:#f5f5f5'
| {{text anchor|USE_MATERIAL_TEMPLATE}}
|
*material_name
*template_name
| Starts defining a new local plant material with the given name and using the properties of the specified material template.

|-
| {{text anchor|BASIC_MAT}}
|
* [[Material token|material]]
| Sets the basic material of the plant. According to Toady, you can use other materials (for instance, iron) but the game may hiccup on plants that aren't structurally plants. For crops, said material should have [STRUCTURAL_PLANT_MAT] to permit proper stockpiling. Generally, this should be "LOCAL_PLANT_MAT:material_name", using a material defined using MATERIAL, USE_MATERIAL, or USE_MATERIAL_TEMPLATE.
|}

{| style="border: none;padding:8px; border-top:1px solid #dddddd;|{{prettytable}} style="border: none;padding:8px; width:auto;"
|- style='background-color:#ddd; border: none;padding:8px;'
! style="border: none;padding:8px; border-top:1px solid #dddddd; width:20%;"|Token
! style="border: none;padding:8px; border-top:1px solid #dddddd; width:20%;"|Arguments
! style="border: none;padding:8px; border-top:1px solid #dddddd;"|Description

|- style=''
| style="border: none;padding:8px; border-top:1px solid #dddddd;|{{text anchor|NAME}}
| style="border: none;padding:8px; border-top:1px solid #dddddd;|
*name
| style="border: none;padding:8px; border-top:1px solid #dddddd;|The singular form of the plant's name as seen in-game.
|- style='background-color:#f5f5f5;'
| style="border: none;padding:8px; border-top:1px solid #dddddd;|{{text anchor|NAME_PLURAL}}
| style="border: none;padding:8px; border-top:1px solid #dddddd;|
*name
| style="border: none;padding:8px; border-top:1px solid #dddddd;|The plural form of the plant's name as seen in-game.

|- style=''
| style="border: none;padding:8px; border-top:1px solid #dddddd;|{{text anchor|ADJ}}
| style="border: none;padding:8px; border-top:1px solid #dddddd;|
*adjective
| style="border: none;padding:8px; border-top:1px solid #dddddd;|The word or phrase used to describe items made from this plant.

|- style='padding:8px !important; background-color:#f5f5f5'
| style="border: none;padding:8px; border-top:1px solid #dddddd;|{{text anchor|ALL_NAMES}}
| style="border: none;padding:8px; border-top:1px solid #dddddd;|
*name
| style="border: none;padding:8px; border-top:1px solid #dddddd;|Sets the NAME, NAME_PLURAL, and ADJ to the specified string.

|- style=''
| style="border: none;padding:8px; border-top:1px solid #dddddd;|{{text anchor|PREFSTRING}}
| style="border: none;padding:8px; border-top:1px solid #dddddd;|
*reason
| style="border: none;padding:8px; border-top:1px solid #dddddd;|What dwarves can like this object for (e.g. "Urist likes plump helmets for their rounded tops.")

|- style='padding:8px !important;background-color:#f5f5f5'
| style="border: none;padding:8px; border-top:1px solid #dddddd;|{{text anchor|MATERIAL}}
| style="border: none;padding:8px; border-top:1px solid #dddddd;|
*material_name
| style="border: none;padding:8px; border-top:1px solid #dddddd;|Starts defining a new local plant material with the given name and '''no''' properties.

|- style=''
| style="border: none;padding:8px; border-top:1px solid #dddddd;|{{text anchor|USE_MATERIAL}}
| style="border: none;padding:8px; border-top:1px solid #dddddd;|
*material_name
*old_material
| style="border: none;padding:8px; border-top:1px solid #dddddd;|Starts defining a new local plant material with the given name and using the properties of another local plant material.

|- style='padding:8px !important;background-color:#f5f5f5'
| style="border: none;padding:8px; border-top:1px solid #dddddd;|{{text anchor|USE_MATERIAL_TEMPLATE}}
| style="border: none;padding:8px; border-top:1px solid #dddddd;|
*material_name
*template_name
| style="border: none;padding:8px; border-top:1px solid #dddddd;|Starts defining a new local plant material with the given name and using the properties of the specified material template.

|- style=''
| style="border: none;padding:8px; border-top:1px solid #dddddd;|{{text anchor|BASIC_MAT}}
| style="border: none;padding:8px; border-top:1px solid #dddddd;|
* [[Material token|material]]
| style="border: none;padding:8px; border-top:1px solid #dddddd;|Sets the basic material of the plant. According to Toady, you can use other materials (for instance, iron) but the game may hiccup on plants that aren't structurally plants. For crops, said material should have [STRUCTURAL_PLANT_MAT] to permit proper stockpiling. Generally, this should be "LOCAL_PLANT_MAT:material_name", using a material defined using MATERIAL, USE_MATERIAL, or USE_MATERIAL_TEMPLATE.
|}

<pre>
.wikitable,
.prettytable{
border: none !important;
width:auto;
max-width:100%;
margin-bottom:20px;
background-color:transparent;
border-spacing:0px;
}
.wikitable tr,
.prettytable tr{
border-top:1px solid #dddddd;
}
.wikitable th,.prettytable th{
border: none !important;
text-align:left;
}
.wikitable td,.wikitable th,
.prettytable td,.prettytable th{
border: none !important;
padding:0;
}
.wikitable tr > th,
.prettytable tr > th{
padding:8px !important;
line-height:1.42857143;
vertical-align:top;
border-top:1px solid #dddddd;
border-collapse:collapse;
border-spacing:0;
text-align:center;
vertical-align:middle;
}
.wikitable tr > td,
.prettytable tr > td{
padding:8px !important;
line-height:1.42857143;
vertical-align:top;
border-top:1px solid #dddddd;
border-collapse:collapse;
border-spacing:0
}
.wikitable tbody > tr:nth-child(even),
.prettytable tbody > tr:nth-child(even){
background-color:#f5f5f5
}
.wikitable tr > th.headerSort,
.prettytable tr > th.headerSort{
padding-right:21px !important
}
/*
.wikitable tr:hover{
background: #f1f1f1;
*/
}
</pre>

== Navigation ==

User Interface:
* [[Dwarf fortress mode#Gameplay user interface]] • [[Map legend]] • [[Status icon]]
* [[Controls]] • [[Controls guide]] • [[Hotkeys]] • [[Macros and keymaps]] • [[Note]]
* [[Interface‎‎]] • [[Menu]] • [[Status|Status screen]] • [[Health screen]] • [[Nobles screen]] • [[Military interface]] • [[Thoughts and preferences]]
* • • • • •

* Gameplay settings: [[announcements.txt]] • [[d_init.txt]]
* Settings: [[init.txt]] • [[Technical tricks]] • [[interface.txt]]

* [[About]] (vs [[Dwarf Fortress]] ?)
* Download & [[Installation]] • [[System requirements]]

* [[Dwarf fortress mode]] • [[Tutorials]] • [[Frequently Asked Questions]] • [[Troubleshooting]] • [[:Category:DF2014:Errors]]
* [[Adventurer mode]] • [[Adventure mode quick start]] • [[Adventure mode quick reference]]
* [[Frames per second]]

----

* [[world generation]] • [[Embark]]
:: [[Quickstart_guide#Pre-Embark]] • [[Quickstart guide/Starting site]] • [[Site finder]] • [[Starting build]]
* [[Troubleshooting]] • [[Frequently Asked Questions]]

* [[Tutorials]] • [[Quickstart guide]] • [[:Category:DF2014:Getting_started]] • [[:Category:DF2014:Quickstart guide]]
* [[:Category:Guides]]

* [[Important advice]]

* [[Design strategies]]

* [[Race]]s • [[Creature]]s
* [[Skills]]

* [[Industry]]
* [[Farming]] • [[Trading]] [[Military]]

* [[Item]]s • [[Materials]] ( [[Material science]] • [[:Category:DF2014:Material properties]] )
* [[Armor]] • [[Weapons]]

* [[Building]] [[Workshop]] [[Furnace]]

----

* [[Biome]] • [[Surroundings]] • [[Climate]] • [[Weather]]
* [[Civilization]] • [[Site]]s •
* [[Nobles]] • [[Holding]]s •

* [[Calendar]]

----
* [[Dwarf Fortress]] [[Reception of Dwarf Fortress]] [[Community of Dwarf Fortress]] [[Legacy of Dwarf Fortress]]
* Development: [[DF2014:Release information|Release information]] • [[Dwarf Fortress Talk|Developer diaries]] • [[Dwarf Fortress Development|Roadmap]]

* [[Challenge]]: [[Playstyle challenge]] [[Megaproject]] [[Stupid dwarf trick]]
* [[:Category:Humor_and_stories]]

* [[!!SCIENCE!!]]
----

[[Modding]]:
* Documentation: [[Token]]s • [[Raw file]] • [[Reactions]] • [[syndrome]]
* [[Speech file]] • [[Dipscript]]

* [[Graphics]]: [[Tilesets]] • [[Graphic set]] • [[Color]] • [[Color scheme]] • [[Character table]]

Development:
* [[DF2014:Release information|Release information]] • [[Dwarf Fortress Talk|Developer diaries]] • [[Dwarf Fortress Development|Roadmap]]

Tools & Utilities
* [[Utilities#Modding tools]]

[[:Category:DF2014:Files|Game Files]]:
* Gameplay settings: [[announcements.txt]] • [[d_init.txt]]
* Settings: [[colors.txt]] • [[init.txt]] • [[interface.txt]]
* Log files: [[errorlog.txt]] • [[gamelog.txt]]
* [[Saved game folder]] 

----
{{Modding navbox|state=collapsed}}

* [[Interaction token|Interaction]] • [[Material token|Material]] • [[Inorganic material definition token|Inorganic material definition]] • [[Plant token|Plant]] •

--

Misc Mechanics:
* [[stress]] [[Thought]] [[Emotion]] [[personalities]] [[Preferences]]
* [[Gait]] • [[Genetics]] • [[Size]] • [[Personality trait]] • [[Attribute]] •

* [[:Category:DF2014:Material_properties]] - [[Material science]]
:* Defined: [[Item value#Material multipliers|Value]] • [[Color#Material_By_Color|Color]] • [[Density]] • [[Strain at yield]] • [[Temperature#Material values|Temperature values]]
:* Derived: [[Magma-safe|Magma safety]] • [[Fire-safe|Fire safety]]
:* Fluids: [[Depth]] • [[Flow]] • [[Pressure]]

* [[:Category:DF2014:Modding Examples]]: [[Interaction examples]] • [[Reaction examples]] • [[Creature examples]]

* [[Text viewer]](?)
* [[World token|World]] • [[Biome token|Biome]] •
* [[Syndrome token|Syndrome]] •

token nonsense testing style options
{{Navbox
| name = name1A
| title = [[Modding]] 1A
| state = no

| group1 = Documentation
| list1 = [[Raw file]] • [[Token]]s • [[Reactions]] • [[syndrome]] • [[Speech file]] • [[Dipscript]]

| group2 = [[Graphics]]
| list2 = [[Tilesets]] • [[Graphic set]] • [[Color]] • [[Color scheme]] • [[Character table]]

| below = [[Modding#Guide]] • [[Utilities#Modding tools]] • [[List of mods]] • [[Graphics set repository]] • [[:Category:DF2014:Files|Game Files]]
}}
{{Navbox
| name = name1B
| title = [[Token]]s 1B
| state = no

| group1 = General
| list1 = [[Biome token|Biome]] • [[Creature token|Creature]] • [[Entity token|Entity]] • [[Interaction token|Interaction]] • [[Material token|Material]] • [[Inorganic material definition token|Inorganic material definition]] • [[Plant token|Plant]] • [[Skill token|Skill]] • [[Syndrome token|Syndrome]] • [[World token|World]]

| group2 = Color
| list2 = [[Descriptor color token|Descriptor color]] • [[Descriptor pattern token|Descriptor pattern]] • [[Descriptor shape token|Descriptor shape]]

| group3 = [[Creature token|Creature]]
| list3 = [[Body token|Body]] • [[Body detail plan token|Body detail plan]] • [[Bodygloss]] • [[Creature variation token|Creature variation]] • [[Creature mannerism token|Creature mannerism]] • [[Creature texture token|Creature texture]] • [[Material definition token|Material definition]] • [[Tissue definition token|Tissue definition]] • [[Personality trait]]

| group4 = [[Entity token|Entity]]
| list4 = [[Position token|Position]] • [[Unit type token|Unit type]] • [[Language token|Language]] • [[Building token|Building]] • [[Ethic]]

| group5 = [[Item definition token|Item definition]]
| list5 = [[Ammo token|Ammo]] • [[Armor token|Armor]] • [[Instrument token|Instrument]] • [[Tool token|Tool]] • [[Trap component token|Trap component]] • [[Weapon token|Weapon]] • [[Item definition token|Other]]

| group6 = [[Reactions]]
| list6 = [[Item token|Item]] • [[Labor token|Labor]] • [[Skill token|Skill]]

}}

{{Navbox
| name = name2
| title = [[Modding]] 2
| state = no

| group1 = Documentation
| list1 = [[Token]]s • [[Raw file]] • [[Reactions]] • [[syndrome]] • [[Speech file]] • [[Dipscript]]

| group2 = [[Graphics]]
| list2 = [[Tilesets]] • [[Graphic set]] • [[Color]] • [[Color scheme]] • [[Character table]]

| group3 = [[Token]]s
| list3 = [[Ammo token|Ammo]] • [[Armor token|Armor]] • [[Biome token|Biome]] • [[Building token|Building]] • [[Body token|Body]] • [[Body detail plan token|Body detail plan]] • [[Bodygloss]] • [[Creature token|Creature]] • [[Creature mannerism token|Creature mannerism]] • [[Creature texture token|Creature texture]] • [[Creature variation token|Creature variation]] • [[Descriptor color token|Descriptor color]] • [[Descriptor pattern token|Descriptor pattern]] • [[Descriptor shape token|Descriptor shape]] • [[Entity token|Entity]] • [[Item token|Item]] • [[Item definition token|Item definition]] • [[Instrument token|Instrument]] • [[Interaction token|Interaction]] • [[Labor token|Labor]] • [[Language token|Language]] • [[Material token|Material]] • [[Material definition token|Material definition]] • [[Inorganic material definition token|Inorganic material definition]] • [[Personality trait]] • [[Plant token|Plant]] • [[Position token|Position]] • [[Skill token|Skill]] • [[Syndrome token|Syndrome]] • [[Tissue definition token|Tissue definition]] • [[Tool token|Tool]] • [[Trap component token|Trap component]] • [[Unit type token|Unit type]] • [[Weapon token|Weapon]] • [[World token|World]]

| below = [[Modding#Guide]] • [[Utilities#Modding tools]] • [[List of mods]] • [[Graphics set repository]] • [[:Category:DF2014:Files|Game Files]]
}}

{{Navbox
| name = name3A
| title = [[Modding]] 3A
| state = no
| bodystyle = width:100%;

| group1 = Documentation
| list1 = [[Token]]s • [[Raw file]] • [[Reactions]] • [[syndrome]] • [[Speech file]] • [[Dipscript]]

| group2 = [[Graphics]]
| list2 = [[Tilesets]] • [[Graphic set]] • [[Color]] • [[Color scheme]] • [[Character table]]

| group3 = [[Token]]s
| list3 = [[Ammo token|Ammo]] • [[Armor token|Armor]] • [[Biome token|Biome]] • [[Building token|Building]] • [[Body token|Body]] • [[Body detail plan token|Body detail plan]] • [[Bodygloss]] • [[Creature token|Creature]] • [[Creature mannerism token|Creature mannerism]] • [[Creature texture token|Creature texture]] • [[Creature variation token|Creature variation]] • [[Descriptor color token|Descriptor color]] • [[Descriptor pattern token|Descriptor pattern]] • [[Descriptor shape token|Descriptor shape]] • [[Entity token|Entity]] • [[Item token|Item]] • [[Item definition token|Item definition]] • [[Instrument token|Instrument]] • [[Interaction token|Interaction]] • [[Labor token|Labor]] • [[Language token|Language]] • [[Material token|Material]] • [[Material definition token|Material definition]] • [[Inorganic material definition token|Inorganic material definition]] • [[Personality trait]] • [[Plant token|Plant]] • [[Position token|Position]] • [[Skill token|Skill]] • [[Syndrome token|Syndrome]] • [[Tissue definition token|Tissue definition]] • [[Tool token|Tool]] • [[Trap component token|Trap component]] • [[Unit type token|Unit type]] • [[Weapon token|Weapon]] • [[World token|World]]

| below = [[Modding guide]] • [[Utilities#Modding tools]] • [[List of mods]] • [[Graphics set repository]] • [[:Category:DF2014:Files|Game Files]]
}}
{{Navbox
| name = name3B
| title = [[Modding]] 3B large list double space
| state = no
| bodystyle = width:100%;

| group1 = Documentation
| list1 = [[Token]]s • [[Raw file]] • [[Reactions]] • [[syndrome]] • [[Speech file]] • [[Dipscript]]

| group2 = [[Graphics]]
| list2 = [[Tilesets]] • [[Graphic set]] • [[Color]] • [[Color scheme]] • [[Character table]]

| group3 = [[Token]]s
| list3 = [[Ammo token|Ammo]]{{*}}[[Armor token|Armor]]{{*}}[[Biome token|Biome]]{{*}}[[Building token|Building]]{{*}}[[Body token|Body]]{{*}}[[Body detail plan token|Body detail plan]]{{*}}[[Bodygloss]]{{*}}[[Creature token|Creature]]{{*}}[[Creature mannerism token|Creature mannerism]]{{*}}[[Creature texture token|Creature texture]]{{*}}[[Creature variation token|Creature variation]]{{*}}[[Descriptor color token|Descriptor color]]{{*}}[[Descriptor pattern token|Descriptor pattern]]{{*}}[[Descriptor shape token|Descriptor shape]]{{*}}[[Entity token|Entity]]{{*}}[[Item token|Item]]{{*}}[[Item definition token|Item definition]]{{*}}[[Instrument token|Instrument]]{{*}}[[Interaction token|Interaction]]{{*}}[[Labor token|Labor]]{{*}}[[Language token|Language]]{{*}}[[Material token|Material]]{{*}}[[Material definition token|Material definition]]{{*}}[[Inorganic material definition token|Inorganic material definition]]{{*}}[[Personality trait]]{{*}}[[Plant token|Plant]]{{*}}[[Position token|Position]]{{*}}[[Skill token|Skill]]{{*}}[[Syndrome token|Syndrome]]{{*}}[[Tissue definition token|Tissue definition]]{{*}}[[Tool token|Tool]]{{*}}[[Trap component token|Trap component]]{{*}}[[Unit type token|Unit type]]{{*}}[[Weapon token|Weapon]]{{*}}[[World token|World]]

| below = [[Modding guide]] • [[Utilities#Modding tools]] • [[List of mods]] • [[Graphics set repository]] • [[:Category:DF2014:Files|Game Files]]
}}
{{Navbox
| name = name5
| title = [[Modding]] 5 large list grouping instead of sub groups - automatic with hlist
| state = no
| bodystyle = width:100%;

| group1 = Documentation
| list1 = [[Token]]s • [[Raw file]] • [[Reactions]] • [[syndrome]] • [[Speech file]] • [[Dipscript]]

| group2 = [[Graphics]]
| list2 = [[Tilesets]] • [[Graphic set]] • [[Color]] • [[Color scheme]] • [[Character table]]

| group3 = [[Token]]s
| list3 = [[Biome token|Biome]] • [[Creature token|Creature]]'''('''[[Body token|Body]] • [[Body detail plan token|Body detail plan]] • [[Bodygloss]] • [[Creature variation token|Creature variation]] • [[Creature mannerism token|Creature mannerism]] • [[Creature texture token|Creature texture]] • [[Material definition token|Material definition]] • [[Tissue definition token|Tissue definition]] • [[Personality trait]]''')''' •
Color'''('''[[Descriptor color token|Descriptor color]] • [[Descriptor pattern token|Descriptor pattern]] • [[Descriptor shape token|Descriptor shape]]''')''' • [[Entity token|Entity]]'''('''[[Position token|Position]] • [[Unit type token|Unit type]] • [[Language token|Language]] • [[Building token|Building]] • [[Ethic]]''')''' • [[Item definition token|Item definition]]'''('''[[Ammo token|Ammo]] • [[Armor token|Armor]] • [[Instrument token|Instrument]] • [[Tool token|Tool]] • [[Trap component token|Trap component]] • [[Weapon token|Weapon]] • [[Item definition token|Other]]''')''' • [[Interaction token|Interaction]] • [[Material token|Material]] • [[Inorganic material definition token|Inorganic material definition]] • [[Plant token|Plant]] • [[Reactions]]'''('''[[Item token|Item]] • [[Labor token|Labor]] • [[Skill token|Skill]]''')''' • [[Syndrome token|Syndrome]] • [[World token|World]]

| below = [[Modding guide]] • [[Utilities#Modding tools]] • [[List of mods]] • [[Graphics set repository]] • [[:Category:DF2014:Files|Game Files]]
}}
{{Navbox
| name = name5A
| title = [[Modding]] 5A - grouping, double space
| state = no
| bodystyle = width:100%;

| group1 = Documentation
| list1 = [[Token]]s • [[Raw file]] • [[Reactions]] • [[syndrome]] • [[Speech file]] • [[Dipscript]]

| group2 = [[Graphics]]
| list2 = [[Tilesets]] • [[Graphic set]] • [[Color]] • [[Color scheme]] • [[Character table]]

| group3 = [[Token]]s
| list3 = [[Biome token|Biome]]{{*}} [[Creature token|Creature]]([[Body token|Body]]{{*}}[[Body detail plan token|Body detail plan]]{{*}}[[Bodygloss]]{{*}}[[Creature variation token|Creature variation]]{{*}}[[Creature mannerism token|Creature mannerism]]{{*}}[[Creature texture token|Creature texture]]{{*}}[[Material definition token|Material definition]]{{*}}[[Tissue definition token|Tissue definition]]{{*}}[[Personality trait]]) {{*}} Color([[Descriptor color token|Descriptor color]]{{*}}[[Descriptor pattern token|Descriptor pattern]]{{*}}[[Descriptor shape token|Descriptor shape]]) {{*}} [[Entity token|Entity]]([[Position token|Position]]{{*}}[[Unit type token|Unit type]]{{*}}[[Language token|Language]]{{*}}[[Building token|Building]]{{*}}[[Ethic]]) {{*}} [[Item definition token|Item definition]]([[Ammo token|Ammo]]{{*}}[[Armor token|Armor]]{{*}}[[Instrument token|Instrument]]{{*}}[[Tool token|Tool]]{{*}}[[Trap component token|Trap component]]{{*}}[[Weapon token|Weapon]]{{*}}[[Item definition token|Other]]) {{*}}[[Interaction token|Interaction]]{{*}}[[Material token|Material]]{{*}}[[Inorganic material definition token|Inorganic material definition]]{{*}}[[Plant token|Plant]]{{*}} [[Reactions]]([[Item token|Item]]{{*}}[[Labor token|Labor]]{{*}}[[Skill token|Skill]]) {{*}}[[Syndrome token|Syndrome]]{{*}}[[World token|World]]

| below = [[Modding guide]] • [[Utilities#Modding tools]] • [[List of mods]] • [[Graphics set repository]] • [[:Category:DF2014:Files|Game Files]]
}}
{{Navbox
| name = name5B
| title = [[Modding]] 5B grouping bold, double space
| state = no
| bodystyle = width:100%;

| group1 = Documentation
| list1 = [[Token]]s • [[Raw file]] • [[Reactions]] • [[syndrome]] • [[Speech file]] • [[Dipscript]]

| group2 = [[Graphics]]
| list2 = [[Tilesets]] • [[Graphic set]] • [[Color]] • [[Color scheme]] • [[Character table]]

| group3 = [[Token]]s
| list3 = [[Biome token|Biome]]{{*}}'''[[Creature token|Creature]]'''([[Body token|Body]]{{*}}[[Body detail plan token|Body detail plan]]{{*}}[[Bodygloss]]{{*}}[[Creature variation token|Creature variation]]{{*}}[[Creature mannerism token|Creature mannerism]]{{*}}[[Creature texture token|Creature texture]]{{*}}[[Material definition token|Material definition]]{{*}}[[Tissue definition token|Tissue definition]]{{*}}[[Personality trait]]){{*}}'''Color'''([[Descriptor color token|Descriptor color]]{{*}}[[Descriptor pattern token|Descriptor pattern]]{{*}}[[Descriptor shape token|Descriptor shape]]){{*}}'''[[Entity token|Entity]]'''([[Position token|Position]]{{*}}[[Unit type token|Unit type]]{{*}}[[Language token|Language]]{{*}}[[Building token|Building]]{{*}}[[Ethic]]){{*}}'''[[Item definition token|Item definition]]'''([[Ammo token|Ammo]]{{*}}[[Armor token|Armor]]{{*}}[[Instrument token|Instrument]]{{*}}[[Tool token|Tool]]{{*}}[[Trap component token|Trap component]]{{*}}[[Weapon token|Weapon]]{{*}}[[Item definition token|Other]]){{*}}[[Interaction token|Interaction]]{{*}}[[Material token|Material]]{{*}}[[Inorganic material definition token|Inorganic material definition]]{{*}}[[Plant token|Plant]]{{*}}'''[[Reactions]]'''([[Item token|Item]]{{*}}[[Labor token|Labor]]{{*}}[[Skill token|Skill]]){{*}}[[Syndrome token|Syndrome]]{{*}}[[World token|World]]

| below = [[Modding guide]] • [[Utilities#Modding tools]] • [[List of mods]] • [[Graphics set repository]] • [[:Category:DF2014:Files|Game Files]]
}}
{{Navbox
| name = name5c
| title = [[Modding]] 5c grouping highilghted otherwise, double space
| state = no
| bodystyle = width:100%;

| group1 = Documentation
| list1 = [[Token]]s • [[Raw file]] • [[Reactions]] • [[syndrome]] • [[Speech file]] • [[Dipscript]]

| group2 = [[Graphics]]
| list2 = [[Tilesets]] • [[Graphic set]] • [[Color]] • [[Color scheme]] • [[Character table]]

| group3 = [[Token]]s
| list3 = [[Biome token|Biome]]{{*}}[[Creature token|Creature]]([[Body token|Body]]{{*}}[[Body detail plan token|Body detail plan]]{{*}}[[Bodygloss]]{{*}}[[Creature variation token|Creature variation]]{{*}}[[Creature mannerism token|Creature mannerism]]{{*}}[[Creature texture token|Creature texture]]{{*}}[[Material definition token|Material definition]]{{*}}[[Tissue definition token|Tissue definition]]{{*}}[[Personality trait]]){{*}}Color([[Descriptor color token|Descriptor color]]{{*}}[[Descriptor pattern token|Descriptor pattern]]{{*}}[[Descriptor shape token|Descriptor shape]]){{*}}[[Entity token|Entity]]([[Position token|Position]]{{*}}[[Unit type token|Unit type]]{{*}}[[Language token|Language]]{{*}}[[Building token|Building]]{{*}}[[Ethic]]){{*}}[[Item definition token|Item definition]]([[Ammo token|Ammo]]{{*}}[[Armor token|Armor]]{{*}}[[Instrument token|Instrument]]{{*}}[[Tool token|Tool]]{{*}}[[Trap component token|Trap component]]{{*}}[[Weapon token|Weapon]]{{*}}[[Item definition token|Other]]){{*}}[[Interaction token|Interaction]]{{*}}[[Material token|Material]]{{*}}[[Inorganic material definition token|Inorganic material definition]]{{*}}[[Plant token|Plant]]{{*}}[[Reactions]]([[Item token|Item]]{{*}}[[Labor token|Labor]]{{*}}[[Skill token|Skill]]){{*}}[[Syndrome token|Syndrome]]{{*}}[[World token|World]]

| below = [[Modding guide]] • [[Utilities#Modding tools]] • [[List of mods]] • [[Graphics set repository]] • [[:Category:DF2014:Files|Game Files]]
}}

=== Reference ===
{{Template:DF2014 buildings}}
{{Template:DF2014 creatures}}
{{Template:DF2014 diamonds}}
{{Template:DF2014 files}}
{{Template:DF2014 gems}}
{{Template:DF2014 labors}}
{{Template:DF2014 materials}}
{{Template:DF2014 metals}}
{{Template:DF2014 military}}
{{Template:DF2014 nobles}}
{{Template:DF2014 plants}}
{{Template:DF2014 rooms}}
{{Template:DF2014 skills}}
{{Template:DF2014 soil}}
{{Template:DF2014 stones}}
{{Template:DF2014 vermin}}
{{Template:DF2014 weapons}}
{{Template:DF2014 workshops}}
{{Template:DF2014 world}}

= Other Misc curiosities=
{{t|Columns-list}} - [https://en.wikipedia.org/wiki/Template:Div_col/styles.css css "fix"] for the annoying margin glitch that skews columns sometimes.

== Download links ==
Bay12Forum
GitHubSomething

Bay12Download
DFFDDownload
SteamDownload

{{{1|Button text}}}
Get Started Tutorial
== Files ==
Maybe merge many of the file articles stubs, and create an entry which documents all DF important files and folders.

[[File:Folder-orange.svg|20px|link=]] Dwarf Fortress
 &emsp;[[File:Folder.svg|20px|link=]] data
 &emsp;&emsp;[[File:Folder.svg|20px|link=]] art
 &emsp;&emsp;[[File:Folder.svg|20px|link=]] init
 &emsp;&emsp;[[File:Folder.svg|20px|link=]] save
 &emsp;&emsp;[[File:Folder.svg|20px|link=]] sound
 &emsp;[[File:Folder.svg|20px|link=]] raw
 &emsp;&emsp;[[File:Folder.svg|20px|link=]] graphics
 &emsp;&emsp;[[File:Folder.svg|20px|link=]] objects

[[File:Folder-orange.svg|20px|link=]] Dwarf Fortress
 &emsp;[[File:Folder.svg|20px|link=]] data
 &emsp;&emsp;[[File:Folder.svg|20px|link=]] init
 &emsp;&emsp;&emsp;[[File:Text-x-generic.svg|20px|link=]][[announcements.txt]]
 &emsp;&emsp;&emsp;[[File:Text-x-generic.svg|20px|link=]][[arena.txt]]
 &emsp;&emsp;&emsp;[[File:Text-x-generic.svg|20px|link=]][[colors.txt]]
 &emsp;&emsp;&emsp;[[File:Text-x-generic.svg|20px|link=]][[d init.txt]]
 &emsp;&emsp;&emsp;[[File:Text-x-generic.svg|20px|link=]][[embark profiles.txt]]
 &emsp;&emsp;&emsp;[[File:Text-x-generic.svg|20px|link=]][[init.txt]]
 &emsp;&emsp;&emsp;[[File:Text-x-generic.svg|20px|link=]][[interface.txt]]
 &emsp;&emsp;&emsp;[[File:Text-x-generic.svg|20px|link=]][[macros]]
 &emsp;&emsp;&emsp;[[File:Text-x-generic.svg|20px|link=]][[world gen.txt]]
 &emsp;[[File:Text-x-generic.svg|20px|link=]][[gamelog.txt]]
 &emsp;[[File:Text-x-generic.svg|20px|link=]][[errorlog.txt]]

[[File:Folder-orange.svg|20px|link=]]Dwarf Fortress \ [[File:Folder.svg|20px|link=]]data \ [[File:Folder.svg|20px|link=]]init
{| cellspacing="5" style="padding-left: 5px;"
| [[File:Text-x-generic.svg|20px|link=]] [[announcements.txt]]
| used to control the types of [[announcement]]s displayed in-game
|- style="border: 1px solid black;"
| [[File:Text-x-generic.svg|20px|link=]] [[arena.txt]]
|-
| [[File:Text-x-generic.svg|20px|link=]] [[colors.txt]]
| defines the [[color scheme]]
|-
| [[File:Text-x-generic.svg|20px|link=]] [[d init.txt]]
| contains settings that affect game features such as saving and population controls. Further detail [[Technical tricks|here]].
|-
| [[File:Text-x-generic.svg|20px|link=]] [[embark profiles.txt]]
|
|-
| [[File:Text-x-generic.svg|20px|link=]] [[init.txt]]
| contains mostly the settings pertaining to the window, rendering and sound of Dwarf Fortress. Further detail [[Technical tricks|here]].
|-
| [[File:Text-x-generic.svg|20px|link=]] [[interface.txt]]
| Manually edit Key bindings
|-
| [[File:Text-x-generic.svg|20px|link=]] [[macros]]
|
|-
| [[File:Text-x-generic.svg|20px|link=]] [[world gen.txt]]
|
|}

== Tokens ==

* [{{text anchor|MANNERISM_EYELIDS}}]
* [{{text anchor|MANNERISM_FINGERS}}:finger:fingers]
* [{{text anchor|MANNERISM_NOSE}}:nose]

syntax highlighting - for simple and quick code block highlight :

<syntaxhighlight lang="BBCode">
* [MANNERISM_EYELIDS]
* [MANNERISM_FINGERS:finger:fingers]
* [MANNERISM_NOSE:nose]
</syntaxhighlight>

Inline template stuff:
* [{{text anchor|MANNERISM_FINGERS}}:finger:fingers]
* [MANNERISM_FINGERS:fingers:fingers]
* [MANNERISM_FINGERS:fingers:fingers]
* [MANNERISM_FINGERS:fingers:fingers]
* [MANNERISM_FINGERS:fingers:fingers]

Template with anchor but no link:
<pre>
[{{{1}}}{{#if:{{{2|}}}|:{{{2}}}}}{{#if:{{{3|}}}|:{{{3}}}}}]
</pre>

== Modding notes ==

* Token is catch all name for everything inside brackets
* Token pages
** Most document how to define new objects of that type.
** Some document how to reference objects and list their default parameters e.g. [[Material_token]] and [[Item_token]]
** Article naming is inconsistent
** Some Token objects aren't covered or aren't tagged as such e.g. [[Caste]].
* Documentation
** Our syntax is sometimes unclear to the uninitiated e.g. [[Creature token]] wth is caste TYPE how it differs from creature type of special?
** Our syntax is sometimes inconsistent.
** Some object names seems inconsistent as far as I understand their use here.
<pre>
[OBJECT:CREATURE]
[CREATURE:<identifier>]

Don't match
[OBJECT:DESCRIPTOR_COLOR] - match article name, never used
[COLOR:<identifier>] - what is used everwhere that I seen.
[OBJECT:DESCRIPTOR_PATTERN]
[COLOR_PATTERN:<identifier>]
[OBJECT:DESCRIPTOR_SHAPE]
[SHAPE:<identifier>]
</pre>

Talk:Release information

2023-01-06T01:17:26Z

Jan:

Serpent man

2023-01-05T23:58:48Z

Jan: no longer an animal person. not sure if still tribal

{{migrated article}}
{{Quality|Unrated}}
{{Creaturelookup/0
|contrib=no
|death=nobutcher
|vary=no
}}
{{av}}
''For other kinds of snake men see [[adder man]], [[anaconda man]], [[black mamba man]], [[bushmaster man]], [[copperhead snake man]], [[King cobra man]], [[kingsnake man]], [[python man]], and [[rattlesnake man]].''
{{creaturedesc}}

'''Serpent men''' are one of the many underworld tribal Creature living on any [[cavern]] level milling around piles of [[food|meat]] and [[leather|tanned hides]]. They stand at roughly the size of an adult [[dwarf]].

Approach with caution, unless the tribe is friendly. If the tribe is friendly, feel free to take advantage of them in fine imperialistic tradition and steal all their resources without compensation. To check whether a tribe of serpent men is friendly, press {{k|u}} to view the unit list. The tribe will be labeled as either hostile or friendly. Alternatively, press {{k|v}} to view one of their profiles.

Like many underground races, the danger of serpent men is not to be found in their [[wood]]en [[weapon]]s, but in the substances found smeared on them. Serpent men use many [[syndrome|poisons]], some of which can be deadly. They will launch group attacks on your fort, and have the ability to swim through your reservoirs and launch amphibious assaults on your [[fisherdwarf|fisherdwarves]]. Additionally, serpent men possess a poisonous bite which paralyzes enemies, making them vulnerable to suffocation as well as other attacks from other serpent men. Serpent men themselves are completely immune to paralysis. Despite their description, they do not possess the {{token|EVIL}} token and are not any more malevolent than any other race of animal people.

If you ssspeak to a ssserpent man in [[adventure mode]], they will talk like thisss, becaussse of the {{token|LISP}} token.

Some [[dwarves]] [[Preferences|like]] serpent men for their ''impressive tails''.

[[File:serpent_man_prev.jpg|thumb|200px|center|Does a great "steam blowing through pipes" impression.]]

{{D for Dwarf}}

There are rumors of a Serpent woman living with a male [[human]], a [[Harpy]], a [[Cave blob|Slime]], a [[Merperson|Mermaid]], a [[Jumping spider man|Spider woman]] and a [[Centaur]]. (''Context:'' https://en.wikipedia.org/wiki/Monster_Musume)

{{Translation| dwarven = shethel udos | elvish = relira onino | goblin = olsmu ngorûg | human = ithrat abo}}

{{gamedata}}
{{gamedata|title=Entity ([[civilization]]) Raws|{{raw|v50:entity_default.txt|ENTITY|SUBTERRANEAN_ANIMAL_PEOPLES}}}}
{{Creatures}}
{{Category|Humanoids}}

Mod

2023-01-05T23:05:54Z

Jan: /* Publishing on DFFD */

{{For/see|using mods and their basic structure|[[modding]] about making mods}}

A '''mod''' (short for modification) is an alteration of the game and the objective of modding. Modifications can range from small tweaks to complete overhauls.

== Installing Mods ==

Mods can be acquired using the [https://steamcommunity.com/app/975370/workshop/ steam workshop] (if using Steam version), a manual download from [[Bay 12 Forums]] or third party websites (like [https://dffd.bay12games.com/ DFFD]), or by [[Modding|creating]] one yourself.

Users of the Steam version can subscribe to mods on Steam Workshop, once the download is complete they will be available when creating a new world automatically. Otherwise, manually download the mod, then place the mod zip file or the unzipped mod folder into the Dwarf Fortress [[mod folder]] (if this folder doesn't exist, you can create it.) You can have more than one mod in the mod folder, including different version of the same mod. The game will detect all mods that are properly made in this folder and let the user select which mods to play (see bellow.)

== Enabling Mods ==
[[File:Ui-p-mod-selection.png|thumb|world generation mod menu]]

When [[World generation|creating a world]] and choosing its initial parameters, if you have a mod available, there should be a '''Mods''' button at the bottom of the screen. Pressing this will let you select which mods you'd like to enable and what the load order should be. You should put mods at the end of the mod list after the vanilla objects if you don't have any further information, so that they can reference vanilla objects after those are loaded.

Something something load order basic

<div class="" style="padding: 0.8em 1em; margin: 0.5rem 0; background: #fcf8e3; border-left: 5px solid #aa6708;">
* Mods are enabled per world and can not be disabled afterwards, however, it is possibly to manually modify the game file as we did in previous versions by applying the mods directly to <code>[[Game folder|<Dwarf Fortress>]]/data/vanilla</code>. Be ware this method has the disadvantage of being a permanent change for all worlds and may break your game.

* Unlike the previous versions of Dwarf Fortress, mods no longer live inside save files and must be installed on every computer where saves using those mods are going to be loaded. Once a world is created that uses mods, then the game will copy the mod to the <code>[[Game folder|<Dwarf Fortress>]]/data/installed_mods</code> folder. That is the version that the game actually uses.
</div>

== Updating Mods ==
If a world is using a mod that's been updated, and is currently using an older version of that mod, the player will be prompted about this when a save is loading. Causing a message like the following to appear: 
[[File:mod_version_v50_prompt.png]]

When this happens, you have the choice of simply updating the mod, updating ''all'' mods at once, continuing to use the older version of the mod in question without updating, selecting the previous task but not updating ''any'' possibly outdated mods or simply returning to the title screen.

== Modding ==

Dwarf Fortress supports mods in the form of new objects and tiles. Each mod is a zip file or unzipped folder with the required format (see below.)

=== Mod Format===

Mods contain an info.txt file and either an "objects" folder or a "graphics" folder (or both.) All of the vanilla objects in the game too use this format. Your mod folder should look something like this:

[[File:Folder-orange.svg|20px|link=]] Mod Name
├ [[File:Text-x-generic.svg|20px|link=]] info.txt
├ [[File:Text-x-generic.svg|20px|link=]] preview.png
├ [[File:Folder.svg|20px|link=]] objects
└ [[File:Folder.svg|20px|link=]] graphics

=== Mod info ===
{{main|Mod info token}}

Each mod must have a <code>info.txt</code> at the root of your mod folder. It has a few fields defining basic metadata information about the mod and can be edited using any text editor (like notepad++). See Example:

{{code|
[ID:wiki_example]
[NAME:Wiki Example Mod]
[NUMERIC_VERSION:5001]
[DISPLAYED_VERSION:50.01]
[EARLIEST_COMPATIBLE_NUMERIC_VERSION:5001]
[EARLIEST_COMPATIBLE_DISPLAYED_VERSION:50.01]
[AUTHOR:Dwarf Fortress Wiki]
[DESCRIPTION:This is an example mod. This text shows up in-game.]

[STEAM_TITLE:Wiki Example Mod]
[STEAM_DESCRIPTION:This text shows up on Steam Workshop.]
[STEAM_TAG:mod]
[STEAM_KEY_VALUE_TAG:test:stuff]
[STEAM_METADATA:metadata test]
[STEAM_CHANGELOG:Made some changes. Shown in 'Change Notes' tab.]

[STEAM_FILE_ID:#########]
}}

Only <code>ID</code> and <code>NAME</code> are required to appear in the in-game mod menu.

STEAM tags are only used by Steam.
* The <code>STEAM_FILE_ID</code> used to identify the mod in the Workshop. This is automatically managed when uploading to Steam the first time. And required if you wish to update an existing Steam Workshop mod.
* The <code>STEAM_TAG</code> and <code>STEAM_KEY_VALUE_TAG</code> are used by Steams search engine and the categorization. You can use as many entries you want, use a separate tag for each one.
* You can also create a thumbnail for your mod by creating an image called <code>preview.png</code> in the same level as your info.txt file. This image will become the thumbnail when the mod is uploaded to steam workshop. The image should be less than 1MB in size.

=== Objects and graphics folder ===

At the root of your mod folder you can have a <code>objects\</code> and <code>graphics\</code> folder, this is where all the [[raw file]]s or [[graphics]] goes (exactly the same as objects from previous versions of Dwarf Fortress) allowing you to tweak or add new content for the game. It's beyond the scope of this short guide to go into what specific tags do, but the vanilla objects and previous mods by members of the community will give you plenty of examples to work with. See: [[modding]].

The filenames of these files are not important, furthermore they can be arbitrarily nested into other sub-folders to help you organize your mod content.

== Publishing mods ==

There are two official platforms for publishing ''Dwarf Fortress'' mods, recommended because it's easy for people to find them there. These are [https://steamcommunity.com/app/975370/workshop/ Steam Workshop] and [https://dffd.bay12games.com/ the Dwarf Fortress File Depot (DFFD)].

=== Publishing on Steam Workshop ===

To upload a mod to Steam Workshop, you need to add STEAM tags to the <code>info.txt</code> file (see above.) Afterward, you put the unzipped mod folder in the "<code>mods/mod_upload</code>" folder. Then select Mods from the title menu, and upload your mods using the button you'll see there. Other Steam users will be able to subscribe to your mod immediately once it is uploaded.

Once the upload process is completed successfully, you'll find a <code>[STEAM_FILE_ID:#########]</code> appended to your info.txt. Make sure this entry is included for future uploads if you want to make changes to your mod and have it overwrite the existing entry on the workshop. Otherwise you'll create a new entry every time you upload.

=== Publishing on DFFD ===

In addition to Steam Workshop, it is recommended you upload your mod to DFFD. This allows people who play ''[[Classic|Dwarf Fortress Classic]]'', or ''[[Premium]]'' via Itch.io, to also download and play your mod. To publish/upload a file to DFFD you first need to create an account.

For legal reasons, mods that contain graphics derived from the ''Premium'' graphics should not be uploaded outside Steam Workshop. For this reason, you might want to separate your mod into two parts: the first without graphics, which is uploaded to both DFFD and Steam Workshop, and the second with ''only'' the graphics, uploaded only to Workshop. Of course, this is not an issue if your graphics are not based off the ''Premium'' ones.

[[Category:Modding]]

Mod

2023-01-05T19:36:29Z

Jan: added new section for updating mods

{{For/see|using mods and their basic structure|[[modding]] about making mods}}

A '''mod''' (short for modification) is an alteration of the game and the objective of modding. Modifications can range from small tweaks to complete overhauls.

== Installing Mods ==

Mods can be acquired using the [https://steamcommunity.com/app/975370/workshop/ steam workshop] (if using Steam version), a manual download from [[Bay 12 Forums]] or third party websites (like [https://dffd.bay12games.com/ DFFD]), or by [[Modding|creating]] one yourself.

Users of the Steam version can subscribe to mods on Steam Workshop, once the download is complete they will be available when creating a new world automatically. Otherwise, manually download the mod, then place the mod zip file or the unzipped mod folder into the Dwarf Fortress [[mod folder]] (if this folder doesn't exist, you can create it.) You can have more than one mod in the mod folder, including different version of the same mod. The game will detect all mods that are properly made in this folder and let the user select which mods to play (see bellow.)

== Enabling Mods ==
[[File:Ui-p-mod-selection.png|thumb|world generation mod menu]]

When [[World generation|creating a world]] and choosing its initial parameters, if you have a mod available, there should be a '''Mods''' button at the bottom of the screen. Pressing this will let you select which mods you'd like to enable and what the load order should be. You should put mods at the end of the mod list after the vanilla objects if you don't have any further information, so that they can reference vanilla objects after those are loaded.

Something something load order basic

<div class="" style="padding: 0.8em 1em; margin: 0.5rem 0; background: #fcf8e3; border-left: 5px solid #aa6708;">
* Mods are enabled per world and can not be disabled afterwards, however, it is possibly to manually modify the game file as we did in previous versions by applying the mods directly to <code>[[Game folder|<Dwarf Fortress>]]/data/vanilla</code>. Be ware this method has the disadvantage of being a permanent change for all worlds and may break your game.

* Unlike the previous versions of Dwarf Fortress, mods no longer live inside save files and must be installed on every computer where saves using those mods are going to be loaded. Once a world is created that uses mods, then the game will copy the mod to the <code>[[Game folder|<Dwarf Fortress>]]/data/installed_mods</code> folder. That is the version that the game actually uses.
</div>

== Updating Mods ==
If a world is using a mod that's been updated, and is currently using an older version of that mod, the player will be prompted about this when a save is loading. Causing a message like the following to appear: 
[[File:mod_version_v50_prompt.png]]

When this happens, you have the choice of simply updating the mod, updating ''all'' mods at once, continuing to use the older version of the mod in question without updating, selecting the previous task but not updating ''any'' possibly outdated mods or simply returning to the title screen.

== Modding ==

Dwarf Fortress supports mods in the form of new objects and tiles. Each mod is a zip file or unzipped folder with the required format (see below.)

=== Mod Format===

Mods contain an info.txt file and either an "objects" folder or a "graphics" folder (or both.) All of the vanilla objects in the game too use this format. Your mod folder should look something like this:

[[File:Folder-orange.svg|20px|link=]] Mod Name
├ [[File:Text-x-generic.svg|20px|link=]] info.txt
├ [[File:Text-x-generic.svg|20px|link=]] preview.png
├ [[File:Folder.svg|20px|link=]] objects
└ [[File:Folder.svg|20px|link=]] graphics

=== Mod info ===
{{main|Mod info token}}

Each mod must have a <code>info.txt</code> at the root of your mod folder. It has a few fields defining basic metadata information about the mod and can be edited using any text editor (like notepad++). See Example:

{{code|
[ID:wiki_example]
[NAME:Wiki Example Mod]
[NUMERIC_VERSION:5001]
[DISPLAYED_VERSION:50.01]
[EARLIEST_COMPATIBLE_NUMERIC_VERSION:5001]
[EARLIEST_COMPATIBLE_DISPLAYED_VERSION:50.01]
[AUTHOR:Dwarf Fortress Wiki]
[DESCRIPTION:This is an example mod. This text shows up in-game.]

[STEAM_TITLE:Wiki Example Mod]
[STEAM_DESCRIPTION:This text shows up on Steam Workshop.]
[STEAM_TAG:mod]
[STEAM_KEY_VALUE_TAG:test:stuff]
[STEAM_METADATA:metadata test]
[STEAM_CHANGELOG:Made some changes. Shown in 'Change Notes' tab.]

[STEAM_FILE_ID:#########]
}}

Only <code>ID</code> and <code>NAME</code> are required to appear in the in-game mod menu.

STEAM tags are only used by Steam.
* The <code>STEAM_FILE_ID</code> used to identify the mod in the Workshop. This is automatically managed when uploading to Steam the first time. And required if you wish to update an existing Steam Workshop mod.
* The <code>STEAM_TAG</code> and <code>STEAM_KEY_VALUE_TAG</code> are used by Steams search engine and the categorization. You can use as many entries you want, use a separate tag for each one.
* You can also create a thumbnail for your mod by creating an image called <code>preview.png</code> in the same level as your info.txt file. This image will become the thumbnail when the mod is uploaded to steam workshop. The image should be less than 1MB in size.

=== Objects and graphics folder ===

At the root of your mod folder you can have a <code>objects\</code> and <code>graphics\</code> folder, this is where all the [[raw file]]s or [[graphics]] goes (exactly the same as objects from previous versions of Dwarf Fortress) allowing you to tweak or add new content for the game. It's beyond the scope of this short guide to go into what specific tags do, but the vanilla objects and previous mods by members of the community will give you plenty of examples to work with. See: [[modding]].

The filenames of these files are not important, furthermore they can be arbitrarily nested into other sub-folders to help you organize your mod content.

== Publishing mods ==

There are two official platforms for publishing ''Dwarf Fortress'' mods, recommended because it's easy for people to find them there. These are [https://steamcommunity.com/app/975370/workshop/ Steam Workshop] and [https://dffd.bay12games.com/ the Dwarf Fortress File Depot (DFFD)].

=== Publishing on Steam Workshop ===

To upload a mod to Steam Workshop, you need to add STEAM tags to the <code>info.txt</code> file (see above.) Afterward, you put the unzipped mod folder in the "<code>mods/mod_upload</code>" folder. Then select Mods from the title menu, and upload your mods using the button you'll see there. Other Steam users will be able to subscribe to your mod immediately once it is uploaded.

Once the upload process is completed successfully, you'll find a <code>[STEAM_FILE_ID:#########]</code> appended to your info.txt. Make sure this entry is included for future uploads if you want to make changes to your mod and have it overwrite the existing entry on the workshop. Otherwise you'll create a new entry every time you upload.

=== Publishing on DFFD ===

In addition to Steam Workshop, it is recommended you upload your mod to DFFD. This allows people who play ''[[Dwarf Fortress Classic]]'', or ''[[Premium]]'' via Itch.io, to also download and play your mod. To publish/upload a file to DFFD you first need to create an account.

For legal reasons, mods that contain graphics derived from the ''Premium'' graphics should not be uploaded outside Steam Workshop. For this reason, you might want to separate your mod into two parts: the first without graphics, which is uploaded to both DFFD and Steam Workshop, and the second with ''only'' the graphics, uploaded only to Workshop. Of course, this is not an issue if your graphics are not based off the ''Premium'' ones.

[[Category:Modding]]

Talk:Mod info token

2023-01-05T19:32:41Z

Jan: /* Required */ new section

== token? ==

Not sure this is a Token in the sense the term is used in game. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 21:13, 21 December 2022 (UTC)

:The wiki also has the [[world token]]s which similarly represent something other than raw objects. I think it is more about the format than anything, and afaik "token" is not a term ever used in-game. The closest we get is the [[creature variation token]]s which call them "tag"s. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 21:21, 21 December 2022 (UTC)
:: All setting files use the same format, but we don't say [[init.txt]] tokens. In this case I'd prefer simply 'Mod info' but I am fine either way. There gonna be some trail and error for awhile. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 22:54, 21 December 2022 (UTC)
:: Btw there is no longer 'raw' folder, now it is 'vanilla' --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 23:10, 21 December 2022 (UTC)

== Required ==

I am not sure all the fields marked as required fields indeed are. When I last run a test I used mod_info text with just an ID and NAME and it worked.
<pre>[ID:wiki_example]
[NAME:Wiki Example Mod]</pre>
--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 19:32, 5 January 2023 (UTC)

The Non-Dwarf's Guide to Rock

2023-01-05T19:27:36Z

Jan: used wikitable and tidied up, sorting should work now

{{migrated article}}
{{Quality|Unrated}}
{{av}}

Wondering what that new kind of rock your dwarves just struck is good for? Possibly nothing, but when you're just getting started it can be tough to tell the trash from the treasure. The following table summarizes the types of stone and ore found in Dwarf Fortress; [[gem]]s are covered in their own article.

The ''Uses'' column lists any special uses or properties of this particular stone type; if no uses are listed, you can always use the stone for general construction and crafting. Note that many "low-value" materials are still ''very'' useful in a fortress. "Colors" are useful for color coding or [[style project|creative aesthetic uses]].

For more detailed and expanded information, see the [[Stone]], [[Ore]], [[Metal|Metals & Alloys]], [[Vein|Veins & Clusters]], and [[Smelting]] pages, or the article on any particular stone, metal or ore.

During the game, you can press {{key|z}} and then navigate to "stone". The list there covers all types of rocks and ores, and tells you what rocks can be smelted into.

==Table of Rocks==

''(Some materials are worth an additional comment; these are numbered, with footnotes below the table.)''

{| class="wikitable sortable" border = 1 cellspacing="0" cellpadding="5"
! Name
! Type
! Uses
! class="unsortable"|Appearance (ASCII)*
! class="unsortable"|Color (Tileset)
|-
| [[Raw adamantine|Adamantine, raw]]||ore, special1, spoilerry||Becomes [[Adamantine]]1 (spoilers!), by far the most valuable substance||{{Raw Tile|£|3:7:1}} {{Raw Tile|*|3:1}}||[[File:Raw adammantineSwatch.png|64px|center]]
|-
| [[Alabaster]]||stone||Low-value stone; used for making [[plaster]]||{{Raw Tile|^|7:7:1}} {{Raw Tile|•|7:1}}||[[File:AlabasterSwatch.png|64px|center]]
|-
| [[Native aluminum|Aluminum, native]]||ore, high-value||Smelt into [[Aluminum]], a high-value decorative [[metal]]||{{Raw Tile|^|7:7:1}} {{Raw Tile|*|7:1}}||[[File:NativeAluminumSwatch.png|64px|center]]
|-
| [[Alunite]]||stone||Low-value [[magma-safe]] stone||{{Raw Tile|`|7:7:1}} {{Raw Tile|•|7:1}}||[[File:AluniteSwatch.png|64px|center]]
|-
| [[Andesite]]||layer stone||Low-value stone||{{Raw Tile|∞|0:7:1}} {{Raw Tile|•|0:1}}||[[File:AndesiteSwatch.png|64px|center]]
|-
| [[Anhydrite]]||stone||Low-value [[magma-safe]] stone||{{Raw Tile|v|7:7:1}} {{Raw Tile|•|7:0}}||[[File:AnhydriteSwatch.png|64px|center]]
|-
| [[Basalt]]||layer stone||Low-value [[magma-safe]] stone||{{Raw Tile|#|0:7:1}} {{Raw Tile|•|0:1}}||[[File:BasaltSwatch.png|64px|center]]
|-
| [[Bauxite]]||stone||Low-value [[magma-safe]] stone; only source of some high-value gems||{{Raw Tile|+|4:7:0}} {{Raw Tile|•|4:0}}||[[File:BauxiteSwatch.png|64px|center]]
|-
| [[Bismuthinite]]||ore, rare||Smelt into [[bismuth]], ingredient of [[bismuth bronze]]||{{Raw Tile|%|7:7:1}} {{Raw Tile|*|7:0}}||[[File:BismuthiniteSwatch.png|64px|center]]
|-
| [[Bituminous coal]]||stone||Smelt into [[Fuel]], flammable||{{Raw Tile|☼|0:7:1}} {{Raw Tile|☼|0:1}}||[[File:Bituminous coalSwatch.png|64px|center]]
|-
| [[Borax]]||stone||Low-value stone||{{Raw Tile|`|7:7:1}} {{Raw Tile|•|7:1}}||[[File:BoraxSwatch.png|64px|center]]
|-
| [[Brimstone]]||stone||Low-value stone||{{Raw Tile|%|6:7:1}} {{Raw Tile|•|6:1}}||[[File:BrimstoneSwatch.png|64px|center]]
|-
| [[Calcite]]||stone||[[Flux]], mid-value [[magma-safe]] stone||{{Raw Tile|"|7:7:1}} {{Raw Tile|•|7:1}}||[[File:CalciteSwatch.png|64px|center]]
|-
| [[Cassiterite]]||ore, uncommon||Smelt into [[Tin]], a low-value metal; ingredient of [[Bronze]]s; [[magma-safe]]||{{Raw Tile|£|6:7:0}} {{Raw Tile|*|6:0}}||[[File:CassiteriteSwatch.png|64px|center]]
|-
| [[Chalk]]||layer stone||[[Flux]], mid-value stone||{{Raw Tile|░|7:7:1}} {{Raw Tile|•|7:1}}||[[File:ChalkSwatch.png|64px|center]]
|-
| [[Chert]]||layer stone|| Low-value [[magma-safe]] stone||{{Raw Tile|=|6:7:0}} {{Raw Tile|•|6:0}}||[[File:ChertSwatch.png|64px|center]]
|-
| [[Chromite]]||stone||Low-value [[magma-safe]] stone||{{Raw Tile|=|0:7:1}} {{Raw Tile|•|0:1}}||[[File:ChromiteSwatch.png|64px|center]]
|-
| [[Cinnabar]]||stone||Low-value stone||{{Raw Tile|£|4:7:1}} {{Raw Tile|*|4:1}}||[[File:CinnabarSwatch.png|64px|center]]
|-
| [[Claystone]]||layer stone||Low-value stone||{{Raw Tile|,|0:7:1}} {{Raw Tile|•|0:1}}||[[File:ClaystoneSwatch.png|64px|center]]
|-
| [[Cobaltite]]||stone||Low-value stone||{{Raw Tile|£|1:7:1}} {{Raw Tile|*|1:1}}||[[File:CobaltiteSwatch.png|64px|center]]
|-
| [[Conglomerate]]||layer stone||Low-value stone||{{Raw Tile|∞|6:7:0}} {{Raw Tile|•|6:0}}||[[File:ConglomerateSwatch.png|64px|center]]
|-
| [[Native copper|Copper, native]]||ore, low-value||Smelt into useful [[Copper]]; ingredient of [[Bronze]]s||{{Raw Tile|£|6:7:0}} {{Raw Tile|*|6:0}}||[[File:NativeCopperSwatch.png|64px|center]]
|-
| [[Cryolite]]||stone||Low-value stone||{{Raw Tile|-|7:7:1}} {{Raw Tile|•|7:1}}||[[File:CryoliteSwatch.png|64px|center]]
|-
| [[Dacite]]||layer stone||Low-value stone||{{Raw Tile|.|0:7:1}} {{Raw Tile|•|7:0}}||[[File:DaciteSwatch.png|64px|center]]
|-
| [[Diorite]]||layer stone||Low-value stone||{{Raw Tile|░|0:7:1}} {{Raw Tile|•|0:1}}||[[File:DioriteSwatch.png|64px|center]]
|-
| [[Dolomite]]||layer stone||[[Flux]], mid-value [[magma-safe]] stone||{{Raw Tile|`|7:7:1}} {{Raw Tile|•|7:1}}||[[File:DolomiteSwatch.png|64px|center]]
|-
| [[Gabbro]]||layer stone||Low-value [[magma-safe]] stone; only source of some [[ore]]s & [[gem]]s||{{Raw Tile|▒|0:7:1}} {{Raw Tile|•|0:1}}||[[File:GabbroSwatch.png|64px|center]]
|-
| [[Galena]]||ore||Smelt into [[Lead]], a low-value metal, with a 50% chance2 for [[Silver]]; [[magma-safe]]||{{Raw Tile|£|7:7:1}} {{Raw Tile|*|7:1}}||[[File:GalenaSwatch.png|64px|center]]
|-
| [[Garnierite]]||ore, uncommon||Smelt into [[Nickel]], a low-value [[magma-safe]] metal ||{{Raw Tile|£|2:7:1}} {{Raw Tile|*|2:1}}||[[File:GarnieriteSwatch.png|64px|center]]
|-
| [[Gneiss]]||layer stone||Low-value stone||{{Raw Tile|=|7:7:1}} {{Raw Tile|•|7:0}}||[[File:GneissSwatch.png|64px|center]]
|-
| [[Native gold|Gold, native]]||ore||Smelt into [[Gold]], a high-value [[metal]]||{{Raw Tile|£|6:7:1}} {{Raw Tile|*|6:1}}||[[File:NativeGoldSwatch.png|64px|center]]
|-
| [[Granite]]||layer stone||Low-value stone; only source of some ores; relatively rich in content||{{Raw Tile|▓|7:0}} {{Raw Tile|•|7:0}}||[[File:GraniteSwatch.png|64px|center]]
|-
| [[Graphite]]||stone||Low-value stone, flammable||{{Raw Tile|o|0:7:1}} {{Raw Tile|•|0:1}}||[[File:GraphiteSwatch.png|64px|center]]
|-
| [[Gypsum]]||stone||Low-value stone; used for making [[plaster]]||{{Raw Tile|#|6:7:1}} {{Raw Tile|•|6:1}}||[[File:GypsumSwatch.png|64px|center]]
|-
| [[Hematite]]||ore||Smelt into [[Iron]], a mid-value metal; ingredient for [[Steel]]; [[magma-safe]]||{{Raw Tile|£|4:7:0}} {{Raw Tile|*|4:0}}||[[File:HematiteSwatch.png|64px|center]]
|-
| [[Horn silver]]||ore||Smelt into [[Silver]], a mid-value metal||{{Raw Tile|£|7:7:1}} {{Raw Tile|*|7:1}}||[[File:HornSilverSwatch.png|64px|center]]
|-
| [[Hornblende]]||stone||Low-value stone||{{Raw Tile|"|0:7:1}} {{Raw Tile|•|0:1}}||[[File:HornblendeSwatch.png|64px|center]]
|-
| [[Ilmenite]]||stone||Low-value [[magma-safe]] stone||{{Raw Tile|.|0:7:1}} {{Raw Tile|•|0:1}}||[[File:IlmeniteSwatch.png|64px|center]]
|-
| [[Ice]]3||stone/water3||Frozen Water||{{Raw Tile|█|3:3:1}} {{Raw Tile|•|3:1}}||[[File:IceSwatch.png|64px|center]]
|-
| [[Jet]]||stone||Low-value stone||{{Raw Tile|░|0:7:1}} {{Raw Tile|•|0:1}}||[[File:JetSwatch.png|64px|center]]
|-
| [[Kaolinite]]||stone||Low-value [[magma-safe]] stone; used for making [[porcelain]]||{{Raw Tile|=|4:7:0}} {{Raw Tile|•|4:0}}||[[File:KaoliniteSwatch.png|64px|center]]
|-
| [[Kimberlite]]||stone|| Low-value stone; only source of [[Faint yellow diamond|diamond]]s||{{Raw Tile|%|1:7:0}} {{Raw Tile|•|1:0}}||[[File:KimberliteSwatch.png|64px|center]]
|-
| [[Lignite]]||stone||Smelt into [[Fuel]], flammable||{{Raw Tile|*|0:7:1}} {{Raw Tile|•|0:1}}||[[File:LigniteSwatch.png|64px|center]]
|-
| [[Limestone]]||layer stone||[[Flux]], mid-value stone||{{Raw Tile|▓|7:7:1}} {{Raw Tile|•|7:1}}||[[File:LimestoneSwatch.png|64px|center]]
|-
| [[Limonite]]||ore, high-value||Smelt into [[Iron]], a mid-value metal; ingredient for [[Steel]]||{{Raw Tile|£|6:7:1}} {{Raw Tile|*|6:1}}||[[File:LimoniteSwatch.png|64px|center]]
|-
| [[Magnetite]]||ore, high-value||Smelt into [[Iron]], a mid-value metal; ingredient for [[Steel]]; [[magma-safe]]||{{Raw Tile|~|0:7:1}} {{Raw Tile|*|0:1}}||[[File:MagnetiteSwatch.png|64px|center]]
|-
| [[Malachite]]||ore, low-value||Smelt into useful [[Copper]]; ingredient of [[Bronze]]s||{{Raw Tile|£|2:7:0}} {{Raw Tile|*|2:0}}||[[File:MalachiteSwatch.png|64px|center]]
|-
| [[Marble]]||layer stone||[[Flux]], mid-value stone||{{Raw Tile|▓|7:7:1}} {{Raw Tile|•|7:1}}||[[File:MarbleSwatch.png|64px|center]]
|-
| [[Marcasite]]||stone||Low-value stone||{{Raw Tile|%|7:7:1}} {{Raw Tile|•|7:1}}||[[File:MarcasiteSwatch.png|64px|center]]
|-
| [[Mica]]||stone||Low-value [[magma-safe]] stone||{{Raw Tile|v|0:7:1}} {{Raw Tile|•|0:1}}||[[File:MicaSwatch.png|64px|center]]
|-
| [[Microcline]]||stone||Low-value stone||{{Raw Tile|%|3:7:1}} {{Raw Tile|•|3:1}}||[[File:MicroclineSwatch.png|64px|center]]
|-
| [[Mudstone]]||layer stone||Low-value stone||{{Raw Tile|≈|6:7:0}} {{Raw Tile|•|6:0}}||[[File:MudstoneSwatch.png|64px|center]]
|-
| [[Obsidian]]||layer stone||High-value [[magma-safe]] stone;Sharpenable hard rock (used to create stone [[short sword]]s); signifies nearby [[magma]] if not a layer||{{Raw Tile|▒|0:7:1}} {{Raw Tile|•|0:1}}||[[File:ObsidianSwatch.png|64px|center]]
|-
| [[Olivine]]||stone||Low-value [[magma-safe]] stone; may contain [[Platinum]]||{{Raw Tile|%|2:7:0}} {{Raw Tile|•|2:0}}||[[File:OlivineSwatch.png|64px|center]]
|-
| [[Orpiment]]||stone||Low-value stone||{{Raw Tile|-|6:7:1}} {{Raw Tile|•|6:1}}||[[File:OrpimentSwatch.png|64px|center]]
|-
| [[Orthoclase]]||stone||Low-value [[magma-safe]] stone||{{Raw Tile|%|6:7:1}} {{Raw Tile|•|6:1}}||[[File:OrthoclaseSwatch.png|64px|center]]
|-
| [[Periclase]]||stone||Low-value [[magma-safe]] stone||{{Raw Tile|,|7:7:1}} {{Raw Tile|•|7:1}}||[[File:PericlaseSwatch.png|64px|center]]
|-
| [[Petrified wood]]||stone||Low-value [[magma-safe]] stone||{{Raw Tile|%|4:7:1}} {{Raw Tile|•|4:1}}||[[File:Petrified woodSwatch.png|64px|center]]
|-
| [[Phyllite]]||layer stone||Low-value stone||{{Raw Tile|-|0:7:1}} {{Raw Tile|•|7:0}}||[[File:PhylliteSwatch.png|64px|center]]
|-
| [[Pitchblende]]||stone||Low-value [[magma-safe]] stone||{{Raw Tile|*|5:7:0}} {{Raw Tile|•|5:0}}||[[File:PitchblendeSwatch.png|64px|center]]
|-
| [[Native platinum|Platinum, native]]||ore, high-value||Smelt into [[Platinum]], a highest-value decorative [[metal]]||{{Raw Tile|£|7:7:1}} {{Raw Tile|*|7:1}}||[[File:NativePlatinumSwatch.png|64px|center]]
|-
| [[Puddingstone]]||stone|| Low-value stone||{{Raw Tile|Θ|6:7:0}} {{Raw Tile|•|6:0}}||[[File:PuddingstoneSwatch.png|64px|center]]
|-
| [[Pyrolusite]]||stone||Low-value stone||{{Raw Tile|%|0:7:1}} {{Raw Tile|•|0:1}}||[[File:PyrolusiteSwatch.png|64px|center]]
|-
| [[Quartzite]]||layer stone||Low-value [[magma-safe]] stone||{{Raw Tile|-|7:7:1}} {{Raw Tile|•|7:1}}||[[File:QuartziteSwatch.png|64px|center]]
|-
| [[Realgar]]||stone||Low-value stone||{{Raw Tile|%|4:7:1}} {{Raw Tile|•|4:1}}||[[File:RealgarSwatch.png|64px|center]]
|-
| [[Rhyolite]]||layer stone||Low-value stone||{{Raw Tile|,|0:7:1}} {{Raw Tile|•|0:1}}||[[File:RhyoliteSwatch.png|64px|center]]
|-
| [[Rock salt]]||layer stone||Low-value stone||{{Raw Tile|#|7:7:1}} {{Raw Tile|•|7:1}}||[[File:Rock saltSwatch.png|64px|center]]
|-
| [[Rutile]]||stone||Low-value [[magma-safe]] stone||{{Raw Tile|`|5:7:0}} {{Raw Tile|•|5:0}}||[[File:RutileSwatch.png|64px|center]]
|-
| [[Saltpeter]]||stone||Low-value stone||{{Raw Tile|x|6:7:1}} {{Raw Tile|•|6:1}}||[[File:SaltpeterSwatch.png|64px|center]]
|-
| [[Sandstone]]||layer stone||Low-value [[magma-safe]] stone||{{Raw Tile|#|6:7:0}} {{Raw Tile|•|6:0}}||[[File:SandstoneSwatch.png|64px|center]]
|-
| [[Satinspar]]||stone||Low-value stone; used for making [[plaster]]||{{Raw Tile|-|7:7:1}} {{Raw Tile|•|7:1}}||[[File:SatinsparSwatch.png|64px|center]]
|-
| [[Schist]]||layer stone||Low-value stone||{{Raw Tile|`|6:7:0}} {{Raw Tile|•|6:0}}||[[File:SchistSwatch.png|64px|center]]
|-
| [[Selenite]]||stone||Low-value stone; used for making [[plaster]]||{{Raw Tile|;|7:7:1}} {{Raw Tile|•|7:1}}||[[File:SeleniteSwatch.png|64px|center]]
|-
| [[Serpentine]]||stone||Low-value stone||{{Raw Tile|≈|2:7:0}} {{Raw Tile|•|2:0}}||[[File:SerpentineSwatch.png|64px|center]]
|-
| [[Shale]]||layer stone||Low-value stone||{{Raw Tile|.|0:7:1}} {{Raw Tile|•|0:1}}||[[File:ShaleSwatch.png|64px|center]]
|-
| [[Siltstone]]||layer stone||Low-value stone||{{Raw Tile|%|6:7:0}} {{Raw Tile|•|6:0}}||[[File:SiltstoneSwatch.png|64px|center]]
|-
| [[Native silver|Silver, native]]||ore||Smelt into [[Silver]], a mid-value metal||{{Raw Tile|£|7:7:1}} {{Raw Tile|*|7:1}}||[[File:NativeSilverSwatch.png|64px|center]]
|-
| [[Slade]]||stone, special||Not workable by dwarves||{{Raw Tile|░|0:1}} {{Raw Tile|*|0:1}}||[[File:SladeSwatch.png|64px|center]]
|-
| [[Slate]]||layer stone||Low-value stone||{{Raw Tile|%|0:7:1}} {{Raw Tile|•|0:1}}||[[File:SlateSwatch.png|64px|center]]
|-
| [[Sphalerite]]||ore, uncommon||Smelt into [[Zinc]], a low-value metal; ingredient for [[Brass]]||{{Raw Tile|£|0:7:1}} {{Raw Tile|*|0:1}}||[[File:SphaleriteSwatch.png|64px|center]]
|-
| [[Stibnite]]||stone||Low-value stone||{{Raw Tile|%|7:7:1}} {{Raw Tile|•|7:1}}||[[File:StibniteSwatch.png|64px|center]]
|-
| [[Sylvite]]||stone||Low-value stone||{{Raw Tile|=|6:7:1}} {{Raw Tile|•|6:1}}||[[File:SylviteSwatch.png|64px|center]]
|-
| [[Talc]]||stone||Low-value [[magma-safe]] stone||{{Raw Tile|||7:7:1}} {{Raw Tile|•|7:1}}||[[File:TalcSwatch.png|64px|center]]
|-
| [[Tetrahedrite]]||ore, low-value||Smelt into useful [[Copper]]; ingredient of [[Bronze]]s; has a 20% additional chance2 of [[Silver]]; smelt into [[Billon]]||{{Raw Tile|£|0:7:1}} {{Raw Tile|*|0:1}}||[[File:TetrahedriteSwatch.png|64px|center]]
|}

:''(* Each stone is one of 16 [[color scheme|colors]] in the game. Different un-mined stone of the same color have a different symbol to distinguish between them. Once mined, the individual stones themselves can sometimes look identical if the color is the same. Use {{k|k}} to loo{{k|k}} at items or the terrain for specific information.)''

'''Notes:'''
# '''Adamantine''' is not exactly like other metals, although it works almost the same. It has a value multiplier of x300 (yes, three ''hundred''). See (spoilers!) [[adamantine]] for a full discussion of this unusual and wondrous material.
# '''% chance''' for additional metals: when [[Galena]] and [[Tetrahedrite]] are smelted, they produce (respectively) four lead or copper bars, 100% of the time. They also produce 0-4 ''additional'' bars of the second metal, with the percent chance to produce each additional bar listed above.
# '''Ice''' has some ''very'' unusual properties in ''Dwarf Fortress'', and can be disastrous if misused. See the article on [[ice]] for a more complete discussion.

===The Value of Rocks & Metals===
You won't find the terms "low-value" or "highest-value" used in the game, but they're handy here for rough comparison. "[[Value]]s" are all relative to each other, on a common scale. The "material value" number multiplies any final product that is created with that material by that number. An average generic statue (base value 25) is worth much more than an average generic throne (base value 10), but a throne carved from raw [[native gold|gold nuggets]] (10 x 30 = 300) will be worth far more than a common-stone statue (25 x 1 = 25). ''(Note - "[[quality]]" also factors into total value of a final product, as do some other considerations, but those are outside the scope of this intro article).'' Bottom line - when in doubt, go for the more valuable stuff.

Common '''stones''' ''(the vast majority)'' have a value multiplier of x1, mid-value ''(all [[flux]] stones like marble)'' are x2, and high-value ''([[obsidian]] only)'' is x3. This affects things like stone tables and doors, statues or stonecrafts - anything made from stone. Metal [[ore]]s have varying values, from 2-40, and can either be treated as stone or smelted into bars of metal.

For '''metals''', low-value ''(like copper or nickel)'' is x2. Mid-value ''(silver or iron)'' is around x10, high-value ''(gold, steel)'' is x30, and highest-value ''(platinum, aluminum)'' is x40.

Note that the raw mined ore and the smelted pure metal often have different value multipliers, but not always. [[Alloy]]s like brass or bronze are often more valuable than the sum of their pure metal ingredients, and have a true spectrum of values between 3-23. ''(Alloy values are not listed in this article.)''

Any metal can be crafted into decorations, furniture, or buildings. Only copper, bronzes, iron, steel, and adamantine can make weapons, armor, and picks, with silver also able to be forged into melee weapons.

''(For comparison, all [[wood]] has a value of x1, equal to common stone.)''



See also:
:* [[Exploratory mining]]

{{Category|Guides}}{{Category|Stone|0}}
[[ru:The Non-Dwarf's Guide to Rock]]

Sedimentary layer

2023-01-05T19:22:30Z

Jan:

{{migrated article}}
{{av}}{{Quality|Unrated}}
[[File:Layers of sedimentary rock in Makhtesh Ramon (50749).jpg|thumb|310px|right|Layers of sedimentary rock in Makhtesh Ramon.]]
'''Sedimentary''' [[stone layers]] contain [[hematite]], [[limonite]], [[magnetite]], [[tetrahedrite]], [[bituminous coal]], [[lignite]], and [[gypsum]]. [[Chalk]]*, [[chert]]**, [[claystone]], [[conglomerate]], [[dolomite]]**, [[limestone]]*, [[mudstone]], [[rock salt]], [[sandstone]]**, [[siltstone]] and [[shale]] layers are sedimentary.
:(* These also function as [[flux]]. **These are also [[magma-safe]].)

Sedimentary layers are, on average, the most economically valuable of the four [[stone layers]]. They are your only source of [[bituminous coal]] and [[lignite]], vital for fueling non-[[magma]] forges and for the [[coke]] that [[steel]]-making requires (especially if you lack [[tree]]s). They are much richer in [[iron]] [[ore]]s than other rock formations. Several sedimentary rocks - [[dolomite]], [[chalk]], and [[limestone]] - are [[flux]]es, required for [[steel]]-making and also being twice as valuable as normal stone, making them useful for [[crafts|trade goods]] or [[furniture]].

Sedimentary layers can be tricky to locate. If you are starting off, and you want access to an embark area with sedimentary layers, use the "Find Desirable Location" function before embark and set your parameters to include sites with [[flux]] stone. Since most flux stones are found in sedimentary layers, this will increase your chances that a suitable site will have sedimentary rock near the surface. Be careful when using the "Find Desirable Location" function, as it will sometimes list green sites that have flux stone but not indicate that it does, actually, have flux stone. To find iron ores, search for a location that has shallow metals, flux stone, medium elevation, and either high or low drainage. On large maps, the ore is sometimes located near mountains and major rivers in large (min ~10x10) chunks.

Alternatively, a [[mountain]] biome that has an [[aquifer]] is guaranteed to be sedimentary as well, due to mountains lacking soil, which means the aquifer must be in sedimentary layers.

If your [[Embark#Changing_Views|embark civilization]] has access to sedimentary layer stones [[Embark#Prepare_Carefully|when preparing]], it is likely one or more of the biomes in their sites overlap a biome containing it.

(In real-world geology, sedimentary [[stone]] is formed by sediment. The sediment gets carried away by rivers and deposited in constantly growing heaps, where the pressure at the bottom eventually forms the sediment into stone.)

==Sedimentary layers==
{{Layerlookup/layers|SEDIMENTARY}}

==Stone found in sedimentary layers==
{{Layerlookup/stones|SEDIMENTARY}}

==Gems found in sedimentary layers==
{{Layerlookup/gems|SEDIMENTARY}}

* See also: [[stone found everywhere]]

{{stones}}
{{Category|Stone Layers}}
[[ru:Sedimentary layer]]

Igneous intrusive layer

2023-01-05T19:22:03Z

Jan:

{{migrated article}}
{{Quality|Unrated}}
{{av}}
[[File:igneous_intrusive_layer.jpg|thumb|300px|right|Created from rocks that have crystallized from the heat of magma.]]
'''Igneous intrusive''' [[stone layers]] can consist of [[granite]], [[diorite]], or [[gabbro]], all of which typically contain [[gold]] and [[tetrahedrite]].

Gabbro can also contain [[garnierite]] (the ore of [[nickel]]), [[kimberlite]] (which may contain [[diamond]]s), and [[olivine]] (which may contain [[native platinum]]). Granite can contain [[cassiterite]] (the ore of [[tin]]), [[bismuthinite]] (the ore of [[bismuth]]), and [[galena]] (the ore of [[lead]], plus a 50% chance of silver).

==Igneous intrusive layers==
{{Layerlookup/layers|IGNEOUS_INTRUSIVE}}

==Stone found in igneous intrusive layers==
{{Layerlookup/stones|IGNEOUS_INTRUSIVE}}

====Stone appearing in both igneous intrusive and igneous extrusive layers====
{{Layerlookup/stones|IGNEOUS_ALL}}

==Gems found in igneous intrusive layers==
{{Layerlookup/gems|IGNEOUS_INTRUSIVE}}

====Gems appearing in both igneous intrusive and igneous extrusive layers====
{{Layerlookup/gems|IGNEOUS_ALL}}

* See also: [[stone found everywhere]]

==In the real world==
Igneous intrusive [[stone]] is formed by magma solidification occurring below the surface, as opposed to [[Igneous extrusive layer|igneous extrusive]] stone, which forms above the surface of the earth.

{{stones}}
{{Category|Stone Layers}}
[[ru:Igneous intrusive layer]]

Igneous intrusive layer

2023-01-05T19:21:46Z

Jan:

{{migrated article}}
{{Quality|Unrated}}
{{av}}
[[File:igneous_intrusive_layer.jpg|thumb|300px|right|Created from rocks that have crystallized from the heat of magma.]]
'''Igneous intrusive'' [[stone layers]] can consist of [[granite]], [[diorite]], or [[gabbro]], all of which typically contain [[gold]] and [[tetrahedrite]].

Gabbro can also contain [[garnierite]] (the ore of [[nickel]]), [[kimberlite]] (which may contain [[diamond]]s), and [[olivine]] (which may contain [[native platinum]]). Granite can contain [[cassiterite]] (the ore of [[tin]]), [[bismuthinite]] (the ore of [[bismuth]]), and [[galena]] (the ore of [[lead]], plus a 50% chance of silver).

==Igneous intrusive layers==
{{Layerlookup/layers|IGNEOUS_INTRUSIVE}}

==Stone found in igneous intrusive layers==
{{Layerlookup/stones|IGNEOUS_INTRUSIVE}}

====Stone appearing in both igneous intrusive and igneous extrusive layers====
{{Layerlookup/stones|IGNEOUS_ALL}}

==Gems found in igneous intrusive layers==
{{Layerlookup/gems|IGNEOUS_INTRUSIVE}}

====Gems appearing in both igneous intrusive and igneous extrusive layers====
{{Layerlookup/gems|IGNEOUS_ALL}}

* See also: [[stone found everywhere]]

==In the real world==
Igneous intrusive [[stone]] is formed by magma solidification occurring below the surface, as opposed to [[Igneous extrusive layer|igneous extrusive]] stone, which forms above the surface of the earth.

{{stones}}
{{Category|Stone Layers}}
[[ru:Igneous intrusive layer]]

Igneous extrusive layer

2023-01-05T18:38:45Z

Jan:

{{migrated article}}
{{Quality|Unrated}}
{{av}}
[[File:igneous_extrusive_preview.png|thumb|260px|right|Created when magma exits a volcano and cools above the Earth's surface.]]
'''Igneous extrusive''' [[stone layers]] are formed from [[andesite]], [[basalt]], [[dacite]], [[obsidian]], and [[rhyolite]]. Of these five, andesite, dacite, and rhyolite are functionally identical, different only in appearance and name, basalt is like the other three except that it is magma-safe, and obsidian is... unique.

==Igneous extrusive layers==
{{Layerlookup/layers|IGNEOUS_EXTRUSIVE}}

==Stone found in igneous extrusive layers==
{{Layerlookup/stones|IGNEOUS_EXTRUSIVE}}

====Stone appearing in both igneous intrusive and igneous extrusive layers====
{{Layerlookup/stones|IGNEOUS_ALL}}

==Gems found in igneous extrusive layers==
{{Layerlookup/gems|IGNEOUS_EXTRUSIVE}}

====Gems appearing in both igneous intrusive and igneous extrusive layers====
{{Layerlookup/gems|IGNEOUS_ALL}}

* See also: [[stone found everywhere]]

==In Real Life==
In real-world geology, Igneous extrusive [[stone]] is formed by lava solidifying above the surface, open to the air. This is the main point of difference from [[igneous intrusive layer|igneous intrusive]] stone, which solidifies below the surface. This distinction is not kept in ''Dwarf Fortress'' geology, in which the difference is simply the name and contents of the two types of stone.

{{stones}}
{{Category|Stone Layers}}
[[ru:Igneous extrusive layer]]

Dwarf Fortress Wiki talk:Versions

2023-01-05T18:25:13Z

Jan: /* Creature List Now Supports Graphics! */

{{archive|
# [[DF Talk:Versions/Archive 1|Page 1]]}}

== Version 0.31.19 starts a new DF generation? ==

My reading of Toady's comments on the release of 0.31.19 is that it came out basically because he felt it would take too long to get DF all the way to 0.32. With the ore changes, the sitefinder changes, the addition of grazing and several different industries, there's a lot of changes between 31.18 and 31.19. So I'm thinking it might be a good idea to call it the first release of DF2011 - and what we refer to as "DF2010" would then become 0.31.18.

Thoughts? --[[User:DeMatt|DeMatt]] 07:06, 28 February 2011 (UTC)

==Revisiting Redirects==
I wasn't around when the redirect policy was created, and I'm having trouble understanding the rationale. The example claims that linking [[Main:Cheese]] to [[cv:Cheese maker]] is problematic...but mainspace only ever redirects to the current version. If the best target in the current version is cheese maker, why not link to it directly? (It's not, at least for Cheese, since [[DF2012:Cheese]] exists now.) The explanation seems to be claiming that 40d articles that link to Cheese will follow the Mainspace link--but that hasn't been the case for a long while now. Articles in 40d automatically link against other articles in 40d, so that version remains internally consistent no matter where mainspace links to in the current version. For a current example, what do we gain by linking [[Main:Mead]] to [[cv:Mead]] and linking [[DF2012:Mead]] to [[DF2012:Alcohol]]?

If this really is just an outdated procedure, I recommend we drop the mummery and allow mainspace to link to cv:(best target). Double redirects ''may'' work (sometimes, but [[Main:Mead]] demonstrates a common problem where automatic redirection fails), but if they are unnecessary I think they should be avoided, partly because of problems like [[Main:Mead]] and partly because of the effort required to protect double redirects from users who believe they are problematic.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:16, 8 January 2014 (UTC)

:I was just thinking that. I'm currently attempting to write a basic extension to eliminate the need for mainspace redirects entirely, although Mediawiki's class structure may make this more difficult than I had hoped (the only method I've found for resolving redirects takes the ''article text'' instead of a title, e.g. "#REDIRECT ..."). I do agree that the current situation with redirects isn't ideal, so I'm hoping this will work better (once I get it to work). --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:42, 8 January 2014 (UTC)

Okay, that wasn't quite as clear as I meant it to be. In general, I think this is a tricky situation. Mediawiki wasn't designed to have five content namespaces, and certainly not chains of redirects between them. The problem that was pointed out in the [[DF:REDIR|policy]] is the fact that with:
Main:Foo -> cv:Bar
pages in the cv: namespace can't use [[<nowiki/>foo]], since the namespace links modification causes it to be treated as [[<nowiki/>cv:foo]] instead, which doesn't exist. The current suggested solution is this:
Main:Foo -> cv:Foo -> cv:Bar
This fixes the problem of [[<nowiki/>foo]] not working on cv pages, but creates issues with double redirects not always working. Another solution, which is more intuitive to new editors, is:
Main:Foo -> cv:Bar
cv:Foo -> cv:Bar
Both require creating two redirects. The first method has the advantage of ''ensuring'' that the cv redirect exists (otherwise, main:foo would be a redlink), while the second has the advantage of working more reliably in a couple cases.

What I'm trying to do is make main:Foo "jump" to cv:Foo when cv:foo exists, ''even if main:foo doesn't exist'' (basically it would treat all mainspace pages as redirects to cv pages, but only if the cv page exists and not the mainspace page). I had main:Bar jumping to cv:Bar fine, but if cv:Foo redirected to cv:Bar, accessing main:Foo would mysteriously stop at cv:Foo even if I increased the redirect limit. What I'm trying to do now is follow the redirects internally, without relying on Mediawiki to do it automatically - unfortunately, that has proved to be harder than I had hoped (and I sent my web server into an infinite loop while trying). I will try to work on this some more when I get a chance, although I'm not sure when that'll be yet :(. For now, feel free to fix broken double mainspace redirects as necessary, as long as redirects in the DF2012 namespace stay pointing to the right page (and new mainspace redirects get added in the DF2012 namespace too). --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:21, 9 January 2014 (UTC)

:You're treating cv like a namespace--it's not. It is simply shorthand for "fill in the current version here". [http://dwarffortresswiki.org/index.php?title=User_talk:Briess&diff=182404&oldid=181281 As I discovered a long time ago on a server not far away], linking from Main:Foo to cv:Foo tends to break redirection chains. If, instead of linking to cv:Foo, you link to DF2012:Foo, it might just work. It would, of course, be better if your patch could evaluate cv itself, but even if you have to hardcode the current version it's a single point of maintenance that requires update very infrequently. (For that matter, we could probably dispense with the cv hack entirely and just have a bot update mainspace links from DF2012 to DF201X when we switch to a new version.)--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:05, 9 January 2014 (UTC)
::I know cv isn't a namespace - I was just trying to avoid future confusion when the DF2012 namespace changes. It's interesting that changing "cv" to "DF2012" fixes some broken redirects, although I've found that simply making an edit to a broken redirect can usually fix it as well. I've actually had the most problems with double redirects when the second one (in the DF2012 namespace) doesn't use the DF2012 prefix (e.g. main:Foo containing <nowiki>[[cv:Foo]] and DF2012:Foo containing [[Bar]]</nowiki>). I'd rather keep the cv alias even if it isn't necessary for mainspace redirects when I get the patch to work, since it makes it easier to refer to the current version of the page (for example, several MDF articles contain links to a vanilla page for things that don't change in the mod).
::Also, using aliases like "cv" is supported by Mediawiki; in fact, several WMF wikis use them (for example, "[[wikipedia:WP:Redirects|WP:Redirects]]" on Wikipedia). It's quite likely that Mediawiki isn't processing double redirects using aliases correctly, though, since that's uncommon on most wikis. --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:35, 9 January 2014 (UTC)

In light of the lack of support for the current redirect policy, I propose we replace the current redirect section with:

:Mainspace article pages should use the cv: alias when redirecting to a versioned page, which will automatically update the link when a new version is released. For example, page "Main:Foo" should redirect to page "cv:Bar" (where "Bar" is the page that best describes the topic Foo in the current version).

:Pages in mainspace should only redirect to an older versioned page if that content no longer exists in the current version of the game (e.g. [[Cave river]], [[Chunk]]). In these cases the cv: alias cannot be used.

:Pages inside a versioned namespace should not use the cv: alias. Instead, they should redirect to the best page within that versioned namespace (e.g. [[DF2012:Dodging]], [[v0.31:Drink]]).

:Due to limitations of the wiki software, double redirects should be avoided if possible. When fixing double redirects in mainspace, please make sure to use the cv: alias as appropriate.

If no one objects, I will make this change in a few days.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:21, 15 January 2014 (UTC)

:Okay with me. It may be worth mentioning that double redirects only really need to be changed when they don't work (since changing a lot of redirects that work isn't necessary), but I think it's clearer and more relevant than the current policy. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:26, 16 January 2014 (UTC)

Done.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:55, 22 January 2014 (UTC)

I was finally able to get my extension to work after being motivated by one too many malfunctioning redirects. It now causes nonexistent pages in the main namespace to behave exactly like redirects to their DF2012 counterparts (when linked to, accessed directly, and transcluded). Double redirects also work (up to 100, in fact, although that was a temporary safety measure that I'll probably change). This means we'll be able to safely get rid of all mainspace redirects (redirects that redirect to something other than "cv" will still function if not deleted). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:20, 14 March 2014 (UTC)
:What about articles which don't exist in the current version but do exist in older versions? Will those still need mainspace redirects, or will your extension be able to automatically redirect them to v0.31/40d/23a? --[[User:Quietust|Quietust]] ([[User talk:Quietust|talk]]) 01:29, 14 March 2014 (UTC)
::It ignores all mainspace pages that actually have content, including redirects, so pages like [[masons guild]] won't be affected (unless deleted). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:47, 14 March 2014 (UTC)

Done and deployed. [[Cat]] is still treated as a redirect, even though I just deleted it (try clicking on the "redirected from" link). Pages that exist are ignored, so [[Masons guild]] and [[History of Dwarf Fortress]] still function normally (as a redirect to a 23a page and a non-redirect, respectively). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 18:57, 14 April 2014 (UTC)

I'm sending around a bot right now to delete all redirects of the format "foo -> cv:foo" (a surprising number don't fit this format, so I'm leaving them alone for now). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:43, 14 April 2014 (UTC)

:I'm confused. Do we use double redirects or not? Is there a single place we define our linking policy (including redirects), and is it updated?
:I had trouble linking to [[Consolidated_development]] in [[v0.34:Dragon]]. It kept pointing to v0.34:Consolidated_development, which does not exist. I ended up linking to Main:Consolidated_development to make it work. --[[User:Nahno|Nahno]] ([[User talk:Nahno|talk]]) 10:18, 1 July 2014 (UTC)

::That's a separate problem altogether - links in the versioned namespaces (v0.34, v0.31, 40d, 23a) automatically link to pages within their namespace. I may be able to set up a fallback to mainspace once I'm able to deploy again, but for now the "main:" alias is the intended solution. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 11:36, 1 July 2014 (UTC)

== Google often directs people to the 0.31 page ==

I've noticed a couple of times that finding a wiki page from an external search will often drop me onto a page from an older version. Is it possible to mitigate this somehow for new players? I could imagine something like redirecting old:Bar -> cv:Bar unless the user has come from old:Foo; no idea if that would actually work though. [[User:PeridexisErrant|PeridexisErrant]] ([[User talk:PeridexisErrant|talk]]) 11:48, 4 May 2014 (UTC)

:As a temporary solution, I could write a script that displays a banner of some kind if the user came from an external site. I'll ask Briess if he can do anything on the server level to increase the weighting of the current version's pages. (Obviously there are situations where people are looking for old pages, like [[23a:dungeon master]], so we don't want to disable indexing entirely on old pages.) —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:03, 4 May 2014 (UTC)

== DF2014? ==

As Toady [http://www.bay12games.com/dwarves/ draws closer to a new release], it might be worthwhile to discuss the addition of a new version to the wiki. The upcoming release covers two years of changes and introduces a number of new plants, foods, drinks, multi-tile trees, climbing, jumping, etc., so it is likely to have significant changes from the current DF2012. To avoid having people start new pages (and lose all the effort spent refining the prior version's page), I think it would be best to have a bot automatically copy over the DF2012 pages as a starting point for DF2014. I would suggest that these copied pages include a noticebox template mentioning that the content may be outdated, so that we can easily track which pages have been reviewed. I think either the {{tl|version check}} or {{tl|old}} template would work. --[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 19:43, 5 May 2014 (UTC)

:This is what [[User:QuietBot]] did after the 0.34 release, so it's certainly possible to use the same script to migrate to DF2014. I would like a way of tagging migrated pages, since inaccuracies in some pages went unnoticed for months after they were migrated. Since {{tl|old}} is already in use, {{tl|version check}} may be a better solution (it can be reworded slightly, or we can make a separate template for DF2014 migration). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:23, 1 June 2014 (UTC)
:Made [[Template:DF2014 migrated]] as an example. Any thoughts? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:32, 1 June 2014 (UTC)

== Redirects inconsistency ==

Following a redirect is supposed to be exactly the same as going straight to the page it redirects to, but this actually isn't the case:
* Go to [[Seeds]] and you get [[v0.34:Seed]] (outdated)
* Go to http://dwarffortresswiki.org/index.php?title=Seeds&redirect=no and click on the link and you get to [[DF2014:Seed]] (current)
So if you search for "seed", the top result is the DF2014 version. But search for "seeds" and you get the redirect, which sends you to the outdated page instead. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 23:22, 22 February 2015 (UTC)

While I'm talking about redirects, it seems redirects to sections don't work: see [[DF2014:How do I manage my seeds and crops]]. I know MediaWiki is capable of this trick because Wikipedia does it. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 23:32, 22 February 2015 (UTC)

:I have absolutely no idea why [[seeds]] redirects to a v0.34 page - it could be a Mediawiki bug. The section links issue is due to a known issue in the redirect extension we use, which has yet to be fixed. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:01, 23 February 2015 (UTC)
:It looks like deleting both [[Seeds]] and [[DF2014:Seeds]] fixed things (by allowing AutoRedirect to handle the redirects instead). Feel free to tag any others with {{tl|bad redirect}}. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:03, 23 February 2015 (UTC)
::It gets stranger. [[Vial]] redirects explicitly to [[cv:Flask]] which displays (when you look at it with &redirect=no) as [[DF2014:Flask]], but still goes to the v0.34 version. It seems redirects interpret the cv: pseudo-namespace (or whatever it's called) in an outdated way. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 18:08, 23 February 2015 (UTC)
::I've added a note to this page about this issue. If it gets resolved, the note should be removed. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 21:04, 23 February 2015 (UTC)

==Reorganizing versions==

The internet deals with moved content... poorly. Google is still linking to v0.34 pages more than a year after the switch to "DF2014", and even the wiki software still has cached links pointing to the old version pages.

I propose reorganizing versions on the wiki to avoid moving content whenever possible. Instead of having a temporary "current version" namespace that changes occasionally, all the current information gets promoted to the Main namespace. When the next version split occurs, the Main articles as of a certain revision number can be copied to the newly-created permanent "old version" namespace, while all the current information remains in Main. This not only fixes the link rot issue, but it has a few other benefits as well: fewer administrative tasks, no lockdown (a historical version of the Main pages can be copied at any point, even if the Main articles are already modified for the new version), almost all the article history is maintained in the Main article (instead of being spread unevenly across multiple versions), no "temporary" namespaces are needed, fewer problematic long redirect chains, and hopefully less user confusion (since Main gets priority in search results, etc.).

As an example, today we would not have a DF2014 namespace (which is good because "temporary" namespaces historically disappear anyway). If you ran a search for [[seed]] you'd end up at Main:seed, which would have all the current information on seeds. The version box at the top of the page would still link to the older versions of the seed article. When a new version is released, an admin would choose a revision number and copy the Main:seed article as it exists at that revision number to v0.40:seed. That's it. One historical copy that needs little to no new editing, and zero redirections/moves.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 19:02, 27 July 2015 (UTC)

:Makes sense to me. It would involve a lot of work, though (e.g. fixing templates and categories to account for the current version being in mainspace), although that should be doable thanks to {{tl|category}}, {{tl|version switch}}, etc.. A bot could be set up to copy revisions from before a release date as well, which would be more difficult (and maybe slower) than a direct copy, but not severely. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:24, 30 July 2015 (UTC)

:Actually, there are a few issues with that, namely that there wouldn't be an easy way to distinguish between versioned and non-versioned mainspace pages. There are ways to resolve Google search priority (we can exclude pages from older versions from search engine results if there are newer versions of those pages available, for example). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:47, 6 August 2015 (UTC)

::There aren't very many non-versioned mainspace pages, and determining if a page is versioned is as simple as looking for the version template and/or categories added by the version template (e.g. copy [http://dwarffortresswiki.org/index.php/Category:Current this category] instead of Main:*). The problem with "suggesting" newer pages to Google is that they obviously aren't crawling our wiki regularly (if they were, the fact that the mainspace redirects point to new pages would automatically be picked up). Even if your Google hints worked they wouldn't do anything for all the other broken links out on the 'net.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:35, 6 August 2015 (UTC)

::: Google actually crawls the wiki constantly - we probably get crawl hits from google for a continuous block of 2-3 hours per day, each and every day. Why they are slow to update is beyond me though. I can't remember why we didn't do this initially, but there was a technical limitation involved if I remember correctly. --[[User:Briess|Briess]] ([[User talk:Briess|talk]]) 22:05, 6 August 2015 (UTC)

::: There are <meta> tags that can be used to hide pages from search results (for search engines that recognize them, that is). Searching for {{tl|av}} or [[:Category:Current]] might work, although we'd have to make sure all of the DF2014 pages include that (some pages don't, particularly some disambiguation pages, although all of them should). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:53, 6 August 2015 (UTC)

:Is there a particular reason main and current are separate to begin with?—[[User:CLA|CLA]] ([[User talk:CLA|talk]]) 00:17, 7 August 2015 (UTC)

::It's mostly intended to distinguish between versioned and non-versioned pages and make version-related templates simpler to work with, since every versioned page has a namespace. I wasn't active here in 2010 when this system was created, so Briess and Emi would know more.
::Another issue I just thought of with Loci's suggestion is categories - currently, categories like [[:Category:Animals]] are used to organize the versioned sub-categories. Sure, we can change {{tl|Category}} to categorize mainspace pages in [[:Category:v0.40:Animals]] or [[:Category:DF2014:Animals]], but that would be less straightforward because there wouldn't be a namespace with that name (until pages are migrated when a newer major version is released). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 13:05, 7 August 2015 (UTC)

:Moving current pages to the main namespace sounds like a great idea. -[[User:Jecowa|Jecowa]] ([[User talk:Jecowa|talk]]) 20:47, 4 January 2018 (UTC)

Another thought: dealing with migrating redirects could be difficult with this proposal - specifically, determining which redirects should be migrated to a versioned namespace. Redirects can't contain {{tl|av}}, at least not before ``#REDIRECT``. I ''think'' it would be possible to copy pages in two stages, though - all non-redirects first, then all redirects whose targets were also copied. Thoughts? Anything I'm missing? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:41, 27 June 2019 (UTC)

Some subpages (particularly /raw and /Edit notice) also deliberately lack {{tl|av}}, although those shouldn't be too hard to handle. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:35, 9 July 2019 (UTC)

:Redirect pages (and all other edge cases I've looked at) can be included in categories (like [[:Category:Current]]) to determine whether or not they should be copied into an archival version. But if the redirects are "properly qualified" then they can all be copied over blindly. Mainspace redirects pointing to versioned information should use a blank namespace (which will be automatically constrained to the archival namespace); mainspace redirects pointing to unversioned information should use an explicit "Main" (which will automatically link back to the unversioned page). Then, when [[[[Toady]]]] gets copied to [[[[v0.4x:Toady]]]] it will point back to [[[[Main:Toady One]]]]. Meanwhile, [[[[Beer]]]], copied to [[[[v0.4x:Beer]]]], will properly point to [[[[v0.4x:Alcohol]]]].--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:00, 14 July 2019 (UTC)

::I think qualifying redirects is the best solution here - categorizing redirects manually is another possible source of errors, since categories (or a lack thereof) would only be visible on the redirect page itself, and [[:Category:Current]] is a hidden category. Copying over mainspace redirects into versioned namespaces would also resolve some issues that have come up due to those not reliably existing currently. I should be able to set up a bot script to add "main:" to current mainspace redirects (and it shouldn't break anything, since those redirects go to other mainspace pages anyway). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:57, 14 July 2019 (UTC)

(Note: I wrote all of this without noticing the previous discussion above.) I was wondering, when the wiki creates a new namespace for a major release again, if it is possible to ''not'' create a namespace for the next current version (e.g. "DF202x") and instead have the mainspace articles (which are currently redirects) become the new cv and move the content there. Therefore, [[cv:Cat]] would just be "[[Cat]]" (or [[Main:Cat]]).

Certain namespace-related templates like [[Template:Ns/0]] would need to be changed, though nothing significant as far as I know. For most cases, any "DF2014" would be replaced with "Main" or even blank. There's also multiple extensions handling the current namespace system and they may need to be modified too, though I'm not sure if or how much. I'm guessing based on the discussions above that it will change stuff up.

My reason is the current namespace is increasingly becoming more anachronistic. "DF2014" could be misinterpreted as "this page is about the 2014 version of the game" or "this page was last updated in 2014", which I've seen a few people in forums mention. Granted that [[Template:Av]] is on the top of very article, I still think the namespace is inconsistent with the recentness of the article. But how is this related to what I'm asking for? Let's say we continue the current system: if we happen to do a new namespace change this year and create DF2020, the next major release (after graphics/UI) will be mythgen, which is estimated to take several years to develop (the Big Wait), and so the anachronism will start over again. The proposed way will prevent this from occurring for the next major release and every release thereafter.

I think the confusion with having a namespace that becomes old-fashioned overtime supersedes the confusion with not marking current versioned articles with a namespace. Most users just search "Cat" on the search bar and naturally expect to get information about the latest release of DF. So if users go a page that's just titled "Cat", they won't expect outdated info about cats from a previous release. That's how the current system works anyways. We'll be skipping the two-step process that we have now. It'll make several wiki tasks much simpler as well. Editors can create new articles for current versions without remembering to add a namespace. It'll fix any existing issues with (double) redirects; instead of [[Main:Kitten]] redirecting to [[cv:Kitten]], which goes to [[DF2014:Kitten]], which then redirects to [[DF2014:Cat]], [[Main:Kitten]] would just redirect to [[Main:Cat]]. And the cv: alias will no longer be necessary since "cv:" = "Main:" and will be forever.

There's no need to differentiate the current version and previous versions with a namespace for the current version is what I'm saying. Articles of previous versions will retain their respective namespaces. Users will still type "40d:Cat" to go to the 40d version of the article, but if they want the current version, they'll just type "Cat" (like now). The mainspace containing the "live" version of an article is natural and would create no uncertainty when browsing the wiki. And it would simplify the wiki somewhat and future-proof this anachronism problem. As a bonus, this change will also prevent web search engines from showing previous version pages when typing "DF cat" or something. (This isn't happening right now as DF2014 has been the current namespace for ~6 years, but it'll happen again when everything moves to a new namespace.)

This is the gist of it, and I may have ignored most of the problems with this proposal. I have personally wished for the whole version namespacing be made less complicated and have been seeking for a solution, and I feel like this is the best way to go about in the future. – [[User:Doorkeeper|Doorkeeper]] 21:27, 14 August 2020 (UTC)

:<s>Whoops, looks like Loci already proposed this exact thing long ago. I definitely missed that discussion and should have checked first. My apologies. I'll move my text to that section and remove this one. – [[User:Doorkeeper|Doorkeeper]] 21:36, 14 August 2020 (UTC)</s> Done. – [[User:Doorkeeper|Doorkeeper]] 21:40, 14 August 2020 (UTC)

:The main issue I have with that is that putting pages about the current version in a namespace also differentiates between those pages and pages not about ''any'' version (for example, [[Toady One]] does not need a 40d or v0.34 page). Yes, we can use {{tl|av}} to mark versioned pages, but people often forget to add that to new pages. The current system also allows determining whether a page is versioned or not from its title, which makes migrations a lot faster. Relying on {{tl|av}} would require either reading the content of every page (which would slow scripts down significantly) or cross-checking with the list of all pages including the template (feasible, but a bit more complicated, and still susceptible to missing templates). I suppose that manually fixing and migrating pages missing {{tl|av}} later wouldn't be too much work, though.
:I am definitely in favor of changing "DF2014" (or a new namespace) to "Current", though. I was in favor of "DF2014" in 2014, but I don't think it makes sense anymore, and "Current" seemed to be a popular alternative in both the DF2012 and DF2014 discussions on the matter. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:02, 16 August 2020 (UTC)

== Weird redirect behaviour ==

[[Pump stack]] redirects to [[cv:Screw pump#Pump stack]]. If you look at the redirect itself it says it redirects to DF2014 namespace, which is correct. But if you actually follow the redirect, it goes to v0.34 namespace. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 16:10, 20 August 2018 (UTC)
:Yeah, that's part of the issue described in the above section (the wiki caching part, not on Google's end.) —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 15:00, 21 August 2018 (UTC)

== v50 organization ==

Some wiki admins have had a talk on Discord and decided that the most sustainable path forward is to put content for all future versions of DF in the main namespace. We will be working on a bot to do this in the next few days. Feel free to chime in with suggestions here. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:56, 14 December 2022 (UTC)

:Is it maybe possible to do backwards-namespacing? Like we have a "Main" namespace, which people are free to update, and whenever there's a new version of DF the "Main" namespace is copied into a namespace for the then old version, much like how you'd branch a stable branch from a development branch when working with a git-project? [[User:Therahedwig|Therahedwig]] ([[User talk:Therahedwig|talk]]) 23:13, 14 December 2022 (UTC)

::Yeah, we could do that if we decide to. We were talking about doing that for v50, actually, and might still do something similar to preserve edit history if it doesn't end up being too hard to automate. Our hope is that we will not introduce new namespaces for v50 -> v5x, unless there is a serious breaking change (and hopefully there isn't one). But if we change our mind, one advantage of the type of migration you mentioned is that it can be done retroactively - we can copy historical revisions that were current at the time of the release, and would only lose some typo fixes made after the release that apply to earlier versions as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:11, 15 December 2022 (UTC)

ETA is < 24 hours. Doing some final checks on a migration script. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 07:08, 19 December 2022 (UTC)

: We should really have a task list as there are many things that change and need updating. Including but not limited to:
:* Most templates that used the previous namespace convention broke, including nav templates.
:* Many game files changed locations and their pages need to be updated.
:* Raws need to be updated.
:* Various features added, changed, removed.
:* UI has been changed -- though I am more inclined to wait for classic release to avoid extra work --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 06:56, 20 December 2022 (UTC)

"''Raws need to be updated.''" Including applying text wraparound where necessary, I suppose - more than a few of them have proven to be that special kind of...''difficult'' to navigate otherwise, shall we say? [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 12:52, 20 December 2022 (UTC)

:There is already a task list in the [[#v50 migration|section below]] that includes templates and raws, with an explanation. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:25, 20 December 2022 (UTC)

== v50 migration ==

The initial migration script is done. New content is in the '''main''' namespace, e.g. [[Cat]]. Old content is still at [[DF2014:Cat]]. History was migrated to the ''new'' (main namespace) articles.

I know several things are broken still. Please reply if you find any others:
<div style="border-left: 2px solid red">
* <s>Versioned templates haven't been migrated yet (e.g. {{tl|vermin}} on [[Ant]])</s>
** Fixed. Most were migrated by a bot.
* <s>Raws are missing on all pages that use them.</s>
** This also affects sidebars, such as on [[Cat]] and [[Microcline]].
** Update: The DFRawFunctions extension has been upgraded to include v50 raws, using the "v50:" prefix for filenames instead of "DF2014:". <s>I haven't finished a migration script to create the /raw pages themselves, but they can typically be created manually by copying the DF2014 /raw pages and changing "DF2014" to "v50" everywhere.</s> —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:20, 1 January 2023 (UTC)
** Update 2: Raws have been added for all pages! They were copied from the "DF2014" pages and had "DF2014" replaced with "v50", which appears to have worked from a spot-check, but let me know if you find any problems. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:57, 4 January 2023 (UTC)
* Some pages where the DF2014 page was a redirect to a main namespace page that contained content were migrated incorrectly.
** In this case, the main namespace page is usually a redirect to itself. This can be fixed by undoing LethosorBot's edit to the main namespace page, then copying the content to the DF2014 page.
** Update: most seem to have been fixed manually - thanks! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:41, 21 December 2022 (UTC)
* <s>Some main-namespace talk pages redirect to DF2014 talk pages. Some of these redirects work, and some (usually older ones) do not.</s>
** Fixed with a bot. Some redirects from talk pages to other deleted talk pages are now broken, e.g. [[Talk:Above_ground]] (exists) -> [[Talk:Tile attributes]] (redlink). I am leaving them like that because they redirect to where the talk page should be created, but I'm also fine with people deleting them if they really want to. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:41, 21 December 2022 (UTC)
* {{tl|quality}} for new articles is disabled (see below)
* Some links from DF2014 to Main weren't working: e.g. the version selector [[DF2014:Mason's workshop]] was linking to [[DF2014:Main:Mason's workshop]] instead of [[Main:Mason's workshop]]. I'm not sure exactly why, but I fixed it with a change to the NamespaceLinks extension. Let me know if you spot similar broken links. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:19, 21 December 2022 (UTC)
</div>

—[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:54, 20 December 2022 (UTC)
:The quality levels of the 50.03 pages seem to be missing. I'm not sure if that's covered under that first point. [[User:Trainzack|Trainzack]] ([[User talk:Trainzack|talk]]) 06:47, 20 December 2022 (UTC)
::If the the [[Dwarf Fortress Wiki:Quality]] feature can be made to work with namespace scheme change, I suggest to automatically assign the lowest quality rating to all pages, alternately add the {{tl|old}} to all pages. Otherwise there will be a lot of pages that will fall through the cracks. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 09:12, 20 December 2022 (UTC)
:::I disabled {{tl|quality}} in the main namespace because it would require some rework to make the rating script and the template work properly there. Feel free to take a stab at the template. I will see what can be done on the extension side. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:14, 20 December 2022 (UTC)
::::What needs to be done on the template side? I'm not sure I see too big of an issue leaving pages as "unknown-quality" for now (or just change the default to tattered) until we get the rating script working. Is that script up anywhere, anything that could be helped with? [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 11:10, 2 January 2023 (UTC)
:::::They're already marked as unknown. Really the only issue I know of with the template is that it doesn't show up with some of the newer skins we added, and that can be fixed by getting rid of the absolute positioning. As for the script, it can be found at https://github.com/DF-Wiki/QualityRatings, and the issue is really only with the configuration system not recognizing the main namespace as valid. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:29, 3 January 2023 (UTC)
::::::Great, I started having a crack at fixing the template with different themes. Is the preference to get some CSS going and then include it in the global stylesheet (i.e different styles per theme) or to try and get a "one size fits all" fix? —[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 08:14, 3 January 2023 (UTC)
:::::::I would rather avoid custom site-wide CSS if we can. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:29, 4 January 2023 (UTC)
::::::::I appreciate that, I think it's the simplest solution to add a few lines to common.css though. Unless there is a way to attach CSS specifically to a template, I saw a few extensions that allowed that but I'm not sure if any are present in the wiki at the moment. Regardless there already exists a class `div.topicon` that is specifically for the quality ratings, is there an issue with expanding this class to accommodate the themes? The list of themes where the quality rating display is broken/invisible: Citizen, MinervaNeue, MonoBook. —[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 21:48, 4 January 2023 (UTC)
:::::::::What do you think of moving the template out of the topicon entirely and just placing it in a div? It would take up a (hopefully) small amount of vertical space in the article. [[User:Lethosor/Sandbox/Quality_test]] is an example. Unfortunately it isn't possible to prevent other templates from displaying above the quality this way ([https://dwarffortresswiki.org/index.php?title=User:Lethosor/Sandbox/Quality_test&oldid=283883]). So maybe we do need some custom CSS after all if we want that. I'm open to trying out whatever you propose. I'm a bit worried about future-proofing against skins we add later (particularly a mobile skin) but at least MediaWiki supports skin-specific global CSS as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:33, 5 January 2023 (UTC)
::::::::::I would rather we avoid taking any more vertical space in the article. The growing block pyramid at the top, starting with version template, is annoying. If you end up placing it inside the article space please use a slim box 100% wide that would include both.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 01:19, 5 January 2023 (UTC)
:::::::::::Agreed with you Jan, however I see that as two different tasks (ArticleVersion template changes, getting quality back on pages). I made a test adjustment to the quality and it takes up a negligable amount of extra space. See [[User:Vallode/sandbox#Page_quality]] for the example, we'd be able to completely remove "topicon" (unless it is used somewhere else?) and then potentially move on to making the ArticleVersion template into a slim version on the left-hand-side instead of a large box? Let me know what you think. --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 17:35, 5 January 2023 (UTC)

It appears some pages are redirecting recursively and never resolving correctly, like the [[https://dwarffortresswiki.org/index.php?title=Character_table&redirect=no|character table]] and [[tileset repository]] 07:35, 20 December 2022 (UTC)
: Indeed, these can be caught here: [[Special:DoubleRedirects]] --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:51, 20 December 2022 (UTC)

It might be useful to change the notice title to "release information '''for editors'''" --[[Special:Contributions/142.59.195.176|142.59.195.176]] 10:26, 20 December 2022 (UTC)
:Can do. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)
::New here, hello. Should we set a date where we remove/only show the banner for logged in users. There are (some) pages that have 4 different notices about the upgrade. [[Engraving]] is one such page, the top banner states "information for editors", we then have the "this page was migrated" banner, a version selection which warns the article might be inaccurate, and a smaller banner saying the page might need to be updated. Quite a lot of screen space, I think we can start to slowly reduce the amount of warnings this coming month? [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 10:07, 2 January 2023 (UTC)
:::Unfortunately, only showing info to logged-in users is difficult with how MediaWiki caching works. In terms of reducing warnings, there is a discussion [[Template_talk:ArticleVersion#.22Note_that_some_content_may_still_need_to_be_updated..22|here]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:43, 4 January 2023 (UTC)
:::As for [[Engraving]] specifically, the {{tl|old}} banner was actually present on [[DF2014:Engraving]] as well and got carried over with the migration. I removed it, and agree that it was redundant. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:46, 4 January 2023 (UTC)

Main talkpages seem to redirect to DF2014 talk. Not sure if it is intentional but I like it, though we should pay attention when creating new discussion relating to v50 ending up there.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 14:18, 20 December 2022 (UTC)
:That's unintentional. I specifically wrote the migration script to not move talk pages, but that has the side-effect of leaving any previously-created "Talk -> DF2014 talk" redirects intact. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)

Yo Lethosor, are we adding graphic sprites for the pages in some way? Or are we waiting for you to add some sort of new template or something? I'm sure you don't need me to tell you that the current templates don't allow that. Not sure if I'm allowed to change/create any templates either, as I don't want to break things for hundreds of pages. Edit: And IF the icons are allowed, should they be left alone, or 2×-3× sized like how the Minecraft wiki does it? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 14:29, 20 December 2022 (UTC)
:Depends on which templates you mean. There are copyright concerns with uploading a premium sprite sheet, for instance. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)
::I'm not talking about uploading an entire sprite sheet. I'm just talking about individual icons for each respective page. One image for cows, one for horses, one for werebeasts, etc. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 16:50, 20 December 2022 (UTC)
:::If we do that for every creature in the sprite sheet, that's not much different (in terms of copyright) from uploading the entire sprite sheet. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:09, 20 December 2022 (UTC)
::::Is there someone we can talk to about that? We finally get this new game with graphics, and then we can't use the very graphics of the game? No matter what the rules are, I'd say that would be the stupidest thing ever. I know I'm infamous here when it comes to copyright and images and stuff, but about 80% of game wikis out there are completely unofficial, and use game file images like no one's business. I can't imagine anyone's door being knocked on if we used the game's sprites, but I won't add any here until we have a go-ahead. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 17:14, 20 December 2022 (UTC)

:::::...I've made noise in Mayday's direction on this matter, at least (prob an incorrect maneuver, ''but'').[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 17:55, 20 December 2022 (UTC)
:::::: I hope some sort of arrangement can be made so we can use the new sprites with permission/limits, just as we are using the raw files. Otherwise we are all (devs and editors alike) shooting ourselves in the foot here.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 21:07, 20 December 2022 (UTC)

:::::::I just thought of something. We're supposedly not allowed to upload entire sprite sheets, right? What if - for the time being - we just use a few of them for the purpose of testing out new infoboxes? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 21:46, 20 December 2022 (UTC)
::::::::I don't know. If someone could ask Kitfox and post the response here, that would be great. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:47, 20 December 2022 (UTC)

:::::::::I've reached out to Alexandra, but she hasn't answered yet. Until then I found these old approvals from the previous community manager, Feeona: ([http://www.bay12forums.com/smf/index.php?topic=173474.msg8243633#msg8243633 link1], [http://www.bay12forums.com/smf/index.php?topic=176640.msg8243642#msg8243642 link2]). Waiting for a newer response until we begin mass uploads is probably the politer option, but like Zippy said, it is also standard for wikis to use game sprites with less approval. I second their idea of trying it out with a few images to test the infoboxes. On the extreme off-chance (and I do think it is) Kitfox protests we can always remove these few. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 22:19, 20 December 2022 (UTC)
:::::::::And here is a third, more official statement: ([http://www.bay12forums.com/smf/index.php?topic=173474.msg8249718#msg8249718 link3]). Perhaps that address of info@kitfoxgames.com is the better channel to ask for a confirmation, rather than Discord DMs, but I will be going to bed, so it is best if someone else does that. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 22:29, 20 December 2022 (UTC)
::::::::::Thanks for tracking this down! Ok, sprites should be fine, but let's avoid uploading the entire premium tileset as a single image, for instance (as the forum thread says, "use common sense"). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:21, 21 December 2022 (UTC)
::::::::::: Looks good, permission is always preferable over fairuse, I think it is a win win for all involved. I agree that we shouldn't upload entire sprite sheets (e.g. there is no reason to upload the windmill from every direction or whole construction phase for workshops) and that there are a lot of details that needs to be ironed out through testing. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 05:07, 21 December 2022 (UTC)
:::::::::We have a green light on uploading all and any sprites. Their response to me can be seen [https://i.imgur.com/BhmHjzC.png here]. I'm sure someone else confirmed it before me. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 19:00, 21 December 2022 (UTC)

Shifting temporarily to a new issue, is the documentation of [[Template:ArticleVersion]] outdated? It would seem so to me, since the current version no longer has its own namespace, with the templates needing updating being different ones. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 18:30, 20 December 2022 (UTC)
:I think it is still accurate enough. We left open the possibility of making another namespace in the future, albeit with a different migration strategy - see [[#v50 organization|above]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:52, 20 December 2022 (UTC)

Some Changes to infoboxes might be needed. Too bad [[User:Doorkeeper]] isn't around. He did a great work with navbox project--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:52, 21 December 2022 (UTC)

I just realized that raw files aren't stored as regular wiki pages but loaded via the DFRawFunctions extension (hence the need to update). Good news it's going to be handled in bulk, consistently and relatively easy to updated. Even better it's Lethosor problem ;) Also I just realized that all the "raw files" (txt files in the new vanilla folder) are released into the public domain. Both are probably not news to the vets but I'll leave it here for those who less up to date like myself. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:35, 22 December 2022 (UTC)

: I noticed that some templates aren't working properly in the new namespace, e.g. [[Basalt]] entry had its raw updated manually but the infobox fail to show any details. Cursory look suggest {{t|layerlookup/0}} need a minor tweak. This should do the work
:: Replace: <nowiki>{{layerlookup/aux|{{{{FULLPAGENAME}}/raw}}|uses={{{uses|}}}|wiki={{{wiki|}}}}}</nowiki>
:: With___: <nowiki>{{layerlookup/aux|{{</nowiki>:<nowiki>{{FULLPAGENAME}}/raw}}|uses={{{uses|}}}|wiki={{{wiki|}}}}}</nowiki>
: Not sure what the plan and ETA with raws update so I didn't touch this high usage template for now. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 08:11, 24 December 2022 (UTC)

::Please do feel free to make this update. I am still working on a script to create the <code>/raw</code> pages themselves. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:12, 1 January 2023 (UTC)

Wouldn't it be an idea to add to the Sitenotice to remove the {{tl|migrated article}} tag when an article has been fully updated? I see many articles that seem to be updated still have the tag. And/or advise to make use of the {{tl|verify}} for sections still in need of checking? --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 10:12, 2 January 2023 (UTC)
:Probably a good shout. The "see this page" link does include the detail on removing but we should more explicitly encourage removing the banner once a page has at least been looked over. [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 11:01, 2 January 2023 (UTC)

== v50 specific issues ==
=== Graphics===
Follow up on the use of game sprites and the need to trying it out with a few images to test the infoboxes. First sprite [[:File:Beds v50.png]] was uploaded and used on [[Bed]] entry. Any thoughts? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:06, 21 December 2022 (UTC)
:Seems like it should be rearranged to be horizontal. Also, has there been a serious discussion about copyright? Full screenshots are 100% fine, but you start going into a grey area when you upload pieces of a spritesheet. I'm of the opinion that it's all fine as long as it's inconvenient to reconstruct the full sheet from the individual images. Maybe a further restriction could be you shouldn't upload any of the art unless it's used in an infobox (maybe an exception for pieces of the UI). And one more restriction could be you shouldn't show everything, like in your bed example, maybe just the wooden bed is good enough, leave out the stone and metal, especially since those can only be made from strange moods. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:43, 21 December 2022 (UTC)
::Actually, your bed image is kinda bad for showing off what a bed looks like because it doesn't show the pillow/blankets. That might point to cropped screenshots being the best path, although less convenient for the uploader, as you don't get details left out. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:46, 21 December 2022 (UTC)
::I created a new license template [[Template:Copyright game]], based it on the way the RimWorld wiki does things. Call it a prototype, but it's probably how your bed image should be labelled. Indeed, I added it to it already. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]])

::: I agree that the horizontal arrangement would suit better here and that we should strive to represent how things look in-game. Otherwise, I am not too concerned about people being able to reconstruct anything (lets just say that ''anyone'' interested in that can get the real thing from the game files), also it seem we have permission to use the sprits on top of fairuse. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 19:55, 21 December 2022 (UTC)

::: Modifying the existing template to allow the inclusion of the new sprites is easy (Something like [https://ibb.co/zFXCrjd this]?) The big question is the matter of consistency is there any exceptions that will break the format (size wise with variant bloat for example), the sprite naming format, etc --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:44, 21 December 2022 (UTC)
::: If we are going to show a variant for each material type, then maybe these should be added as separate images so we can add a tooltip for each image. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:49, 21 December 2022 (UTC)

:I've got another prototype going here and here: [[User:Brightgalrs/vector.css]] and [[User:Brightgalrs/Sandbox]]. (You'll need to add the css stuff to your own /vector.css). Basically it's a way to recolor images using css classes. No idea if there's a better way. Also, the real implementation would require a change to [[MediaWiki:Common.css]]. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 22:41, 21 December 2022 (UTC)
:Should mention, there ''is'' a different way, just upload each image 16 times, one for each coloring. But maybe that's not very elegant. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 22:45, 21 December 2022 (UTC)

: It should be noted that soon the classic edition will be released, hence one should plan to have both the Premium and classic alongside in that little space --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 03:14, 22 December 2022 (UTC)
::I'm looking into a tab extension to potentially support this in infoboxes. Perhaps [https://www.mediawiki.org/wiki/Extension:Tabs Extension:Tabs]? I tried [https://www.mediawiki.org/wiki/Extension:TabberNeue Extension:TabberNeue], but it displays a placeholder if JavaScript is disabled, which isn't great. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:22, 22 December 2022 (UTC)
::: The Neue Tabber seem to works pretty much like the old one (which fandom [https://coding-help.fandom.com/wiki/Tabber#Adding_images_into_tabbers still use]) defaulting to showing the first tab only. Quick look suggest that neue work the same, plus the notice that 'Tabber requires Javascript to function' warning? if so, and if it is a bother, then you should be able to edit out the tabberneue-noscript string in code. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 06:29, 22 December 2022 (UTC)
::: I much prefer your tabber solution, but if that fails we can also use the gallery slideshow mode. If so, beware it has no way to control image size so the images have to be maliciously uploaded using the exact same size. example:
<gallery mode="slideshow">
File:SteelSample.png
File:TinSample.png
File:ZincSample.png
File:GoldSample.png
</gallery> --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 10:19, 22 December 2022 (UTC)

==== adding premium set to Infobox ====
I am unclear where are we going with this? 
1) Will (A) tabs be implemented, (B) we be using mediawiki toggle [[Template_talk:V50_workshop|example]] for premium and classic/blocked, (c) put images side by side, or (d) something else? 
2) Also [[silver]] and [[Pig iron]] use very different image style for example. 
3) Anything else you want ? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 12:32, 30 December 2022 (UTC)

: Personally, I would love tabs to be implemented, but I think that side by side might be best for most. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 12:32, 30 December 2022 (UTC)
: Here is rough layout we can use. It should fit most buildings given the default sprite size. There is also a different floor plan for both (inspired by reddit)

{|
|- valign=top
|
{| style="width:200px; background-color:#eaecf0; border-collapse: collapse; "
|+ 5×5
|- style="border-bottom:2px solid #3366cc; "
|<div class="mw-customtoggle-infoboxtab mw-ui-button mw-ui-progressive" style="border-top-right-radius: 10px; border-top-left-radius:10px;">toggle</div>
|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|- valign=top
|colspan=2|<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">
[[File:Siege workshop.png|center|160px]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab"">
{|
|rowspan=2 style="width:50%; font-size: 125%;"|<center>{{Template:Picture Siege workshop}}</center>
|style="line-height: 1em; font-size: 125%;"|
{| style="border-spacing:4px;"
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|}
|
{| style="width:200px; background-color:#eaecf0; border-collapse: collapse; "
|+ 3×3
|- style="border-bottom:2px solid #3366cc; "
|colspan=2 style="text-align: right;"|<div class="mw-customtoggle-infoboxtab mw-ui-button mw-ui-progressive" style="float:left; border-top-right-radius: 10px; border-top-left-radius:10px;">toggle</div>{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|- valign=top
|rowspan=2 style="width:50%;"|
<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">[[File:Carpenter's workshop.png]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab""><center>
{| style="font-size: 175%; border-spacing: 0; background-color: black; border: 2px solid black"
|- 
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"| {{Raw Tile|"|7:0:0}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|{{=}}|6:0:0}}
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"|
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|]|0:0:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
|}</center></div>
|
{| style="border-spacing:5px;"
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|
{| style="width:200px; height:100px; padding:10px; background-color:#eaecf0; border-collapse: collapse;"
|+ 1×1
|- style="border-bottom:2px solid #3366cc;"
| colspan=3 style="text-align:center;"|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|-
| style="border-right: 1px dotted #545557;"|[[File:Screw_press.png|32px|center|link=]]
| style="font-size:125%;"|<center>{{Template:Picture Screw press}}</center>
| style="border-left: 1px dotted #545557;"|<center>{{Template:Floor Plan Screw press}}</center>
|}
|
{| style="width:200px; height:100px; padding:10px; background-color:#eaecf0; border-collapse: collapse;"
|+ 1×3
|- style="border-bottom:2px solid #3366cc;"
| colspan=3 style="text-align:center;"|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|-
| style="border-right: 1px dotted #545557;"|[[File:water_wheel.png|32px|center|link=]]
| style="font-size:125%;"|<center>{{Template:Picture Water wheel}}</center>
| style="border-left: 1px dotted #545557;line-height:normal;"|<center>{{Template:Floor Plan Water wheel}}</center>
|}
|}
:Any thoughts on the direction and or any and all of its elements? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 10:16, 31 December 2022 (UTC)

::I kind of like side-by-side, if it fits. If anyone wants to implement a toggle button or tabs, I would ask that that be implemented in a template for now, so that e.g. we could change a toggle button to tabs in a single place if we decide to install an extension to support that. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:14, 1 January 2023 (UTC)

::: I noticed a comment saying that [[impassable tile]] are no longer used in v50, is that true for all constructions? If so, floor plans are no longer needed, making things much easier as we can fit everything in except the 5v5 constructions like trade depot (and even these can be placed one above the other if so desired). If not, any thought on the alternative floor plan design? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:46, 1 January 2023 (UTC)

:::: None of the constructions have blocking tiles any more from my experience playing. I haven't tested siege weaponry with that stuff, but none of the workshops have it, nor does any furniture. (walls and fortifications will of course obstruct movement [[User:AndrielChaoti|AndrielChaoti]] ([[User talk:AndrielChaoti|talk]]) 18:47, 1 January 2023 (UTC)
::::: Ok, I have removed them from v50. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 23:48, 1 January 2023 (UTC)

I have added a basic side by side variant to [[Template:V50 workshop]] and [[Template:Building]] for testing, let us know if there any issues. Few notes:
* The default image naming scheme of <code>workshop-name.png</code> will likely conflict with existing images here or on commons, maybe another naming scheme should be used like <code>v50 workshop-name.png</code> as it is with ascii pictures.
* There is inconsistency in image size. If you want to use large zoomed images then toggle is best, otherwise they need to be all in native size (96px for 3x3).
* In the current version the code roughly centers the images and if there is a big image like with [[Siege workshop]] it drops to a new line --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 23:48, 1 January 2023 (UTC)

How about combining shortcut keys and the new menu icons:
<div style="color:white; font-size: large; text-shadow: -1px -1px 0 #000, 1px -1px 0 #000, -1px 1px 0 #000, 1px 1px 0 #000;">[[File:Ui b.png]]<div style="position: absolute; bottom:-14px; right:3px;">b</div>[[File:Ui bo.png]]<div style="position: absolute; bottom:-14px; right:3px;">o</div>[[File:Ui bol.png]]<div style="position: absolute; bottom:-14px; right:3px;">l</div>[[File:Ui boll.png]]<div style="position: absolute; bottom:-14px; right:3px;">l</div></div>
--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 02:24, 3 January 2023 (UTC)

:I worry that this is difficult to read (I read it as "boil" at first). I would rather use something like {{tl|k}} with a known background. What about something like this? [[File:Ui boll.png]]<div style="position: absolute; bottom:-14px; right:0px;">{{k|l}}</div> or, alternatively, using flexbox without any overlap: [[File:Ui boll.png]]{{k|l}} —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:37, 3 January 2023 (UTC)
:: Same, but that is the best I came up with. We can use the key or maybe someone can help improve the design. Also 'l' is hard to read even with {{t|key}}.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 03:05, 3 January 2023 (UTC)
:: I added a {{t|Menu icon}} to start things so others can have a go with it. Also any thoughts on the icon naming convention (their shortcut sequence), is there easier/better way? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 09:36, 3 January 2023 (UTC)
::[[User:BarelyCreative]] updated the template: {{Menu icon|b|o|l|y}}. I think it looks good, thoughts? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:40, 3 January 2023 (UTC)
:::I like that, yeah. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:29, 4 January 2023 (UTC)
::::There were some places where it didn't make sense so display every icon all the time (like step-by-step guides), so I changed it slightly to allow display of fewer icons using "num" and counting from the end: <nowiki>{{Menu icon|b|o|l|y|sep=-;|num=2}}</nowiki> {{Menu icon|b|o|l|y|sep=-|num=2}} [[User:BarelyCreative|BarelyCreative]] ([[User talk:BarelyCreative|talk]]) 09:05, 4 January 2023 (UTC)

==== Bizarre palette-swapping idea/prototype ====
No idea if this is a good idea, since it takes a bit of time to set up, and there might be some performance issues... and maybe display issues?

But take a look at this:
{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock|palette-name=amber}}

It's way to swap palettes on an image, although the image itself is a table, with each cell representing a pixel. The template itself looks like this:
<code><nowiki>{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock|palette-name=saffron}}</nowiki></code>
Input the pattern and desired palette name.

I've got a larger showcase here: [[User:Brightgalrs/Sandbox/PaletteSwapShowcase]]. Only did a rock pattern so far, but all palettes are implemented.
The major use for this would be on each stone, metal, wood, etc. type's page. The palette could be read directly from the raws. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 03:22, 24 December 2022 (UTC)

:From a technical perspective, my primary concern is indeed performance. Both on the server side and client side, a large number of tables that large (in terms of markup and cell count, that is) tend to be resource-intensive to generate and render. I saw your image-filtering experiments on [[User:Brightgalrs/vector.css]], and while that strikes me as a newer and less-backwards-compatible approach, it would probably be more resource-friendly.
:Is this color adjustment something the game is doing natively? i.e. does this accurately match what the game displays? I bet we could slap together an image-filtering extension (or find an existing one?) that can do this if needed. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:49, 24 December 2022 (UTC)
::Yeah that's what I suspected. The images the template creates are spot on, checked it against a screenshot I took of some mica rocks in-game. The css stuff is unfortunately totally incorrect, was cool to learn about it though, so not a complete waste of my time :p. The premium, in-game graphics are true sprites, basically patterns of indexed colors. Each of the in-game colors (which are significantly expanded over the 16 ascii colors, there's 116/117) there is a palette defined in "\Dwarf Fortress\data\vanilla\vanilla_descriptors_graphics\graphics\images\palettes.png". Each indexed color of the sprite is swapped for the corresponding color in the palette. Because of that, the css stuff doesn't work since it's doing the hue/saturation/brightness changes to the entire sprite.
::I've looked into an existing mediawiki extension, couldn't find anything. One thing I did't really look at is some type of lua script/module that would basically emulate what the game is doing. So some function that takes in the base image as well as the desired palette, and based on that finds and replaces each color. No idea what mediawiki's capabilities are on that front. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 05:31, 24 December 2022 (UTC)
:::We do have Scribunto installed now, so it's totally possible to do something in Lua too - forgot about that. I can add you to the group that grants access to edit the Module namespace if you want to give that a shot. If we use an extension, we'd probably need a custom one, similar to DFDiagram (or perhaps DFDiagram could be extended - it's in dire need of a rewrite anyway). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:43, 24 December 2022 (UTC)
::::I asked around on the mediawiki irc, I think scribunto/lua is a deadend, at least for taking an uploaded image and doing stuff to it with a lua script. However I did come up with this even more bizarre solution, using block elements. [[User:Brightgalrs/Sandbox/PaletteSwapShowcase2]], maybe less resource intensive? Definitely displays a lot worse though, probably unusable.
::::{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock2|palette-name=saffron}}
::::I dunno, maybe none of this is worth it and we should just write some external program to put all the images together offline, and then just mass upload. It wouldn't be ''that'' many... [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 06:37, 24 December 2022 (UTC)

====Is there an easy way to just paste images from the clipboard?====

I use KDE spectacle to take screenshots straight to the clipboard (after cropping) -- is there an easy way to just paste (and auto-upload) an image into an article? It would make it a lot easier to contribute images. [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 23:35, 1 January 2023 (UTC)
:Unfortunately there is not. I would be open to a MediaWiki extension to support this if someone finds one. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:32, 2 January 2023 (UTC)
:: Looks like this could do it, but I haven't used it before: https://www.mediawiki.org/wiki/Extension:SimpleBatchUpload [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 19:41, 2 January 2023 (UTC)

====Standards for adding graphical version screenshots and images====

Hello, new user looking into adding imagery from the new version. Is there a standard for quality of new screenshots or images? I noticed that at a certain zoom level (2 zooms in from the furthest zoomed-out view), the graphics appear crisp and 1:1 pixel scaled, and I would propose that all images be taken at this scale whenever possible. If they need to be displayed larger, they should be nearest neighbor scaled in a photo editing program at 100% increments (Microsoft Paint will do this if you first select the image rather than directly scaling the whole canvas). I would also propose that images should be cropped to conform to the 32x32 pixel grid when possible, though this could be problematic with so many new graphical elements exceeding the bounds of their tiles. I would say the best practice for capturing artwork for items, furniture etc. ought to be done in a 3x3 open area to avoid shadows from nearby walls, or else extracted from the raw files (if this doesn't run afoul of being able to re-create the graphical version using those assets).

I know that perfect is the enemy of good, and any documentation is better than none, but just thought I'd ask about this, and see if/where something like this ought to be posted. [[User:Unclesporky|Unclesporky]] ([[User talk:Unclesporky|talk]]) 13:58, 3 January 2023 (UTC)
:It has been stated in [[Template:V50 workshop]] that <q>screenshots should be at the "native" resolution</q> but someone could edit the [[Screenshot]] page for best practice for the steam version. Or post some examples in [[Talk:Screenshot]] to find out what is best? --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 14:21, 3 January 2023 (UTC)

====How would I/should I go about putting creature sprites on their pages?====

Howdy. New player and wiki user here. I wanted to try and help update the wiki to the Steam release of DF, so I figured I'd chip in by putting each creature's sprites on their respective page, since I'll often look up a creature I have yet to see in game only to be met by a blue J, or whatever. I found all of the game's creature sprites in C:\Program Files (x86)\Steam\steamapps\common\Dwarf Fortress\data\vanilla\vanilla_creatures_graphics\graphics\images, so I figured I could just chop those up in Photoshop and stick them on here no problem, but the programming syntax/whatever it is on this site is incredibly confusing, I don't know how I'd actually go about doing it. I figured I'd just find the spot on the page where the little letter is and replace that with the image code, but it seems the pages are built using heavily nested templates that I can't even begin to understand. Any help?--[[User:Treese|Treese]] ([[User talk:Treese|talk]]) 03:07, 5 January 2023 (UTC)
:Based on [[User:Zippy|Zippy]]'s work at {{tl|Creaturelookup_b}}, I added an "image" parameter to {{tl|creaturelookup/0}}, which is what creature pages should all be using. See [[Dwarf]] and [[Cow]] for examples. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:37, 5 January 2023 (UTC)

=== Hotkeys/Menu navigation ===
Most key bindings and menus have changed. Should the article reflect a) only the old version, b) only the GUI version or c) both? For example, [[Bridge|bridges]] used to be built via {{k|b}} -> {{k|g}}, but now it's in Place strucutures {{k|b}} -> Constructions {{k|n}} -> Bridge {{k|b}}. What should be written in the article? Currently, it's {{k|b}} -> {{k|g}}. I ''think'' it should be only b), but I am not sure if there will be differences regarding hotkeys or menus between the premium version and the free version and then, c) would be the most appropriate option. --[[User:Prometherus|Prometherus]] ([[User talk:Prometherus|talk]]) 10:16, 22 December 2022 (UTC)

: Not sure. I wish the classic release soon --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 16:45, 22 December 2022 (UTC)
:: Are you Toady's herald? Looks like it was just released! [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:18, 22 December 2022 (UTC)
:: And our questions are answered, the old hotkeys seem to have been thrown out. Part of me is disappointed (useless muscle memory) but also relieved (unified UI for both versions is good in general and for the wiki). [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:25, 22 December 2022 (UTC)
::: According to info, in a sort of 'demo version' at that. I'll wait a little while longer, for myself.[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 18:22, 22 December 2022 (UTC)
::::It's unlikely that keybindings in it will change significantly. My vote is that we should include information for both premium and classic, everywhere. Hopefully the keybindings are not different between versions. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 18:26, 22 December 2022 (UTC)
:::Shouldn't it be based on the 50 or what verion the article is written for? [[User:Dominick|Dominick]] [[User_talk:dominick|(TALK)]] 18:42, 22 December 2022 (UTC)
:::: The keybindings seem to be consistent between versions, (haven't checked exhausitvely, but since the menu layout is the same I think it is a good assumption). Should also keep in mind/consider that not all actions have keybindings. An option would be write 'Click on the <Example Text> icon or press {{k|E}}' [[User:Koos|Koos]] ([[User talk:Koos|talk]]) 23:14, 23 December 2022 (UTC)

=== Removed features & concepts ===

Since they're removed concepts, I've set [[Room]] to be a redirect for [[DF2014:Room]] and created [[Template:Activity zones]] for the nav bar bedrooms, etc, and made the necessary changes to [[Bedroom]] for it. Is this the correct approach, before I go on much further? (also a note, if it is, then [[Template:v50_rooms]] probably needs to be deleted) I also imagine that considering the number of changes in the interface, that things like [[Adventure mode]] and related pages might best be truncated to "not in 50.03" and when it does make it across, being more deliberately brought over in pieces? [[User:HawkOwl|HawkOwl]] ([[User talk:HawkOwl|talk]]) 06:23, 23 December 2022 (UTC)

:Usually it is marked with [[Template:Removed_feature]]. For example: [[Dipscript]] or [[Party]]. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:45, 23 December 2022 (UTC)

:: Ah, that's fair. Should that be mentioned in [[Dwarf_Fortress_Wiki:Versions#Redirects]]? [[User:HawkOwl|HawkOwl]] ([[User talk:HawkOwl|talk]]) 10:03, 23 December 2022 (UTC)

:::I think the redirect policy mostly had in mind things that were removed a ''long'' time ago, like [[Tax collector]] and [[Economy]] (and the latter actually has a stub page as well). I guess we could clarify. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:34, 23 December 2022 (UTC)

:::: The "current" redirects also cause the version box to incorrectly show that the current version has a page - e.g. [[23a:Cave_river]] shows a v50.04 version, but it's just a redirect back to that version. Similarly, what should happen to redirects like [[Clothes maker]], where a concept has evolved? It currently goes to [[23a:Clothes maker]] - that's correct if the user is trying to look up a very old concept, but if a new user is looking for "how to make clothes", they should be directed to [[Clothier]]. --[[User:Danny252|Danny252]] ([[User talk:Danny252|talk]]) 12:16, 26 December 2022 (UTC)

:::: One should be careful with cv redirects. Most that were recently adjusted were unused plural forms (that should probably be deleted) but few like [[Crown]] needed that for backward compatibility. Removing the [https://dwarffortresswiki.org/index.php?title=Crown&type=revision&diff=279966&oldid=219482 cv part] means the the link on [[v0.31:Tilesets]] is now broken. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 22:30, 26 December 2022 (UTC)

:::::If [[v0.31:Tilesets]] is about v0.31, it should not be using "main:" in its links - ''all'' of those links are going to pages about v50, not v0.31, regardless of whether the target is a redirect or not. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:37, 26 December 2022 (UTC)
:::::: You right, I removed it. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 17:55, 27 December 2022 (UTC)

Crown cv redir issue is now fixed, I believe. As goes with such cases where one can simply revert the troublesome edit, unless I've mistepped, myself? [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 23:52, 26 December 2022 (UTC)
:Both [https://dwarffortresswiki.org/index.php?title=Crown&diff=prev&oldid=280026] and [https://dwarffortresswiki.org/index.php?title=Crown&diff=prev&oldid=279966] should not have had any effect, because "cv" is an alias to the main namespace now, just like "main". Proof: [[Crown]], [[cv:Crown]], [[main:Crown]]. It's possible caching is coming into play here, although I purged the redirect cache after making that alias change earlier this month... —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:02, 27 December 2022 (UTC)

I think there have been some changes not captured, but as a newb, I'm afraid to edit the page(s). A good example is Strawberry. I'm playing the Steam version right now and Strawberry plants are "not relevant to brewing" in Labor > kitchen > veg / fruit / leaves. Unless I'm mistaken and need to process them? Another example is the trade caravan = it seems the 3 square pathing no longer happens; it's just yak(s). 12:31, 28 December 2022 (UTC) 12:29, 28 December 2022 (UTC)
:Strawberries should be brewable according to the Raws.
:Trade wagons has been modified in v50. The first wagons will arrive at the same time your fort is becoming a barony. Until then, it's only pack animals and stairs are indeed fine. The [[Trading]] page needs a huge rework anyway... I'll try to do that next week. --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 13:40, 2 January 2023 (UTC)

<s>As far as I can tell, none of the workshop buildings in v50 have blocking tiles any more. There's a comment to the like in data/vanilla/vanilla_buildings/objects/building_custom.txt that says this "[BLOCK:1:0:0:0] workbenches no longer block". Hesitant to update that template as I'm not sure if it's referenced for all of the old versions too. </s> [[User:AndrielChaoti|AndrielChaoti]] ([[User talk:AndrielChaoti|talk]]) 05:54, 29 December 2022 (UTC)
: A new template has been created: {{tl|V50 workshop}} --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 13:40, 2 January 2023 (UTC)
::Thanks! In general, I would like to delegate the switching responsibility to the template (like how {{tl|creaturelookup/0}} works), but in cases where the parameters diverge significantly like with workshops, it could make sense to make an entirely new template. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:40, 3 January 2023 (UTC)

=== creature infobox prototype (moved) ===

Check it out, I made a temporary template and added it to the [[cow]]s page. Now it shows the sprites (but not the zombified versions yet). I wanted to show everyone a prototype of what v50 creature infoboxes should look like. Or at least something similar to it. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 19:11, 27 December 2022 (UTC)
:Hi, I'm new to editing wikis but I have done a bit of work with sprite sheets and I've been going through the DF data files to find the different graphics hoping to help with the animal pages. I've thrown together a template with grass and a few nature sprites (plants, a tree, and a rock) for size reference but I'm unsure how large the 'display' tiles in the middle of the template should be to suit all animals. I can see in the sprite sheets that some land animals have an adult and child sprite, so two tiles. Others have a male, female, and child, but after seeing you include the zombie cows I'm unsure if I should make it twice the size to add them too. Alternatively, I could grab some tiles from the haunted biomes for the zombie animals and make a separate template for a side-by-side comparison. Either way, let me know if this helps. I'd like to help with other graphics too as we add the premium tilesets but the animals seemed the easiest to tackle with me being new to wiki editing. ~~[[User:UristTheSeventh|UristTheSeventh]] ([[User talk:UristTheSeventh|talk]])
::@Zippy, I am a bit perplexed about the purple cows. Why do we need a zombified version of creatures on every page?
::@UristTheSeventh, we can use all the help. Maybe post an example, so that we can have something to compare and contrast.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 11:49, 3 January 2023 (UTC)
:::@Jan Here are the examples:
:::[[File:Creature template.png]] [[File:Armadillo.png]] [[File:Seagull.png]]
:::It'll need to be wider or arranged differently for different creatures with more that two sprites or for multi-tile creatures. I can also do an aquatic and air themed template for swimming and flying creatures. ~~[[User:UristTheSeventh|UristTheSeventh]] ([[User talk:UristTheSeventh|talk]])
::::Looks nice, like the metal template. There are several people working on updating the graphics you should talk more among yourselves. Best I can offer is that I width wise I am hoping to go up to 200px for infoboxes.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 01:13, 5 January 2023 (UTC)

=== When do we remove the migration note on specific pages? ===

At what point can we remove the "this page was auto migrated from v47" warning? There are a bunch of small pages that are more or less accurate, if I've reviewed them, can I go ahead and remove the warning? [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 23:33, 1 January 2023 (UTC)
:Yes, feel free to remove it if you think all content is accurate. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:31, 2 January 2023 (UTC)

=== Any info on fixing "creature description not found?" ===

I see this issue on most creature pages, it seems to be due to a lookup that's not currently functioning? Cows interestingly doesn't have this issue but I couldn't figure out how to recreate whatever fix it's editor did. --[[User:Yallendallis|Yallendallis]] ([[User talk:Yallendallis|talk]]) 00:22, 3 January 2023 (UTC)
:That is the missing raws issue described above. Cow was fixed by the addition of [[cow/raw]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:28, 3 January 2023 (UTC)
::Ah makes sense, not fully used to the language of wikis yet so I read over it while looking. To put this bit of questioning to rest for any future readers, is it correct that it's fine to update any raws manually, though it will be done automatically at some point? --[[User:Yallendallis|Yallendallis]] ([[User talk:Yallendallis|talk]]) 07:48, 3 January 2023 (UTC)
:::Yes. I'm circling back to work on a script right now, so not much point in doing it if you're reading this. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:57, 4 January 2023 (UTC)
:::This should be fixed now. If you continue to see pages with problems, you can try [https://www.mediawiki.org/wiki/Manual:Purge purging the cache]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:59, 4 January 2023 (UTC)

=== Adventurer Mode related sections ===

The topic has already been discussed [[#Removed features & concepts|above]], but I don't see a clear line on what to do with article sections that mention Adventurer Mode. Like for example in [[Butcher#Adventurer_mode|Butcher]].

'''a) Truncate''' or '''b) leave in place with a mention''' that the mode is not yet present IG but will be added in a future update?

Personally I think option b) is better, because I think it's silly to undo some work just to reintroduce it a few weeks later, with the necessary corrections. Even if a copy/paste of a previous version takes ~15 seconds, considering the number of articles that need to be corrected, it would be a bit of a waste of time.--[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 14:22, 3 January 2023 (UTC)

== Toggleable image ==

Any objections/comments to using this template for now for toggling between classic and premium images? I'd probably rename it to "Template:Premium-classic thumb image". I'm sure someone can come up with a better UI eventually, but should be easy to migrate at that point. I also think we should use the same customtoggle class for this and for the infobox. [[User:NiftyManiac|NiftyManiac]] ([[User talk:NiftyManiac|talk]]) 23:12, 1 January 2023 (UTC)

{{User:NiftyManiac/Sandbox/TemplateDualImage|
premium=File:Quickstart-finder.png|
classic=File:Quickstart-finder-partial.png
}}

{{User:NiftyManiac/Sandbox/TemplateDualImage|
premium=File:Quickstart-finder.png|
classic=File:Quickstart-finder-partial.png|
caption=My caption|
width=100px
}}

:This looks nice to me! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:30, 2 January 2023 (UTC)

: Good initiative. From the top of my head:
:* I suggest using a shorthand, no one wants to type 'Premium-classic thumb image'.
:* If we end up using toggle for infoboxes (not sure where we headed there), then I agree definitely same custom toggle class should be used for all, thus allowing to switch premium-classic view on the whole page at a click.
:* The button part on a separate row isn't pretty, creating a lot of dead space that can be used by the text. Are we set on the label 'toggle ascii'? Classic isn't Ascii per se, maybe we can use a 'toggle' with a tooltip {{tooltip|for example|does bla bla bla}}, or maybe we can get rid of the text and have a smaller icon button ([[User:Jan/sandbox#Metal_example|two examples]]).
: I hope that helps. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 11:21, 2 January 2023 (UTC)

:: I added [[Template:Dual image]] with some of your suggestions. Agree that it's not super pretty, feel free to try something different.

::* I put the toggle in the caption mostly because I gave up on trying to make a more sophisticated replacement for the default thumb image behavior, I'm sure someone with better wiki-fu could put together something more intelligent.
::* I cut the text down to just "Toggle"; I think the best solution would be a small graphic showing the old and new dwarf icons with arrows between them. [[User:NiftyManiac|NiftyManiac]] ([[User talk:NiftyManiac|talk]]) 19:21, 2 January 2023 (UTC)

{{Dual image|
premium=File:DFwiki5by53by3farm.png|
classic=File:Quickstart_layout_3.png|
width=100px|
caption=A 5x5 room with a 3x3 farm plot
}}
::: I updated the layout, now it should look just like a regular image thumb. I didn't had time to test it, if it doesn't work for you or you don't like it just revert the last change. cheers. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 21:46, 2 January 2023 (UTC)
::::I don't know which part of this talk page to put this, but I added the ability to add icons to the v50 workshops template. Leaving the icon part blank will not break the template in any way. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 09:47, 3 January 2023 (UTC)
{{clear}}
==Creature List Now Supports Graphics!==
I wasn't easy, but I made new templates so the [[Creature]]s page now supports both graphics sprites ''and'' ASCII tiles. Allow me to show you:

{{v50_creaturecurrent_table_head}}
{{v50_creaturecurrent table row|graphic=[[File:dwarf_sprite.png]]|name=[[Dwarf]]|symbol=☺|color=3:0:0|playable=Fort, Adv|hostile=No|food=No|size=60,000|value=Not tameable|biome=[[Mountain halls]], [[Fortress|dwarf fortress]]es, [[hillock]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:elf_sprite.png]]|name=[[Elf]]|symbol=e|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=60,000|value=Not tameable|biome=[[Forest retreat]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:human_sprite.png]]|name=[[Human]]|symbol=U|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=70,000|value=Not tameable|biome=[[Town]]s and cities|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:goblin_sprite.png]]|name=[[Goblin]]|symbol=g|color=7:0:0|playable=Adv|hostile=Usually1|food=No|size=60,000|value=Not tameable|biome=[[Dark fortress]]es and [[dark pit]]s|note=Snatchers2}}
{{v50_creaturecurrent table row|graphic=[[File:kobold_sprite.png]]|name=[[Kobold]]|symbol=k|color=6:0:0|playable=Adv|hostile=Usually1|food=No|size=20,000|value=Not tameable|biome=Caves|note=Skulking race}}
|}

Oh wait, there's a bonus. You can also modify the background color of the box the sprites go in. I added that to make possibly-hard-to-see-otherwise sprites more easy to see - depending on the colors it has. Allow me to demonstrate.

{{v50_creaturecurrent_table_head}}
{{v50_creaturecurrent table row|graphic=[[File:dwarf_sprite.png]]|bgcolor=#829ccc|name=[[Dwarf]]|symbol=☺|color=3:0:0|playable=Fort, Adv|hostile=No|food=No|size=60,000|value=Not tameable|biome=[[Mountain halls]], [[Fortress|dwarf fortress]]es, [[hillock]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:elf_sprite.png]]|bgcolor=#c7dfc0|name=[[Elf]]|symbol=e|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=60,000|value=Not tameable|biome=[[Forest retreat]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:human_sprite.png]]|bgcolor=#c7dfc0|name=[[Human]]|symbol=U|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=70,000|value=Not tameable|biome=[[Town]]s and cities|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:goblin_sprite.png]]|bgcolor=#dfc0c0|name=[[Goblin]]|symbol=g|color=7:0:0|playable=Adv|hostile=Usually1|food=No|size=60,000|value=Not tameable|biome=[[Dark fortress]]es and [[dark pit]]s|note=Snatchers2}}
{{v50_creaturecurrent table row|graphic=[[File:kobold_sprite.png]]|bgcolor=#dfc0c0|name=[[Kobold]]|symbol=k|color=6:0:0|playable=Adv|hostile=Usually1|food=No|size=20,000|value=Not tameable|biome=Caves|note=Skulking race}}
|}

To change the background color, add <code><nowiki>|bgcolor=COLOR</nowiki></code> segment after the <code><nowiki>|graphic</nowiki></code> part. You can use color names or HTML hex color codes. I added this to the v50 creatures page, but at this time, I only added the first five creatures I just displayed. It's gonna take a while to find ALL of those creature sprites. I hope a lot of people help out on that one. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 05:29, 5 January 2023 (UTC)

:Thanks, looks nice! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:44, 5 January 2023 (UTC)
:Nice stuff, took the quick liberty to change the padding-left -> text-align to make all the sprites center aligned relative to each other :) Sweet work --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 17:41, 5 January 2023 (UTC)
:: Good work indeed. One minor issue, is that all the sprites have different sizes, which sometimes create slight variation in table row height. Consider using capping the image size vertically for example <code><nowiki>[[File:dwarf_sprite.png|x32px]]</nowiki></code>--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:15, 5 January 2023 (UTC)
:: Also often in such tables people want to click on the image to go for the specific entry, and often will try to click on the very first thing they see in line the thumb image, but currently that will take them to the file page. Consider adding link parameter for example: <code><nowiki>[[File:dwarf_sprite.png|x32px|link=dwarf]]</nowiki></code> [[File:dwarf_sprite.png|x32px|link=dwarf]] or no link at all <code><nowiki>[[File:dwarf_sprite.png|x32px|link=]]</nowiki></code> [[File:dwarf_sprite.png|x32px|link=]] --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:24, 5 January 2023 (UTC)

Dwarf Fortress Wiki talk:Versions

2023-01-05T18:24:27Z

Jan: /* Creature List Now Supports Graphics! */

{{archive|
# [[DF Talk:Versions/Archive 1|Page 1]]}}

== Version 0.31.19 starts a new DF generation? ==

My reading of Toady's comments on the release of 0.31.19 is that it came out basically because he felt it would take too long to get DF all the way to 0.32. With the ore changes, the sitefinder changes, the addition of grazing and several different industries, there's a lot of changes between 31.18 and 31.19. So I'm thinking it might be a good idea to call it the first release of DF2011 - and what we refer to as "DF2010" would then become 0.31.18.

Thoughts? --[[User:DeMatt|DeMatt]] 07:06, 28 February 2011 (UTC)

==Revisiting Redirects==
I wasn't around when the redirect policy was created, and I'm having trouble understanding the rationale. The example claims that linking [[Main:Cheese]] to [[cv:Cheese maker]] is problematic...but mainspace only ever redirects to the current version. If the best target in the current version is cheese maker, why not link to it directly? (It's not, at least for Cheese, since [[DF2012:Cheese]] exists now.) The explanation seems to be claiming that 40d articles that link to Cheese will follow the Mainspace link--but that hasn't been the case for a long while now. Articles in 40d automatically link against other articles in 40d, so that version remains internally consistent no matter where mainspace links to in the current version. For a current example, what do we gain by linking [[Main:Mead]] to [[cv:Mead]] and linking [[DF2012:Mead]] to [[DF2012:Alcohol]]?

If this really is just an outdated procedure, I recommend we drop the mummery and allow mainspace to link to cv:(best target). Double redirects ''may'' work (sometimes, but [[Main:Mead]] demonstrates a common problem where automatic redirection fails), but if they are unnecessary I think they should be avoided, partly because of problems like [[Main:Mead]] and partly because of the effort required to protect double redirects from users who believe they are problematic.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:16, 8 January 2014 (UTC)

:I was just thinking that. I'm currently attempting to write a basic extension to eliminate the need for mainspace redirects entirely, although Mediawiki's class structure may make this more difficult than I had hoped (the only method I've found for resolving redirects takes the ''article text'' instead of a title, e.g. "#REDIRECT ..."). I do agree that the current situation with redirects isn't ideal, so I'm hoping this will work better (once I get it to work). --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:42, 8 January 2014 (UTC)

Okay, that wasn't quite as clear as I meant it to be. In general, I think this is a tricky situation. Mediawiki wasn't designed to have five content namespaces, and certainly not chains of redirects between them. The problem that was pointed out in the [[DF:REDIR|policy]] is the fact that with:
Main:Foo -> cv:Bar
pages in the cv: namespace can't use [[<nowiki/>foo]], since the namespace links modification causes it to be treated as [[<nowiki/>cv:foo]] instead, which doesn't exist. The current suggested solution is this:
Main:Foo -> cv:Foo -> cv:Bar
This fixes the problem of [[<nowiki/>foo]] not working on cv pages, but creates issues with double redirects not always working. Another solution, which is more intuitive to new editors, is:
Main:Foo -> cv:Bar
cv:Foo -> cv:Bar
Both require creating two redirects. The first method has the advantage of ''ensuring'' that the cv redirect exists (otherwise, main:foo would be a redlink), while the second has the advantage of working more reliably in a couple cases.

What I'm trying to do is make main:Foo "jump" to cv:Foo when cv:foo exists, ''even if main:foo doesn't exist'' (basically it would treat all mainspace pages as redirects to cv pages, but only if the cv page exists and not the mainspace page). I had main:Bar jumping to cv:Bar fine, but if cv:Foo redirected to cv:Bar, accessing main:Foo would mysteriously stop at cv:Foo even if I increased the redirect limit. What I'm trying to do now is follow the redirects internally, without relying on Mediawiki to do it automatically - unfortunately, that has proved to be harder than I had hoped (and I sent my web server into an infinite loop while trying). I will try to work on this some more when I get a chance, although I'm not sure when that'll be yet :(. For now, feel free to fix broken double mainspace redirects as necessary, as long as redirects in the DF2012 namespace stay pointing to the right page (and new mainspace redirects get added in the DF2012 namespace too). --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:21, 9 January 2014 (UTC)

:You're treating cv like a namespace--it's not. It is simply shorthand for "fill in the current version here". [http://dwarffortresswiki.org/index.php?title=User_talk:Briess&diff=182404&oldid=181281 As I discovered a long time ago on a server not far away], linking from Main:Foo to cv:Foo tends to break redirection chains. If, instead of linking to cv:Foo, you link to DF2012:Foo, it might just work. It would, of course, be better if your patch could evaluate cv itself, but even if you have to hardcode the current version it's a single point of maintenance that requires update very infrequently. (For that matter, we could probably dispense with the cv hack entirely and just have a bot update mainspace links from DF2012 to DF201X when we switch to a new version.)--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:05, 9 January 2014 (UTC)
::I know cv isn't a namespace - I was just trying to avoid future confusion when the DF2012 namespace changes. It's interesting that changing "cv" to "DF2012" fixes some broken redirects, although I've found that simply making an edit to a broken redirect can usually fix it as well. I've actually had the most problems with double redirects when the second one (in the DF2012 namespace) doesn't use the DF2012 prefix (e.g. main:Foo containing <nowiki>[[cv:Foo]] and DF2012:Foo containing [[Bar]]</nowiki>). I'd rather keep the cv alias even if it isn't necessary for mainspace redirects when I get the patch to work, since it makes it easier to refer to the current version of the page (for example, several MDF articles contain links to a vanilla page for things that don't change in the mod).
::Also, using aliases like "cv" is supported by Mediawiki; in fact, several WMF wikis use them (for example, "[[wikipedia:WP:Redirects|WP:Redirects]]" on Wikipedia). It's quite likely that Mediawiki isn't processing double redirects using aliases correctly, though, since that's uncommon on most wikis. --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:35, 9 January 2014 (UTC)

In light of the lack of support for the current redirect policy, I propose we replace the current redirect section with:

:Mainspace article pages should use the cv: alias when redirecting to a versioned page, which will automatically update the link when a new version is released. For example, page "Main:Foo" should redirect to page "cv:Bar" (where "Bar" is the page that best describes the topic Foo in the current version).

:Pages in mainspace should only redirect to an older versioned page if that content no longer exists in the current version of the game (e.g. [[Cave river]], [[Chunk]]). In these cases the cv: alias cannot be used.

:Pages inside a versioned namespace should not use the cv: alias. Instead, they should redirect to the best page within that versioned namespace (e.g. [[DF2012:Dodging]], [[v0.31:Drink]]).

:Due to limitations of the wiki software, double redirects should be avoided if possible. When fixing double redirects in mainspace, please make sure to use the cv: alias as appropriate.

If no one objects, I will make this change in a few days.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:21, 15 January 2014 (UTC)

:Okay with me. It may be worth mentioning that double redirects only really need to be changed when they don't work (since changing a lot of redirects that work isn't necessary), but I think it's clearer and more relevant than the current policy. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:26, 16 January 2014 (UTC)

Done.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:55, 22 January 2014 (UTC)

I was finally able to get my extension to work after being motivated by one too many malfunctioning redirects. It now causes nonexistent pages in the main namespace to behave exactly like redirects to their DF2012 counterparts (when linked to, accessed directly, and transcluded). Double redirects also work (up to 100, in fact, although that was a temporary safety measure that I'll probably change). This means we'll be able to safely get rid of all mainspace redirects (redirects that redirect to something other than "cv" will still function if not deleted). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:20, 14 March 2014 (UTC)
:What about articles which don't exist in the current version but do exist in older versions? Will those still need mainspace redirects, or will your extension be able to automatically redirect them to v0.31/40d/23a? --[[User:Quietust|Quietust]] ([[User talk:Quietust|talk]]) 01:29, 14 March 2014 (UTC)
::It ignores all mainspace pages that actually have content, including redirects, so pages like [[masons guild]] won't be affected (unless deleted). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:47, 14 March 2014 (UTC)

Done and deployed. [[Cat]] is still treated as a redirect, even though I just deleted it (try clicking on the "redirected from" link). Pages that exist are ignored, so [[Masons guild]] and [[History of Dwarf Fortress]] still function normally (as a redirect to a 23a page and a non-redirect, respectively). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 18:57, 14 April 2014 (UTC)

I'm sending around a bot right now to delete all redirects of the format "foo -> cv:foo" (a surprising number don't fit this format, so I'm leaving them alone for now). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:43, 14 April 2014 (UTC)

:I'm confused. Do we use double redirects or not? Is there a single place we define our linking policy (including redirects), and is it updated?
:I had trouble linking to [[Consolidated_development]] in [[v0.34:Dragon]]. It kept pointing to v0.34:Consolidated_development, which does not exist. I ended up linking to Main:Consolidated_development to make it work. --[[User:Nahno|Nahno]] ([[User talk:Nahno|talk]]) 10:18, 1 July 2014 (UTC)

::That's a separate problem altogether - links in the versioned namespaces (v0.34, v0.31, 40d, 23a) automatically link to pages within their namespace. I may be able to set up a fallback to mainspace once I'm able to deploy again, but for now the "main:" alias is the intended solution. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 11:36, 1 July 2014 (UTC)

== Google often directs people to the 0.31 page ==

I've noticed a couple of times that finding a wiki page from an external search will often drop me onto a page from an older version. Is it possible to mitigate this somehow for new players? I could imagine something like redirecting old:Bar -> cv:Bar unless the user has come from old:Foo; no idea if that would actually work though. [[User:PeridexisErrant|PeridexisErrant]] ([[User talk:PeridexisErrant|talk]]) 11:48, 4 May 2014 (UTC)

:As a temporary solution, I could write a script that displays a banner of some kind if the user came from an external site. I'll ask Briess if he can do anything on the server level to increase the weighting of the current version's pages. (Obviously there are situations where people are looking for old pages, like [[23a:dungeon master]], so we don't want to disable indexing entirely on old pages.) —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:03, 4 May 2014 (UTC)

== DF2014? ==

As Toady [http://www.bay12games.com/dwarves/ draws closer to a new release], it might be worthwhile to discuss the addition of a new version to the wiki. The upcoming release covers two years of changes and introduces a number of new plants, foods, drinks, multi-tile trees, climbing, jumping, etc., so it is likely to have significant changes from the current DF2012. To avoid having people start new pages (and lose all the effort spent refining the prior version's page), I think it would be best to have a bot automatically copy over the DF2012 pages as a starting point for DF2014. I would suggest that these copied pages include a noticebox template mentioning that the content may be outdated, so that we can easily track which pages have been reviewed. I think either the {{tl|version check}} or {{tl|old}} template would work. --[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 19:43, 5 May 2014 (UTC)

:This is what [[User:QuietBot]] did after the 0.34 release, so it's certainly possible to use the same script to migrate to DF2014. I would like a way of tagging migrated pages, since inaccuracies in some pages went unnoticed for months after they were migrated. Since {{tl|old}} is already in use, {{tl|version check}} may be a better solution (it can be reworded slightly, or we can make a separate template for DF2014 migration). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:23, 1 June 2014 (UTC)
:Made [[Template:DF2014 migrated]] as an example. Any thoughts? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:32, 1 June 2014 (UTC)

== Redirects inconsistency ==

Following a redirect is supposed to be exactly the same as going straight to the page it redirects to, but this actually isn't the case:
* Go to [[Seeds]] and you get [[v0.34:Seed]] (outdated)
* Go to http://dwarffortresswiki.org/index.php?title=Seeds&redirect=no and click on the link and you get to [[DF2014:Seed]] (current)
So if you search for "seed", the top result is the DF2014 version. But search for "seeds" and you get the redirect, which sends you to the outdated page instead. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 23:22, 22 February 2015 (UTC)

While I'm talking about redirects, it seems redirects to sections don't work: see [[DF2014:How do I manage my seeds and crops]]. I know MediaWiki is capable of this trick because Wikipedia does it. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 23:32, 22 February 2015 (UTC)

:I have absolutely no idea why [[seeds]] redirects to a v0.34 page - it could be a Mediawiki bug. The section links issue is due to a known issue in the redirect extension we use, which has yet to be fixed. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:01, 23 February 2015 (UTC)
:It looks like deleting both [[Seeds]] and [[DF2014:Seeds]] fixed things (by allowing AutoRedirect to handle the redirects instead). Feel free to tag any others with {{tl|bad redirect}}. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:03, 23 February 2015 (UTC)
::It gets stranger. [[Vial]] redirects explicitly to [[cv:Flask]] which displays (when you look at it with &redirect=no) as [[DF2014:Flask]], but still goes to the v0.34 version. It seems redirects interpret the cv: pseudo-namespace (or whatever it's called) in an outdated way. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 18:08, 23 February 2015 (UTC)
::I've added a note to this page about this issue. If it gets resolved, the note should be removed. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 21:04, 23 February 2015 (UTC)

==Reorganizing versions==

The internet deals with moved content... poorly. Google is still linking to v0.34 pages more than a year after the switch to "DF2014", and even the wiki software still has cached links pointing to the old version pages.

I propose reorganizing versions on the wiki to avoid moving content whenever possible. Instead of having a temporary "current version" namespace that changes occasionally, all the current information gets promoted to the Main namespace. When the next version split occurs, the Main articles as of a certain revision number can be copied to the newly-created permanent "old version" namespace, while all the current information remains in Main. This not only fixes the link rot issue, but it has a few other benefits as well: fewer administrative tasks, no lockdown (a historical version of the Main pages can be copied at any point, even if the Main articles are already modified for the new version), almost all the article history is maintained in the Main article (instead of being spread unevenly across multiple versions), no "temporary" namespaces are needed, fewer problematic long redirect chains, and hopefully less user confusion (since Main gets priority in search results, etc.).

As an example, today we would not have a DF2014 namespace (which is good because "temporary" namespaces historically disappear anyway). If you ran a search for [[seed]] you'd end up at Main:seed, which would have all the current information on seeds. The version box at the top of the page would still link to the older versions of the seed article. When a new version is released, an admin would choose a revision number and copy the Main:seed article as it exists at that revision number to v0.40:seed. That's it. One historical copy that needs little to no new editing, and zero redirections/moves.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 19:02, 27 July 2015 (UTC)

:Makes sense to me. It would involve a lot of work, though (e.g. fixing templates and categories to account for the current version being in mainspace), although that should be doable thanks to {{tl|category}}, {{tl|version switch}}, etc.. A bot could be set up to copy revisions from before a release date as well, which would be more difficult (and maybe slower) than a direct copy, but not severely. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:24, 30 July 2015 (UTC)

:Actually, there are a few issues with that, namely that there wouldn't be an easy way to distinguish between versioned and non-versioned mainspace pages. There are ways to resolve Google search priority (we can exclude pages from older versions from search engine results if there are newer versions of those pages available, for example). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:47, 6 August 2015 (UTC)

::There aren't very many non-versioned mainspace pages, and determining if a page is versioned is as simple as looking for the version template and/or categories added by the version template (e.g. copy [http://dwarffortresswiki.org/index.php/Category:Current this category] instead of Main:*). The problem with "suggesting" newer pages to Google is that they obviously aren't crawling our wiki regularly (if they were, the fact that the mainspace redirects point to new pages would automatically be picked up). Even if your Google hints worked they wouldn't do anything for all the other broken links out on the 'net.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:35, 6 August 2015 (UTC)

::: Google actually crawls the wiki constantly - we probably get crawl hits from google for a continuous block of 2-3 hours per day, each and every day. Why they are slow to update is beyond me though. I can't remember why we didn't do this initially, but there was a technical limitation involved if I remember correctly. --[[User:Briess|Briess]] ([[User talk:Briess|talk]]) 22:05, 6 August 2015 (UTC)

::: There are <meta> tags that can be used to hide pages from search results (for search engines that recognize them, that is). Searching for {{tl|av}} or [[:Category:Current]] might work, although we'd have to make sure all of the DF2014 pages include that (some pages don't, particularly some disambiguation pages, although all of them should). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:53, 6 August 2015 (UTC)

:Is there a particular reason main and current are separate to begin with?—[[User:CLA|CLA]] ([[User talk:CLA|talk]]) 00:17, 7 August 2015 (UTC)

::It's mostly intended to distinguish between versioned and non-versioned pages and make version-related templates simpler to work with, since every versioned page has a namespace. I wasn't active here in 2010 when this system was created, so Briess and Emi would know more.
::Another issue I just thought of with Loci's suggestion is categories - currently, categories like [[:Category:Animals]] are used to organize the versioned sub-categories. Sure, we can change {{tl|Category}} to categorize mainspace pages in [[:Category:v0.40:Animals]] or [[:Category:DF2014:Animals]], but that would be less straightforward because there wouldn't be a namespace with that name (until pages are migrated when a newer major version is released). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 13:05, 7 August 2015 (UTC)

:Moving current pages to the main namespace sounds like a great idea. -[[User:Jecowa|Jecowa]] ([[User talk:Jecowa|talk]]) 20:47, 4 January 2018 (UTC)

Another thought: dealing with migrating redirects could be difficult with this proposal - specifically, determining which redirects should be migrated to a versioned namespace. Redirects can't contain {{tl|av}}, at least not before ``#REDIRECT``. I ''think'' it would be possible to copy pages in two stages, though - all non-redirects first, then all redirects whose targets were also copied. Thoughts? Anything I'm missing? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:41, 27 June 2019 (UTC)

Some subpages (particularly /raw and /Edit notice) also deliberately lack {{tl|av}}, although those shouldn't be too hard to handle. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:35, 9 July 2019 (UTC)

:Redirect pages (and all other edge cases I've looked at) can be included in categories (like [[:Category:Current]]) to determine whether or not they should be copied into an archival version. But if the redirects are "properly qualified" then they can all be copied over blindly. Mainspace redirects pointing to versioned information should use a blank namespace (which will be automatically constrained to the archival namespace); mainspace redirects pointing to unversioned information should use an explicit "Main" (which will automatically link back to the unversioned page). Then, when [[[[Toady]]]] gets copied to [[[[v0.4x:Toady]]]] it will point back to [[[[Main:Toady One]]]]. Meanwhile, [[[[Beer]]]], copied to [[[[v0.4x:Beer]]]], will properly point to [[[[v0.4x:Alcohol]]]].--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:00, 14 July 2019 (UTC)

::I think qualifying redirects is the best solution here - categorizing redirects manually is another possible source of errors, since categories (or a lack thereof) would only be visible on the redirect page itself, and [[:Category:Current]] is a hidden category. Copying over mainspace redirects into versioned namespaces would also resolve some issues that have come up due to those not reliably existing currently. I should be able to set up a bot script to add "main:" to current mainspace redirects (and it shouldn't break anything, since those redirects go to other mainspace pages anyway). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:57, 14 July 2019 (UTC)

(Note: I wrote all of this without noticing the previous discussion above.) I was wondering, when the wiki creates a new namespace for a major release again, if it is possible to ''not'' create a namespace for the next current version (e.g. "DF202x") and instead have the mainspace articles (which are currently redirects) become the new cv and move the content there. Therefore, [[cv:Cat]] would just be "[[Cat]]" (or [[Main:Cat]]).

Certain namespace-related templates like [[Template:Ns/0]] would need to be changed, though nothing significant as far as I know. For most cases, any "DF2014" would be replaced with "Main" or even blank. There's also multiple extensions handling the current namespace system and they may need to be modified too, though I'm not sure if or how much. I'm guessing based on the discussions above that it will change stuff up.

My reason is the current namespace is increasingly becoming more anachronistic. "DF2014" could be misinterpreted as "this page is about the 2014 version of the game" or "this page was last updated in 2014", which I've seen a few people in forums mention. Granted that [[Template:Av]] is on the top of very article, I still think the namespace is inconsistent with the recentness of the article. But how is this related to what I'm asking for? Let's say we continue the current system: if we happen to do a new namespace change this year and create DF2020, the next major release (after graphics/UI) will be mythgen, which is estimated to take several years to develop (the Big Wait), and so the anachronism will start over again. The proposed way will prevent this from occurring for the next major release and every release thereafter.

I think the confusion with having a namespace that becomes old-fashioned overtime supersedes the confusion with not marking current versioned articles with a namespace. Most users just search "Cat" on the search bar and naturally expect to get information about the latest release of DF. So if users go a page that's just titled "Cat", they won't expect outdated info about cats from a previous release. That's how the current system works anyways. We'll be skipping the two-step process that we have now. It'll make several wiki tasks much simpler as well. Editors can create new articles for current versions without remembering to add a namespace. It'll fix any existing issues with (double) redirects; instead of [[Main:Kitten]] redirecting to [[cv:Kitten]], which goes to [[DF2014:Kitten]], which then redirects to [[DF2014:Cat]], [[Main:Kitten]] would just redirect to [[Main:Cat]]. And the cv: alias will no longer be necessary since "cv:" = "Main:" and will be forever.

There's no need to differentiate the current version and previous versions with a namespace for the current version is what I'm saying. Articles of previous versions will retain their respective namespaces. Users will still type "40d:Cat" to go to the 40d version of the article, but if they want the current version, they'll just type "Cat" (like now). The mainspace containing the "live" version of an article is natural and would create no uncertainty when browsing the wiki. And it would simplify the wiki somewhat and future-proof this anachronism problem. As a bonus, this change will also prevent web search engines from showing previous version pages when typing "DF cat" or something. (This isn't happening right now as DF2014 has been the current namespace for ~6 years, but it'll happen again when everything moves to a new namespace.)

This is the gist of it, and I may have ignored most of the problems with this proposal. I have personally wished for the whole version namespacing be made less complicated and have been seeking for a solution, and I feel like this is the best way to go about in the future. – [[User:Doorkeeper|Doorkeeper]] 21:27, 14 August 2020 (UTC)

:<s>Whoops, looks like Loci already proposed this exact thing long ago. I definitely missed that discussion and should have checked first. My apologies. I'll move my text to that section and remove this one. – [[User:Doorkeeper|Doorkeeper]] 21:36, 14 August 2020 (UTC)</s> Done. – [[User:Doorkeeper|Doorkeeper]] 21:40, 14 August 2020 (UTC)

:The main issue I have with that is that putting pages about the current version in a namespace also differentiates between those pages and pages not about ''any'' version (for example, [[Toady One]] does not need a 40d or v0.34 page). Yes, we can use {{tl|av}} to mark versioned pages, but people often forget to add that to new pages. The current system also allows determining whether a page is versioned or not from its title, which makes migrations a lot faster. Relying on {{tl|av}} would require either reading the content of every page (which would slow scripts down significantly) or cross-checking with the list of all pages including the template (feasible, but a bit more complicated, and still susceptible to missing templates). I suppose that manually fixing and migrating pages missing {{tl|av}} later wouldn't be too much work, though.
:I am definitely in favor of changing "DF2014" (or a new namespace) to "Current", though. I was in favor of "DF2014" in 2014, but I don't think it makes sense anymore, and "Current" seemed to be a popular alternative in both the DF2012 and DF2014 discussions on the matter. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:02, 16 August 2020 (UTC)

== Weird redirect behaviour ==

[[Pump stack]] redirects to [[cv:Screw pump#Pump stack]]. If you look at the redirect itself it says it redirects to DF2014 namespace, which is correct. But if you actually follow the redirect, it goes to v0.34 namespace. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 16:10, 20 August 2018 (UTC)
:Yeah, that's part of the issue described in the above section (the wiki caching part, not on Google's end.) —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 15:00, 21 August 2018 (UTC)

== v50 organization ==

Some wiki admins have had a talk on Discord and decided that the most sustainable path forward is to put content for all future versions of DF in the main namespace. We will be working on a bot to do this in the next few days. Feel free to chime in with suggestions here. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:56, 14 December 2022 (UTC)

:Is it maybe possible to do backwards-namespacing? Like we have a "Main" namespace, which people are free to update, and whenever there's a new version of DF the "Main" namespace is copied into a namespace for the then old version, much like how you'd branch a stable branch from a development branch when working with a git-project? [[User:Therahedwig|Therahedwig]] ([[User talk:Therahedwig|talk]]) 23:13, 14 December 2022 (UTC)

::Yeah, we could do that if we decide to. We were talking about doing that for v50, actually, and might still do something similar to preserve edit history if it doesn't end up being too hard to automate. Our hope is that we will not introduce new namespaces for v50 -> v5x, unless there is a serious breaking change (and hopefully there isn't one). But if we change our mind, one advantage of the type of migration you mentioned is that it can be done retroactively - we can copy historical revisions that were current at the time of the release, and would only lose some typo fixes made after the release that apply to earlier versions as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:11, 15 December 2022 (UTC)

ETA is < 24 hours. Doing some final checks on a migration script. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 07:08, 19 December 2022 (UTC)

: We should really have a task list as there are many things that change and need updating. Including but not limited to:
:* Most templates that used the previous namespace convention broke, including nav templates.
:* Many game files changed locations and their pages need to be updated.
:* Raws need to be updated.
:* Various features added, changed, removed.
:* UI has been changed -- though I am more inclined to wait for classic release to avoid extra work --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 06:56, 20 December 2022 (UTC)

"''Raws need to be updated.''" Including applying text wraparound where necessary, I suppose - more than a few of them have proven to be that special kind of...''difficult'' to navigate otherwise, shall we say? [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 12:52, 20 December 2022 (UTC)

:There is already a task list in the [[#v50 migration|section below]] that includes templates and raws, with an explanation. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:25, 20 December 2022 (UTC)

== v50 migration ==

The initial migration script is done. New content is in the '''main''' namespace, e.g. [[Cat]]. Old content is still at [[DF2014:Cat]]. History was migrated to the ''new'' (main namespace) articles.

I know several things are broken still. Please reply if you find any others:
<div style="border-left: 2px solid red">
* <s>Versioned templates haven't been migrated yet (e.g. {{tl|vermin}} on [[Ant]])</s>
** Fixed. Most were migrated by a bot.
* <s>Raws are missing on all pages that use them.</s>
** This also affects sidebars, such as on [[Cat]] and [[Microcline]].
** Update: The DFRawFunctions extension has been upgraded to include v50 raws, using the "v50:" prefix for filenames instead of "DF2014:". <s>I haven't finished a migration script to create the /raw pages themselves, but they can typically be created manually by copying the DF2014 /raw pages and changing "DF2014" to "v50" everywhere.</s> —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:20, 1 January 2023 (UTC)
** Update 2: Raws have been added for all pages! They were copied from the "DF2014" pages and had "DF2014" replaced with "v50", which appears to have worked from a spot-check, but let me know if you find any problems. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:57, 4 January 2023 (UTC)
* Some pages where the DF2014 page was a redirect to a main namespace page that contained content were migrated incorrectly.
** In this case, the main namespace page is usually a redirect to itself. This can be fixed by undoing LethosorBot's edit to the main namespace page, then copying the content to the DF2014 page.
** Update: most seem to have been fixed manually - thanks! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:41, 21 December 2022 (UTC)
* <s>Some main-namespace talk pages redirect to DF2014 talk pages. Some of these redirects work, and some (usually older ones) do not.</s>
** Fixed with a bot. Some redirects from talk pages to other deleted talk pages are now broken, e.g. [[Talk:Above_ground]] (exists) -> [[Talk:Tile attributes]] (redlink). I am leaving them like that because they redirect to where the talk page should be created, but I'm also fine with people deleting them if they really want to. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:41, 21 December 2022 (UTC)
* {{tl|quality}} for new articles is disabled (see below)
* Some links from DF2014 to Main weren't working: e.g. the version selector [[DF2014:Mason's workshop]] was linking to [[DF2014:Main:Mason's workshop]] instead of [[Main:Mason's workshop]]. I'm not sure exactly why, but I fixed it with a change to the NamespaceLinks extension. Let me know if you spot similar broken links. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:19, 21 December 2022 (UTC)
</div>

—[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:54, 20 December 2022 (UTC)
:The quality levels of the 50.03 pages seem to be missing. I'm not sure if that's covered under that first point. [[User:Trainzack|Trainzack]] ([[User talk:Trainzack|talk]]) 06:47, 20 December 2022 (UTC)
::If the the [[Dwarf Fortress Wiki:Quality]] feature can be made to work with namespace scheme change, I suggest to automatically assign the lowest quality rating to all pages, alternately add the {{tl|old}} to all pages. Otherwise there will be a lot of pages that will fall through the cracks. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 09:12, 20 December 2022 (UTC)
:::I disabled {{tl|quality}} in the main namespace because it would require some rework to make the rating script and the template work properly there. Feel free to take a stab at the template. I will see what can be done on the extension side. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:14, 20 December 2022 (UTC)
::::What needs to be done on the template side? I'm not sure I see too big of an issue leaving pages as "unknown-quality" for now (or just change the default to tattered) until we get the rating script working. Is that script up anywhere, anything that could be helped with? [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 11:10, 2 January 2023 (UTC)
:::::They're already marked as unknown. Really the only issue I know of with the template is that it doesn't show up with some of the newer skins we added, and that can be fixed by getting rid of the absolute positioning. As for the script, it can be found at https://github.com/DF-Wiki/QualityRatings, and the issue is really only with the configuration system not recognizing the main namespace as valid. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:29, 3 January 2023 (UTC)
::::::Great, I started having a crack at fixing the template with different themes. Is the preference to get some CSS going and then include it in the global stylesheet (i.e different styles per theme) or to try and get a "one size fits all" fix? —[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 08:14, 3 January 2023 (UTC)
:::::::I would rather avoid custom site-wide CSS if we can. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:29, 4 January 2023 (UTC)
::::::::I appreciate that, I think it's the simplest solution to add a few lines to common.css though. Unless there is a way to attach CSS specifically to a template, I saw a few extensions that allowed that but I'm not sure if any are present in the wiki at the moment. Regardless there already exists a class `div.topicon` that is specifically for the quality ratings, is there an issue with expanding this class to accommodate the themes? The list of themes where the quality rating display is broken/invisible: Citizen, MinervaNeue, MonoBook. —[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 21:48, 4 January 2023 (UTC)
:::::::::What do you think of moving the template out of the topicon entirely and just placing it in a div? It would take up a (hopefully) small amount of vertical space in the article. [[User:Lethosor/Sandbox/Quality_test]] is an example. Unfortunately it isn't possible to prevent other templates from displaying above the quality this way ([https://dwarffortresswiki.org/index.php?title=User:Lethosor/Sandbox/Quality_test&oldid=283883]). So maybe we do need some custom CSS after all if we want that. I'm open to trying out whatever you propose. I'm a bit worried about future-proofing against skins we add later (particularly a mobile skin) but at least MediaWiki supports skin-specific global CSS as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:33, 5 January 2023 (UTC)
::::::::::I would rather we avoid taking any more vertical space in the article. The growing block pyramid at the top, starting with version template, is annoying. If you end up placing it inside the article space please use a slim box 100% wide that would include both.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 01:19, 5 January 2023 (UTC)
:::::::::::Agreed with you Jan, however I see that as two different tasks (ArticleVersion template changes, getting quality back on pages). I made a test adjustment to the quality and it takes up a negligable amount of extra space. See [[User:Vallode/sandbox#Page_quality]] for the example, we'd be able to completely remove "topicon" (unless it is used somewhere else?) and then potentially move on to making the ArticleVersion template into a slim version on the left-hand-side instead of a large box? Let me know what you think. --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 17:35, 5 January 2023 (UTC)

It appears some pages are redirecting recursively and never resolving correctly, like the [[https://dwarffortresswiki.org/index.php?title=Character_table&redirect=no|character table]] and [[tileset repository]] 07:35, 20 December 2022 (UTC)
: Indeed, these can be caught here: [[Special:DoubleRedirects]] --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:51, 20 December 2022 (UTC)

It might be useful to change the notice title to "release information '''for editors'''" --[[Special:Contributions/142.59.195.176|142.59.195.176]] 10:26, 20 December 2022 (UTC)
:Can do. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)
::New here, hello. Should we set a date where we remove/only show the banner for logged in users. There are (some) pages that have 4 different notices about the upgrade. [[Engraving]] is one such page, the top banner states "information for editors", we then have the "this page was migrated" banner, a version selection which warns the article might be inaccurate, and a smaller banner saying the page might need to be updated. Quite a lot of screen space, I think we can start to slowly reduce the amount of warnings this coming month? [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 10:07, 2 January 2023 (UTC)
:::Unfortunately, only showing info to logged-in users is difficult with how MediaWiki caching works. In terms of reducing warnings, there is a discussion [[Template_talk:ArticleVersion#.22Note_that_some_content_may_still_need_to_be_updated..22|here]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:43, 4 January 2023 (UTC)
:::As for [[Engraving]] specifically, the {{tl|old}} banner was actually present on [[DF2014:Engraving]] as well and got carried over with the migration. I removed it, and agree that it was redundant. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:46, 4 January 2023 (UTC)

Main talkpages seem to redirect to DF2014 talk. Not sure if it is intentional but I like it, though we should pay attention when creating new discussion relating to v50 ending up there.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 14:18, 20 December 2022 (UTC)
:That's unintentional. I specifically wrote the migration script to not move talk pages, but that has the side-effect of leaving any previously-created "Talk -> DF2014 talk" redirects intact. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)

Yo Lethosor, are we adding graphic sprites for the pages in some way? Or are we waiting for you to add some sort of new template or something? I'm sure you don't need me to tell you that the current templates don't allow that. Not sure if I'm allowed to change/create any templates either, as I don't want to break things for hundreds of pages. Edit: And IF the icons are allowed, should they be left alone, or 2×-3× sized like how the Minecraft wiki does it? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 14:29, 20 December 2022 (UTC)
:Depends on which templates you mean. There are copyright concerns with uploading a premium sprite sheet, for instance. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)
::I'm not talking about uploading an entire sprite sheet. I'm just talking about individual icons for each respective page. One image for cows, one for horses, one for werebeasts, etc. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 16:50, 20 December 2022 (UTC)
:::If we do that for every creature in the sprite sheet, that's not much different (in terms of copyright) from uploading the entire sprite sheet. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:09, 20 December 2022 (UTC)
::::Is there someone we can talk to about that? We finally get this new game with graphics, and then we can't use the very graphics of the game? No matter what the rules are, I'd say that would be the stupidest thing ever. I know I'm infamous here when it comes to copyright and images and stuff, but about 80% of game wikis out there are completely unofficial, and use game file images like no one's business. I can't imagine anyone's door being knocked on if we used the game's sprites, but I won't add any here until we have a go-ahead. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 17:14, 20 December 2022 (UTC)

:::::...I've made noise in Mayday's direction on this matter, at least (prob an incorrect maneuver, ''but'').[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 17:55, 20 December 2022 (UTC)
:::::: I hope some sort of arrangement can be made so we can use the new sprites with permission/limits, just as we are using the raw files. Otherwise we are all (devs and editors alike) shooting ourselves in the foot here.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 21:07, 20 December 2022 (UTC)

:::::::I just thought of something. We're supposedly not allowed to upload entire sprite sheets, right? What if - for the time being - we just use a few of them for the purpose of testing out new infoboxes? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 21:46, 20 December 2022 (UTC)
::::::::I don't know. If someone could ask Kitfox and post the response here, that would be great. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:47, 20 December 2022 (UTC)

:::::::::I've reached out to Alexandra, but she hasn't answered yet. Until then I found these old approvals from the previous community manager, Feeona: ([http://www.bay12forums.com/smf/index.php?topic=173474.msg8243633#msg8243633 link1], [http://www.bay12forums.com/smf/index.php?topic=176640.msg8243642#msg8243642 link2]). Waiting for a newer response until we begin mass uploads is probably the politer option, but like Zippy said, it is also standard for wikis to use game sprites with less approval. I second their idea of trying it out with a few images to test the infoboxes. On the extreme off-chance (and I do think it is) Kitfox protests we can always remove these few. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 22:19, 20 December 2022 (UTC)
:::::::::And here is a third, more official statement: ([http://www.bay12forums.com/smf/index.php?topic=173474.msg8249718#msg8249718 link3]). Perhaps that address of info@kitfoxgames.com is the better channel to ask for a confirmation, rather than Discord DMs, but I will be going to bed, so it is best if someone else does that. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 22:29, 20 December 2022 (UTC)
::::::::::Thanks for tracking this down! Ok, sprites should be fine, but let's avoid uploading the entire premium tileset as a single image, for instance (as the forum thread says, "use common sense"). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:21, 21 December 2022 (UTC)
::::::::::: Looks good, permission is always preferable over fairuse, I think it is a win win for all involved. I agree that we shouldn't upload entire sprite sheets (e.g. there is no reason to upload the windmill from every direction or whole construction phase for workshops) and that there are a lot of details that needs to be ironed out through testing. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 05:07, 21 December 2022 (UTC)
:::::::::We have a green light on uploading all and any sprites. Their response to me can be seen [https://i.imgur.com/BhmHjzC.png here]. I'm sure someone else confirmed it before me. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 19:00, 21 December 2022 (UTC)

Shifting temporarily to a new issue, is the documentation of [[Template:ArticleVersion]] outdated? It would seem so to me, since the current version no longer has its own namespace, with the templates needing updating being different ones. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 18:30, 20 December 2022 (UTC)
:I think it is still accurate enough. We left open the possibility of making another namespace in the future, albeit with a different migration strategy - see [[#v50 organization|above]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:52, 20 December 2022 (UTC)

Some Changes to infoboxes might be needed. Too bad [[User:Doorkeeper]] isn't around. He did a great work with navbox project--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:52, 21 December 2022 (UTC)

I just realized that raw files aren't stored as regular wiki pages but loaded via the DFRawFunctions extension (hence the need to update). Good news it's going to be handled in bulk, consistently and relatively easy to updated. Even better it's Lethosor problem ;) Also I just realized that all the "raw files" (txt files in the new vanilla folder) are released into the public domain. Both are probably not news to the vets but I'll leave it here for those who less up to date like myself. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:35, 22 December 2022 (UTC)

: I noticed that some templates aren't working properly in the new namespace, e.g. [[Basalt]] entry had its raw updated manually but the infobox fail to show any details. Cursory look suggest {{t|layerlookup/0}} need a minor tweak. This should do the work
:: Replace: <nowiki>{{layerlookup/aux|{{{{FULLPAGENAME}}/raw}}|uses={{{uses|}}}|wiki={{{wiki|}}}}}</nowiki>
:: With___: <nowiki>{{layerlookup/aux|{{</nowiki>:<nowiki>{{FULLPAGENAME}}/raw}}|uses={{{uses|}}}|wiki={{{wiki|}}}}}</nowiki>
: Not sure what the plan and ETA with raws update so I didn't touch this high usage template for now. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 08:11, 24 December 2022 (UTC)

::Please do feel free to make this update. I am still working on a script to create the <code>/raw</code> pages themselves. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:12, 1 January 2023 (UTC)

Wouldn't it be an idea to add to the Sitenotice to remove the {{tl|migrated article}} tag when an article has been fully updated? I see many articles that seem to be updated still have the tag. And/or advise to make use of the {{tl|verify}} for sections still in need of checking? --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 10:12, 2 January 2023 (UTC)
:Probably a good shout. The "see this page" link does include the detail on removing but we should more explicitly encourage removing the banner once a page has at least been looked over. [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 11:01, 2 January 2023 (UTC)

== v50 specific issues ==
=== Graphics===
Follow up on the use of game sprites and the need to trying it out with a few images to test the infoboxes. First sprite [[:File:Beds v50.png]] was uploaded and used on [[Bed]] entry. Any thoughts? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:06, 21 December 2022 (UTC)
:Seems like it should be rearranged to be horizontal. Also, has there been a serious discussion about copyright? Full screenshots are 100% fine, but you start going into a grey area when you upload pieces of a spritesheet. I'm of the opinion that it's all fine as long as it's inconvenient to reconstruct the full sheet from the individual images. Maybe a further restriction could be you shouldn't upload any of the art unless it's used in an infobox (maybe an exception for pieces of the UI). And one more restriction could be you shouldn't show everything, like in your bed example, maybe just the wooden bed is good enough, leave out the stone and metal, especially since those can only be made from strange moods. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:43, 21 December 2022 (UTC)
::Actually, your bed image is kinda bad for showing off what a bed looks like because it doesn't show the pillow/blankets. That might point to cropped screenshots being the best path, although less convenient for the uploader, as you don't get details left out. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:46, 21 December 2022 (UTC)
::I created a new license template [[Template:Copyright game]], based it on the way the RimWorld wiki does things. Call it a prototype, but it's probably how your bed image should be labelled. Indeed, I added it to it already. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]])

::: I agree that the horizontal arrangement would suit better here and that we should strive to represent how things look in-game. Otherwise, I am not too concerned about people being able to reconstruct anything (lets just say that ''anyone'' interested in that can get the real thing from the game files), also it seem we have permission to use the sprits on top of fairuse. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 19:55, 21 December 2022 (UTC)

::: Modifying the existing template to allow the inclusion of the new sprites is easy (Something like [https://ibb.co/zFXCrjd this]?) The big question is the matter of consistency is there any exceptions that will break the format (size wise with variant bloat for example), the sprite naming format, etc --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:44, 21 December 2022 (UTC)
::: If we are going to show a variant for each material type, then maybe these should be added as separate images so we can add a tooltip for each image. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:49, 21 December 2022 (UTC)

:I've got another prototype going here and here: [[User:Brightgalrs/vector.css]] and [[User:Brightgalrs/Sandbox]]. (You'll need to add the css stuff to your own /vector.css). Basically it's a way to recolor images using css classes. No idea if there's a better way. Also, the real implementation would require a change to [[MediaWiki:Common.css]]. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 22:41, 21 December 2022 (UTC)
:Should mention, there ''is'' a different way, just upload each image 16 times, one for each coloring. But maybe that's not very elegant. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 22:45, 21 December 2022 (UTC)

: It should be noted that soon the classic edition will be released, hence one should plan to have both the Premium and classic alongside in that little space --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 03:14, 22 December 2022 (UTC)
::I'm looking into a tab extension to potentially support this in infoboxes. Perhaps [https://www.mediawiki.org/wiki/Extension:Tabs Extension:Tabs]? I tried [https://www.mediawiki.org/wiki/Extension:TabberNeue Extension:TabberNeue], but it displays a placeholder if JavaScript is disabled, which isn't great. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:22, 22 December 2022 (UTC)
::: The Neue Tabber seem to works pretty much like the old one (which fandom [https://coding-help.fandom.com/wiki/Tabber#Adding_images_into_tabbers still use]) defaulting to showing the first tab only. Quick look suggest that neue work the same, plus the notice that 'Tabber requires Javascript to function' warning? if so, and if it is a bother, then you should be able to edit out the tabberneue-noscript string in code. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 06:29, 22 December 2022 (UTC)
::: I much prefer your tabber solution, but if that fails we can also use the gallery slideshow mode. If so, beware it has no way to control image size so the images have to be maliciously uploaded using the exact same size. example:
<gallery mode="slideshow">
File:SteelSample.png
File:TinSample.png
File:ZincSample.png
File:GoldSample.png
</gallery> --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 10:19, 22 December 2022 (UTC)

==== adding premium set to Infobox ====
I am unclear where are we going with this? 
1) Will (A) tabs be implemented, (B) we be using mediawiki toggle [[Template_talk:V50_workshop|example]] for premium and classic/blocked, (c) put images side by side, or (d) something else? 
2) Also [[silver]] and [[Pig iron]] use very different image style for example. 
3) Anything else you want ? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 12:32, 30 December 2022 (UTC)

: Personally, I would love tabs to be implemented, but I think that side by side might be best for most. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 12:32, 30 December 2022 (UTC)
: Here is rough layout we can use. It should fit most buildings given the default sprite size. There is also a different floor plan for both (inspired by reddit)

{|
|- valign=top
|
{| style="width:200px; background-color:#eaecf0; border-collapse: collapse; "
|+ 5×5
|- style="border-bottom:2px solid #3366cc; "
|<div class="mw-customtoggle-infoboxtab mw-ui-button mw-ui-progressive" style="border-top-right-radius: 10px; border-top-left-radius:10px;">toggle</div>
|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|- valign=top
|colspan=2|<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">
[[File:Siege workshop.png|center|160px]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab"">
{|
|rowspan=2 style="width:50%; font-size: 125%;"|<center>{{Template:Picture Siege workshop}}</center>
|style="line-height: 1em; font-size: 125%;"|
{| style="border-spacing:4px;"
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|}
|
{| style="width:200px; background-color:#eaecf0; border-collapse: collapse; "
|+ 3×3
|- style="border-bottom:2px solid #3366cc; "
|colspan=2 style="text-align: right;"|<div class="mw-customtoggle-infoboxtab mw-ui-button mw-ui-progressive" style="float:left; border-top-right-radius: 10px; border-top-left-radius:10px;">toggle</div>{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|- valign=top
|rowspan=2 style="width:50%;"|
<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">[[File:Carpenter's workshop.png]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab""><center>
{| style="font-size: 175%; border-spacing: 0; background-color: black; border: 2px solid black"
|- 
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"| {{Raw Tile|"|7:0:0}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|{{=}}|6:0:0}}
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"|
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|]|0:0:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
|}</center></div>
|
{| style="border-spacing:5px;"
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|
{| style="width:200px; height:100px; padding:10px; background-color:#eaecf0; border-collapse: collapse;"
|+ 1×1
|- style="border-bottom:2px solid #3366cc;"
| colspan=3 style="text-align:center;"|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|-
| style="border-right: 1px dotted #545557;"|[[File:Screw_press.png|32px|center|link=]]
| style="font-size:125%;"|<center>{{Template:Picture Screw press}}</center>
| style="border-left: 1px dotted #545557;"|<center>{{Template:Floor Plan Screw press}}</center>
|}
|
{| style="width:200px; height:100px; padding:10px; background-color:#eaecf0; border-collapse: collapse;"
|+ 1×3
|- style="border-bottom:2px solid #3366cc;"
| colspan=3 style="text-align:center;"|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|-
| style="border-right: 1px dotted #545557;"|[[File:water_wheel.png|32px|center|link=]]
| style="font-size:125%;"|<center>{{Template:Picture Water wheel}}</center>
| style="border-left: 1px dotted #545557;line-height:normal;"|<center>{{Template:Floor Plan Water wheel}}</center>
|}
|}
:Any thoughts on the direction and or any and all of its elements? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 10:16, 31 December 2022 (UTC)

::I kind of like side-by-side, if it fits. If anyone wants to implement a toggle button or tabs, I would ask that that be implemented in a template for now, so that e.g. we could change a toggle button to tabs in a single place if we decide to install an extension to support that. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:14, 1 January 2023 (UTC)

::: I noticed a comment saying that [[impassable tile]] are no longer used in v50, is that true for all constructions? If so, floor plans are no longer needed, making things much easier as we can fit everything in except the 5v5 constructions like trade depot (and even these can be placed one above the other if so desired). If not, any thought on the alternative floor plan design? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:46, 1 January 2023 (UTC)

:::: None of the constructions have blocking tiles any more from my experience playing. I haven't tested siege weaponry with that stuff, but none of the workshops have it, nor does any furniture. (walls and fortifications will of course obstruct movement [[User:AndrielChaoti|AndrielChaoti]] ([[User talk:AndrielChaoti|talk]]) 18:47, 1 January 2023 (UTC)
::::: Ok, I have removed them from v50. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 23:48, 1 January 2023 (UTC)

I have added a basic side by side variant to [[Template:V50 workshop]] and [[Template:Building]] for testing, let us know if there any issues. Few notes:
* The default image naming scheme of <code>workshop-name.png</code> will likely conflict with existing images here or on commons, maybe another naming scheme should be used like <code>v50 workshop-name.png</code> as it is with ascii pictures.
* There is inconsistency in image size. If you want to use large zoomed images then toggle is best, otherwise they need to be all in native size (96px for 3x3).
* In the current version the code roughly centers the images and if there is a big image like with [[Siege workshop]] it drops to a new line --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 23:48, 1 January 2023 (UTC)

How about combining shortcut keys and the new menu icons:
<div style="color:white; font-size: large; text-shadow: -1px -1px 0 #000, 1px -1px 0 #000, -1px 1px 0 #000, 1px 1px 0 #000;">[[File:Ui b.png]]<div style="position: absolute; bottom:-14px; right:3px;">b</div>[[File:Ui bo.png]]<div style="position: absolute; bottom:-14px; right:3px;">o</div>[[File:Ui bol.png]]<div style="position: absolute; bottom:-14px; right:3px;">l</div>[[File:Ui boll.png]]<div style="position: absolute; bottom:-14px; right:3px;">l</div></div>
--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 02:24, 3 January 2023 (UTC)

:I worry that this is difficult to read (I read it as "boil" at first). I would rather use something like {{tl|k}} with a known background. What about something like this? [[File:Ui boll.png]]<div style="position: absolute; bottom:-14px; right:0px;">{{k|l}}</div> or, alternatively, using flexbox without any overlap: [[File:Ui boll.png]]{{k|l}} —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:37, 3 January 2023 (UTC)
:: Same, but that is the best I came up with. We can use the key or maybe someone can help improve the design. Also 'l' is hard to read even with {{t|key}}.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 03:05, 3 January 2023 (UTC)
:: I added a {{t|Menu icon}} to start things so others can have a go with it. Also any thoughts on the icon naming convention (their shortcut sequence), is there easier/better way? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 09:36, 3 January 2023 (UTC)
::[[User:BarelyCreative]] updated the template: {{Menu icon|b|o|l|y}}. I think it looks good, thoughts? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:40, 3 January 2023 (UTC)
:::I like that, yeah. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:29, 4 January 2023 (UTC)
::::There were some places where it didn't make sense so display every icon all the time (like step-by-step guides), so I changed it slightly to allow display of fewer icons using "num" and counting from the end: <nowiki>{{Menu icon|b|o|l|y|sep=-;|num=2}}</nowiki> {{Menu icon|b|o|l|y|sep=-|num=2}} [[User:BarelyCreative|BarelyCreative]] ([[User talk:BarelyCreative|talk]]) 09:05, 4 January 2023 (UTC)

==== Bizarre palette-swapping idea/prototype ====
No idea if this is a good idea, since it takes a bit of time to set up, and there might be some performance issues... and maybe display issues?

But take a look at this:
{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock|palette-name=amber}}

It's way to swap palettes on an image, although the image itself is a table, with each cell representing a pixel. The template itself looks like this:
<code><nowiki>{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock|palette-name=saffron}}</nowiki></code>
Input the pattern and desired palette name.

I've got a larger showcase here: [[User:Brightgalrs/Sandbox/PaletteSwapShowcase]]. Only did a rock pattern so far, but all palettes are implemented.
The major use for this would be on each stone, metal, wood, etc. type's page. The palette could be read directly from the raws. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 03:22, 24 December 2022 (UTC)

:From a technical perspective, my primary concern is indeed performance. Both on the server side and client side, a large number of tables that large (in terms of markup and cell count, that is) tend to be resource-intensive to generate and render. I saw your image-filtering experiments on [[User:Brightgalrs/vector.css]], and while that strikes me as a newer and less-backwards-compatible approach, it would probably be more resource-friendly.
:Is this color adjustment something the game is doing natively? i.e. does this accurately match what the game displays? I bet we could slap together an image-filtering extension (or find an existing one?) that can do this if needed. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:49, 24 December 2022 (UTC)
::Yeah that's what I suspected. The images the template creates are spot on, checked it against a screenshot I took of some mica rocks in-game. The css stuff is unfortunately totally incorrect, was cool to learn about it though, so not a complete waste of my time :p. The premium, in-game graphics are true sprites, basically patterns of indexed colors. Each of the in-game colors (which are significantly expanded over the 16 ascii colors, there's 116/117) there is a palette defined in "\Dwarf Fortress\data\vanilla\vanilla_descriptors_graphics\graphics\images\palettes.png". Each indexed color of the sprite is swapped for the corresponding color in the palette. Because of that, the css stuff doesn't work since it's doing the hue/saturation/brightness changes to the entire sprite.
::I've looked into an existing mediawiki extension, couldn't find anything. One thing I did't really look at is some type of lua script/module that would basically emulate what the game is doing. So some function that takes in the base image as well as the desired palette, and based on that finds and replaces each color. No idea what mediawiki's capabilities are on that front. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 05:31, 24 December 2022 (UTC)
:::We do have Scribunto installed now, so it's totally possible to do something in Lua too - forgot about that. I can add you to the group that grants access to edit the Module namespace if you want to give that a shot. If we use an extension, we'd probably need a custom one, similar to DFDiagram (or perhaps DFDiagram could be extended - it's in dire need of a rewrite anyway). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:43, 24 December 2022 (UTC)
::::I asked around on the mediawiki irc, I think scribunto/lua is a deadend, at least for taking an uploaded image and doing stuff to it with a lua script. However I did come up with this even more bizarre solution, using block elements. [[User:Brightgalrs/Sandbox/PaletteSwapShowcase2]], maybe less resource intensive? Definitely displays a lot worse though, probably unusable.
::::{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock2|palette-name=saffron}}
::::I dunno, maybe none of this is worth it and we should just write some external program to put all the images together offline, and then just mass upload. It wouldn't be ''that'' many... [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 06:37, 24 December 2022 (UTC)

====Is there an easy way to just paste images from the clipboard?====

I use KDE spectacle to take screenshots straight to the clipboard (after cropping) -- is there an easy way to just paste (and auto-upload) an image into an article? It would make it a lot easier to contribute images. [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 23:35, 1 January 2023 (UTC)
:Unfortunately there is not. I would be open to a MediaWiki extension to support this if someone finds one. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:32, 2 January 2023 (UTC)
:: Looks like this could do it, but I haven't used it before: https://www.mediawiki.org/wiki/Extension:SimpleBatchUpload [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 19:41, 2 January 2023 (UTC)

====Standards for adding graphical version screenshots and images====

Hello, new user looking into adding imagery from the new version. Is there a standard for quality of new screenshots or images? I noticed that at a certain zoom level (2 zooms in from the furthest zoomed-out view), the graphics appear crisp and 1:1 pixel scaled, and I would propose that all images be taken at this scale whenever possible. If they need to be displayed larger, they should be nearest neighbor scaled in a photo editing program at 100% increments (Microsoft Paint will do this if you first select the image rather than directly scaling the whole canvas). I would also propose that images should be cropped to conform to the 32x32 pixel grid when possible, though this could be problematic with so many new graphical elements exceeding the bounds of their tiles. I would say the best practice for capturing artwork for items, furniture etc. ought to be done in a 3x3 open area to avoid shadows from nearby walls, or else extracted from the raw files (if this doesn't run afoul of being able to re-create the graphical version using those assets).

I know that perfect is the enemy of good, and any documentation is better than none, but just thought I'd ask about this, and see if/where something like this ought to be posted. [[User:Unclesporky|Unclesporky]] ([[User talk:Unclesporky|talk]]) 13:58, 3 January 2023 (UTC)
:It has been stated in [[Template:V50 workshop]] that <q>screenshots should be at the "native" resolution</q> but someone could edit the [[Screenshot]] page for best practice for the steam version. Or post some examples in [[Talk:Screenshot]] to find out what is best? --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 14:21, 3 January 2023 (UTC)

====How would I/should I go about putting creature sprites on their pages?====

Howdy. New player and wiki user here. I wanted to try and help update the wiki to the Steam release of DF, so I figured I'd chip in by putting each creature's sprites on their respective page, since I'll often look up a creature I have yet to see in game only to be met by a blue J, or whatever. I found all of the game's creature sprites in C:\Program Files (x86)\Steam\steamapps\common\Dwarf Fortress\data\vanilla\vanilla_creatures_graphics\graphics\images, so I figured I could just chop those up in Photoshop and stick them on here no problem, but the programming syntax/whatever it is on this site is incredibly confusing, I don't know how I'd actually go about doing it. I figured I'd just find the spot on the page where the little letter is and replace that with the image code, but it seems the pages are built using heavily nested templates that I can't even begin to understand. Any help?--[[User:Treese|Treese]] ([[User talk:Treese|talk]]) 03:07, 5 January 2023 (UTC)
:Based on [[User:Zippy|Zippy]]'s work at {{tl|Creaturelookup_b}}, I added an "image" parameter to {{tl|creaturelookup/0}}, which is what creature pages should all be using. See [[Dwarf]] and [[Cow]] for examples. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:37, 5 January 2023 (UTC)

=== Hotkeys/Menu navigation ===
Most key bindings and menus have changed. Should the article reflect a) only the old version, b) only the GUI version or c) both? For example, [[Bridge|bridges]] used to be built via {{k|b}} -> {{k|g}}, but now it's in Place strucutures {{k|b}} -> Constructions {{k|n}} -> Bridge {{k|b}}. What should be written in the article? Currently, it's {{k|b}} -> {{k|g}}. I ''think'' it should be only b), but I am not sure if there will be differences regarding hotkeys or menus between the premium version and the free version and then, c) would be the most appropriate option. --[[User:Prometherus|Prometherus]] ([[User talk:Prometherus|talk]]) 10:16, 22 December 2022 (UTC)

: Not sure. I wish the classic release soon --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 16:45, 22 December 2022 (UTC)
:: Are you Toady's herald? Looks like it was just released! [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:18, 22 December 2022 (UTC)
:: And our questions are answered, the old hotkeys seem to have been thrown out. Part of me is disappointed (useless muscle memory) but also relieved (unified UI for both versions is good in general and for the wiki). [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:25, 22 December 2022 (UTC)
::: According to info, in a sort of 'demo version' at that. I'll wait a little while longer, for myself.[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 18:22, 22 December 2022 (UTC)
::::It's unlikely that keybindings in it will change significantly. My vote is that we should include information for both premium and classic, everywhere. Hopefully the keybindings are not different between versions. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 18:26, 22 December 2022 (UTC)
:::Shouldn't it be based on the 50 or what verion the article is written for? [[User:Dominick|Dominick]] [[User_talk:dominick|(TALK)]] 18:42, 22 December 2022 (UTC)
:::: The keybindings seem to be consistent between versions, (haven't checked exhausitvely, but since the menu layout is the same I think it is a good assumption). Should also keep in mind/consider that not all actions have keybindings. An option would be write 'Click on the <Example Text> icon or press {{k|E}}' [[User:Koos|Koos]] ([[User talk:Koos|talk]]) 23:14, 23 December 2022 (UTC)

=== Removed features & concepts ===

Since they're removed concepts, I've set [[Room]] to be a redirect for [[DF2014:Room]] and created [[Template:Activity zones]] for the nav bar bedrooms, etc, and made the necessary changes to [[Bedroom]] for it. Is this the correct approach, before I go on much further? (also a note, if it is, then [[Template:v50_rooms]] probably needs to be deleted) I also imagine that considering the number of changes in the interface, that things like [[Adventure mode]] and related pages might best be truncated to "not in 50.03" and when it does make it across, being more deliberately brought over in pieces? [[User:HawkOwl|HawkOwl]] ([[User talk:HawkOwl|talk]]) 06:23, 23 December 2022 (UTC)

:Usually it is marked with [[Template:Removed_feature]]. For example: [[Dipscript]] or [[Party]]. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:45, 23 December 2022 (UTC)

:: Ah, that's fair. Should that be mentioned in [[Dwarf_Fortress_Wiki:Versions#Redirects]]? [[User:HawkOwl|HawkOwl]] ([[User talk:HawkOwl|talk]]) 10:03, 23 December 2022 (UTC)

:::I think the redirect policy mostly had in mind things that were removed a ''long'' time ago, like [[Tax collector]] and [[Economy]] (and the latter actually has a stub page as well). I guess we could clarify. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:34, 23 December 2022 (UTC)

:::: The "current" redirects also cause the version box to incorrectly show that the current version has a page - e.g. [[23a:Cave_river]] shows a v50.04 version, but it's just a redirect back to that version. Similarly, what should happen to redirects like [[Clothes maker]], where a concept has evolved? It currently goes to [[23a:Clothes maker]] - that's correct if the user is trying to look up a very old concept, but if a new user is looking for "how to make clothes", they should be directed to [[Clothier]]. --[[User:Danny252|Danny252]] ([[User talk:Danny252|talk]]) 12:16, 26 December 2022 (UTC)

:::: One should be careful with cv redirects. Most that were recently adjusted were unused plural forms (that should probably be deleted) but few like [[Crown]] needed that for backward compatibility. Removing the [https://dwarffortresswiki.org/index.php?title=Crown&type=revision&diff=279966&oldid=219482 cv part] means the the link on [[v0.31:Tilesets]] is now broken. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 22:30, 26 December 2022 (UTC)

:::::If [[v0.31:Tilesets]] is about v0.31, it should not be using "main:" in its links - ''all'' of those links are going to pages about v50, not v0.31, regardless of whether the target is a redirect or not. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:37, 26 December 2022 (UTC)
:::::: You right, I removed it. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 17:55, 27 December 2022 (UTC)

Crown cv redir issue is now fixed, I believe. As goes with such cases where one can simply revert the troublesome edit, unless I've mistepped, myself? [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 23:52, 26 December 2022 (UTC)
:Both [https://dwarffortresswiki.org/index.php?title=Crown&diff=prev&oldid=280026] and [https://dwarffortresswiki.org/index.php?title=Crown&diff=prev&oldid=279966] should not have had any effect, because "cv" is an alias to the main namespace now, just like "main". Proof: [[Crown]], [[cv:Crown]], [[main:Crown]]. It's possible caching is coming into play here, although I purged the redirect cache after making that alias change earlier this month... —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:02, 27 December 2022 (UTC)

I think there have been some changes not captured, but as a newb, I'm afraid to edit the page(s). A good example is Strawberry. I'm playing the Steam version right now and Strawberry plants are "not relevant to brewing" in Labor > kitchen > veg / fruit / leaves. Unless I'm mistaken and need to process them? Another example is the trade caravan = it seems the 3 square pathing no longer happens; it's just yak(s). 12:31, 28 December 2022 (UTC) 12:29, 28 December 2022 (UTC)
:Strawberries should be brewable according to the Raws.
:Trade wagons has been modified in v50. The first wagons will arrive at the same time your fort is becoming a barony. Until then, it's only pack animals and stairs are indeed fine. The [[Trading]] page needs a huge rework anyway... I'll try to do that next week. --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 13:40, 2 January 2023 (UTC)

<s>As far as I can tell, none of the workshop buildings in v50 have blocking tiles any more. There's a comment to the like in data/vanilla/vanilla_buildings/objects/building_custom.txt that says this "[BLOCK:1:0:0:0] workbenches no longer block". Hesitant to update that template as I'm not sure if it's referenced for all of the old versions too. </s> [[User:AndrielChaoti|AndrielChaoti]] ([[User talk:AndrielChaoti|talk]]) 05:54, 29 December 2022 (UTC)
: A new template has been created: {{tl|V50 workshop}} --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 13:40, 2 January 2023 (UTC)
::Thanks! In general, I would like to delegate the switching responsibility to the template (like how {{tl|creaturelookup/0}} works), but in cases where the parameters diverge significantly like with workshops, it could make sense to make an entirely new template. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:40, 3 January 2023 (UTC)

=== creature infobox prototype (moved) ===

Check it out, I made a temporary template and added it to the [[cow]]s page. Now it shows the sprites (but not the zombified versions yet). I wanted to show everyone a prototype of what v50 creature infoboxes should look like. Or at least something similar to it. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 19:11, 27 December 2022 (UTC)
:Hi, I'm new to editing wikis but I have done a bit of work with sprite sheets and I've been going through the DF data files to find the different graphics hoping to help with the animal pages. I've thrown together a template with grass and a few nature sprites (plants, a tree, and a rock) for size reference but I'm unsure how large the 'display' tiles in the middle of the template should be to suit all animals. I can see in the sprite sheets that some land animals have an adult and child sprite, so two tiles. Others have a male, female, and child, but after seeing you include the zombie cows I'm unsure if I should make it twice the size to add them too. Alternatively, I could grab some tiles from the haunted biomes for the zombie animals and make a separate template for a side-by-side comparison. Either way, let me know if this helps. I'd like to help with other graphics too as we add the premium tilesets but the animals seemed the easiest to tackle with me being new to wiki editing. ~~[[User:UristTheSeventh|UristTheSeventh]] ([[User talk:UristTheSeventh|talk]])
::@Zippy, I am a bit perplexed about the purple cows. Why do we need a zombified version of creatures on every page?
::@UristTheSeventh, we can use all the help. Maybe post an example, so that we can have something to compare and contrast.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 11:49, 3 January 2023 (UTC)
:::@Jan Here are the examples:
:::[[File:Creature template.png]] [[File:Armadillo.png]] [[File:Seagull.png]]
:::It'll need to be wider or arranged differently for different creatures with more that two sprites or for multi-tile creatures. I can also do an aquatic and air themed template for swimming and flying creatures. ~~[[User:UristTheSeventh|UristTheSeventh]] ([[User talk:UristTheSeventh|talk]])
::::Looks nice, like the metal template. There are several people working on updating the graphics you should talk more among yourselves. Best I can offer is that I width wise I am hoping to go up to 200px for infoboxes.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 01:13, 5 January 2023 (UTC)

=== When do we remove the migration note on specific pages? ===

At what point can we remove the "this page was auto migrated from v47" warning? There are a bunch of small pages that are more or less accurate, if I've reviewed them, can I go ahead and remove the warning? [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 23:33, 1 January 2023 (UTC)
:Yes, feel free to remove it if you think all content is accurate. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:31, 2 January 2023 (UTC)

=== Any info on fixing "creature description not found?" ===

I see this issue on most creature pages, it seems to be due to a lookup that's not currently functioning? Cows interestingly doesn't have this issue but I couldn't figure out how to recreate whatever fix it's editor did. --[[User:Yallendallis|Yallendallis]] ([[User talk:Yallendallis|talk]]) 00:22, 3 January 2023 (UTC)
:That is the missing raws issue described above. Cow was fixed by the addition of [[cow/raw]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:28, 3 January 2023 (UTC)
::Ah makes sense, not fully used to the language of wikis yet so I read over it while looking. To put this bit of questioning to rest for any future readers, is it correct that it's fine to update any raws manually, though it will be done automatically at some point? --[[User:Yallendallis|Yallendallis]] ([[User talk:Yallendallis|talk]]) 07:48, 3 January 2023 (UTC)
:::Yes. I'm circling back to work on a script right now, so not much point in doing it if you're reading this. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:57, 4 January 2023 (UTC)
:::This should be fixed now. If you continue to see pages with problems, you can try [https://www.mediawiki.org/wiki/Manual:Purge purging the cache]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:59, 4 January 2023 (UTC)

=== Adventurer Mode related sections ===

The topic has already been discussed [[#Removed features & concepts|above]], but I don't see a clear line on what to do with article sections that mention Adventurer Mode. Like for example in [[Butcher#Adventurer_mode|Butcher]].

'''a) Truncate''' or '''b) leave in place with a mention''' that the mode is not yet present IG but will be added in a future update?

Personally I think option b) is better, because I think it's silly to undo some work just to reintroduce it a few weeks later, with the necessary corrections. Even if a copy/paste of a previous version takes ~15 seconds, considering the number of articles that need to be corrected, it would be a bit of a waste of time.--[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 14:22, 3 January 2023 (UTC)

== Toggleable image ==

Any objections/comments to using this template for now for toggling between classic and premium images? I'd probably rename it to "Template:Premium-classic thumb image". I'm sure someone can come up with a better UI eventually, but should be easy to migrate at that point. I also think we should use the same customtoggle class for this and for the infobox. [[User:NiftyManiac|NiftyManiac]] ([[User talk:NiftyManiac|talk]]) 23:12, 1 January 2023 (UTC)

{{User:NiftyManiac/Sandbox/TemplateDualImage|
premium=File:Quickstart-finder.png|
classic=File:Quickstart-finder-partial.png
}}

{{User:NiftyManiac/Sandbox/TemplateDualImage|
premium=File:Quickstart-finder.png|
classic=File:Quickstart-finder-partial.png|
caption=My caption|
width=100px
}}

:This looks nice to me! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:30, 2 January 2023 (UTC)

: Good initiative. From the top of my head:
:* I suggest using a shorthand, no one wants to type 'Premium-classic thumb image'.
:* If we end up using toggle for infoboxes (not sure where we headed there), then I agree definitely same custom toggle class should be used for all, thus allowing to switch premium-classic view on the whole page at a click.
:* The button part on a separate row isn't pretty, creating a lot of dead space that can be used by the text. Are we set on the label 'toggle ascii'? Classic isn't Ascii per se, maybe we can use a 'toggle' with a tooltip {{tooltip|for example|does bla bla bla}}, or maybe we can get rid of the text and have a smaller icon button ([[User:Jan/sandbox#Metal_example|two examples]]).
: I hope that helps. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 11:21, 2 January 2023 (UTC)

:: I added [[Template:Dual image]] with some of your suggestions. Agree that it's not super pretty, feel free to try something different.

::* I put the toggle in the caption mostly because I gave up on trying to make a more sophisticated replacement for the default thumb image behavior, I'm sure someone with better wiki-fu could put together something more intelligent.
::* I cut the text down to just "Toggle"; I think the best solution would be a small graphic showing the old and new dwarf icons with arrows between them. [[User:NiftyManiac|NiftyManiac]] ([[User talk:NiftyManiac|talk]]) 19:21, 2 January 2023 (UTC)

{{Dual image|
premium=File:DFwiki5by53by3farm.png|
classic=File:Quickstart_layout_3.png|
width=100px|
caption=A 5x5 room with a 3x3 farm plot
}}
::: I updated the layout, now it should look just like a regular image thumb. I didn't had time to test it, if it doesn't work for you or you don't like it just revert the last change. cheers. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 21:46, 2 January 2023 (UTC)
::::I don't know which part of this talk page to put this, but I added the ability to add icons to the v50 workshops template. Leaving the icon part blank will not break the template in any way. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 09:47, 3 January 2023 (UTC)
{{clear}}
==Creature List Now Supports Graphics!==
I wasn't easy, but I made new templates so the [[Creature]]s page now supports both graphics sprites ''and'' ASCII tiles. Allow me to show you:

{{v50_creaturecurrent_table_head}}
{{v50_creaturecurrent table row|graphic=[[File:dwarf_sprite.png]]|name=[[Dwarf]]|symbol=☺|color=3:0:0|playable=Fort, Adv|hostile=No|food=No|size=60,000|value=Not tameable|biome=[[Mountain halls]], [[Fortress|dwarf fortress]]es, [[hillock]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:elf_sprite.png]]|name=[[Elf]]|symbol=e|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=60,000|value=Not tameable|biome=[[Forest retreat]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:human_sprite.png]]|name=[[Human]]|symbol=U|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=70,000|value=Not tameable|biome=[[Town]]s and cities|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:goblin_sprite.png]]|name=[[Goblin]]|symbol=g|color=7:0:0|playable=Adv|hostile=Usually1|food=No|size=60,000|value=Not tameable|biome=[[Dark fortress]]es and [[dark pit]]s|note=Snatchers2}}
{{v50_creaturecurrent table row|graphic=[[File:kobold_sprite.png]]|name=[[Kobold]]|symbol=k|color=6:0:0|playable=Adv|hostile=Usually1|food=No|size=20,000|value=Not tameable|biome=Caves|note=Skulking race}}
|}

Oh wait, there's a bonus. You can also modify the background color of the box the sprites go in. I added that to make possibly-hard-to-see-otherwise sprites more easy to see - depending on the colors it has. Allow me to demonstrate.

{{v50_creaturecurrent_table_head}}
{{v50_creaturecurrent table row|graphic=[[File:dwarf_sprite.png]]|bgcolor=#829ccc|name=[[Dwarf]]|symbol=☺|color=3:0:0|playable=Fort, Adv|hostile=No|food=No|size=60,000|value=Not tameable|biome=[[Mountain halls]], [[Fortress|dwarf fortress]]es, [[hillock]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:elf_sprite.png]]|bgcolor=#c7dfc0|name=[[Elf]]|symbol=e|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=60,000|value=Not tameable|biome=[[Forest retreat]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:human_sprite.png]]|bgcolor=#c7dfc0|name=[[Human]]|symbol=U|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=70,000|value=Not tameable|biome=[[Town]]s and cities|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:goblin_sprite.png]]|bgcolor=#dfc0c0|name=[[Goblin]]|symbol=g|color=7:0:0|playable=Adv|hostile=Usually1|food=No|size=60,000|value=Not tameable|biome=[[Dark fortress]]es and [[dark pit]]s|note=Snatchers2}}
{{v50_creaturecurrent table row|graphic=[[File:kobold_sprite.png]]|bgcolor=#dfc0c0|name=[[Kobold]]|symbol=k|color=6:0:0|playable=Adv|hostile=Usually1|food=No|size=20,000|value=Not tameable|biome=Caves|note=Skulking race}}
|}

To change the background color, add <code><nowiki>|bgcolor=COLOR</nowiki></code> segment after the <code><nowiki>|graphic</nowiki></code> part. You can use color names or HTML hex color codes. I added this to the v50 creatures page, but at this time, I only added the first five creatures I just displayed. It's gonna take a while to find ALL of those creature sprites. I hope a lot of people help out on that one. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 05:29, 5 January 2023 (UTC)

:Thanks, looks nice! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:44, 5 January 2023 (UTC)
:Nice stuff, took the quick liberty to change the padding-left -> text-align to make all the sprites center aligned relative to each other :) Sweet work --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 17:41, 5 January 2023 (UTC)
:: Good work indeed. One minor issue, is that all the sprites have different sizes, which sometimes create slight variation in table row height. Consider using capping the image size vertically for example <code><nowiki>[[File:dwarf_sprite.png|x32px]]</nowiki></code>--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:15, 5 January 2023 (UTC)
:: Also often in such tables people want to click on the image to go for the specific entry, and often will try to click on the image which will take them to the file page. Consider adding link parameter for example: <code><nowiki>[[File:dwarf_sprite.png|x32px|link=dwarf]]</nowiki></code> [[File:dwarf_sprite.png|x32px|link=dwarf]] or no link at all <code><nowiki>[[File:dwarf_sprite.png|x32px|link=]]</nowiki></code> [[File:dwarf_sprite.png|x32px|link=]] --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:24, 5 January 2023 (UTC)

Dwarf Fortress Wiki talk:Versions

2023-01-05T18:18:36Z

Jan: /* Creature List Now Supports Graphics! */

{{archive|
# [[DF Talk:Versions/Archive 1|Page 1]]}}

== Version 0.31.19 starts a new DF generation? ==

My reading of Toady's comments on the release of 0.31.19 is that it came out basically because he felt it would take too long to get DF all the way to 0.32. With the ore changes, the sitefinder changes, the addition of grazing and several different industries, there's a lot of changes between 31.18 and 31.19. So I'm thinking it might be a good idea to call it the first release of DF2011 - and what we refer to as "DF2010" would then become 0.31.18.

Thoughts? --[[User:DeMatt|DeMatt]] 07:06, 28 February 2011 (UTC)

==Revisiting Redirects==
I wasn't around when the redirect policy was created, and I'm having trouble understanding the rationale. The example claims that linking [[Main:Cheese]] to [[cv:Cheese maker]] is problematic...but mainspace only ever redirects to the current version. If the best target in the current version is cheese maker, why not link to it directly? (It's not, at least for Cheese, since [[DF2012:Cheese]] exists now.) The explanation seems to be claiming that 40d articles that link to Cheese will follow the Mainspace link--but that hasn't been the case for a long while now. Articles in 40d automatically link against other articles in 40d, so that version remains internally consistent no matter where mainspace links to in the current version. For a current example, what do we gain by linking [[Main:Mead]] to [[cv:Mead]] and linking [[DF2012:Mead]] to [[DF2012:Alcohol]]?

If this really is just an outdated procedure, I recommend we drop the mummery and allow mainspace to link to cv:(best target). Double redirects ''may'' work (sometimes, but [[Main:Mead]] demonstrates a common problem where automatic redirection fails), but if they are unnecessary I think they should be avoided, partly because of problems like [[Main:Mead]] and partly because of the effort required to protect double redirects from users who believe they are problematic.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:16, 8 January 2014 (UTC)

:I was just thinking that. I'm currently attempting to write a basic extension to eliminate the need for mainspace redirects entirely, although Mediawiki's class structure may make this more difficult than I had hoped (the only method I've found for resolving redirects takes the ''article text'' instead of a title, e.g. "#REDIRECT ..."). I do agree that the current situation with redirects isn't ideal, so I'm hoping this will work better (once I get it to work). --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:42, 8 January 2014 (UTC)

Okay, that wasn't quite as clear as I meant it to be. In general, I think this is a tricky situation. Mediawiki wasn't designed to have five content namespaces, and certainly not chains of redirects between them. The problem that was pointed out in the [[DF:REDIR|policy]] is the fact that with:
Main:Foo -> cv:Bar
pages in the cv: namespace can't use [[<nowiki/>foo]], since the namespace links modification causes it to be treated as [[<nowiki/>cv:foo]] instead, which doesn't exist. The current suggested solution is this:
Main:Foo -> cv:Foo -> cv:Bar
This fixes the problem of [[<nowiki/>foo]] not working on cv pages, but creates issues with double redirects not always working. Another solution, which is more intuitive to new editors, is:
Main:Foo -> cv:Bar
cv:Foo -> cv:Bar
Both require creating two redirects. The first method has the advantage of ''ensuring'' that the cv redirect exists (otherwise, main:foo would be a redlink), while the second has the advantage of working more reliably in a couple cases.

What I'm trying to do is make main:Foo "jump" to cv:Foo when cv:foo exists, ''even if main:foo doesn't exist'' (basically it would treat all mainspace pages as redirects to cv pages, but only if the cv page exists and not the mainspace page). I had main:Bar jumping to cv:Bar fine, but if cv:Foo redirected to cv:Bar, accessing main:Foo would mysteriously stop at cv:Foo even if I increased the redirect limit. What I'm trying to do now is follow the redirects internally, without relying on Mediawiki to do it automatically - unfortunately, that has proved to be harder than I had hoped (and I sent my web server into an infinite loop while trying). I will try to work on this some more when I get a chance, although I'm not sure when that'll be yet :(. For now, feel free to fix broken double mainspace redirects as necessary, as long as redirects in the DF2012 namespace stay pointing to the right page (and new mainspace redirects get added in the DF2012 namespace too). --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:21, 9 January 2014 (UTC)

:You're treating cv like a namespace--it's not. It is simply shorthand for "fill in the current version here". [http://dwarffortresswiki.org/index.php?title=User_talk:Briess&diff=182404&oldid=181281 As I discovered a long time ago on a server not far away], linking from Main:Foo to cv:Foo tends to break redirection chains. If, instead of linking to cv:Foo, you link to DF2012:Foo, it might just work. It would, of course, be better if your patch could evaluate cv itself, but even if you have to hardcode the current version it's a single point of maintenance that requires update very infrequently. (For that matter, we could probably dispense with the cv hack entirely and just have a bot update mainspace links from DF2012 to DF201X when we switch to a new version.)--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:05, 9 January 2014 (UTC)
::I know cv isn't a namespace - I was just trying to avoid future confusion when the DF2012 namespace changes. It's interesting that changing "cv" to "DF2012" fixes some broken redirects, although I've found that simply making an edit to a broken redirect can usually fix it as well. I've actually had the most problems with double redirects when the second one (in the DF2012 namespace) doesn't use the DF2012 prefix (e.g. main:Foo containing <nowiki>[[cv:Foo]] and DF2012:Foo containing [[Bar]]</nowiki>). I'd rather keep the cv alias even if it isn't necessary for mainspace redirects when I get the patch to work, since it makes it easier to refer to the current version of the page (for example, several MDF articles contain links to a vanilla page for things that don't change in the mod).
::Also, using aliases like "cv" is supported by Mediawiki; in fact, several WMF wikis use them (for example, "[[wikipedia:WP:Redirects|WP:Redirects]]" on Wikipedia). It's quite likely that Mediawiki isn't processing double redirects using aliases correctly, though, since that's uncommon on most wikis. --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:35, 9 January 2014 (UTC)

In light of the lack of support for the current redirect policy, I propose we replace the current redirect section with:

:Mainspace article pages should use the cv: alias when redirecting to a versioned page, which will automatically update the link when a new version is released. For example, page "Main:Foo" should redirect to page "cv:Bar" (where "Bar" is the page that best describes the topic Foo in the current version).

:Pages in mainspace should only redirect to an older versioned page if that content no longer exists in the current version of the game (e.g. [[Cave river]], [[Chunk]]). In these cases the cv: alias cannot be used.

:Pages inside a versioned namespace should not use the cv: alias. Instead, they should redirect to the best page within that versioned namespace (e.g. [[DF2012:Dodging]], [[v0.31:Drink]]).

:Due to limitations of the wiki software, double redirects should be avoided if possible. When fixing double redirects in mainspace, please make sure to use the cv: alias as appropriate.

If no one objects, I will make this change in a few days.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:21, 15 January 2014 (UTC)

:Okay with me. It may be worth mentioning that double redirects only really need to be changed when they don't work (since changing a lot of redirects that work isn't necessary), but I think it's clearer and more relevant than the current policy. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:26, 16 January 2014 (UTC)

Done.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:55, 22 January 2014 (UTC)

I was finally able to get my extension to work after being motivated by one too many malfunctioning redirects. It now causes nonexistent pages in the main namespace to behave exactly like redirects to their DF2012 counterparts (when linked to, accessed directly, and transcluded). Double redirects also work (up to 100, in fact, although that was a temporary safety measure that I'll probably change). This means we'll be able to safely get rid of all mainspace redirects (redirects that redirect to something other than "cv" will still function if not deleted). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:20, 14 March 2014 (UTC)
:What about articles which don't exist in the current version but do exist in older versions? Will those still need mainspace redirects, or will your extension be able to automatically redirect them to v0.31/40d/23a? --[[User:Quietust|Quietust]] ([[User talk:Quietust|talk]]) 01:29, 14 March 2014 (UTC)
::It ignores all mainspace pages that actually have content, including redirects, so pages like [[masons guild]] won't be affected (unless deleted). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:47, 14 March 2014 (UTC)

Done and deployed. [[Cat]] is still treated as a redirect, even though I just deleted it (try clicking on the "redirected from" link). Pages that exist are ignored, so [[Masons guild]] and [[History of Dwarf Fortress]] still function normally (as a redirect to a 23a page and a non-redirect, respectively). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 18:57, 14 April 2014 (UTC)

I'm sending around a bot right now to delete all redirects of the format "foo -> cv:foo" (a surprising number don't fit this format, so I'm leaving them alone for now). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:43, 14 April 2014 (UTC)

:I'm confused. Do we use double redirects or not? Is there a single place we define our linking policy (including redirects), and is it updated?
:I had trouble linking to [[Consolidated_development]] in [[v0.34:Dragon]]. It kept pointing to v0.34:Consolidated_development, which does not exist. I ended up linking to Main:Consolidated_development to make it work. --[[User:Nahno|Nahno]] ([[User talk:Nahno|talk]]) 10:18, 1 July 2014 (UTC)

::That's a separate problem altogether - links in the versioned namespaces (v0.34, v0.31, 40d, 23a) automatically link to pages within their namespace. I may be able to set up a fallback to mainspace once I'm able to deploy again, but for now the "main:" alias is the intended solution. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 11:36, 1 July 2014 (UTC)

== Google often directs people to the 0.31 page ==

I've noticed a couple of times that finding a wiki page from an external search will often drop me onto a page from an older version. Is it possible to mitigate this somehow for new players? I could imagine something like redirecting old:Bar -> cv:Bar unless the user has come from old:Foo; no idea if that would actually work though. [[User:PeridexisErrant|PeridexisErrant]] ([[User talk:PeridexisErrant|talk]]) 11:48, 4 May 2014 (UTC)

:As a temporary solution, I could write a script that displays a banner of some kind if the user came from an external site. I'll ask Briess if he can do anything on the server level to increase the weighting of the current version's pages. (Obviously there are situations where people are looking for old pages, like [[23a:dungeon master]], so we don't want to disable indexing entirely on old pages.) —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:03, 4 May 2014 (UTC)

== DF2014? ==

As Toady [http://www.bay12games.com/dwarves/ draws closer to a new release], it might be worthwhile to discuss the addition of a new version to the wiki. The upcoming release covers two years of changes and introduces a number of new plants, foods, drinks, multi-tile trees, climbing, jumping, etc., so it is likely to have significant changes from the current DF2012. To avoid having people start new pages (and lose all the effort spent refining the prior version's page), I think it would be best to have a bot automatically copy over the DF2012 pages as a starting point for DF2014. I would suggest that these copied pages include a noticebox template mentioning that the content may be outdated, so that we can easily track which pages have been reviewed. I think either the {{tl|version check}} or {{tl|old}} template would work. --[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 19:43, 5 May 2014 (UTC)

:This is what [[User:QuietBot]] did after the 0.34 release, so it's certainly possible to use the same script to migrate to DF2014. I would like a way of tagging migrated pages, since inaccuracies in some pages went unnoticed for months after they were migrated. Since {{tl|old}} is already in use, {{tl|version check}} may be a better solution (it can be reworded slightly, or we can make a separate template for DF2014 migration). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:23, 1 June 2014 (UTC)
:Made [[Template:DF2014 migrated]] as an example. Any thoughts? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:32, 1 June 2014 (UTC)

== Redirects inconsistency ==

Following a redirect is supposed to be exactly the same as going straight to the page it redirects to, but this actually isn't the case:
* Go to [[Seeds]] and you get [[v0.34:Seed]] (outdated)
* Go to http://dwarffortresswiki.org/index.php?title=Seeds&redirect=no and click on the link and you get to [[DF2014:Seed]] (current)
So if you search for "seed", the top result is the DF2014 version. But search for "seeds" and you get the redirect, which sends you to the outdated page instead. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 23:22, 22 February 2015 (UTC)

While I'm talking about redirects, it seems redirects to sections don't work: see [[DF2014:How do I manage my seeds and crops]]. I know MediaWiki is capable of this trick because Wikipedia does it. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 23:32, 22 February 2015 (UTC)

:I have absolutely no idea why [[seeds]] redirects to a v0.34 page - it could be a Mediawiki bug. The section links issue is due to a known issue in the redirect extension we use, which has yet to be fixed. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:01, 23 February 2015 (UTC)
:It looks like deleting both [[Seeds]] and [[DF2014:Seeds]] fixed things (by allowing AutoRedirect to handle the redirects instead). Feel free to tag any others with {{tl|bad redirect}}. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:03, 23 February 2015 (UTC)
::It gets stranger. [[Vial]] redirects explicitly to [[cv:Flask]] which displays (when you look at it with &redirect=no) as [[DF2014:Flask]], but still goes to the v0.34 version. It seems redirects interpret the cv: pseudo-namespace (or whatever it's called) in an outdated way. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 18:08, 23 February 2015 (UTC)
::I've added a note to this page about this issue. If it gets resolved, the note should be removed. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 21:04, 23 February 2015 (UTC)

==Reorganizing versions==

The internet deals with moved content... poorly. Google is still linking to v0.34 pages more than a year after the switch to "DF2014", and even the wiki software still has cached links pointing to the old version pages.

I propose reorganizing versions on the wiki to avoid moving content whenever possible. Instead of having a temporary "current version" namespace that changes occasionally, all the current information gets promoted to the Main namespace. When the next version split occurs, the Main articles as of a certain revision number can be copied to the newly-created permanent "old version" namespace, while all the current information remains in Main. This not only fixes the link rot issue, but it has a few other benefits as well: fewer administrative tasks, no lockdown (a historical version of the Main pages can be copied at any point, even if the Main articles are already modified for the new version), almost all the article history is maintained in the Main article (instead of being spread unevenly across multiple versions), no "temporary" namespaces are needed, fewer problematic long redirect chains, and hopefully less user confusion (since Main gets priority in search results, etc.).

As an example, today we would not have a DF2014 namespace (which is good because "temporary" namespaces historically disappear anyway). If you ran a search for [[seed]] you'd end up at Main:seed, which would have all the current information on seeds. The version box at the top of the page would still link to the older versions of the seed article. When a new version is released, an admin would choose a revision number and copy the Main:seed article as it exists at that revision number to v0.40:seed. That's it. One historical copy that needs little to no new editing, and zero redirections/moves.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 19:02, 27 July 2015 (UTC)

:Makes sense to me. It would involve a lot of work, though (e.g. fixing templates and categories to account for the current version being in mainspace), although that should be doable thanks to {{tl|category}}, {{tl|version switch}}, etc.. A bot could be set up to copy revisions from before a release date as well, which would be more difficult (and maybe slower) than a direct copy, but not severely. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:24, 30 July 2015 (UTC)

:Actually, there are a few issues with that, namely that there wouldn't be an easy way to distinguish between versioned and non-versioned mainspace pages. There are ways to resolve Google search priority (we can exclude pages from older versions from search engine results if there are newer versions of those pages available, for example). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:47, 6 August 2015 (UTC)

::There aren't very many non-versioned mainspace pages, and determining if a page is versioned is as simple as looking for the version template and/or categories added by the version template (e.g. copy [http://dwarffortresswiki.org/index.php/Category:Current this category] instead of Main:*). The problem with "suggesting" newer pages to Google is that they obviously aren't crawling our wiki regularly (if they were, the fact that the mainspace redirects point to new pages would automatically be picked up). Even if your Google hints worked they wouldn't do anything for all the other broken links out on the 'net.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:35, 6 August 2015 (UTC)

::: Google actually crawls the wiki constantly - we probably get crawl hits from google for a continuous block of 2-3 hours per day, each and every day. Why they are slow to update is beyond me though. I can't remember why we didn't do this initially, but there was a technical limitation involved if I remember correctly. --[[User:Briess|Briess]] ([[User talk:Briess|talk]]) 22:05, 6 August 2015 (UTC)

::: There are <meta> tags that can be used to hide pages from search results (for search engines that recognize them, that is). Searching for {{tl|av}} or [[:Category:Current]] might work, although we'd have to make sure all of the DF2014 pages include that (some pages don't, particularly some disambiguation pages, although all of them should). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:53, 6 August 2015 (UTC)

:Is there a particular reason main and current are separate to begin with?—[[User:CLA|CLA]] ([[User talk:CLA|talk]]) 00:17, 7 August 2015 (UTC)

::It's mostly intended to distinguish between versioned and non-versioned pages and make version-related templates simpler to work with, since every versioned page has a namespace. I wasn't active here in 2010 when this system was created, so Briess and Emi would know more.
::Another issue I just thought of with Loci's suggestion is categories - currently, categories like [[:Category:Animals]] are used to organize the versioned sub-categories. Sure, we can change {{tl|Category}} to categorize mainspace pages in [[:Category:v0.40:Animals]] or [[:Category:DF2014:Animals]], but that would be less straightforward because there wouldn't be a namespace with that name (until pages are migrated when a newer major version is released). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 13:05, 7 August 2015 (UTC)

:Moving current pages to the main namespace sounds like a great idea. -[[User:Jecowa|Jecowa]] ([[User talk:Jecowa|talk]]) 20:47, 4 January 2018 (UTC)

Another thought: dealing with migrating redirects could be difficult with this proposal - specifically, determining which redirects should be migrated to a versioned namespace. Redirects can't contain {{tl|av}}, at least not before ``#REDIRECT``. I ''think'' it would be possible to copy pages in two stages, though - all non-redirects first, then all redirects whose targets were also copied. Thoughts? Anything I'm missing? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:41, 27 June 2019 (UTC)

Some subpages (particularly /raw and /Edit notice) also deliberately lack {{tl|av}}, although those shouldn't be too hard to handle. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:35, 9 July 2019 (UTC)

:Redirect pages (and all other edge cases I've looked at) can be included in categories (like [[:Category:Current]]) to determine whether or not they should be copied into an archival version. But if the redirects are "properly qualified" then they can all be copied over blindly. Mainspace redirects pointing to versioned information should use a blank namespace (which will be automatically constrained to the archival namespace); mainspace redirects pointing to unversioned information should use an explicit "Main" (which will automatically link back to the unversioned page). Then, when [[[[Toady]]]] gets copied to [[[[v0.4x:Toady]]]] it will point back to [[[[Main:Toady One]]]]. Meanwhile, [[[[Beer]]]], copied to [[[[v0.4x:Beer]]]], will properly point to [[[[v0.4x:Alcohol]]]].--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:00, 14 July 2019 (UTC)

::I think qualifying redirects is the best solution here - categorizing redirects manually is another possible source of errors, since categories (or a lack thereof) would only be visible on the redirect page itself, and [[:Category:Current]] is a hidden category. Copying over mainspace redirects into versioned namespaces would also resolve some issues that have come up due to those not reliably existing currently. I should be able to set up a bot script to add "main:" to current mainspace redirects (and it shouldn't break anything, since those redirects go to other mainspace pages anyway). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:57, 14 July 2019 (UTC)

(Note: I wrote all of this without noticing the previous discussion above.) I was wondering, when the wiki creates a new namespace for a major release again, if it is possible to ''not'' create a namespace for the next current version (e.g. "DF202x") and instead have the mainspace articles (which are currently redirects) become the new cv and move the content there. Therefore, [[cv:Cat]] would just be "[[Cat]]" (or [[Main:Cat]]).

Certain namespace-related templates like [[Template:Ns/0]] would need to be changed, though nothing significant as far as I know. For most cases, any "DF2014" would be replaced with "Main" or even blank. There's also multiple extensions handling the current namespace system and they may need to be modified too, though I'm not sure if or how much. I'm guessing based on the discussions above that it will change stuff up.

My reason is the current namespace is increasingly becoming more anachronistic. "DF2014" could be misinterpreted as "this page is about the 2014 version of the game" or "this page was last updated in 2014", which I've seen a few people in forums mention. Granted that [[Template:Av]] is on the top of very article, I still think the namespace is inconsistent with the recentness of the article. But how is this related to what I'm asking for? Let's say we continue the current system: if we happen to do a new namespace change this year and create DF2020, the next major release (after graphics/UI) will be mythgen, which is estimated to take several years to develop (the Big Wait), and so the anachronism will start over again. The proposed way will prevent this from occurring for the next major release and every release thereafter.

I think the confusion with having a namespace that becomes old-fashioned overtime supersedes the confusion with not marking current versioned articles with a namespace. Most users just search "Cat" on the search bar and naturally expect to get information about the latest release of DF. So if users go a page that's just titled "Cat", they won't expect outdated info about cats from a previous release. That's how the current system works anyways. We'll be skipping the two-step process that we have now. It'll make several wiki tasks much simpler as well. Editors can create new articles for current versions without remembering to add a namespace. It'll fix any existing issues with (double) redirects; instead of [[Main:Kitten]] redirecting to [[cv:Kitten]], which goes to [[DF2014:Kitten]], which then redirects to [[DF2014:Cat]], [[Main:Kitten]] would just redirect to [[Main:Cat]]. And the cv: alias will no longer be necessary since "cv:" = "Main:" and will be forever.

There's no need to differentiate the current version and previous versions with a namespace for the current version is what I'm saying. Articles of previous versions will retain their respective namespaces. Users will still type "40d:Cat" to go to the 40d version of the article, but if they want the current version, they'll just type "Cat" (like now). The mainspace containing the "live" version of an article is natural and would create no uncertainty when browsing the wiki. And it would simplify the wiki somewhat and future-proof this anachronism problem. As a bonus, this change will also prevent web search engines from showing previous version pages when typing "DF cat" or something. (This isn't happening right now as DF2014 has been the current namespace for ~6 years, but it'll happen again when everything moves to a new namespace.)

This is the gist of it, and I may have ignored most of the problems with this proposal. I have personally wished for the whole version namespacing be made less complicated and have been seeking for a solution, and I feel like this is the best way to go about in the future. – [[User:Doorkeeper|Doorkeeper]] 21:27, 14 August 2020 (UTC)

:<s>Whoops, looks like Loci already proposed this exact thing long ago. I definitely missed that discussion and should have checked first. My apologies. I'll move my text to that section and remove this one. – [[User:Doorkeeper|Doorkeeper]] 21:36, 14 August 2020 (UTC)</s> Done. – [[User:Doorkeeper|Doorkeeper]] 21:40, 14 August 2020 (UTC)

:The main issue I have with that is that putting pages about the current version in a namespace also differentiates between those pages and pages not about ''any'' version (for example, [[Toady One]] does not need a 40d or v0.34 page). Yes, we can use {{tl|av}} to mark versioned pages, but people often forget to add that to new pages. The current system also allows determining whether a page is versioned or not from its title, which makes migrations a lot faster. Relying on {{tl|av}} would require either reading the content of every page (which would slow scripts down significantly) or cross-checking with the list of all pages including the template (feasible, but a bit more complicated, and still susceptible to missing templates). I suppose that manually fixing and migrating pages missing {{tl|av}} later wouldn't be too much work, though.
:I am definitely in favor of changing "DF2014" (or a new namespace) to "Current", though. I was in favor of "DF2014" in 2014, but I don't think it makes sense anymore, and "Current" seemed to be a popular alternative in both the DF2012 and DF2014 discussions on the matter. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:02, 16 August 2020 (UTC)

== Weird redirect behaviour ==

[[Pump stack]] redirects to [[cv:Screw pump#Pump stack]]. If you look at the redirect itself it says it redirects to DF2014 namespace, which is correct. But if you actually follow the redirect, it goes to v0.34 namespace. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 16:10, 20 August 2018 (UTC)
:Yeah, that's part of the issue described in the above section (the wiki caching part, not on Google's end.) —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 15:00, 21 August 2018 (UTC)

== v50 organization ==

Some wiki admins have had a talk on Discord and decided that the most sustainable path forward is to put content for all future versions of DF in the main namespace. We will be working on a bot to do this in the next few days. Feel free to chime in with suggestions here. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:56, 14 December 2022 (UTC)

:Is it maybe possible to do backwards-namespacing? Like we have a "Main" namespace, which people are free to update, and whenever there's a new version of DF the "Main" namespace is copied into a namespace for the then old version, much like how you'd branch a stable branch from a development branch when working with a git-project? [[User:Therahedwig|Therahedwig]] ([[User talk:Therahedwig|talk]]) 23:13, 14 December 2022 (UTC)

::Yeah, we could do that if we decide to. We were talking about doing that for v50, actually, and might still do something similar to preserve edit history if it doesn't end up being too hard to automate. Our hope is that we will not introduce new namespaces for v50 -> v5x, unless there is a serious breaking change (and hopefully there isn't one). But if we change our mind, one advantage of the type of migration you mentioned is that it can be done retroactively - we can copy historical revisions that were current at the time of the release, and would only lose some typo fixes made after the release that apply to earlier versions as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:11, 15 December 2022 (UTC)

ETA is < 24 hours. Doing some final checks on a migration script. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 07:08, 19 December 2022 (UTC)

: We should really have a task list as there are many things that change and need updating. Including but not limited to:
:* Most templates that used the previous namespace convention broke, including nav templates.
:* Many game files changed locations and their pages need to be updated.
:* Raws need to be updated.
:* Various features added, changed, removed.
:* UI has been changed -- though I am more inclined to wait for classic release to avoid extra work --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 06:56, 20 December 2022 (UTC)

"''Raws need to be updated.''" Including applying text wraparound where necessary, I suppose - more than a few of them have proven to be that special kind of...''difficult'' to navigate otherwise, shall we say? [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 12:52, 20 December 2022 (UTC)

:There is already a task list in the [[#v50 migration|section below]] that includes templates and raws, with an explanation. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:25, 20 December 2022 (UTC)

== v50 migration ==

The initial migration script is done. New content is in the '''main''' namespace, e.g. [[Cat]]. Old content is still at [[DF2014:Cat]]. History was migrated to the ''new'' (main namespace) articles.

I know several things are broken still. Please reply if you find any others:
<div style="border-left: 2px solid red">
* <s>Versioned templates haven't been migrated yet (e.g. {{tl|vermin}} on [[Ant]])</s>
** Fixed. Most were migrated by a bot.
* <s>Raws are missing on all pages that use them.</s>
** This also affects sidebars, such as on [[Cat]] and [[Microcline]].
** Update: The DFRawFunctions extension has been upgraded to include v50 raws, using the "v50:" prefix for filenames instead of "DF2014:". <s>I haven't finished a migration script to create the /raw pages themselves, but they can typically be created manually by copying the DF2014 /raw pages and changing "DF2014" to "v50" everywhere.</s> —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:20, 1 January 2023 (UTC)
** Update 2: Raws have been added for all pages! They were copied from the "DF2014" pages and had "DF2014" replaced with "v50", which appears to have worked from a spot-check, but let me know if you find any problems. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:57, 4 January 2023 (UTC)
* Some pages where the DF2014 page was a redirect to a main namespace page that contained content were migrated incorrectly.
** In this case, the main namespace page is usually a redirect to itself. This can be fixed by undoing LethosorBot's edit to the main namespace page, then copying the content to the DF2014 page.
** Update: most seem to have been fixed manually - thanks! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:41, 21 December 2022 (UTC)
* <s>Some main-namespace talk pages redirect to DF2014 talk pages. Some of these redirects work, and some (usually older ones) do not.</s>
** Fixed with a bot. Some redirects from talk pages to other deleted talk pages are now broken, e.g. [[Talk:Above_ground]] (exists) -> [[Talk:Tile attributes]] (redlink). I am leaving them like that because they redirect to where the talk page should be created, but I'm also fine with people deleting them if they really want to. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:41, 21 December 2022 (UTC)
* {{tl|quality}} for new articles is disabled (see below)
* Some links from DF2014 to Main weren't working: e.g. the version selector [[DF2014:Mason's workshop]] was linking to [[DF2014:Main:Mason's workshop]] instead of [[Main:Mason's workshop]]. I'm not sure exactly why, but I fixed it with a change to the NamespaceLinks extension. Let me know if you spot similar broken links. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:19, 21 December 2022 (UTC)
</div>

—[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:54, 20 December 2022 (UTC)
:The quality levels of the 50.03 pages seem to be missing. I'm not sure if that's covered under that first point. [[User:Trainzack|Trainzack]] ([[User talk:Trainzack|talk]]) 06:47, 20 December 2022 (UTC)
::If the the [[Dwarf Fortress Wiki:Quality]] feature can be made to work with namespace scheme change, I suggest to automatically assign the lowest quality rating to all pages, alternately add the {{tl|old}} to all pages. Otherwise there will be a lot of pages that will fall through the cracks. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 09:12, 20 December 2022 (UTC)
:::I disabled {{tl|quality}} in the main namespace because it would require some rework to make the rating script and the template work properly there. Feel free to take a stab at the template. I will see what can be done on the extension side. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:14, 20 December 2022 (UTC)
::::What needs to be done on the template side? I'm not sure I see too big of an issue leaving pages as "unknown-quality" for now (or just change the default to tattered) until we get the rating script working. Is that script up anywhere, anything that could be helped with? [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 11:10, 2 January 2023 (UTC)
:::::They're already marked as unknown. Really the only issue I know of with the template is that it doesn't show up with some of the newer skins we added, and that can be fixed by getting rid of the absolute positioning. As for the script, it can be found at https://github.com/DF-Wiki/QualityRatings, and the issue is really only with the configuration system not recognizing the main namespace as valid. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:29, 3 January 2023 (UTC)
::::::Great, I started having a crack at fixing the template with different themes. Is the preference to get some CSS going and then include it in the global stylesheet (i.e different styles per theme) or to try and get a "one size fits all" fix? —[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 08:14, 3 January 2023 (UTC)
:::::::I would rather avoid custom site-wide CSS if we can. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:29, 4 January 2023 (UTC)
::::::::I appreciate that, I think it's the simplest solution to add a few lines to common.css though. Unless there is a way to attach CSS specifically to a template, I saw a few extensions that allowed that but I'm not sure if any are present in the wiki at the moment. Regardless there already exists a class `div.topicon` that is specifically for the quality ratings, is there an issue with expanding this class to accommodate the themes? The list of themes where the quality rating display is broken/invisible: Citizen, MinervaNeue, MonoBook. —[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 21:48, 4 January 2023 (UTC)
:::::::::What do you think of moving the template out of the topicon entirely and just placing it in a div? It would take up a (hopefully) small amount of vertical space in the article. [[User:Lethosor/Sandbox/Quality_test]] is an example. Unfortunately it isn't possible to prevent other templates from displaying above the quality this way ([https://dwarffortresswiki.org/index.php?title=User:Lethosor/Sandbox/Quality_test&oldid=283883]). So maybe we do need some custom CSS after all if we want that. I'm open to trying out whatever you propose. I'm a bit worried about future-proofing against skins we add later (particularly a mobile skin) but at least MediaWiki supports skin-specific global CSS as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:33, 5 January 2023 (UTC)
::::::::::I would rather we avoid taking any more vertical space in the article. The growing block pyramid at the top, starting with version template, is annoying. If you end up placing it inside the article space please use a slim box 100% wide that would include both.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 01:19, 5 January 2023 (UTC)
:::::::::::Agreed with you Jan, however I see that as two different tasks (ArticleVersion template changes, getting quality back on pages). I made a test adjustment to the quality and it takes up a negligable amount of extra space. See [[User:Vallode/sandbox#Page_quality]] for the example, we'd be able to completely remove "topicon" (unless it is used somewhere else?) and then potentially move on to making the ArticleVersion template into a slim version on the left-hand-side instead of a large box? Let me know what you think. --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 17:35, 5 January 2023 (UTC)

It appears some pages are redirecting recursively and never resolving correctly, like the [[https://dwarffortresswiki.org/index.php?title=Character_table&redirect=no|character table]] and [[tileset repository]] 07:35, 20 December 2022 (UTC)
: Indeed, these can be caught here: [[Special:DoubleRedirects]] --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:51, 20 December 2022 (UTC)

It might be useful to change the notice title to "release information '''for editors'''" --[[Special:Contributions/142.59.195.176|142.59.195.176]] 10:26, 20 December 2022 (UTC)
:Can do. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)
::New here, hello. Should we set a date where we remove/only show the banner for logged in users. There are (some) pages that have 4 different notices about the upgrade. [[Engraving]] is one such page, the top banner states "information for editors", we then have the "this page was migrated" banner, a version selection which warns the article might be inaccurate, and a smaller banner saying the page might need to be updated. Quite a lot of screen space, I think we can start to slowly reduce the amount of warnings this coming month? [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 10:07, 2 January 2023 (UTC)
:::Unfortunately, only showing info to logged-in users is difficult with how MediaWiki caching works. In terms of reducing warnings, there is a discussion [[Template_talk:ArticleVersion#.22Note_that_some_content_may_still_need_to_be_updated..22|here]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:43, 4 January 2023 (UTC)
:::As for [[Engraving]] specifically, the {{tl|old}} banner was actually present on [[DF2014:Engraving]] as well and got carried over with the migration. I removed it, and agree that it was redundant. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:46, 4 January 2023 (UTC)

Main talkpages seem to redirect to DF2014 talk. Not sure if it is intentional but I like it, though we should pay attention when creating new discussion relating to v50 ending up there.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 14:18, 20 December 2022 (UTC)
:That's unintentional. I specifically wrote the migration script to not move talk pages, but that has the side-effect of leaving any previously-created "Talk -> DF2014 talk" redirects intact. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)

Yo Lethosor, are we adding graphic sprites for the pages in some way? Or are we waiting for you to add some sort of new template or something? I'm sure you don't need me to tell you that the current templates don't allow that. Not sure if I'm allowed to change/create any templates either, as I don't want to break things for hundreds of pages. Edit: And IF the icons are allowed, should they be left alone, or 2×-3× sized like how the Minecraft wiki does it? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 14:29, 20 December 2022 (UTC)
:Depends on which templates you mean. There are copyright concerns with uploading a premium sprite sheet, for instance. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)
::I'm not talking about uploading an entire sprite sheet. I'm just talking about individual icons for each respective page. One image for cows, one for horses, one for werebeasts, etc. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 16:50, 20 December 2022 (UTC)
:::If we do that for every creature in the sprite sheet, that's not much different (in terms of copyright) from uploading the entire sprite sheet. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:09, 20 December 2022 (UTC)
::::Is there someone we can talk to about that? We finally get this new game with graphics, and then we can't use the very graphics of the game? No matter what the rules are, I'd say that would be the stupidest thing ever. I know I'm infamous here when it comes to copyright and images and stuff, but about 80% of game wikis out there are completely unofficial, and use game file images like no one's business. I can't imagine anyone's door being knocked on if we used the game's sprites, but I won't add any here until we have a go-ahead. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 17:14, 20 December 2022 (UTC)

:::::...I've made noise in Mayday's direction on this matter, at least (prob an incorrect maneuver, ''but'').[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 17:55, 20 December 2022 (UTC)
:::::: I hope some sort of arrangement can be made so we can use the new sprites with permission/limits, just as we are using the raw files. Otherwise we are all (devs and editors alike) shooting ourselves in the foot here.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 21:07, 20 December 2022 (UTC)

:::::::I just thought of something. We're supposedly not allowed to upload entire sprite sheets, right? What if - for the time being - we just use a few of them for the purpose of testing out new infoboxes? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 21:46, 20 December 2022 (UTC)
::::::::I don't know. If someone could ask Kitfox and post the response here, that would be great. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:47, 20 December 2022 (UTC)

:::::::::I've reached out to Alexandra, but she hasn't answered yet. Until then I found these old approvals from the previous community manager, Feeona: ([http://www.bay12forums.com/smf/index.php?topic=173474.msg8243633#msg8243633 link1], [http://www.bay12forums.com/smf/index.php?topic=176640.msg8243642#msg8243642 link2]). Waiting for a newer response until we begin mass uploads is probably the politer option, but like Zippy said, it is also standard for wikis to use game sprites with less approval. I second their idea of trying it out with a few images to test the infoboxes. On the extreme off-chance (and I do think it is) Kitfox protests we can always remove these few. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 22:19, 20 December 2022 (UTC)
:::::::::And here is a third, more official statement: ([http://www.bay12forums.com/smf/index.php?topic=173474.msg8249718#msg8249718 link3]). Perhaps that address of info@kitfoxgames.com is the better channel to ask for a confirmation, rather than Discord DMs, but I will be going to bed, so it is best if someone else does that. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 22:29, 20 December 2022 (UTC)
::::::::::Thanks for tracking this down! Ok, sprites should be fine, but let's avoid uploading the entire premium tileset as a single image, for instance (as the forum thread says, "use common sense"). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:21, 21 December 2022 (UTC)
::::::::::: Looks good, permission is always preferable over fairuse, I think it is a win win for all involved. I agree that we shouldn't upload entire sprite sheets (e.g. there is no reason to upload the windmill from every direction or whole construction phase for workshops) and that there are a lot of details that needs to be ironed out through testing. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 05:07, 21 December 2022 (UTC)
:::::::::We have a green light on uploading all and any sprites. Their response to me can be seen [https://i.imgur.com/BhmHjzC.png here]. I'm sure someone else confirmed it before me. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 19:00, 21 December 2022 (UTC)

Shifting temporarily to a new issue, is the documentation of [[Template:ArticleVersion]] outdated? It would seem so to me, since the current version no longer has its own namespace, with the templates needing updating being different ones. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 18:30, 20 December 2022 (UTC)
:I think it is still accurate enough. We left open the possibility of making another namespace in the future, albeit with a different migration strategy - see [[#v50 organization|above]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:52, 20 December 2022 (UTC)

Some Changes to infoboxes might be needed. Too bad [[User:Doorkeeper]] isn't around. He did a great work with navbox project--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:52, 21 December 2022 (UTC)

I just realized that raw files aren't stored as regular wiki pages but loaded via the DFRawFunctions extension (hence the need to update). Good news it's going to be handled in bulk, consistently and relatively easy to updated. Even better it's Lethosor problem ;) Also I just realized that all the "raw files" (txt files in the new vanilla folder) are released into the public domain. Both are probably not news to the vets but I'll leave it here for those who less up to date like myself. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:35, 22 December 2022 (UTC)

: I noticed that some templates aren't working properly in the new namespace, e.g. [[Basalt]] entry had its raw updated manually but the infobox fail to show any details. Cursory look suggest {{t|layerlookup/0}} need a minor tweak. This should do the work
:: Replace: <nowiki>{{layerlookup/aux|{{{{FULLPAGENAME}}/raw}}|uses={{{uses|}}}|wiki={{{wiki|}}}}}</nowiki>
:: With___: <nowiki>{{layerlookup/aux|{{</nowiki>:<nowiki>{{FULLPAGENAME}}/raw}}|uses={{{uses|}}}|wiki={{{wiki|}}}}}</nowiki>
: Not sure what the plan and ETA with raws update so I didn't touch this high usage template for now. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 08:11, 24 December 2022 (UTC)

::Please do feel free to make this update. I am still working on a script to create the <code>/raw</code> pages themselves. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:12, 1 January 2023 (UTC)

Wouldn't it be an idea to add to the Sitenotice to remove the {{tl|migrated article}} tag when an article has been fully updated? I see many articles that seem to be updated still have the tag. And/or advise to make use of the {{tl|verify}} for sections still in need of checking? --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 10:12, 2 January 2023 (UTC)
:Probably a good shout. The "see this page" link does include the detail on removing but we should more explicitly encourage removing the banner once a page has at least been looked over. [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 11:01, 2 January 2023 (UTC)

== v50 specific issues ==
=== Graphics===
Follow up on the use of game sprites and the need to trying it out with a few images to test the infoboxes. First sprite [[:File:Beds v50.png]] was uploaded and used on [[Bed]] entry. Any thoughts? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:06, 21 December 2022 (UTC)
:Seems like it should be rearranged to be horizontal. Also, has there been a serious discussion about copyright? Full screenshots are 100% fine, but you start going into a grey area when you upload pieces of a spritesheet. I'm of the opinion that it's all fine as long as it's inconvenient to reconstruct the full sheet from the individual images. Maybe a further restriction could be you shouldn't upload any of the art unless it's used in an infobox (maybe an exception for pieces of the UI). And one more restriction could be you shouldn't show everything, like in your bed example, maybe just the wooden bed is good enough, leave out the stone and metal, especially since those can only be made from strange moods. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:43, 21 December 2022 (UTC)
::Actually, your bed image is kinda bad for showing off what a bed looks like because it doesn't show the pillow/blankets. That might point to cropped screenshots being the best path, although less convenient for the uploader, as you don't get details left out. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:46, 21 December 2022 (UTC)
::I created a new license template [[Template:Copyright game]], based it on the way the RimWorld wiki does things. Call it a prototype, but it's probably how your bed image should be labelled. Indeed, I added it to it already. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]])

::: I agree that the horizontal arrangement would suit better here and that we should strive to represent how things look in-game. Otherwise, I am not too concerned about people being able to reconstruct anything (lets just say that ''anyone'' interested in that can get the real thing from the game files), also it seem we have permission to use the sprits on top of fairuse. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 19:55, 21 December 2022 (UTC)

::: Modifying the existing template to allow the inclusion of the new sprites is easy (Something like [https://ibb.co/zFXCrjd this]?) The big question is the matter of consistency is there any exceptions that will break the format (size wise with variant bloat for example), the sprite naming format, etc --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:44, 21 December 2022 (UTC)
::: If we are going to show a variant for each material type, then maybe these should be added as separate images so we can add a tooltip for each image. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:49, 21 December 2022 (UTC)

:I've got another prototype going here and here: [[User:Brightgalrs/vector.css]] and [[User:Brightgalrs/Sandbox]]. (You'll need to add the css stuff to your own /vector.css). Basically it's a way to recolor images using css classes. No idea if there's a better way. Also, the real implementation would require a change to [[MediaWiki:Common.css]]. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 22:41, 21 December 2022 (UTC)
:Should mention, there ''is'' a different way, just upload each image 16 times, one for each coloring. But maybe that's not very elegant. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 22:45, 21 December 2022 (UTC)

: It should be noted that soon the classic edition will be released, hence one should plan to have both the Premium and classic alongside in that little space --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 03:14, 22 December 2022 (UTC)
::I'm looking into a tab extension to potentially support this in infoboxes. Perhaps [https://www.mediawiki.org/wiki/Extension:Tabs Extension:Tabs]? I tried [https://www.mediawiki.org/wiki/Extension:TabberNeue Extension:TabberNeue], but it displays a placeholder if JavaScript is disabled, which isn't great. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:22, 22 December 2022 (UTC)
::: The Neue Tabber seem to works pretty much like the old one (which fandom [https://coding-help.fandom.com/wiki/Tabber#Adding_images_into_tabbers still use]) defaulting to showing the first tab only. Quick look suggest that neue work the same, plus the notice that 'Tabber requires Javascript to function' warning? if so, and if it is a bother, then you should be able to edit out the tabberneue-noscript string in code. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 06:29, 22 December 2022 (UTC)
::: I much prefer your tabber solution, but if that fails we can also use the gallery slideshow mode. If so, beware it has no way to control image size so the images have to be maliciously uploaded using the exact same size. example:
<gallery mode="slideshow">
File:SteelSample.png
File:TinSample.png
File:ZincSample.png
File:GoldSample.png
</gallery> --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 10:19, 22 December 2022 (UTC)

==== adding premium set to Infobox ====
I am unclear where are we going with this? 
1) Will (A) tabs be implemented, (B) we be using mediawiki toggle [[Template_talk:V50_workshop|example]] for premium and classic/blocked, (c) put images side by side, or (d) something else? 
2) Also [[silver]] and [[Pig iron]] use very different image style for example. 
3) Anything else you want ? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 12:32, 30 December 2022 (UTC)

: Personally, I would love tabs to be implemented, but I think that side by side might be best for most. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 12:32, 30 December 2022 (UTC)
: Here is rough layout we can use. It should fit most buildings given the default sprite size. There is also a different floor plan for both (inspired by reddit)

{|
|- valign=top
|
{| style="width:200px; background-color:#eaecf0; border-collapse: collapse; "
|+ 5×5
|- style="border-bottom:2px solid #3366cc; "
|<div class="mw-customtoggle-infoboxtab mw-ui-button mw-ui-progressive" style="border-top-right-radius: 10px; border-top-left-radius:10px;">toggle</div>
|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|- valign=top
|colspan=2|<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">
[[File:Siege workshop.png|center|160px]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab"">
{|
|rowspan=2 style="width:50%; font-size: 125%;"|<center>{{Template:Picture Siege workshop}}</center>
|style="line-height: 1em; font-size: 125%;"|
{| style="border-spacing:4px;"
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|}
|
{| style="width:200px; background-color:#eaecf0; border-collapse: collapse; "
|+ 3×3
|- style="border-bottom:2px solid #3366cc; "
|colspan=2 style="text-align: right;"|<div class="mw-customtoggle-infoboxtab mw-ui-button mw-ui-progressive" style="float:left; border-top-right-radius: 10px; border-top-left-radius:10px;">toggle</div>{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|- valign=top
|rowspan=2 style="width:50%;"|
<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">[[File:Carpenter's workshop.png]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab""><center>
{| style="font-size: 175%; border-spacing: 0; background-color: black; border: 2px solid black"
|- 
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"| {{Raw Tile|"|7:0:0}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|{{=}}|6:0:0}}
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"|
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|]|0:0:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
|}</center></div>
|
{| style="border-spacing:5px;"
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|
{| style="width:200px; height:100px; padding:10px; background-color:#eaecf0; border-collapse: collapse;"
|+ 1×1
|- style="border-bottom:2px solid #3366cc;"
| colspan=3 style="text-align:center;"|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|-
| style="border-right: 1px dotted #545557;"|[[File:Screw_press.png|32px|center|link=]]
| style="font-size:125%;"|<center>{{Template:Picture Screw press}}</center>
| style="border-left: 1px dotted #545557;"|<center>{{Template:Floor Plan Screw press}}</center>
|}
|
{| style="width:200px; height:100px; padding:10px; background-color:#eaecf0; border-collapse: collapse;"
|+ 1×3
|- style="border-bottom:2px solid #3366cc;"
| colspan=3 style="text-align:center;"|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|-
| style="border-right: 1px dotted #545557;"|[[File:water_wheel.png|32px|center|link=]]
| style="font-size:125%;"|<center>{{Template:Picture Water wheel}}</center>
| style="border-left: 1px dotted #545557;line-height:normal;"|<center>{{Template:Floor Plan Water wheel}}</center>
|}
|}
:Any thoughts on the direction and or any and all of its elements? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 10:16, 31 December 2022 (UTC)

::I kind of like side-by-side, if it fits. If anyone wants to implement a toggle button or tabs, I would ask that that be implemented in a template for now, so that e.g. we could change a toggle button to tabs in a single place if we decide to install an extension to support that. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:14, 1 January 2023 (UTC)

::: I noticed a comment saying that [[impassable tile]] are no longer used in v50, is that true for all constructions? If so, floor plans are no longer needed, making things much easier as we can fit everything in except the 5v5 constructions like trade depot (and even these can be placed one above the other if so desired). If not, any thought on the alternative floor plan design? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:46, 1 January 2023 (UTC)

:::: None of the constructions have blocking tiles any more from my experience playing. I haven't tested siege weaponry with that stuff, but none of the workshops have it, nor does any furniture. (walls and fortifications will of course obstruct movement [[User:AndrielChaoti|AndrielChaoti]] ([[User talk:AndrielChaoti|talk]]) 18:47, 1 January 2023 (UTC)
::::: Ok, I have removed them from v50. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 23:48, 1 January 2023 (UTC)

I have added a basic side by side variant to [[Template:V50 workshop]] and [[Template:Building]] for testing, let us know if there any issues. Few notes:
* The default image naming scheme of <code>workshop-name.png</code> will likely conflict with existing images here or on commons, maybe another naming scheme should be used like <code>v50 workshop-name.png</code> as it is with ascii pictures.
* There is inconsistency in image size. If you want to use large zoomed images then toggle is best, otherwise they need to be all in native size (96px for 3x3).
* In the current version the code roughly centers the images and if there is a big image like with [[Siege workshop]] it drops to a new line --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 23:48, 1 January 2023 (UTC)

How about combining shortcut keys and the new menu icons:
<div style="color:white; font-size: large; text-shadow: -1px -1px 0 #000, 1px -1px 0 #000, -1px 1px 0 #000, 1px 1px 0 #000;">[[File:Ui b.png]]<div style="position: absolute; bottom:-14px; right:3px;">b</div>[[File:Ui bo.png]]<div style="position: absolute; bottom:-14px; right:3px;">o</div>[[File:Ui bol.png]]<div style="position: absolute; bottom:-14px; right:3px;">l</div>[[File:Ui boll.png]]<div style="position: absolute; bottom:-14px; right:3px;">l</div></div>
--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 02:24, 3 January 2023 (UTC)

:I worry that this is difficult to read (I read it as "boil" at first). I would rather use something like {{tl|k}} with a known background. What about something like this? [[File:Ui boll.png]]<div style="position: absolute; bottom:-14px; right:0px;">{{k|l}}</div> or, alternatively, using flexbox without any overlap: [[File:Ui boll.png]]{{k|l}} —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:37, 3 January 2023 (UTC)
:: Same, but that is the best I came up with. We can use the key or maybe someone can help improve the design. Also 'l' is hard to read even with {{t|key}}.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 03:05, 3 January 2023 (UTC)
:: I added a {{t|Menu icon}} to start things so others can have a go with it. Also any thoughts on the icon naming convention (their shortcut sequence), is there easier/better way? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 09:36, 3 January 2023 (UTC)
::[[User:BarelyCreative]] updated the template: {{Menu icon|b|o|l|y}}. I think it looks good, thoughts? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:40, 3 January 2023 (UTC)
:::I like that, yeah. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:29, 4 January 2023 (UTC)
::::There were some places where it didn't make sense so display every icon all the time (like step-by-step guides), so I changed it slightly to allow display of fewer icons using "num" and counting from the end: <nowiki>{{Menu icon|b|o|l|y|sep=-;|num=2}}</nowiki> {{Menu icon|b|o|l|y|sep=-|num=2}} [[User:BarelyCreative|BarelyCreative]] ([[User talk:BarelyCreative|talk]]) 09:05, 4 January 2023 (UTC)

==== Bizarre palette-swapping idea/prototype ====
No idea if this is a good idea, since it takes a bit of time to set up, and there might be some performance issues... and maybe display issues?

But take a look at this:
{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock|palette-name=amber}}

It's way to swap palettes on an image, although the image itself is a table, with each cell representing a pixel. The template itself looks like this:
<code><nowiki>{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock|palette-name=saffron}}</nowiki></code>
Input the pattern and desired palette name.

I've got a larger showcase here: [[User:Brightgalrs/Sandbox/PaletteSwapShowcase]]. Only did a rock pattern so far, but all palettes are implemented.
The major use for this would be on each stone, metal, wood, etc. type's page. The palette could be read directly from the raws. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 03:22, 24 December 2022 (UTC)

:From a technical perspective, my primary concern is indeed performance. Both on the server side and client side, a large number of tables that large (in terms of markup and cell count, that is) tend to be resource-intensive to generate and render. I saw your image-filtering experiments on [[User:Brightgalrs/vector.css]], and while that strikes me as a newer and less-backwards-compatible approach, it would probably be more resource-friendly.
:Is this color adjustment something the game is doing natively? i.e. does this accurately match what the game displays? I bet we could slap together an image-filtering extension (or find an existing one?) that can do this if needed. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:49, 24 December 2022 (UTC)
::Yeah that's what I suspected. The images the template creates are spot on, checked it against a screenshot I took of some mica rocks in-game. The css stuff is unfortunately totally incorrect, was cool to learn about it though, so not a complete waste of my time :p. The premium, in-game graphics are true sprites, basically patterns of indexed colors. Each of the in-game colors (which are significantly expanded over the 16 ascii colors, there's 116/117) there is a palette defined in "\Dwarf Fortress\data\vanilla\vanilla_descriptors_graphics\graphics\images\palettes.png". Each indexed color of the sprite is swapped for the corresponding color in the palette. Because of that, the css stuff doesn't work since it's doing the hue/saturation/brightness changes to the entire sprite.
::I've looked into an existing mediawiki extension, couldn't find anything. One thing I did't really look at is some type of lua script/module that would basically emulate what the game is doing. So some function that takes in the base image as well as the desired palette, and based on that finds and replaces each color. No idea what mediawiki's capabilities are on that front. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 05:31, 24 December 2022 (UTC)
:::We do have Scribunto installed now, so it's totally possible to do something in Lua too - forgot about that. I can add you to the group that grants access to edit the Module namespace if you want to give that a shot. If we use an extension, we'd probably need a custom one, similar to DFDiagram (or perhaps DFDiagram could be extended - it's in dire need of a rewrite anyway). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:43, 24 December 2022 (UTC)
::::I asked around on the mediawiki irc, I think scribunto/lua is a deadend, at least for taking an uploaded image and doing stuff to it with a lua script. However I did come up with this even more bizarre solution, using block elements. [[User:Brightgalrs/Sandbox/PaletteSwapShowcase2]], maybe less resource intensive? Definitely displays a lot worse though, probably unusable.
::::{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock2|palette-name=saffron}}
::::I dunno, maybe none of this is worth it and we should just write some external program to put all the images together offline, and then just mass upload. It wouldn't be ''that'' many... [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 06:37, 24 December 2022 (UTC)

====Is there an easy way to just paste images from the clipboard?====

I use KDE spectacle to take screenshots straight to the clipboard (after cropping) -- is there an easy way to just paste (and auto-upload) an image into an article? It would make it a lot easier to contribute images. [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 23:35, 1 January 2023 (UTC)
:Unfortunately there is not. I would be open to a MediaWiki extension to support this if someone finds one. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:32, 2 January 2023 (UTC)
:: Looks like this could do it, but I haven't used it before: https://www.mediawiki.org/wiki/Extension:SimpleBatchUpload [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 19:41, 2 January 2023 (UTC)

====Standards for adding graphical version screenshots and images====

Hello, new user looking into adding imagery from the new version. Is there a standard for quality of new screenshots or images? I noticed that at a certain zoom level (2 zooms in from the furthest zoomed-out view), the graphics appear crisp and 1:1 pixel scaled, and I would propose that all images be taken at this scale whenever possible. If they need to be displayed larger, they should be nearest neighbor scaled in a photo editing program at 100% increments (Microsoft Paint will do this if you first select the image rather than directly scaling the whole canvas). I would also propose that images should be cropped to conform to the 32x32 pixel grid when possible, though this could be problematic with so many new graphical elements exceeding the bounds of their tiles. I would say the best practice for capturing artwork for items, furniture etc. ought to be done in a 3x3 open area to avoid shadows from nearby walls, or else extracted from the raw files (if this doesn't run afoul of being able to re-create the graphical version using those assets).

I know that perfect is the enemy of good, and any documentation is better than none, but just thought I'd ask about this, and see if/where something like this ought to be posted. [[User:Unclesporky|Unclesporky]] ([[User talk:Unclesporky|talk]]) 13:58, 3 January 2023 (UTC)
:It has been stated in [[Template:V50 workshop]] that <q>screenshots should be at the "native" resolution</q> but someone could edit the [[Screenshot]] page for best practice for the steam version. Or post some examples in [[Talk:Screenshot]] to find out what is best? --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 14:21, 3 January 2023 (UTC)

====How would I/should I go about putting creature sprites on their pages?====

Howdy. New player and wiki user here. I wanted to try and help update the wiki to the Steam release of DF, so I figured I'd chip in by putting each creature's sprites on their respective page, since I'll often look up a creature I have yet to see in game only to be met by a blue J, or whatever. I found all of the game's creature sprites in C:\Program Files (x86)\Steam\steamapps\common\Dwarf Fortress\data\vanilla\vanilla_creatures_graphics\graphics\images, so I figured I could just chop those up in Photoshop and stick them on here no problem, but the programming syntax/whatever it is on this site is incredibly confusing, I don't know how I'd actually go about doing it. I figured I'd just find the spot on the page where the little letter is and replace that with the image code, but it seems the pages are built using heavily nested templates that I can't even begin to understand. Any help?--[[User:Treese|Treese]] ([[User talk:Treese|talk]]) 03:07, 5 January 2023 (UTC)
:Based on [[User:Zippy|Zippy]]'s work at {{tl|Creaturelookup_b}}, I added an "image" parameter to {{tl|creaturelookup/0}}, which is what creature pages should all be using. See [[Dwarf]] and [[Cow]] for examples. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:37, 5 January 2023 (UTC)

=== Hotkeys/Menu navigation ===
Most key bindings and menus have changed. Should the article reflect a) only the old version, b) only the GUI version or c) both? For example, [[Bridge|bridges]] used to be built via {{k|b}} -> {{k|g}}, but now it's in Place strucutures {{k|b}} -> Constructions {{k|n}} -> Bridge {{k|b}}. What should be written in the article? Currently, it's {{k|b}} -> {{k|g}}. I ''think'' it should be only b), but I am not sure if there will be differences regarding hotkeys or menus between the premium version and the free version and then, c) would be the most appropriate option. --[[User:Prometherus|Prometherus]] ([[User talk:Prometherus|talk]]) 10:16, 22 December 2022 (UTC)

: Not sure. I wish the classic release soon --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 16:45, 22 December 2022 (UTC)
:: Are you Toady's herald? Looks like it was just released! [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:18, 22 December 2022 (UTC)
:: And our questions are answered, the old hotkeys seem to have been thrown out. Part of me is disappointed (useless muscle memory) but also relieved (unified UI for both versions is good in general and for the wiki). [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:25, 22 December 2022 (UTC)
::: According to info, in a sort of 'demo version' at that. I'll wait a little while longer, for myself.[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 18:22, 22 December 2022 (UTC)
::::It's unlikely that keybindings in it will change significantly. My vote is that we should include information for both premium and classic, everywhere. Hopefully the keybindings are not different between versions. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 18:26, 22 December 2022 (UTC)
:::Shouldn't it be based on the 50 or what verion the article is written for? [[User:Dominick|Dominick]] [[User_talk:dominick|(TALK)]] 18:42, 22 December 2022 (UTC)
:::: The keybindings seem to be consistent between versions, (haven't checked exhausitvely, but since the menu layout is the same I think it is a good assumption). Should also keep in mind/consider that not all actions have keybindings. An option would be write 'Click on the <Example Text> icon or press {{k|E}}' [[User:Koos|Koos]] ([[User talk:Koos|talk]]) 23:14, 23 December 2022 (UTC)

=== Removed features & concepts ===

Since they're removed concepts, I've set [[Room]] to be a redirect for [[DF2014:Room]] and created [[Template:Activity zones]] for the nav bar bedrooms, etc, and made the necessary changes to [[Bedroom]] for it. Is this the correct approach, before I go on much further? (also a note, if it is, then [[Template:v50_rooms]] probably needs to be deleted) I also imagine that considering the number of changes in the interface, that things like [[Adventure mode]] and related pages might best be truncated to "not in 50.03" and when it does make it across, being more deliberately brought over in pieces? [[User:HawkOwl|HawkOwl]] ([[User talk:HawkOwl|talk]]) 06:23, 23 December 2022 (UTC)

:Usually it is marked with [[Template:Removed_feature]]. For example: [[Dipscript]] or [[Party]]. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:45, 23 December 2022 (UTC)

:: Ah, that's fair. Should that be mentioned in [[Dwarf_Fortress_Wiki:Versions#Redirects]]? [[User:HawkOwl|HawkOwl]] ([[User talk:HawkOwl|talk]]) 10:03, 23 December 2022 (UTC)

:::I think the redirect policy mostly had in mind things that were removed a ''long'' time ago, like [[Tax collector]] and [[Economy]] (and the latter actually has a stub page as well). I guess we could clarify. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:34, 23 December 2022 (UTC)

:::: The "current" redirects also cause the version box to incorrectly show that the current version has a page - e.g. [[23a:Cave_river]] shows a v50.04 version, but it's just a redirect back to that version. Similarly, what should happen to redirects like [[Clothes maker]], where a concept has evolved? It currently goes to [[23a:Clothes maker]] - that's correct if the user is trying to look up a very old concept, but if a new user is looking for "how to make clothes", they should be directed to [[Clothier]]. --[[User:Danny252|Danny252]] ([[User talk:Danny252|talk]]) 12:16, 26 December 2022 (UTC)

:::: One should be careful with cv redirects. Most that were recently adjusted were unused plural forms (that should probably be deleted) but few like [[Crown]] needed that for backward compatibility. Removing the [https://dwarffortresswiki.org/index.php?title=Crown&type=revision&diff=279966&oldid=219482 cv part] means the the link on [[v0.31:Tilesets]] is now broken. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 22:30, 26 December 2022 (UTC)

:::::If [[v0.31:Tilesets]] is about v0.31, it should not be using "main:" in its links - ''all'' of those links are going to pages about v50, not v0.31, regardless of whether the target is a redirect or not. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:37, 26 December 2022 (UTC)
:::::: You right, I removed it. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 17:55, 27 December 2022 (UTC)

Crown cv redir issue is now fixed, I believe. As goes with such cases where one can simply revert the troublesome edit, unless I've mistepped, myself? [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 23:52, 26 December 2022 (UTC)
:Both [https://dwarffortresswiki.org/index.php?title=Crown&diff=prev&oldid=280026] and [https://dwarffortresswiki.org/index.php?title=Crown&diff=prev&oldid=279966] should not have had any effect, because "cv" is an alias to the main namespace now, just like "main". Proof: [[Crown]], [[cv:Crown]], [[main:Crown]]. It's possible caching is coming into play here, although I purged the redirect cache after making that alias change earlier this month... —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:02, 27 December 2022 (UTC)

I think there have been some changes not captured, but as a newb, I'm afraid to edit the page(s). A good example is Strawberry. I'm playing the Steam version right now and Strawberry plants are "not relevant to brewing" in Labor > kitchen > veg / fruit / leaves. Unless I'm mistaken and need to process them? Another example is the trade caravan = it seems the 3 square pathing no longer happens; it's just yak(s). 12:31, 28 December 2022 (UTC) 12:29, 28 December 2022 (UTC)
:Strawberries should be brewable according to the Raws.
:Trade wagons has been modified in v50. The first wagons will arrive at the same time your fort is becoming a barony. Until then, it's only pack animals and stairs are indeed fine. The [[Trading]] page needs a huge rework anyway... I'll try to do that next week. --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 13:40, 2 January 2023 (UTC)

<s>As far as I can tell, none of the workshop buildings in v50 have blocking tiles any more. There's a comment to the like in data/vanilla/vanilla_buildings/objects/building_custom.txt that says this "[BLOCK:1:0:0:0] workbenches no longer block". Hesitant to update that template as I'm not sure if it's referenced for all of the old versions too. </s> [[User:AndrielChaoti|AndrielChaoti]] ([[User talk:AndrielChaoti|talk]]) 05:54, 29 December 2022 (UTC)
: A new template has been created: {{tl|V50 workshop}} --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 13:40, 2 January 2023 (UTC)
::Thanks! In general, I would like to delegate the switching responsibility to the template (like how {{tl|creaturelookup/0}} works), but in cases where the parameters diverge significantly like with workshops, it could make sense to make an entirely new template. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:40, 3 January 2023 (UTC)

=== creature infobox prototype (moved) ===

Check it out, I made a temporary template and added it to the [[cow]]s page. Now it shows the sprites (but not the zombified versions yet). I wanted to show everyone a prototype of what v50 creature infoboxes should look like. Or at least something similar to it. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 19:11, 27 December 2022 (UTC)
:Hi, I'm new to editing wikis but I have done a bit of work with sprite sheets and I've been going through the DF data files to find the different graphics hoping to help with the animal pages. I've thrown together a template with grass and a few nature sprites (plants, a tree, and a rock) for size reference but I'm unsure how large the 'display' tiles in the middle of the template should be to suit all animals. I can see in the sprite sheets that some land animals have an adult and child sprite, so two tiles. Others have a male, female, and child, but after seeing you include the zombie cows I'm unsure if I should make it twice the size to add them too. Alternatively, I could grab some tiles from the haunted biomes for the zombie animals and make a separate template for a side-by-side comparison. Either way, let me know if this helps. I'd like to help with other graphics too as we add the premium tilesets but the animals seemed the easiest to tackle with me being new to wiki editing. ~~[[User:UristTheSeventh|UristTheSeventh]] ([[User talk:UristTheSeventh|talk]])
::@Zippy, I am a bit perplexed about the purple cows. Why do we need a zombified version of creatures on every page?
::@UristTheSeventh, we can use all the help. Maybe post an example, so that we can have something to compare and contrast.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 11:49, 3 January 2023 (UTC)
:::@Jan Here are the examples:
:::[[File:Creature template.png]] [[File:Armadillo.png]] [[File:Seagull.png]]
:::It'll need to be wider or arranged differently for different creatures with more that two sprites or for multi-tile creatures. I can also do an aquatic and air themed template for swimming and flying creatures. ~~[[User:UristTheSeventh|UristTheSeventh]] ([[User talk:UristTheSeventh|talk]])
::::Looks nice, like the metal template. There are several people working on updating the graphics you should talk more among yourselves. Best I can offer is that I width wise I am hoping to go up to 200px for infoboxes.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 01:13, 5 January 2023 (UTC)

=== When do we remove the migration note on specific pages? ===

At what point can we remove the "this page was auto migrated from v47" warning? There are a bunch of small pages that are more or less accurate, if I've reviewed them, can I go ahead and remove the warning? [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 23:33, 1 January 2023 (UTC)
:Yes, feel free to remove it if you think all content is accurate. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:31, 2 January 2023 (UTC)

=== Any info on fixing "creature description not found?" ===

I see this issue on most creature pages, it seems to be due to a lookup that's not currently functioning? Cows interestingly doesn't have this issue but I couldn't figure out how to recreate whatever fix it's editor did. --[[User:Yallendallis|Yallendallis]] ([[User talk:Yallendallis|talk]]) 00:22, 3 January 2023 (UTC)
:That is the missing raws issue described above. Cow was fixed by the addition of [[cow/raw]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:28, 3 January 2023 (UTC)
::Ah makes sense, not fully used to the language of wikis yet so I read over it while looking. To put this bit of questioning to rest for any future readers, is it correct that it's fine to update any raws manually, though it will be done automatically at some point? --[[User:Yallendallis|Yallendallis]] ([[User talk:Yallendallis|talk]]) 07:48, 3 January 2023 (UTC)
:::Yes. I'm circling back to work on a script right now, so not much point in doing it if you're reading this. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:57, 4 January 2023 (UTC)
:::This should be fixed now. If you continue to see pages with problems, you can try [https://www.mediawiki.org/wiki/Manual:Purge purging the cache]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:59, 4 January 2023 (UTC)

=== Adventurer Mode related sections ===

The topic has already been discussed [[#Removed features & concepts|above]], but I don't see a clear line on what to do with article sections that mention Adventurer Mode. Like for example in [[Butcher#Adventurer_mode|Butcher]].

'''a) Truncate''' or '''b) leave in place with a mention''' that the mode is not yet present IG but will be added in a future update?

Personally I think option b) is better, because I think it's silly to undo some work just to reintroduce it a few weeks later, with the necessary corrections. Even if a copy/paste of a previous version takes ~15 seconds, considering the number of articles that need to be corrected, it would be a bit of a waste of time.--[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 14:22, 3 January 2023 (UTC)

== Toggleable image ==

Any objections/comments to using this template for now for toggling between classic and premium images? I'd probably rename it to "Template:Premium-classic thumb image". I'm sure someone can come up with a better UI eventually, but should be easy to migrate at that point. I also think we should use the same customtoggle class for this and for the infobox. [[User:NiftyManiac|NiftyManiac]] ([[User talk:NiftyManiac|talk]]) 23:12, 1 January 2023 (UTC)

{{User:NiftyManiac/Sandbox/TemplateDualImage|
premium=File:Quickstart-finder.png|
classic=File:Quickstart-finder-partial.png
}}

{{User:NiftyManiac/Sandbox/TemplateDualImage|
premium=File:Quickstart-finder.png|
classic=File:Quickstart-finder-partial.png|
caption=My caption|
width=100px
}}

:This looks nice to me! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:30, 2 January 2023 (UTC)

: Good initiative. From the top of my head:
:* I suggest using a shorthand, no one wants to type 'Premium-classic thumb image'.
:* If we end up using toggle for infoboxes (not sure where we headed there), then I agree definitely same custom toggle class should be used for all, thus allowing to switch premium-classic view on the whole page at a click.
:* The button part on a separate row isn't pretty, creating a lot of dead space that can be used by the text. Are we set on the label 'toggle ascii'? Classic isn't Ascii per se, maybe we can use a 'toggle' with a tooltip {{tooltip|for example|does bla bla bla}}, or maybe we can get rid of the text and have a smaller icon button ([[User:Jan/sandbox#Metal_example|two examples]]).
: I hope that helps. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 11:21, 2 January 2023 (UTC)

:: I added [[Template:Dual image]] with some of your suggestions. Agree that it's not super pretty, feel free to try something different.

::* I put the toggle in the caption mostly because I gave up on trying to make a more sophisticated replacement for the default thumb image behavior, I'm sure someone with better wiki-fu could put together something more intelligent.
::* I cut the text down to just "Toggle"; I think the best solution would be a small graphic showing the old and new dwarf icons with arrows between them. [[User:NiftyManiac|NiftyManiac]] ([[User talk:NiftyManiac|talk]]) 19:21, 2 January 2023 (UTC)

{{Dual image|
premium=File:DFwiki5by53by3farm.png|
classic=File:Quickstart_layout_3.png|
width=100px|
caption=A 5x5 room with a 3x3 farm plot
}}
::: I updated the layout, now it should look just like a regular image thumb. I didn't had time to test it, if it doesn't work for you or you don't like it just revert the last change. cheers. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 21:46, 2 January 2023 (UTC)
::::I don't know which part of this talk page to put this, but I added the ability to add icons to the v50 workshops template. Leaving the icon part blank will not break the template in any way. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 09:47, 3 January 2023 (UTC)
{{clear}}
==Creature List Now Supports Graphics!==
I wasn't easy, but I made new templates so the [[Creature]]s page now supports both graphics sprites ''and'' ASCII tiles. Allow me to show you:

{{v50_creaturecurrent_table_head}}
{{v50_creaturecurrent table row|graphic=[[File:dwarf_sprite.png]]|name=[[Dwarf]]|symbol=☺|color=3:0:0|playable=Fort, Adv|hostile=No|food=No|size=60,000|value=Not tameable|biome=[[Mountain halls]], [[Fortress|dwarf fortress]]es, [[hillock]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:elf_sprite.png]]|name=[[Elf]]|symbol=e|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=60,000|value=Not tameable|biome=[[Forest retreat]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:human_sprite.png]]|name=[[Human]]|symbol=U|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=70,000|value=Not tameable|biome=[[Town]]s and cities|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:goblin_sprite.png]]|name=[[Goblin]]|symbol=g|color=7:0:0|playable=Adv|hostile=Usually1|food=No|size=60,000|value=Not tameable|biome=[[Dark fortress]]es and [[dark pit]]s|note=Snatchers2}}
{{v50_creaturecurrent table row|graphic=[[File:kobold_sprite.png]]|name=[[Kobold]]|symbol=k|color=6:0:0|playable=Adv|hostile=Usually1|food=No|size=20,000|value=Not tameable|biome=Caves|note=Skulking race}}
|}

Oh wait, there's a bonus. You can also modify the background color of the box the sprites go in. I added that to make possibly-hard-to-see-otherwise sprites more easy to see - depending on the colors it has. Allow me to demonstrate.

{{v50_creaturecurrent_table_head}}
{{v50_creaturecurrent table row|graphic=[[File:dwarf_sprite.png]]|bgcolor=#829ccc|name=[[Dwarf]]|symbol=☺|color=3:0:0|playable=Fort, Adv|hostile=No|food=No|size=60,000|value=Not tameable|biome=[[Mountain halls]], [[Fortress|dwarf fortress]]es, [[hillock]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:elf_sprite.png]]|bgcolor=#c7dfc0|name=[[Elf]]|symbol=e|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=60,000|value=Not tameable|biome=[[Forest retreat]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:human_sprite.png]]|bgcolor=#c7dfc0|name=[[Human]]|symbol=U|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=70,000|value=Not tameable|biome=[[Town]]s and cities|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:goblin_sprite.png]]|bgcolor=#dfc0c0|name=[[Goblin]]|symbol=g|color=7:0:0|playable=Adv|hostile=Usually1|food=No|size=60,000|value=Not tameable|biome=[[Dark fortress]]es and [[dark pit]]s|note=Snatchers2}}
{{v50_creaturecurrent table row|graphic=[[File:kobold_sprite.png]]|bgcolor=#dfc0c0|name=[[Kobold]]|symbol=k|color=6:0:0|playable=Adv|hostile=Usually1|food=No|size=20,000|value=Not tameable|biome=Caves|note=Skulking race}}
|}

To change the background color, add <code><nowiki>|bgcolor=COLOR</nowiki></code> segment after the <code><nowiki>|graphic</nowiki></code> part. You can use color names or HTML hex color codes. I added this to the v50 creatures page, but at this time, I only added the first five creatures I just displayed. It's gonna take a while to find ALL of those creature sprites. I hope a lot of people help out on that one. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 05:29, 5 January 2023 (UTC)

:Thanks, looks nice! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:44, 5 January 2023 (UTC)
:Nice stuff, took the quick liberty to change the padding-left -> text-align to make all the sprites center aligned relative to each other :) Sweet work --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 17:41, 5 January 2023 (UTC)
: Good work indeed. One minor issue, is that all the sprites have different sizes, which sometimes create slight variation in table row height. Consider using capping the image size vertically for example <code><nowiki>[[File:dwarf_sprite.png|x32px]]</nowiki></code>--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:15, 5 January 2023 (UTC)

Dwarf Fortress Wiki talk:Versions

2023-01-05T18:16:04Z

Jan: /* Creature List Now Supports Graphics! */

{{archive|
# [[DF Talk:Versions/Archive 1|Page 1]]}}

== Version 0.31.19 starts a new DF generation? ==

My reading of Toady's comments on the release of 0.31.19 is that it came out basically because he felt it would take too long to get DF all the way to 0.32. With the ore changes, the sitefinder changes, the addition of grazing and several different industries, there's a lot of changes between 31.18 and 31.19. So I'm thinking it might be a good idea to call it the first release of DF2011 - and what we refer to as "DF2010" would then become 0.31.18.

Thoughts? --[[User:DeMatt|DeMatt]] 07:06, 28 February 2011 (UTC)

==Revisiting Redirects==
I wasn't around when the redirect policy was created, and I'm having trouble understanding the rationale. The example claims that linking [[Main:Cheese]] to [[cv:Cheese maker]] is problematic...but mainspace only ever redirects to the current version. If the best target in the current version is cheese maker, why not link to it directly? (It's not, at least for Cheese, since [[DF2012:Cheese]] exists now.) The explanation seems to be claiming that 40d articles that link to Cheese will follow the Mainspace link--but that hasn't been the case for a long while now. Articles in 40d automatically link against other articles in 40d, so that version remains internally consistent no matter where mainspace links to in the current version. For a current example, what do we gain by linking [[Main:Mead]] to [[cv:Mead]] and linking [[DF2012:Mead]] to [[DF2012:Alcohol]]?

If this really is just an outdated procedure, I recommend we drop the mummery and allow mainspace to link to cv:(best target). Double redirects ''may'' work (sometimes, but [[Main:Mead]] demonstrates a common problem where automatic redirection fails), but if they are unnecessary I think they should be avoided, partly because of problems like [[Main:Mead]] and partly because of the effort required to protect double redirects from users who believe they are problematic.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:16, 8 January 2014 (UTC)

:I was just thinking that. I'm currently attempting to write a basic extension to eliminate the need for mainspace redirects entirely, although Mediawiki's class structure may make this more difficult than I had hoped (the only method I've found for resolving redirects takes the ''article text'' instead of a title, e.g. "#REDIRECT ..."). I do agree that the current situation with redirects isn't ideal, so I'm hoping this will work better (once I get it to work). --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:42, 8 January 2014 (UTC)

Okay, that wasn't quite as clear as I meant it to be. In general, I think this is a tricky situation. Mediawiki wasn't designed to have five content namespaces, and certainly not chains of redirects between them. The problem that was pointed out in the [[DF:REDIR|policy]] is the fact that with:
Main:Foo -> cv:Bar
pages in the cv: namespace can't use [[<nowiki/>foo]], since the namespace links modification causes it to be treated as [[<nowiki/>cv:foo]] instead, which doesn't exist. The current suggested solution is this:
Main:Foo -> cv:Foo -> cv:Bar
This fixes the problem of [[<nowiki/>foo]] not working on cv pages, but creates issues with double redirects not always working. Another solution, which is more intuitive to new editors, is:
Main:Foo -> cv:Bar
cv:Foo -> cv:Bar
Both require creating two redirects. The first method has the advantage of ''ensuring'' that the cv redirect exists (otherwise, main:foo would be a redlink), while the second has the advantage of working more reliably in a couple cases.

What I'm trying to do is make main:Foo "jump" to cv:Foo when cv:foo exists, ''even if main:foo doesn't exist'' (basically it would treat all mainspace pages as redirects to cv pages, but only if the cv page exists and not the mainspace page). I had main:Bar jumping to cv:Bar fine, but if cv:Foo redirected to cv:Bar, accessing main:Foo would mysteriously stop at cv:Foo even if I increased the redirect limit. What I'm trying to do now is follow the redirects internally, without relying on Mediawiki to do it automatically - unfortunately, that has proved to be harder than I had hoped (and I sent my web server into an infinite loop while trying). I will try to work on this some more when I get a chance, although I'm not sure when that'll be yet :(. For now, feel free to fix broken double mainspace redirects as necessary, as long as redirects in the DF2012 namespace stay pointing to the right page (and new mainspace redirects get added in the DF2012 namespace too). --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:21, 9 January 2014 (UTC)

:You're treating cv like a namespace--it's not. It is simply shorthand for "fill in the current version here". [http://dwarffortresswiki.org/index.php?title=User_talk:Briess&diff=182404&oldid=181281 As I discovered a long time ago on a server not far away], linking from Main:Foo to cv:Foo tends to break redirection chains. If, instead of linking to cv:Foo, you link to DF2012:Foo, it might just work. It would, of course, be better if your patch could evaluate cv itself, but even if you have to hardcode the current version it's a single point of maintenance that requires update very infrequently. (For that matter, we could probably dispense with the cv hack entirely and just have a bot update mainspace links from DF2012 to DF201X when we switch to a new version.)--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:05, 9 January 2014 (UTC)
::I know cv isn't a namespace - I was just trying to avoid future confusion when the DF2012 namespace changes. It's interesting that changing "cv" to "DF2012" fixes some broken redirects, although I've found that simply making an edit to a broken redirect can usually fix it as well. I've actually had the most problems with double redirects when the second one (in the DF2012 namespace) doesn't use the DF2012 prefix (e.g. main:Foo containing <nowiki>[[cv:Foo]] and DF2012:Foo containing [[Bar]]</nowiki>). I'd rather keep the cv alias even if it isn't necessary for mainspace redirects when I get the patch to work, since it makes it easier to refer to the current version of the page (for example, several MDF articles contain links to a vanilla page for things that don't change in the mod).
::Also, using aliases like "cv" is supported by Mediawiki; in fact, several WMF wikis use them (for example, "[[wikipedia:WP:Redirects|WP:Redirects]]" on Wikipedia). It's quite likely that Mediawiki isn't processing double redirects using aliases correctly, though, since that's uncommon on most wikis. --[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:35, 9 January 2014 (UTC)

In light of the lack of support for the current redirect policy, I propose we replace the current redirect section with:

:Mainspace article pages should use the cv: alias when redirecting to a versioned page, which will automatically update the link when a new version is released. For example, page "Main:Foo" should redirect to page "cv:Bar" (where "Bar" is the page that best describes the topic Foo in the current version).

:Pages in mainspace should only redirect to an older versioned page if that content no longer exists in the current version of the game (e.g. [[Cave river]], [[Chunk]]). In these cases the cv: alias cannot be used.

:Pages inside a versioned namespace should not use the cv: alias. Instead, they should redirect to the best page within that versioned namespace (e.g. [[DF2012:Dodging]], [[v0.31:Drink]]).

:Due to limitations of the wiki software, double redirects should be avoided if possible. When fixing double redirects in mainspace, please make sure to use the cv: alias as appropriate.

If no one objects, I will make this change in a few days.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:21, 15 January 2014 (UTC)

:Okay with me. It may be worth mentioning that double redirects only really need to be changed when they don't work (since changing a lot of redirects that work isn't necessary), but I think it's clearer and more relevant than the current policy. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:26, 16 January 2014 (UTC)

Done.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:55, 22 January 2014 (UTC)

I was finally able to get my extension to work after being motivated by one too many malfunctioning redirects. It now causes nonexistent pages in the main namespace to behave exactly like redirects to their DF2012 counterparts (when linked to, accessed directly, and transcluded). Double redirects also work (up to 100, in fact, although that was a temporary safety measure that I'll probably change). This means we'll be able to safely get rid of all mainspace redirects (redirects that redirect to something other than "cv" will still function if not deleted). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:20, 14 March 2014 (UTC)
:What about articles which don't exist in the current version but do exist in older versions? Will those still need mainspace redirects, or will your extension be able to automatically redirect them to v0.31/40d/23a? --[[User:Quietust|Quietust]] ([[User talk:Quietust|talk]]) 01:29, 14 March 2014 (UTC)
::It ignores all mainspace pages that actually have content, including redirects, so pages like [[masons guild]] won't be affected (unless deleted). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 01:47, 14 March 2014 (UTC)

Done and deployed. [[Cat]] is still treated as a redirect, even though I just deleted it (try clicking on the "redirected from" link). Pages that exist are ignored, so [[Masons guild]] and [[History of Dwarf Fortress]] still function normally (as a redirect to a 23a page and a non-redirect, respectively). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 18:57, 14 April 2014 (UTC)

I'm sending around a bot right now to delete all redirects of the format "foo -> cv:foo" (a surprising number don't fit this format, so I'm leaving them alone for now). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:43, 14 April 2014 (UTC)

:I'm confused. Do we use double redirects or not? Is there a single place we define our linking policy (including redirects), and is it updated?
:I had trouble linking to [[Consolidated_development]] in [[v0.34:Dragon]]. It kept pointing to v0.34:Consolidated_development, which does not exist. I ended up linking to Main:Consolidated_development to make it work. --[[User:Nahno|Nahno]] ([[User talk:Nahno|talk]]) 10:18, 1 July 2014 (UTC)

::That's a separate problem altogether - links in the versioned namespaces (v0.34, v0.31, 40d, 23a) automatically link to pages within their namespace. I may be able to set up a fallback to mainspace once I'm able to deploy again, but for now the "main:" alias is the intended solution. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 11:36, 1 July 2014 (UTC)

== Google often directs people to the 0.31 page ==

I've noticed a couple of times that finding a wiki page from an external search will often drop me onto a page from an older version. Is it possible to mitigate this somehow for new players? I could imagine something like redirecting old:Bar -> cv:Bar unless the user has come from old:Foo; no idea if that would actually work though. [[User:PeridexisErrant|PeridexisErrant]] ([[User talk:PeridexisErrant|talk]]) 11:48, 4 May 2014 (UTC)

:As a temporary solution, I could write a script that displays a banner of some kind if the user came from an external site. I'll ask Briess if he can do anything on the server level to increase the weighting of the current version's pages. (Obviously there are situations where people are looking for old pages, like [[23a:dungeon master]], so we don't want to disable indexing entirely on old pages.) —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:03, 4 May 2014 (UTC)

== DF2014? ==

As Toady [http://www.bay12games.com/dwarves/ draws closer to a new release], it might be worthwhile to discuss the addition of a new version to the wiki. The upcoming release covers two years of changes and introduces a number of new plants, foods, drinks, multi-tile trees, climbing, jumping, etc., so it is likely to have significant changes from the current DF2012. To avoid having people start new pages (and lose all the effort spent refining the prior version's page), I think it would be best to have a bot automatically copy over the DF2012 pages as a starting point for DF2014. I would suggest that these copied pages include a noticebox template mentioning that the content may be outdated, so that we can easily track which pages have been reviewed. I think either the {{tl|version check}} or {{tl|old}} template would work. --[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 19:43, 5 May 2014 (UTC)

:This is what [[User:QuietBot]] did after the 0.34 release, so it's certainly possible to use the same script to migrate to DF2014. I would like a way of tagging migrated pages, since inaccuracies in some pages went unnoticed for months after they were migrated. Since {{tl|old}} is already in use, {{tl|version check}} may be a better solution (it can be reworded slightly, or we can make a separate template for DF2014 migration). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:23, 1 June 2014 (UTC)
:Made [[Template:DF2014 migrated]] as an example. Any thoughts? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:32, 1 June 2014 (UTC)

== Redirects inconsistency ==

Following a redirect is supposed to be exactly the same as going straight to the page it redirects to, but this actually isn't the case:
* Go to [[Seeds]] and you get [[v0.34:Seed]] (outdated)
* Go to http://dwarffortresswiki.org/index.php?title=Seeds&redirect=no and click on the link and you get to [[DF2014:Seed]] (current)
So if you search for "seed", the top result is the DF2014 version. But search for "seeds" and you get the redirect, which sends you to the outdated page instead. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 23:22, 22 February 2015 (UTC)

While I'm talking about redirects, it seems redirects to sections don't work: see [[DF2014:How do I manage my seeds and crops]]. I know MediaWiki is capable of this trick because Wikipedia does it. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 23:32, 22 February 2015 (UTC)

:I have absolutely no idea why [[seeds]] redirects to a v0.34 page - it could be a Mediawiki bug. The section links issue is due to a known issue in the redirect extension we use, which has yet to be fixed. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:01, 23 February 2015 (UTC)
:It looks like deleting both [[Seeds]] and [[DF2014:Seeds]] fixed things (by allowing AutoRedirect to handle the redirects instead). Feel free to tag any others with {{tl|bad redirect}}. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:03, 23 February 2015 (UTC)
::It gets stranger. [[Vial]] redirects explicitly to [[cv:Flask]] which displays (when you look at it with &redirect=no) as [[DF2014:Flask]], but still goes to the v0.34 version. It seems redirects interpret the cv: pseudo-namespace (or whatever it's called) in an outdated way. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 18:08, 23 February 2015 (UTC)
::I've added a note to this page about this issue. If it gets resolved, the note should be removed. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 21:04, 23 February 2015 (UTC)

==Reorganizing versions==

The internet deals with moved content... poorly. Google is still linking to v0.34 pages more than a year after the switch to "DF2014", and even the wiki software still has cached links pointing to the old version pages.

I propose reorganizing versions on the wiki to avoid moving content whenever possible. Instead of having a temporary "current version" namespace that changes occasionally, all the current information gets promoted to the Main namespace. When the next version split occurs, the Main articles as of a certain revision number can be copied to the newly-created permanent "old version" namespace, while all the current information remains in Main. This not only fixes the link rot issue, but it has a few other benefits as well: fewer administrative tasks, no lockdown (a historical version of the Main pages can be copied at any point, even if the Main articles are already modified for the new version), almost all the article history is maintained in the Main article (instead of being spread unevenly across multiple versions), no "temporary" namespaces are needed, fewer problematic long redirect chains, and hopefully less user confusion (since Main gets priority in search results, etc.).

As an example, today we would not have a DF2014 namespace (which is good because "temporary" namespaces historically disappear anyway). If you ran a search for [[seed]] you'd end up at Main:seed, which would have all the current information on seeds. The version box at the top of the page would still link to the older versions of the seed article. When a new version is released, an admin would choose a revision number and copy the Main:seed article as it exists at that revision number to v0.40:seed. That's it. One historical copy that needs little to no new editing, and zero redirections/moves.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 19:02, 27 July 2015 (UTC)

:Makes sense to me. It would involve a lot of work, though (e.g. fixing templates and categories to account for the current version being in mainspace), although that should be doable thanks to {{tl|category}}, {{tl|version switch}}, etc.. A bot could be set up to copy revisions from before a release date as well, which would be more difficult (and maybe slower) than a direct copy, but not severely. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:24, 30 July 2015 (UTC)

:Actually, there are a few issues with that, namely that there wouldn't be an easy way to distinguish between versioned and non-versioned mainspace pages. There are ways to resolve Google search priority (we can exclude pages from older versions from search engine results if there are newer versions of those pages available, for example). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:47, 6 August 2015 (UTC)

::There aren't very many non-versioned mainspace pages, and determining if a page is versioned is as simple as looking for the version template and/or categories added by the version template (e.g. copy [http://dwarffortresswiki.org/index.php/Category:Current this category] instead of Main:*). The problem with "suggesting" newer pages to Google is that they obviously aren't crawling our wiki regularly (if they were, the fact that the mainspace redirects point to new pages would automatically be picked up). Even if your Google hints worked they wouldn't do anything for all the other broken links out on the 'net.--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:35, 6 August 2015 (UTC)

::: Google actually crawls the wiki constantly - we probably get crawl hits from google for a continuous block of 2-3 hours per day, each and every day. Why they are slow to update is beyond me though. I can't remember why we didn't do this initially, but there was a technical limitation involved if I remember correctly. --[[User:Briess|Briess]] ([[User talk:Briess|talk]]) 22:05, 6 August 2015 (UTC)

::: There are <meta> tags that can be used to hide pages from search results (for search engines that recognize them, that is). Searching for {{tl|av}} or [[:Category:Current]] might work, although we'd have to make sure all of the DF2014 pages include that (some pages don't, particularly some disambiguation pages, although all of them should). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:53, 6 August 2015 (UTC)

:Is there a particular reason main and current are separate to begin with?—[[User:CLA|CLA]] ([[User talk:CLA|talk]]) 00:17, 7 August 2015 (UTC)

::It's mostly intended to distinguish between versioned and non-versioned pages and make version-related templates simpler to work with, since every versioned page has a namespace. I wasn't active here in 2010 when this system was created, so Briess and Emi would know more.
::Another issue I just thought of with Loci's suggestion is categories - currently, categories like [[:Category:Animals]] are used to organize the versioned sub-categories. Sure, we can change {{tl|Category}} to categorize mainspace pages in [[:Category:v0.40:Animals]] or [[:Category:DF2014:Animals]], but that would be less straightforward because there wouldn't be a namespace with that name (until pages are migrated when a newer major version is released). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 13:05, 7 August 2015 (UTC)

:Moving current pages to the main namespace sounds like a great idea. -[[User:Jecowa|Jecowa]] ([[User talk:Jecowa|talk]]) 20:47, 4 January 2018 (UTC)

Another thought: dealing with migrating redirects could be difficult with this proposal - specifically, determining which redirects should be migrated to a versioned namespace. Redirects can't contain {{tl|av}}, at least not before ``#REDIRECT``. I ''think'' it would be possible to copy pages in two stages, though - all non-redirects first, then all redirects whose targets were also copied. Thoughts? Anything I'm missing? —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:41, 27 June 2019 (UTC)

Some subpages (particularly /raw and /Edit notice) also deliberately lack {{tl|av}}, although those shouldn't be too hard to handle. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:35, 9 July 2019 (UTC)

:Redirect pages (and all other edge cases I've looked at) can be included in categories (like [[:Category:Current]]) to determine whether or not they should be copied into an archival version. But if the redirects are "properly qualified" then they can all be copied over blindly. Mainspace redirects pointing to versioned information should use a blank namespace (which will be automatically constrained to the archival namespace); mainspace redirects pointing to unversioned information should use an explicit "Main" (which will automatically link back to the unversioned page). Then, when [[[[Toady]]]] gets copied to [[[[v0.4x:Toady]]]] it will point back to [[[[Main:Toady One]]]]. Meanwhile, [[[[Beer]]]], copied to [[[[v0.4x:Beer]]]], will properly point to [[[[v0.4x:Alcohol]]]].--[[User:Loci|Loci]] ([[User talk:Loci|talk]]) 20:00, 14 July 2019 (UTC)

::I think qualifying redirects is the best solution here - categorizing redirects manually is another possible source of errors, since categories (or a lack thereof) would only be visible on the redirect page itself, and [[:Category:Current]] is a hidden category. Copying over mainspace redirects into versioned namespaces would also resolve some issues that have come up due to those not reliably existing currently. I should be able to set up a bot script to add "main:" to current mainspace redirects (and it shouldn't break anything, since those redirects go to other mainspace pages anyway). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:57, 14 July 2019 (UTC)

(Note: I wrote all of this without noticing the previous discussion above.) I was wondering, when the wiki creates a new namespace for a major release again, if it is possible to ''not'' create a namespace for the next current version (e.g. "DF202x") and instead have the mainspace articles (which are currently redirects) become the new cv and move the content there. Therefore, [[cv:Cat]] would just be "[[Cat]]" (or [[Main:Cat]]).

Certain namespace-related templates like [[Template:Ns/0]] would need to be changed, though nothing significant as far as I know. For most cases, any "DF2014" would be replaced with "Main" or even blank. There's also multiple extensions handling the current namespace system and they may need to be modified too, though I'm not sure if or how much. I'm guessing based on the discussions above that it will change stuff up.

My reason is the current namespace is increasingly becoming more anachronistic. "DF2014" could be misinterpreted as "this page is about the 2014 version of the game" or "this page was last updated in 2014", which I've seen a few people in forums mention. Granted that [[Template:Av]] is on the top of very article, I still think the namespace is inconsistent with the recentness of the article. But how is this related to what I'm asking for? Let's say we continue the current system: if we happen to do a new namespace change this year and create DF2020, the next major release (after graphics/UI) will be mythgen, which is estimated to take several years to develop (the Big Wait), and so the anachronism will start over again. The proposed way will prevent this from occurring for the next major release and every release thereafter.

I think the confusion with having a namespace that becomes old-fashioned overtime supersedes the confusion with not marking current versioned articles with a namespace. Most users just search "Cat" on the search bar and naturally expect to get information about the latest release of DF. So if users go a page that's just titled "Cat", they won't expect outdated info about cats from a previous release. That's how the current system works anyways. We'll be skipping the two-step process that we have now. It'll make several wiki tasks much simpler as well. Editors can create new articles for current versions without remembering to add a namespace. It'll fix any existing issues with (double) redirects; instead of [[Main:Kitten]] redirecting to [[cv:Kitten]], which goes to [[DF2014:Kitten]], which then redirects to [[DF2014:Cat]], [[Main:Kitten]] would just redirect to [[Main:Cat]]. And the cv: alias will no longer be necessary since "cv:" = "Main:" and will be forever.

There's no need to differentiate the current version and previous versions with a namespace for the current version is what I'm saying. Articles of previous versions will retain their respective namespaces. Users will still type "40d:Cat" to go to the 40d version of the article, but if they want the current version, they'll just type "Cat" (like now). The mainspace containing the "live" version of an article is natural and would create no uncertainty when browsing the wiki. And it would simplify the wiki somewhat and future-proof this anachronism problem. As a bonus, this change will also prevent web search engines from showing previous version pages when typing "DF cat" or something. (This isn't happening right now as DF2014 has been the current namespace for ~6 years, but it'll happen again when everything moves to a new namespace.)

This is the gist of it, and I may have ignored most of the problems with this proposal. I have personally wished for the whole version namespacing be made less complicated and have been seeking for a solution, and I feel like this is the best way to go about in the future. – [[User:Doorkeeper|Doorkeeper]] 21:27, 14 August 2020 (UTC)

:<s>Whoops, looks like Loci already proposed this exact thing long ago. I definitely missed that discussion and should have checked first. My apologies. I'll move my text to that section and remove this one. – [[User:Doorkeeper|Doorkeeper]] 21:36, 14 August 2020 (UTC)</s> Done. – [[User:Doorkeeper|Doorkeeper]] 21:40, 14 August 2020 (UTC)

:The main issue I have with that is that putting pages about the current version in a namespace also differentiates between those pages and pages not about ''any'' version (for example, [[Toady One]] does not need a 40d or v0.34 page). Yes, we can use {{tl|av}} to mark versioned pages, but people often forget to add that to new pages. The current system also allows determining whether a page is versioned or not from its title, which makes migrations a lot faster. Relying on {{tl|av}} would require either reading the content of every page (which would slow scripts down significantly) or cross-checking with the list of all pages including the template (feasible, but a bit more complicated, and still susceptible to missing templates). I suppose that manually fixing and migrating pages missing {{tl|av}} later wouldn't be too much work, though.
:I am definitely in favor of changing "DF2014" (or a new namespace) to "Current", though. I was in favor of "DF2014" in 2014, but I don't think it makes sense anymore, and "Current" seemed to be a popular alternative in both the DF2012 and DF2014 discussions on the matter. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:02, 16 August 2020 (UTC)

== Weird redirect behaviour ==

[[Pump stack]] redirects to [[cv:Screw pump#Pump stack]]. If you look at the redirect itself it says it redirects to DF2014 namespace, which is correct. But if you actually follow the redirect, it goes to v0.34 namespace. [[User:Hairy Dude|Hairy Dude]] ([[User talk:Hairy Dude|talk]]) 16:10, 20 August 2018 (UTC)
:Yeah, that's part of the issue described in the above section (the wiki caching part, not on Google's end.) —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 15:00, 21 August 2018 (UTC)

== v50 organization ==

Some wiki admins have had a talk on Discord and decided that the most sustainable path forward is to put content for all future versions of DF in the main namespace. We will be working on a bot to do this in the next few days. Feel free to chime in with suggestions here. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 22:56, 14 December 2022 (UTC)

:Is it maybe possible to do backwards-namespacing? Like we have a "Main" namespace, which people are free to update, and whenever there's a new version of DF the "Main" namespace is copied into a namespace for the then old version, much like how you'd branch a stable branch from a development branch when working with a git-project? [[User:Therahedwig|Therahedwig]] ([[User talk:Therahedwig|talk]]) 23:13, 14 December 2022 (UTC)

::Yeah, we could do that if we decide to. We were talking about doing that for v50, actually, and might still do something similar to preserve edit history if it doesn't end up being too hard to automate. Our hope is that we will not introduce new namespaces for v50 -> v5x, unless there is a serious breaking change (and hopefully there isn't one). But if we change our mind, one advantage of the type of migration you mentioned is that it can be done retroactively - we can copy historical revisions that were current at the time of the release, and would only lose some typo fixes made after the release that apply to earlier versions as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:11, 15 December 2022 (UTC)

ETA is < 24 hours. Doing some final checks on a migration script. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 07:08, 19 December 2022 (UTC)

: We should really have a task list as there are many things that change and need updating. Including but not limited to:
:* Most templates that used the previous namespace convention broke, including nav templates.
:* Many game files changed locations and their pages need to be updated.
:* Raws need to be updated.
:* Various features added, changed, removed.
:* UI has been changed -- though I am more inclined to wait for classic release to avoid extra work --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 06:56, 20 December 2022 (UTC)

"''Raws need to be updated.''" Including applying text wraparound where necessary, I suppose - more than a few of them have proven to be that special kind of...''difficult'' to navigate otherwise, shall we say? [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 12:52, 20 December 2022 (UTC)

:There is already a task list in the [[#v50 migration|section below]] that includes templates and raws, with an explanation. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:25, 20 December 2022 (UTC)

== v50 migration ==

The initial migration script is done. New content is in the '''main''' namespace, e.g. [[Cat]]. Old content is still at [[DF2014:Cat]]. History was migrated to the ''new'' (main namespace) articles.

I know several things are broken still. Please reply if you find any others:
<div style="border-left: 2px solid red">
* <s>Versioned templates haven't been migrated yet (e.g. {{tl|vermin}} on [[Ant]])</s>
** Fixed. Most were migrated by a bot.
* <s>Raws are missing on all pages that use them.</s>
** This also affects sidebars, such as on [[Cat]] and [[Microcline]].
** Update: The DFRawFunctions extension has been upgraded to include v50 raws, using the "v50:" prefix for filenames instead of "DF2014:". <s>I haven't finished a migration script to create the /raw pages themselves, but they can typically be created manually by copying the DF2014 /raw pages and changing "DF2014" to "v50" everywhere.</s> —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 20:20, 1 January 2023 (UTC)
** Update 2: Raws have been added for all pages! They were copied from the "DF2014" pages and had "DF2014" replaced with "v50", which appears to have worked from a spot-check, but let me know if you find any problems. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:57, 4 January 2023 (UTC)
* Some pages where the DF2014 page was a redirect to a main namespace page that contained content were migrated incorrectly.
** In this case, the main namespace page is usually a redirect to itself. This can be fixed by undoing LethosorBot's edit to the main namespace page, then copying the content to the DF2014 page.
** Update: most seem to have been fixed manually - thanks! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:41, 21 December 2022 (UTC)
* <s>Some main-namespace talk pages redirect to DF2014 talk pages. Some of these redirects work, and some (usually older ones) do not.</s>
** Fixed with a bot. Some redirects from talk pages to other deleted talk pages are now broken, e.g. [[Talk:Above_ground]] (exists) -> [[Talk:Tile attributes]] (redlink). I am leaving them like that because they redirect to where the talk page should be created, but I'm also fine with people deleting them if they really want to. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:41, 21 December 2022 (UTC)
* {{tl|quality}} for new articles is disabled (see below)
* Some links from DF2014 to Main weren't working: e.g. the version selector [[DF2014:Mason's workshop]] was linking to [[DF2014:Main:Mason's workshop]] instead of [[Main:Mason's workshop]]. I'm not sure exactly why, but I fixed it with a change to the NamespaceLinks extension. Let me know if you spot similar broken links. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:19, 21 December 2022 (UTC)
</div>

—[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:54, 20 December 2022 (UTC)
:The quality levels of the 50.03 pages seem to be missing. I'm not sure if that's covered under that first point. [[User:Trainzack|Trainzack]] ([[User talk:Trainzack|talk]]) 06:47, 20 December 2022 (UTC)
::If the the [[Dwarf Fortress Wiki:Quality]] feature can be made to work with namespace scheme change, I suggest to automatically assign the lowest quality rating to all pages, alternately add the {{tl|old}} to all pages. Otherwise there will be a lot of pages that will fall through the cracks. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 09:12, 20 December 2022 (UTC)
:::I disabled {{tl|quality}} in the main namespace because it would require some rework to make the rating script and the template work properly there. Feel free to take a stab at the template. I will see what can be done on the extension side. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:14, 20 December 2022 (UTC)
::::What needs to be done on the template side? I'm not sure I see too big of an issue leaving pages as "unknown-quality" for now (or just change the default to tattered) until we get the rating script working. Is that script up anywhere, anything that could be helped with? [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 11:10, 2 January 2023 (UTC)
:::::They're already marked as unknown. Really the only issue I know of with the template is that it doesn't show up with some of the newer skins we added, and that can be fixed by getting rid of the absolute positioning. As for the script, it can be found at https://github.com/DF-Wiki/QualityRatings, and the issue is really only with the configuration system not recognizing the main namespace as valid. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:29, 3 January 2023 (UTC)
::::::Great, I started having a crack at fixing the template with different themes. Is the preference to get some CSS going and then include it in the global stylesheet (i.e different styles per theme) or to try and get a "one size fits all" fix? —[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 08:14, 3 January 2023 (UTC)
:::::::I would rather avoid custom site-wide CSS if we can. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:29, 4 January 2023 (UTC)
::::::::I appreciate that, I think it's the simplest solution to add a few lines to common.css though. Unless there is a way to attach CSS specifically to a template, I saw a few extensions that allowed that but I'm not sure if any are present in the wiki at the moment. Regardless there already exists a class `div.topicon` that is specifically for the quality ratings, is there an issue with expanding this class to accommodate the themes? The list of themes where the quality rating display is broken/invisible: Citizen, MinervaNeue, MonoBook. —[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 21:48, 4 January 2023 (UTC)
:::::::::What do you think of moving the template out of the topicon entirely and just placing it in a div? It would take up a (hopefully) small amount of vertical space in the article. [[User:Lethosor/Sandbox/Quality_test]] is an example. Unfortunately it isn't possible to prevent other templates from displaying above the quality this way ([https://dwarffortresswiki.org/index.php?title=User:Lethosor/Sandbox/Quality_test&oldid=283883]). So maybe we do need some custom CSS after all if we want that. I'm open to trying out whatever you propose. I'm a bit worried about future-proofing against skins we add later (particularly a mobile skin) but at least MediaWiki supports skin-specific global CSS as well. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:33, 5 January 2023 (UTC)
::::::::::I would rather we avoid taking any more vertical space in the article. The growing block pyramid at the top, starting with version template, is annoying. If you end up placing it inside the article space please use a slim box 100% wide that would include both.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 01:19, 5 January 2023 (UTC)
:::::::::::Agreed with you Jan, however I see that as two different tasks (ArticleVersion template changes, getting quality back on pages). I made a test adjustment to the quality and it takes up a negligable amount of extra space. See [[User:Vallode/sandbox#Page_quality]] for the example, we'd be able to completely remove "topicon" (unless it is used somewhere else?) and then potentially move on to making the ArticleVersion template into a slim version on the left-hand-side instead of a large box? Let me know what you think. --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 17:35, 5 January 2023 (UTC)

It appears some pages are redirecting recursively and never resolving correctly, like the [[https://dwarffortresswiki.org/index.php?title=Character_table&redirect=no|character table]] and [[tileset repository]] 07:35, 20 December 2022 (UTC)
: Indeed, these can be caught here: [[Special:DoubleRedirects]] --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:51, 20 December 2022 (UTC)

It might be useful to change the notice title to "release information '''for editors'''" --[[Special:Contributions/142.59.195.176|142.59.195.176]] 10:26, 20 December 2022 (UTC)
:Can do. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)
::New here, hello. Should we set a date where we remove/only show the banner for logged in users. There are (some) pages that have 4 different notices about the upgrade. [[Engraving]] is one such page, the top banner states "information for editors", we then have the "this page was migrated" banner, a version selection which warns the article might be inaccurate, and a smaller banner saying the page might need to be updated. Quite a lot of screen space, I think we can start to slowly reduce the amount of warnings this coming month? [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 10:07, 2 January 2023 (UTC)
:::Unfortunately, only showing info to logged-in users is difficult with how MediaWiki caching works. In terms of reducing warnings, there is a discussion [[Template_talk:ArticleVersion#.22Note_that_some_content_may_still_need_to_be_updated..22|here]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:43, 4 January 2023 (UTC)
:::As for [[Engraving]] specifically, the {{tl|old}} banner was actually present on [[DF2014:Engraving]] as well and got carried over with the migration. I removed it, and agree that it was redundant. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:46, 4 January 2023 (UTC)

Main talkpages seem to redirect to DF2014 talk. Not sure if it is intentional but I like it, though we should pay attention when creating new discussion relating to v50 ending up there.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 14:18, 20 December 2022 (UTC)
:That's unintentional. I specifically wrote the migration script to not move talk pages, but that has the side-effect of leaving any previously-created "Talk -> DF2014 talk" redirects intact. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)

Yo Lethosor, are we adding graphic sprites for the pages in some way? Or are we waiting for you to add some sort of new template or something? I'm sure you don't need me to tell you that the current templates don't allow that. Not sure if I'm allowed to change/create any templates either, as I don't want to break things for hundreds of pages. Edit: And IF the icons are allowed, should they be left alone, or 2×-3× sized like how the Minecraft wiki does it? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 14:29, 20 December 2022 (UTC)
:Depends on which templates you mean. There are copyright concerns with uploading a premium sprite sheet, for instance. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 16:27, 20 December 2022 (UTC)
::I'm not talking about uploading an entire sprite sheet. I'm just talking about individual icons for each respective page. One image for cows, one for horses, one for werebeasts, etc. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 16:50, 20 December 2022 (UTC)
:::If we do that for every creature in the sprite sheet, that's not much different (in terms of copyright) from uploading the entire sprite sheet. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 17:09, 20 December 2022 (UTC)
::::Is there someone we can talk to about that? We finally get this new game with graphics, and then we can't use the very graphics of the game? No matter what the rules are, I'd say that would be the stupidest thing ever. I know I'm infamous here when it comes to copyright and images and stuff, but about 80% of game wikis out there are completely unofficial, and use game file images like no one's business. I can't imagine anyone's door being knocked on if we used the game's sprites, but I won't add any here until we have a go-ahead. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 17:14, 20 December 2022 (UTC)

:::::...I've made noise in Mayday's direction on this matter, at least (prob an incorrect maneuver, ''but'').[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 17:55, 20 December 2022 (UTC)
:::::: I hope some sort of arrangement can be made so we can use the new sprites with permission/limits, just as we are using the raw files. Otherwise we are all (devs and editors alike) shooting ourselves in the foot here.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 21:07, 20 December 2022 (UTC)

:::::::I just thought of something. We're supposedly not allowed to upload entire sprite sheets, right? What if - for the time being - we just use a few of them for the purpose of testing out new infoboxes? --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 21:46, 20 December 2022 (UTC)
::::::::I don't know. If someone could ask Kitfox and post the response here, that would be great. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:47, 20 December 2022 (UTC)

:::::::::I've reached out to Alexandra, but she hasn't answered yet. Until then I found these old approvals from the previous community manager, Feeona: ([http://www.bay12forums.com/smf/index.php?topic=173474.msg8243633#msg8243633 link1], [http://www.bay12forums.com/smf/index.php?topic=176640.msg8243642#msg8243642 link2]). Waiting for a newer response until we begin mass uploads is probably the politer option, but like Zippy said, it is also standard for wikis to use game sprites with less approval. I second their idea of trying it out with a few images to test the infoboxes. On the extreme off-chance (and I do think it is) Kitfox protests we can always remove these few. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 22:19, 20 December 2022 (UTC)
:::::::::And here is a third, more official statement: ([http://www.bay12forums.com/smf/index.php?topic=173474.msg8249718#msg8249718 link3]). Perhaps that address of info@kitfoxgames.com is the better channel to ask for a confirmation, rather than Discord DMs, but I will be going to bed, so it is best if someone else does that. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 22:29, 20 December 2022 (UTC)
::::::::::Thanks for tracking this down! Ok, sprites should be fine, but let's avoid uploading the entire premium tileset as a single image, for instance (as the forum thread says, "use common sense"). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:21, 21 December 2022 (UTC)
::::::::::: Looks good, permission is always preferable over fairuse, I think it is a win win for all involved. I agree that we shouldn't upload entire sprite sheets (e.g. there is no reason to upload the windmill from every direction or whole construction phase for workshops) and that there are a lot of details that needs to be ironed out through testing. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 05:07, 21 December 2022 (UTC)
:::::::::We have a green light on uploading all and any sprites. Their response to me can be seen [https://i.imgur.com/BhmHjzC.png here]. I'm sure someone else confirmed it before me. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 19:00, 21 December 2022 (UTC)

Shifting temporarily to a new issue, is the documentation of [[Template:ArticleVersion]] outdated? It would seem so to me, since the current version no longer has its own namespace, with the templates needing updating being different ones. --[[User:Voliol|Voliol]] ([[User talk:Voliol|talk]]) 18:30, 20 December 2022 (UTC)
:I think it is still accurate enough. We left open the possibility of making another namespace in the future, albeit with a different migration strategy - see [[#v50 organization|above]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 21:52, 20 December 2022 (UTC)

Some Changes to infoboxes might be needed. Too bad [[User:Doorkeeper]] isn't around. He did a great work with navbox project--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:52, 21 December 2022 (UTC)

I just realized that raw files aren't stored as regular wiki pages but loaded via the DFRawFunctions extension (hence the need to update). Good news it's going to be handled in bulk, consistently and relatively easy to updated. Even better it's Lethosor problem ;) Also I just realized that all the "raw files" (txt files in the new vanilla folder) are released into the public domain. Both are probably not news to the vets but I'll leave it here for those who less up to date like myself. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:35, 22 December 2022 (UTC)

: I noticed that some templates aren't working properly in the new namespace, e.g. [[Basalt]] entry had its raw updated manually but the infobox fail to show any details. Cursory look suggest {{t|layerlookup/0}} need a minor tweak. This should do the work
:: Replace: <nowiki>{{layerlookup/aux|{{{{FULLPAGENAME}}/raw}}|uses={{{uses|}}}|wiki={{{wiki|}}}}}</nowiki>
:: With___: <nowiki>{{layerlookup/aux|{{</nowiki>:<nowiki>{{FULLPAGENAME}}/raw}}|uses={{{uses|}}}|wiki={{{wiki|}}}}}</nowiki>
: Not sure what the plan and ETA with raws update so I didn't touch this high usage template for now. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 08:11, 24 December 2022 (UTC)

::Please do feel free to make this update. I am still working on a script to create the <code>/raw</code> pages themselves. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:12, 1 January 2023 (UTC)

Wouldn't it be an idea to add to the Sitenotice to remove the {{tl|migrated article}} tag when an article has been fully updated? I see many articles that seem to be updated still have the tag. And/or advise to make use of the {{tl|verify}} for sections still in need of checking? --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 10:12, 2 January 2023 (UTC)
:Probably a good shout. The "see this page" link does include the detail on removing but we should more explicitly encourage removing the banner once a page has at least been looked over. [[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 11:01, 2 January 2023 (UTC)

== v50 specific issues ==
=== Graphics===
Follow up on the use of game sprites and the need to trying it out with a few images to test the infoboxes. First sprite [[:File:Beds v50.png]] was uploaded and used on [[Bed]] entry. Any thoughts? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:06, 21 December 2022 (UTC)
:Seems like it should be rearranged to be horizontal. Also, has there been a serious discussion about copyright? Full screenshots are 100% fine, but you start going into a grey area when you upload pieces of a spritesheet. I'm of the opinion that it's all fine as long as it's inconvenient to reconstruct the full sheet from the individual images. Maybe a further restriction could be you shouldn't upload any of the art unless it's used in an infobox (maybe an exception for pieces of the UI). And one more restriction could be you shouldn't show everything, like in your bed example, maybe just the wooden bed is good enough, leave out the stone and metal, especially since those can only be made from strange moods. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:43, 21 December 2022 (UTC)
::Actually, your bed image is kinda bad for showing off what a bed looks like because it doesn't show the pillow/blankets. That might point to cropped screenshots being the best path, although less convenient for the uploader, as you don't get details left out. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:46, 21 December 2022 (UTC)
::I created a new license template [[Template:Copyright game]], based it on the way the RimWorld wiki does things. Call it a prototype, but it's probably how your bed image should be labelled. Indeed, I added it to it already. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]])

::: I agree that the horizontal arrangement would suit better here and that we should strive to represent how things look in-game. Otherwise, I am not too concerned about people being able to reconstruct anything (lets just say that ''anyone'' interested in that can get the real thing from the game files), also it seem we have permission to use the sprits on top of fairuse. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 19:55, 21 December 2022 (UTC)

::: Modifying the existing template to allow the inclusion of the new sprites is easy (Something like [https://ibb.co/zFXCrjd this]?) The big question is the matter of consistency is there any exceptions that will break the format (size wise with variant bloat for example), the sprite naming format, etc --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:44, 21 December 2022 (UTC)
::: If we are going to show a variant for each material type, then maybe these should be added as separate images so we can add a tooltip for each image. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 20:49, 21 December 2022 (UTC)

:I've got another prototype going here and here: [[User:Brightgalrs/vector.css]] and [[User:Brightgalrs/Sandbox]]. (You'll need to add the css stuff to your own /vector.css). Basically it's a way to recolor images using css classes. No idea if there's a better way. Also, the real implementation would require a change to [[MediaWiki:Common.css]]. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 22:41, 21 December 2022 (UTC)
:Should mention, there ''is'' a different way, just upload each image 16 times, one for each coloring. But maybe that's not very elegant. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 22:45, 21 December 2022 (UTC)

: It should be noted that soon the classic edition will be released, hence one should plan to have both the Premium and classic alongside in that little space --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 03:14, 22 December 2022 (UTC)
::I'm looking into a tab extension to potentially support this in infoboxes. Perhaps [https://www.mediawiki.org/wiki/Extension:Tabs Extension:Tabs]? I tried [https://www.mediawiki.org/wiki/Extension:TabberNeue Extension:TabberNeue], but it displays a placeholder if JavaScript is disabled, which isn't great. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:22, 22 December 2022 (UTC)
::: The Neue Tabber seem to works pretty much like the old one (which fandom [https://coding-help.fandom.com/wiki/Tabber#Adding_images_into_tabbers still use]) defaulting to showing the first tab only. Quick look suggest that neue work the same, plus the notice that 'Tabber requires Javascript to function' warning? if so, and if it is a bother, then you should be able to edit out the tabberneue-noscript string in code. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 06:29, 22 December 2022 (UTC)
::: I much prefer your tabber solution, but if that fails we can also use the gallery slideshow mode. If so, beware it has no way to control image size so the images have to be maliciously uploaded using the exact same size. example:
<gallery mode="slideshow">
File:SteelSample.png
File:TinSample.png
File:ZincSample.png
File:GoldSample.png
</gallery> --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 10:19, 22 December 2022 (UTC)

==== adding premium set to Infobox ====
I am unclear where are we going with this? 
1) Will (A) tabs be implemented, (B) we be using mediawiki toggle [[Template_talk:V50_workshop|example]] for premium and classic/blocked, (c) put images side by side, or (d) something else? 
2) Also [[silver]] and [[Pig iron]] use very different image style for example. 
3) Anything else you want ? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 12:32, 30 December 2022 (UTC)

: Personally, I would love tabs to be implemented, but I think that side by side might be best for most. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 12:32, 30 December 2022 (UTC)
: Here is rough layout we can use. It should fit most buildings given the default sprite size. There is also a different floor plan for both (inspired by reddit)

{|
|- valign=top
|
{| style="width:200px; background-color:#eaecf0; border-collapse: collapse; "
|+ 5×5
|- style="border-bottom:2px solid #3366cc; "
|<div class="mw-customtoggle-infoboxtab mw-ui-button mw-ui-progressive" style="border-top-right-radius: 10px; border-top-left-radius:10px;">toggle</div>
|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|- valign=top
|colspan=2|<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">
[[File:Siege workshop.png|center|160px]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab"">
{|
|rowspan=2 style="width:50%; font-size: 125%;"|<center>{{Template:Picture Siege workshop}}</center>
|style="line-height: 1em; font-size: 125%;"|
{| style="border-spacing:4px;"
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#86878a; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:12px; height:12px; background-color:#b7b9bd; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|}
|
{| style="width:200px; background-color:#eaecf0; border-collapse: collapse; "
|+ 3×3
|- style="border-bottom:2px solid #3366cc; "
|colspan=2 style="text-align: right;"|<div class="mw-customtoggle-infoboxtab mw-ui-button mw-ui-progressive" style="float:left; border-top-right-radius: 10px; border-top-left-radius:10px;">toggle</div>{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|- valign=top
|rowspan=2 style="width:50%;"|
<div class="mw-collapsible" id="mw-customcollapsible-infoboxtab">[[File:Carpenter's workshop.png]]</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-infoboxtab""><center>
{| style="font-size: 175%; border-spacing: 0; background-color: black; border: 2px solid black"
|- 
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"| {{Raw Tile|"|7:0:0}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|{{=}}|6:0:0}}
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"|
| style="padding: 0; line-height: 1em"|
|-
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|]|0:0:1}}
| style="padding: 0; line-height: 1em"| {{Raw Tile|░|0:7:1}}
|}</center></div>
|
{| style="border-spacing:5px;"
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
|-
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#b7b9bd; border:1px solid #545557;"|
| style="width:18px; height:18px; background-color:#86878a; border:1px solid #545557;"|
|}
|-
| style="text-align: center;" | Layout
|}
</div>
|
{| style="width:200px; height:100px; padding:10px; background-color:#eaecf0; border-collapse: collapse;"
|+ 1×1
|- style="border-bottom:2px solid #3366cc;"
| colspan=3 style="text-align:center;"|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|-
| style="border-right: 1px dotted #545557;"|[[File:Screw_press.png|32px|center|link=]]
| style="font-size:125%;"|<center>{{Template:Picture Screw press}}</center>
| style="border-left: 1px dotted #545557;"|<center>{{Template:Floor Plan Screw press}}</center>
|}
|
{| style="width:200px; height:100px; padding:10px; background-color:#eaecf0; border-collapse: collapse;"
|+ 1×3
|- style="border-bottom:2px solid #3366cc;"
| colspan=3 style="text-align:center;"|{{Tooltip|Hotkey|adasdasdasd}}: {{Key|b|o|g}}
|-
| style="border-right: 1px dotted #545557;"|[[File:water_wheel.png|32px|center|link=]]
| style="font-size:125%;"|<center>{{Template:Picture Water wheel}}</center>
| style="border-left: 1px dotted #545557;line-height:normal;"|<center>{{Template:Floor Plan Water wheel}}</center>
|}
|}
:Any thoughts on the direction and or any and all of its elements? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 10:16, 31 December 2022 (UTC)

::I kind of like side-by-side, if it fits. If anyone wants to implement a toggle button or tabs, I would ask that that be implemented in a template for now, so that e.g. we could change a toggle button to tabs in a single place if we decide to install an extension to support that. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:14, 1 January 2023 (UTC)

::: I noticed a comment saying that [[impassable tile]] are no longer used in v50, is that true for all constructions? If so, floor plans are no longer needed, making things much easier as we can fit everything in except the 5v5 constructions like trade depot (and even these can be placed one above the other if so desired). If not, any thought on the alternative floor plan design? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:46, 1 January 2023 (UTC)

:::: None of the constructions have blocking tiles any more from my experience playing. I haven't tested siege weaponry with that stuff, but none of the workshops have it, nor does any furniture. (walls and fortifications will of course obstruct movement [[User:AndrielChaoti|AndrielChaoti]] ([[User talk:AndrielChaoti|talk]]) 18:47, 1 January 2023 (UTC)
::::: Ok, I have removed them from v50. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 23:48, 1 January 2023 (UTC)

I have added a basic side by side variant to [[Template:V50 workshop]] and [[Template:Building]] for testing, let us know if there any issues. Few notes:
* The default image naming scheme of <code>workshop-name.png</code> will likely conflict with existing images here or on commons, maybe another naming scheme should be used like <code>v50 workshop-name.png</code> as it is with ascii pictures.
* There is inconsistency in image size. If you want to use large zoomed images then toggle is best, otherwise they need to be all in native size (96px for 3x3).
* In the current version the code roughly centers the images and if there is a big image like with [[Siege workshop]] it drops to a new line --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 23:48, 1 January 2023 (UTC)

How about combining shortcut keys and the new menu icons:
<div style="color:white; font-size: large; text-shadow: -1px -1px 0 #000, 1px -1px 0 #000, -1px 1px 0 #000, 1px 1px 0 #000;">[[File:Ui b.png]]<div style="position: absolute; bottom:-14px; right:3px;">b</div>[[File:Ui bo.png]]<div style="position: absolute; bottom:-14px; right:3px;">o</div>[[File:Ui bol.png]]<div style="position: absolute; bottom:-14px; right:3px;">l</div>[[File:Ui boll.png]]<div style="position: absolute; bottom:-14px; right:3px;">l</div></div>
--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 02:24, 3 January 2023 (UTC)

:I worry that this is difficult to read (I read it as "boil" at first). I would rather use something like {{tl|k}} with a known background. What about something like this? [[File:Ui boll.png]]<div style="position: absolute; bottom:-14px; right:0px;">{{k|l}}</div> or, alternatively, using flexbox without any overlap: [[File:Ui boll.png]]{{k|l}} —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:37, 3 January 2023 (UTC)
:: Same, but that is the best I came up with. We can use the key or maybe someone can help improve the design. Also 'l' is hard to read even with {{t|key}}.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 03:05, 3 January 2023 (UTC)
:: I added a {{t|Menu icon}} to start things so others can have a go with it. Also any thoughts on the icon naming convention (their shortcut sequence), is there easier/better way? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 09:36, 3 January 2023 (UTC)
::[[User:BarelyCreative]] updated the template: {{Menu icon|b|o|l|y}}. I think it looks good, thoughts? --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:40, 3 January 2023 (UTC)
:::I like that, yeah. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:29, 4 January 2023 (UTC)
::::There were some places where it didn't make sense so display every icon all the time (like step-by-step guides), so I changed it slightly to allow display of fewer icons using "num" and counting from the end: <nowiki>{{Menu icon|b|o|l|y|sep=-;|num=2}}</nowiki> {{Menu icon|b|o|l|y|sep=-|num=2}} [[User:BarelyCreative|BarelyCreative]] ([[User talk:BarelyCreative|talk]]) 09:05, 4 January 2023 (UTC)

==== Bizarre palette-swapping idea/prototype ====
No idea if this is a good idea, since it takes a bit of time to set up, and there might be some performance issues... and maybe display issues?

But take a look at this:
{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock|palette-name=amber}}

It's way to swap palettes on an image, although the image itself is a table, with each cell representing a pixel. The template itself looks like this:
<code><nowiki>{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock|palette-name=saffron}}</nowiki></code>
Input the pattern and desired palette name.

I've got a larger showcase here: [[User:Brightgalrs/Sandbox/PaletteSwapShowcase]]. Only did a rock pattern so far, but all palettes are implemented.
The major use for this would be on each stone, metal, wood, etc. type's page. The palette could be read directly from the raws. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 03:22, 24 December 2022 (UTC)

:From a technical perspective, my primary concern is indeed performance. Both on the server side and client side, a large number of tables that large (in terms of markup and cell count, that is) tend to be resource-intensive to generate and render. I saw your image-filtering experiments on [[User:Brightgalrs/vector.css]], and while that strikes me as a newer and less-backwards-compatible approach, it would probably be more resource-friendly.
:Is this color adjustment something the game is doing natively? i.e. does this accurately match what the game displays? I bet we could slap together an image-filtering extension (or find an existing one?) that can do this if needed. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 03:49, 24 December 2022 (UTC)
::Yeah that's what I suspected. The images the template creates are spot on, checked it against a screenshot I took of some mica rocks in-game. The css stuff is unfortunately totally incorrect, was cool to learn about it though, so not a complete waste of my time :p. The premium, in-game graphics are true sprites, basically patterns of indexed colors. Each of the in-game colors (which are significantly expanded over the 16 ascii colors, there's 116/117) there is a palette defined in "\Dwarf Fortress\data\vanilla\vanilla_descriptors_graphics\graphics\images\palettes.png". Each indexed color of the sprite is swapped for the corresponding color in the palette. Because of that, the css stuff doesn't work since it's doing the hue/saturation/brightness changes to the entire sprite.
::I've looked into an existing mediawiki extension, couldn't find anything. One thing I did't really look at is some type of lua script/module that would basically emulate what the game is doing. So some function that takes in the base image as well as the desired palette, and based on that finds and replaces each color. No idea what mediawiki's capabilities are on that front. [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 05:31, 24 December 2022 (UTC)
:::We do have Scribunto installed now, so it's totally possible to do something in Lua too - forgot about that. I can add you to the group that grants access to edit the Module namespace if you want to give that a shot. If we use an extension, we'd probably need a custom one, similar to DFDiagram (or perhaps DFDiagram could be extended - it's in dire need of a rewrite anyway). —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:43, 24 December 2022 (UTC)
::::I asked around on the mediawiki irc, I think scribunto/lua is a deadend, at least for taking an uploaded image and doing stuff to it with a lua script. However I did come up with this even more bizarre solution, using block elements. [[User:Brightgalrs/Sandbox/PaletteSwapShowcase2]], maybe less resource intensive? Definitely displays a lot worse though, probably unusable.
::::{{User:Brightgalrs/Sandbox/PaletteSwitch|templatename=User:Brightgalrs/Sandbox/Rock2|palette-name=saffron}}
::::I dunno, maybe none of this is worth it and we should just write some external program to put all the images together offline, and then just mass upload. It wouldn't be ''that'' many... [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 06:37, 24 December 2022 (UTC)

====Is there an easy way to just paste images from the clipboard?====

I use KDE spectacle to take screenshots straight to the clipboard (after cropping) -- is there an easy way to just paste (and auto-upload) an image into an article? It would make it a lot easier to contribute images. [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 23:35, 1 January 2023 (UTC)
:Unfortunately there is not. I would be open to a MediaWiki extension to support this if someone finds one. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:32, 2 January 2023 (UTC)
:: Looks like this could do it, but I haven't used it before: https://www.mediawiki.org/wiki/Extension:SimpleBatchUpload [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 19:41, 2 January 2023 (UTC)

====Standards for adding graphical version screenshots and images====

Hello, new user looking into adding imagery from the new version. Is there a standard for quality of new screenshots or images? I noticed that at a certain zoom level (2 zooms in from the furthest zoomed-out view), the graphics appear crisp and 1:1 pixel scaled, and I would propose that all images be taken at this scale whenever possible. If they need to be displayed larger, they should be nearest neighbor scaled in a photo editing program at 100% increments (Microsoft Paint will do this if you first select the image rather than directly scaling the whole canvas). I would also propose that images should be cropped to conform to the 32x32 pixel grid when possible, though this could be problematic with so many new graphical elements exceeding the bounds of their tiles. I would say the best practice for capturing artwork for items, furniture etc. ought to be done in a 3x3 open area to avoid shadows from nearby walls, or else extracted from the raw files (if this doesn't run afoul of being able to re-create the graphical version using those assets).

I know that perfect is the enemy of good, and any documentation is better than none, but just thought I'd ask about this, and see if/where something like this ought to be posted. [[User:Unclesporky|Unclesporky]] ([[User talk:Unclesporky|talk]]) 13:58, 3 January 2023 (UTC)
:It has been stated in [[Template:V50 workshop]] that <q>screenshots should be at the "native" resolution</q> but someone could edit the [[Screenshot]] page for best practice for the steam version. Or post some examples in [[Talk:Screenshot]] to find out what is best? --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 14:21, 3 January 2023 (UTC)

====How would I/should I go about putting creature sprites on their pages?====

Howdy. New player and wiki user here. I wanted to try and help update the wiki to the Steam release of DF, so I figured I'd chip in by putting each creature's sprites on their respective page, since I'll often look up a creature I have yet to see in game only to be met by a blue J, or whatever. I found all of the game's creature sprites in C:\Program Files (x86)\Steam\steamapps\common\Dwarf Fortress\data\vanilla\vanilla_creatures_graphics\graphics\images, so I figured I could just chop those up in Photoshop and stick them on here no problem, but the programming syntax/whatever it is on this site is incredibly confusing, I don't know how I'd actually go about doing it. I figured I'd just find the spot on the page where the little letter is and replace that with the image code, but it seems the pages are built using heavily nested templates that I can't even begin to understand. Any help?--[[User:Treese|Treese]] ([[User talk:Treese|talk]]) 03:07, 5 January 2023 (UTC)
:Based on [[User:Zippy|Zippy]]'s work at {{tl|Creaturelookup_b}}, I added an "image" parameter to {{tl|creaturelookup/0}}, which is what creature pages should all be using. See [[Dwarf]] and [[Cow]] for examples. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:37, 5 January 2023 (UTC)

=== Hotkeys/Menu navigation ===
Most key bindings and menus have changed. Should the article reflect a) only the old version, b) only the GUI version or c) both? For example, [[Bridge|bridges]] used to be built via {{k|b}} -> {{k|g}}, but now it's in Place strucutures {{k|b}} -> Constructions {{k|n}} -> Bridge {{k|b}}. What should be written in the article? Currently, it's {{k|b}} -> {{k|g}}. I ''think'' it should be only b), but I am not sure if there will be differences regarding hotkeys or menus between the premium version and the free version and then, c) would be the most appropriate option. --[[User:Prometherus|Prometherus]] ([[User talk:Prometherus|talk]]) 10:16, 22 December 2022 (UTC)

: Not sure. I wish the classic release soon --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 16:45, 22 December 2022 (UTC)
:: Are you Toady's herald? Looks like it was just released! [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:18, 22 December 2022 (UTC)
:: And our questions are answered, the old hotkeys seem to have been thrown out. Part of me is disappointed (useless muscle memory) but also relieved (unified UI for both versions is good in general and for the wiki). [[User:Brightgalrs|Brightgalrs]] ([[User talk:Brightgalrs|talk]]) 18:25, 22 December 2022 (UTC)
::: According to info, in a sort of 'demo version' at that. I'll wait a little while longer, for myself.[[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 18:22, 22 December 2022 (UTC)
::::It's unlikely that keybindings in it will change significantly. My vote is that we should include information for both premium and classic, everywhere. Hopefully the keybindings are not different between versions. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 18:26, 22 December 2022 (UTC)
:::Shouldn't it be based on the 50 or what verion the article is written for? [[User:Dominick|Dominick]] [[User_talk:dominick|(TALK)]] 18:42, 22 December 2022 (UTC)
:::: The keybindings seem to be consistent between versions, (haven't checked exhausitvely, but since the menu layout is the same I think it is a good assumption). Should also keep in mind/consider that not all actions have keybindings. An option would be write 'Click on the <Example Text> icon or press {{k|E}}' [[User:Koos|Koos]] ([[User talk:Koos|talk]]) 23:14, 23 December 2022 (UTC)

=== Removed features & concepts ===

Since they're removed concepts, I've set [[Room]] to be a redirect for [[DF2014:Room]] and created [[Template:Activity zones]] for the nav bar bedrooms, etc, and made the necessary changes to [[Bedroom]] for it. Is this the correct approach, before I go on much further? (also a note, if it is, then [[Template:v50_rooms]] probably needs to be deleted) I also imagine that considering the number of changes in the interface, that things like [[Adventure mode]] and related pages might best be truncated to "not in 50.03" and when it does make it across, being more deliberately brought over in pieces? [[User:HawkOwl|HawkOwl]] ([[User talk:HawkOwl|talk]]) 06:23, 23 December 2022 (UTC)

:Usually it is marked with [[Template:Removed_feature]]. For example: [[Dipscript]] or [[Party]]. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 07:45, 23 December 2022 (UTC)

:: Ah, that's fair. Should that be mentioned in [[Dwarf_Fortress_Wiki:Versions#Redirects]]? [[User:HawkOwl|HawkOwl]] ([[User talk:HawkOwl|talk]]) 10:03, 23 December 2022 (UTC)

:::I think the redirect policy mostly had in mind things that were removed a ''long'' time ago, like [[Tax collector]] and [[Economy]] (and the latter actually has a stub page as well). I guess we could clarify. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 19:34, 23 December 2022 (UTC)

:::: The "current" redirects also cause the version box to incorrectly show that the current version has a page - e.g. [[23a:Cave_river]] shows a v50.04 version, but it's just a redirect back to that version. Similarly, what should happen to redirects like [[Clothes maker]], where a concept has evolved? It currently goes to [[23a:Clothes maker]] - that's correct if the user is trying to look up a very old concept, but if a new user is looking for "how to make clothes", they should be directed to [[Clothier]]. --[[User:Danny252|Danny252]] ([[User talk:Danny252|talk]]) 12:16, 26 December 2022 (UTC)

:::: One should be careful with cv redirects. Most that were recently adjusted were unused plural forms (that should probably be deleted) but few like [[Crown]] needed that for backward compatibility. Removing the [https://dwarffortresswiki.org/index.php?title=Crown&type=revision&diff=279966&oldid=219482 cv part] means the the link on [[v0.31:Tilesets]] is now broken. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 22:30, 26 December 2022 (UTC)

:::::If [[v0.31:Tilesets]] is about v0.31, it should not be using "main:" in its links - ''all'' of those links are going to pages about v50, not v0.31, regardless of whether the target is a redirect or not. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 23:37, 26 December 2022 (UTC)
:::::: You right, I removed it. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 17:55, 27 December 2022 (UTC)

Crown cv redir issue is now fixed, I believe. As goes with such cases where one can simply revert the troublesome edit, unless I've mistepped, myself? [[User:Silverwing235|Silverwing235]] ([[User talk:Silverwing235|talk]]) 23:52, 26 December 2022 (UTC)
:Both [https://dwarffortresswiki.org/index.php?title=Crown&diff=prev&oldid=280026] and [https://dwarffortresswiki.org/index.php?title=Crown&diff=prev&oldid=279966] should not have had any effect, because "cv" is an alias to the main namespace now, just like "main". Proof: [[Crown]], [[cv:Crown]], [[main:Crown]]. It's possible caching is coming into play here, although I purged the redirect cache after making that alias change earlier this month... —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:02, 27 December 2022 (UTC)

I think there have been some changes not captured, but as a newb, I'm afraid to edit the page(s). A good example is Strawberry. I'm playing the Steam version right now and Strawberry plants are "not relevant to brewing" in Labor > kitchen > veg / fruit / leaves. Unless I'm mistaken and need to process them? Another example is the trade caravan = it seems the 3 square pathing no longer happens; it's just yak(s). 12:31, 28 December 2022 (UTC) 12:29, 28 December 2022 (UTC)
:Strawberries should be brewable according to the Raws.
:Trade wagons has been modified in v50. The first wagons will arrive at the same time your fort is becoming a barony. Until then, it's only pack animals and stairs are indeed fine. The [[Trading]] page needs a huge rework anyway... I'll try to do that next week. --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 13:40, 2 January 2023 (UTC)

<s>As far as I can tell, none of the workshop buildings in v50 have blocking tiles any more. There's a comment to the like in data/vanilla/vanilla_buildings/objects/building_custom.txt that says this "[BLOCK:1:0:0:0] workbenches no longer block". Hesitant to update that template as I'm not sure if it's referenced for all of the old versions too. </s> [[User:AndrielChaoti|AndrielChaoti]] ([[User talk:AndrielChaoti|talk]]) 05:54, 29 December 2022 (UTC)
: A new template has been created: {{tl|V50 workshop}} --[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 13:40, 2 January 2023 (UTC)
::Thanks! In general, I would like to delegate the switching responsibility to the template (like how {{tl|creaturelookup/0}} works), but in cases where the parameters diverge significantly like with workshops, it could make sense to make an entirely new template. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:40, 3 January 2023 (UTC)

=== creature infobox prototype (moved) ===

Check it out, I made a temporary template and added it to the [[cow]]s page. Now it shows the sprites (but not the zombified versions yet). I wanted to show everyone a prototype of what v50 creature infoboxes should look like. Or at least something similar to it. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 19:11, 27 December 2022 (UTC)
:Hi, I'm new to editing wikis but I have done a bit of work with sprite sheets and I've been going through the DF data files to find the different graphics hoping to help with the animal pages. I've thrown together a template with grass and a few nature sprites (plants, a tree, and a rock) for size reference but I'm unsure how large the 'display' tiles in the middle of the template should be to suit all animals. I can see in the sprite sheets that some land animals have an adult and child sprite, so two tiles. Others have a male, female, and child, but after seeing you include the zombie cows I'm unsure if I should make it twice the size to add them too. Alternatively, I could grab some tiles from the haunted biomes for the zombie animals and make a separate template for a side-by-side comparison. Either way, let me know if this helps. I'd like to help with other graphics too as we add the premium tilesets but the animals seemed the easiest to tackle with me being new to wiki editing. ~~[[User:UristTheSeventh|UristTheSeventh]] ([[User talk:UristTheSeventh|talk]])
::@Zippy, I am a bit perplexed about the purple cows. Why do we need a zombified version of creatures on every page?
::@UristTheSeventh, we can use all the help. Maybe post an example, so that we can have something to compare and contrast.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 11:49, 3 January 2023 (UTC)
:::@Jan Here are the examples:
:::[[File:Creature template.png]] [[File:Armadillo.png]] [[File:Seagull.png]]
:::It'll need to be wider or arranged differently for different creatures with more that two sprites or for multi-tile creatures. I can also do an aquatic and air themed template for swimming and flying creatures. ~~[[User:UristTheSeventh|UristTheSeventh]] ([[User talk:UristTheSeventh|talk]])
::::Looks nice, like the metal template. There are several people working on updating the graphics you should talk more among yourselves. Best I can offer is that I width wise I am hoping to go up to 200px for infoboxes.--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 01:13, 5 January 2023 (UTC)

=== When do we remove the migration note on specific pages? ===

At what point can we remove the "this page was auto migrated from v47" warning? There are a bunch of small pages that are more or less accurate, if I've reviewed them, can I go ahead and remove the warning? [[User:Kelvie|Kelvie]] ([[User talk:Kelvie|talk]]) 23:33, 1 January 2023 (UTC)
:Yes, feel free to remove it if you think all content is accurate. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:31, 2 January 2023 (UTC)

=== Any info on fixing "creature description not found?" ===

I see this issue on most creature pages, it seems to be due to a lookup that's not currently functioning? Cows interestingly doesn't have this issue but I couldn't figure out how to recreate whatever fix it's editor did. --[[User:Yallendallis|Yallendallis]] ([[User talk:Yallendallis|talk]]) 00:22, 3 January 2023 (UTC)
:That is the missing raws issue described above. Cow was fixed by the addition of [[cow/raw]]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 02:28, 3 January 2023 (UTC)
::Ah makes sense, not fully used to the language of wikis yet so I read over it while looking. To put this bit of questioning to rest for any future readers, is it correct that it's fine to update any raws manually, though it will be done automatically at some point? --[[User:Yallendallis|Yallendallis]] ([[User talk:Yallendallis|talk]]) 07:48, 3 January 2023 (UTC)
:::Yes. I'm circling back to work on a script right now, so not much point in doing it if you're reading this. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 04:57, 4 January 2023 (UTC)
:::This should be fixed now. If you continue to see pages with problems, you can try [https://www.mediawiki.org/wiki/Manual:Purge purging the cache]. —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:59, 4 January 2023 (UTC)

=== Adventurer Mode related sections ===

The topic has already been discussed [[#Removed features & concepts|above]], but I don't see a clear line on what to do with article sections that mention Adventurer Mode. Like for example in [[Butcher#Adventurer_mode|Butcher]].

'''a) Truncate''' or '''b) leave in place with a mention''' that the mode is not yet present IG but will be added in a future update?

Personally I think option b) is better, because I think it's silly to undo some work just to reintroduce it a few weeks later, with the necessary corrections. Even if a copy/paste of a previous version takes ~15 seconds, considering the number of articles that need to be corrected, it would be a bit of a waste of time.--[[User:Halavus|Halavus]] ([[User talk:Halavus|talk]]) 14:22, 3 January 2023 (UTC)

== Toggleable image ==

Any objections/comments to using this template for now for toggling between classic and premium images? I'd probably rename it to "Template:Premium-classic thumb image". I'm sure someone can come up with a better UI eventually, but should be easy to migrate at that point. I also think we should use the same customtoggle class for this and for the infobox. [[User:NiftyManiac|NiftyManiac]] ([[User talk:NiftyManiac|talk]]) 23:12, 1 January 2023 (UTC)

{{User:NiftyManiac/Sandbox/TemplateDualImage|
premium=File:Quickstart-finder.png|
classic=File:Quickstart-finder-partial.png
}}

{{User:NiftyManiac/Sandbox/TemplateDualImage|
premium=File:Quickstart-finder.png|
classic=File:Quickstart-finder-partial.png|
caption=My caption|
width=100px
}}

:This looks nice to me! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 00:30, 2 January 2023 (UTC)

: Good initiative. From the top of my head:
:* I suggest using a shorthand, no one wants to type 'Premium-classic thumb image'.
:* If we end up using toggle for infoboxes (not sure where we headed there), then I agree definitely same custom toggle class should be used for all, thus allowing to switch premium-classic view on the whole page at a click.
:* The button part on a separate row isn't pretty, creating a lot of dead space that can be used by the text. Are we set on the label 'toggle ascii'? Classic isn't Ascii per se, maybe we can use a 'toggle' with a tooltip {{tooltip|for example|does bla bla bla}}, or maybe we can get rid of the text and have a smaller icon button ([[User:Jan/sandbox#Metal_example|two examples]]).
: I hope that helps. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 11:21, 2 January 2023 (UTC)

:: I added [[Template:Dual image]] with some of your suggestions. Agree that it's not super pretty, feel free to try something different.

::* I put the toggle in the caption mostly because I gave up on trying to make a more sophisticated replacement for the default thumb image behavior, I'm sure someone with better wiki-fu could put together something more intelligent.
::* I cut the text down to just "Toggle"; I think the best solution would be a small graphic showing the old and new dwarf icons with arrows between them. [[User:NiftyManiac|NiftyManiac]] ([[User talk:NiftyManiac|talk]]) 19:21, 2 January 2023 (UTC)

{{Dual image|
premium=File:DFwiki5by53by3farm.png|
classic=File:Quickstart_layout_3.png|
width=100px|
caption=A 5x5 room with a 3x3 farm plot
}}
::: I updated the layout, now it should look just like a regular image thumb. I didn't had time to test it, if it doesn't work for you or you don't like it just revert the last change. cheers. --[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 21:46, 2 January 2023 (UTC)
::::I don't know which part of this talk page to put this, but I added the ability to add icons to the v50 workshops template. Leaving the icon part blank will not break the template in any way. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 09:47, 3 January 2023 (UTC)
{{clear}}
==Creature List Now Supports Graphics!==
I wasn't easy, but I made new templates so the [[Creature]]s page now supports both graphics sprites ''and'' ASCII tiles. Allow me to show you:

{{v50_creaturecurrent_table_head}}
{{v50_creaturecurrent table row|graphic=[[File:dwarf_sprite.png]]|name=[[Dwarf]]|symbol=☺|color=3:0:0|playable=Fort, Adv|hostile=No|food=No|size=60,000|value=Not tameable|biome=[[Mountain halls]], [[Fortress|dwarf fortress]]es, [[hillock]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:elf_sprite.png]]|name=[[Elf]]|symbol=e|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=60,000|value=Not tameable|biome=[[Forest retreat]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:human_sprite.png]]|name=[[Human]]|symbol=U|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=70,000|value=Not tameable|biome=[[Town]]s and cities|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:goblin_sprite.png]]|name=[[Goblin]]|symbol=g|color=7:0:0|playable=Adv|hostile=Usually1|food=No|size=60,000|value=Not tameable|biome=[[Dark fortress]]es and [[dark pit]]s|note=Snatchers2}}
{{v50_creaturecurrent table row|graphic=[[File:kobold_sprite.png]]|name=[[Kobold]]|symbol=k|color=6:0:0|playable=Adv|hostile=Usually1|food=No|size=20,000|value=Not tameable|biome=Caves|note=Skulking race}}
|}

Oh wait, there's a bonus. You can also modify the background color of the box the sprites go in. I added that to make possibly-hard-to-see-otherwise sprites more easy to see - depending on the colors it has. Allow me to demonstrate.

{{v50_creaturecurrent_table_head}}
{{v50_creaturecurrent table row|graphic=[[File:dwarf_sprite.png]]|bgcolor=#829ccc|name=[[Dwarf]]|symbol=☺|color=3:0:0|playable=Fort, Adv|hostile=No|food=No|size=60,000|value=Not tameable|biome=[[Mountain halls]], [[Fortress|dwarf fortress]]es, [[hillock]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:elf_sprite.png]]|bgcolor=#c7dfc0|name=[[Elf]]|symbol=e|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=60,000|value=Not tameable|biome=[[Forest retreat]]s|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:human_sprite.png]]|bgcolor=#c7dfc0|name=[[Human]]|symbol=U|color=3:0:0|playable=Adv|hostile=Variable1|food=No|size=70,000|value=Not tameable|biome=[[Town]]s and cities|note=Trading race}}
{{v50_creaturecurrent table row|graphic=[[File:goblin_sprite.png]]|bgcolor=#dfc0c0|name=[[Goblin]]|symbol=g|color=7:0:0|playable=Adv|hostile=Usually1|food=No|size=60,000|value=Not tameable|biome=[[Dark fortress]]es and [[dark pit]]s|note=Snatchers2}}
{{v50_creaturecurrent table row|graphic=[[File:kobold_sprite.png]]|bgcolor=#dfc0c0|name=[[Kobold]]|symbol=k|color=6:0:0|playable=Adv|hostile=Usually1|food=No|size=20,000|value=Not tameable|biome=Caves|note=Skulking race}}
|}

To change the background color, add <code><nowiki>|bgcolor=COLOR</nowiki></code> segment after the <code><nowiki>|graphic</nowiki></code> part. You can use color names or HTML hex color codes. I added this to the v50 creatures page, but at this time, I only added the first five creatures I just displayed. It's gonna take a while to find ALL of those creature sprites. I hope a lot of people help out on that one. --[[User:Zippy|Zippy]] ([[User talk:Zippy|talk]]) 05:29, 5 January 2023 (UTC)

:Thanks, looks nice! —[[User:Lethosor|Lethosor]] ([[User talk:Lethosor|talk]]) 05:44, 5 January 2023 (UTC)
:Nice stuff, took the quick liberty to change the padding-left -> text-align to make all the sprites center aligned relative to each other :) Sweet work --[[User:Vallode|Vallode]] ([[User talk:Vallode|talk]]) 17:41, 5 January 2023 (UTC)
: Good work indeed. One minor issue, is that all the sprites have different sizes, which sometimes create slight variation in table row height. Consider using capping the image size vertically for example <code><nowiki>[[File:dwarf_sprite.png|</nowiki>'''x'''<nowiki>32px]]</nowiki></code>--[[User:Jan|Jan]] ([[User talk:Jan|talk]]) 18:15, 5 January 2023 (UTC)

Template:V50 creaturecurrent table row

2023-01-05T18:09:11Z

Jan: saves few vertical pixels, I believe it making the list look a little more homogenous

|-
|style="padding:0px; text-align: center; {{#if:{{{bgcolor|}}}|background:{{{bgcolor}}}}};"|{{{graphic}}}
|style="font-size:145%;font-weight: bold; font-family: 'Courier New', 'Quicktype Mono', 'Bitstream Vera Sans Mono', 'Lucida Console', 'Lucida Sans Typewriter', monospace; background: black;color:{{fgcolor|{{{color|0:0:0}}}}};text-align:center;"|{{{symbol|}}}
|{{{name|}}}
|{{{playable|}}}
|{{{hostile|}}}
|{{{food|}}}
|{{{size|}}}
|{{{value|}}}
|{{{biome|}}}
|{{{note|}}}

Template:V50 creaturecurrent table row

2023-01-05T18:05:57Z

Jan: to prevent invalid parameter passed if unused.

|-
|style="text-align: center; {{#if:{{{bgcolor|}}}|background:{{{bgcolor}}}}};"|{{{graphic}}}
|style="font-size:145%;font-weight: bold; font-family: 'Courier New', 'Quicktype Mono', 'Bitstream Vera Sans Mono', 'Lucida Console', 'Lucida Sans Typewriter', monospace; background: black;color:{{fgcolor|{{{color|0:0:0}}}}};text-align:center;"|{{{symbol|}}}
|{{{name|}}}
|{{{playable|}}}
|{{{hostile|}}}
|{{{food|}}}
|{{{size|}}}
|{{{value|}}}
|{{{biome|}}}
|{{{note|}}}

Trading

2023-01-05T17:47:18Z

Jan: more common syntax

{{migrated article}}
{{Quality|Unrated}}
{{av}}
{{buggy}}
[[File:Barter-Chickens for Subscription.jpg|thumb|300px|right|Bartering in the olden times.]]'''Trading''' in ''Dwarf Fortress'' first occurs in the first [[Calendar|autumn]] after establishing your fortress, with the arrival of the [[dwarf|dwarven]] [[caravan]]. Trading is a good way to acquire resources that aren't readily available in the local area. It also allows for more freedom in selecting starting gear and skills at [[embark]], since neglected items can be obtained through trade later.

'''Trader''' is the term used at your [[trade depot]] to refer to your fortress representative when dealing with merchants in a visiting caravan ({{key|r}} - "''Trader requested at Depot"''). As a [[profession]], the term applies to visiting merchants and dwarves whose highest [[skill]] is [[Appraiser]].

== Trade depot ==

{{Dual image
|premium=File:DFwikiGraphicalTradeDepot.png
|classic=File:DFwikiASCIITradeDepot.png
|width=100px
|caption=A Trade Depot
}}

{{Main|Trade depot}}
Building a [[trade depot]] is a prerequisite for trade with caravans that arrive at your fortress. While it may be convenient to build a depot outside at first, it is usually a good idea to move it inside, or secure it with [[wall]]s, [[bridge]]s and other fortifications, to protect incoming caravans and your goods from [[steals drink|thirsty animals]], [[thief|thieves]] and [[goblin]]s.

Everything that is on your map belongs to you, except:
* the items that are on merchants' animals and wagons
* the items that are in the trade depot (they belong to the caravan until they are moved out of it)
* items worn by non-fortress units (initially forbidden, but can be claimed via unforbidding and dumping them)

==Trading flowchart ==
{{:Trading/Flowchart}}

{{Clear}}

== Trading ==
[[File:Trading with the Elves.PNG|thumb|Trading screen]]

Before you can begin trading, you need to designate what goods to trade and have the fortress's representative trader at the [[trade depot]]. Select the trade depot with {{K|q}} and then {{k|r}}equest the trader. Be sure that {{k|b}} reads "Only broker may trade" if you want your [[broker]] to represent your fortress. If it reads "Anyone can trade", a random, probably unskilled dwarf will volunteer to conduct the trade. Pressing {{k|b}} will toggle this setting. Then select the trade depot again and press {{k|g}} for Move Goods, you will be presented with a list of all items in your fortress that belong to you. Mark the goods you want to sell --insert clever advice--, and your dwarves will begin moving them to the depot.

Once the trade goods are moved to the depot and your trader has arrived, select the depot again with {{k|q}} and enter the {{k|t}}rade menu. In the trade menu select the items to offer from the right and the desired items from the left. All caravans have a weight limit which cannot be exceeded, and the allowed additional weight is displayed in the lower right corner. If your broker (specifically, not necessarily your trader) has at least Novice or better [[Appraisal]] skill, the value of all items will be displayed. Once the proposal is ready, press {{K|t}} to propose the trade, but merchants will not agree unless they make adequate profit. Be sure to use '''trade''', not '''offer''' {{K|o}}, as this will make a gift of the selected items. The amount of acceptable profit is determined by the trader's [[Broker skills|skills]] and the merchant's mood, described below. Merchants may attempt to propose counteroffers if they do not accept the proposal, which can then be accepted, rejected, or further amended by the trader.

With more experienced traders and pleased merchants, even marginally profitable trades can be successful, and counterproposals can be rejected safely, offering the same trade again. Note however that a low profit margin for the traders may not be desirable - it has been suggested that both export and profit numbers influence the size of next year's caravan and, in the case of the dwarven caravan, immigration numbers.{{Verify}}

Note: Goods brought by caravans rarely have base quality higher than superior, and decorations on a good rarely exceed superior as well.

Note if you give or trade away an artifact, you will receive a special screen:
[[File:Treasure_Gift.PNG|750px]]
[[File:Treasure_Trade.PNG|750px]]

=== Items cue colors ===
{| class="wikitable"
! {{DFtext|Brown|6:0}}
| Items have been created (or modified) by your fortress. They can be traded away or offered as a gift.
|-
! {{DFtext|Gray|7:0}}
| Items were created by another source. They can be traded, but if one of these items has been selected, the entire selection cannot be offered as a gift.
|-
! {{DFtext|Purple|5:0}}
| Items are under a no-export mandate. If they are traded away it will result in disciplinary action (see [[justice]]) against the dwarf that brought the item to the depot.
|-
! {{DFtext|Green|2:0}}
| Items have just been gifted to the caravan and they will not trade it back.
|-
! {{DFtext|Red|4:0}}
| Items have been seized from another caravan and cannot be traded as is; you will need to decorate them or turn them into other items for them to become "valid" trading items.
|}

Note that containers (barrels, bins, etc.) will be displayed according to the origin of the ''container'', not the contents. So a foreign barrel holding locally-produced beer will display as foreign (white). Once you {{k|v}}iew the container, the locally-made contents are displayed as local (brown).

=== Seizing items ===

Pressing {{K|s}} from the trade menu will seize the selected items of the merchant's. If you seize goods from a caravan, the merchant will respond "Take what you want. I can't stop you." and then leave immediately without the seized goods. Items cannot be seized from the dwarven caravan, and other races will not buy goods stolen from one of their caravans (then marked in red) unless they are tricked into asking for them via counteroffer, or the items are "laundered" by decoration or used to create other goods. Seizing goods will hurt diplomatic relations, but is not grounds for an automatic [[siege]].

Pressing the seize button while no goods are selected will result in the merchant interpreting your seizure as a joke. This apparently does nothing to benefit or hinder your trading.

As a side note, if you deconstruct your trade depot with a caravan in it, all the caravan's items will drop to the ground, to be readily hauled away by your dwarves. This does not mark the items as stolen, and the caravan will leave. However, ''next'' year's caravan is partly based on the profits from the previous year - so if you are relying on that race's caravans for needed items, you're hurting yourself in the long run.

Trying to interrogate a merchant can also cause a wagon to fall apart.

Another way to steal without marking as stolen is to forbid the trade depot just before they leave, causing them to leave their goods at the depot.

If you're using the search plugin for [[Utility:DFHack|DFHack]] (e.g. from the [[Utility:Lazy Newb Pack|Lazy Newb Pack]]), be warned that {{K|s}} means "seize" and '''NOT''' "search", and there is '''no warning''' for it. Use {{K|q}} to search the merchant's goods and {{K|w}} to search yours.

Note that the civilization attached to a particular caravan will keep track of the value of items the caravan was carrying when they set out to trade, and they will compare this value with the value of items they return home with. Regardless of what method you use to confiscate items from a caravan, even if you came to possess the goods through no fault of your own (an [[ambush]] killed the traders and guards, for example) the parent civilization may decide that you stole from them and send a [[siege]] instead of a caravan the following year. It is prudent to take measures to protect caravans visiting your lands!

===Offering items===

{{key|o}} You can also give away items, as gifts to the leaders of the [[civilization]] you are trading with. This presumably helps relations between yourself and the other faction, though there is not yet a clear correlation between the value of the offerings and the improvement to relations. The exact effects of offerings on trading are unknown but it is believed due to the offerings' net trade value being counted towards the merchants' profit, possibly with a modifier (possibly a multiplier of more than 1 as a bonus or less than 1 to compensate for the improved relations){{Verify}}, which in turn increases the quantity and variety of trade goods brought by next year's caravan. Also the [[Monarch]] requires offerings to be made before their arrival. You cannot offer items that were not made at your fortress; the merchants do not want your spare [[Goblinite]] clothes.

The value of an offering for the purpose of becoming the capital is adjusted by your current export agreement.

Unless you are looking for [[fun]], under no conditions should you offer or trade items which are wooden or used wood in their creation (clear glass, for example) to [[elves]], as this will insult the traders, and may cause them to leave or even damage relations enough to provoke a war between you and the elven civilization you traded with. They will accept their own "grown wood" items in trade without insult, however.

== Miscellaneous trading advice ==
* Thieves and thieving critters tend to follow caravans. Expect assaults and intruders.
* Create your trading depot inside your fort, preferably in the beginning. Place a 3-tile wide path (which must be free of obstructions such as stairways, traps, minecart tracks and boulders) to the entrance of the fort and position war-trained animals along it (chains do not block wagons); this will help to protect the traders and keep the depot close to your supplies.
* Avoid having multiple wagon paths to your depot. Caravan [[wagon]]s cannot move through each other, and if two wagons happen to meet at a fork they may become gridlocked against each other, resulting in the destruction of wagons and loss of trade opportunities.
* All caravans will bring extra food (meat and edible plants), wooden logs, and cloth/leather (for making clothes) if the supplies of your fortress are low enough, independent of whether or not you requested them. This does not apply in the case that the weight limit is exceeded by (other) items you requested. The supply situation, as observed by traders, is based solely on the number of unforbidden items in your fortress, stockpiled or not; thus, it is possible to trick caravans into thinking your supplies are low by [[forbid]]ding all of your relevant stocks immediately prior to their arrival.
**In order to '''avoid''' this behavior, you should make sure that, for each dwarf in your fortress, you have the following ''unforbidden'' items:
*** 5 pieces of food - meat, fish, plants, or "other" in your [[Status]] screen (even though "other" includes inedible items)
*** 1 wood log
*** 5 pieces of cloth, pieces of leather, or complete sets of [[wear|pristine]] clothing (shirt+pants+shoe)
* Define your trade depot as a burrow. When traders arrive, you can add your broker or another dwarf, perhaps one you want to train in trading, to the burrow. They will head to the depot immediately, and stay there until you remove them from the burrow.
* Each trade you make (regardless of value) will increase your trader's skills by 50, distributed among Comedian, Judge of Intent, Negotiator, and Persuader. Each skill seems to gain around 5-15 experience points, but the sum will always be 50. The skill gain occurs as soon as the "t" button is pressed - if the offer is rejected, the dwarf will still gain 50 points. If the same offer is subsequently accepted, no additional skill will be gained.
* Selecting "only broker may trade" ensures that you will start negotiations with a decently-skilled trader, but also requires a significant wait while your broker makes his way to the depot. Selecting "anyone can trade" will result in a poorly-trained trader arriving immediately. Once your fortress is producing enough goods to buy out the caravan, waiting for your broker is unnecessary; allowing your commoners to trade spreads out the trading skill gains and eliminates the micromanagement of trying to get your broker to the depot in a timely manner.
* If your trade depot has no values for the worth of items, then ensuring that a dwarf with the Appraiser skill is assigned as the trader will cause the values to appear.

== Types of Merchant Caravans==
By default, each friendly civilization will send one merchant [[caravan]] per year, linked to one season, which is spring for elves, summer for humans, and autumn for dwarves - no race trades in winter by default. Merchants from different races has different trading preferences.

If your fortress was founded in spring, it is highly unlikely that you will receive an elven caravan that spring, and it is uncommon for a human caravan your first summer, so probably your first and only caravan your first year will be the dwarven one. Caravans will only show up if that race considers the fortress site accessible (as denoted on the embark screen) and "worth the effort" (as determined by the [[Entity_token#PROGRESS_TRIGGER_POPULATION|[PROGRESS_TRIGGER_*]]] tokens in the entity definition), with the exception of dwarves, who always arrive unless they are [[extinct]].

=== Dwarven ===
: ''"Greetings from the mountainhome. Your efforts are legend there. Let us trade!"''
:: (Or, if your fort ''is'' the [[Fortress|mountainhome]]...)
: ''"Greetings from the outer lands. Your efforts are legend there. Let us trade!"''

Typically, the first caravan you receive is the [[Dwarves|dwarven]] one from your home civilization, giving you at least 22 weeks to prepare (assuming you started mid-spring, the default). This does require that you are on the same continent as they are, and you are not isolated by mountains or bodies of water.

The dwarven caravan:
* arrives in [[Calendar|autumn]].
* carries metal bars, [[leather]], weapons and armor, food and booze, and more. Dwarves alone may bring [[steel]] and steel goods.
:* If the trading civilization does not have access to [[iron]], they can still bring steel (and steel goods) and [[pig iron]] bars, but will not bring iron products.
* usually carries a selection of books that your civilization has access to. This can include books written in previous forts of yours within the same civilization.
* is heavily guarded.

The dwarven caravan from your home civilization:
* sends a liaison who will speak with the [[Expedition leader]], [[Mayor]], [[Baron]], [[Count]], or [[Duke]] to negotiate an import-export agreement (unless the [[Monarch]] is present).
* influences the number of immigrants received (if the caravan leaves intact).
* will not cause sieges when repeatedly destroyed or lost.
* is the only caravan to arrive during a fortress' first year.
* always arrives, regardless of embark location, unless the dwarven civilization is [[extinct]].
* cannot have its goods seized from the trade menu.
* may not arrive if your civilization lacks any notable figures.
* cannot be offered goods if the monarch is present.

=== Elven ===
[[Image:Evil_elves.png|thumb|400px|A typical elven caravan.]]
:''"Greetings. We are enchanted by your more ethical works. We've come to trade."''

Assuming you do have friendly contact with [[elf|elves]], their first caravan will arrive sometime in spring, giving you about a full year before they arrive.

The elven caravan:
* arrives in the [[Calendar|spring]].
* does not use [[wagon]]s, only [[Creature#Domestic animals|pack animals]]
* carries [[cloth]], [[rope]]s, various above-ground seeds, [[plant]]s and their byproducts, [[log]]s, [[wood]]en goods & [[weapon]]s, clothing and [[armor]], and may carry tame exotic [[creature]]s.
* is unguarded.
* does not accept some items in trade: Elven merchants do not like to be offered any "tree" byproducts, including wood and charcoal products, unless they are "grown", which only elves can produce (see list below).

Because they do not utilize wagons, elven caravans have a much smaller weight limit than dwarven and human ones, making trading heavy items like furniture problematic. Because of this and that they tend to offer only items made of (living) wood*, the total value of what they offer tends to be considerably less than other caravans, meaning your fortress doesn't have to bring nearly as much to trade to get everything that it might find useful.

: (* Wooden items offered by the elves have been "grown" as that item, so, somehow, that makes it acceptable to them. See next section.)

"No wagons" also means that the entire caravan will use the most direct 1-tile-wide path to your Trade Depot, which could be a good or bad thing, depending on that path and your plans for this caravan.

==== Unacceptable items ====
Elves view living trees as [[Elf#Ethics|sacred]] - or some crap like that. Offering or attempting to trade items that required the killing of a tree will greatly offend the merchant, causing their mood to drop rapidly. They will refuse to trade any more that season and leave immediately. Additionally, you will be called "uncouth", "crude", and "barbaric" for not understanding their customs.

: ''"Once a beautiful tree, and now? It is a rude bauble, fit only for your kind."''

Unacceptable items (as offered by dwarves) include:
:* [[Wood]]en items (including all subterranean mushrooms/fungus/etc. such as [[tower-cap]]s)
:* Items derived from wood - [[ash]] and [[charcoal]], as well as [[lye]], [[potash]], and [[pearlash]]
:* Items made from clear and crystal [[glass]] (due to the [[pearlash]] used); basic green glass is perfectly acceptable
:* Items «[[decoration|decorated]]» with any of the above materials
:* [[Obsidian]] shortswords (since they have wooden handles)
:* Any of the above, regardless of who made them (i.e. from earlier trades, or captured gear from fallen enemies)
:* Tallow [[Soap]] (made with [[lye]]), but not Plant Soap{{bug|8571}}

:"''I see your low race still revels in death. That poor, gentle creature...''"

Elven traders also do not like to be offered any animal byproducts:
* Items made of (or [[decoration|decorated]] with) [[leather]], [[wool]], [[hair]], [[bone]], [[shell]], [[horn]], or [[ivory]].
* [[Soap]], [[fat]]/[[tallow]], [[meat]], [[fish]] (raw or prepared), or any related creature remains (which have no trade value anyways)
* Prepared meals containing any of the above items

However, [[stone]] and [[metal]] items, even when [[charcoal]] is used in production, are acceptable (since the elves are unfamiliar with metalworking, and do not know that charcoal is used to make metal items). Items made from [[silk]] are acceptable, as are all non-wooden plant-derived products such as [[cloth]] and [[thread]]. You can also transport your goods to the [[trade depot]] in a wooden [[bin]], as long as you do not try to sell the bin. Living animals are acceptable, as long as the [[cage]] or [[trap]] is not made of [[wood]].

Be especially careful with reselling decorated items from other caravans, as non-wood/glass items may have decorations of wood or clear/crystal glass. Note that "grown" wooden items from elven caravans ''can'' be resold to them, as the elves know that they were made in an elf-kosher way.

=== Human ===
:''"Greetings. The craftsdwarfship of the dwarves is unparalleled. Let's make a deal!"''

Assuming you do have friendly contact with [[human]]s, their first caravan will arrive sometime in summer, giving you well over a full year before they arrive.

The human caravan:
* arrives in [[Calendar|summer]].
:* Usually your first caravan opportunity
* carries metal bars, sand, [[leather]], cloth, wood, food and booze, books, ropes, waterskins, quivers, backpacks, metal weapons and clothing and armor, cages and a few domestic animals.
* carries only large-sized clothing and armor, which is unusable by dwarves.
* is moderately guarded.
* sends a chief treasurer to negotiate import/export agreements

==== Good Humor ====
Choosing to seize goods from a human caravan without marking anything to be taken is treated as a joke, which will raise the visiting trader's mood. This can only be done once each year.

=== Goblins and Kobolds ===
{{mod}}
{{main|modding#trade}}

A [[goblin]] caravan will only arrive if you mod the game, primarily because their entity lacks the [[entity token]]s needed to make use of pack animals and wagons. That, and that the token {{token|BABYSNATCHER|e}} makes them hostile to all non-goblin civilizations. The same caveats apply to [[kobold]]s (whose {{token|UTTERANCES|c}} and {{token|ITEM_THIEF|e}} tags, similarly, make them hostile to every civilization).

The goblin caravan:
*will arrive every season, four times per year
*is unguarded
*brings mostly food and cloth
*does not send a liaison or a guild representative
*does not make import/export agreements

== Merchant mood ==
{{Verify|Are we sure that this section is correct?}}
If your trader has Novice or better [[Judge of intent]] skill, there will be a line added below the merchant's dialogue describing the caravan's attitude. Their attitude rises with successful trades (especially if they get lots of profit) and falls when you propose deals they don't like. You can never make a deal that's at a loss for the merchant, even if they are at the highest possible mood.

* {{DFtext|(trader) seems ecstatic with the trading.|2:1}}
* {{DFtext|(trader) seems very happy about the trading.|3:1}}
* {{DFtext|(trader) seems pleased with the trading.|1:1}}
* {{DFtext|(trader) seems willing to trade.|7:1}}
* {{DFtext|(trader) seems to be rapidly losing patience.|6:1}}
* {{DFtext|(trader) is not going to take much more of this.|4:1}}
* {{DFtext|(trader) is unwilling to trade.|5:1}}

The happier you make a merchant, the less profit margin they will demand in a trade. Dwarven merchants start off wanting about 100% profit, maybe a little more. If you repeatedly offer less than what they expect, that will "lower" their mood. If, on the other hand, you meet or exceed their expectation, that will, over several trades, improve their mood. If merchants reach the lowest level, no further trade will be possible, and they will immediately pack up and leave your depot. Since annoyed merchants are more likely to reject deals, you should be generous in initial negotiations. Skilled negotiators seem less likely to offend merchants with unsuccessful deals.

An easy way to capitalize on this mood system is to perform several partial trades. First trade for a few items, offering goods twice the value of the items you ask for (e.g. offer 2000☼ for 1000☼ of his stuff). This will likely make the merchant ecstatic about trading with you. Perform the next trades more aggressively, working them down to about a 30% profit. With the merchant in such a good mood, they are more likely to counteroffer than reject a trade outright. If you don't like the counter-offer, try to split the difference, or just back out of the trade and start again.

== Trade Agreements and Liaisons ==
[[Outpost liaison]]s (from your own civilization) and foreign Merchant Nobles (if added with the [[Position token#TRADE|TRADE responsibility]]) will arrive with the caravan to speak to your [[noble]] dwarves (and they ''will'' speak to those dwarves, even if they have to wait at their bedside in the hospital for months after the caravan has left), appearing on the map edge at the same time as the caravan (though in a different location). Meeting with them allows you to request specific items for the next caravan to bring (at a premium price) or take requests for production for the next caravan (for which the merchants will pay a premium).

Current [[Trade agreement|trade agreements]] can be viewed through the Civilization menu ({{k|c}}). These trade agreements are cleared when a liaison of the corresponding civilization enters the screen, so they are generally not accessible after the caravan has arrived.

In the event that your leader is replaced, killed, or taken by a [[strange mood]], the liaison may decide to leave your fortress [[stymied|"unhappy"]].{{bug|576}} Curiously, this will '''not''' occur if your leader is otherwise unable to perform the "conduct meeting" task. You can currently lock a liaison in a room and they will wait years to attend the meeting your noble is constantly conducting (and all subsequent diplomats appear to wait in line for the first to finish); this behavior is presumably a bug.{{bug|8947}}

Whether having successfully met with your leader or given up, a liaison who has decided to leave but is prevented from reaching the map edge will eventually go [[insane]].

== Bugs ==

*Aggressive, untrainable creatures (captured goblins, for example) cannot be traded; when a dwarf attempts to move the caged animal to the Depot, the creature is set free.
*When merchants leave with an animal, the merchants seem to be dragging their beast of burden instead of leading it. If the animal is incapacitated but not dead, the merchant will continue to walk at the same speed, dragging the unconscious beast.
*If a merchant's chosen map edge exit is guarded by a hostile creature (including those on a [[restraint]]), the merchant will wander back and forth repeatedly and eventually go insane rather than path to an alternate exit.
* Animals bought from merchants don't always become available for use.{{bug|10162}}

== Loyalty cascade ==
{{main|Faction#Loyalty cascade|l1=Faction}}
If you order your military to kill merchants from your own civilization, a bizarre result of the way loyalty is handled makes the members of your military who attacked the traders become enemies of your civilization, but remain members of your fort's government (dwarves of this [[faction]] are referred to as ''separatists''). As enemies, they attack your other dwarves (''citizens''), but as members of the fort, they still follow orders. Allowing citizen militia dwarves to attack the separatists will give them opposite loyalties of the separatists, (i.e. loyal to civ, not to fort), or ''loyalists'', who do '''not''' follow orders. And then, if a separatist or loyalist kill a citizen, they become enemies of the civ '''and''' fort, making them ''Renegades'', who are essentially complete enemies of the citizens.

To prevent the cascade from spreading, order the original separatists away from the fortress and let them fight amongst themselves. If the results are renegades, it is okay to allow other dwarves to kill them (by stationing them nearby). If the results are separatists/loyalists, then you will need to separate them, somehow.

== Exploits ==
*Deconstructing the Depot will cause merchants to leave your fortress and abandon any goods in the Depot because items are not available until the building is fully deconstructed. However any animals they had caged will still belong to the merchants and only become friendly, you won't actually own them. According to Toady One, this is actually working as intended, and is not really an exploit or bug: "...the reckoning comes when they return with lesser value, and it has the same negative effect (it'll be listed as a disaster rather than an intentional seizing -- the depot could be destroyed, for instance -- but it counts for the same value if I remember). The overall wording could be changed and the interaction could be deepened to recognize this or that, but it's working as intended."[https://dwarffortress.mantishub.io/view.php?id=293#c8393]
*If you wait until the merchants leave the map, you can "claim" caged animals by linking a lever to the cage and opening it, the animals will be released in a tamed state. Check the {{k|u}}nit screen before releasing them; if the creatures still show as Merchant creatures, they will wander off the map when released; if they show as Tame creatures, they will stay once released.
*If you lock them in your fortress for a minute or two (real time), the merchants '''may''' drop items and leave behind pack animals (both of which are yours for the taking!) Note: Results are not consistent.
* If [[Caravan#Destruction|spooked or attacked]] the merchants' caravan could leave their stuff behind as they attempt to flee the map, leaving the items free for the taking.

[[File:Bullock_Team_Wool_Wagon.jpg|thumb|400px|center|An old trading wagon from the 1880's.]]

== World level Trade ==
During world generation, trade is established between sites. This probably determines growth.

{{Translation| dwarven = nish | elvish = lathì | goblin = otsmor | human = batow}}

{{Category|Trade| }}
[[ru:Trading]][[zh:Trading]]

Quickstart guide

2023-01-05T17:47:13Z

Jan: more common syntax

{{Quality|Unrated}}
{{av}}
{{old}}
:''For installation instructions, see [[Installation]].''
:''This is a quickstart guide for [[dwarf fortress mode]] for those who have never played before and quickly want to jump in head-first.'' ''If you are looking to learn adventure mode instead, see the [[Adventure mode quick start]] guide.''
:''Also see [[Tutorials]] for more detailed tutorials that people have submitted.''
{{TipBox2|float=right|Before you get started...|Always remember that '''losing is [[fun]]!''' Be prepared to lose a few fortresses before you get all the way through this guide – it can be easy to accidentally kill the entire fortress while learning. But remember: losing means that next time, ''[[#Situational Awareness|you'll remember how you lost]].'' In a big way, ''Dwarf Fortress'' uses the principle of learning from one's mistakes.}}

So, you want to play '''Dwarf Fortress''', but you have no idea what to do. That's understandable; in ''Dwarf Fortress'' you can really do anything you like. It is a huge, complex, and totally open-ended game. But in order to do anything, first you need a sustainable fortress. It turns out that this is not as hard as you might think.

[[File:FlowchartDF.png|thumb|446px|right|[[Main:From Caravan to Happy Dwarves|From Caravan to Happy Dwarves]] - This is a flowchart showing approximately what sequence of actions players usually take when starting up a new fort. Feel free to ignore it if you want. It's not necessary to refer to this to understand the rest of the guide, but by the time you finish the guide it will probably all make sense.]]

__TOC__

= Common UI Concepts =
{{old}}

{{TipBox2|float=right|titlebg=#0a0|Keeping Up|While the guide contains many links, you may still need to look something up. Refer to the [[Dwarf fortress mode|Fortress Mode Reference Guide]] or use the wiki [[Special:Search|search]] function. Also, don't hesitate to [[Main:Troubleshooting|ask for help]] if you can't find answers on the wiki.}}

This is just the Quickstart Guide, so we skip lots of details on the UI. If you're looking for more UI help as you get deeper into your first fortress, you may also want to read this section in the [[Dwarf_fortress_mode#Gameplay_user_interface|Fortress Mode Guide]].
{{KeyConventions}}

== Options menu ==
{{main|Dwarf_fortress_mode#Options_screen|l1=Options screen}}

Most basic game-related tasks (saving, keybindings, sound, etc.) are performed through the options menu, which can be reached with {{k|Esc}} from the main screen.

To save and quit back to the main menu, select {{DFtext|Save and return to title menu}}.
{{tc|#d00|Unless you know what you are doing, do not select either}} {{DFtext|Retire the Fortress (for the time being)}} or {{DFtext|Abandon the Fortress to Ruin}}! These will essentially cause you to lose your save.

=World Generation=
First, [[World generation|generate a new world]]. ''Dwarf Fortress'' worlds are always procedurally randomly generated - there is no "default" or "standard" world. Luckily, the basic version of this process is simple, and with these suggested settings won't take too long. Wait until the game shows that the world has been generated, since stopping history too soon can limit material availability for embark and trade.

{{TipBox2|titlebg=#00a|Starting World|
For your first game, [[World generation|generate a new world]] using the {{DFtext|Create new world}} option in the main menu with the following options:

* {{DFtext|World size}} is {{DFtext|Medium|3:1}}

* {{DFtext|History length}} is {{DFtext|100 years|3:1}}

* {{DFtext|Number of Civilizations}} is {{DFtext|Medium|3:1}}

* {{DFtext|Number of Sites}} is {{DFtext|Medium|3:1}}

* {{DFtext|Number of Beasts}} is {{DFtext|Low|3:1}}

* {{DFtext|Natural Savagery}} is {{DFtext|Very Low|3:1}}

* {{DFtext|Mineral Occurrence}} is {{DFtext|Everywhere|3:1}}
}}

= Embark =
{{migrated section}}
{{main|Embark}}

Embarking is the process of choosing a site, outfitting your initial dwarves, and sending them on their way.

After generating a world, select {{DFtext|Play now}} then choose fortress mode. The game will load and update the world, then show the world map.

Mouse over the map to inspect it. Left-click to zoom in, where you can then click the {{DFtext|Embark}} button in the bottom right corner to choose an embark site.

== Choosing a Good Site ==

Choosing a good embark site is crucial for beginners. Highly skilled players can run a fortress on an evil glacier, but for now, stick to friendly environments. Look for features in an embark site that will make your first fort easier to manage.

{{ambox
|type=type
|text=The world tooltip will only show features from the moused-over tile, but since the embark area covers multiple tiles it can contain '''multiple biomes'''. It is '''very important''' to inspect all tiles in your site. Each may have significantly different features such as an aquifer or evil biome '''not initially shown''' in the info due to not being under the cursor.
}}

{{TipBox2|titlebg=#00a|Starting Site|
[[File:DFwikiStartingSiteExample.png|thumb|350px|An example of a good starting location, note details in the top-right corner]]
For your first game, find a site with the following properties:
*'''NO [[Aquifer]]''' (or at least no '''heavy''' or '''varied''' aquifers. Light is interesting on later embarks, but heavy guarantees '''[[Fun]]'''!)
*'''Trees:''' Woodland or Heavily Forested (or, at the very least, sparsely forested)
*'''Surroundings:''' Serene, calm, or at least '''not''' any evil or savage biome.
*A '''River'''
The following are also good to have, but focus on getting a decent site, not a perfect one.
*'''[[Climate|Temperature]]:''' Warm or Temperate
*'''Clay or Soil''' makes farming easier when starting out
*'''Flux stone layer''' For your steel industry
*Also avoid sites containing '''towers''', '''goblins''', or other groups at war with you.
See '''[[/Starting site/]]''' for more info on why these characteristics are important.}}

[[File:Quickstart-finder.png|thumb|right|Initial finder criteria]]
While finding a site is not as simple as world generation, the {{DFtext|Find embark location}} button at the bottom of the screen can help.
[[File:Quickstart-finder-partial.png|thumb|right|Finder partial match missing Good surroundings]]

Once the find tool has finished searching with matches found, press {{K|Esc}} to look at the results. Any region in which it found a match will be indicated by a green {{DFtext|X|2:1}} on the map. Any embark sites matching the criteria will be shown by a rectangle of yellow {{DFtext|X|6:1}}s on the zoomed-in map.

Additionally, when placing the embark area you can resize it using the buttons on-screen. A 4x4 embark (the default) is usually reasonable, but you may want to change the size to avoid an undesirable biome or match your finder criteria.

If you are unable to find a site that you are willing to embark on, you could always create a new world. Otherwise, move on to the next step.

== Skills and Equipment ==
{{TipBox2|float=right|titlebg=#0a0|Optional: Preparing Carefully|If, at this point, you'd like to get into all of the details of picking individual skills and equipment for your expedition, select {{DFtext|Prepare for the journey carefully}} and see '''[[Quickstart_guide/Preparing_carefully|Preparing carefully]]''' for instructions. '''This is completely optional'''.
And preparing carefully makes little difference in the long run, especially without experience as to what to change.}}
Now the '''Prepare for the Journey''' screen should appear. You will be given the choice to either:
*{{DFtext|Play Now!}}
*{{DFtext|Prepare for the journey carefully}}.
In addition, settings are also displayed on the right-hand side.
Turn enemies to {{DFtext|Off}}. Selecting {{DFtext|Play Now!}} will start you out with a default set of equipment that is reasonably safe, allowing you to skip having to set up your skills and equipment. If you'd like to get going now, just select that option.
{{clear}}

=A Minimal Fortress=
[[File:DFwikiGettingYourBearingsExample.png|thumb|right|Starting out. In this example, the dwarves will be digging out an entrance tunnel in the cliff on the right.]]

At this point, you have embarked, and your dwarves have arrived at their destination. You will see your dwarves clustered around their wagonful of supplies, somewhere near the center of your map. '''Immediately hit {{K|Space}} to pause the game''' unless it is already paused.

==Getting your bearings==
'''Do not unpause the game just yet.''' Take a look around with {{k|w}}{{k|a}}{{k|s}}{{k|d}}. Look up and down a few [[z-level]]s with the scroll wheel. Place the cursor on various tiles to familiarize yourself with what the symbols mean. If you get lost, you can press {{K|F1}} (or {{k-|Fn|F1}} on some systems) to return to the wagon. (You can define more [[hotkeys]] later, to jump quickly to other sites of interest.) Notice the terrain features, the vegetation, and any minerals visible. If you chose a site with flowing water, where is it? What about pools of water? The more carefully you examine your site before breaking ground, the better off you will be.

In the bottom left, click the citizens information button to see a list of your dwarves. In the {{DFtext|Others}} tab, you can see any wild animals that may be nearby.

The {{DFtext|Stocks}} button at the top of the screen will show the items owned by your fortress.

On the left, there are buttons for various message logs.

Your wagon serves as the initial meeting area for your dwarves. Since you should have started in a non-freezing, calm (low savagery), non-evil biome, you shouldn't face any immediate danger, but if for some reason the area around your wagon proves to be unsafe, immediately designate another meeting zone (see [[#Temporary Meeting Area|Temporary Meeting Area]] below).

==Controlling Your Dwarves==
The first thing to keep in mind is that, for the most part, you can't directly control your dwarves the way you control characters in a typical fantasy RPG. Instead, you '''designate''' things that need to be done and then dwarves with the appropriate labor assignments will decide what to do.

Some tasks receive a higher priority. For example, if a dwarf needs to eat, then he will go eat, and only get around to digging a tunnel once he is done eating. It is also possible to designate things that no dwarf is able to do. For example, if you designate an area to mine, but no dwarf has mining as one of his allowed labors, or no dwarf has a [[pick]], then the mining will never get done, and the game will not always advise you of why.

So, what you are doing throughout the game is essentially giving your dwarves a detailed group-wide to-do list, but it's up to them to figure out which one of them will execute any given task if the task is even possible. Often many of the details of how a task is performed (such as exactly which rock will be used to make crafts) are left up to them.

===Labor and work details===
{{TipBox2|float=right|titlebg=#aa0|Utilities|2=
You may have noticed that the UI for managing dwarves is a bit difficult to use. There are a few utilities available for this purpose (for Windows, Mac OS X, and most Linux systems):
* '''[[Utilities#Dwarf_Therapist|Dwarf Therapist]]''' (not yet supported for v50) can make labor management considerably easier, especially when you're dealing with twenty times the number of dwarves you have now. It can group and sort dwarves by multiple attributes and display their preferences, mood, and more.
* '''[[Utility:DFHack|DFHack]]''' (not yet supported for v50) includes "Dwarf Manipulator", a UI for managing labors. It has fewer features than Dwarf Therapist, but displays much of the same information and is adequate for normal use. In addition, it is accessible from within DF via {{k-|u|l}}, eliminating the need to constantly switch between applications.
}}
{{Main|Labor}}

'''Labors''' are how you control what types of tasks a dwarf is allowed do. When dwarves are idle, it could be because you haven't given them anything to do, or it could be because none of the idle dwarves have been told that they're allowed to do the types of tasks you've designated. For example, if you designate an area to mine, but none of the dwarves have the mining labor enabled, they will all just sit around ignoring your mining designation, thinking that it isn't their job.

Labors are assigned to dwarves in groups called '''work details'''. Open the labor menu from the bottom left to see all the default work details and their assignments.

Fortunately, you don't need to assign a dwarf for every single labor in the game; work details can be set to "everybody does this" to allow any idle dwarf to pick up the job.

'''While you're here''', set the Hunters and Fisherdwarves work details to "nobody does this." Dwarves with these details enabled will constantly be outside attempting to perform them, and for now you don't want dwarves wandering around alone where they can get killed (in addition, they won't be doing anything useful, like hauling).

Also, the default embark comes with three pickaxes: so for efficiency, make sure two dwarves have the Miners detail enabled.

As dwarves perform jobs, they gain skill in those areas which leads to them working faster or producing higher-quality things. Note that ''any'' unskilled dwarf can perform any labor given the necessary equipment and materials; they'll just be worse at it.

The default work details contain all the essential labors for the very start of your fortress, but this guide will involve other labors. Keep in mind that at some point you'll have to assign the following labors by creating custom work details:

{| class="wikitable"
! Category
! Labor
|-
| Farming/Related || Wood Burning
|-
| Metalsmithing || Furnace Operating
|-
| Metalsmithing || Armoring
|-
| Metalsmithing || Weaponsmithing
|-
| Metalsmithing || Blacksmithing
|-
| Metalsmithing || Metalcrafting
|-
| Jewelry || Gem Cutting
|}

==Strike The Earth!==
{{TipBox2|titlebg=green|float=right|Getting your dwarves to safety|
As you now know, you can't control your dwarves directly. So how do you tell them to get inside your newly dug rooms?
*[[Activity_zone#Meeting_area|Meeting Area]] You can designate a Meeting Area zone inside the new rooms. Press {{k|z}} and click "Meeting Area". Draw a rectangle to create a meeting area, then click "Accept". ''See also the [[zone]] page for more information.''
*[[Stockpiles]] (see [[Quickstart_guide#Stockpiles|below]]) Stockpiles tell your dwarves where to put things. Create a stockpile for everything, and dwarves will start to haul all your items there.}}
Decide where you will build your main entrance. Generally, you will want to get all your dwarves and supplies inside a protected area as quickly as possible. The best strategy is to put the entrance near your wagon to speed up the process of hauling all of your supplies inside.

The digging orders menu allows you to select areas to dig. Click the pick axe at the bottom or press {{K|m}}. There are multiple methods of digging:
* '''[[Mining]]''' ({{K|m}}) removes solid, floor-to-ceiling terrain (natural 'walls') on the z-level selected, leaving behind a rock or soil surface (also referred to as a natural floor). This does '''not''' do anything in areas without natural walls (for example, the surface or previously-mined areas).
* '''[[Channel]]ing''' ({{K|m}}-{{K|u}}) removes ''natural'' (rock/soil) floors (either created naturally or by mining) and creates a ramp (▲) on the z-level below. Note that you will see a down arrow (▼) on the current z-level, indicating a ramp on the level below. (For best results, ensure that the area below is unrevealed, i.e. black).

To designate an area for digging:
#Hit {{K|m}} to bring up the digging orders menu.
#Hit {{K|m}} to mine or {{k|u}} to channel (see above)
#Draw a rectangular are you want to dig out.
#A rectangle will be highlighted and a miner will start to dig out this area once you unpause the game with {{K|Space}}.

[[File:DFwikiDigChannelExamples.png|200px|thumb|right|Demonstrating the difference between mining and channeling. Mining creates empty space on the same level where it is designated. Channeling creates empty space in the level below, clearing the floor. The levels are connected by up/down ramps. ]]

{{TipBox2|titlebg=red|float=left|Channeling|
Note that channeling can be [[fun|dangerous]]. Unless you know what you're doing, you should only ever make a pit one z-level deep. If you dig a pit multiple z-levels deep, only the lowest level will have an upward [[ramp]], which is not enough for dwarves to leave the pit. (Dwarves can [[climb]] out in some circumstances, but this is unreliable.)

<diagram>
Pit depth: 1 z-level 2 z-levels 2 z-levels
Ground[%26] [#2:1]__[#4:1][%31][#2:1]__ __ __ __ [#4:1][%31][#2:1]_
[#6:1][@4:1][%178][%178][#4:1][@][%30][#6:1][@4:1][%178][%178][@#] [#6:1][@4:1][%178][%178][#4:1][@][%31][#6:1][@4:1][%178][%178][@#] [#6:1][@4:1][%178][%178][#4:1][@][%31][#6:1][#4:1][@][%30][#6:1][@4:1][%178][@#]
[#6:1][@4:1][%178][%178][%178][%178][%178][@#] [#6:1][@4:1][%178][%178][#4:1][@][%30][#6:1][@4:1][%178][%178][@#] [#6:1][@4:1][%178][%178][#4:1][@][%30][#6:1][@4:1][%178][%178][@#]
[#6:1][@4:1][%178][%178][%178][%178][%178][@#] [#6:1][@4:1][%178][%178][%178][%178][%178][@#]
</diagram>

This diagram shows the cross-section (side view) of 1x1 pits channeled 1 z-level deep, 2 z-levels deep and the correct way to do a 2 z-level deep ramp. The appearance of "downward ramps" can be confusing as there is no such thing - the down arrow indicates a ramp on the level below. Dwarves in the first pit can walk up the ramp to ground level and escape, while dwarves in the second pit cannot use the ramp at all. The third pit lets dwarves walk back to the surface again since the two ramps are offset to produce a continued slope. In short, channels (particularly channels multiple z-levels deep) can be dangerous. Digging an entryway from the surface level is one of the few times you'll ever need to channel.

Stairs can also be used for an entryway, but channels allow [[wagon]]s entry to your fortress.
}}
If your wagon is near a [[cliff]] or hill (generally speaking, any difference in levels, usually shown by the existence of natural ramps), you can just designate a tunnel to mine ({{K|m}}) into the cliff to create an entryway. If the wagon is surrounded by flat terrain, [[channel]] out a 3x3 rectangle on the surface with {{K|m}}-{{K|u}} to create a sort of pit with ramps on the edges, then go down one z-level with {{K|c}} (or use the mouse scroll wheel) and tunnel into one wall of the pit (with {{K|m}}) to create your entry.

Dig a hallway one tile wide and ''at least'' 10 long, ideally more like 20. This will be your entryway.

Your entryway defines the boundary between your safe and protected inner fort, and the big, bad, outside world. You want this to be your only entrance, so that you only have to worry about defending this one opening. A somewhat-outdated video guide to starting a fortress can be found [https://www.youtube.com/watch?v=CLYDcuk29bE&feature=plcp here]. (Note that this applies to v0.34.11, not v{{current/version/ns}}, so some parts may be inaccurate in the current version.)

{{clear}}
=== ''Additional miners'' ===
Mining will go faster if you have more than one dwarf doing it. By default, only one dwarf has the Mining labor enabled, but this can be changed fairly easily:
* Press {{K|y}} to open the labor menu, and select "Miners" on the left side.
* Choose a dwarf that isn't doing anything especially useful (the fish cleaner is a good choice for a beginning fortress, but you can always change your mind if you end up with a useless peasant later on)
* Click the check box next to the dwarf to enable the mining labor.
* Exit with {{k|Esc}} or right mouse.
The next time you designate an area for mining, both of your miners should start working (assuming they're not busy doing something else).

'''Notes:'''
* Each miner requires a [[pick]]. A standard embark comes with 3 picks. If you want more than three miners, you'll need to forge more picks (forging is covered later in this guide). Two miners should be adequate for most fortresses, but more miners can add reliability (for when a miner decides to sleep) and speed. For now, you'll almost never need more than two miners, but you'll want more once your fortress expands.
* If you're digging a one-tile-wide hallway, only one miner can work from an end.
* Mining, Wood Cutting, & Hunting labors are mutually exclusive - a dwarf can only have up to one of these professions active at a time. For this reason, it's not recommended to make your only woodcutter a miner, since they won't be able to cut wood anymore.

==Delving Secure Lodgings==
Near the middle of the entry tunnel, build a 5x5 room, and link it to the entrance tunnel with a 3-tile-wide passageway. Expand the main entry tunnel to ''three'' tiles wide from the entrance of the new room to the outside entry. At the end of the entry tunnel, dig a small room, which will later become your main stairwell. Two tiles past that, dig a larger room, which will later become your general stockpile, and connect it to the stairwell with a narrow passageway.

[[File:DFwikiExampleLayout.png|thumb|right|An example layout, as described in this section. Note the 3-tile wide passage - this allows merchants to access your depot, which will go in the 5x5 room. Note that the turn also needs to be 3 tiles wide; otherwise, wagons won't be able to access the room.]]

=== ''Room dimensions'' ===
Apart from wagon access (3 tiles wide), the trade depot (5x5), and other workshops (3x3), there are no fixed dimensions you need to worry about. The lower limiting factor is the traffic your tunnels receive (dwarves may have to start climbing over each other), and the space your rooms need (stockpiles, tables/chairs, livestock). The practical maximum size is limited by how long it takes your miners to dig the rooms out, especially if they're digging in stone instead of soil (digging through soil is much faster). Most sites have at least one level soil layer below ground level, which is where you're digging right now, but as you dig deeper you'll hit stone (if you haven't already), and digging will become slower. In most fortresses, even the main hallways never need to be wider than 3 tiles, and needing more than 3 tiles of stairs per floor is very rare. A 3x3 per floor staircase (9 stairs!) is absolute overkill for anything but 20-year-old 300-resident capitals. For most tunnels in your fortress, 2 tiles wide will be sufficient, and many will be fine at just 1 tile wide. 11x11 is a reasonable size for stockpile rooms. However, something smaller is perfectly fine for rarer stockpiles, offices, and small dining rooms. Commoners’ bedrooms need not be larger than the amount of furniture you want inside.

=== ''Mining safety'' ===
While mining, take care to avoid digging into [[water]]. Dwarves are usually poor swimmers, and are unlikely to escape from an underground flood. However, it is safe to mine ''next to'' underground water, as long as you leave at least one "wall" tile between them (see the picture to the right). You can also mine one z-level under a body of water (for example, mining under a river), but you will have to designate each tile individually because DF automatically cancels digging of newly-revealed "damp" tiles (tiles are considered damp when they are adjacent to a water tile, regardless of whether the water tile is on the same z-level or not).

Also note that '''water can flow diagonally''':
<diagram>
[#00f]≈[#]▓.▓ [#00f]≈[#]▓.▓
▓▓.▓ ▓..▓

[#0f0]ok[#] [#f00]flood[#]
</diagram>

=== ''Stockpiles'' ===
[[File:DFwikiStockpileMenu.png|right|thumb|Keep corpses, refuse, stone and wood out of general use stockpiles. You can come back and change the settings on this stockpile by clicking on it to open the stockpile menu, and clicking "Custom". Try to remember to come back here to disable/forbid types of things as you create more specific stockpiles for them.]]
'''Stockpiles''' are very important. These areas are where your dwarves will drop things for storage when they aren't needed elsewhere. To create a '''general purpose stockpile''' for your first storage area:
#Hit {{K|p}} to open the Stockpiles menu.
#Click the plus sign at the bottom to add a new stockpile.
#Draw a rectangle and click "Accept".
#Click [[Stockpile#Custom_stockpiles|"Custom"]] to change the goods that the stockpile accepts. Enable everything but '''Corpses''', '''Refuse''', '''Stone''', '''Gems''', and '''Wood'''. To do this, first click "All" in the top left to enable everything, then go through each type you want to exclude, and click "None" in the top-center of the screen. This will reject all goods of that type.
#{{k|Esc}} or right mouse twice to exit the stockpiles menu.
Once you exit the stockpiles menu and unpause, you should see dwarves running off to haul everything from your wagon into the new stockpile area. Later, if you like, you can change what sort of things the stockpile accepts by hitting {{K|p}}, clicking on the stockpile, then changing the stockpile settings as above.

It is particularly important to '''keep wood, stone, refuse, and corpses out of your general purpose stockpile''', so you may want to double check to make sure all of these things are disabled in the stockpile settings. Failure to keep these things out of this stockpile will rapidly fill it up, causing workshops to become cluttered when dwarves can't store things in the stockpile.
'''Note:''' When assigning stockpiles, you should make sure they're in a vacant area (i.e. the tiles should not have any items already stored on them). Dwarves will not haul items to occupied tiles, so make sure the area is vacant (and already mined out) before assigning a stockpile.

=== ''Stairways'' ===

{{TipBox2|float=right|titlebg=#0a0|width=45%|Up, Down, Up/Down: Types of Stairs|
In Dwarf Fortress, every [[z-level]] is composed of a [[floor]] and a [[wall]] (or "space between floors"). The confusingly named "down" and "up" [[stairs]] have nothing to do with the direction creatures can move to; instead, down stairs penetrate floors, while up stairs penetrate walls. Up/down stairs penetrate the wall and the floor below. ''(note the picture to the left)''

When you designate a staircase to be dug out, the top level will be down-stairs, any inner levels will be up/down stairs, and the bottom level will be up-stairs.
}}

Dig a [[Stairs|stairway]] in the room you dug out for the stairwell (''not'' the 5x5 room that you dug out earlier): press {{K-|m|t}}, click on the floor of the room to start the staircase, scroll down one level, and click again to finish designating the staircase. This will create down-stairs on the top level, and up-stairs on the level below. To continue digging downwards later, you can designate another staircase ({{K-|m|t}}) starting on the lowest exposed level and continuing downwards. For now just dig down one level.

[[Image:DF2014 Terraform.png|thumb|left|600px|''This is how the different stairs would look like from the side.'']]

{{clear}}

==Temporary Meeting Area==
[[File:DFwikiTemporaryMeetingHallExample.png|thumb|right|An example meeting area. Note that this layer has a different type of soil than the layer above - this can happen often. Also note that the "north" side of this room is directly below the lake in the level above, but no water is present.]]

On the second z-level below ground (the one below the stockpile level, which you just reached with the staircase), dig a short, 3-tile wide passageway (this only needs to be 1-2 tiles long). Past that, dig out a room between 5x5 and 7x7, leaving room to enlarge it in at least one direction in the future. Using the {{k|z}} key, create a meeting area in the room you just created, filling the entire room (be careful not to make this too small lest your [[overcrowding|overcrowded]] animals start fighting). This works much like creating a stockpile except that you define what the area is for before you draw the rectangle. Select "Meeting area", draw the rectangle, filling the entire room, and click "Accept". Your idle dwarves will hang around in this area, hopefully keeping them inside the fort and out of trouble.

NOTE: Again, make sure your [[DF2014:Activity_zone|activity zone]] is already mined out before attempting to designate the meeting area.

{{clear}}

==Refuse==
[[File:Dwarf fort tut miasma.jpg|thumb|right|Avoiding [[Miasma]]]]
Outside your fort entrance, use {{K|p}} and click the "plus stockpile" icon to create a stock{{K|p}}ile for [[Stockpile#Refuse|refuse]] (trash can icon) ''at least'' 5x5 in size. This should be outside in the open or you will have problems with [[Miasma]]. If you do not disable [[vermin]] (Item Types -> remains), you will probably have to expand it later as it will fill up with vermin remains rather quickly. If you are seeing refuse appear in your general-purpose stockpile instead of the refuse pile, click on the general stockpile and check its custom settings to make sure refuse has been disabled.
{{clear}}

==Food==

Food is necessary for your dwarves' survival - to keep functioning, they require constant supplies of food and drink - the amount of food and drink currently available is displayed in the status bar at the top of the screen. Luckily, your dwarves will eat almost everything raw, including plants.

===''Farming''===
For a reliable, long-term food and alcohol supply, you'll need to set up a farm. Dig out a medium-sized room in a [[soil]] layer (including sand, clay, loam, silt, peat, and ooze) accessible from inside your existing fortress. 5x5 is a good size to start with, but you'll want to leave room to expand in at least one direction. You must pick an ''underground'' area with mud or soil*. Placing this near the stockpiles is more efficient, since farmers won't need to travel as far.

{{Dual image
|premium=File:DFwiki5by53by3farm.png
|classic=File:Quickstart_layout_3.png
|width=100px
|caption=A 5x5 room with a 3x3 farm plot
}}


* Hopefully you have chosen a site with a soil layer, which will make farming much easier, but if not you will need to [[Irrigation|irrigate]] to create the required mud on stone floors.

Use {{K-|b|o|f|p}} to build a 3x3 [[Farming|farm plot]] in the room you just created. Position the farm plot ideally near the wall to leave space for more plots later on.

The {{DFtext|Planters}} work detail must be enabled for at least one dwarf, or the farm plot won't get built and farming will not take place. By default, Planters is set to "Everybody does this", so there's no need to change this now.

{{K|Esc}} out of the build menu and wait for the farmer dwarf to create the plot. Once the plot is built, click on it, and set the plot to grow [[plump helmet]]s during all seasons. You need to go through each season tab to enable plump helmets in all seasons — otherwise you'll end up with an idle field for 3/4ths of the year.

Later, if you are curious what is planted in each plot this season and how much, click on the plot and it will show the list of seeds currently planted. There is no icon for a partially grown plant, so an empty field will look identical to a fully planted field until your crops are ready for harvest.

Note that a default embark starts with ''five'' plump helmet seeds — for now, only half of your field will end up being planted. Eventually, as your dwarves consume plump helmets, more seeds will become available and will be automatically planted by an unoccupied farmer.
:''For more troubleshooting tips, see [[How do I build a farm]]''
{{clear}}

=== ''Emergency food sources'' ===
Occasionally, even with a working plump helmet farm, you may experience food shortages. For now, you should have plenty of food on hand left over from embarking. However, if you ever run low on food, there are a few ways to obtain more:

==== ''Plant gathering'' ====
If you have shrubs ({{raw tile|"|2:0}}) growing above ground, you can harvest plants from them. Note that this requires a dwarf with the {{dftext|Plant gatherers}} work detail, and time (this can take a while for an inexperienced dwarf, and it doesn't always yield edible plants). To start, {{K|g}}ather plants on the surface (similar to selecting an area for mining, except it only selects plants in the given rectangle). Once processed, some will leave behind harvested plants (often edible berries).

====''Butchering''====
If you suddenly run low on food, butchering an animal is another option. Build a [[butcher]] shop ({{K-|b|o|f|b}}) and mark one of your animals for slaughtering (press {{k|u}}, click on "Pets/Livestock", and click the meat cleaver next to the animal you want to slaughter). A dwarf with the butchering labor enabled will haul the animal off to the butcher's shop, work for a while, and produce neat stacks of meat products.

==Building material==
Initially, [[wood]] is probably a good choice for building material, as it's lightweight and can be easily obtained. You will need plenty of building materials as your fortress grows, but wood will suffice for now. If you are unable to locate enough wood (or if you run out of trees, which is unlikely at this point), extend your staircase down to a stone level ({{k|m}}-{{k|t}}) and mine out a small area (at least 5x5) to obtain stone.

Even if you don't have trees, you can obtain 3 logs from your embark wagon. Click on your wagon, and click the button in the top right to deconstruct it. This will flag the wagon for disassembly. Eventually a carpenter will come along and turn the useless wagon into 3 units of wood. (Removing other buildings is done the same way.)

===''Woodcutting''===
{{Update in next major version}}
Assuming your site has [[tree]]s above ground, now is a good time to start obtaining wood. Create a stock{{K|p}}ile for wood outside your entrance (preferably near to it). As it will only be temporary, don't make it too big (maybe 5x3, or 15 tiles total). Later, you will move this closer to your carpenter's workshop (once you build one), so don't worry about placement too much. Also near the entry, designate a couple of trees to be chopped down with {{K|l}}. One tree will produce many logs, so only designate three to five at this point. If you designate too many trees, your woodcutters will spend all of their time chopping them down and hauling the resulting logs, instead of doing other work. As soon as one tree is cut down and its wood stored in a stockpile, you can proceed to the next step (your woodcutter will continue cutting down any remaining designated trees).

==Drinks==
Drinks can be more problematic than food, since they require more preparation (except for [[water]], that is). In warmer weather, you can specify a "water source" activity {{K|z}}one around a lake or river on the surface to keep your dwarves from dying of thirst, but dwarves deprived of [[alcohol]] slow down and become unhappy. In addition, drinking outside can be dangerous — dwarves running outside constantly risk running into wild animals, or worse. Creating a [[still]] to brew alcohol is the simplest solution to these problems.

You need a brewer to brew drinks. Fortunately, the brewing labor is enabled on all dwarves by default. If you want to change this later, use the [[Labor|labor menu]] ({{K|y}}).

[[File:DFwikiCompletedStillQuickstart.png|thumb|right|A completed still]]
Assuming you have building materials available (which you will if your woodcutter has been doing their job), you can now create a still:
# Dig out a 3x3 area connected to the farm plot.
# Use {{k-|b|o|f|l}} to build a still. Position it in the 3x3 area you just created.
# Click on a building material for the still (this is probably one of the logs you just cut down by default).
After a short delay, one of your dwarves should run off, drag a log over to the workshop site, and build the workshop. (This is also how building other workshops works, but you won't need to do that yet).

To brew drinks, click on the still, click "Add new task", and "Brew drink from plant". '''This will not work yet''', since you don't have any empty barrels or rock pots, but you should start brewing in the first six months (see [[Calendar]] and [[Status]]).
{{clear}}

==Pasture==
{{TipBox2|float=right|Grazers|
If you aren't sure whether or not an animal is a grazer, you can check {{catlink|Grazer|this category}}. (You can also [[Special:search|search]] for the animal on this wiki.)
}}
If you have any grazing animals with you, such as the draft animals used to pull your wagon, they will die if they are kept away from grass for too long. Use {{K|z}} to create a Pen/[[Pasture]] zone over a grassy area outside and assign your grazing animals to it with the "plus bunny" icon in the top right of the zone menu. This area needs to be about 10x10 or so to ensure they have enough grass and don't trample it all. The amount of grass required varies greatly, depending on the type(s) of animals being pastured. If you intend to keep grazing animals permanently, you may need vastly larger pastures later. As an alternative, you might wish to [[Butcher's shop|slaughter]] your largest animals for food and materials.

==Designing your first fortress==
While this guide recommends a vertical fortress design around a central stairwell, with each z-level being used for a particular purpose, it is not really that important to use this design for your first fortress. Therefore, feel free to put any of the areas described in the rest of this guide on your main level or wherever you want as long as dwarves can get to them without going outside the fort. In other words, you can think of the "levels" described in the guide more as areas that can really all be on the same level if you have space. Later you can ponder over what makes things most efficient, but for now just do whatever you find easiest. Note that you may need to dig down a bit to get to stone if you have more than one z-level of sand/clay/soil below the surface.

==Workshops==
[[File:DFwikiStockpileWorkshopQuickstart.png|thumb|right|An example workshop layout. The gem stockpile (empty) is north of the Jeweler's workshop (southwest corner), the wood stockpile is east of the Carpenter's workshop (northwest corner), and the stone stockpile occupies the rest of the space. Note the wheelbarrow (Ö/umlaut-O) in the stone stockpile.]]
Most labors of your dwarves need a place where they can process raw materials — [[workshop]]s. Almost all of them occupy a 3x3 square, and most of them require just 1 unit of any building material (wood, stone, metal). Dig your stairwell down one level (with {{K-|m|t}}), if you haven't already. It's fine if this layer is soil — in fact, soil is better, since it's easier to dig through (if you only have one soil layer, you can put these workshops somewhere on your first level). Dig space for your workshops off of the stairwell. It will hold your [[Mechanic's_workshop|mechanic's]], [[Stoneworker's_workshop|stoneworker's]], [[Carpenter's_workshop|carpenter's]], and [[Jeweler's_workshop|jeweler's]] [[workshop]]s. Something to consider is stockpile proximity: the farther away the material is the dwarves use, the more time they waste with walking. So for now, dig out some more space for stockpiles close to where your new workshops will be (wood for your carpenter, stone for your stoneworker and mechanic, and gems for your jeweler).
It doesn't matter if you put everything in one large room or dig out small rooms for each workshop and stockpile. Once you've dug out your rooms, set your miners to work by adding a z-level or two to the staircase. Hopefully you'll obtain some stone by doing this, which will be useful eventually. While your miners are busy, use {{K-|b|o}} to build the workshops, using whatever building material you have. If you are still digging in soil and don't have stone yet, just use wood; the material really doesn't matter in this case. Be sure that your craftsdwarves still have labors corresponding to each workshop enabled (see [[#Labor and work details|Labor and work details]] above) so they will begin construction. (Dwarves already busy mining or hauling may not immediately stop to construct workshops; if you like, you may temporarily disable other labors in order to jumpstart workshop construction.) If the construction of any building gets "suspended" click on the workshop and click "Resume construction" to unsuspend it. (This can happen if another dwarf or object is blocking the way. See [[#"Garbage" Dumping|Garbage Dumping]] below if you find you need to remove an object.)

{{TipBox2|float=right|titlebg=#0a0|Too Good for Menial Peon Work|Certain labors are crucial in setting up a fort. At some point you may want to disable less important labors such as hauling for dwarves with the crucial skills of mining, masonry, architecture, carpentry, mechanics, and maybe others. You want these dwarves working on creating beds, doors, and trap components before hauling stone and cleaning.}}

Click on your stoneworker's shop and queue up one [[table|table]] and one [[throne]]/chair. You will find out why you need these in a second, but now is a good time to start building them. If you still don't have any stone at this point just use wood at the carpenter's workshop.

At this point, it is a good idea to build a few [[wheelbarrow]]s to make hauling large objects (particularly stone) more efficient. Queue up 2 or 3 at the carpenter's workshop. (Wheelbarrows are located near the bottom of the list, you will need to scroll all the way down.) While the wheelbarrows are being built, click on your stone stockpile and click the barrel icon, and increase "Max wheelbarrows" to 3. Your dwarves will automatically move wheelbarrows to the stockpile once they are built.

===''"Where did I build that ____?"''===
As you build workshops, furnaces, Trade Depot, other buildings, rooms and even zones, you may start to lose track of where they all are -- or where they're supposed to be built, but some dwarf is too busy eating/drinking/hauling. There are a couple of commands available from the main UI that will help you locate what you built.

* You can View {{K|P}}laces and click the "Workshops" tab to see a Building List, and also Zoom to the building/item, or view the building's tasks.

* For incomplete buildings/constructions, you can also open the {{K|t}}ask list and then recenter on the partially constructed building to find the intended location.

{{clear}}

== Brewing ==
You'll need [[barrel]]s to store drinks for your dwarves. Queue up two or three barrels in your carpenter's workshop. (If you run out of wood at any point, cut down another tree or two outside). If a lack of wood cancelled a job, you will need to queue the job again. Go back to your still and order some drinks to be brewed. Each drink requires one barrel and one edible plant, such as a plump helmet. Even if none of yours have been harvested yet, you should have some left over from embark. Also, brewing plump helmets creates ''two'' seeds from one plant, which makes plump helmets an excellent choice for a beginning fortress. Five barrels should be plenty for now (each plant makes 5 "units", or servings, of booze, and dwarves don't need to drink too often, so 30 units should last you a whole year. When the stocks get low, you'll probably want to start queueing up more drinks to be made (you should have more empty barrels by then)).

=="Garbage" Dumping==
{{main|Garbage dump}}

'''Note that garbage is not the same thing as refuse.''' [[Stockpile#Refuse|Refuse]] is [[Miasma|rotting stuff]]. Garbage is anything you designate to be hauled to a [[Activity_zone#Garbage_Dump|garbage dump]], even important things that aren't really garbage. Think of your garbage dump zone as a way to specify that objects you select will be brought to a specific area.

[[File:DFwikiGarbageDump.png|thumb|right| The garbage dump icon in-game.]]

Press {{K|z}}, click on "Garbage Dump", and create a 1x1 activity zone somewhere near your mason's and mechanic's workshops. Unlike stockpile areas where you are limited to storing one object per tile, any number of items may be piled in a garbage area. That means you will only need one tile to hold as much "garbage" as you like. Although many of the room sizes in this guide are suggestions, think of the 1x1 garbage dump size as mandatory. At some point you will probably want to retrieve an important item from your garbage dump, and the more tiles your dump contains, the harder it will be to find anything in it. Press {{k-|i|p}} to select the mass dump/forbid tool. Select a rectangle over the loose stones cluttering up your living area (if there are any – this often isn't a problem yet if you've built your fort in a soil layer). This will designate this stone to be transported to a garbage dump zone. Be sure not to designate the stone in your stockpiles by mistake, since that will only cause your dwarves to perform unnecessary hauling. Once the stone from your living area has been moved there, it will be set as [[Forbid|forbidden]]. Before it can be used you will need to unforbid it using {{K-|i|F}} (or just {{K|i}}). Note that dwarves hauling stone (or any large, heavy objects) move slowly, and can take a lot of time to reach their destination. This can be a major waste of time if you designate 50 boulders to be dumped at once. Unless the stone is in the way of something, you don't ''need'' to dump it every time you dig out a new area. Stones lying on the ground don't slow dwarves down at all. If there is a particular dwarf you don't want hauling "garbage", use the labor menu ({{K|y}}) and select the "Haulers" work detail. From there you can select certain dwarves that you want to haul items. By default, Haulers is set to "Everybody does this". You might want to exclude Miners from hauling, since they are far more useful when digging than when moving the stone they just dug out.

Congratulations! Knowing how to use garbage dump zones puts you head and shoulders above many new players - it takes some people weeks to figure this out.

==Trading==
Not all embark sites have all the resources you need for a successful fortress, but every site has ''something'' you can sell. A talented dwarf can process any useless resource into something valuable, and [[trading]] is a good way to sell those goods.

''Note that producing goods creates [[wealth]] and getting too much wealth too fast can have [[Immigration#Migrant_wave_sizes|unwanted]] [[Siege|consequences]].''
===Trade Depot===
Build a [[trade depot]] using {{K-|b|T}} in the 5x5 room you created near your entrance. This is where [[caravan]]s will park their stuff and where [[trading]] will take place when one arrives. (as stated earlier, the wagons are 3x3 so the entrance tunnel needs to be at least 3x3 for the wagons to go by). You need at least 3 logs or boulders to build the depot. [[File:DFwikiTradeDepotExample.png|thumb|right|An example Trade Depot.]]

===Producing for export===
While there are some goods that are more valuable, and some that are less valuable, it's a good idea to simply produce/export what you have too much of and to import what you have too little of.
Generally though, [[Gem]]s and [[Finished goods]] are decent exports for a new player.

===Trading===
Once a caravan has arrived, you can mark the goods you want to sell through the Trade Depot, and your dwarves will begin moving them to the depot. Be careful not to sell wooden items to [[Elf|Elves]]; '''this includes containers:''' even a wooden bin full of metal crafts will make them upset. The same applies to items made of bone and shell (as those involve animal harm). Also note that the traders will want to make a profit off of you. While they're happy with about 200%, the more profit they make on your site, the more goods they will bring next time, so it can be a good idea to give them even better deals.

''A more detailed overview of the entire process is [[Trading#Trading_Flowchart|here]].''

===What to buy===
In your first fortress, your priority should be importing some [[food]] and [[alcohol]]. In addition, you might want more [[Meat industry|livestock]], [[seed]]s (comes with a free bag), and - depending on what resources you are missing - additional [[pick]]s, [[barrel]]s, [[wood]], [[bag]]s, as well as [[rope]] and a [[bucket]] (for a well). While you're at it, check if you need an [[anvil]]. Maybe you forgot to bring one, or a [[kea]] stole it. Always having a small supply of ''all 3 kinds'' of [[cloth]], some [[gem]]s, [[leather]], a bit of [[sand]] (free bag!) are handy to have, as those are hard to come by on short notice.
If you're short on weapons-grade [[metal]] for your military, import not only actual metal [[bar]]s and [[ore]]s, buy ''all'' metal goods you can afford and [[Melt item|melt]] them down in a [[smelter]] to increase your yield.

===Troubleshooting===
Once the depot is built, make sure your depot is accessible. There needs to be a 3-wide passage from the depot to the edge of the map.

If you see the message [[Their wagons have bypassed your inaccessible site]] when the merchants arrive, try these solutions:
* Is the path to the depot (in your fortress) less than 3 tiles wide? If so, expand the entranceway and try again.
* Are there [[tree]]s blocking a path to the depot outside? Try clearing a path by cutting down a few.
* Are there [[boulder]]s ({{raw tile|∞|7:0:0}}) blocking the path outside? To remove them easily, you need a [[stonecutter]]. If you selected "play now", you should have one already. Use {{K|v}} to smooth stone and designate the boulder(s) for smoothing. They should flash this symbol: {{raw tile|┼|7:0:1}}
* Is the path to the depot only accessible via stairs or did you build traps in the way? Wagons cannot pass traps or stairs, even if they're 3x3 wide.
* Building a paved [[road]] {{K-|b|n|o}} will stop trees from growing on the wagon path, and can be a good way to ensure that the wagons have an unobstructed path to your depot.
It's possible that there are multiple obstacles blocking the depot, so this can take some troubleshooting.

''The first few times the traders arrive, they will not bring a wagon anyway. They will only start to bring a wagon once your fortress is a [[barony]]. Without a wagon, they will carry much less goods and you can sell them much less, because their carrying capacity is greatly reduced.''

== Migrants ==
{{gametext|Some migrants have arrived.}}
At some point soon, you'll most likely be getting migrants (if you haven't already). You'll usually get between 5 and 15 migrants in the first 2 waves, which occur sometime during your second and third seasons. See [[/Migrants|this page]] for advice when you receive migrants.

== Bedrooms ==
Up to this point, your dwarves have probably been sleeping on dirt or rock in your fortress. While this is fine for a short time, your dwarves will gradually become less happy if they are forced to sleep without a bed. Under normal circumstances beds can only be made from wood, so be sure to designate some more trees to be cut down if you're short on logs.

[[Bedroom design|Designing living quarters]] is largely a matter of personal preference and aesthetic sense. While a few useful designs are discussed here, there are many other options. In general, try to keep the bedrooms close to the stairs, and make your access hallways at least two tiles wide to reduce congestion.

=== Location ===
{{migrated section}}
Because noise generated from certain jobs (especially mining and woodcutting) can bother sleeping dwarves, doing these jobs within 8 tiles of a sleeping dwarf should be avoided (see [[noise]] for more information). There are two ways of accomplishing this:
* Placing bedrooms at the end of a hallway at least 8 tiles long will avoid most noise (as long as you are careful to avoid noisy jobs directly above or below the bedrooms).
* Extending your fortress down several z-levels will also work (9 levels from the surface is a safe choice), although extending a 3x3 staircase takes more work than extending a single hallway.
Both options work equally well, as long as you are careful to avoid disturbing sleeping dwarves. Ultimately it depends on how you want your fortress to look.

=== Layout ===
Due to the limited resources of a new fortress, setting up a communal sleeping area in a dormitory is often the best short-term solution. However, you can also set up individual bedrooms for dwarves.

'''Benefits of individual bedrooms:'''
* Dwarves are happier with their own bedroom and furniture.
* Individual rooms can increase your fort's perceived wealth.
'''Benefits of dormitories:'''
* Dormitories are easier to set up and expand (only one room is necessary, and each dwarf only requires one bed).
* Sleeping dwarves are much less likely to be attacked when other dwarves are around them.
* Multiple dwarves can sleep in a dormitory. In contrast, only one dwarf can ever sleep in a bedroom (dwarves cannot sleep in another dwarf's bedroom, even when unoccupied).
* Far fewer beds are needed – in a fort of 50 dwarves, for example, around five dwarves will be sleeping at a time (on average). A dormitory, therefore, rarely requires above ten beds, while individual bedrooms would require 50 beds to be built.
* Even when all of the beds are occupied, dwarves will still sleep in the general area of the dormitory. This is more convenient than having dwarves sleeping all over your fort.
For now, setting up a dormitory is easiest (although you can change this later, if you feel the need to).

=== Building ===
Queue up as many beds as you need in a carpenter's workshop (no more than 3 or 4 should be necessary for a dormitory). Build the beds with {{k-|b|f|b}}. You can check "Keep building after placement" to place multiple beds. (As long as your furniture/general-purpose stockpile isn't full yet, dwarves will store beds in them as they are finished, so there may be a delay before they're available to be built.)

'''Setting up a dormitory:'''
# Dig out an empty room in the location you selected.
# Open the {{K|z}}one menu and click on "Dormitory". Draw a rectangle over the room you dug out.
# Once you have a bed ready, build it anywhere in your dormitory.
You can place multiple beds in the dormitory.

[[File:DfwikiIndividualBedroomsQuickstart.png|thumb|right|An example of individual bedrooms (with furniture, discussed below)]]
'''Setting up individual bedrooms:'''
# Dig out a small room for each bed (the size and shape are up to you, but 2 to 4 tiles generally works best).
# Build each bed ({{K-|b|f|b}}) in a room when ready
# Make sure each room is enclosed by a door ({{K-|b|p|r}}). You can make doors at the carpenter's or stoneworker's workshops.
# Open the {{K|z}}one menu, and click on "Bedroom".
# Click "Multi" (instead of "Paint"), and draw a rectangle containing multiple bedrooms. Each room with a bed, enclosed by a door, will be marked as a bedroom.
You should see {{DFtext|Current owner: Nobody}} in the menu. A dwarf will eventually get around to claiming the bedroom – you don't need to assign each dwarf to a specific bedroom.

==Nobles and Administrators==
Hit the {{k|n}} key to open up the [[Noble|nobles and administrators]] screen. The most important positions to assign are '''[[manager]]''', '''[[broker]]''', and '''[[bookkeeper]]'''.
* A '''manager''' will allow you to queue up [[work order]], which will greatly simplify managing your production.
* A '''bookkeeper''' will allow you to maintain inventory counts on the stoc{{K|k}}s screen so you'll know what you do and don't have.
* A '''broker''' is necessary to trade with a caravan once one has arrived at your [[trade depot]].

===Manager & Bookkeeper===
Your [[expedition leader]] is a good choice for manager and bookkeeper when starting out. Don't worry that it's just one dwarf doing all this; none of these jobs take very long.

:''See [[Stocks]] for a detailed explanation of the stoc{{K|k}}s screen.''

===Broker===
The broker should be another one of your other dwarves (rather than being the same as your bookkeeper) so that they're not too busy doing bookkeeping to actually talk to the traders when a trade delegation arrives.

Don't worry about the [[chief medical dwarf]] yet. They will be needed when you set up your [[Healthcare|hospital]] which won't be covered in this guide. Feel free to go check out the [[Healthcare]] guide once you're done.

===Offices (Studies)===
Some of your administrative positions (manager and bookkeeper) require an [[office]] in order to function. If your manager, for example, doesn't have an office, you will not be able to do any of the things that require a manager even though you have one assigned.
[[File:DFwikiNoblesScreen.png|right|thumb|Nobles screen. The red stuff turns green once an office is assigned.]]

Earlier you should have queued up a table and throne in your mason's shop, and they should be done by now.
# Dig out a room near your sleeping quarters or stockpiles (at least 1x3, no more than 5x5).
# Place the furniture in it with {{k-|b|f|r}} (chair) and {{k-|b|f|t}} (table).
# Wait for the dwarves to install the furniture
# Using the {{K|z}}ones menu, mark the room as an office, and then assign the office to your expedition leader (who should be both your bookkeeper and manager).
# Hit {{K|n}} to verify that these positions now have the office they need (if so, the icon next to the position should no longer be red).

==Furniture==
{{TipBox2|float=right|titlebg=#0a0|width=45%|Different Names, Same Thing|As you've noticed, some things have different names based on what they're made of (for example, chairs vs. thrones and chests vs. coffers) even if they're functionally the same (material almost never makes a difference). [[Furniture#Furniture_types_with_multiple_names|Here's a list.]]

[[Bed]]s are a notable exception — they can only be made of wood, which also includes the giant mushrooms in the caverns.
}}
Now would be a good time to start building some [[furniture]]. You could queue up all these items directly from your workshops, but why not give your new manager a little practice?
Using the work {{K|o}}rders menu, click the clipboard icon in the top right to queue up a new job, and type "[[bed]]", and then select "Make bed." Click the number sign to set the quantity to around 4 (or more, depending on how many beds you need). Next, queue up at least four [[table]]s, eight [[throne]]s/chairs, and four doors. Make sure you select a material you have – rock or wood will both work for all of these (except beds), so use whatever you have in your stockpiles. If you like, you can also queue up a few wooden [[chest]]s or rock coffers and [[cabinet]]s (which can be used in bedrooms, if you set up individual bedrooms). The tables and chairs will go in your [[dining room]], speaking of which...

==Dining and Food Prep Area==
Right off the main stairwell (any unused area by the staircase will work), create three rooms. One will be for general food storage, one a [[dining room|dining hall]], and one a [[kitchen]]. The kitchen will allow you to make [[Cook#Recipes|prepared food]]. Make the room for the kitchen 5x5. The storage area and dining hall should be larger. Ideally, leave empty space on at least one side of your dining hall so that it can be expanded later if necessary.

[[File:DFwikiDiningFoodPrepExample.png|right|thumb|Dining level with dining hall (east), kitchen (north), storage area (west), fishery, butcher's workshop, and tanner's workshop (south).]]

Use {{K-|b|o|f|k}} to build the kitchen in the middle of the 5x5 room. Use {{k|p}} to create food stockpiles in the remaining space around it, as well as the entire food storage room. Go back to your general-purpose stockpile on the top level and change the settings to disable food (click "Food" then click "None" in the center column). This will cause any food in your general purpose stockpile to get moved to your new food-only stockpiles. Hit {{K|y}} and select ''[[Kitchen]]'' from the top of the screen, then disable all cooking for plants, and enable brewing for them so that they will only be used for brewing. Also disable alcoholic beverages for cooking, otherwise your cooks will waste perfectly good hooch in their cooking. The only time you might want to use alcohol in cooking is when you have lots of booze but are running out of food. If you plan to do any fishing, dig out another area and create a [[Fishery]] on this level so the uncleaned fish your fisherdwarf just caught can be cleaned (gutted) for consumption or cooking. If you plan to do any hunting or [[Status#Animal_Status_Screen|slaughter]] any animals, create a [[Butcher's shop]] on this level so animal corpses can be butchered. The fishery/butcher's shop can be placed behind the kitchen or the general food stockpile, for example. A door is recommended for the butcher's shop in order to contain [[Miasma]] should something rot, and to otherwise avoid offending squeamish dwarves. Eventually, go check out the subpage on [[/Stockpiles/]] for more information on fine-tuning these stockpiles for maximum efficiency. For now you can safely procrastinate on this and move on to the next section.

==Placing Furniture==
Once your furnishings are complete, you need to place them in rooms using the build furniture ({{K-|b|f}}) command. Put the new chai{{K|r}}s and {{k|t}}ables in the dining room. If you like, you can add doors for aesthetics (they can be useful in case something starts rotting in your food stockpiles). If you created chests and cabinets, you can add them to each room if you want, but it is not urgent now.

==Meeting Hall==
Add a Meeting Area {{K|z}}one in the dining room. This will cause idle dwarves to hang around in the dining hall. You want idlers in a central location, close to where you will be placing your emergency drawbridge levers. You should probably remove the temporary meeting area (and any other meeting areas that you created earlier).

==Checking Supplies==
{{TipBox2|float=right|titlebg=#a00|Hostile Wilds|Before turning on either hunting or fishing, examine the {{K|u}}nits screen to see if there are any dangerous critters your hunters/fishers need worry about. With hunting especially, you may need to check this screen frequently.}}
Use the [[stocks|stoc{{K|k}}s]] screen to check your stock levels. How much food and booze do you have left? You only have unprepared food at this point, and the booze you brought with you, but soon you will be making more. If you are running low on food, you can designate gathering some [[shrub|outdoor plants]], [[Status#Animal_Status_Screen|slaughter]] some animals, turn on [[fishing]], or turn on [[hunting]] to tide you over for a bit. Hunting and slaughtering animals both require a butcher's shop.

==Brewing and Cooking==
Once your first crop of plump helmets starts to come in, you will want to start [[brewing]] as a [[repeat]]ing task. Also, now would be a good time to start [[cooking]] actual meals rather than forcing your dwarves to eat raw food. Cooking [[Cooking#Recipes|easy meals]] will train dwarves faster, but they may be happier with [[Cooking#Recipes|lavish meals]]. So, you might want to cook easy ones until your cook or cooks skill up to a certain point then have them start making lavish meals. Prepared food is cooked from two (easy), three (fine), or four (lavish) raw food/alcohol ingredients. Each prepared food item will be called a 'something' (for instance, a specific animal meat) "biscuit", "stew", or "roast" depending on the lavishness of the meal.

{{TipBox2|float=right|titlebg=#0a0|Conserving Resources|Some things absolutely require wood (like beds and charcoal), but others can be made out of more common materials like stone. For this reason it's best, especially in the beginning, to make everything that you can out of stone. For example, you could make wood chests and barrels, but stone coffers and rock pots would let you save wood for things that require it and help you rid yourself of all that stone. And if you decide you want solid gold chests or something later when you have more resources, you can always throw out the rock coffers.}}
Speaking of booze, in order to keep the booze flowing, you will need to create some [[barrel]]s, or some stone [[pot]]s. Your dwarves should have emptied a few barrels by now to get you started, but you will definitely need more. A ''lot'' more. If you have an abundance of trees, then you can designate some more for cutting, and have your carpenter make a bunch of wooden barrels, but it may be more prudent to make a [[Craftsdwarf's workshop]], make sure someone has the [[Stonecrafting]] labor enabled, and build a bunch of rock pots. (Rock pots are essentially barrels made of rock.) And don't worry that you've made too many; you almost can't get enough of them. Keep checking your food and drink stock levels on the status bar at the top of the screen periodically. While cooked food (properly stockpiled) and alcohol don't spoil, there is really no need to stock 2,000 units of dwarven wine at this point. Ten times the number of drinks and meals as you have dwarves is more than enough. If you start running out of food or drinks, designate some wild plants for harvesting, [[Status#Animal_Status_Screen|slaughter]] some of your animals, start hunting or fishing, or start more farms. (Actually, now would be a fine time to make another 3x3 farm. Set it to produce [[sweet pod]]s in the spring and summer, [[cave wheat]] or [[pig tail]]s (your choice) in the fall (autumn), and [[plump helmet]]s in the winter. Having multiple types of plants will give your dwarves more variety in their food and drink, keeping them from [[Thought|grumbling]].)

==Storage Space==
{{TipBox2|titlebg=#0a0|float=right|Advanced Stockpiling|Check out the [[/Stockpiles|Stockpiles]] sub-page for more information on fine-tuning your stockpiles, especially in the food production area. This is somewhat complicated and it can safely be skipped if you don't feel like tinkering with stockpiles right now.}}
You should probably start making some wooden '''[[Bin|bins]]''' to help you store more stuff in less space. You might not need them yet, but you certainly will later. Bins are somewhat like barrels/pots, but they can store things other than just food and drink. Bins will also reduce the amount of labor needed to [[haul]] things to your trade depot or other stockpiles. So designate some more trees to be chopped down and queue up some bins. As with barrels and pots, you almost can't have enough bins.

=Beyond a Minimal Fortress=

By now you should have your main entrance created, along with a farm, general-purpose stockpile, refuse pile (for trash), and [[trade depot]]. Somewhere you should have a mason's shop, a mechanic's shop, a carpenter's shop, and a jeweler's shop, surrounded by appropriate storage piles with garbage zone (for excess stone). You should also have a furnished dining area with kitchen, still, and food storage, and a residential area with furnished bedrooms and an office. You should have selected your administrators, and might even have an optional fishery, butcher's shop, craftsdwarf's workshop, or other stuff. At this point, you have all the components of a minimal but functional fortress! Your next steps will be to make it safer and better-protected, to set up your [[metal industry]], and later to prepare your [[military|militia]].

==Traps==
Start producing '''[[mechanism]]s''' at your [[mechanic's workshop]]. Queue up ten. After they are built, use them to create [[Trap#Stone-fall_Trap|stone fall traps]] using {{k-|b|t|t}}. Be sure not to block access to your depot! Queue up some [[cage]]s, and more mechanisms, and use these to create some [[Trap#Cage_Trap|cage traps]] right after your stone traps. Cage traps are incredibly effective at stopping ambushers, but traps in general will not protect you from [[thief|thieves and kidnappers]] who will almost always bypass them. (To deal with these ambushers, see the next section on [[#Guard Animals|guard animals]]). Continue to fill up your entry hall with alternating rows of stone and cage traps as the parts become available. Ideally you want to have enough cage traps to take out most of the [[goblin]]s so your military will only have to mop up.

Note that traps will block wagons from reaching your trade depot (although pack animals will still arrive safely). A few ways to avoid this are shown below:

{|
|-
|<diagram>
[#1:1]^^^^^
[#2:1].....
.....
.....
[#1:1]^^^^^
</diagram>
|A simple strategy, most useful above ground where invaders can come from the sides – underground, this is less useful (invaders don't tend to emerge from the walls).
'''Legend:''' In this diagram and the one below, traps are blue {{DFtext|^|1:1}} (^) symbols, and the green {{DFtext|.|2:1}} and red {{DFtext|.|4}} (.) symbols represent the ground and cave floor.
|-
|<diagram fg="4:0">
░░░░░░░░░
░.......░
░.......░
░.......░
....[#1:1]^[#]....
....[#1:1]^[#]....
....[#1:1]^[#]....
░░░░░░░░░
</diagram>
|A more complex design, but also extremely effective (best used underground). The majority of invaders will choose to take the shortest path, directly through the traps. This can also be extended to make a wider group of traps of a longer safe route.

This is relatively easy to implement if you already have a 3-tile wide hallway – just dig a small loop off it and place traps in the old location.
|}

Note that this is only necessary when caravans can't get to your trade depot, because the hallway is filled with traps - if your trade depot is not behind a trap-lined hallway, you can safely make a hallway full of traps - citizens won't trigger traps.

If you place a trap somewhere you didn't mean to, remove it by clicking on it and selecting "Remove this building".

==Guard Animals==
Create one 1x1 [[pasture]] near the beginning of your entryway, in the middle tile, using {{K|z}}. Assign a [[dog]] or other non-grazing animal to it. This animal will spot thieves and raiders before they gain entrance to your fortress. Try to pick a disposable animal, as it ''will'' be slaughtered by the first ambush raiders. Ideally, don't assign female animals; you want them safe for [[Meat industry#Breeding|breeding]] (you should make sure to keep at least one male around for breeding as well).

==Drawbridge==
In case of an [[ambush]] or [[siege]], you will want to close up your fort, keeping the goblins out until your [[squad]]s have formed up and are in position. Therefore, you can build a [[Bridge|drawbridge]] ({{k-|b|n|b}}) to seal off your entryway. Make sure to set the draw direction, which then forms a barrier to block enemy ranged units. If you don't get the orientation of the bridge correct, it will just retract (disappear) instead of raising up, allowing enemy ranged units to fire across.

Put the drawbridge between the trade depot and the hall-o-traps so you can lock things out of the fort. Build a lever ({{k-|b|m|l}}) near your meeting area and [[Lever#Linking|link]] it to the drawbridge by clicking on the lever and selecting "Link lever". (This linking will require 3 [[mechanisms]] in total.)

==Metal Industry==
[[File:DFwikiForgesandSmeltersExample.png|thumb|right|Level -2: Forge and smelters with bars stockpile in the middle.]]
Now, below your first workshop level, dig out four more 5x5 rooms around the stairwell. Three of these will be [[smelter]]s ({{k-|b|o|u|l}}), and one a [[metalsmith's forge]] ({{k-|b|o|i}}). Designate stockpiles for bars around the smelters and forge. The bar stockpiles will hold [[Fuel|coke and charcoal]] and metal [[bar]]s. You will probably need larger bar stockpiles, but you can dig out more space and expand them later. Also dig out some space and create a stockpile for [[ore]] somewhere nearby. To make an ore stockpile, designate a stone stockpile, then change the settings on it to forbid all types of stone other than ore. Finally, go to your general-purpose stockpile on the top level and disable Bars. Stone should already be disabled on this stockpile, and if so, then ore is already disabled for it.

===Wood Burning===
Somewhere near your carpenter's shop, near your wood stockpile, dig out an area and build a [[wood furnace]] ({{k-|b|o|u|f}}). This is where you will create charcoal (see below) and ash (for making soap). Dwarf Fortress has two forms of carbon which are useful as [[fuel]] in the metal industry: ''charcoal'' (which is charred wood), and ''coke'' (refined coal). They are completely interchangeable. If your map has a lot of '''lignite''' or '''bituminous coal''', you can process that into coke, using charcoal to jump-start the process. If you don't find coal on your map, you'll need to either dig down to [[magma]] or make charcoal out of wood to run your forges and smelters, but don't worry about this yet. You need to do some digging around.

===Mining===
{{TipBox2|float=right|titlebg=#0a0|"I have struck what?"|New players who don't have a degree in geology usually find themselves confused as to what all these mineral names mean. In DF you'll never strike "iron ore" but you will strike [[magnetite]] or [[limonite]] which are [[ore]]s of [[iron]]. If you don't know that these things are ores of iron then it obviously won't occur to you to try to smelt iron. See '''''[[The Non-Dwarf's Guide to Rock]]''''' to help you figure out exactly what you've found.}}
At this point you want to start looking for metal ore. You may have already found some while digging out rooms, in which case you can just mine into the walls of the rooms to get more ore. If you haven't found ore yet or you want to see what else you can find, you will need to dig [[Exploratory mining|exploratory tunnels]] looking for ores, minerals, and [[gem]]s. For now just start digging tunnels out from your stairwell or rooms in all directions and see what you run into. Note that digging into '''damp stone''' or '''warm stone''' is not recommended as those areas may be holding back water or lava which can flood your fort.

===Fuel===
Whether you find [[coal]] or not, you will need to burn wood into at least one unit of [[charcoal]]. If you find some coal ([[lignite]] or [[bituminous coal]]), start your [[smelter]]s out processing it into [[coke]] using your charcoal to get things started. From then out you can burn coke to make more coal into more coke and so on. Put these coke-making jobs on repeat. Only use one smelter to begin with, but you should be getting a group of [[Immigration|immigrants]] fairly soon, if you haven't already, and you can put them to work in the other smelters. Don't give up on finding coal right away. Dig around for a while and if you're starting to get impatient then burn some more wood into charcoal, smelt some ore, and make some [[weapon]]s. If you rely on charcoal for fuel then you'll be needing a ''lot'' of wood, so in that case dig out another room near the furnace and create a wood stockpile. You might also want to just remove a smelter, replace it with a [[wood furnace]], and create the new wood stockpile down in the smelting area. Finally, go designate more trees for chopping.

===Forging===
{{TipBox2|float=right|titlebg=#0a0|Alternative Energy|If you don't find coal then you will have to continue to burn wood into charcoal, or dig down to the bottom of the map and find the magma sea so you can power [[magma smelter]]s and [[magma forge]]s. Getting to magma can be difficult for various reasons that you will discover, so make sure you are ready for some trouble before you go that direction. Burning charcoal should work out okay in the short term.}}
Once you have smelted some ore to get metal bars, and have additional bars of either coal or charcoal, you can start forging metal items. Here are some suggestions on what to make first:
#'''[[Pick]]s''' - You may have only started out with one pick which limits the number of miners you have to one. By this point you are probably wishing you had more miners. Make a few picks and give some dwarves the mining labor once you get some immigrants. It doesn't matter what metal you use to make picks, at least when it comes to mining, so even copper is perfectly good.
#'''[[Weapon]]s''' - Picks actually make pretty good weapons, but there can be some issues equipping them because they're tied to the mining labor. You may want to make a few axes. They make good weapons, at least against most lightly armored opponents you're likely to encounter first, and can be used to chop trees. Start with 5 or so.
#'''[[Armor]]''' - You're going to want some armor. Start with mail shirts, helms, leggings, then gauntlets and boots. Start with 3 or so of each in the order listed, then make more later when your military grows. Also make some shields out of wood, unless you're swimming in metal (since the shield's material doesn't matter for defensive purposes). Once you have the essentials covered, you can include breastplates (but they take 3 bars of metal to make, and they don't cover as much of the torso and arms as a mail shirt).
An important thing to note is that mail shirts protect the upper leg as well as the torso and arms, and high boots protect the lower leg. As dwarves have no knees (at least in military terms), high boots and mail shirts are sufficient to protect your dwarves' legs.
[[Steel]] is the best normal metal to make armor and most weapons out of, but you will likely find that you want some arms before you can make steel. [[Iron]] is good, as is [[bronze]]. [[Copper]] is not ideal, but it still works and is better than no metal weapons/armor at all.

==Gemcutting and Trinkets==
[[File:DFwikiCraftsExample.png|thumb|right|A craftsdwarf workshop. They produce crafts and trinkets which can be traded in a Depot.]]
You should have uncovered some [[gem]]s by now, so put your [[jeweler]] to work [[Gem cutter|cutting]] them. These will be used for [[Trading|trade]]. Only buy things that you need in the first year. [[Finished goods|Stone crafts]] produced by a craftsdwarf can make good trading goods as well. To get enough goods, you will need to dedicate a craftsdwarf's workshop and craftsdwarf to this task full-time, but you're very unlikely to ever run out of stone.

==Sticking to the Plan==
{{TipBox2|float=right|titlebg=#a00|Getting Distracted|Say one of your new immigrants turns out to be a legendary weaver. Should you plant some pig tails and create a loom for him? '''No!''' Put his legendary butt to work smelting metal or something that's part of your current industry even though he has no skill at it. Do not split your efforts yet. You can make use of his unique talents later when you can afford to diversify your industry.}}
Metalsmithing will be your primary economic activity, with cutting gems (and possibly making stone crafts) being used to give you some short-term [[wealth]] until the [[metal industry]] gets going. This means you will need miners, haulers, smiths and furnace operators. Unless a dwarf is doing something else vital to the proper functioning of your fort, such as training in the militia, making traps, cooking food, and so forth, they should be doing one of those four things.

==Wealth and Invasion==
{{TipBox2|float=right|titlebg=#a00|Crafting Invitations for Trouble|Creating too much wealth initially is a sure fire method of pulling down a goblin ambush that you are ill-equipped to deal with. Titans will also start attacking you should your wealth go over a certain amount. For this reason, spend no time smelting gold, smoothing, or engraving anything yet. Most of the wealth you create in the beginning should be the [[weapon|sharp pointy kind]].}}
You may have struck [[gold]] or some other valuable metal, and you may be tempted to put your furnaces and smiths to work creating valuable metal crafts. Don't do it! Until you have your militia formed and fully equipped with armor and weaponry, your smelters and forge should be doing nothing else but smelting cheaper materials like coal, iron, making pig iron and steel if possible, and making weapons and armor. Making [[steel]] will actually increase your wealth quite a bit, but at least you can stab and beat things to death with steel; you can't make weapons from gold.

=Military=

Your '''military''' is an important part of fortress defense. Unless you have totally cut yourself off from the outside world, then you will want at least some sort of military. Once you reach this point, you should hopefully have enough dwarves to start a small military training program. You will need at least 5 dwarves who aren't otherwise doing anything important. If you don't have any spare dwarves yet, or just don't want to mess with it yet, just skip to the next section and come back to this later. Don't wait too long to set up your military though; you especially will want soldiers before you reach a population of 80 dwarves. (You will find out why.) When you're ready to start up your military, see the [[Military quickstart]] guide.

= What Next? =

Congratulations! If you've made it this far then you have a self-sustaining fort going and can now start to branch out into whatever you are interested in exploring. Expect some goblin invasions, forgotten beasts, titans, dragons, giants, and other creatures to interrupt your activities at various points. This is part of the [[fun]].

Here are some things that people almost always do eventually, though not necessarily in any particular order (these are somewhat essential):
*Build [[coffin]]s and a graveyard or [[tomb]]s for dead dwarves and pets
*Set up a [[Healthcare|hospital]]
*Build a [[well]]
*Start producing [[textile industry|clothing]] to replace [[wear|worn-out attire]]
*Build a [[jail]] for unruly dwarves
*Set up [[Scheduling#Alert_Levels|civilian alerts]] to get civilians to a safe area during ambushes and sieges

Here are some things that players often do as their population grows:
*[[Smoothing|Smooth]] and [[engraving|engrave]] walls and floors
*Produce [[Meat industry|Meat]], [[Egg production|eggs]], milk and [[Beekeeping industry|honey]]
*Continue to expand the [[military]]
*Explore new [[Industry|industries]]
*Dig down to the [[caverns]] and create a defended lower entrance with traps to defend the fort against the [[creatures|denizens]] below
*Enable [[Animal training]] for a dwarf and train some war animals
*Build a [[Mass pitting]] system to dispose of caged enemies
*Build above-ground [[construction]]s such as an archery tower or garden
*Create a [[statue|statue garden]] or [[zoo]]
*Farm in an [[Farming#Above-ground_farming|above-ground farm plot]]
*Dig down to [[magma]] and set up [[magma forge]]s and [[magma smelter]]s to avoid the need for fuel
*Build [[machine component]]s to pump magma and water
*Create more [[Trap design|elaborate traps]] such as magma and drowning chambers
*Try some [[stupid dwarf trick]]s

You may also want to just read over the [[Dwarf fortress mode|Fortress Mode Reference Guide]] and the many other very useful documents on the wiki to give you other ideas of what to do.

Keep in mind that how you play is not set in stone. Some people never defend, some start a [[Megaprojects|megaproject]] right after settling, some never dig and just build an above ground castle or town using logs. Some never smelt ore, some start smelting as soon as they arrive. Some make their home in the dangerous natural caverns. Some deal with invaders by flooding the map or isolating themselves completely. And that's not even considering the [[List of mods|mods]] and some of the crazier [[challenges]] that people have come up with. There's really no one "right" way to play DF.

= Feedback =
If you have any feedback on this guide, you can leave a message on the [[{{TALKPAGENAME}}|talk page]] for this article.

{{Getting Started}}
{{Category|Fortress mode}}
{{Category|Quickstart guide}}

[[ru:Быстрый старт]]
[[zh:Quickstart guide]]

Bed

2023-01-05T15:22:06Z

Jan: +version template

{{av}}{{Quality|Unrated}}
{{furniture|name=Bed
|tile=Θ|col=6:0:0
|wood=y
|rooms=
* [[Bedroom]]
* [[Barracks]]
* [[Dormitory]]}}
A '''bed''' is a piece of [[furniture]] manufactured in a [[carpenter's workshop]] and then constructed on an indoor floor. A constructed bed is the base object needed in a [[bedroom]] or a [[dormitory]]. Once a bedroom is set up, it may be left unassigned (to be claimed by any roomless [[dwarf]]) or assigned to a dwarf. Dwarves gain unhappy [[thoughts]] from [[sleep]]ing without a bed and happy thoughts from having their own, high-quality bedrooms, so building beds is often a necessity for a happy fortress.

[[File:beds v50.png|left|Top to bottom: wood, stone, and metal bedframes. Once made at a [[carpenter's workshop]], it will be complete with a pillow and a colored blanket!]]Unlike many other pieces of furniture, standard beds can only be created from [[wood]] (beds made of other materials such as [[metal]], [[stone]], [[gem]]s, or [[bone]] only exist in the form of [[legendary artifact]]s created during [[strange mood]]s). If your fortress has no surface [[tree]]s, you will have to bring wood with you, or rely on [[subterranean]] trees or [[trading|trade]] to get wood for beds. Manufacturing a bed requires one piece of [[wood]]. To construct a bed, click on a [[carpenter's workshop]], click on "Add new task", then click on "Make bed".

In the first season after [[embark]], your first dwarves will want to sleep sometime around 6 weeks after embark (around the 28th of the 2nd month by default), although the exact timing will vary between each dwarf. A beginning fortress might only need 4-5 beds for their initial 7 dwarves, although as time passes and their sleeping rhythms get more out of sync, that number drops. Although a fortress of 100 dwarves might only need a dozen or so beds to accommodate all sleepers at any one time, by the time a fortress reaches that size, some private [[bedroom]]s will, most likely, be a good idea, and bedrooms can ''only'' be defined from a bed.

It's not a big deal for a dwarf to "sleep in the dirt" that first time, but doing so will create a negative [[thought]], and it will take a while for that thought to go away. So, just in case more [[tantrum|bad thoughts]] arise later for some unlucky emo dwarf, it's always best to avoid them whenever you can. You almost certainly have [[Quickstart guide|better things to do]] than to dig out the perfect [[bedroom design|housing tract]] those first few weeks, so a few beds stuffed into some random corner should be more than good enough for your first seven.

== (De-)Construction ==
Because beds may only be built [[indoors]], a bed on the surface will need to have a [[floor]] or [[wall]] built above it before it can be constructed.

Beds can be deconstructed even while a dwarf is sleeping in them, causing the dwarf to wake up. See [[noise]], however.

== Bed Assignments ==
To create a bedroom from the bed, first you must {{k|b}}uild the {{k|f}}urniture {{k|b}}ed, then open the {{k|z}}one menu and click Bedroom. You can then either select a rectangle which contains the bed or draw your room by clicking the paintbrush icon and holding the left mouse button to select the wanted tiles (from the Paint menu which is the one selected by default), or click Multi and draw a rectangle that will automatically draw bedrooms from all the closed (either through doors or constructions such as walls) rooms in the rectangle. Finally, click Accept if you are in the Paint menu, Done if you are in the Multi menu. If, after defining a bedroom, you leave the bedroom unassigned, the next dwarf without a bedroom to sleep in the bed will claim it.

To assign the bed to a specific dwarf, create the bedroom as above, then hit {{k|z}}one, click your bedroom, the icon with a dwarf head and a plus sign, and choose a dwarf from the list. Dwarves who already have assigned beds will have "Has ''Quality'' Quarters" written below their name.

You can (re-)assign or free (unassign) a bed, even if a dwarf is sleeping in it at the time. The change in assignment will take effect when they wake up. Each bed can only be assigned to one dwarf at a time, however, it is possible for one dwarf to be assigned to multiple beds. If, after you assign a dwarf their bed, you see two dwarves listed, don't panic - it's okay, they're [[marriage|married]], and will share that bed. Married dwarves can sleep in the same bed at the same time (along with all 34 war dogs assigned to them).
[[File:bed_preview.png|thumb|300px|center|Not good enough for a noble.]]
==See also==
*[[Bedroom design]]

{{Translation
| dwarven = zust
| elvish = sira
| goblin = zozax
| human = ina
}}
{{Buildings}}
{{Category|Furniture|Bed}}