Known bugs/formattest

[edit] RETURN TO KNOWN BUGS TALK PAGE HERE

CLICK TO RETURN TO WHENCE YOU CAME AFTER READING

[edit] THIS PAGE IS A TEST..

[edit] THIS IS EXAMPLE 1 - with subpages

Version history also contains bugs that aren't listed on this page.

Bugs and feature requests can now be logged at Get Satisfaction: Mojang.

Notch will focus the Beta 1.6 update on bug fixes. He will be going through several bug lists, including this one, and fixing the bugs mentioned. 1.6: Maps and huge bug fix release: http://notch.tumblr.com/post/4988431144/the-maps {EXAMPLE STARTS HERE}

[edit] ALL Bugs)

[edit] General

General was too long to use as example ... All bug examples below lead to the same example page, this is just a mockup of how the result might look, so just click one after you admired how short the short description is...

[edit] Achievements

Main article: Achievements#Bugs

• Hoe and sword achievement not triggered with stone version
• Throwing leather on the ground earns the achievement for killing a cow.
• wood gained by creeper damage gives "Getting Wood" achievement.

[edit] Audio

• On "Fast" graphics, no rain sound (Confirmed)
• The openAL32.dll and openAL64.dll that come with Minecraft do not work properly.

[edit] ETC

• another short description here
• ETC ...

[edit] End Of Example 1

lorum ipsum

[edit] THIS IS EXAMPLE 2 - without subpages

Version history also contains bugs that aren't listed on this page.

Bugs and feature requests can now be logged at Get Satisfaction: Mojang.

Notch will focus the Beta 1.6 update on bug fixes. He will be going through several bug lists, including this one, and fixing the bugs mentioned. 1.6: Maps and huge bug fix release: http://notch.tumblr.com/post/4988431144/the-maps {EXAMPLE STARTS HERE}

[edit] ALL BUGS

[edit] General

General was stil too long to use as example ... All bug examples below lead to the separate headers in this same page, again this is just a mockup of how the result might look, so just click one after you admired how short the short description is... and judge how this page may be with a table for every entry.

[edit] Achievements

Main article: Achievements#Bugs

• Hoe and sword achievement not triggered with stone version
• Throwing leather on the ground earns the achievement for killing a cow.
• wood gained by creeper damage gives "Getting Wood" achievement.

[edit] Audio

• On "Fast" graphics, no rain sound (Confirmed)
• The openAL32.dll and openAL64.dll that come with Minecraft do not work properly.

[edit] ETC

• another short description here
• ETC ...

[edit] ALL Bugentries =

This needs to auto collapse in the TOC .. how do I do that again??

[edit] General

skipped

[edit] Achievements

templates here

[edit] bug1

BLANK EXAMPLE

LONGTEXTEMPTYEXAMPLE 

STEPSEMPTYEXAMPLE 

NOTESEMPTYEXAMPLE  

Note: Keep in mind it's a quick test, I haven't bothered with text sizes; background colors,and other formatting and layout options YET. Also the content (which fields to use) is still an open debate, This is just an example of what's possible, and how to use it.
Click here for a reference on how to use this template

[edit] bug2

LONGTEXTEMPTYEXAMPLE 

STEPSEMPTYEXAMPLE 

NOTESEMPTYEXAMPLE  

Note: Keep in mind it's a quick test, I haven't bothered with text sizes; background colors,and other formatting and layout options YET. Also the content (which fields to use) is still an open debate, This is just an example of what's possible, and how to use it.
Click here for a reference on how to use this template

[edit] bug3

LONGTEXTEMPTYEXAMPLE 

STEPSEMPTYEXAMPLE 

NOTESEMPTYEXAMPLE  

Note: Keep in mind it's a quick test, I haven't bothered with text sizes; background colors,and other formatting and layout options YET. Also the content (which fields to use) is still an open debate, This is just an example of what's possible, and how to use it.
Click here for a reference on how to use this template

[edit] Audio

[edit] bug4

LONGTEXTEMPTYEXAMPLE 

STEPSEMPTYEXAMPLE 

NOTESEMPTYEXAMPLE  

Note: Keep in mind it's a quick test, I haven't bothered with text sizes; background colors,and other formatting and layout options YET. Also the content (which fields to use) is still an open debate, This is just an example of what's possible, and how to use it.
Click here for a reference on how to use this template

[edit] bug5

LONGTEXTEMPTYEXAMPLE 

STEPSEMPTYEXAMPLE 

NOTESEMPTYEXAMPLE  

Note: Keep in mind it's a quick test, I haven't bothered with text sizes; background colors,and other formatting and layout options YET. Also the content (which fields to use) is still an open debate, This is just an example of what's possible, and how to use it.
Click here for a reference on how to use this template

[edit] bug6

LONGTEXTEMPTYEXAMPLE 

STEPSEMPTYEXAMPLE 

NOTESEMPTYEXAMPLE  

Note: Keep in mind it's a quick test, I haven't bothered with text sizes; background colors,and other formatting and layout options YET. Also the content (which fields to use) is still an open debate, This is just an example of what's possible, and how to use it.
Click here for a reference on how to use this template

[edit] End Of Example 2

[edit] Conclusion, difference between two examples

Example 1 is more work, but will result in a great main page, because it wont have all the tables inline Example 2 well.. Will still result in a great readable page until you scroll beyond the list of short description links, it will just have a LOT of tables and chapters in it :D

[edit] FORMATTEST

Further below...

[edit] BLANK REFERENCE - DO NOT DELETE

LONGTEXTEMPTYEXAMPLE 

STEPSEMPTYEXAMPLE 

NOTESEMPTYEXAMPLE  

Note: Keep in mind it's a quick test, I haven't bothered with text sizes; background colors,and other formatting and layout options YET. Also the content (which fields to use) is still an open debate, This is just an example of what's possible, and how to use it.
Click here for a reference on how to use this template

[edit] VARIABLE REFERENCE

Needs to be placed in a beter place later on ..

Explanation of variables / terminology and guidelines:

1st variable = A short title

2nd variable = Full text desciption

3rd variable = Reproduction steps

4rd variable = Notes / exceptions

5th variable = our indication of the Impact (not how annoying you think it is, or how often you have this occurring)

Cosmetic = Its not affecting gameplay, but it's still a bug
Low = when it's anything between nuisance, 
  glitch or for example if its just affecting 1 or fraction of the player(s) in SMP    
  (default value)
Medium = anything substantially above low, but not game breaking,  
High = for example ; game breaking, server breaking. map breaking, 
 In general really messy bugs that affect entire maps / servers etc. etc.  - usually hard to resolve /workaround 

6th variable = SMP and or SSP ('both' when not provided)

7th variable = Version (assumes 'latest' when not provided)

8th variable = (do not use | priority AS INDICATED BY MOJANG (default value tbd - to be determined)

9th variable = (do not use) link to @Jeb_ 's shortlist , see talk page .. or any other official reply from mojang (getsatisfaction or the blog or their twitter)

[edit] THIS GOT MOVED FROM THE TALK PAGE DUE TO LENGTH

[edit] This is what i suggested on the talk page and moved here

Is it an idea to reformat this page into a more viable representation of bugs.. Right now Its a long messy list, Some bits are really hard to read .. there is no indication in impact,severity, priority, and all those nice features of a bug system, etc.. Not that we expect to have a bug system on wiki but it should be easy enough to make a template to get some additional attributes to each bug..Which hopefully will help Mojang solve it quicker in the long run.. and read and digest it to start with.. I'll try to make an example for it. Lalophobia 11:44, 4 May 2011 (UTC)

SOoooo ... anyone that knows how to make it suffistocated - so the table grows for about 10 rows before it repeats the header ? and such - regardless , I got a primitive example of what I think would be useful fields

Explanation of variables / terminology and guidelines:

Moved here

As you can see in this example I tried to make it so people could simply add a bug to this list in a human way (Give it a name - just tell whats the freaking bug, and how to reproduce it, and how much impact the bug has) - and the extra variables that make sense to a developer are buried later on in the string + this will also make converting the current list a lot easier ;)

Example with the variables 1=1, 2=2, 3=3 etc. .. The numbers currently in the labels in the table were to help me figure it out.. and to show you how it works, in the final version they will obviously not be there..

