Guybrush Threepwood

Shouldn't this work on it's own anyway? Maybe the problem is how you save it. Are you moving/copying a temporary copy of the file on top of the file to write to it? Just guessing here, could also just be a weird java problem.

affects 29b

To clarify this a bit: data 0 is the all-spore now again ( at least for the red huge mushroom, didn't try the brown one ), but the huge mushroom structure drops the all-cap blocks now. So the old blocks stay the same, but are no longer obtainable. Better stock up on them if you play some kiddie server 😛

(tested in 14w28b)

I doubt it. There was an all-cap available the whole time already (metadata:14), so you would effectively just remove the corresponding all-spore (data:0) when you replace their texture with the all-cap one. Either way it would be a bug.

Seems to be fixed in 14w18a, but now I have different issues.. [MC-47513]

this is clearly a configuration issue. you should close this.

this is now merged in upstream: https://github.com/LWJGL/lwjgl/pull/66

now we just need mojang to ship a nightly build for the linux users. (which is one of the reasons why they have the new launcher; they did the same for the max users not a long time ago).

let's hope they find this thread at some point .. in the future

just edit the corresponding verions/<mcversion>/<mcversion>.json and place your new library in the library folder

Good to hear this! I tried talking to them on IRC, but sadly there wasn't much activity. I didn't just want to create a bug report, as I was not sure if it is definitively a LWJGL bug.

Also, I just tested it with Terasology , a open source minecraft clone also using lwjgl, and I get the same problem. So it's either a lwjgl bug or a jre/openjdk bug. I will try to talk with some of the lwjgl developers about it, since it seems like you can't expect ANY support from mojang.

Hey, I just found this post on the minecraftforum about the issue. http://www.minecraftforum.net/topic/1780873-minecraft-resets-refresh-rate-to-60hz-upon-quit/
You should probably edit the title of the issue, as it not only affects 120hz monitors.

Haha, ok, if I use the ingame fullscreen option the game immediately sets the refresh rate to 60hz (I think it re-applies ( ? ) the settings to every monitor, as my 2nd one also flashes because of a resolution/refresh change) and then kind of crashes and leaves me with a minecraft window that doesn't render properly anymore. (1.6.4)

I suppose this metamodes option is nvidia-exclusive (never heard of it)?
I'm running the game windowed (kind of borderless windowed) with awesomeWM and I'm not using a display manager. I only get the 60hz framerate reset (also with older versions, not just 1.7).

Maybe you should update the description of the bug report report to reflect that it only affects specific multi-monitor setups?

Devin, do you have multiple monitors with different refresh rates? Maybe that's part of the problem?

me: 120hz main, 60hz 2nd

affects 14w05b

Yes, they still spawn and they still don't work.

affects 14w02b

Yes, I also suspect LWJGL to be the cause of this, as I can't see why Minecraft should do this by itself. Still, that's only a suspicion. And, no, I don't use any other LWJGL games. Still, the problem affects Minecraft, so I'm reporting it here. That's probably the best way as Grum is also involved in the LWJGL community, if this should be a LWJGL bug.

As this only happens with Minecraft and because Devin get's the same quirky behaviour with a complete different setup: No.

Just to clarify:

Minecraft 1.7.2
OpenJDK Runtime Environment (IcedTea 2.4.3) (ArchLinux build 7.u45_2.4.3-1-x86_64)
X.Org 1.14
Mesa 10.1 - r600g