Minecraft Wiki talk:Community portal/Archive 14

Using categories for Edition-specific info
I've been reading back through some of the archives here, to get a feel for how the Edition-specific information has been handled in the past. I've seen a lot of suggestions come and go over time, such as utilizing namespaces to separate out the Edition-specific info, or using sub-pages, etc. None of these ideas were meritorious, as they would have required duplicated effort &mdash; multiple copies of the same information about blocks, mobs, etc. What I haven't seen in the archives is a suggestion for using categories for this purpose instead, so I thought I'd propose it here, and see what people make of the idea. By tagging a particular page with a category, such as Category:Blocks available in Pocket Edition, or Category:Mobs available in Xbox 360 Edition we can simplify the management of lists of features that are currently available for a specific Edition. Such categories would become sub-categories under their respective headings, both under and under, for instance.

With the establishment of the Project, I am hoping that there can become a unified, standardised way of dealing with Edition-specific information on the Minecraft Wiki. Using categories is just one suggestion to assist this goal. Any input, advice, comments, opinions, and criticisms would be greatly appreciated. &mdash; 10:17, 22 July 2013 (UTC)
 * The big problem with using categories for that is that categories are per-page. There's a lot of cases where version-specific info is basically an aside in a page which is mostly general.  (For example, Blazes dropping glowstone, or the Ender Dragon's missile attack.)  There are a few version-specific pages (Nether Reactor comes to mind), but those are really the exception. -- 13:07, 22 July 2013 (UTC)


 * You're quite right, and I have other ideas for highlighting minor differences between the Editions on a single page. This idea was more targeted at dynamically building a list of features that are available in each Edition, rather than trying to maintain static lists. See the Project for details of ways to highlight in-text information. &mdash;  21:50, 22 July 2013 (UTC)
 * I agree with the idea. It seems very appropriate and will make things easier on people who are looking for the information thay need. 02:45, 28 August 2013 (UTC)


 * My OCD agrees with this. Categories organized this way would make finding information easier to find.  Although converting everything to this format would be a challenge.
 * - &middot;  &middot; 23:26, 12 September 2013 (MST)

Curse sidebar crashing Firefox for Android?
If anyone else browses the wiki using Firefox on their Android phone, has anyone noticed that the curse sidebar sometimes crashes the browser? Or is it just the lousy 420MB RAM on this phone?  —  undefined 22:07, 28 July 2013 (UTC)


 * I don't think it's the sidebar. It's probably the terrible JavaScript they have running to do that floating advert thing. Even on my desktop it causes my browser to slow down, so I have a script that prevents all the non-essential JavaScript from running. – ᐸ  – 07:41, 29 July 2013 (UTC)


 * That makes sense. Can I use that?  —  undefined 08:49, 29 July 2013 (UTC)


 * As long as Firefox for Android supports extensions: http://userscripts.org/174505 – ᐸ  – 09:17, 29 July 2013 (UTC)

Merging Related Projects
Over a week ago, I proposed on the talk pages of the two projects and  that they be merged under the new  project. I have not had a reply on either talk page, so I am bringing this suggestion back to the Community Portal, to confirm this merger.

The  Project page has seen no activity since 23-Feb-2013, when it was last edited by, who also has not edited the Wiki at all since then. That looks to be the ONLY activity in this project.

The  Project page was last edited on 24-Apr-2013 by, who has not edited the Wiki since 30-Apr-2013. There are 7 contributors listed for this project. Of them, only two have accounts on the Wiki, and those two ( and ) have beebn inactive on the Wiki since September 2012.

The reason for this merger, firstly, is that has stated  that "I don't think a separate project for each edition is necessary". Secondly, having given some thought to Ultradude's comment, I can see the logic in this, and it would be easier to find all information about making the Minecraft Wiki easier to navigate for edition-specific information if it were all under a single project.

The information currently on both of these projects is essentially repeated on the Project anyway, other than the contributors list. I propose that both projects be redirected to the Project page for a period of 6 months, (in case the previous contributors return to actively editing the Wiki) and after that be removed entirely. &mdash; 13:02, 29 July 2013 (UTC)
 * .  —  undefined 21:54, 29 July 2013 (UTC)
 * Thanks for the support. I have added the merge tag to both of these project pages now, to indicate that a merge is pending, and that discussion is invited on the suggestion. &mdash; 08:26, 31 July 2013 (UTC)

News you've all been waiting for
Let's keep all the discussion on this topic on the associated talk page! Thanks! --   15:29, 2 August 2013 (UTC)

Displaytitle
Hey, would someone add the displaytitle to the wiki? It would help the translators change the title. --- Tonkku107 (|) 10:17, 6 August 2013 (UTC)
 * We won't be adding any new extensions until after the migration to Gamepedia. Remind me about it at that point. --   10:42, 6 August 2013 (UTC)
 * does work, I've done it on my userpage. The problem with displaytitle is that the resulting has to be some form of the original title.  —  undefined 21:41, 6 August 2013 (UTC)


 * Changing the setting of would allow displaytitle to do more than change case. Not as much work as installing an extension, but will still probably have to wait until after the migration. --  undefined 02:09, 7 August 2013 (UTC)


 * Shouldn't you install the extension? It would help translators and other people name the articles properly. --- Tonkku107 (|) 19:10, 11 January 2014 (UTC)

