User talk:VengefulDonut

Welcome to this wiki! Dwarf Fortress rapidly becomes more complicated, and we're always glad to have new writers.
Since you should try to follow wiki standards, and you probably don't know ours yet, we've made a list of basic guidelines. Note that this is a template, not a customized message for you.

• To tell us who you are when you talk, please sign your posts on discussion pages by typing --~~~~ after your posts. This can also be inserted with the button if JavaScript is enabled.
• Don't put a question mark in the title of a page. Question marks mess things up, and your page will be moved to a different name.
• When making comments on a talk page, use one more colon before each line in your comment than was used in the comment you reply to. In general, put exactly one empty line between comments by different users but do not use blank lines inside of a comment.
• Avoid making many small edits to a page. Instead, try to make one large edit. This makes the history of the page a lot easier to read.
• Don't edit the user page of another user. If you want to tell them something, add the comment to their talk page.
• If you put a comment at the bottom of a talk page with section headers, you've probably put it in a section. Putting things in the wrong sections is confusing. You can create a section!
• Generally, read and follow the rules. They're like a little constitution, except not boring! Really, read them.

"You have been processed! Go forth, now, and edit!" --Savok

Extension request

Ok, I'll see about getting all three of those installed this weekend then. Briess 14:52, 16 September 2009 (UTC)

All three of the extensions you listed seem to either cause PHP to die a horrible death or are incompatible with ParserFunctions. Are there any other extensions that fulfill the same purpose? I'll look into what I can do to make the extensions you listed work, but I'm no PHP guru. --Briess 01:10, 27 September 2009 (UTC)

After an extreme period of laziness, I would like to direct your attention to Special:Version (I installed the extension you requested. Sorry about the delay :V) --Briess 11:49, 8 October 2009 (UTC)

I'll look into what I need to do to update the number of regex evaluations first thing tomorrow morning. Any specific number you're looking for? --Briess 04:29, 11 November 2009 (UTC)

It's a bit more complex than I had hoped to increase the regex evaluations limit; I'll have to spend more time on this tomorrow to get it working. --Briess 03:22, 12 November 2009 (UTC)

I got several of the random limits increased that deal with this, but I'm possibly missing a few other random template limits that may later become an issue. If they do, just let me know. --Briess 06:47, 16 November 2009 (UTC)

Favicon

Hrm, ok. Do you happen to have a copy of the favicon image somewhere? I couldn't find it in the copy I received of the wiki. Briess 18:56, 17 September 2009 (UTC)

I don't think I had a valid favicon, I just had an empty file to remove all the 404 errors. --Senso 14:13, 18 September 2009 (UTC)

Internal Error when submitting screenshot

Hey Donut, I saw your name on the screenshot template page so I hope you're the right person to talk to! When I try to upload an image, I'm getting an Internal Error reading "The upload directory (public) is not writable by the webserver." What do I do? --KenboCalrissian 13:31, 18 September 2009 (UTC)

Briess is the new server admin. --Senso 14:14, 18 September 2009 (UTC)

Russian Interwiki

Do you happen to have the webserver address for the russian wiki? I wasn't able to recover that from the db dumps when I took over the wiki, unfortunately. --Briess 06:35, 16 November 2009 (UTC)

RE: Ads

You might be interested in looking into Firefox and AdBlockPlus. Had no idea the new host even had ads on the pages until I noticed your post in the current events. (After coming from a very long forced vacation, admittedly.) -Edward 21:42, 25 February 2010 (UTC)

Wagn

Other than server maintainability (I'll be able to drop the PHP stack on the dfwiki backend server); the big three are:

• Uptime. I'm sick (and I'm sure others are sick of it too) of getting an email at 3:30 in the morning from the server saying that PHP has crashed. Again. because of one of many known mediawiki bugs.
• Wagn offers much more extensive inter relational features for articles (cards).
• End users can directly modify HTML for layouts and looks of pages.

--Briess 20:38, 27 February 2010 (UTC)

Dwarf Fortress Wiki:Versions

Based on your comments and input on the administration requests pages I thought you might be interested in this kind of discussion. Please bring in your comments on this page and on it's talk page and let everyone know what you think. Thanks! Mason11987 20:46, 28 February 2010 (UTC)

== What about {{version}}? ==

