Zelda Wiki:Discussion Center


 * Archive 1
 * Archive 2
 * Archive 3

Comment templates
So gradually we've been getting a lot of "comment" templates in articles, like "Navi's Comment" and "Tatl's Comment" etc. And I'm not here to complain about them, they're quite neat to have (and hell, I contributed most of the Fi ones). However, I notice we've now got templates for Midna, various manuals and even one for Nintendoland, so I want to propose that perhaps we form a standard for these templates. Right now, they are placed in different sections of various articles, and tend to mount up (take a look at Octorok to see what I mean).

Would it be worth having a new section devoted to these templates? Or even a new template altogether, that encompasses and displays all the current content in one? At the very least, I would think it's worth merging all the existing templates into one multi-purpose comment template (if we do it right, there would functionally be no difference, and it would allow for easy expansion in the future). --Dorsal Axe 22:22, 28 January 2013 (UTC)
 * Merging them sounds like a potential idea, but I'm not sure the best way of doing so. There's also the figure descriptions in TWW and TMC, too. 01:46, 30 January 2013 (UTC)


 * Whether it's or , I don't really see much of a difference. Why would standardizing these templates be worth editing  the 300+ pages they're used on? Also, if I understand it correctly, editing a piece of a heavily-used template as opposed to a separate, smaller one = bigger job queue = bigger server strain (I might be talking through my hat on that one, though).


 * But I do agree the comments could use a face-lift in terms of style. If anyone had any ideas on that front they'd be greatly appreciated. This isn't the first time we've talked about needing to change the darn things, but I don't remember hearing any suggestions as to what we could actually do to them (can't really think of any myself, at the moment). :P As for their placement, I don't particularly see a problem with them being placed differently as long as it's logical and justifiable. It does look pretty bad when they pile up like that, though. Perhaps a dedicated section would indeed be order in those cases. What would we call such a section, however? Hm...  02:16, 30 January 2013 (UTC)


 * What is the policy for enemy pages at the moment when it comes to covering different games? Some pages are split by game, others try to go for a more "general" approach. Personally I think the general approach is lacking and flawed, and find it much easier to organize and follow pages that refer to the enemy and how it changes from game to game. This would solve the issue that's being brought up here, because without dedicated sections in an article for specific games the templates have nowhere to go, and end up bunched up at the top. 01:04, 31 January 2013 (UTC)


 * Reorganizing these pages by game would be a big step backward since we spent a considerable amount of time and effort (and by "we" I mean Cipriano) reorganizing them into what Cip likes to call "a superior encyclopedic format." This "general" approach emphasizes in-universe writing, which in turn makes for a more engaging read. On the other hand, organizing them by game can often cause redundancy. A subject that spans several games always carry some similarities from one title to another.


 * There are pros and cons to either approach. If you ask me, the key is finding a balance between the two. Take the Link and Zelda articles for example. (Or the Soldier article, if I may be so bold). 22:57, 31 January 2013 (UTC)


 * Yes, a balance is vital, but I'm not necessarily sure it's our job to be TOO in-universe. I think the Hyrule Historia approach is best, stay relatively in-universe but don't be afraid to mention specific games, I mean, it's impossible NOT to mention them. I don't see the big deal of having sections covering what are effectively different "events" in the universe's history. I mean, pretending that Stalfos use either swords or maces when in fact they only use maces in ONE game (which is on ONE timeline) means the "general" approach is way too vague when you have a subject as universal and yet heavily varied as the Stalfos. Hyrule Historia doesn't pretend they're the same in each era, either. I guess I'm arguing for the same thing as you, I just don't see how having different subsections hurts that "feel" at all, it just organizes things. Not the best example because I'm not thinking in terms of timeline here, just release dates, but nobody would expect a history book to cover the changing history of a nation in a non-chronological manner. 00:36, 1 February 2013 (UTC)

Just an idea...for pages with multiple templates, why not use the tab template? It makes it less cluttered and allows us to save space. 02:01, 1 February 2013 (UTC)

The Dividing Line of Cheats and Glitches
A recent edit has come to my attention that claims that cheats/hacks and glitches are independent of one another, and thus anything involving cheating devices should not constitute as being a glitch. I disagree with this, though, and I think that even though it's initiated by a cheating device, you still can encounter glitches that would only be available under the influence of said devices; thus, it's only an issue of discerning what a glitch is (a malfunction), and even though it's by external means, the glitches likely aren't the intended result of the codes within the cheats as the latter are only meant to unlock certain abilities. These abilities simply open the range for which glitches may occur. I'd really like to hear what other people have to say about this, though. 07:49, 4 February 2013 (UTC)
 * I think a gltich is really defined as a game not behaving as intended. Using hacking or a cheat cartridge to cause strange things to occur isn't really glitching the game at all, because it's impossible on normal hardware. Numerous games are designed so that once you break the "laws" of the game you are suddenly able to witness a ton of things simply not working as intended. These are never fixed because no player would normally have access to them. For example, you can use cheat codes to access Master Hand in the original Smash Bros., but playing as Master Hand frequently causes errors. But these aren't really glitches because there's no way anyone would normally access this.
 * Think of it like breaking the fourth wall. A standard glitch breaks this fourth wall in normal game play, suddenly allowing you to see behind the "set" of the game. With a cheat device, you can just run around behind the set and look around and mess with things, but that isn't a glitch, that's just messing with the innards of a game and seeing what happens.
 * Stuff like the crooked cartridge is similar, but at least you don't have to have a cheat device to perform those glitches. I would still call those cheats rather than glitches, however, because it's not massively different, you have to go about it with a real aim to effectively break the game.
 * As for the glitch in question in the edit, that's definitely not a glitch. If you break the sequence of any game you can cause very similar things to occur. There would be like a billion examples. It's all to do with the way games are programmed. If you don't trigger certain "flags" or events, things won't activate, characters won't appear, etc., it's very normal behavior and often very intentional. 14:31, 4 February 2013 (UTC)
 * I'm inclined to agree. In fact, the other day I almost removed the very section in question myself. Using external tools to push a game beyond the limits of its intended design is not a true glitch by any definition. My understanding is that the purpose of these pages is to highlight exploits caused by flaws and oversights in the game's coding (like using the hookshot through other objects, missing collision, reusing consumable items etc.) It's definitely not a cheat, and I think Darkness simply said that for want of a better word. This is more like... breaking the game through hacking?
 * And I'd also agree that the Crooked Cartridge trick isn't really a glitch either, since that's not strictly an issue with the software. Let's face it: If you mess with the hardware, bad things are gonna happen. But it's an interesting sequence breaking trick nonetheless, I suppose. As for this one, it's neither a trick of any use, nor something anyone is going to ever come across without deliberately going out of their way to mess with the game. --Dorsal Axe 16:40, 4 February 2013 (UTC)

Finding Uncategorized Files
Hey all,

As you know, the FileInfo template can be used to categorize image files by game, among other things. This is great, because when you're looking for images from a certain game, there's a whole category devoted to them. But there are a LOT of files on this wiki that were uploaded before this template existed (or were not uploaded with it correctly implemented). These should be categorized by game for ease of access by the editors. Most of these files, however, still do not appear under the Special:UncategorizedFiles, because they're equipped with the (now obsolete) Copyright template, and are thus categorized under Copyright images, which is an extremely unhelpful category with over 14,000 entries.

So my question is this: Is there a way to disable the categorization of files with the Copyright template into the Copyright images category, at least temporarily, so that these files will show up in the Uncategorized Files? Or are there better options to find these images, so we can get to sorting? 00:21, 20 March 2013 (UTC)


 * I've actually brought this up before in the chat so I'm totally with you on this one. Right now Template:Copyright has two formats, the standalone format and the one used with FileInfo. It's as easy as splitting the two into separate templates and not having the FileInfo one add the "Copyrighted images" category (which we could probably do away with, it's not particularly useful as you said). 00:32, 20 March 2013 (UTC)
 * Maybe just make "Copyrighted images" a hidden category? I believe that if pages are only in a hidden category they show up on UncategorizedFiles. Not completely sure though as I have limited experience with them. -- Snorlax Monster  04:46, 23 March 2013 (UTC)

