Talk:Java Edition 1.13-pre5

Page creation
Please do not create a page simply because it's listed on the bug tracker. There's no point having an empty page with 0 information, it serves no purpose. --Pepijn (talk) 14:28, 28 June 2018 (UTC)


 * What I'm more concerned about is creating a page that has no content at all and is not useful to readers at all, such as how this page was when it was created initially. As you can see, I tried to turn it around to make it a somewhat useful article - but I do agree that there's really not much point of having a page simply because it's listed on the bug tracker.-- Madminecrafter12 Orange Glazed Terracotta.png to meLight Blue Glazed Terracotta.png 14:31, 28 June 2018 (UTC)


 * You could also prepare the page in your userspace and then either move it over or copy its contents when the version actually is released. But when you created the page, it was actually already known that a 1.13-pre5 will come today (see [ this tweet]), so creating / preparing a page beforehand is justified then in my opinion. At least it's better than just creating a blank page just to be the one who created the page. | violine1101(Talk) 17:15, 28 June 2018 (UTC)


 * I have noticed that a lot of people seem to create snapshot pages "just to be the one who created the page." Personally, when I create snapshot pages, I like to put at least an infobox (version nav), a sentence summarizing the additions/changes, and a ref to the minecraft.net article. I don't usually like to create snapshot pages before they're released, but if other people prefer to, that's not too much of a problem - I just really think it would be better if they still add useful content right away - such as a version nav, a brief description of the snapshot, and a link to the tweet, rather than just one short sentence.-- Madminecrafter12 Orange Glazed Terracotta.png to meLight Blue Glazed Terracotta.png 18:09, 28 June 2018 (UTC)

DROP TABLE id_changes;
Maybe we should do something with the table. It's too wide on small screens, and this gets even worse with the siderail.

One proposal was to remove  namespace prefixes. It reduces the extent of the issue substantially.

My proposal is to use a list formatted like this:



Any comments? --AttemptToCallNil (report bug, view backtrace) 18:10, 28 June 2018 (UTC)