Terraria Wiki:Community noticeboard

__NEWSECTIONLINK__

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)
 * if you want i don't mind doing this if people will find this useful Vix83
 * There are already several pages like this for the individual equipment types: Pickaxe, Hammer, Sword, Armor, etc. Equazcion  ( talk ) 12:06, 26 Apr 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)

i totally understand this problem, the dutch project has most pages not updated since 1.0.6, i think thi is due to having not enoug frequent working people in these languages, i'm the only one working on dutch for example.User:Superstrijder15 10:36 8-6-2015 dutch time

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)

The Horseman's Blade
I am a melee player and I am currently trying to get a Horseman's Blade from Pumpking. On the page, it says the use time is 25-29. What does that mean? Is there a definite use time? Also, is Pumpking more likely to drop melee weapons if I use other melee weapons instead of, say, magic weapons? Random info: I currently use a true night's edge.
 * In the code, the actual useAnimation time for the Horseman's Blade is 26, so its functional usetime should be 25, unless there's some quirk of the weapon I'm not aware of that causes it to require an average to be listed. It's likely someone accounting for modifiers, which is unnecessary.
 * As for your other question, I'm not aware of any situation in which the weapons you use during a battle influence the items an enemy will drop. Pumpking's drop rates all increase at the same time based on how many waves of the Pumpkin Moon you've cleared. Gearzein (talk) 02:07, 18 April 2015 (UTC)

Random Page languages (and the bone page)
Has anybody noticed by clicking the 'Random Page' button often redirects you to a page in a different language? I find that annoying and it happens too often.

Although I am aware that this is fixable by deleting the end of the web address but It is still something that I feel needs fixing.

Also, I think that there should be something added to the page describing the bone item. Playing the console version (Don't know if this is just on that version) If you throw bones onto the ground at fast speeds you can often duplicate the bones so I think that should be noted.

Thanks for reading.
 * The random page issue is something we've been attempting to address. The foreign language pages you're arriving at are part of translation projects that start out here, at the English version of the wiki. I got Gamepedia to install an extension that is supposed to allow us to filter those pages out when Random pages are chosen, but there seems to be some technical issue with it that they are still trying to sort out. I too hope this will get fixed.


 * The Bone issue you describe sounds like a bug, and the policy here is to leave bugs out of wiki articles. You can report game bugs at the forum. Equazcion  ( talk ) 20:56, 18 Apr 2015 (UTC)

Developer Email
Hi, does anyone know the any of the developer's email, or some way I could send a message to them?
 * I don't know of any contact info myself. If you have a game suggestion or bug to report, it's best to use the forum:  Equazcion  ( talk ) 02:18, 26 Apr 2015 (UTC)

Lost item/update dilemma
The lost item: Hi. I am a long-term Terraria player, but lately I have been having some doubts over some things, and I have recently lost a horseman's blade. It happened like this. I was fighting through the pumpkin moon, and than I kill a pumpking, and I get a horseman's blade (woo-hoo!), the sword I had been searching for for a LONG time! But just as I start swinging it, and as soon as I saw the pumpkin heads come onto the screen, the game literally just cut out. No lag before it quit, no freeze, no blackout, it just kicked me, and then the game wouldn't open again. I have never downloaded viruses (I check regularly), I haven't damaged my device in any way, and have never done anything else that may have led to this. When I finally got back on, I literally had every other thing from that pumpkin moon (spooky wood, stake launcher, spooky twig, etc) but NO HORSEMAN'S BLADE! It's almost as though the game selectively removed it. I am a melee player, and it took me a long time to get this weapon (Not to mention legitimately), and it seemed like the best weapon I had. But it's gone now, and I'm very frustrated/upset. Does anyone know what caused this, if there's a glitch associated with this weapon, or more importantly, any possible way without hacks that I could get it back??😰 Thank you for your time.

Update dilemma: Hi, me again, I have recently been reading Terraria reviews (iOS) with the latest bug fixing patch. It sounds great, with things like making the truffle spawn, allowing reforges, etc. But the problem is...More than the majority of the reviews are complaining about the update, with glitches such as character wipes, world corruption, going into a piggy bank/safe and finding 1000+ dirt where biome chest items once were...bottom line, they say don't updat if you can avoid it. I still have 1.2, and have not updated yet. Should I:

A) Risk getting the update and maybe lose my true swords (originally horseman's blade), turtle armor/dragon, etc.

OR

B) Stick with 1.2 until the patch either gets fixed or a new one comes out


 * This isn't really the right place to go for technical support. You might have better luck on the official forum. But I do know that the game saves your progress periodically, so it makes sense the last thing you got before a crash is what you'd lose. I'm inclined to guess it was just incredibly poor timing, but as I said, maybe someone on the forum will know more. BlueMana (talk) 06:49, 26 April 2015 (UTC)

