Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to manage AT Launcher's modpacks right from MultiMC #405

Closed
evelynharthbrooke opened this issue Jul 28, 2014 · 14 comments
Closed

Ability to manage AT Launcher's modpacks right from MultiMC #405

evelynharthbrooke opened this issue Jul 28, 2014 · 14 comments
Labels
close:declined We are not going to do that. feature

Comments

@evelynharthbrooke
Copy link

I would find it really useful if we could manage AT Launcher's mod packs since you have FTB integration, so why not add AT Launcher integration as well?

@LawAbidingEnt
Copy link

Yah this would be a really nice feature.

@02JanDal
Copy link
Member

When I first did the FTB integration we didn't have the jarmod support in place, and the way AT and Technic do it required jarmod support, even for instances with just Forge (with other words: they did it wrong).

Now that we have Jarmod support we could revisit this, but we often have problems with the FTB support, so we would have to think about this a bit if we want to do this.

@evelynharthbrooke
Copy link
Author

I see. I'll just use the launchers for now when it comes to Technic and AT modpacks. Hopefully you guys will add it in the future though as it would prove useful to many people who use Technic and AT modpacks.

@Khitiara
Copy link
Member

http://www.creeperrepo.net/ATL/launcher/json/packs.json
http://www.creeperrepo.net/ATL/packs/${name}/versions/${version}/Configs.xml
where name is the pack name has all non alphanumeric characters removed and version is the version you want, retrieved from packs.json

AT Launcher support in a nutshell

@Khitiara
Copy link
Member

I dont know about technic, and I have an irrational bias against it anyway
someone else can figure it out

@Khitiara
Copy link
Member

we have permission to do something similar to ftb support for AT Launcher
you would still need to use it to download packs, but display and launching will be done by use sort of

@02JanDal
Copy link
Member

This issue will be dedicated to AT Launcher, please create a new one for technic

@RyanTheAllmighty
Copy link

Yes this is all good by us (ATLauncher) as long as there is no downloading/installing of packs and it's used as a launching mechanism. Good luck, feel free to contact me if you need any changes done to support this as I'm all for it :)

@02JanDal 02JanDal added this to the 0.7.0 milestone Jul 31, 2014
@Khitiara
Copy link
Member

in two weeks i will get started when i return the US

@evelynharthbrooke evelynharthbrooke changed the title Ability to manage AT Launcher's and Technic Launcher's modpacks right from MultiMC Ability to manage AT Launcher's modpacks right from MultiMC Aug 2, 2014
@peterix peterix removed this from the 0.6.0 milestone Sep 11, 2014
@Khitiara Khitiara removed their assignment Jan 3, 2015
@Aphenon
Copy link

Aphenon commented Jan 18, 2015

Was this feature dropped? i would love to have this.

@RyanTheAllmighty
Copy link

I'm sad this never made it in. The fact it's still open provides hope, but only very little since it's been left here.

Any update on this or how I can help in anyway make this happen?

@peterix
Copy link
Member

peterix commented Feb 23, 2015

Yep. We don't have enough manpower.

Currently, all my effort goes into this:
https://github.com/MultiMC/MultiMC5/commits/feature/remote_version_files

Basically making a new instance format that can handle modpacks and direct resource downloads. Kinda like QuickMods should have been, only built from bottom up, not the other way.

@peterix
Copy link
Member

peterix commented Jan 29, 2016

Long time no see! I'm moving all the ideas to workflowy - a place better suited for the kind of structured organization and planning needed to actually manage hundreds of ideas.

The feature will most likely take the form of direct support - and import from the platform. Not tracking or launching of existing ATL instances.

So, this has been moved to workflowy (Ideas -> Packs).

@peterix peterix closed this as completed Jan 29, 2016
@peterix peterix reopened this Feb 14, 2018
@peterix
Copy link
Member

peterix commented May 26, 2018

So, I'm looking at this, and I don't think this can ever go forward.

  1. I don't want to reimplement other launcher's logic just to be able to launch some arbitrary instances from them. It would tie MultiMC to their internals. It did that with FTB, and I'm not a fan of the mess it causes in the code. The launchers go in different directions, and the differences are often irreconcilable.
  2. Import from platform is not possible.

I might do this in the 'direct import from platform' way on a private branch just for the heck of it... But it cannot be deployed.

@peterix peterix closed this as completed May 26, 2018
@peterix peterix added the close:declined We are not going to do that. label May 26, 2018
peterix pushed a commit that referenced this issue Feb 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
close:declined We are not going to do that. feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants