Minecraft Wiki talk:Issues/Weekly 12w17a

Spelling and case quibbles
x Oakwood, pinewood, and sprucewood are single words. Spelling them with a hyphen like they are in the names for the oak, pine, and spruce wooden slabs is improper for this reason. "Jungle-Wood" is fine because "junglewood" is not even a proper word.
 * This is an extremely, extremely trivial annoyance. Not a bug--Moxxy 20:46, 26 April 2012 (UTC)
 * No, misspellings and even incorrect letter cases are bugs. Please don't downgrade genuine bugs to annoyances, because annoyances are not bugs. However, checking in an actual dictionary, oakwood and sprucewood aren't words, which just leaves pinewood. For consistency and clarity, the way Mojang currently has it is probably the best option, although Jungle-Wood should have a lower-case W. As usages vary no one way is ever likely to be universally satisfactory.82.69.54.207 22:04, 26 April 2012 (UTC)
 * But we are not talking about obvious typos or misspellings. This is an extremely anal bug about using "correct" words from the dictionary. Everybody knows what oakwood is just as much as oak-wood so Mojang are completely entitled to concatenate it like that. I believe it is a trivial annoyance too. --Mattrition 11:17, 27 April 2012 (UTC)
 * So sorry, I completely misunderstood the issue. My belief that it is a trivial annoyance is still true, though. --Mattrition 11:33, 27 April 2012 (UTC)

Nether Portal Linkage Issue
a The first portal made in the overworld will spawn a portal in the nether as intended but subsequent portals WILL NOT. Any new portals made in the overworld will link to the first portal that Minecraft considered being the "closest" and will not spawn a portal regardless if it should have.

What that means is if you make a new portal in the nether, it WILL spawn new portal in the overworld in the appropriate coordinates. Also if you made a new portal in the nether with the appropriate coordinates to an existing portal in the overworld they will link up and function properly. (Example: I made a portal in my base that kept taking me to the communal portal exit in the nether. When I built a portal in the nether where my base's portal should have spawned, they link properly.)

This exists in single-player as well as multi-player with pure vanilla MC. Also this seems to have been present since 1.2.5, but not sure about earlier versions yet. -- KaizenNeko  ( T &#124; C )  20:51, 26 April 2012 (UTC)
 * This is intended behaviour, always has been. Lots of information here. Flagging this as annoyance, but I would prefer it removed. I think the linking is like this for very good reasons. --Mattrition 21:07, 26 April 2012 (UTC)
 * Negative, this is not working as intended. Steps to reproduce: Make a portal at 0x,0z. Enter nether. Arrive at roughly 0x,0z in nether. Exit nether & make a portal at 1024x,1024z. That portal should place you at about 128x,128z in the nether, but it's not. It places you at the 0x,0z one in the nether. Building a portal in the nether at the correct location will fix it. However, this behaviour DOES NOT appear in 1.2.4 to is is definitely a bug. -- [[File:Icon-KaizenNeko.png]] KaizenNeko ( T &#124; C )  21:15, 26 April 2012 (UTC)
 * Will retest with greater distances. [[File:Icon-KaizenNeko.png]] KaizenNeko ( T &#124; C )  21:20, 26 April 2012 (UTC)
 * Was this changed between 1.2.4 and 1.2.5? I just checked it in 1.2.4 and it will make a portal regardless of the 128 block range in the nether. However 1.2.5 will not if it's in the 128 block radius of another portal. But like you said, Mattrition, this is the current behaviour and there for not a bug. -- [[File:Icon-KaizenNeko.png]] KaizenNeko ( T &#124; C )  21:30, 26 April 2012 (UTC)
 * I've moved the whole report to the discussion for now, since the bug seems to be non-existent from both our tests. If we do indeed find that the linking mechanics have changed for the worse, we can discuss what form to relist the bug in. --Mattrition 11:27, 27 April 2012 (UTC)