Terraria Wiki:Community noticeboard

__NEWSECTIONLINK__

Discount Card
Possibly, add a buy price that shows how much the item is worth with the Discount Card equipped. I think it would be helpful.
 * It's a flat 20% discount, the math isn't that difficult. It's not feasible to calculate out every instance of a percentage on the wiki. Gearzein (talk) 01:11, 5 February 2015 (UTC)

i deleted my game data by accident and was hoping there were some gamers out the on xbox that could help me with some donations comment gamer tags
 * The wiki can't provide you with any technical support and isn't a place for social gatherings. You'll have to consult the official discussion forums for help like this. Gearzein (talk) 22:14, 25 February 2015 (UTC)

Golem Strategies Page
It has come to my attention that the Golem strategies page has become a bit, messy, so to speak. People are; firstly, trying to advertise themselves by saying, for example if I were to do it; Cooly9's Amazing Melee Tactic. Then with half the strategies it is the same one being repeated over and over again. The people who write most of them don't even know when capitol letters are used! What is your opinion on this? Cooly9 (talk) 07:19, 25 February 2015 (UTC)


 * Hi, I was looking at the page, did a few edits to the general info and then looked at the rest. I also think that the strategies are all about the same, too detailed and most could be shortened to one sentence. I would gladly help you to rewrite the page, but I feel bad about removing other people's contributions. Did you talk to anyone about the guide? Is it okay to do a revision like that?
 * The guide project is being started over, because all the guides are like that. These personal advertisements are entirely unnecessary. At some point Curse is going to be making some kind of video guide for them, but in the interim, please feel free to do whatever is necessary to clean them up. Gearzein (talk) 15:27, 5 March 2015 (UTC)

Tier page
It would be nice to have a page listing all the various tiers of equipment that gives a rough idea of which are better than others. I would find it very helpful, at least. If there's something like this that I missed, I apologize. Nerman8r (talk) 17:02, 14 March 2015 (UTC)

addition to main page & update
It would be great to add the Giant Tortoise to the Hardmode enemy section, and Undead Miner to Normal. Both are missing. The section could also use an alphabetizing. Looks wonky as hell w the Giant Fungus Bulb in the C's, Mummy in the D's. Some other names are also off. Next, I like the consolidation work ya did w Enemies on the Main page (slimes, mummies, etc.). 67.183.29.146 05:19, 22 March 2015 (UTC)
 * I have no problem alphabetizing what is already there, but you may notice, there are way more than just those two enemies missing. If all were added, you can imagine the page would get quite long.  Chrisf1020  (talk)  05:55, 24 March 2015 (UTC)

Add mount page
Add Mounts page to main page?


 * I think this is a good idea since pets have been added to the main page but I don't know how to do that... --66.214.76.114 03:35, 28 October 2014 (UTC)


 * I think it's a good idea to add Mounts to the main page, but.....there is not much space in there. The main page should contain only the most common things and basic information. Mounts may not be that important to be shown in main page. -- MrGlowing (talk) 17:33, 5 March 2015 (UTC)