Placed block pictures
So I've been thinking recently that it would be nice to have pictures of more of the blocks in placed form. Especially those that are unusual like pumpkin or glowing mushroom. I know there's a giant picture showing a 2x2 chunk of each block overlapped on the Block page, but it's a bit hard to make sense of. I'm thinking of something like a little hut or similar so you can see how they look when actually you use them. I noticed some pages have this kind of thing as floating image on the right, and others have a gallery section at the bottom. Which is a better way to add something like this? BlueMana (talk) 15:47, 26 April 2015 (UTC)
 * We've got this: which could be sliced up, I think that would be sufficient -- a square sample, like we have in infoboxes for many block types already.  Equazcion  ( talk ) 16:25, 26 Apr 2015 (UTC)
 * Descriptions here: . Equazcion  ( talk ) 16:27, 26 Apr 2015 (UTC)
 * Those would probably do. I like the second image is better though, since it shows a square, as well as vertical and horizontal bars. There are some details you can't see on the plain 3x3 square, like the stem on the pumpkin or how the living wood looks like a broken branch on the ends. Of course using the plain square for blocks that don't have those features is an option. BlueMana (talk) 16:51, 26 April 2015 (UTC)
 * Good point, the added little strips/single blocks do reveal some details you wouldn't see otherwise for certain block types. Equazcion  ( talk ) 17:10, 26 Apr 2015 (UTC)
 * Alright, final question: Using those images, would it make the most sense to go ahead and put it right in the infobox? Even the larger style is only about the same size as the 3x3 wall images, since walls are wider.— BlueMana (talk) 18:27, 26 April 2015 (UTC)
 * Yeah I say put 'em right in the infobox. These don't seem so big as to warrant some separate type of display. PS. I generally use " &amp;nbsp; " (space, nbsp, space) to space the inventory images away from the placed images, which usually seems to look adequate (not set in stone, if you have something better in mind). Another note, if you do upload these individual images, I suggest using a uniform filename convention, adding "(placed)", "placed", "sample", or something to that effect, after the item name. This will simplify certain coding tasks in the future. Thanks :) Equazcion  ( talk ) 18:38, 26 Apr 2015 (UTC)
 * Sure thing. I figured I'd just copy the format from one of the Wall pages. They don't seem to use nbsp (at least not consistently) but I can certainly stick that in.— BlueMana (talk) 18:55, 26 April 2015 (UTC)
 * Whoever did those wall infoboxes originally seems to have attempted to space the images out that way:

| image =
 * ...but they didn't realize that consecutive spaces are ignored. A space-nbsp-space would have solved that. I might go through the wall pages to fix those too. Equazcion  ( talk ) 19:08, 26 Apr 2015 (UTC)
 * I altered the item infobox template so it'll automatically display a placed image alongside an inventory image, as long as the placed image is name "File:Item Name (placed).png" or "File:Item Name (placed).gif". So all you'd need to do is upload the placed images with " (placed)" after the item name, and they should show up automatically. Equazcion  ( talk ) 14:07, 27 Apr 2015 (UTC)

Okay, wha'd I do wrong?— BlueMana (talk) 14:36, 27 April 2015 (UTC)
 * You didn't do anything wrong. The page cache just needed to be purged (which I just did, so your image comes up now). To clear a page cache, you can add "?action=purge" to the end of the URL in your browser. If you want to make this easier, you can go to your User:BlueMana/common.js and add the following line: importScript('User:Equazcion/utcClock.js');. This is a script (an add-on for this wiki only) that will place a clock at the top of each wiki page. Clicking the clock will purge the cache of the current page automatically. Let me know if you need any clarification.  Equazcion  ( talk ) 15:09, 27 Apr 2015 (UTC)
 * Alright, the action=purge method seems to be working just fine. I'll do more later today.— BlueMana (talk) 15:48, 27 April 2015 (UTC)