Massive Zelda Powerpoint
Hey there, I have been working on a extremely large power point over the past few weeks as a project of mine, however, with it reaching its finish, I will have to do something with it soon. And that is where Zelda Wiki comes in. I was wondering if I could have my power point uploaded to the wiki as a General Knowledge source for any Zelda fan who wants to learn more. The power point contains information on characters, items and much more.Once finished, it will need to be removed from my computer so I would like it to go on the Wiki. I would really like other people to have as much fun viewing it as i had making it. I would really appreciate it if you took the time to have a look, and maybe put it on the site and reply as soon as possible.

All my thanks
 * I think it would be better if you compared the information you collected with what is already in the wiki and change or add to the respective articles if they lack info :) Zeldafan1982 22:34, 20 March 2013 (UTC)
 * What Zeldafan said. Sadly, we cannot host a powerpoint with the MediaWiki software, and we already have pages for all the characters and whatnot. We'd be glad to have you share anything relevant that's not already on the pages, though! 16:54, 21 March 2013 (UTC)

Licensing overhaul
Alright, so lately we've been making a big effort to properly categorize our files, thanks to FileInfo. To that end, I have a few proposals for our image licensing policies, which doesn't really cover all the bases at the moment. Here they are:


 * Get rid of AV-Copyright: The same copyright laws and "fair use" doctrine apply to audio and images (to my knowledge), and since we have the type field now to distinguish sounds from images, there's no reason we can't just merge this into Copyright.


 * Get rid of Category:Copyrighted images: A category that lumps together over 90% of the wiki's files is of no particular use to anyone. At the very least, it should only be for miscellanious copyrighted files that aren't already categorized by game.


 * Get rid of WikimediaImage. This template's outdated since we have the "source" field to tell us where the file came from. I also think we should be properly licensing or images here, instead of just being lazy and sending readers to the source to find the image's status. This template would be superseded by the Public Domain template and a new copyleft/GDFL template (see below).


 * Fan Art = Derivative Work ≠ Every user-made work. It's getting to the point where almost any user-made work is getting categorized as fan art, when a lot of it isn't fan art at all. We need to establish that fan art =, that is, a piece of art depicting something copyrighted, like for exampe, a fan-made image of Link. Heavily edited images from any of the games (example) and images from fan games (example) would also count as fan art. Photographs most personal images are original works, not derivative works and therefore NOT fan art. Those works should be put under a copyleft license. Otherwise I think our fan art policies are fine, although we should probably mention that Nintendo holds some copyright as well as the author. Copyrights can be a little tricky for derivative works so I guess it's good to play it safe and always assume the author claims copyrights, and therefore require permission before use (with the exception of fan games, which I guess could be seen as fair use).


 * Have a (more specifically a GFDL) licensing template, like : For any image released under the GFDL (as many Wikimedia Foundation images are). This license also applies to personal works that are neither copyrighted nor public domain (with the exception of derivative works as mentioned above). Images that would apply to this license, which are currently getting lumped in with fan art as I said, would be photographs, signatures, and other such personal images,


 * Have a "not sure" option. Got this idea from Mario Wiki, pretty self-explanatory. This would be the default if no license was selected during the upload. If we're not going to force people to select a license, we need to have something that lets us know what files haven't been properly licensed.

