Anon

Can we bump this? I did many of the same steps as OP but agree that it seems to be an account issue. I had a LOT of entities loaded for a very long time and this begins my theory. I think having the entities loaded must have kicked me / caused an error on the realm instance/server which SEEMS to have resulted in my account being blacklisted from joining realms servers. My brother’s account works fine on my computer and network.

The lightning_rod.json file is the source of the error. The lightning_rod.png texture contains no specific texture for the bottom, so I suggest using the middle of the upper part's texture.

This can be fixed by replacing line 29 of lightning_rod.json with:

"down":  { "uv": [ 1, 1, 3, 3 ], "texture": "#texture" }

Mycelium wasn't mentioned in the other posts so my search turned up nothing. Why are these blocks considered transparent? It doesn't make sense.

I just had a skeleton trap spawn on a mushroom biome where I had cleared the mycilium and replaced it with grass in 1.12.2

Also noticed dried_kelp_block has texture names dried_kelp_top and dried_kelp_side instead of dried_kelp_block_top and dried_kelp_block_side

Please update list

As of 1.13, all the log, stripped_log, as well as sandstone, red_sandstone, quartz_pillar, chiseled_quartz_block, and purpur_pillar don't have "_side" on the filenames like every other block that has a different top texture.

> Throttled or not. The message is wrong and misleads error tracking.

Exactly. This causes a lot of pain to regular users, especially non technical users with the popularity of proxies and VPNs for avoiding unfair geoblocking. I spent about 25 minutes debugging before stumbling onto this thread. I kept reading "turn your VPN off" which caused me the trouble since my VPN was on originally and turning it off was causing the problem.

> Lets think it through, the throttling is so bots cant bruteforce accounts

Bruteforcing is done no matter the errors. If someone is bruteforcing to steal accounts, they will research the service and know what the error message means.

> The reason VPNs are "blocked" is because once somebody tries 3 invalid passwords on that IP, it throttles it for a hour

This is not the issue I had. I found that if my IP jumped somewhere in the world, I would be told "invalid password" immediately (first login attempt failed). The first time I then tried my password a few more times, including typing it manually and copying it from my password manager with a different clipboard which then blocks the IP for an hour.

This wasn't my issue, but 3 incorrect passwords attempts access to an account is no problem, but it needs a proper, correct error message. 3 incorrect attempts on the same IP seems very problematic, especially with common VPNs and proxies. If they are all on different accounts, there is no security lost in allowing 10-50 attempts.

This is indeed a bug, the error message is incorrect.