Amount of English pages in the Wiki
Because of amount of pages in English is somewhat vague. I have found no data on the topic over the wiki, so I decided to use script to count up translated pages. Besides from fact that 1212 pages are translations, it yields another interesting result: while page claims there are 2750 pages, actually there are 3116 non-redirect pages. This that English wiki has at least 366 pages without a single wiki-link. Well, the Minecraft Wiki in English as of August, 29th has 1538-1904 pages (that are eligible to be counted in built-in statistics). The list of the biggest wikis also includes (2489 content pages),  (760 pages),  (654),  (594) and  (560) language sections. I used here information from front pages of respective wikis. More data can be found (this is not guaranteed to be absolutely precise though). 21:07, 29 August 2013 (UTC)
 * I have a related query on this. Does anyone know of any way we can exclude translated pages from Special:Random? Same goes for most of the "storage" subpages like circuit schematics and such... but we can't just attempt to exclude subpages, because many subpages are "useful" ones, like tutorials. That said, perhaps there ought to be a Tutorial namespace to get around that? Hm. Anyway, the point is that honestly, Special:Random is almost useless because an infuriatingly large proportion of the time, you end up landing on a translated page or a "storage" page, rather than a "normal" page. Just thought I'd raise the issue -- 16:41, 1 September 2013 (UTC)
 * EDIT: Indeed, it would appear that this issue has been raised . At least, the language half. There's still the question of "storage" subpages -- 16:47, 1 September 2013 (UTC)

Minecraft style tooltip
Thanks to getting me the colour values, I was able to make a pretty accurate replica of the minecraft tooltips in the inventory.

I've added a script that replaces normal tooltips with these minecraft style tooltips, primarily for the grid template (although that's disabled for now, to make sure the script isn't horribly broken), but can be added to any element with the  class.

To get the title the script will first look for a  attribute, then a normal title attribute, then a normal title attribute on the first link directly within the element. You can also add a description with the  attribute, which will also convert forward slashes  to line breaks. The description requires a title (in some form).

Both the title and the description support the standard minecraft (except k), except using   instead of , for typing convenience (although I could easily support the section symbol too if wanted). Since the formatting codes are styled by just using classes (in the format of,   being the formatting code), these classes can be used anywhere. For example: Pink text. The styling works best in conjunction with the minecraft font.

Now, onto using the script. If you just want an unformatted title (maybe with a description), it is best to use the title attribute instead of, as at least then people will still be able to see the title with JavaScript disabled. However, if you want formatting in the title, you should use  with an unformatted title attribute. If you add formatting to the title attribute, it'll still work, but in cases where JavaScript is disabled, the formatting codes will show up in the title.

Here's some examples: (hover over them)  <span class="minetip" title="Test">

<span class="minetip" title="Test" data-minetip-text="This is some lengthy description/Which spans multiple lines/&dAnd supports &oformatting!"> <span class="minetip" title="Test" data-minetip-text="This is some lengthy description/Which spans multiple lines/&dAnd supports &oformatting!">

<span class="minetip" title="Not so formatted :(" data-minetip-title="I have a &bformatted&f title!" data-minetip-text="This is some lengthy description/Which spans multiple lines/&dAnd supports &oformatting!"> <span class="minetip" title="Not so formatted :(" data-minetip-title="I have a &bformatted&f title!" data-minetip-text="This is some lengthy description/Which spans multiple lines/&dAnd supports &oformatting!">

If you don't like the minecraft tooltips, or perhaps you're on a browser such as Opera which places the link URL into the tooltip, with no way to remove it without removing the link, you can add  to your userjs (or run   in your console to test it on this page), which will revert back to using the native browser tooltips, however it retains the multi-line description, so you're not missing out on information (just formatting). (FYI, I plan to create a "script options" script at some point, so things like this can be done through a menu. It'll save client-side though.)

Please test this script in your browsers, so I can enable it for the grid template. When it is, you'll still have to wait until the lua version for proper support of this script (requires additional syntax). In the meantime, you can use the title parameter of the grid template, but formatting will still look bad with JavaScript disabled.

