starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-27 07:05:58 +03:00

[GH-ISSUE #2940] Minecraft Bedrock Perpetually Updates #2099

New issue

Closed

opened 2026-02-27 03:00:51 +03:00 by kerem · 9 comments

kerem commented

2026-02-27 03:00:51 +03:00

Owner

Originally created by @thelegendofbrian on GitHub (Jun 30, 2020).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2940

User Story

As a system administrator, I want to update a server when an update is available.

Basic info

Distro: [Ubuntu 18.04]
Game: [Minecraft Bedrock]
Command: [Update]
LinuxGSM version: [v20.3.3]

Further Information

When updating the game, every other update command issued results in an update which isn't actually needed. When an update is thought to be available, it states the local build is 1.16.1.2 and the remote build is 1.16.1.02, which shouldn't result in a update, but it does.

To Reproduce

Steps to reproduce the behaviour:

Install an mcbserver and start the server at least once
Issue ./mcbserver update 4 times
Notice there were 2 updates attempted

Expected behaviour

An update should only occur if there is an update available.

Originally created by @thelegendofbrian on GitHub (Jun 30, 2020). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2940 ## User Story As a system administrator, I want to update a server when an update is available. ## Basic info * **Distro:** [Ubuntu 18.04] * **Game:** [Minecraft Bedrock] * **Command:** [Update] * **LinuxGSM version:** [v20.3.3] ## Further Information When updating the game, every other update command issued results in an update which isn't actually needed. When an update is thought to be available, it states the local build is 1.16.1.2 and the remote build is 1.16.1.02, which shouldn't result in a update, but it does. ## To Reproduce Steps to reproduce the behaviour: 1. Install an mcbserver and start the server at least once 2. Issue `./mcbserver update` 4 times 3. Notice there were 2 updates attempted ## Expected behaviour An update should only occur if there is an update available.

kerem

2026-02-27 03:00:51 +03:00

closed this issue
added the
type: bug

outcome: wontfix

game: Minecraft Bedrock
labels

kerem commented

2026-02-27 03:00:52 +03:00

Author

Owner

@issue-label-bot[bot] commented on GitHub (Jun 30, 2020):

Issue-Label Bot is automatically applying the label type: bug to this issue, with a confidence of 0.55. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@issue-label-bot[bot] commented on GitHub (Jun 30, 2020): Issue-Label Bot is automatically applying the label `type: bug` to this issue, with a confidence of 0.55. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback! Links: [app homepage](https://github.com/marketplace/issue-label-bot), [dashboard](https://mlbot.net/data/GameServerManagers/LinuxGSM) and [code](https://github.com/hamelsmu/MLapp) for this bot.

kerem commented

2026-02-27 03:00:52 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Jun 30, 2020):

How odd. the update logic is as simple as if local and remote version number do not match then update. So my guess is that its getting the wrong local version

@dgibbs64 commented on GitHub (Jun 30, 2020): How odd. the update logic is as simple as if local and remote version number do not match then update. So my guess is that its getting the wrong local version

kerem commented

2026-02-27 03:00:52 +03:00

Author

Owner

@mspencerl87 commented on GitHub (Jul 1, 2020):

My Minecraft is setup to check for updates every 60 minutes.
It is constantly trying to update from 1.16.1.2 to 1.16.1.02

@mspencerl87 commented on GitHub (Jul 1, 2020): My Minecraft is setup to check for updates every 60 minutes. It is constantly trying to update from 1.16.1.2 to 1.16.1.02

kerem commented

2026-02-27 03:00:52 +03:00

Author

Owner

@mspencerl87 commented on GitHub (Jul 1, 2020):

How odd. the update logic is as simple as if local and remote version number do not match then update. So my guess is that its getting the wrong local version

Any idea which file to change in the mcbserver directories to rectify the issue?
Could one simply "rename file" ?

@mspencerl87 commented on GitHub (Jul 1, 2020): > How odd. the update logic is as simple as if local and remote version number do not match then update. So my guess is that its getting the wrong local version Any idea which file to change in the mcbserver directories to rectify the issue? Could one simply "rename file" ?

kerem commented

2026-02-27 03:00:52 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Jul 3, 2020):

Yeah looks like the minecraft devs have got the remote release number wrong which is causing the error. The logs give 2 and the remote location (zipfile name) gives 02

Update available
* Local build: 1.16.1.2
* Remote build: 1.16.1.02

There is nothing I can do to fix this. It will need to be raised with Mojang.

@dgibbs64 commented on GitHub (Jul 3, 2020): Yeah looks like the minecraft devs have got the remote release number wrong which is causing the error. The logs give `2` and the remote location (zipfile name) gives `02` ``` Update available * Local build: 1.16.1.2 * Remote build: 1.16.1.02 ``` There is nothing I can do to fix this. It will need to be raised with Mojang. ![image](https://user-images.githubusercontent.com/4478206/86488950-9bfd5a80-bd5a-11ea-9d63-b1c00035709a.png)

kerem commented

2026-02-27 03:00:52 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Jul 3, 2020):

If anyone wants to contact Mojang feel free to reference this issue. I will, however, close this as there is nothing more I can do until they fix filename

@dgibbs64 commented on GitHub (Jul 3, 2020): If anyone wants to contact Mojang feel free to reference this issue. I will, however, close this as there is nothing more I can do until they fix filename

kerem commented

2026-02-27 03:00:52 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Mar 20, 2021):

Good news with the latest update they appear to have fixed this issue

@dgibbs64 commented on GitHub (Mar 20, 2021): Good news with the latest update they appear to have fixed this issue

kerem commented

2026-02-27 03:00:52 +03:00

Author

Owner

@mspencerl87 commented on GitHub (Mar 22, 2021):

All hell (pun intended) Microsoft lol thanks if anyone had to do anything on GitHub!!! My son will be happy now.
Thanks for the update @dgibbs64

@mspencerl87 commented on GitHub (Mar 22, 2021): All hell (pun intended) Microsoft lol thanks if anyone had to do anything on GitHub!!! My son will be happy now. Thanks for the update @dgibbs64

kerem commented

2026-02-27 03:00:52 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 23, 2022):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions[bot] commented on GitHub (Mar 23, 2022): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

kerem referenced this issue

2026-02-27 03:54:42 +03:00

[PR #2099] [CLOSED] Add CS:GO Danger Zone to Gamemode overview #3490