Terraria Armor Dye Simulator (TADS)
I think the armor set pages (crimson armor, hallowed armor, frost armor) could have a Dye Simulator. like, each dye has its own button that when pressed, dyes the whole armor that color. or like, you enter a color in a text box beside each piece, and press a button labeled "Dye it!" and the piece is dyed that color! I thought this up when I was nearly run over. I should throw myself up in front of cars more often! ha! (no I shoudn't)

I bet nobody will agree with me. maybe somebody should make a program for this. I'm sure we can work this is java script, right? maybe. I have no idea! -- Robstar14 16:17, 30 January 2014 (UTC)


 * Good idea. -- Reno 17:08, 05 August 2014 (EST)


 * I "third" that idea! Nerman8r (talk) 16:41, 14 March 2015 (UTC)

Corrupted player?
Just wanting to ask this for my friend, in the character selection, it is red colored and unclickable, do this means his character is corrupt? Screenshot: http://prntscr.com/32yg9u FunAlways (talk) 01:54, 22 March 2014 (UTC)


 * possibly. no your computer you should go to Documents,My games,Terraria,Players and then the characters folder. with a world file the world and the back up will have "bad" at the end meaning that the world data is messed up. it might be the same with players. Michelangelo42 (talk) 14:38, 10 October 2014 (UTC)

This hardly seems like the place to be asking for tech support. Anyone mind if I delete this? Nerman8r (talk) 16:42, 14 March 2015 (UTC)
 * Generally we don't delete stuff from talk pages, except outright vandalism or things like that. It's also worth noting that you're responding to conversations from almost half a year ago; please check the dates before posting in reply to talk pages. Gearzein (talk) 16:46, 14 March 2015 (UTC)
 * Alright, but be aware that it creates a precedent. If people see others getting tech support here, they'll post more topics about tech support, because of normative influence. Nerman8r (talk) 17:02, 14 March 2015 (UTC)
 * I'm aware. In my experience, deleting comments means they either get re-added or repeated down the line. There's no problem with small instances of support- telling someone what version an edition of the game is currently on or how to find a page here isn't a big deal. For everything else we direct people to the forums- not just "block them and hope for the best" but specifically direct them to a place where their issue can be resolved, if possible. That's what's been done elsewhere on the wiki, including this page.
 * This may not have been policy a year ago when the original comment was made, so my primary concern was that comment being responded to a year later and the precedent it sets to repeat that action. Talk pages are meant to be a record of discussion and ideally remain as unaltered as possible, which is why they're committed to archive rather than wiped, but at the moment this page isn't long enough to dump into a second archive. Gearzein (talk) 18:12, 14 March 2015 (UTC)

Neater glitches/anomalies and verification system
I hate to say it, but the bugs and anomalies layout on the wiki seems too messy. It feels like we should add a drop-down system to stop it from looking overwhelming. Also, a lot of the bugs seem too ludicrous to be real. I mean, the Eye of Chutulu connecting to The Twins? I think we should add a system that forces a bug reporter to add a source, whether it be a video or a photo, and have someone moderating them. I'm not sure if it would be worth the hassle though, so feel free to tweak. - MinecraftPhotos4U (talk) 17:40, 26 November 2014 (UTC)
 * Aside from the most well-known bugs, bugs are generally pretty much unverifiable, and tend to remain on articles permanently. Whether or not they're fixed is usually also unverifiable. If you required a photo or video no one would really post them, and/or people would still fake them with software. I wouldn't mind prohibiting the whole bug posting thing here altogether, it just seems like a big move.  Equazcion ( talk ) 20:36, 6 Dec 2014 (UTC)

Bug clearing
I think bug reporting on this wiki has gotten kind of ridiculous. Prompted by User:MinecraftPhotos4U above, I'd like to consider some solutions. Bugs are generally unverifiable and tend to remain on articles forever -- we can't verify that they were ever there, so we certainly can't verify whether they were "fixed", at least in the vast majority of cases. As a result, some older articles have ridiculously long bug lists.

I'd like to do one of two things:
 * Option 1 is to systematically clear out all bugs from every article and start over. People will probably re-post the ones they still experience during gameplay.
 * Option 2 is to remove the bug template and prohibit the posting of bugs in articles, perhaps limiting them to the dedicated list of bugs pages.

Since posting bugs on this wiki basically doesn't accomplish anything, the second choice is somewhat logical -- however people like to post bugs they notice, and I don't want to get too draconian with reverting everyone who does that.

I'm basically planning to carry out option 1 already at the very least (not doing it yet though, will wait for input in case there are well-reasoned objections). Option 2 is a maybe, based hopefully on some discussion. If anyone has any input please do post it here.  Equazcion ( talk ) 13:55, 7 Dec 2014 (UTC)


 * personally I find Option 2 way too harsh and should probably be used as a last resort. Over on the Minecraft Wiki, bugs are not actually posted on the wiki itself but rather on the Mojang Bug Tracker site, which each page links to. I'm not sure if Re-Logic could do something similar, although it would definitely be a change for the better. Duplicates would be a considerable problem, though.


 * Alternatively, a page called Unverified Bugs and Anomalies could be created. Bugs would be reported here (with the appropiate environment e.g. iOS 7, iPad 2, 1.2 update, )and the bug must be able to be recreated. If the bug test proves successful, the bugs would go on a subpage of an article (for example: Gems/Bugs) which would be protected to admin levels (or possibly a new bug verifier user class?) to block the intake of unverified bugs. Although this also sounds complex, it may just be slightly easier than the other solution I have stated above.


 * Thank you for your time -MinecraftPhotos4U (talk) 17:21, 7 December 2014 (UTC)
 * Just to note, Minecraft wiki essentially uses option 2 -- that is, it prohibits bug posting in wiki articles, and instead directs everyone to an off-site listing. We could do the same here, directing people to the bug reporting sections at the forum (re-logic doesn't have an actual bug tracker yet). Also note the list of bugs pages already function as our list of unverified bugs. I don't think it would be feasible to have a system where people submit bugs for verification though. We just wouldn't have the resources for that.  Equazcion ( talk ) 17:26, 7 Dec 2014 (UTC)


 * We could possibly do it manually, it would be fairly complex but basically: make a new section, describe the bug, show steps to recreate it, optional image/video, signature. Then, in that section other players describe what happened when they tried it. When x amount of positives is reached, it gets added onto the page like Ores/bugs. - MinecraftPhotos4U (talk) 17:36, 7 December 2014 (UTC)


 * I don't think mangling the wiki into a makeshift bug tracker is really the way to go. It would be a little too complicated and I don't think we have the participation or admins to make it work. Bug tracking should really be administered by the developer anyway. They've chosen to do it through the forum and I think if we end up directing people anywhere, that would have to be it.  Equazcion ( talk ) 17:42, 7 Dec 2014 (UTC)
 * Seems like the way to go then. Should we put a link to the forum on every page though? - MinecraftPhotos4U (talk) 17:45, 7 December 2014 (UTC)
 * I'm thinking of maybe an interface message telling people where to go to post bugs when they edit an article. Gonna wait a bit for other responses here though.  Equazcion ( talk ) 17:50, 7 Dec 2014 (UTC)


 * Equazcion has a point about verifiability but I feel we should still allow bugs to be brought up here. A lot of times (and this goes for any game), something strange will happen and I will look online to see whether it's supposed to happen and if anyone else has seen it happen. If it only happens to me, I assume it's either a new bug or I'm misinterpreting what is going on. If it's happened to someone else, then I could theoretically verify it for them, just as they have for me. Maybe that's the trick to verification? Each bug that comes up goes up for vote. Bugs that are real get voted up; false or resolved bugs get no votes; bugs never get voted down, but bugs that do not get votes for a certain period of time are marked as resolved. Since each user can only vote once, no one could manage to keep a bug alive unless it truly is still in the game, unless of course they make multiple accounts (which would violate policy and typical internet etiquette anyway).
 * Feel free to mercilessly tear my idea apart. This is a wiki after all.--Macks2008 (talk) 18:13, 7 December 2014 (UTC)
 * That would be ideal; the problem is that we don't really have any feasible way of making it work here (see the discussion above). What you're describing is a bug tracker. This game doesn't currently have one, and the wiki isn't equipped for something like this (a voting system etc). Re-Logic currently uses the forum for bug reports -- people reply to threads there to chime in on whether they've experienced a reported bug. It would be nice to be able to make "popular" bugs visible on pages, but we don't have any way of doing that. Our choices are pretty much limited, I think, to either the free-for-all bug posting we've been allowing until now, or prohibiting them altogether.  Equazcion ( talk ) 18:27, 7 Dec 2014 (UTC)


 * I'm personally tempted to back option 2 on the pretense that bugs should be reported and fixed quickly and don't need to be catalogued, but if that were implemented just after 1.2.4.1's release then the known bugs in the current version would've gone unrecorded here for almost half a year. On the other hand, most of the ones in the List of bugs are unverifiable and anecdotal, and encouraging people to submit bugs here isn't constructive for anyone involved. Maybe bugs should be treated like references currently are- only those verified in some sense by the devs and not expected to be fixed quickly, like fluid reproduction, should be noted. On the whole, though, I think we'd do better to get rid of the template and redirect editors with bugs to the report forum, because the current bug template lends too much authority to potentially spurious claims without being comprehensive enough to actually do anything about the reports. Gearzein (talk) 18:37, 7 December 2014 (UTC)


 * Personally I would prefer option 2 as well. In the case that the bug template is used to warn the user (e.g. game crash bugs) we could replace them with important and other useful bugs (e.g. item/liquid duplication) could be replaced with a note. (Maybe we also want to remove hint while we are at it.) --0icke0 (talk) 19:20, 7 December 2014 (UTC)


 * The bug reporting in the mainspace has definitely gotten out of hand, but I think the main reason for that is as Equazcion stated, many of the bugs are outdated and just never removed. Option 1 definitely needs to happen in my opinion. Initially, I didn't like the idea of removing the Bug template completely, as I do like to see the existing bugs for any given item on its page, but lately I have been seeing the same bugs being added over and over, as well as some that can't be proven, and some that are downright outlandish. I'm still not sure if I would like to see the template removed, but wiping the bugs on existing pages would be a good start for sure. I also agree with the idea that bugs should be reported rather than just listed on the wiki, so that there is a chance of it getting fixed in the future. Chrisf1020 (talk) 19:39, 7 December 2014 (UTC)

Based on the above, I've begun making the necessary changes to implement option 2. I'm going to hopefully remove all the bug template code from pages via bot, but in the meantime I've cleared the bug template itself, which will hopefully cause bugs to stop displaying in articles for the time being. Thank you to everyone who posted! This really helped.  Equazcion ( talk ) 20:08, 7 Dec 2014 (UTC)

The removal seems to be going well. It seems some "notes" sections that only contained bugs are now empty notes sections that may need to be removed manually, but this doesn't seem like a big deal. Feel free to remove them when you come across them.  Equazcion ( talk ) 20:45, 7 Dec 2014 (UTC)


 * Removing them manually... That sounds like a job for me, since I know nobody else will do it. Chrisf1020 (talk) 21:18, 7 December 2014 (UTC)


 * Thanks :) It's no big deal if a stray Notes section exists in an article for a while, but if you're willing to do it that would be cool :)  Equazcion ( talk ) 22:24, 7 Dec 2014 (UTC)