Here's a screenshot for reference to how they should look: http://matt-russell.com/images/sharex/2013/SS_09-14_11-49-28AM.png <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px> – 15:51, 12 September 2013 (UTC)


 * Examples work perfectly on my Mac, using Opera 12, Firefox 19, Safari 6, and Chrome 19. -- undefined 05:30, 13 September 2013 (UTC)
 * The examples here work great using the latest Chrome on Windows XP. <span class=nowrap> --   22:35, 13 September 2013 (UTC)
 * The examples work on Firefox/Linux, but they're awful big. -- 23:23, 13 September 2013 (UTC)


 * They're the same size as the default GUI scale in Minecraft. I could change the styling to scale around the font-size, so setting it to 8px would be the same as using the "small" GUI scale. <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px> – 01:22, 14 September 2013 (UTC)


 * Which I've now done, and updated the example image. You would change the font size by styling #minetip-tooltip with a font-size. The size must be a multiple of 8px, or everything breaks.
 * Also: Here's a test grid: <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px>  – 02:14, 14 September 2013 (UTC)

Something wrong with Minecraft Forum?
I can't seem to go onto minecraftforum.net.

It showes a SQL error. I decided to post this here since the wiki and the forum are connected. 13:54, 22 September 2013 (UTC)
 * They have been having some intermittent problems, but it seems to be ok now. I just loaded and logged in fine. --   16:42, 22 September 2013 (UTC)

New logo?
Did we just get a new logo in the top left corner? <span class=nowrap> --   04:34, 25 September 2013 (UTC)


 * Yep. It's been in the works for a while (see ). -- undefined 05:19, 25 September 2013 (UTC)


 * But when was it implemented? At the time of my original post I felt like it hadn't been there for 5 minutes... <span class=nowrap> --   23:50, 25 September 2013 (UTC)

How do I get the mobile site back?
I disabled the mobile site on my iPod and now I want it back! –Preceding unsigned comment was added by &#32;07:39, 29 September 2013‎(UTC). Please sign your posts with


 * Click the "mobile view" link in the footer. <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px> ⎜ 07:42, 29 September 2013 (UTC)

File licensing
If someone uploaded a file without setting a license, how do you set one. The files in question are and. Thanks! 14:54, 5 October 2013 (UTC)

Article of the Day/Week Idea
(Copied from at his request --  22:02, 6 October 2013 (UTC))

I noticed we don't have a random page of the day or week. Shouldn't we make it? Why? Okay, it could be automated. -  ·  · 18:51, 6 October 2013 (UTC)


 * The is a better place for this discussion. It could be done; the trick would be getting enough user involvement to pick an article for every day. -- undefined 19:01, 6 October 2013 (UTC)


 * I, for one, think this is a good idea. ~ 19:56, 6 October 2013 (UTC)


 * The big thing is that the "random pages" may include a lot of chaff -- notably, the random page link in the sidebar ranges across all languages, old version pages, and so on. -- 22:02, 6 October 2013 (UTC)


 * Yeah, I'm not sure there's any good way to completely automate it. Possibly add a hidden category to articles deemed suitable for featuring, and have it pick from those at random. -- undefined 22:12, 6 October 2013 (UTC)


 * Well, if you want to go with a whitelist strategy, then rather than walking the whole wiki for an entertainment feature, I'd suggest going by categories: Collect all members of the topic categories: Blocks, Items, Game mechanics (or whatever it's called), Environment and so on.  Add in the contents of Tutorials/, the "Minecraft Wiki" namespace itself (AIUI, Projects and Help are aliases for this), and any other identifiable groupings that come to mind.  (Open question: user pages?)  Sweep the above for child pages and include those.  Then prune:  Exclude any that are Ajax-loaded, were created (say) less than a week ago (to block vandal pages and such), or have "bad" tags/categories such as "delete", "wip", "obsolete", or "needs work".  Deduplicate as needed.  This process should be automated so the list can be automagically updated, say weekly.  --  23:06, 6 October 2013 (UTC)


 * I could start with the design if anybody wants me to. ~ 01:21, 7 October 2013 (UTC)


 * I seriously doubt there's enough interest in this to keep it going for more than a couple weeks. To gauge interest, try creating a project to nominate pages and see if people will keep adding to it after the initial interest. &mdash; &middot;  &middot; 01:36, 7 October 2013 (UTC)


 * You read my mind O-o. Use, with ARTICLE being the article of the week. ~ 01:51, 7 October 2013 (UTC)

Munin, I agree that a voting scheme is unworkable, for that and other reasons (*cough* Astroturf). What I've described is a setup which might allow an automatic random selection, and that doesn't depend on community participation. -- 01:56, 7 October 2013 (UTC)


 * My template didn't work anyways. Meh. ~ 01:58, 7 October 2013 (UTC)
 * If this is to be implemented, I think it should be one article a week. Unless it's automatic, doing it every day wouldbe rather hectic in my opinion. <span class=nowrap> --   20:46, 7 October 2013 (UTC)


 * (Could be databased in ) One more thing, the picture, it would be nice to have a main picture, and a picture, that would explain something interesting or important with that thing. Also, I think that unimplemented features should also be added, just of curiosity and would be interesting to visitors. -  ·  · 11:50, 8 October 2013 (UTC)


 * Remember, we want this to be basically automated. Finding the "main picture" for pages that have one might be doable, but picking one "that would explain something interesting", definitely can't be done automatically.  The problem with including "unimplemented features" is that those pages are serious targets for abuse (and sources of confusion) already. --  19:47, 8 October 2013 (UTC)


 * We could have a system that picks 10 or so pages from the category, and have an optional vote. This would look at the pages and their votes, and pick the one with the highest. If two or more have the same, or no votes are cast, it will randomly pick one of them. Again, the voting is not required for an article to be selected. I have no idea how to code this, but I think it's possible.   16:13, 10 October 2013 (UTC)


 * Seems like a good idea, but that might be a little to complicated. ~ 00:00, 11 October 2013 (UTC)


 * About the "main picture" thing, we could even have a separate text. Similar to a /doc page for templates, we could have a /AotW page. It could be set so if it is non-existent then it will just use the first section of a page, along with the first picture that appears.   14:05, 11 October 2013 (UTC)


 * But what about the articles that don't have images? ~ 21:16, 11 October 2013 (UTC)