Solar eclipses
It has been months (total, not straight) since I saw my last solar eclipse and I haven't seen one since then... It's been at least 50 Terraria days (I've been counting). I really need the Terra blade as a stepping stone to get other items like the North Pole, horseman's blade, etc. I don't want to AFK farm for too long and risk missing an eclipse... Any suggestions?
 * As far as I know, there's nothing you can do to trigger or increase the chances of a Solar Eclipse. You're better off asking at the forum though. Equazcion  ( talk ) 23:06, 28 Apr 2015 (UTC)

Ore spawn in different world sizes!!!!!!
So im new to this game and there is one thing that is making me so furious about. Some ores don spawn in small worlds but they do in medium, same way the other way around. And my small world has no underground rooms with chests. PLEASSE HELP!!!! Im i doing something wrong. Im pulling out my hair
 * We can't provide technical support here. You're best off asking this question at the forum: http://forums.terraria.org Equazcion  ( talk ) 02:24, 6 May 2015 (UTC)


 * Not every world spawns with every ore. For example, a world might have Copper Ore but no Tin Ore, or vice versa. As far as the underground cabins go, either you're just unlucky, or you're having technical difficulties, in which case you should head to the forums. --KM100 (talk) 02:36, 6 May 2015 (UTC)

Broken Hero Sword
I have a few questions, first, I have the chlorophyte claymore with +18 damage and it already does 96 damage so i use this quite often but I'm wondering if the terra blade is still better? Also I had two broken hero swords and I made the true Excalibur and true nights edge or whatever the second one is, but I need another broken hero sword! I'll be on most of the day today and my PS4 PSN name is: shockshellteipe1. If. By one is willing to give me a broken hero sword id pay a few gold for it. Thanks in advance! Also anyone just looking to mess around add me as well because only a few people in my friends list have this game!
 * You're best off asking these questions at the forum. Equazcion  ( talk ) 16:07, 10 May 2015 (UTC)


 * Yes, the Terra Blade has higher speed, damage and knockback. BloodVsWater (talk) 23:21, 14 May 2015 (UTC)
 * A quick search for Terra Blade and some math would've revealed this (legendary terra blade comes out to around 101- this took me about four seconds on my calculator). As Equazcion said, discussion and debate of these questions belongs on the forums- this noticeboard is specifically meant to deal with issues and policy on the wiki, not field questions about gameplay. There is a giant notice at the top of this page to clarify this, and making it any larger or more noticeable runs the risk of becoming comically condescending. Even so, many of these questions don't even need to be redirected there, as actually using the wiki for its intended purpose would make their answers pretty plainly obvious. Gearzein (talk) 00:05, 15 May 2015 (UTC)

Online on iOS 8
That you can play online on ipad/iPhone like just press on the online buttom so you dont need a computer or a special app for that plz i relly want that me and my friend want to play togheter so plz do this in next update.
 * Unfortunately, the developers don't read this wiki, and we can't comment on their development cycle, as we don't know it. In order to get more information on iOS multiplayer or request its inclusion to the dev team, you'll need to head to the forums and make a suggestion there. Gearzein (talk) 07:03, 12 May 2015 (UTC)

PvP classes page
Has anyone noticed that some of the more recent PvP class additions have become a bit, loose? One of them doesn't even explain the effectiveness of their strategy, and several have quotes like "YOU WILL BE UNSTOPPABLE" or "THIS IS A VERY GOOD LOADOUT". And several of these people don't even know where to capitalize or even spell certain items correctly (clorophyte, or ademantite for example)! I really don't feel like going back and making changes to every grammatical error I find.
 * Yeah, several of the guides pages are lacking in content or quality, mainly because they're not concrete. Unlike other pages, none of the guides' info can be "checked" as lots of people have different playstyles and find different methods far more effective than others. The guides pages could definitely still use some cleanup, so any help is appreciated. While you still should respect the content uploaded by authors, feel free to remove (or embellish on) some of the classes that don't explain why they're effective. --KM100 (talk) 14:51, 16 May 2015 (UTC)
 * I still think it'd be way more effective to just delete all of the pages that cover "character classes". These are entirely player created and most seem more like a personal theme or aesthetic than actual strategy, almost as if they're a loophole through the inability to just show off your characters normally.
 * Of course, I'd rather these have suitable replacements before this, as we do need actual guides on viable strategies and weapons that fit together well in as provable a way as possible (like no Scourge or other homing weapons for pvp). These guides don't need cleanup, though- they need a complete page-one rewrite. I've started working on some but I don't have the time I used to nowadays. Gearzein (talk) 20:49, 16 May 2015 (UTC)

Yeah. Oh, and another problem is that some people aren't even making new strategies; instead, they're editing better-written classes and making errors there, too! BloodVsWater (talk) 00:36, 18 May 2015 (UTC)BloodVsWaterBloodVsWater (talk) 00:36, 18 May 2015 (UTC)


 * As I've said before, I think crowdsourced strategy guides are a flawed concept from the get-go. You could clean them up or rewrite them completely, but the same sort of problems (precisely the types described above) will crop up again over time. I'm hoping that if/when the Curse/Gamepedia strategy videos are introduced, they will at least provide some solid source material that everyone can refer back to when editing guide pages, for at least some sense of consistency. Equazcion  ( talk ) 01:20, 18 May 2015 (UTC)


 * I'm reluctant to publicly discuss the progress (har har) made on the Curse-made tutorials since their proposal but to be frank, it may be more prudent to start taking action against this on our own terms. I don't know what action, honestly. I've been trying to police the guides a bit and hold them to some kind of standard, but that's punching fish in a barrel at best. I'm hoping that a combination of well-written, article-style tutorials and persistent curation will ultimately make them fall into some sort of place. We're probably pretty low on Curse's totem pole as far as official video content goes, so I'm equally reluctant to press them for results, but we're smart enough to manage the content here ourselves. Gearzein (talk) 02:45, 18 May 2015 (UTC)

Plantera Strategies page
Just like what Cooly9 said, the Plantera strategies page is morphing into a page not unlike the previous Golem page, with entries like "Example's amazing Example tactic". What, if anything, should I do, or should I leave major edits like this to people in a higher position of authority?
 * General wiki rules apply to guides as well. If you see that kind of stuff and feel like you can deal with it, go ahead and clean it up. If your rewrite's good, then it's good; if not, someone else will come along and fix it. As stated above, though, guides are in kind of a weird state so don't worry about it too much.
 * Also, please remember to sign your comments with four tildes ( ~ ). Gearzein (talk) 02:45, 18 May 2015 (UTC)

Profile Pages
This is (I think) the first time I have used the noticeboard so tell me if i'm doing something wrong. Hello there, I was just looking at my profile page and saw something saying level 44 (Currently) and something else above it. I feel it has something to do with the number of edits/contributions i've made on this wiki but then I see that on someone else's page they have about 10 more contributions than me but is only level 14. Huh. C74SS1F13D 07:12, 25 May 2015 (UTC)
 * It's the Gamepedia leveling system, some sort of social interwiki contribution tracking thing. It's meant to be a fun aside thing that measures your progress as a wiki editor and contributor, but I've honestly never been able to make heads or tails of how it's actually measured. I was level zero for about six months then shot up to like 50 or so overnight a few weeks ago. Admins also have the means to grant or revoke wiki points for individual contributions, and Curse staff get on your case if they're concerned that you might be gaming the system to get more of them, but I don't know what they're for. It's just a bit of harmless embellishment, don't worry too much about it. Gearzein (talk) 07:26, 25 May 2015 (UTC)
 * Ohh ok so I can delete this section of the noticeboard now? C74SS1F13D 07:29, 25 May 2015 (UTC)
 * Just leave it, it'll get pushed to an archive at a later date. Gearzein (talk) 07:48, 25 May 2015 (UTC)

Eye-Ball
Hey guys I created a new page about a future enemy called eye-ball may be included in a update please add one of those cool tables with stats of enemies Thanks in advance! Here is a link Eye-Ball to go on page to edit
 * Where did you see this possible future enemy, and where did the name "Eye-Ball" come from? We can fix the page up with stats tables etc, but unfortunately there shouldn't really be a new page set up yet for this enemy if we only just have a glimpse of it somewhere with no name etc to go on. A mention on the Upcoming Features page might suffice. Thank you for contributing though! Equazcion  ( talk ) 22:13, 27 May 2015 (UTC)
 * I think this page's creation is way premature, even for a spoiler item. There's not even consensus that it's an enemy in places where it's being discussed, and I've seen the term eye-ball used exactly twice to describe it. Since nothing is known about it, this page really only invites conjecture and speculation by attaching a fan name to it. Gearzein (talk) 03:46, 28 May 2015 (UTC)

Music Box (PS4 version)
Music Box

On the console version, the (Snow) and (Ice) Music Boxes are opposite what is captured on the wiki page. Same with Music Box (Boss 4) and Music Box (Boss 5).

I took screenshots of each, as seen below. KM100 suggested "it would probably be better to have the name switched instead of the info (such as Snow (Pc only.png), Ice (Console only.png)), or a simple note describing how they're switched. Having all the info and links listed twice with a ton of icons becomes quite confusing." I posted the proposed results on the Terraria Wiki:Sandbox page, but I'm not sure if that looks acceptable. I'd appreciate any feedback on this, so the proper changes can be made to the page.

Thanks in advance. --NibKing (talk) 19:19, 19 June 2015 (UTC)
 * It looks good to me. Although it extends the list, I think it's much clearer to list the versions separately like this. I added a footnote to your sandbox version to tie the info together and explain the existence of duplicates. Equazcion  ( talk ) 19:44, 19 Jun 2015 (UTC)
 * I'm just gonna copy/paste what's in the Sandbox then. Glad you added the notes, because I wasn't sure how. --NibKing (talk) 20:07, 19 June 2015 (UTC)

Version categories
This was sparked by an old argument begun originally by User:Dxos3, which he recently brought up again at my talk page.

The issue is that a console player, for example, has no place to turn in order to see a straight listing of content available on their platform alone. We have Category:Console content, but this is populated only by console only, pc/console only, and console/mobile only. The Console content listing is therefore missing most of the content available in the console edition, ie. the content that all versions contain. One could argue that a console player can easily determine which items they will and won't have access to, but some players may wish to see a browsable list of everything available on their platform alone, without having to click other things and be disappointed by a "pc-only" message.

User:Dxos3 originally wanted an organized page with sections and graphics, but this proved to be somewhat unfeasible -- it would need to be created manually (it was started at one point but languished and was eventually deleted), and even if done initially would likely (I think) end up deteriorating.

Since we already maintain those "____ only content" banners pretty diligently, filling out these categories with their missing content seems like a good compromise. I've added an "allversions=yes" parameter to our infoboxes, which would add all-version content to all the content categories (eg. Category:Console content would then list all content available in the console edition). I also created all versions for use on pages with no infoboxes, which does the same thing.

I may be able to mass-add these parameters/templates to the necessary pages via bot. I wanted to present this here first for comment. If you have thoughts on whether or not this should be done feel free to say something. Equazcion ( talk ) 13:51, 20 Jun 2015 (UTC)
 * My only question is how mechanics and other pages will be handled. Pages like Fishing will be listed in the PC Version category because of their "____ only content" banners, but will core mechanics like Defense end up on the page, or is their inclusion (or lack thereof) even something to be concerned about? Regardless, it seems like a good idea, and would definitely help some users who want an absolute list. --KM100 (talk) 04:48, 23 June 2015 (UTC)
 * I think an initiative like this should be limited to ID-tagged entities like items and NPCs; I feel it goes without clarification that most mechanics are in all versions of the game unless specified, and those that are would hopefully remain pretty limited (I can't think of any other than fishing itself). That said, I think it's a much more solid idea than the original proposed page of links, and generally endorse both better use of categories and fewer dedicated list pages across the wiki. Gearzein (talk) 09:24, 23 June 2015 (UTC)

Console/mobile history
Adding to this and maybe a really good idea here but in all the items (yes I know it would be an insane amount of work at this point) if we can start adding to the version history the version of which it was introduced to console and mobile as well? Below is just a quickie example. Console/mobile version pages can also be created just like the pc versions to make it to where players can still reference to them directly by page or when chatting in talks about when items came in or such by adding the version tags to their posts.

slight note on below: I know my formatting is horrid but its early in the morning and cant really think of everything.

-- History --
 * {Console_Version}
 * 1.06: Introduced
 * {Pc_Version}

DragoHanter (talk) 16:28, 20 June 2015 (UTC)
 * That's an entirely unrelated suggestion, so I've moved it to its own section here -- but yeah the console/mobile histories could be better organized and perhaps separated. Equazcion  ( talk ) 17:08, 20 Jun 2015 (UTC)

Bug Policy
I've been thinking about the "no bugs" policy on this wiki. I wasn't here before the policy, so I may not fully understand the reasons for its existence, but I think it's too strict. The PC version at least, currently has mercifully few serious bugs, but with with imminent release of a major new version, it's entirely possible there will be some new ones. In particular, I think there should be some allowance for documenting bugs which are both harmful (as opposed to exploitable or just funny) and reproducible. Like if (totally made up) using the new multi-chest quick sort near two piggy banks destroys the items that should be stacked there, I think it would be appropriate to warn people about that until it got fixed. Is this worth considering, or is it better to cross that bridge when we come to it?— BlueMana (talk) 04:49, 26 June 2015 (UTC)
 * I didn't voice my concerns here either, because by the time I knew of the policy it was already long-since enforced. But, I definitely agree that it's getting too strict. It's starting to become more of a pain to remove the bugs that everyone keeps listing (such as the temple door bomb glitch, or mismatched npc quote glitches) then it is to remove the bugs that are completely unsourced and probably made up. Obviously, some restrictions need to stay in place, so there aren't "Bug: starting up the game might delete all your items!" posts everywhere, but a "remove nearly everything that isn't 100% intended" policy is starting to get tiresome. --KM100 (talk) 05:07, 26 June 2015 (UTC)
 * (edit conflict) See here for the discussion that led to the rule. It explains the reasoning. In short, bugs are largely anecdotal -- ie. unverifiable, could be fabricated, and would always nevertheless remain in articles forever, since it also couldn't generally be verified whether or not they were fixed. Bug lists got very long and were mostly useless. That said, the most prominent bugs can be posted, ie. those the developers have openly discussed, or those that are detrimental, consistently reproducible for everyone, and warrant warning players against behaviors that would trigger them and resultingly damage their world or player files. As far as exploits go (the ones that haven't been discussed by the developers), they can be a slippery slope and lead to a decline in wiki articles to cheat forum status. It might be tough to craft rules regarding which of them can and can't be posted so as to avoid that eventuality. I'd be open to re-examining it though. Equazcion  ( talk ) 05:13, 26 Jun 2015 (UTC)
 * The current bug policy does do a good job on preventing unverifiable bugs from being posted, the problem are those people who don't read the policy (or believe their bug is an exception to it) continue posting glitches. It gets pretty irksome when I have to constantly undo the same mobile version glitches that I can personally verify (and have videos documenting them). I do think that major exploits (e.g. duplication glitches) should stay off the wiki for the most part, but I feel as if easily-repeatable or verifiable dangerous glitches should still be allowed to stay.


 * I agree that it'd be hard to get a policy that specifies exactly what can and cannot be posted, though, and it'd be even harder to get everyone to follow it, so I'm fine with waiting until further word. --KM100 (talk) 05:29, 26 June 2015 (UTC)


 * One block to that may at one point have been that most of the bugs you're describing, ie. those that everyone experiences, were confined to mobile, and our consistent trusted editors were all PC players who couldn't verify them. If you wanted to personally be the gatekeeper for mobile bugs, we could start allowing those that everyone would undoubtedly notice and feel a need to post, based on your judgment. Bug reports still wouldn't serve much of a purpose here, but not having to perpetually revert them could be reason alone to allow the ones that keep getting reported and can be verified by someone trusted. I won't take it upon myself to say this should be done though, I'm just putting it out there as one possibility for discussion. Hopefully others will chime in on that or other possible solutions. Equazcion  ( talk ) 05:40, 26 Jun 2015 (UTC)
 * I think we've come pretty far in six months, enough to have trusted regular editors who can confirm whether widely-reported bugs in certain versions are actually true. The policy is ignored enough as it is- with the upcoming increase in traffic, we'll have a lot more people coming through to report that certain things don't work as intended- but fortunately, with a large enough sample it should be a lot easier to weed out false positives and nonsense.
 * Additionally, I voiced my concerns at the time that the possibility of bugs becoming long-term functionality still existed, and unfortunately that seemed to come to pass, as many bugs remained in the mobile versions for a very long time, particularly the rarity of Vitamins and similar debuff-immunity items. The Ankh Charm and associated items are very common and high-profile accessories for players of all types, and unfortunately I'd have to admit that as a wiki, we failed in our primary responsibility of conveying accurate information to players for a distressingly long period of time. It's worth considering letting up on the policy a little bit. Bugs definitely need to be controlled and vetted in some way before they're placed in public view, but it's looking strongly like the effects they have on game functionality can't just be ignored or deferred elsewhere- especially if everyone's encountering them. Gearzein (talk) 06:04, 26 June 2015 (UTC)
 * These posting will be in public view immediately, as people post bugs to whichever article they feel they apply to. Preempting bug postings by directing people elsewhere via an interface message has not, as we've seen, been completely effective (although it has cut down on bug postings drastically, I think, if you compare to the volume we used to get). We could move posted bugs off to a temporary holding page for verification as they come, but that's not much better than reverting, as we would still need to perform the move each time, and people will still re-post the same bugs to the articles after they're removed, since they will not know this had already happened.
 * Once we accept that people will be posting bugs in public view immediately: Our choices are whether to revert them or let them be. It's a nice ideal to say we can simply allow bugs that most of us regulars think are accurate and widespread, whilst reverting others that we don't, but in practice that doesn't seem like it would be quite as simple as it sounds (in my mind). It would be difficult to revert some bug postings on the grounds that "I haven't seen this so widely reported yet and/or I think most of us wiki regulars haven't experienced this bug yet and/or I don't think this bug is as important as the others you can see we've allowed; so I'm removing it" (an exaggerated way of putting it, just to illustrate the potential difficulty and the way those reverts might be interpreted, rather accurately, despite any careful wording we would choose).
 * Whichever solution we put into practice should include some way to show consistency, for example via a policy, or an individual decision-maker to appoint per platform, or else hold a discussion for each new bug that appears, hope that several people participate each time, and then have that saved discussion to point to as rationale for reverting a particular bug in the future. Equazcion  ( talk ) 06:45, 26 Jun 2015 (UTC)

That said, I made that rather long reply late at night and may have overcomplicated things. I agree a bug like Ankh Charm ingredients being rarer than intended (if that was the bug you refer to) is something that should be on the wiki if true. It's one of the rare examples, though, of a useful bug report as far as the wiki is concerned. I almost never see bugs like that posted, ie. important malfunctions that could cause wasted time and headaches if players aren't made aware. I actually don't remember seeing anyone post this particular bug. If it's accurate then it's good that we're discussing it now and can decide to allow it on the page. However, the current bug policy would actually already allow for this particular example. The remaining question is still whether not to revert the more minor glitches, misquotes, and exploits in the future, and if so how to decide practically which stay and which go. Equazcion ( talk ) 13:30, 26 Jun 2015 (UTC)
 * So it sounds like the standard I suggested (harmful and repeatable) is closer to current policy than I realized. Perhaps all that is needed then is better clarity about when it's allowable to post bugs. What if there was a rule that bug reports must include a link to a TCF thread where the bug in confirmed either by a staff member or a clear consensus of users?— BlueMana (talk) 14:42, 26 June 2015 (UTC)
 * I think that's actually a pretty good idea. Harmful, repeatable, and including a link to confirmation or consensus at the official forum; and in the policy I suppose I'd explicitly specify that "harmful" includes things that merit warning in order to help players avoid a severe annoyance, as in the Ankh Charm example. What do we all think of that? Equazcion  ( talk ) 17:34, 26 Jun 2015 (UTC)
 * PS. We just got another one of these. As a separate issue, are we still addressing the possibility of allowing exploits or minor bugs that get posted perpetually? Equazcion  ( talk ) 17:51, 26 Jun 2015 (UTC)
 * This sounds workable- it's largely the same policy we had previously but the meaning of "verifiable" is hopefully clear enough to act on. As for the door of the Jungle Temple, I was under the impression that was fixed, but even if it's still around, it could be considered to present somewhat of a risk to new players who may try to breach an otherwise indestructible structure before they're prepared. If phrased properly- as a warning similar to the one that Lihzahrds spawn prior to Hardmode rather than an exploit or sequence-break- it'd be worth considering. Gearzein (talk) 19:57, 26 June 2015 (UTC)
 * They announced it was fixed on Google Play and iOS. Amazon still doesn't have that update, so I suppose it could be Amazon users who are still reporting it; or else they thought they fixed it but they didn't. In any event, we still don't really know how to handle repeated minor bug reports in the future. KM100 did bring up the point that it gets tiresome reverting the same bug repeatedly that he can personally attest to. I suppose we'll have to continue doing that for now though, since no consistent alternative is apparent yet. Equazcion  ( talk ) 20:52, 26 Jun 2015 (UTC)

Global file usage
Greetings from Russian wiki. I want to ask you about the service (absolutely all). When you delete files on your wiki (English section), please check the use of the file in the other language sections of Terraria Wiki. This is necessary to avoid the presence of red links. If you do not already know, our wiki uses a centralized storage system overall. This means that any file on the base (English) wiki can be used in all sections of the same wiki. For example, image of File:Blue Slime.png used in the Russian wiki thanks to this system, although Blue Slime was not uploaded on the Russian wiki because it is called a direct linkas if it were uploaded - ru:File:Blue Slime.png.

Since the global usage of the file is not displayed on the English wiki, then kindly requested to check each file before deleting when used in any section Terraria Wiki.

There is another option, dear members of the Curse, set on the wiki this extension: mw:Extension:GlobalUsage. This will allow all users to monitor file usage by other language sections.

Again, administrators and bureaucrats, if you delete a file in the English wiki, please before deleting move this file in all language sections where it is used, so that no unforeseen red links. Equazcion, please do this kind of mandatory rule for all administrators. If the extension is not set, then let everyone removers checks every file on each section. Section is not too much, it will not take much time.

Thanks, good luck in filling articles with the upcoming update. Alex Great talk 05:27, 28 June 2015 (UTC)
 * mw:Extension:GlobalUsage is probably ideal. For now I wrote a script that will let us check foreign uses of images. The new link, "List Foreign Uses", should show up for everyone at the top of image pages. If it's not there yet, do a hard refresh (ctrl-F5). Equazcion  ( talk ) 12:04, 28 Jun 2015 (UTC)
 * Very useful. Thanks for support. Alex Great talk 12:51, 28 June 2015 (UTC)
 * For File:Wandering Eye (2nd form).gif doesn't work. Alex Great talk 12:56, 28 June 2015 (UTC)
 * No problem :) Should be fixed now. Ctrl-F5 to refresh javascript. Equazcion  ( talk ) 13:07, 28 Jun 2015 (UTC)

