mojira.dev

gil2455526

Assigned

No issues.

Reported

MC-80867 Realms GUI icons appear blank Invalid MC-75043 Invalid lang in options.txt leads to connection error Fixed MC-36628 Closing inventory sometimes reset music loops Duplicate MC-36377 Jukeboxes infinitely loop record, even after being broken. Also, music overlap. Duplicate MC-30194 World doesn't load! Invalid MC-29655 Crash during cross-dimention respawn Invalid MCL-1394 Custom Directory not used when using old game versions Awaiting Response MC-1906 Bugged torch hitbox on slabs Duplicate

Comments

Also affects half filled dyed water cauldrons.

Upon further testing had one instance of this same bug still present, three instances of Launcher crash and two of success. Requires further testing.

Post the crashlog located at \.minecraft\crash-reports The most recent, please.

Not really a bug, Minecraft takes some seconds to synchronize client and server, and in the meantime the server is taking into consideration things that happen to the player

Just saying, even large minecraft servers don't use more than 4 GBs of RAM...

have you checked the volume of player sounds (Minecart sounds are controlled by that)

This is not a place for questions or support. Also, you are not telling WHERE it says there is a mod.

You are not describing the issue...

I think I know what's happening. When the chunks turn into lazy chunks, for some reason the redstone stops updating but the hoppers still move items around.

Can confirm in creative following this procedure:

1. Spawn a named mob using commands. Eg. /summon Skeleton ~ ~ ~ {CustomName:"Skelly"}
2. Go 150 - 200 blocks away from it.
3. Go back to see it gone.

Migrated accounts use the email now. It's safer.

I guess by "lagging" you mean players with high ping?

Updated crash report and dev console with 13w36b

The thing is, I did. Right after a working one. It just stops. No saving chunks, no loading, nothing. Not even chat works.

Dev console added, even loaded a working world for comparison.

Ok, I loaded the wrong one at first...

Posting the crash report would be of great help.

That would be useful, but I believe it's more of a new feature than a bug.

It did save, but the date of last play was wrong. Check MC-17830

Duplicate of MC-17830

I think I know why it happens, the game doesn't check if the door is still valid without a block update.