All articles should have pictures, it's a great way of making the wiki look nicer, so when you see an article without images, try to upload some! :) --  undefined NL Admin  08:30, 12 October 2013 (UTC)


 * Exactly. If an article has no pictures, then it's an issue with the article, not Article of the Week.   14:57, 12 October 2013 (UTC)

Mojavatars
Back in May, I that we need to clean up the pictures used by the quote template. I've been somewhat inactive for a while, but I now have a folder of Mojavatars, both the plain ones seen at http://www.mojang.com/about and their head/square versions I made. I simply got rid of the whitespace above the avatar and then cropped the bottom to a 145x145 square (the originals are 145x217). Here's a quick layout of what I have: https://web.archive.org/web/20190712012944/http://i.imgur.com/WQLgxnb.png. I also think that the heads should keep the same facing as the original picture instead of flipping them to face right. My intent is not only to clean up the quotes, but I also think that all of the articles on Mojangsters should use their respective Mojavatars in the person template and leave the real-life pictures for their galleries. Any thoughts? }} 03:07, 7 October 2013 (UTC)


 * If you mean the person infoboxes, then I think their actual picture should stay there. Perhaps their avatar could be there too? And I do think they should face the way the picture was made. But it seems Dinnerbone's twitter pic is flipped upside down! <span class=nowrap> --   20:51, 7 October 2013 (UTC)


 * That's really my point to standardizing at least the quote template. I don't understand why we keep updating their pictures with their random Twitter avatars when they really should stay as the official Mojang avatars here. }}  04:37, 8 October 2013 (UTC)


 * The twitter images (%name%-twitter)(Most of them) are for twitter posts. Every other posts uses ether the user images from that post and/or the official mojavatars.
 * --<span style="color:#AEAEAE">undefined 13:21, 9 October 2013 (UTC)


 * Why are we differentiating the source of a Mojangster quote? It shouldn't matter where it comes from, whether it's from social media, interview, MineCon recording, or any place words and sentences can be received from a Mojangster. I'm citing consistency on this issue, and in terms of official artwork, usage of these "Mojavatars" should be the only way to mark them here. Another reason is confusion. Many people either don't use Twitter or refuse to acknowledge it exists. The random avatars that Mojangsters change to on a whim means nothing to these visitors, so if they find themselves on the Mojangster's article from their quote and find out that the image has no connection, it would definitely be confusing. }}  03:47, 11 October 2013 (UTC)

Subpages
Can you make a .js that will list all subpages of a page? ( - ) 17:11, 17 October 2013 (UTC)


 * You can use.
 * &mdash; &middot;  &middot; 17:25, 17 October 2013 (UTC)

Thanks! ( - ) 17:54, 17 October 2013 (UTC)

