2025年3月6日實行

Effective from 6 March 2025

此公告只提供英文版。如有需要，請自行將公告翻譯成中文（或其他語言）。

==========

"This is an announcement that I hope I don't ever have to make, but I have to." Read below to see why.

After a careful and long (and somewhat hesitant) consideration, I have decided to cease support for Minecraft Bedrock Edition players on the MCMTR server, effective from Thursday, 6 March 2025.

As you probably know (either from watching my live streams on YT, or chatting with me before), we're hosting both the MCMTR and MTR Crafters Minecraft servers on the same server hosting provider. Currently, the maximum amount of resources (RAM) that I can afford to pay is 20GB, which means the TOTAL RAM used by both servers cannot exceed 20GB.

Given the increased demand of RAM for the MTR Crafters server (and to be frank, our priority for development on MTR Crafters over MCMTR), it's natural that I want to find ways to reduce the server resources used by MCMTR. One thing I noticed after attempting to reduce RAM is that the MCMTR server would always crash and then restart after certain times that a Bedrock player joins (usually around the 15th to 20th Bedrock player (including REPEATED joining of the same player - ie. player X joins, X leaves, X rejoins - counts as TWO separate joins even though it's the same player)). It is ALWAYS a BEDROCK player joining that would cause a server crash.

Actually, it's not the server crashing that causes me frustration. It's what happens AFTER a server crash that causes me a lot of frustration. After a server crash, the server will restart. Every time the server restarts, ALL trains running on the server across all lines get removed (to make sure there won't be any individual, "left-over" minecarts once the server restarts, which would otherwise affect train operation on lines with automatic operation). As a result, players would have to wait for trains to propagate the network before they can get to ride them (so in a worst-case scenario, a player could end up waiting for more than 20 minutes for a train to arrive at a platform because no train would have reached that platform before then). Now, imagine the server CONSTANTLY restarting, then nobody would be able to play on MCMTR properly, let alone ride trains - the very purpose of MCMTR.

However, to be fair, Bedrock players are NOT TO BE BLAMED for the server crashes. Since MCMTR is a Java-based server, the only reason that Bedrock players can even join is because we have installed the GeyserMC plugin (shoutout to them), which unfortunately has bugs and is therefore NOT a perfect solution for cross-platform playing in Minecraft. That said, I know a major reason why Bedrock players quit and rejoin far more often than Java players is because sometimes when you venture (either walk or ride trains) far enough, you won't see anything around you (no blocks, no terrain, only the sky) maybe due to chunk loading/generation errors. I understand their frustration; if I were them, my instinct would be to do the same.

So, given all the above, I find the ending of support for Bedrock players a necessary move. In recent years, players who bought Minecraft Bedrock edition were also getting a Java Edition account at the same time, so technically there shouldn't be any excuse for you not being able to play on Java...

Finally, as for why 6 March is the date chosen for this change? Well, it's the 5th Anniversary of MCMTR (can you believe that?!). What better day to make major server reforms, hence (hopefully) improving server quality?

Thank you for your understanding and support. Happy 5th Anniversary, MCMTR. Long live, MCMTR.

That's all from me for now. If you have any comments (or perhaps a better suggestion for me), then please don't hesitate to ask. I want more interaction in our server. I find the current level of community interaction appalling.

MCMTR server owner,

Kinson