Mark J Nohr

@Avoma - So you built the kelp farm I referenced? I reliably reproduced the problem and it does seem to be related to  MC-89146 which is not resolved. 

Yeah that sounds good although I've yet to see this flying machine reliably stop. The mechanism depicted gets it started but when when it returns it sometimes stops but usually just turns around or just stops for a few seconds. 

I saw this flying machine from ilmango that seems to have a better on/off mechanism but most likely still suffers from the block misplacement bug when logging out -> in. And remembering to turn it off before leaving the property seems unrealistic (we are playing a game after all 🙂

https://www.youtube.com/watch?v=8kho1aVOsTo&t=555s

Are you guys from Mojang or just super helpful community members? 

All of this said, is there a workaround cuz this blows? The referenced possible underlying bug has been around for 6 years! and it's a normal level bug. 

@ampolive - Indeed MC-89146 could be the contributor to this issue.

I was surprised when I killed the drowned next to the flying machine that this issue happened (so no log off and back on required). Maybe another clue for the developers. 

Ahhh, you are right, I have the start trigger assembly one block too low. 

Aside from that the reloading issue is the main problem. See the picture. After logging back in one machine is cruising along while the other on the right has reloaded incorrectly. 

FYI. This issue caused us to stop using your service and migrated to APEX. We are finding a much better performing and more configurable world and none of this log in shenanigans. 

You have an advantage being directly associated with the game developers and shouldn;t be losing customers

Sorry, its a long string that cannot be copied and the screen shot only yields your companies' logo (maybe want to fix that also???).

I'm confident I included enough of the string and a good enough description for someone that handles the software to recognize the error. Although it is currently not happening, inability to log in for long periods of time is a too often experience that I'm sure your developers are aware of. It is a very common complaint from your customers. 

From a high level -

Please, when an issue has been confirmed and an effort has been started to fix it, update the error message presented to the users. You have many many users that will continue to not only waste their time (pissing them off), but your servers will be bombarded compounding the problem. 

Also please - proactively - notify users through discord or email, Jira - when the issue is cleared. Having to go back and check also wastes time and pisses users off.

This particular error (and logging in - in general - ) has always been an indeterministic annoying roll of the dice. There is obviously the wrong infrastructure/architecture being employed to handle the volume of player logins. I suspect there is a mojang/microsoft update on the horizon and Mojang is just putting most of their networking energy into that update so fixing bugs with a sunsetting infrastructure has been destaffed. 

Its hard to grow and even harder to migrate to become compliant with the new master. 

All users can do is continue to point at the severity of the problem.

We are considering hosting our own server because of this flaky behavior.

Sorry Im not sure what this comment means.
I tried to gathering information on the discord community help but alas there was not anyone on there able to offer more than basic knowledge. these follow-up questions ae a bit more detailed and I wasn't thinking the general community would be able to answer them.

Thanks for the response. 🙂

I found the turtles, did not move them, and only sea grass led them 15 or so blocks to a common location. Penned them in as shown in the build video. Mated them with grass and received the heart response from them. Afterwards only one of the turtles would receive and respond with heart to the grass. After many minecraft days occurred with no digging or eggs appearing I increased the pen size to 5X5 and waited several more minecraft days. When no eggs appeared I added a 3rd turtle from 15 or so block away and mated that turtle with the existing turtle that would still accept grass. Again several minecraft days and no digging and no eggs. 

Q: is there a maximum number of blocks from a turtle's original hatching block for that turtle to lay eggs?

Q: Do I have to not sleep for the turtles to lay eggs?

Q: Do I have to not sleep for turtles to hatch?

Q: Do I need to be present for turtles to lay eggs or hatch or can I be somewhere else in the realm and return?

Q:  Is there a distance I need to stand back from the turtles for them to lay eggs and hatch (like slime spawning)?

Q: Has it been confirmed by replicating what I have done here? I have found 3 videos on line specifying a turtle farm is much the same way that claim to work. 

Tough bug. I can connect now. It did fail to connect once and the message was different in that is was RED. 

A lot of us are wondering what the root cause was. Was it a configuration of source under your control - is it something that won't happen again?

I'll ask again (since my comment was deleted). In the future can you adopt a policy of 1st insuring the error message displayed to the user indicates if it is a server side issue? Almost all of the users 1st wasted time verifying their installation and firewall settings.