So there you have it, guys. I don't know how many of you care for policy-writing, but since it's an essential part of the wiki it's only right that I brought it up here first. I have some stuff already written up here if we go through with it. Any thoughts on this are welcome. 20:47, 24 March 2013 (UTC)

PS: Maybe we should start categorizing fan art by game as well.


 * Everything you said sounds good with me, so I support.  01:10, 25 March 2013 (UTC)


 * The image you used as an example for "photographs" would be fan art, as costumes are technically a form of art, and therefore a fan costume would be fan art. Also, the problem with the "fan art" category could also be addressed by changing the name of the category/changing what the template says to allow for more files to be covered by that category. I brought up the problem here. Everything else looks fine, however, so I support. 01:28, 25 March 2013 (UTC)


 * This is the part of the reason why I brought this all up in the first place. And yes, it depends on how you interpret the word "Fan art", but in this context I'm saying Fan art should only be for derivative works because the legality of them is a little different than flat-out copyrighted, public domain, and copyleft works, and that's really the only reason to have a separate license for them in the first place. It's not even a proper license, which is why we should be tagging images with a clearer license (either copyright, public domain, or copyleft) whenever possible. That's why I'm proposing we change the Fan Art license to include less images as opposed to more.


 * I guess a photograph of someone dressed up as Hylia might be considered a derivative work, and some signatures too, if they have copyrighted material in them. Images such as File:Hee hee.jpg, however, are certainly not fan art nor derivative works. 01:58, 25 March 2013 (UTC)


 * I'm for all these changes. Especially the one about getting rid of the massive and unhelpful Category:Copyrighted images. :P 05:13, 25 March 2013 (UTC)


 * I agree, these suggestions are all great and we should work to getting them done sooner, rather than later. --Xizor 11:18, 27 March 2013 (UTC)
 * I agree with most of what you said: there is no need to give sound files different licenses, being from Wikipedia is not a license, Fan Art is not a license, there are several copyleft images hosted on ZW that should be correctly tagged, and an unknown license option would be good so that staff can figure out how the image should be licensed to ensure correct licensing.
 * I'd also like to see the abolition of Website; it is just as unclear as Template:Fan Art. For example, File:Bulbapedia.png was classified as fan art when it is actually copyrighted to Bulbagarden. Likewise, another license I think that should be added would be one indicating it is property of Zelda Wiki (e.g. for File:3dlogo.png) - perhaps ? Also, whether fan art is copyrighted or fair use is complex, but is discussed in detail here; cosplay is discussed here.
 * Also, I think it would be best to specify the specific license rather than just "Copyleft" (and this could be particularly problematic if Creative Commons images are permitted, and I think they should be). Also, I think it would be best to specify the version number of the license too, but I understand if you want to keep it simple.
 * In regards to using images from Wikipedia, apparently dual licensing means that when re-using it you get to chose which one you want to use. So currently that would be GFDL, when applicable.
 * Also, I suggest adding the file type of "photograph". While game content is unlikely to considered this, merchandise and the games themselves, as well as cosplays, will fall into this category.
 * Also, I really think the link at the bottom of every page should be to Zelda Wiki:GNU Free Documentation License not the Wikipedia page. -- Snorlax Monster  02:21, 3 April 2013 (UTC)


 * Yeah, Template:Website could be replaced with Copyright, and in some cases copyleft. Having a template for ZW copyrights might be a good idea, though I can't imagine it would be used for more than a handful of images. We should probably leave it off the upload form for that reason. A Creative Commons license sounds fine, although I think we should only use it when we need to and leave the GFDL as our principal copyleft license. We also may or may not want to put that one on the upload form for the sake of keeping it simple, since very few of our images seem to require a CC license at the moment.


 * A "photographs" type might be useful. For those who aren't on the Skype chat, a "personal image" type has also been suggested for the various user images that don't have any use in the mainspace. This would solve the problem of having to sort out these miscellaneous images. "Printed Media" has also been suggested as a replacement for "Scans". This type would cover scans of all manga, comics, manuals, and other books, as well as cover art (including box art).


 * Well, I think we've covered just about everything we need to for now. Time to move forward with this, I think, unless anyone has something else to add. 21:44, 5 April 2013 (UTC)

Alright, I've made the corresponding changes to FileInfo and the upload form, and added some new guidelines. Please let me know if I've missed anything. Now we come to the hard part: categorizing everything! 20:09, 27 April 2013 (UTC)

