If I'm correct this is kind of what we are aiming for. More extensibility of a similar system.
New Version Checker Mod
- Thread starter trajing
- Start date
-
The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
@CoolSquid, looks nice...I'm not sure if your license allows it so I'll just ask. Would you mind if we snatched some of the code for it? We will ofc add things on top of it, but I would think that reimplementing things that you already have coded up would be a wast
Last edited:
Okay, so I talked with the rest of the dev team. Please note that these decisions aren't final:
EDIT: Probably going to have CF integration.
- Update severity changes how much the update checker bugs you. Title Screen for basic, stop loading of MC with a click to advance screen for severe, and display in game (closable) for critical.
- Choice between YAML and JSON for how to provide version data, also probably CurseForge integration
if Squid lets us borrow his code. - Config option for modpack makers to turn off notifications before shipping the pack to their users. Please note that critical notifications still display.
- Separate versions for display and for internal purposes. The reason for this is that different modders use different formats for versions. The display version will be the actual version, and the internal one will be a simple integer, compared against the server.
EDIT: Probably going to have CF integration.
My only concern relates to "critical" notifications. There must be no attempt to bully users into updating. The mods purpose is to inform, not to attempt to coerce compliance.
Allthough, for "critical" updates - if the version checker could actually update mods with critical defects to the best available version, I'd be behind that.
Allthough, for "critical" updates - if the version checker could actually update mods with critical defects to the best available version, I'd be behind that.
That would be up to each individual mod author.
It is well beyond the purview of the mod or the team creating/maintaining it to track all the mods and their updates and rate them. If a mod author wants to flag every update as critical, they can (I'm sure the team and community will discourage it, but there's no good reason to try and stop them at a technical level). Any attempt to restrict that will bite everyone in the butt, HARD, at some point in the future.
It is well beyond the purview of the mod or the team creating/maintaining it to track all the mods and their updates and rate them. If a mod author wants to flag every update as critical, they can (I'm sure the team and community will discourage it, but there's no good reason to try and stop them at a technical level). Any attempt to restrict that will bite everyone in the butt, HARD, at some point in the future.
My response to anything involving "reinventing the wheel" is this:
The MC Modding community needs to drop its position on making a new version of a mod is reinventing the wheel.
More mods for the same thing = Competition
Competition = Innovation.
No Competition = Best Buy.
Automatic downloads with no user action are generally frowned upon. However, these critical notifications will be closable
A critical notification with a "click here to fix it" on the other hand would (a) involve user action and (b) be awesome to help extrememly out of date, not particularly technical players, get the correct version in a repeatable way. i.e. if everyone on a server (including the owner) clicks the button, everyone will be able to connect.
Except that the server it self doesn't have an gui thus the owner still need to install it manually on the server.
you also probably would need to restart the game after it has finished downloading before it would have an effect.
unless I am missing something in that case please correct me.
You are correct on both counts. A cli command ("/nvcm update") would solve the first. I don't now nearly enough about minecraft specifically or java in general to hazard a guess as to how the second could be accomplished automatically. Asking the user to restart now would probably have to suffice.
In my opinion auto updating servers are the worst thing ever.
because downloading the file and all that stuff can cause lag and having the server randomly stop when you are on line can be devastating. So if the mod is able to auto-update it should be because of an command and nothing else.
because downloading the file and all that stuff can cause lag and having the server randomly stop when you are on line can be devastating. So if the mod is able to auto-update it should be because of an command and nothing else.
I'm not going to auto update. Period. There'll be a GUI for downloads (the mod author has to provide a link for the update, and it's completely optional), and you'll just have to restart your client. I suppose servers could update through a command. The command could, in theory, use the same code with little modifications. But, then, ask Strikingwolf about how possible that is, I'm just working on the backend.