Brandon Gallegos
Assigned
Reported
Comments
long time user since the beta days.
Mojang give us a damn tool please; i’ve been able to work around this by downloading the world.
in our case 4.3gb and clearing out entity data manually to reupload a ‘patched’ file.
If Mojang could give realm owners a tool/button to ‘clear/optimize’ the realm without wasting all of our time (and your server resources) that should be a goal #1.
Tracking and debugging your codebase for the last year you keep dropping the ball on spawning and storing entity data.
Overall we all signed up for this; choosing to go rolling release cycles on paid subscriptions.
That is what kills me nowhere else would the player base take the abuse as hard as us.
Front page this as known a known issue; get ahead of the class action building every time a new person or the continued old keep reporting your issues and your fixes and solutions are making it worse.
You have never as a company accepted that old realms and large are the underlying issue.
Change the spawn algorithm to just despawn like mad when it detects a cap instead of letting the leaky code keep breaking it give us a hacky patch.
Like how hard would it be for the realm/server to start kicking out error states in the chat if detected; your giving us nothing to solve it other than a thread to pile on.
Hopefully these ideas resonate and someone sees this comment and takes action. I have loads of private feedback to give too.
Like one trick right now is to trick the crashed realm with wire shark and sending old client connect strings. Your code is buggy. 14.2 was golden and in two weeks of fun you guys locked us to a worse codebase 14.3.
Give us owners a tool to downgrade/rollback and lock realms to older versions when we experience builds this broken !!!!
worse is in the public builds you can’t cross play server files; so what limit overrides are you patching around instead of fixing the bugs ?
cause clear ya realm from one code base should work offline but doesn’t; only will when you manually edit out entity data and spawns before load.
even when you do this however your code gives a max of minutes before crashing from overloaded data; write the error codes to console aka the chat log PLEASE; follow in MS footstep without registry errors on crash our feedback is pretty moot.
We need more controls over the software we paid and continue to pay over for.