There could be multiple templates that includes the different versions with verified or unverified options. ThePyromancer13 19:47, 11 Jan 2015 (AEDT)
 * The template and all associated bugs have already been removed. Adding new templates to differentiate between known and speculative bugs would run counter to the idea of keeping unverifiable information to a minimum. Gearzein (talk) 00:26, 12 January 2015 (UTC)

Crafting Recipe Protection
Crafting recipe pages are some of the most commonly debated and vandalized parts of pages, which is nonsense because they nearly never change. I'm considering emulating the way NPCs handle names and moving crafting recipes to their own protected subpages. Is anyone aware of any reasons why this is a bad idea, or does anyone have any objections or alternate solutions? If not, I'll begin implementing it in a few days, as well as looking into its viability for other contested but nonvolatile page elements such as weapon and armor stats. It's probably not worth doing for every infobox on the wiki but I'm at least considering doing it for high-traffic weapons and items. Gearzein (talk) 13:40, 10 February 2015 (UTC)
 * I've implemented this for the Terra Blade. I checked it on my phone to be sure it displayed properly on mobile devices, but if anyone has any problems with the page displaying poorly or being too slow or anything, let me know. Gearzein (talk) 11:57, 13 February 2015 (UTC)
 * The crafting recipe protection works :). Just comes up with {{/crafting} }.Cooly9 (talk) 10:01, 24 February 2015 (UTC)
 * Not sure whether this is anything to do with you, but on my mobile device the Honey Comb page is being wierd. I noticed the crafting recipe is in a new, better, format but then I noticed that the collapsable sections are just plain text, and I cannot edit the page.  What is going on? Cooly9 (talk) 09:56, 24 February 2015 (UTC)
 * The above method is it working as intended. Honey Comb appears to be an anomaly in several ways- apparently it's using the old Template:Crafts template rather than the Template:Crafting recipe that every other page uses. It's just a barebones table on PC though and doesn't include any collapsible areas. Checking on my phone, it does appear to be locked- I'll take a look at the protection settings and see what's up. Gearzein (talk) 14:36, 24 February 2015 (UTC)
 * Odd. It appears that many pages are unable to be edited from mobile devices, at least while not logged in. Some became editable after expanding all sections and scrolling to the bottom, but attempting to edit only provides a login prompt. The page isn't protected or anything- it's either something with the Abuse Filter (unlikely), something weird with mediawiki (highly likely), or something going on over at Curse. I don't use the mobile version of the wiki and couldn't say what's going on off the top of my head, but I'll be looking into it. Gearzein (talk) 14:47, 24 February 2015 (UTC)