Mirrored images
I created a new template: Template:Mirror. If the community will take it, for all the images, you can specify a single standard that all such pictures should look to the right by default. I.e. some NPC files should be reuploaded (to the right). If someone is not a mirror, then the idea is failure. Alex Great talk 13:41, 28 June 2015 (UTC)
 * Or maybe specify a single standard with looking to the left. I mean that all the images looked in one direction only. Alex Great talk 13:45, 28 June 2015 (UTC)

Pedguin stream
For whoever happens to be paying attention right now:

We don't normally do this here, but I felt I had to point out that Cenx and possibly Redigit are currently offering additional 1.3 info at Pedguin's 1.3 changelog analysis stream, going on right now: http://www.twitch.tv/pedguin. Equazcion ( talk ) 14:41, 28 Jun 2015 (UTC)

Achievement section in related pages
Hi. I'm wondering, is there a guideline to follow about listing related achievements in a page ? I mean ... For example :
 * The Twins : by killing them, you'll earn "Ophthalmologist" (Xbox, PS3), or will contribute to "Buckets of Bolts" or "Mecha Mayhem" (PC 1.3).
 * Blood Moon : if you survive the night, you'll earn "Red Moon Rises" (Xbox, PS3, iOS) or "Bloodbath" (PC 1.3).
 * Angler (but also fishing) : linked to "Servant-in-Training", "Good Little Slave", "Trout Monkey", "Fast and Fishious", "Supreme Helper Minion!" (PC 1.3).

