starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-24 21:56:01 +03:00

[GH-ISSUE #2509] [Rust + 7DTD] Check if oxide is up to date before downloading #1843

New issue

Open

opened 2026-02-27 02:59:19 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 02:59:19 +03:00

Owner

Originally created by @sasjafor on GitHub (Sep 14, 2019).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2509

User Story

As a server owner, I want mods-update to check if oxide is up to date before downloading so that it doesn't unnecessarily download oxide every time the command is run.

Basic info

Distro: Ubuntu 19.04
Game: Rust
Command: mods-update

Further Information

The version of umod/oxide can be retrieved from this URL: https://api.github.com/repositories/94599577/releases/latest . The name field contains the current oxide version, which could then be stored by LGSM and compared before downloading.

Originally created by @sasjafor on GitHub (Sep 14, 2019). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2509 ## User Story As a server owner, I want mods-update to check if oxide is up to date before downloading so that it doesn't unnecessarily download oxide every time the command is run. ## Basic info * Distro: Ubuntu 19.04 * Game: Rust * Command: mods-update ## Further Information The version of umod/oxide can be retrieved from this URL: https://api.github.com/repositories/94599577/releases/latest . The name field contains the current oxide version, which could then be stored by LGSM and compared before downloading. ## Further Reading I'm using this plugin https://umod.org/plugins/smooth-restarter, which also checks that field.

kerem added the

labels

2026-02-27 02:59:19 +03:00

kerem commented

2026-02-27 02:59:20 +03:00

Author

Owner

@issue-label-bot[bot] commented on GitHub (Sep 14, 2019):

Issue-Label Bot is automatically applying the label type: feature request to this issue, with a confidence of 0.82. 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 (Sep 14, 2019): Issue-Label Bot is automatically applying the label `type: feature request` to this issue, with a confidence of 0.82. 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 02:59:20 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Sep 16, 2019):

From what I remember there was no practical way to check the version of oxide has updated so the updater simply downloads it every time. This comes down to how the mod is distributed. The mods command does need to be revisited and refactors. This request will be looked into when the refactor happens.

@dgibbs64 commented on GitHub (Sep 16, 2019): From what I remember there was no practical way to check the version of oxide has updated so the updater simply downloads it every time. This comes down to how the mod is distributed. The mods command does need to be revisited and refactors. This request will be looked into when the refactor happens.

kerem commented

2026-02-27 02:59:21 +03:00

Author

Owner

@h3o66 commented on GitHub (Sep 13, 2020):

I think this could be used now, if we now use the version from the github releases, there could be done a version check.

Edit: if this aleady done then as well for 7 days to die

@h3o66 commented on GitHub (Sep 13, 2020): I think this could be used now, if we now use the version from the github releases, there could be done a version check. Edit: if this aleady done then as well for 7 days to die

kerem commented

2026-02-27 02:59:21 +03:00

Author

Owner

@h3o66 commented on GitHub (Sep 13, 2020):

Connected to #2768
oxide == umod

@h3o66 commented on GitHub (Sep 13, 2020): Connected to #2768 oxide == umod

kerem referenced this issue

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

[PR #1843] [CLOSED] Adding debugging information #3414