How to Help guide updating?
I'm new to this wiki in terms of being a member and helping out, so I'm not the best at coding for the time being. My question is: can someone update the "How to Help" guide a bit to I Claude a more detailed description on how to add images? The paragraph there nor the page that is referred to there helps me with any problems or step by step how to input an image and it actually works so it displays. I tried to do "The Blade of Grass" page and add a demon altar jpeg image there but it doesn't acually display the image. Can someone help? Glowbomb12 22:29, 10 February 2015 (UTC)

Honey Comb damage
Does anyone know the base damage of a bee released by the Honey Comb and how many bees are released (between x and y)? Also, there is some confusion in the article. The first paragraph mentions it releases "several bees" but in the Notes it says that "Only one bee will appear (...)".

Note about "best modifiers"
Articles on modifiable items tend to contain a short intro note about which modifier is the "best" obtainable for that item. This information was added to let people know the highest-value modifier than can possibly be applied to the item. Some people see these passages as strategic recommendations, but they are not. They are solely intended to communicate the technical limit on how valuable a modifier the item can obtain, which can be helpful info during reforging (avoid continuing to hit "reforge" in the hopes of obtaining a more valuable modifier that is impossible to apply to the particular item). For some clarity, see Modifier, which describes where these limitations apply.

Articles (main wiki articles outside of Guide: pages, at least) shouldn't generally contain strategic tips on which modifiers to apply for given scenarios, except perhaps in special cases, and then only under the Tips header.