Oh, and the copyrighted images category is now limited to the pages that just use the Copyright template instead of FileInfo. So you can use that to see which files still need to be properly categorized by game and type. 21:50, 27 April 2013 (UTC)

New Page Suggestion: Enemy HP
Considering that there is already a page based around Weapon Strength, I'd like to propose another page similar that depicts the various number of 'Hit Points' required to defeat the multitude of enemies in Zelda. The health is simply calculated by the amount of hits the enemy takes and the strength of the weapon used i.e. it takes 10 hits from the Biggoron's Sword, 20 hits from the Master Sword (40 hits from the Kokiri Sword) equalling 40 hit points. Completing an article with all the enemies of Zelda's HP would result in quite a large page, however another suggestion brought by Hylian King is to add an extra section within the Enemy infobox that incorporates the HP in the existing enemy pages. Thoughts? --Smighty 07:42, 10 April 2013 (UTC)
 * I must say that I quite like the sound of the second suggestion. Having a large page showing the HP of every single enemy in the entire series would be excessive if we're simply able to place the information on their individual pages. I feel that having the values within the individual infoboxes would be far more useful and practical. However, how would go about defining "1 hit." Looking at the Weapon Strength page, and using as an example, I believe that it would make the most sense if we were to either base it around the weakest sword (i.e. the Recruit's Sword) or the weakest weapon (i.e. the Whip). By this I mean that 1 hit point would be equal to one hit from the Recruit's Sword and two from the Whip, or one from the Whip and a half from the Recruit's Sword. Personally, I prefer the latter method: whatever the weakest object, item or weapon in the game is, (even if it isn't a sword) one hit from it would be equal to one hit point. So long as we can agree on the definition of a "hit," I don't see why we can't do this.  10:09, 10 April 2013 (UTC)


 * I like the notion, but this is something that's going to be much easier said than done.


 * The information that is of use to readers is how much hits it takes to kill an enemy with any given weapon. To make them understand that from a single HP value based on, say, the number of hits from the first sword, they need to understand the Weapon Strength. As such, we have to make the Weapon Strength stats readily available with every mention of HP. I can only vaguely think of how we're going to do that. Ideas, anyone?


 * Another issue is getting readers to understand our point of reference in the first place. A number in an infobox is not going to mean anything to anyone. We have to somehow make it plain to see that the stat equals the number of hits it takes to kill the enemy with the most basic sword (or however we decide to define a "hit", though I would recommend the weakest sword because that's how the Weapon Strength page is organized for the most part).


 * Thirdly, we need to figure out how to deal with enemies that appear in several games. I would suggest that for pages such as Moblin we have an entire section dedicated to HP, and provide a link to that section in the infobox, so as to not overload the latter.


 * So there's a few issues we need to address if this is going to work. 12:04, 10 April 2013 (UTC)


 * Here's my take. If we add the HP to the infobox, we need to add a link which takes the user to the weapon strength page. Perhaps we do an asterisk (*) and then at the bottom of the infobox provide a link saying "See how HP is calculated: Weapon Strength." My point is that if we just flat out list an HP value, people are going to go "Wait, where did they get that?" There has to be some form of clarification. Don't get me wrong, though, I still think it's a good idea. We just need to be very clear with it. 12:38, 10 April 2013 (UTC)


 * I think we should continue in the same scheme as the Weapon Strength page and follow with the weakest sword’s rating as a “Hit” Point. It would be most understandable for the readers if we went with what Justin said and linked the Weapon Strength page to the stat. However it is not required to use the weakest weapon to determine the Hit Points of an enemy as the weapon strength has already been well established on this Wiki, for example:

2 hits from Kokiri = 1 Master, 2 hits from Master = 1 Biggoron/Giant’s So, if you kill something with 4 hits from the Biggoron then that’s 8 from Master and 16 from Kokiti = 16 Hit points altogether. Divide Biggoron's by 4. OoT is my example because it is what I'm MOST familiar with, I understand there will be complications for other weaponry within various Zelda titles such as Spirit Tracks.


 * Some enemies may propose a strategical combat issue if the HP is to be included into the Enemies’ existing Info box. Then, some enemies of the same kind might require two separate HP stats by the method of killing, for example:

The Deku Baba can be cut down with one swing of the Kokiri Sword (The weakest sword of OoT) while in stalk stance (creating Deku Stick), however to attack while it is lunging requires two swings (creating Deku Nut). Does this suggest the Small Deku Baba has 2 HP, and the stalk is merely a weak point?
 * Perhaps the Strategy Section or the Overview should contain the details of their variations and the Enemy Infobox should contain their direct suspected HP. Obviously, what we're trying to establish as HP is simply what the programmers had hidden in the coding: How many hits to defeat, and by extension, with what? Zelda isn't some math driven RPG, but to give any kind realistic combat system there must have been enemy HP for all expected opponents.
 * Another, easier solution is to merely have a HP stat for Bosses. Only issue is with some like Gohma who are all in the one page and the best way to not clutter said page is using what HK said and create another page containing their HP. --Smighty 23:21, 12 April 2013 (UTC)

I've thought about this before, but it's REALLY difficult to do for most games, since, as mentioned, different weapons to different damage. The Japanese guide for A Link to the Past has an HP damage listing for every weapon type, for example, rather than a single number. Even the swords are inconsistent. Without having a big infobox increase or some kind of... very complex table hidden in a drop down, the only game that would really fit into a simple HP listing would be Zelda II, since that game has basic damage information that doesn't vary on method of attack.

An alternate thing that would be easier to add would be the damage CAUSED by an enemy. This is usually much simpler, as most enemies only have one attack, and the heart damage doesn't vary too wildly from game to game. 12:49, 15 April 2013 (UTC)


 * That's not a bad idea, and as you said, it would be much easier to implement. However, I still think that both ideas could work if we just do them correctly. Taking both ideas into account, I've come up with the following solutions:
 * Include a section in the infobox containing the enemy's HP. If the enemy has appeared in three games or less, then all the values could be located in the infobox. If the enemy appears in more than three games, then the infobox would contain the HP value in its most recent appearance. There would also be a note here linking to the Weapon Strength article (as Justin suggested). There could also be a tooltip saying something like "based on the number of hits from the standard Sword."
 * For enemies appearing in more than three games, include a section within the article listing the enemy's HP in older appearances. This could possibly come in the form of a table, which would also link to the Weapon Strength article, and be a subsection of "Weaknesses," or a separate section altogether, like HK suggested.
 * Include a section in the infobox listing the enemy's attack power.
 * For bosses or enemies with multiple attacks, include a section within the article listing all of the enemy's attacks, as well as their power. This could come in the form of a table, like the HP, and be located in either the "Strategy" heading or its own separate section.
 * For enemy articles arranged by game, and with a different attack power in each game, a single table would be used (similar to the HP table), listing the attack power in each game.
 * As Smighty mentioned, any exceptions to the standard HP (such as Deku Babas' weak stalks) would be noted under the "Weaknesses" heading.
 * Obviously these are just some rough ideas, but I think they could work if expanded upon. 19:51, 15 April 2013 (UTC)

That's some great stuff, let's start by narrowing down on how to exhibit enemy attacks and their strength. Danny mentioned a graph containing to ALL of an enemies attacks, thought I might knock something up as an example:
 * {| class="wikitable sortable"

! One Handed Attacks ! Damage ! Type ! Additional Effects !Two Handed Moves !Scripted Attacks (Hands stunned) If we were to keep the graph smaller, because generally it wouldn't need to be this large, would we state simply their maximum and minimum damage, or is this preferable? --Smighty 11:41, 18 April 2013 (UTC)
 * +Bongo Bongo's Attacks
 * Sweep
 * -1 Heart
 * On contact
 * Punch
 * -1 Heart
 * On contact
 * Downward Slap
 * -2 Heart
 * On contact
 * Throw
 * -2 Heart
 * On grapple
 * Throws Link
 * Crush
 * -2 Heart
 * On grapple
 * -1/2 heart while grappled
 * Crush
 * -2 Heart
 * On grapple
 * -1/2 heart while grappled
 * -1/2 heart while grappled
 * Clap
 * -2 Heart
 * On contact
 * On contact
 * Charge
 * -3 Heart
 * On contact
 * }
 * }

Adding pdf files?
I was recently working on a page for The Legend of Zelda: A Link to the Past Nintendo Player's Guide, and I was wondering if it would be possible to have the pdf file of the guide available on the wiki. The reasoning behind this is because it was originally offered for free on Nintendo's own Zelda website, so it's effectively public domain. This also applies to the Link's Awakening guide, and two smaller sections from another guide for the NES games. At the moment I don't think pdfs can be uploaded at all, but I really think these wouldn't be a bad thing to have on the wiki. 12:56, 15 April 2013 (UTC)
 * I'm not going to comment on if allowing PDFs is a good idea or not right now, but I just what to correct you on a factual error. Just because you give something away for free doesn't make it Public Domain; you can do that and have it still be completely copyrighted (although typically you would use a free license like GFDL or Creative Commons to encourage redistribution while still maintaining rights to it). Also, it's entirely possible to just convert PDFs to another file type if you want to upload them.
 * On a related note, I have the PDF for The Legend of Zelda Game Watch which is only two pages, and if people want it I'm happy to upload it. -- Snorlax Monster  14:49, 15 April 2013 (UTC)
 * Oh, okay, my terminology was wrong, but basically Nintendo has given it away for free, so I don't think there's anything illegal about the pdf files in this instance. 16:51, 15 April 2013 (UTC)
 * I'm no expert on Copyright law, but I don't believe that using the guides would be illegal so long as we used the same format as all of our other Copyrighted files. As for the PDF idea, I think it's good. I'm curious as to how the files would be uploaded though. What file formats are there that could be used? Other than that, the only issue I can see is file size. So long as the files aren't excessively large, it makes sense for them to be uploaded. They're useful, informative, and would make it much easier for editors to find references and scans if necessary. Furthermore, this idea isn't just limited to Strategy Guides, and could be expanded to incorporate other things in the future. 19:51, 15 April 2013 (UTC)
 * Well, ideally if we could upload pdfs that would be fine since that covers most of these things, but it would also be possible to zip them up if that cannot be done. I've seen other wikis offer zips but I'm not sure if the wiki we have supports it or not, so... at the moment, none of the offered formats would work, obviously. pdfs or a zip format would be ideal (preferably both). Nintendo have offered The Minish Cap manual for download as a pdf on their site, so we could have that here too. Zips could be used for other things, but not entirely sure what exactly. Perhaps things that were once offered on Zelda websites, such as wallpapers and icons, but that's far less important. They'd have to be monitored carefully, however, I think it should be limited to higher level users, because it could be open to abuse from, well, you know, the usual. 00:59, 16 April 2013 (UTC)

It is possible to enable PDF downloads on a wiki. This extension provides a side-by-side layout of the pages. an example of it in use.

Uploading an entire book is not exactly the same as uploading an image of, say, Skyloft. Having a Skyloft image here for all to see doesn't prevent Nintendo from selling Skyward Sword (it promotes sales of the product if anything). Since we're using that image for educational purposes and not for profit, we can easily call that fair use of Nintendo's copyright. Distributing an entire published work is different, because you're preventing the sale of that product by making it freely available to anyone.

I'm no expert on copyright laws, either, but I'm pretty sure uploading the entire guide is still technically illegal. Zelda.com had the right to make it available for free because it's their copyright. We do not have that right; just because it was free at some point doesn't mean it's free for us to distribute, even if the book is long out of print.

It would be nice to have this resource available on the wiki, and I'd imagine the likelihood of us getting sued by Nintendo for this are slim to none. However, I personally don't think it's worth taking on the liability. Anyone who wants the guide can easily find it on their own. Same goes for manuals, although I guess they're a little different. We'd probably have a better chance calling that fair use since Nintendo doesn't sell them. They do distribute some of them for free here. Perhaps if we referred people to that site for those manuals, then uploaded the rest ourselves... 11:37, 16 April 2013 (UTC)

Names Template Meaning Field
Something that's been a bit of an issue recently has been whether or not to include the English translations in the Meaning field of the Names Template when the foreign name is the equivalent of the English one. I think we should get this issue out of the way before it gets too out of hand. So, what does everyone think we should do? Personally, I feel like we should follow the example of other wikis and at least state that it's the same as the English one ("Same as English" would suffice). I feel that leaving it blank just looks...unfinished, and that it almost begs the reader to fill it. 02:28, 8 July 2013 (UTC)


 * Sounds good... My only concern is that when all or most of the foreign names are equivalents of the NoA name, which happens quite frequently, we would end up with something like this:


 * It's functional, but also very repetitive and inelegant. Perhaps we can add another parameter that defines the meaning for all the languages, so we'd only have one "Same as English" spanning the entire table. If even one name is different, though, it throws a wrench in the works.


 * Also, we should have some way of identifying which pages have "meanings" fields that need to be filled. We'll get more help from translators if they know where to look. I'm thinking we should have it so that the Names template adds a page to a "Articles Requiring Translations" category whenever a meanings field is left blank.


 * I think both ideas are really good. Addressing the issue with the former: if a different name breaks the format, could we not just end that there and continue following the break? (An XXYXX format to show that two bear "Same as English," then the discrepancy, then another set of two.) 22:46, 8 July 2013 (UTC)


 * Yeah, definitely. That may prove difficult to implement, though. 22:56, 8 July 2013 (UTC)


 * I'm not big on the idea, just because the English translations would be the same as the page most of the time. I'm not really opposed to it, considering that I don't really do translations, but I just think it's excessive. Just wanted to put in my two cents. Feel free to disregard me if you really want to do it. 23:43, 9 July 2013 (UTC)

References for all pronunciations
So, anyone who has been watching my recent edits has probably figured out I like references a lot, particularly for dates. Since there has been a recent focus on pronunciations, I propose that all pronunciations be referenced or removed. Without an official source indicating the correct pronunciation of a word, our guess at its pronunciation is no more useful than the reader's guess based on the spelling of the word. Many pronunciations would simply come from commercials, some from developer interviews, some from in-game voice acting (SSB series mostly), etc. -- Snorlax Monster  17:05, 17 July 2013 (UTC)


 * I support this idea, for the simple fact that I pronounced Triforce as "Trihfuhs" until I finally noticed the "r" at about age 13, and I still didn't want to call it "Triforce." That, plus I called Vaati "Vayti" until I figured out that I was wrong. It's easy for someone to think that they are correct when they really aren't. References help to eliminate the doubt. 12:39, 18 July 2013 (UTC)


 * Sounds good, though I believe the Japanese names may also indicate how a name should be pronounced? 15:57, 21 July 2013 (UTC)
 * On one hand, yes; on the other hand, sometimes the English names are spelled the same as the Japanese names and pronounced completely differently. -- Snorlax Monster  16:29, 21 July 2013 (UTC)

The Spoiler Template
Hello, everyone! I'm here with a proposal that is being set force by several staff members. However, we feel that it is in the best interest of the wiki to allow the community to decide our course of action, so here we go.

It has been proposed that we eliminate the spoiler template, as spoilers should be implied in any encyclopedia. I have offered an alternative, saying that we could create a sitenotice (like the one you can see right now at the top of all pages which directs you to this very discussion) that states something along the lines of "We are an encyclopedia, and pages are bound to contain spoilers. Read at your own risk," or simply make a statement on the front page (which I do not recommend, because our Google Analytics shows that most of our viewers find us and read just the page they're looking for before they leave). In the end, it is ultimately up to all of you. Feel free to put forth suggestions, questions, opinions, etc. We look forward to your input! 11:41, 12 August 2013 (UTC)
 * I think spoilers are implied by being an encyclopedia, yes. IMO make the default sitenotice a spoiler warning, but if there's something important to go in there (e.g. discussing whether we should have spoiler template) I don't think we need to worry about having it there that much. -- Snorlax Monster  12:50, 12 August 2013 (UTC)
 * I agree with Justin's proposal. Spoilers should be expected in a wiki anyway. Zeldafan1982 13:48, 12 August 2013 (UTC)

I agree,but what about people who have never been to a wiki before? Barr1213 16:50, 12 August 2013 (UTC)
 * That would be the purpose of the sitenotice, Barr.
 * The template appears on a fraction of the pages that could be considered "spoilerific." There's no point in keeping it if we use it arbitrarily. Also, what exactly constitutes a significant spoiler is subjective, so it's much easier to just have a general sitenotice instead. We could reinstate the old one we had for spoilers a few years back. I find it's pretty clever. 18:58, 12 August 2013 (UTC)
 * I also agree. Basically every page on this wiki has spoilers. For example, the Epona page says you can talk to Epona as a minish. I didn't know that before I read the page so technically it was "spoiled". It would be pointless to keep the template when it would need to be put on almost every page. --Planetbox 14:53, 13 August 2013 (UTC)
 * @Planetbox I don't think that that's the best example. Spoilers are typically something that refer to a part of the plot. Like it would be a spoiler to reveal that Ganondorf dies at the end of Twilight Princess. Or a spoiler to reveal that Beast Ganon is the final boss of Ocarina of Time. Talking to Epona as a Minish is more of a fun fact. Nutter! (talk) 03:53, 6 September 2013 (UTC)
 * I agree with this. It would be very difficult and laborious to isolate every single potential spoiler on the wiki using the template, and attempting to separate spoilers into distinct sections would likely disrupt the flow and quality of writing. As others have mentioned, this is an encyclopedia, and spoilers are to be expected. Furthermore, as HK said, what makes a spoiler is down to personal opinion, so it would be substantially difficult to decide whether or not something is a spoiler on a case-by-case basis, and it would be much simpler to incorporate a general sitenotice instead. 08:25, 14 August 2013 (UTC)


 * Just want to add that this was not my proposal. I simply put it forth on behalf of the staff who suggested it, since I'm quite active and all that. Yeah, we respect each other like that. I actually don't want to get rid of the template, but I'm open to change because they make valid points. We did use to have a sitenotice about spoilers, and I wouldn't mind reverting to that. Granted, we could also make an "anonnotice," which is a sitenotice that only displays for anonymous editors. I think our users know full well that we have spoilers all over the place, so an anonnotice would work wonders. Plus, if necessary, we can change the sitenotice whenever something important happens (like this discussion). Just some food for thought. 16:15, 14 August 2013 (UTC)

Not a regular here, but I'll add that spoiler templates on wikis are generally pointless. The mere existance of articles like Demise is a spoiler and you can't do anything about that, and that's the kind of things that would be most important to keep hidden.

Incidentally, this is the biggest NIWA wiki that still currently uses spoiler templates, I think. Toomai 22:26, 17 August 2013 (UTC)


 * I don't think that getting rid of the spoiler template would be a problem, like most of you have already said: It's a wiki and everyone knows it's bound to have spoilers. So I'll support removing it if everyone's on board with that idea. But, at the same time, I don't see that keeping the template is causing much of a problem either. (EDIT: maybe we should bring this down to a vote?)  14:08, 18 August 2013 (UTC)

It is pointless. If somebody is looking for something, then they are probably seeking out spoilers. If we remove it then some of the more rule conscious users will focus less on using the template and more on editing the wiki.The DJ (talk) 03:03, 21 August 2013 (UTC)

We could put the disclaimer of "read at your own risk", and if something important comes up, we could put it under a linebreak of some sort.

Voting
Okay, guys, at this point, I think we should open up a poll for the future of the template. I'll provide options based on what we've discussed here. Feel free to place your vote in the appropriate section. 11:28, 2 September 2013 (UTC)

If you'd like to remove the template, please place your vote here, stating a short reason why. Please place a hashtag (#) in front of your post to automatically number them.


 * 1) I suppose removing it wouldn't be so awful. We can always opt for the anonnotice to warn anonymous readers about spoilers, anyway. 11:28, 2 September 2013 (UTC)
 * 2) I think spoilers are implied by being an encyclopedia. Everything is a spoiler, and just labeling some things as spoilers is unnecessary. -- Snorlax Monster  11:54, 2 September 2013 (UTC)
 * 3) Given how differently the articles are written, you cannot hope to efficiently contain every single spoiler inside the template, so I think a site-wide notification would be considerably more effective. 14:16, 2 September 2013 (UTC)
 * 4) A wiki by nature contains spoilers so, indeed, it seems unnecessary. Having a general notification should be enough. If a reader doesn't want to read info about certain games all he/she has to do is check the infobox and skip the articles for those games. Zeldafan1982 (talk) 15:01, 2 September 2013 (UTC)
 * 5) Again, the people that look up the Wiki are probably looking for spoilers, and those that edit the Wiki without the template will not have it to distract them from actually editing the Wiki.The DJ (talk) 03:04, 6 September 2013 (UTC)
 * 6) Per DJ. Plus, Mario Wiki and Bulbapedia don't say ANYTHING about spoilers (at least not that I've seen) and they, alongside this, are the biggest NIWA Wikis- so why are we still doing it? Overall, support. Nutter! (talk) 03:37, 6 September 2013 (UTC)
 * 7) As I mentioned before, any page can have spoilers, even stuff like the Epona page or the Ordon Pumpkin page. If we're going to keep the template, we shouldn't put it on every page if we could just put it on the whole wiki (if that makes sense). --Planetbox (talk) 19:47, 8 September 2013 (UTC)

