Seán Ó Séaghdha

It definitely happens in multiplayer. Latest server running on Ubuntu + latest client on Windows 10. Sometimes changing dimension will reset it; sometimes not. It’s a long walk in the nether to our froglight farm without it.

Also, sometimes it seems to deplete your hunger as though you were getting the effect which is especially annoying.

I migrated my account during the testing phase long ago and everything was fine. Just ran the launcher today after not running Java for a while & it updates and then refuses to log me in. This is pretty poor. An update should not completely break functionality and it should not take 6 months to (not) fix.

Are we going to have to go through this nonsense every time there’s an update?

It seems weirdly pedantic to close this bug. Maybe it’s not expressed very well, but as someone who has this bug on Android and Windows 10, it’s disappointing to see it dismissed.

This continues to happen to us intermittently and I haven’t been able to pin down a specific cause, but I can comment on some of the suggested contributing factors.

1. Old territory: we started a new 1.7 world - there is no old territory

2. Exploration: being a new world there was lots of exploration, so this could be a factor

3. Connection speed: might increase chances of it happening but also happens across gigabit LAN

4. Command blocks / redstone: although we now have some of this, it happened back when the world was new

5. Java parameters: I was running -XX:+UseG1GC -XX:MaxGCPauseMillis=200 and will try without -XX:MaxGCPauseMillis=200 though it seems a little ‘voodoo’

6. Restart: helps when logins are totally failing after this error, but sometimes the server seems to ‘recover’ on its own. It’s set to restart overnight anyway.

😉

This one has a better explanation. ;-P

It’s not a matter of whether it ‘works as intended’ IN ENGLISH. Where are your screenshots for the other 60 or so languages?

It’s a matter of whether throwing ambiguous and incomplete phrases at translators with no context (and no way of finding out the context) is a sensible way of doing things.

The OP wasn’t using 14w03a. I was trying to comment on the offhand way they were completely shut down with no real discussion. I know there are a lot of rubbish reports here, but that’s plain rude.

Your psychic powers are amazing.

Isn’t it possible the problem is actually that you can’t set r=1?

Get with the program, Talven81!

This is not a “language translation request”. It’s sad to see this bad attitude coming up again and again. A bug is a bug, even if it’s in the translation strings.

Furthermore, you’ve obviously never been to Crowdin if you think anyone ever got any response whatsoever from Mojang there.

This is an issue for all languages, including US English.

The new strings added:

• Game menu

• Edit sign message

• Now playing

The gui.achievements string and screenshot.success have also been there for a while. Map scaling and item durability aren’t normally shown (are they?) so they probably shouldn’t be part of the translation.

So this issue should be fixed for 1.7.3. Don’t worry though...I’ve found another translation mess. 😉

Yikes, this is happening to me on my home LAN! Only started happening since I set up a vanilla 1.7.2 server. Never saw this on Craftbukkit.

Oops!

<sigh>

If you just kept one of these many bug reports open until it’s actually resolved then maybe people would stop creating them. This kind of behaviour doesn’t make Mojang popular. I would love to move on to 1.7.2, but unfortunately that requires (thanks to Mojang’s terrain fiddling) opening our 1.6.2 world in 1.6.4...which we can’t do since no one can login. And yes, I know there are workarounds, but what about all those people running CraftBukkit who don’t have access to 1.7.2 yet?

Epic fail just made worse by ‘resolving’ all these bugs. Unintentional, I’m sure, but it just makes people feel utterly alienated. Not good PR.

Is is important to include a soft hyphen in that word though?

And could we get a clarification about ‘stat’? Does it mean ‘statistic’ or ‘achievement’ or both?

How is this resolved?

You’ve told one person out of all the translators that it can be done this way. I think this will be resolved when the translation string uses numbered tokens. It’s unreasonable to expect all the translators to follow bug reports.

I’m happy to pass this info on, but it’s not a very efficient way of doing it.

Still an issue in 1.7.1

Same as MC-32085 and still a current bug.