An exception is Minion-summoning items, where the benefits of the most valuable obtainable magic modifier (Mythical) are mostly lost due to the fact that minions themselves are not magic weapons, and there are no actual summon modifiers yet (though these are apparently coming in 1.3) -- so in those cases we do make the judgment call of saying Ruthless is the "most valuable".

I hope I've explained this at least somewhat clearly. In short, for most articles, the "best modifier" statement is intended to be a cold reading of the technical upper modifier limit, value-wise (ie. coins), as described at Modifier. If anyone has tips on better modifiers strategically, they should go under Tips, and only in exceptional cases. Equazcion ( talk ) 23:05, 27 Mar 2015 (UTC)

Character Creation page
Could somebody make this? It would be great, telling about hairstyles and how long your name can be and such. A "Character" page could redirect to it.
 * If you have a good enough idea, feel free to try writing it up yourself. There's already pages for most character gen options, like Hairstyles and Difficulty, but if the page is worthwhile and informative then we'll see. I personally don't think it'll work though- it might make a suitable guide page but there isn't a lot to character generation that would warrant a mainspace article. Gearzein (talk) 16:08, 1 April 2015 (UTC)

Pages in different Languages
Hello, I just noticed while editing the Zombie/de page that some of the wiki pages in languages other than english are seriously lagging behind on updates and are filled with incorrect data. Could someone help with that? For example, the german zombie page only lists two of the different zombie types in Terraria and includes information that may have been correct at some point, but isn't anymore.Terrariapc1 (talk) 12:03, 2 April 2015 (UTC)
 * Unfortunately, we don't have a lot of users fluent enough in other languages to bring all the translations up to date; most of the translation projects that are still active have only one or two active users, if that. It's not acceptable to just run them through google translate, as that's usually worse than no page at all, so most of them are pretty out of date. The staff and other users here are more than willing to help out with templates and formatting stuff, but all the text is up to people who speak the language.
 * If you'd like to keep contributing, though, we really appreciate anything you have to add, even if it's just a couple of lines or some spelling corrections. Having the wiki available in as many languages as possible is an important goal for us, and every little bit helps. Gearzein (talk) 19:19, 1 April 2015 (UTC)


 * Thanks for the info. I would like to keep at least the main, basic pages in order, but I only speak English and German well enough to edit those pages. I don't know anybody whose speaks the others and has enough spare time to edit and cares about the Terraria wiki. So, anyone who does speak these languages and happens to see this, please edit too! I just noticed as well that when I'm configuring the drops, if I enter the drop name in english, then the link and the picture file work, but the wiki displays the name in english. How do I get the .png files and links to work while displaying the, for example, german name? Terrariapc1 (talk) 10:53, 2 April 2015 (UTC)
 * There are a couple of translated templates lying around, but because of the way item names are set up, they all seem to display drops and other items in english. Many templates that refer to an item's picture count on the image being the same name as the page title because of their reliance on . There are a few fixes I can think of for this, but for the moment you might just have to make do and work around it. Gearzein (talk) 16:01, 2 April 2015 (UTC)


 * Thanks again. Looks like some people will just have to work with english item names for now. Terrariapc1 (talk) 05:19, 3 April 2015 (UTC)
 * By the way, when I created a new page in German, (the Spawn/de page) I finished, but when I visited the english site, it didn't say that I could see this page in another language. Did I miss a command I have to enter or is that some sort of bug? Terrariapc1 (talk) 14:22, 3 April 2015 (UTC)
 * Okay. So, the NPC template exists in other languages, as well as the item template, but the crafting template is only available in english, which defeats the entire point of translating in the first place. Can somebody please fix this? Terrariapc1 (talk) 05:52, 4 April 2015 (UTC)
 * You should probably address these concerns to the admin noticeboard; they'll probably draw more attention there.
 * As for the problem of having the templates predominately in English, that's a little complicated. The end goal of almost any translation project is to have their own subdomains- the best example of this is the French Terraria Wiki, which this wiki helps out from time to time but otherwise has its own separate infrastructure, userbase and administrative staff. As far as I know, every translation project started at this wiki has either reached that point or failed and fallen to the wayside, and this has so far been the ugly solution to so many templates requiring the page title and image title to be identical. Some templates can be modified to display translated names, but a lot of them are really messily coded, and at the very least it would take time to get them set up. The wiki just isn't structured to be easily translated. Another admin might have some more insight into this, but the best advice I can give you is to translate the text you can at the moment- try to get the German front page as free of redlinks as you can- and see if Curse is willing to let you "graduate"
 * As far as the translation links, that's fortunately much easier. Just add a translation link of the format  at the bottom of the page, like so. Gearzein (talk) 06:28, 4 April 2015 (UTC)
 * I really have to thank you now. You've told me a lot of things I would have had trouble finding out or might have never found out. I really wish that everybody on online servers could be this helpful, but there are lots of people out there who just don't care. I'll do the best I can. Terrariapc1 (talk) 08:28, 4 April 2015 (UTC)
 * Hey, I'm back! This time, I have a request: On the page Door/de, could you show me how to get the picture working while also displaying the right name inthe crafting table? I've tried different methods, but it either says "[[File:(Picture of Wooden Door)Holztür(german for Wooden Door).png]] (Picture of Wooden Door)Holztür" or "[[File:(Picture of Wooden Door)Holztür.png.png]] [[(Picture of Wooden Door)Holztür.png]]". Could someone show me please? Terrariapc1 (talk) 14:13, 8 April 2015 (UTC)