If you'd like to keep the template, please place your vote here, stating a short reason why. Please place a hashtag (#) in front of your post to automatically number them.


 * I just wanted to make a response to Nutter regarding the other NIWA wikis. While we are a part of NIWA, the biggest part of NIWA is and always has been its policy of total freedom within its members. Yes, I do believe we should eliminate the template, but not simply because other NIWA wikis don't use it. I take great pride in our independence, and I don't believe we should do anything simply because another site does it. I just wanted to put this out there. 09:11, 6 September 2013 (UTC)


 * (@Nutter) Bulbapedia does have a spoiler template (something I hope to attempt to eradicate after this is settled, citing the ease it was done here as precedent). Being a staff member on both sites let's me use the other as a case study for things I want done but may be resisted :P. -- Snorlax Monster  10:51, 6 September 2013 (UTC)

Alternatives
Okay, so it looks like we're generally all for getting rid of the template. I'd like to ask you now, what would you like to do? Should we create an anonnotice (sitenotice to anonymous users only) that states that we have spoilers? Should put a warning on the front page? Should we just drop it altogether? Those seem to be the three proposed options. Let's find out what you guys want to do. This will be our final voting before we put the changes into effect. 18:12, 13 September 2013 (UTC)


 * Anonymous Users Notice
 * This will create a sitenotice for logged out users only which warns of spoilers.


 * 1) This was my suggestion, and I stand by it. 18:12, 13 September 2013 (UTC)
 * 2) Zeldafan1982 (talk) 18:45, 13 September 2013 (UTC)


 * Main Page Warning
 * This will place something on the main page stating that we contain spoilers.