Minecraft changed my google.
Every time I try to go on to google it goes to a different browser and links to minecraft. how can i change it back to google? :(


 * What do you mean by "links to minecraft"? As far as I know, minecraft should not do anything to your browser. Which browser do you use?   (  - ) 08:44, 21 October 2013 (UTC)


 * Make sure you're going to Google.com. People have created malicious websites that are typos of Google.com. <span class=nowrap> --   21:05, 21 October 2013 (UTC)


 * Really? I thought it was google.co.uk .   (  - ) 08:01, 22 October 2013 (UTC)


 * I just tried .com and it redirected me to .co.uk .   (  - ) 08:01, 22 October 2013 (UTC)


 * Goggle[dot]com isn't malicious anymore. -  ·  · 09:28, 22 October 2013 (UTC)

It's probably not related to minecraft.

Maybe something changed your default browser, and the default web-page (AKA 'home page') on the other browser is a minecraft page.

To make IE your default ( Why on Earth would anyone do that? ) "Tools, Programs, Make default".

For Firefox, it's "Tools", "Options", "Advanced" and in the System Defaults, next to 'Always check to see if Firefix is the default" there's a button to "Check Now".

To set your home page(s) in Internet Exploder Explorer, it's "Tools", "Internet Options", and there's a box to put address/es in. Or 'use current'.

For Firefox, that's "Tools", "Options" and in General there's "Home Page".

(It's probably very similar in chrome or whatever, IDK, I don't use those, but I expect the options let you set your default browser and 'home page' or similar).

17:37, 22 October 2013 (UTC)


 * It's also possible that if you aren't using a legal copy of Minecraft, but rather downloaded a hacked copy, you have gotten hijacked by something malicious. You should make sure to run a malware software, like Malwarebytes, and make sure you aren't infected. Always use official sources for your downloads. --   18:54, 22 October 2013 (UTC)


 * In response to Lennbot's comment earlier, Google automatically redirects you to the URL of your region. For me google.com redirects to google.com.au. In America it would stay the same .com. <span class=nowrap> --   05:26, 26 October 2013 (UTC)

Why isn't this wiki like all the others?
So, why hasn't this wiki been required to change to the new style like brickipedia and the aether wiki were? It's just like the cutting room floor, it looks just like an old wiki. So, why isn't it like all the others if it's a wiki? 19:50, 22 October 2013 (UTC)


 * Because this is run by Curse, not Wikia, so it shouldn't be expected to look like Wikia wikis. -- undefined 22:59, 22 October 2013 (UTC)

Videos
I think that the videos should have a description in  tags. It would clear up and make it easier to find the actual dead-end pages if links were used. ( - ) 15:23, 26 October 2013 (UTC)


 * Good idea. &mdash; &middot;  &middot; 18:38, 26 October 2013 (UTC)


 * The only problem is that admins would have to do it because the videos are protected.   (  - ) 12:42, 27 October 2013 (UTC)

Those big ol' version history pages
We need to sort out how we do the version history pages. Currently we have these massive pages which occasionally have to have older versions archived to sub-pages to make them still barely usable, and when a new version is released the content from the upcoming features page is cut and pasted to the version history page, losing all the edit history. This is far from ideal in many areas. We also don't have redirects set up for every version, instead relying on the verlink template to get to the right page. This is bad for searchability (although search is still horribly broken anyway) and also means we're relying on a complicated template which doesn't actually even work correctly for all versions (and while the lua version would fix the issue of it being complicated and not working properly, redirects would still be easier and work better). If we had redirects set up we could just link to any version directly and it would get to the right place. These redirects should exist regardless of what we do.

There was about having a version namespace and each minor version will have its own page, with patches and related dev versions on the same page. Personally I don't know what the benefit of a version namespace would be, however I do certainly think separate pages would work better. I suppose in this case we'd convert the old version history pages into disambiguation-like pages. Using load-page isn't an acceptable solution (more of a workaround really), anchors won't work and you have to wait for the normal page to load with content you don't want, then have a second delay to load the content you do. So I feel separate pages may be the only viable option anyway.

If we were to go with the separate page route, I don't think it should just be for the PC versions; in which case we need to think about handling all the different editions. Of course, we could just have all the editions on the same page, but I feel that would be messy, especially since there is no relation between the version numbers of different editions. The Xbox Edition is easy as they use TU*, but the other editions have conflicting versioning with the PC edition. Should we have the PC edition take up the main name as usual, and other versions are prefixed with their edition, maybe with an about template linking them together?

Something else I'd like to solve, but it isn't that important is the duplication of content between snapshots and the final version release. I don't really know what to do with this without keeping all the extra guff that happens between snapshots that are irrelevant to the final release. Perhaps something similar to what I wanted to do with the history template where snapshot information could be toggled. However, there are editing usability and formatting issues there that need to be sorted out, which is why that never happened in the first place.

The final thing on my hit list is those awful tables. Look at this. How do I know what version all this is for? Oh of course, I have to scroll to the middle of the content. Not to mention all that wasted horizontal space and having to manually set an anchor. I say we send the tables to a fiery death and just use normal headers. Here's an I never got around to doing anything with. <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px> ⎜ 06:49, 30 October 2013 (UTC)


 * Sounds reasonable. I'd have ambiguous titles (e.g., ) point to the PC release version, with about templates linking to identically-numbered beta/alpha/classic/PE/etc. versions. Tables worked fine as long as the changelogs were relatively short; beta 1.8 is the first version that really shows the flaws of that format. They might be worth keeping on the classic/indev/infdev pages, where multiple releases have the same version number. From alpha onwards, though, there's no need to have them. -- undefined 07:40, 30 October 2013 (UTC)

I've made some mockup pages for and  which I think are fairly complete, however there are some details to work out:

1. Should snapshots each have their own page? They range from huge to tiny, so you either have separate pages with some of them being stubs, or merged pages with some of them being massive (having both isn't an option, it'd be inconsistent and confusing). Because the infobox provides very easy navigation between versions, having separate stub pages doesn't seem much of an issue, whereas massive pages cause awful loading and editing times, as well as apparently making it impossible to view/edit on some browsers. Opinions?

2. And what about pre-releases? Do we treat them like snapshots? What should they be named? Do we stop saying snapshots and instead say dev/development versions, so pre-releases can be included?

3. With versions for other editions, I can't decide what the best naming scheme is: Alpha 0.8.0 (Pocket Edition), Pocket Edition Alpha 0.8.0, Pocket Edition/Alpha 0.8.0, or ???.

4. What do we call each part of the version number (for the type field)? It looks like semantic versioning, so: ; however the "minor" versions aren't really that minor, often involving large overhauls of code, and there's always the issue of old versions which were hugely inconsistent with their version numbers.

Once these details are solved and if no one else brings up any issues, then I'd like to test this format out with the upcoming versions, and if that works out then apply it to all the older versions. We don't want to rush into splitting all this up because it'll be a right mess if we do it wrong and need to change it. <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px> ⎜ 05:26, 16 December 2013 (UTC)


 * And here's a mockup for . Doing this made me realise that we can get rid of the version part of the page, maybe rename it to Planned features and just link to the upcoming version's page somewhere, thus getting rid of the duplicated information, and the need to lose edit history when a version gets released.
 * I'm pretty sure that giving each snapshot its own page is the way to go, so I'm sticking with that
 * I'm leaning towards putting pre-releases on the same page as the release page, since the last (or only) pre-release should be identical to the released version, it seems silly to give it its own page, and multiple pre-releases generally just have bug fixes or some minor changes, so I think it's fine to show those on the release version page. It would only be a small amount of duplicated information.
 * Looking at the version naming on other wikis, I'm going to go for Pocket Edition Alpha 0.8.0. I'll be focusing on getting the computer edition pages in order first, so there'll be some time before we need to commit to a particular name.
 * I'm not really worried about the type field, I've made it optional so for now I'll just use it in cases where the type is known. <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px> ⎜ 12:24, 27 December 2013 (UTC)

The current numbered list does not look good. It needs something... tonkku107 « <small style=display:inline-block;line-height:9px;vertical-align:-3px> » 18:36, 12 January 2014 (UTC)


 * It doesn't have to, it's temporary until everything is moved. <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px> ⎜ 01:23, 13 January 2014 (UTC)

I'm not sure about that. If we put the snapshots in individual pages, it will be more annoying to see every single page, instead of seeing all the news in one single page. And it won't be more organized. Think, if an snapshot is out, it will cost a lot of time to create a new article, and the editing will be less organized. I think that we must keep the original Version History page, but organizing them in different versions pages (e.g. 1.8, 1.7) -- 23:45, 12 January 2014 (UTC)


 * Is it too difficult to open multiple pages? Some snapshots are massive and having them all crammed together onto the same page, along with the full version's history would just take us back to the mess we already have. If anything, this is more organized, as you have links to the release version a snapshot belongs to as well as previous/next snapshots and previous/next release versions, which makes for very easy navigation. It's just as easy to copy the changes onto a new page as it is to copy it onto an existing one. <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px> ⎜ 01:23, 13 January 2014 (UTC)

MsUpload
What exactly does MsUpload mean? ( - ) 17:50, 30 October 2013 (UTC)
 * Uploaded via Drag and drop in the edit bar. "Drop files here" -- ( ~ ) 18:46, 30 October 2013 (UTC)

Tekkit Server I NEED HELP
can somebody help me with making a tekkit server i want to record a series on it but i cannot because i do not how to port forward and make a server


 * I'm not sure if tekkit makes a difference but try going to .   (  - ) 17:08, 31 October 2013 (UTC)

Suggestion
Could someone see about making a script somewhat like Wikipedia's Twinkle or HotCat? It would be nice to be able to simply enable a gadget in your preferences and be able to add, categories, et cetera to pages at the click of a button, along with a single click to welcome a user. ~ 17:29, 4 November 2013 (UTC)


 * ( - ) 18:48, 4 November 2013 (UTC)


 * Why can't you just use wikipedia's script? This wiki doesn't have gadgets, though I would like them, especially once user gadgets are a thing. <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px> ⎜ 01:18, 5 November 2013 (UTC)


 * Because Twinkle has a ton of features that use pages not on this wiki. It uses pages such as, , , only to name a few. We don't have those pages on this wiki. <span class=nowrap> --   01:21, 5 November 2013 (UTC)


 * Then remove those features from the script or just ignore them. <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px> ⎜ 01:39, 5 November 2013 (UTC)


 * But if people try to use the "ARV" feature to report vandalism and that accidentally create ... <span class=nowrap> --   01:41, 5 November 2013 (UTC)


 * Then don't use that feature? <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px> ⎜ 03:33, 5 November 2013 (UTC)


 * My point is that if someone randomly started using and then used that feature thinking it would report the vandals, It would create an unnecessary page. <span class=nowrap> --   05:03, 5 November 2013 (UTC)


 * That's their responsibility for using a third-party tool made for a different site. You could do a lot worse than just creating a page, the title of which we could just protect against creation. <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px> ⎜ 08:16, 5 November 2013 (UTC)


 * I didn't know this would start an argument, it was just a suggestion. I didn't mean directly copy the script over from Wikipedia and act as if I made it myself, I meant make a script that could create a dropdown list to:


 * Add articles to categories (more like HotCat)
 * Add delete to articles
 * The right to rollback edits (something very useful, for me anyways)
 * Quickly add a welcome template to a new user's talk page (with customization options)


 * ~ 11:44, 5 November 2013 (UTC)

In terms of public acceptance, as in a script available in a public namespace, I believe this wiki does not need any special vandalism fighting scripts and we don't deal with enough categories to ever come close to Wikipedia's level. You are welcome to port anything you want into your userspace though. For a while, I had HotCat.js in my userspace, tweaked slightly for the wiki, but it works straight from Wikipedia if you wanted to use that. If you want Twinkle, you're going to have to port it to your userspace and tweak it yourself. It shouldn't be hard to comment out parts that deal with what you're talking about. }} 19:47, 5 November 2013 (UTC)


 * I tried the part about Twinkle, and it was a horrible failure. Somebody deleted it. I'll try again... probably tomorrow or the day after. ~ 23:27, 5 November 2013 (UTC)


 * I've copied the Wikipedia script into : There's heaps of work to do, it isn't even appearing yet. <span class=nowrap> --   04:14, 6 November 2013 (UTC)

Why this?
I don't understand this revision.

https://minecraft.gamepedia.com/index.php?title=Cake&diff=prev&oldid=111758

-  ·  · 11:47, 5 November 2013 (UTC)


 * What don't you understand about it?   (  - ) 18:06, 5 November 2013 (UTC)


 * This means that the normally accessible item (what you get when you craft it) is not stackable, but the block (what you get when you use the pick block function in creative) is stackable. }}  19:42, 5 November 2013 (UTC)


 * Okay. -  ·  · 07:47, 6 November 2013 (UTC)