Questionable Redirects
I find it a bit strange that every hook type redirects to the main "Hooks" page, yet other, even more similar items don't. For example, Dual Hook and Ivy Whip both redirect to the same page, yet Copper Broadsword and Tin Broadsword, or Boreal Wood Wall and Palm Wood Wall all have their own, unique pages. I think every hook should get their own page, but the Hooks page should still be kept, as with other general pages like Dyes or Pickaxes. KM100 (talk) 01:56, 12 April 2015 (UTC)
 * The hooks used to have their own individual pages. They were combined because of the difficult logistics of maintaining individual pages on them, when all hooks share so much intricate information. The vast majority of the info needed to be repeated exactly on each page. If users changed information on one hook page, that information usually needed to be matched up on all the remaining pages; this occurred often and the pages then often became a mess of inconsistency. The Paintings and Developer-reserved items, along with several other item groups, were merged for similar reasons.
 * Dyes were considered for merging, but that would have been more difficult due to their crafting tables. Currently, the individual dye pages allow players to easily search a dye and see a page listing what other dyes can be crafted from it, or which dyes go into making it. Combining all of this information into a single page for all dyes would be difficult, both on the creation end and for readers afterward.
 * Combining things like Walls or Pickaxes could be a possibility, but it's not a pressing issue, since each of those individual pages doesn't describe the fundamentals of those item types the way Hooks or Paintings did, and don't fall easily into inconsistency. Equazcion  ( talk ) 02:11, 12 Apr 2015 (UTC)


 * Well, I find it a bit questionable to not have unique pages because of the way hooks work. Pages like the Enchanted Boomerang don't explain exactly how every boomerang in the game functions; it just says it's a specific type of Boomerang. If there would be a change to the fundamental boomerang programming, the main boomerang page would be the only thing that would need to be changed.
 * I can definitely understand why paintings and furniture item should get grouped together, since they're all identical, but it seems a bit silly to group all the hooks and wings into a single page despite their differences. But I'm nobody to decide how the wiki should work, so if nobody else thinks it's a good separate them, they shouldn't be separated. - KM100 (talk) 02:53, 12 April 2015 (UTC)


 * I hear what you're saying. The difference that led to this need with items like Hooks and Wings, versus items like Boomerangs or Walls, is the intricacy of their workings. Before the merges, people would add (for example) notes and tips on individual Wing pages that they didn't realize pertained to all Wings. It became logistically impossible to keep checking for these inconsistencies and move information around as appropriate. While this happens occasionally for things like Boomerangs (someone may report that one travels through one-block-thick barriers up-close, for example, when they basically all do that), it doesn't occur to anywhere near the degree that it did for Hooks or Wings nor create the resulting mess -- presumably because there isn't as much intricate detail to pick apart regarding a Boomerang's mechanics.
 * I'm open to exploring the possibility of linking the Hooks, Wings, etc. off to individual pages again, but a) I'm not sure that there's a good reason to do so, and b) if we did consider it, we would need to devise some method of keeping the same mess from arising again. Equazcion  ( talk ) 03:12, 12 Apr 2015 (UTC)