I just want to comment that according to our statistics, half of our viewers find the page they want via search engines and never even visit the main page. I feel that this method is ineffective as such. 18:12, 13 September 2013 (UTC)


 * Drop Entirely
 * Give users no warning of spoilers.

Animals Infobox
Currently there isn't an infobox for the animals. The problem is that the one that is being used places them automatically in the People category. In some cases this is ok (with Christine for example). In other cases though (e.g. Epona, Walrus, Crimson Loftwing) it is clearly wrong. There are three options: a) The category can be suppressed (example). The problem here is that the field races is in use whereas a species field would be better. b) Same as above except that the field changes from Races to Races / Species or an additional Species field is added and c) A separate template/infobox for animals. Personally I prefer the latter. Zeldafan1982 (talk) 17:09, 27 August 2013 (UTC)

Enemies category
As it is, the enemies are categorized by game but not by type (except for the Octo Family). There are of course the (really awesome) enemy templates but I think it would be nice if there were categories as well. I think the bosses can be included there since they are enemies. Also, since this would clutter the sub-categories section, all the sub-categories that will be created can be placed under one category which will be of course under the enemies category. What do you think? Zeldafan1982 (talk) 17:09, 27 August 2013 (UTC)

Policy of user pages
Since I'm relatively new at this wiki, I want to make sure that my efforts are all...kosher, so to say. Is there a specific policy on user page content? I'm thinking of possibly starting a fanon English pronunciation project as a user page &mdash; and not all my own guesses (though I can start with my own), but also taking input from the community and presenting multiple alternative pronunciations different people may prefer. Something in a list format, perhaps like: (Some of these are mine, and some of them are alternatives I imagine others might be using, but I wouldn't know for sure without asking or being told.) And sorted semi-alphabetically (as well as IPA can be sorted, anyway). It's not meant to favor official pronunciations, even if they're confirmed one way or another. Gamers can be very peculiar with how they pronounce stuff in their head, and it's fun to gather the different possibilities &mdash; no reasonably explainable pronunciation would be excluded. - Dermot Mac Flannchaidh (talk) 11:57, 2 September 2013 (UTC)
 * Ghini: ,
 * Goron: ,
 * Hylia: ,
 * Lynel: ,
 * Nabooru: ,
 * Outset: ,
 * Peahat: ,
 * Rauru: ,
 * Zant: ,


 * Users pages are and always have been the sole property of the user, as opposed to Wikipedia. You're free to do whatever you darn well please, as long as there's nothing which would be considered against the site policy. I personally have a ton of pages in my userspace which serve multiple purposes, like a regular sandbox, a sandbox specifically for testing coding... and... um... I thought there were more than that. Maybe I'm just forgetting because I'm tired. And now I'm rambling. Fantastic. Point is, do what you please :P 12:09, 2 September 2013 (UTC)


 * Alright. Thank you.  I'll consider my options. - Dermot Mac Flannchaidh (talk) 12:25, 2 September 2013 (UTC)

Alright, I have a working page at User:Dermot Mac Flannchaidh/Pronunciation. I'm extending an open invitation to other users to suggest fanon pronunciations of their own. The pronunciations will be in IPA, but you can comment on the talk page using REE-spell style if you're more comfortable with it. I can read X-SAMPA too. - Dermot Mac Flannchaidh (talk) 16:43, 5 September 2013 (UTC)