There is already a section about history of changes, but nothing about achievements. With the arrival of 1.3, it will be more important to list those ... --ChoirJ (talk) 21:56, 28 June 2015 (UTC)
 * There's no current guideline or consistent practice, as far as I'm aware. I can't see any reason not to include them on pages for items/characters that directly trigger them. Equazcion  ( talk ) 22:16, 28 Jun 2015 (UTC)
 * If you were asking how they should be listed, I would just add an item to the Notes section of each page. Perhaps later we'll devise a template and/or separate section if people think that has become necessary. Equazcion  ( talk ) 22:19, 28 Jun 2015 (UTC)

So what's the plan for the Wiki and 1.3?
1.3, being the final main update and a huge one at that is certain to cause some manner of chaos when released. So with two days ahead, there is a wonder if there is some manner of contingency plan in place to reduce the mass of crossfire edits and more. 76.125.252.80 02:40, 29 June 2015 (UTC)
 * There's no need for any such panic. I know I, at least, won't just be regulating these edits, I'll be making them. All of our sysops are regular users, and all of our users are players, and we're all here because we use this resource frequently and want to contribute to it. That's how a wiki's meant to work- high traffic can never really be a negative, because the majority of users are here either to read or fill in gaps with what they know, and the ratio won't meaningfully change just because the volume does. The plan is to continue as usual. Gearzein (talk) 03:35, 29 June 2015 (UTC)
 * Very well. I just wanted to pop in, shout 'Yellow Alert, Shields Up!', to make sure there was at least something in place. I actually meant nothing by my 'panic' note in the change summary. 76.125.252.80 08:11, 29 June 2015 (UTC)