Did you have something like this in mind? category:version template:version (: VengefulDonut 21:32, 28 February 2010 (UTC)

I did see that before and I think that's awesome as notes about particular items in an article, but it doesn't quite bring us to the two goals I hoped for here. It informs users about a statement but because of the difficulty (and undesirability) of labeling every statement in an article I think a single template per article can bring something different to the table. I hope you don't mind but I copied your comment and my response to the versions talk page so others can contribute to this and expand on it. Mason11987 ^(T-C) 21:38, 28 February 2010 (UTC)

Could you drop by and comment on "consensus" again? [1] Mason ^(T-C) 00:32, 8 March 2010 (UTC)

Right, but the goal as I understood it is to maintain a persistent archive of old material, which would require a copy of every page as eventually something will be affected. As per the double redirect situation, I'll be working on that tonight. --Briess 02:12, 8 March 2010 (UTC)

Unfortunately, no, there's no way for me to just copy the pages. I figure that we move everything to 40d, have the main namespace redirect there, and once we have to edit an article, edit the redirect to become an article again. Eventually, every article will probably be edited in some way, shape, or form and thus will need to be moved out anyways. --Briess 02:16, 8 March 2010 (UTC)

Doing so greatly increases the server resources required to serve up both wikis. This only increases disk space usage, which is nearly limitless. --Briess 02:21, 8 March 2010 (UTC)

Re: Category:Creatures : awwww, fuck. --Briess 23:05, 8 March 2010 (UTC)

Slightly Annoyed

Being a furry is not "who you are". It's an association people make by choice. Unlike race and gender, it's not genetically coded into you. 
Unlike religion, it's not fueled by deep rooted conviction. It's an arbitrary and ultimately meaningless label that people can choose either to attach 
or not attach to themselves on a whim. VengefulDonut 00:11, 1 March 2010 (UTC)

Considering the application has been accepted, and my responding to you there would break the conversation on that page, I'll respond here. (A little late, I suppose) "Who you are" is defined by a LOT more than just the genetic coding that went into making you. Your personality and opinions are shaped by the actions of your environment upon you as you develop. (Your environment includes other people) A person, who they are, is defined by their actions. I am an artist, not because my blood says I am, but because I got bored in school and drew so much I just happened to get good at it and kept going. My brother is a musician because he likes women and music is good at attracting them, but he's become quite involved in the music scene itself, unrelated to his initial goal. "Who you are" is different from "What you are". --Kydo 14:10, 5 March 2010 (UTC)

I will allow your definition of terms. In this context, my argument would become that discrimination based on "who you are" rather than "what you are" is acceptable.

You didn't even have do all that work to make me allow that. I will use words with whatever meaning you want the words to have, as long as we both know what the meaning is. If necessary, I can just make up a new word to fill the gap of the word you redefined. (: VengefulDonut 01:12, 6 March 2010 (UTC)

Actually, this is a pretty basic concept at the moment, dude. The whole nature versus nurture issue of what defines us as people. It's part of that weird overlap between experimental psychology and philosophy. These days most people pretty much agree that who you grow up to become is heavily influenced by your experiences in life, with genetics only holding a foundation which defines how you are most likely to react to certain things at a face value. Like, disliking certain flavors is caused by how your brain processes that information, not your experiences. --Kydo 13:54, 6 March 2010 (UTC)

Not what you know, but who you know...

But I can't remove {{mod}} from it because it's locked

Hey! Good catch - done. And any time see a need for something, absolutely, no problem, just lemme know. (I assume you didn't RA because of time/energy, obviously not b/c of qualification or interest.)--Albedo 20:29, 12 March 2010 (UTC)
btw - you don't think the Modding Guide deserves that category and warning template? I'd think that is the essence of what that's for, no?--Albedo 20:44, 12 March 2010 (UTC)

The article is about how to make mods, not about particular mods

Sure, but that template does more than label a mod as such. It does (at least) two other things that are directly related - first, it's a (friendly) warning, which is not out of place on that page imo, and it also adds that page to the "modding" category, which is again approp. --Albedo 20:55, 15 March 2010 (UTC)

DF2010

"it feels good to spread it"? I'm "proud"?, Wow... haha. I named an article something succinct and people continue to use it. It isn't some ego high I get when I see other people use it as you seem to be suggesting, although I find that hilarious.

The reality is that people will put things in the wiki and they need to use SOME word/phrase/term to refer to the upcoming version of DF, and "The upcoming version of DF" doesn't exactly have the kind of ring to it that people would use. Having them all use the same name for it makes it substantially easier to search for and update then thousands of phrases like "the next version", "post-40d" "the upcoming version", "the yet-to-be-released version". Basically people WILL make references to the next version in this wiki as long as information exists about it, and having them all use the same name (even if it isn't accurate) is certainly more helpful then everyone using whatever name they choose. I'm skeptical there will be another major release version (that we will have in it's own namespace) in 2010 anyways. Basically I disagree with your assessment of the harm I've done, and I disagree with your assessment that I get some kind of pleasure out of people using some random name, but I'm glad you took my joke on the versions talk page so seriously. Mason ^(T-C) 18:59, 15 March 2010 (UTC)

I re-read your memssage a few times and I suppose I could have taken it in a different manner and so I removed my last message. It appears that after your initial assumption about my intentions it was hard for me to AGF with regard to you.