Real-life Minecraft activities for kids
I am an educator working with 8-11 yr olds in after school and summer time programs. I am currently planning a Minecraft-themed day, in which we will bring the game to life with hands-on activities, like building a fire to roast smores and creating a village with moving boxes. My understanding of the game isn't particularly deep, though I get the basic concepts of creation and survival. Any suggestions of real-life activities I can do on this day? Thanks so much! –Preceding unsigned comment was added by ( • )&#32;18:40, 8 November 2013&#32;(UTC). Please sign your posts with


 * You're better off posting on the forums than here. Even though this is the Community portal, it is strictly for the wiki. Minecraft-related discussions in general belong on the forums. . }}  19:29, 8 November 2013 (UTC)

ID Names vs Data Values
The main reason (at least for me) the box that summarizes each block has Data Values is for commands such as /give. Since we are now changing to use the ID Name instead of the Data Value, we should put that in the box. Many of them are fairly obvious, but some are not. They can be found on the page http://www.minecraftinfo.com/idnamelist.htm, but I don't want to start on a project that really should be done consistantly throughout the Wiki. I also just realized that I don't know how to edit stuff in that box. I'm talking about the box with the picture, and then things like durability, stackability, drops, damage, etc. 12:59, 9 November 2013 (UTC)


 * I agree. (the infobox template) is protected, so an admin would need to do it.   (  - ) 14:11, 9 November 2013 (UTC)


 * Done; the  parameter can be used for this. -- undefined 20:21, 9 November 2013 (UTC)

