Multimc5: Feature Request: Managed Instances

[CamJW101]

---

Hello! I run a semi-large Minecraft community where everyone uses MultiMC to play. We have a server that changes mods, versions, features, etc. fairly often. Right now, the process to update one's instance to connect to our server after a feature change look like this:

1. I make a new instance in MultiMC with the required settings, mods, and version.
2. I export the instance as a ZIP file.
3. I send the ZIP file to a discord server where the players then download it
   

   4. The players make a new instance from that ZIP file and play.

I think this process could be simplified by implementing a feature I'm calling "Managed Instances." Instead of the process above, it would look something like this:

1. I host the zip file somewhere, most likely a web server.
2. The player makes a new instance, and selects a new option to have the settings managed by a remote host.
3. When the player runs the instance on MultiMC, MultiMC downloads the ZIP file from the web server and checks for changes to the settings or files.
4. MultiMC applies the changes and starts the instance.

I think this would be great for communities looking to streamline their custom feature distributions. It would also make it much easier to identify bugs and distribute modpack bug fixes that would affect everyone. Of course the "Managed Instance" wouldn't affect player specific settings like RAM and Credentials.

Let me know what you think! I think this would be pretty feasible to add to the existing program.

[CamJW101]

I would appreciate constructive criticism and reasons as to why this is not a feature worth adding instead of 👎s, but who am I to judge?

[v3Monsta]

If I had to guess as to why people are wary about this idea, it's because there is a non-zero chance that the remote host could potentially install a malicious instance. I have no clue how an instance could be malicious-- maybe it's as simple as distributing something malicious alongside the actual instance, but there is no denying that it's possible.

What do I know though, that's just my initial reaction and I have no idea how this attack would work. I suppose you could also say that MMC already downloads stuff from remote hosts (see FTB Legacy), but those are one-off installs and isn't some random host somewhere doing whatever it wants.

[CamJW101]

That is true. I don't know how you would go about checking for malicious content. I guess there could be disclaimers as well warning people to make sure they trust the external host. That OR the distribution could be controlled by MultiMC, and settings/instances could be shared with codes generated in the Application.

[comp500]

Modpack updating would certainly be beneficial, but I think it would be preferable for there to be an Update button rather than the update occurring whenever the pack is started. This conveys the intent of the action of the button better, and means that malicious updates are easier to spot.

[Xalaxis]

It's worth noting that in the scenario @CamJW101 proposes (creating a zip instance every time there is an update and distributing it) there would be the same opportunity for a malicious file to be included in the zip whether it is distributed manually or automatically. It's also worth noting that MultiMC already has functionality for downloading a ZIP instance one-time at creation:

So I think adding a warning message with the option for the user to tick "I trust this source" should be enough to allay any concerns, it's the responsibility of users (and in the case of CraftForge, Curse) to accept the risk for malware concerns. This feature would be extremely useful if implemented and is distinct from #2640 because it's more to do with "user managed" packs rather than those hosted on a third-party service.

[Meegooo]

Now that Twitch pack search is there, this would be a nice feature to update those modpacks.

[Xalaxis]

Now that Twitch pack search is there, this would be a nice feature to update those modpacks.

2640 is for the update of "third-party" modpacks. This is more for personal ZIP packs.