I still disagree with your concern about the use of the name, and I disagree that we should encourage people not to use that name. A single name now is better then no name, and that one has already stuck. If we can replace it with the real name later then so be it but I don't think the use of the name should be cause for concern.

Re: Bot Edit Request

I was already planning to do that, the way I want to do it is just a little more involved than previous scripts. I want it to change them if they're non-namespace links, and then if the page has any red links after the change, to add {{Red link}} to the top, so that we have a nice way to find what redirect chains need to be fixed. It's the second half of this that's a little trickier than just going through and changing them. Emi 18:51, 2 April 2010 (UTC)

Article Names

Article names only with the first word capitalised? I'm assuming this is the rule you were quoting: "Naming: The titles of new pages should be singular nouns, with only the first word capitalized. Example: Screw pump, Metalsmith's forge, Gear assembly." The next sentence was "Exceptions are proper nouns and terms that are always plural." I am fully aware of this convention, and always attempt to follow it. The only articles I can think of where I capitalised more that the first word were proper nouns. --Eagle0600 01:17, 8 April 2010 (UTC)

Mineral template

Wow, that's neat. I just made one minor tweak to not make it list everything as "layers" since, well, only layer stones are layers. I'm not quite sure how those templates work, but it would probably suffice to have it only append "layers" if it's an ENVIRONMENT token (as opposed to ENVIRONMENT_SPEC which can be a layer stone, a large cluster, a vein, or even a small cluster). --Quietust 23:43, 9 April 2010 (UTC)

Hehehe. I was just considering whether to comment on your page about that same issue. I guess we're on the same page :) VengefulDonut 23:45, 9 April 2010 (UTC)

Just noticed that the environment links (i.e. stone types or layer types) aren't being reinterpreted into the current namespace. I'm not even going to try fixing the template, since it's highly likely I'd just break it. --Quietust 00:19, 10 April 2010 (UTC)

Ah. Oops. I'll nab that next. VengefulDonut 00:20, 10 April 2010 (UTC)

Aquifer Breach

Any word on getting part 5 up? I noticed it's still not up, but there's no info as to it getting remade/abandoned either. --Edward 14:11, 10 April 2010 (UTC)

Link format

I noticed your corrections to the trap design article. Is there a functional difference between the two methods of linking, or is just a cosmetic thing? The auto-format box uses brackets. If that is incorrect, I'd love to know so I can work within the system in the future. Thanks! JohnnyMadhouse 14:49, 13 April 2010 (UTC)

Thanks! I will keep that in mind in the future. JohnnyMadhouse 15:14, 13 April 2010 (UTC)

The Raw Templates

These raw templates seem to be quite versatile, automatically adapting to changes. I was thinking that it might also be nice for them to support previous versions, if only to easily improve the consistency of pages in the 40d namespace and also simplify importing 23a data (for the stuff that's actually in the raws, anyways). Given that older versions used different raw filenames (and the fact that some raws, such as Creatures, are split across multiple files), it might be useful to choose some reserved page names that will contain all of the relevant raws from a particular version, whether by copy/paste or by transcluding each individual raw file from its own page (assuming that won't cause its own problems). Opinions? --Quietust 18:01, 15 April 2010 (UTC)

Material inclusions for the stone infobox template

The infoboxes for stone types, in the old version's wiki pages, included what minerals/gems could be found within that stone. Would it be possible to add this functionality for the new templates? I know it's less straightforward than the material properties, but I imagine it could still be automated. G-Flex 03:20, 21 April 2010 (UTC)

Yes. That is next on my list, time permitting. VengefulDonut 12:46, 21 April 2010 (UTC)

Expletives uttered during development (IRC)

Yeah, sometimes stupid things happen. It seems I'm mostly cussing at myself for being stupid. --Briess 20:30, 21 April 2010 (UTC)

I'm workin on it >.> --Briess 22:31, 21 April 2010 (UTC)

Yeah, use irc.redwolfs.net to connect to newnet for now --Briess 22:34, 21 April 2010 (UTC)

BASIC_COLOR

Several layer stones, minerals, and gems use BASIC_COLOR so that the mined stone/gem appears in a different color. These particular stones are dacite, phyllite, gneiss, bismuthinite, stibnite, anhydrite, clear tourmaline, gray chalcedony, dendritic agate, shell opal, bone opal, and clear garnet. One minor annoyance is that while DISPLAY_COLOR specifies both foreground and background colors, BASIC_COLOR includes only the foreground color, so simply using one's value in place of the other won't work properly. The proper solution would be to only pass the "itemcolor" parameter to {{Mineral}} if a BASIC_COLOR token is present, but I don't quite recall the best way of doing that. --Quietust 16:30, 23 April 2010 (UTC)