Zipped files no longer allowed?
I tried to upload a new version of Minecrafter.zip, but it says ".zip is not a permitted file type." Why" ~ 13:44, 9 November 2013 (UTC)
 * .zip files have never been allowed. Only media files that can actually be rendered by a browser. This is noted on the upload page "Permitted file types: png, gif, jpg, jpeg, ico, svg, jpg, jpeg, gif, png, webp, bmp, ogg, mp3, pdf, sc2map, ogg, ogv, oga, flac, wav, webm." and I don't see zip in there anywhere. --   16:35, 9 November 2013 (UTC)


 * That is the entire reason I created this section. Up until about 2 weeks after the move to Gamepedia, zipped files were allowed. ~ 17:35, 9 November 2013 (UTC)


 * While it may have been possible to upload zip files, this was never encouraged; as per, the wiki is not a file-hosting service. Zip files can't be rendered in articles, so they contribute nothing to the wiki. Either keep it as a regular page in your userspace, or use a dedicated file host; there are plenty of free ones out there. -- undefined 20:21, 9 November 2013 (UTC)


 * Well... then do tags work? ~ 20:33, 9 November 2013 (UTC)


 * Ah, forgot about the section on Majr's talk page. ~ 20:34, 9 November 2013 (UTC)

Edit summaries
What does the (top) part of some edit summaries mean? ( - ) 17:48, 11 November 2013 (UTC)


 * Could you give the name of a page where you've seen this? ~ 22:54, 11 November 2013 (UTC)


 * If you mean a link to the page, like or  for example, it just links to the level 1 header at the top of the page. ~ 22:55, 11 November 2013 (UTC)


 * It means it's the latest revision. <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px> ⎜ 00:49, 12 November 2013 (UTC)