Note: Keep in mind it's a quick test, I haven't bothered with text sizes; background colors,and other formatting and layout options YET. Also the content (which fields to use) is still an open debate, This is just an example of what's possible, and how to use it.
Click here for a reference on how to use this template

Example bug (picked a random one)

If you enter Fullscreen mode, then exit it, mouse clicks will no longer work for game dialogs 
(game menu, inventory etc.). However, mining and using items still work. Pressing Esc, 
waiting for the game to save and restarting the client or re-entering fullscreen to save and 
quit resolves this problem. Here is a topic on Minecraft Forums related to this bug.

example in practice

If you enter Fullscreen mode, then exit it, mouse clicks will no longer work for game dialogs 
(game menu, inventory etc.). However, mining and using items still work. Pressing Esc, 
waiting for the game to save and restarting the client or re-entering fullscreen to save and 
quit resolves this problem. Here is a topic on Minecraft Forums related to this bug.

press f11
press alt-tab
return to minecraft; it's in windowed mode by then 
reproduced: notice game menu items are unclickable 

1-mining and using items still work
2-Esc, waiting for the game to save and restarting the client 
or re-entering fullscreen to save and quit resolves this problem
3-Here is a topic on Minecraft Forums related to this bug 

Note: Keep in mind it's a quick test, I haven't bothered with text sizes; background colors,and other formatting and layout options YET. Also the content (which fields to use) is still an open debate, This is just an example of what's possible, and how to use it.
Click here for a reference on how to use this template

Let me know if you see this being a good idea Of course , the actual formatting of my example can use a boost, but it's currently a test.. and it seems to be usable ;) The only pretty big downside I can imagine right away ,is that the page will grow in length rapidly. So we may end up having to put a list of just the "Descriptive Text" titles on this page, which links to the actual bug entry - But share your ideas please..

[edit] This is what was replied before I moved it out of context

I'm just a little worried this is going to get absolutely huge. I mean, there are a LOT of bugs on the list. Also I wonder if priority/impact should be included - I'm just thinking of the crazy edit wars that might take place because different people have different perceptions of bug priority. Also not sure what the @Jeb box is for, considering I don't believe Jeb is even working on MineCraft right now. Notch is the one fixing these.

Otherwise I think this isn't a bad idea. It will probably be a lot of work to convert though.

P.S. - I absolutely agree with distinguishing if a bug is in both SSP and SMP - current layout doesn't really take this into account (you can kind of assume SSP bugs also occur in SMP, but that may not always be true)--Warlock 15:14, 4 May 2011 (UTC)

[edit] This is what I replied

I think I made some edits while you were typing that , I do realize it wont work if it's just a huge page with nothing but tables ;p

Current page = 
<index of chapters>

SSP
chapter (such as beds, mobs, etc.)
-bug 1 full text 
-bug 2 full text
-etc.

chapter 2 (such as beds, mobs, etc.)
-bug 1 full text 
-bug 2 full text
-etc.
 
SMP
chapter (such as beds, mobs, etc.)
-bug 1 full text 
-bug 2 full text
-etc. 

What I think the best solution would be

Current bug page = 
<index of chapters>
(no distinction between SMP/SSP but the chapters are still handy)

 chapter (such as beds, mobs, etc.)
- Short Description 1
- Short Description 2
- etc.

chapter 2 (such as beds, mobs, etc.)
- Short Description x
- Short Description y
- etc.

Each short description would then link to a specific header on "Bugs - Page 2"

 Bugs - page 2
<index of headings>
 each heading = same as short description

 bugs per category, but one long list anyway
 

the 2nd page may be a stupid long page of tables, because when this page loads you automatically get the bug you clicked on

+then you click the 'back' button to go back to the better readable overview on page 1

- however its probably equally easy and more friendly to maintain in the long run to make a "page 2"-like , for each category (in short; lots of options anyway, but i agree it wont work if the main page is a long list of tables)

Makes sense? Ps, sorry that this whole chapter turned out to be quite a wad of text Lalophobia | 15:52, 4 May 2011 (UTC)

[edit] RETURN TO KNOWN BUGS TALK PAGE HERE

CLICK TO RETURN TO WHENCE YOU CAME AFTER READING