Smart Cursor and Auto Select
I just created a new page (Cursor modes) explaining in more detail what Smart Cursor and Auto Select do. I hope that's a reasonable thing to add, because I definitely wanted something like that when I was a brand new player. So now I'm wondering how to integrate it with existing pages. The settings and game controls pages already have incomplete descriptions which seem redundant now. Would it be good remove (for further shorten) those and link to the new page instead? I'm kinda new at wiki editing and don't want to do anything too controversial. P.S. I think I've covered the basics, and then some, but if I've left out any functions for either mode, please help me complete the list. BlueMana (talk) 00:26, 13 April 2015 (UTC)
 * Seems useful enough to me; I know one of the things I looked up when I was first starting was what smart cursor did, only to find little to no information. I've already gone ahead and changed the Smart Cursor and Auto Select redirects to point to the new page, and edited the other pages to match. If I think of anything else I'll go ahead and link it there too.
 * Feel free to make any changes you feel to be necessary, not just here but in the future as well- there are few mistakes so drastic they can't be undone, so be bold in editing. Gearzein (talk) 00:53, 13 April 2015 (UTC)
 * Thanks. I'm sure I'll be more confident as I get a few edits under my belt. BlueMana (talk) 01:38, 13 April 2015 (UTC)

Lihzahrd Temple rename
I'd like to move Lihzahrd Temple to Jungle Temple. Near as I can tell, "Lihzahrd Temple" was a name chosen by WelchDrew originally, while the developers always referred to it as the Jungle Temple, beginning right from the 1.2 release notes. The Temple Key tooltip also agrees. There is zero mention of "Lihzahrd Temple" in the game code. All mentions on other pages can be changed via bot and we'd leave a redirect behind just in case. Any thoughts/objections? Equazcion ( talk ) 04:18, 13 Apr 2015 (UTC)
 * I'm supporting this, but consider that a quick search of the forums for the terms "Lihzahrd temple" and "jungle temple" reveals that there are nearly twice as many results for the first. While a redirect could fix the surface problem of people looking for the temple on the wiki and not finding it, the lihzahrd brand is strongly entrenched, and such a change could still prove confusing. There is also potential for conflict with Jungle Shrines, though I don't consider that as serious an issue.
 * All in all though, I don't have any serious objections. There's not enough other structures in the Jungle to cause any serious confusion by removing its association with the enemy type that predominately spawns there. Gearzein (talk) 04:49, 13 April 2015 (UTC)
 * That the forum widely uses "Lihzahrd Temple" was to be expected, since most of those users get their info from the wiki. I think they'll adjust to the change. I'll put up a dab link at the top of each page to cross-link the Shrine and Temple in case there's confusion. I'm gonna go ahead with the move, just wanted to get at least one opinion from another experienced editor. Thanks. Equazcion  ( talk ) 05:02, 13 Apr 2015 (UTC)
 * I can see points on both sides. The Temple Key says it open the "jungle temple", but it's not clear if that is intended to name the place, or simply describe it. "Lihzahrd" may not mean anything to you at that point in the game if you haven't read spoilers. Perhaps the page should just be called Temple. It's not like there are any other temples. BlueMana (talk) 05:25, 13 April 2015 (UTC)
 * I'd agree that "temple" is probably technically sufficient since there are no other temples, but that would still be a little ambiguous to a casual reader; "Jungle Temple" is more descriptive and anyway seems to be more endorsed. It's not completely clear what the intended name is, but many such things aren't. All we have to go on in this case are the tooltips, release notes and other developer comments, which so far point to "Jungle Temple" predominately (near as I can tell). Equazcion  ( talk ) 05:43, 13 Apr 2015 (UTC)

