mojira.dev

Josh Krauth-Harding

Assigned

No issues.

Reported

MC-76130 Out of RAM, with lots of RAM available Invalid MC-75336 Missing a few folders in assets (but those files are still used?) Invalid MC-65867 Some enchantments not working? Duplicate MC-64647 Can't add effects to beacons Duplicate MC-64557 Server crashes for no apparent reason Duplicate MC-64064 Picking up drops while inventory is full destroys the dropped item Duplicate MC-62185 Whitelisting broken Fixed MC-60164 Trapdoors switch sides, although their hitboxes remain Duplicate MC-57597 Ocean sound not playing Invalid MC-57492 Repeaters/Comparators face opposite way of placed. Duplicate MC-57174 Cannot place lily pads correctly. Duplicate MC-57111 Fire animation missing Duplicate MC-55793 No slimes spawning Duplicate MC-55262 Monsters don't spawn at night Duplicate MC-55261 Whitelist Broken? (NOT OFFLINE) Invalid MC-55182 Whitelist Broken? Duplicate MC-40371 New Minecraft Music Only Plays on Menu Screens Works As Intended MC-37422 Bed's Textures Messed up Duplicate MC-35553 When joining a server: "Logging in..." forever Duplicate

Comments

Thanks for the heads up, though I should mention that I'm not using a resource pack. Maybe that's a bug in itself?

Thanks for the heads up. Could you explain what it means for them to be hashed/how I can get to them (if I can)?

Confirmed on our server.

@Sonic – thanks!

@Blah - I'm not seeing any messages from the Server Watchdog function. I'm not sure that that's our problem.

Error is the Internal Exception: io.netty.handler.timeout.ReadTimeoutException - but I'm not sure that's the bug (as in I'm not sure that it's duplicating MC-34947).

I genuinely don't know what's not working. In the console here, I have two different players in which I unwhitelisted, then whitelisted again. Both had different outcomes:
18.07 15:53:08 [Server] Server thread/INFO [MegaPixelPerfect: Added EmmetsChild to the whitelist]
18.07 15:53:02 [Server] Server thread/INFO [MegaPixelPerfect: Removed EmmetsChild from the whitelist]
This worked fine, however:
18.07 15:53:48 [Server] Server thread/INFO [MegaPixelPerfect: Removed Wintersami from the whitelist]
Then: http://i.gyazo.com/97a7eee4371c26b5525527b2ea063959.png - Click to view direct image.
(For some reason the error message is no longer showing up in the console, so I took a screenshot from where I was doing it in game).

This made me think, however. Maybe the issue is something in game, so I tried the same process in the console. The same effect happened, however, I only got italicized meesages in-game, no response in the console whatsoever, I also did NOT get an error message when adding Wintersami, the player I was having trouble with. Nothing at all.

@Kumasasa, I wasn't sure how to find the server.log, but I can show you what the console says: 17.07 17:04:02 [Server] Server thread/INFO Could not add Falconheart2017 to the whitelist

Can confirm - Without VBO I get around 80 fps, and with it I get around 60.

@Mlakuss - Yes, it is.

I can also confirm this! Also, glad I'm not the only one.

I too am still having this problem. Not fixed!

Something just occurred to me...
When this bug is fixed, will these repeaters go back to facing the correct direction? Because we've been doing some building with them today, and placing them in the wrong direction, and if they switch back tomorrow or whenever it is fixed, we might have a problem..

Also confirmed.

Can also confirm.

Can confirm that this is happening both in slime chunks and in swamps. Haven't seen a single slime in either... help?

Yep, having the exact same issue.

I know in 20a there was a bug where no hostile mobs would spawn, which was immediately fixed in 20b. Perhaps whatever was keeping them to spawn is now keeping slimes from spawning..?

Anymore help? It's looking like the players already whitelisted are able to log onto the server.

Online mode is enabled which I assume means the exact same thing as offline mode is disabled.

@Blah – Yes, I am able to go into server.properties.

Also keep in mind that this happened randomly. 4-5 people were whitelisted before it stopped working.