Keith

Images are attached to the file.

Hi Mark. I did some more digging outside of the debugger itself and discovered there was a problem with worldguard plugin that had hopper/chest accessibility denied for all regions even if none were created. Turning that to allowed fixed the hopper issue on my server.

On a side note, redstone does not appear to be functioning for anyone on the server. I took two screenshots for this and attached them.

Thank you.

The bug is still in 1.16 pre-6. How to reopen this report??

This happens on Nintendo Switch as well. It's extremely frustrating.

I can see how this is a duplicate; however, there is no mention of the lectern in the description of MC-120986. Will someone with access add the lectern to the list of affected blocks in the description?

Since the vast majority of realms die out from inactivity owing to grief 99% of realms will never grow to the size that yours has. For this reason I don't believe this will ever be a priority for Mojang to tackle. With that said you are correct, the crashes are clearly owing to high file size. My own suspicion is that it has to do with autosave. You probably noticed that around 1.3 Gb you begin to get lag spikes every 20-30 seconds...you can almost set your clock by them. I believe the server is trying to do an autosave at this time. At around 1.5 Gb the autosaves begin to take long enough that I believe they are overlapping? Crashes become very common around this stage. At 1.6 Gb the game will crash within 1 min of restarting from the previous crash making the game completely unplayable. The only course of action at this point is a reset.
My Suggestions:
#1 Offer a higher tier of realms with better hardware to handle a growing realm. I would be willing to pay $50-75 a month for such a service especially if we could add another 5 or so players.
#2 Alternatively Mojang could release DS software as they do for java so we can run our own servers.
#3 A temporary fix but they could add a Reset The End and Reset The Nether button to shrink file size for awhile.

You are not alone, there is another bug report here describing this issue MCPE-12347

Confirmed in 1.0.7 on realm. Full protection IV unbreaking III diamond armor. 1 Blaze is able to 1-shot me. You never see the projectile in these cases. I hear my armor break (in this case chestplate, leggings, boots, and some durability taken off the helmet) and I am dead.

Confirmed in 1.0.5

This happens maybe 15 times a day on my realm. Crash if often due to someone changing dimensions (to the overworld, nether, or the end). The realm is nearly unplayable. This is confirmed to still be a problem with 1.0.5. I don't know if this is related but there is also heavy lag spikes every 20 seconds or so.

Confirmed on MCPE Realm. 1.0.3 Being near the spawner will make this more likely to happen but they can one shot you anywhere. You hear all your armor break (even diamond Protection IV) then you're dead.

Confirmed for 1.10.

Confirmed for 1.9.4.

@Henry Walker I am the server owner/admin. This is a problem with the game itself, not my sever.

No, non-opped players definitely can run all commands through the signs (not just ones they could use in the command line) outside of spawn chunks. For example, I once built a store that used these signs to purchase, (the store had to be outside of spawn chunks) and the sign itself used a /setblock command, which ran a line of other command blocks.

Edit: this comment was directed to Tan Chin Cheern. I agree with Skylinerw. I also just tested this in 1.9.4 by deoping myself, leaving spawn, running a command through a sign. I haven't heard anything about this, so I doubt it's been fixed in any recent update.

I thought about that, but I couldn't come up with any conceivable reason that would be the case. And even if it was, why wouldn't they be able to run commands that non-ops can normally run, like /trigger, /me, or /say?

Derp. Thought I was up to date, then I opened my Nvidia dashboard and realized I wasn't. I'm pretty sure this will fix the issue. Thanks, brotha.

Confirmed in 1.9.1-pre1.

Would you mind updating the affected versions for MC-15567 since this is still an issue?

Blah, I just tested this in 14w30c and it's still broken.

In creative, I right-clicked on a spawner with a ghast egg. The ghast is still displayed outside of the spawner.