Leaf

In general, instead of using the `inheritsFrom` system in the vanilla launcher, multimc uses a "patch json" system. We just add our stuff as a patch against the target version....

Moved multimc to #49, this is now liteloader

I was under the impression you want to redistribute everything we depend on (in release builds at least) on our own maven, to avoid issues when some random 3rd party...

I'm still leaning towards the metadata json being the authority on _where_ to get stuff in addition to _what_ to get, whether by specifying a maven repo or a canonical...

> > that was more of a lack of trust in dl.liteloader.com specifically -- i have no such worries about actual apache maven going down > > dl.liteloader.com is run...

This would require impact itself to implement modloader support (at a minimum) and would require the installer to translate the impact jar & mixin refmap from notch/official mappings to forge's...

Forge/modloader support would be a nice to have that may come after Impact 5 (a major refactor), depending on stuff. This isn't a won't fix, but it may remain unresolved...

Well, if they've not run the launcher before we may need to _create_ launcher_profiles?

Do they definitely need to have run the mc version before?

> When you edit that JTextField it doesn't update the actual setting tho =( My bad, atm you have to hit enter for it to update the setting. If we...