ChE_clarinetist

Seriously, you moderators suck, censoring comments that provide a different view than your own about whether an issue is a bug or intended feature. You have no authority to decide for the developers what is intended or not, and you have no right to remove my comments arguing that what I have reported is a bug just because you are looking at 1 single instance of code from quite a few versions ago. Let the developers do their job of determining "intended feature" or "confirmed bug" and stop being so arrogant that you feel you can speak for the developers when you did not develop any of the code.

"Apparent oversight" is when something that should be changed to match other changes is not made, ergo causing strange, or "buggy" behavior. Therefore, bug report. Just say saying "I have never seen a dev confirm it is intended" may work for you to keep it closed, how about a dev "never confirming it is a bug"? By your logic that means that is also not a good argument to keep this closed, since ONLY A DEV can decide what a bug is, and NOT some random moderators and contributors to a bug reporting site basing it only on the fact that "cloud height is defined as a static value, therefore it is intended". Consider that cloud height has been at 127/128 since beta 1.8, and when OR 1.2.1 the world height was changed to 256, clouds were left at 127/128 to "allow players to build much further above the clouds".

And I can think of a very easy way to figure out cloud height since people have said it is hard-coded into the game at 127: change the definition to reference "seaLevel + 64". Or any number, 64 just preserves the current sea level-to-cloud height difference.

Not sure where my last comment went, but this is NOT a feature request. It is a bug report of an apparent oversight during development that allows players to change the base height and sea level so that clouds appear in strange locations on the new settings. I have never seen a dev admit that this unexpected placement of clouds in relation to sea level/base height is an intended feature, hence why this report should be re-opened until a dev can confirm the intended feature or resolve the bug report.

Since my issue just got linked here as a duplicate, can this be reopened now that the Customized World type was added, allowing players easy access to adjusting sea level and base height? Adjusting the sea level to 128 and base height to 16.0 (just below 128 for main land, nice island style generation) in Customized worlds causes the clouds to be moving at the surface of the water or across the lowest layers of land, which is quite distracting.

The Wiki is a player-created website with observations from the game, NOT to be taken as developer intent.

You are not a developer, so you cannot "assure that it is intended". Please refrain from speaking for the developers when you are not a developer, or even a moderator on the bug tracker.

You can't really say it was intended for clouds to stay at the same height when the customized world type came out allowing easy access to changing sea level and base height. Clouds always used to be 128, and was intended, but it sure seems like an oversight in the customized world type to keep that limit, I mean just look at the screenshots and tell me if that is "intended".

@Volki Craft
I can dispute that. I had migrated my account to the Mojang account almost immediately upon its release, so that is not the issue (at least, not the issue in all cases). I also started the my world in 14w04a, and had 2 wolves tamed in around 14w08/09, and as soon as the 14w10 series was released the wolves stopped responding to my command to stand up.

Added another vote to this issue, as it is still present in 14w11b. Most likely relating to the switch from username to UUID not being propagated to wolves/cats that were previously tamed.

Sorry, this can be closed. I thought I pressed cancel to prevent this issue from being created, and I can't figure out how to delete the issue myself for my stupidity. This is not an issue after all. Turns out I just forgot to open my inventory before punching the tree (thought I had done that, but guess not). Spruce wood works fine for the achievements.