1.3 pre-release streams
Due to the fact that information from the 1.3 pre-release video streams is not anything we can verify, I'll be continuing to revert and delete this info when no good references are included. However, I'm going to trust that our admins and a few select trusted wiki regulars (you probably know who you are) are posting accurate info. For those editors: The purpose of the points above is so that we don't have a bulk of questionable material to sift through later. Of course, once the release happens, everyone can post whatever they find in the game, since the rest of the hive can then verify it immediately (more or less).
 * Please only create pages or post information for content you saw with your own eyes, or that has already been referenced to a dev posting before.
 * Keep information on new items general, as specifics may be less reliable from merely seeing a video. Remember that item and character stats you see may not represent base stats, as they may be altered my modifiers or other boosts that might not be apparent to the audience.
 * Please also continue to confine 1.3 information to articles exclusively on 1.3 content, rather than updating articles on exiting content to show 1.3 changes.

None of this applies to the Upcoming features page. That page will be moot in the next 36 hours or so (as opposed to newly created pages for individual items, which will serve as their permanent wiki pages), so I think we can relax the standards at that particular page somewhat. Equazcion ( talk ) 10:38, 29 Jun 2015 (UTC)

"Future" Flag
It seems one of the biggest problems being faced right now is the persistence of people uploading future content on mainspace articles. Having future features on these articles is definitely a problem, but it seems sort of silly to revert all edits relating to them. So, I think this could handle that: All upcoming features on main articles could be flagged with this, until the release of 1.3, when all instances of " " could be removed via bot. This would theoretically hide them until the release of 1.3, and then reveal them with minimum hassle. Now, I'm no bot expert, so I'm unsure if this would actually work or not. Any opinions? –KM100 (talk) 17:43, 29 June 2015 (UTC)
 * The problem with future changes on main articles at this point isn't just the fact that they don't apply yet, but the fact that we don't know if they're reliable. I've been letting everyone put up new pages for stuff they saw in pre-release streams, and have been tagging those with a template/category for later review. Content within other articles might be a little more tedious to sift through later and verify -- it wouldn't just be a matter of un-commenting it. My opinion is that this should wait til info can be checked right away. While these do comprise most of our reverts at the moment, there really aren't so many of them that it's a remotely serious problem. Equazcion  ( talk ) 17:52, 29 Jun 2015 (UTC)