New .ogg files
So with  released, adding more music to the game, there are many .ogg files that need to be uploaded (so empty). However I do not know how to upload them, and with the whole copyright issues, it seems too risky to even try. , or anybody, I know this is not an easy task, but could you spare time to upload the new .ogg files? -- 02:15, 18 November 2013 (UTC)

Using content from the wiki
Am I allowed using content from the wiki in say, a webpage or an app, so long as no apps are shown on that Page? ex. I want to use the brewing picture, am i allowed to have ads in the app, but not show ads on any place where wiki content is? Sorry if this is the wrong place, I went on IRC and was told to come here.

-- 12:02, 19 November 2013 (UTC)


 * You can use content from the wiki as long as it follows the CC-by-NC-SA license. Any content taken directly from the game belongs to Mojang, including screenshots, so if an image carries the Mojang copyright, it's their permission you need. However, you are not allowed (by the cc license) to use any original wiki content in any project that is of a commercial nature, i.e. apps that need to be purchased, or that gain you revenue through advertising. --   12:40, 19 November 2013 (UTC)

MCW
Could we possibly create a false namespace, MCW, that could link to Minecraft Wiki namespace pages? Typing, say, MCW:AN into the search bar would be much faster than having to type Minecraft Wiki:Admin noticeboard. If anyone approves of this, I could create all of the pages myself. ~ 22:23, 22 November 2013 (UTC)


 * This is based off of . ~ 22:26, 22 November 2013 (UTC)


 * For example, MCW:AN links to the admin noticeboard. ~ 14:48, 23 November 2013 (UTC)


 * Why do we need this? There's a link to the admin noticeboard in the left sidebar already. -- undefined 17:44, 23 November 2013 (UTC)


 * I don't mean make a single page for the admin noticeboard, but for all pages in the Minecraft Wiki namespace. For example, MCW:CP for the community portal. ~ 17:46, 23 November 2013 (UTC)


 * Also in the sidebar. -- undefined 18:02, 23 November 2013 (UTC)


 * Yes, but what about the administrator guide, how to help, the welcome, the style guide, the redstone style guide, and other pages that aren't mentioned in the sidebar. ~ 18:28, 23 November 2013 (UTC)


 * We don't need a Wikipedia voting section. As for your suggestion,, but it requires Curse to perform the necessary changes internally and nothing really happened about it. You can use "Project" in place of "Minecraft Wiki" as a shortcut, such as . I personally would like the shortcut just to save four characters in edit summary links, but other than that, Project works fine. }}  08:54, 5 December 2013 (UTC)

Old diff styling
Is there a possible way to get the old yellow and green diff styling back, through scripts or preferences? ~ 21:49, 4 December 2013 (UTC)


 * Add this to your .css page:
 * {| class="wikitable collapsible collapsed"

!   padding: 0; } td.diff-marker { color: black; font-size: 1em; font-weight: normal; } td.diff-context, td.diff-deletedline, td.diff-addedline { border: none; border-radius: 0; } td.diff-context { background-color: #eee; } td.diff-deletedline { background-color: #ffa; } td.diff-addedline { background-color: #cfc; } td.diff-deletedline .diffchange, td.diff-addedline .diffchange { background: transparent; color: red; }
 * table.diff td {
 * table.diff td {
 * }  }}  08:54, 5 December 2013 (UTC)

Help getting new wiki page to show up on Google Search
After finding a dearth of reliable information on spawn chunks, I decided to create my own wiki page, using information gathered from some ridiculously technical YouTube LPers and my own experiments (in another life, I was a software developer). Any idea on how to increase the page profile in Google search? Right now, it only shows up if you do an advanced search like "spawn chunks" site:minecraft.gamepedia.com. Little Help?


 * It increases as Google looks over it's search results every once a while (a few hours to a few days, not entirley sure). Apart from page views and such obvious things, the amount of pages that link to your page is also very important for search result ranking. -- 21:03, 16 December 2013 (UTC)

Creepers
my house blown up by a creeper 3 hearts left i hate creepers anybody know what the story behind them is? 17:12 12/17/13
 * Answer: A pig got infected by a virus, and TNT developed inside the body. Pigs turned into Creepers, and then they became angry, causing a player within 2 blocks to get blown to smitherines. Just kidding, you should go to the forums. -- 17:45, 17 December 2013 (UTC)

will ps3 get minecraft on disc
i just wnt to here ppls opinion on if minecraft will be on disc for ps3.

References to the Russian section of the wiki articles
Colleagues, please view all of the substantive articles (about blocks, objects, animals) references to the Russian section of the wiki, and to report those articles where no link. Thanks in advance. Translated through yandex translate. is from Russia 13:53, 23 December 2013 (UTC)