Armor set bonuses
I've noticed the armor pages are often unclear about the distinction between set bonuses and the combined bonuses from individual parts. I'd like to put this in a more consistent format with a clearly labeled "Set Bonus" on everything. I know this can get complicated with the hardmode armors where the helmet changes the set bonus, but I still think we can do better than what we have now. Any thoughts, objections? --BlueMana (talk) 17:26, 3 April 2015 (UTC)
 * No objection here. The main Armor page could benefit from splitting up that info. It might be difficult to squeeze another column into that table, but if it can be done in a space-efficient way then maybe; or we can just add separate bullet points to each armor set where the set bonuses are split off. It might take some experimenting to see how the info would best fall into place. Equazcion  ( talk ) 17:54, 3 Apr 2015 (UTC)

After experimenting with adding a column, I decided that wasn't feasible. On my 1280 screen (which I assume is a typical mid-low end size) everything got squished pretty bad. So I just added Set Bonus: as a bullet point to each armor that has one, separating it in the cases where it had previously been combined with piece bonus. It's a little untidy, but it was the best way I could think of to present that information. Next up are the individual armor type pages. My thought is that the top-right info box should only show the set bonus (which is already the case for some armor, but it's not consistent). The individual pieces are right there on the same page where you can read their bonuses after all. But if that option is unpopular another approach would be to split it into two lines, Set Bonus, and Total Bonus. What do y'all think? BlueMana (talk) 18:50, 16 April 2015 (UTC)
 * You did a nice job. It doesn't look all that untidy to me. I think for now the individual armor pages should just show the set bonus in the upper-right infobox. As you say, the individual piece effects are already shown in their individual infoboxes. We could add a separate line to the armor box to total up the piece effects at some point afterward, if people want to do that. Equazcion  ( talk ) 19:29, 16 Apr 2015 (UTC)

Front Page
Just throwing this out there, because I realize it's a serious undertaking, but has anyone else thought about entirely redesigning the front page? The top third or so is fine, but the whole bottom section where we list as many game entities as we can fit into the table looks really messy. I don't have any ideas in mind for what it could look like, mind, but I've been thinking about how unwieldy the current one is a lot lately for some reason. Gearzein (talk) 10:56, 17 April 2015 (UTC)
 * It'll get even worse if we try to remain consistent once 1.3 is released and attempt to cram in that new content. An easy measure would be to remove the extensive enemy list, which I think is overkill for a front page. Most of the other stuff is general enough to stay, though I'd maybe prune down the "mechanics" list to remove some of the more generic items like health and mana. Equazcion  ( talk ) 11:13, 17 Apr 2015 (UTC)