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

Impact on Forge above 1.12.2 (1.14.4) #105

Open
metl-play opened this issue Jul 30, 2020 · 4 comments
Open

Impact on Forge above 1.12.2 (1.14.4) #105

metl-play opened this issue Jul 30, 2020 · 4 comments
Labels
enhancement New feature or request

Comments

@metl-play
Copy link

Is your feature request related to a problem? Please describe.

I would like to use Forge alongside to Impact on MC 1.14.4 (this is my personal wish, more supported versions would be perfect).
I know you guys aren´t related to Forge but since Impact+Forge on 1.12.2 works it could be possible to update this.

Describe the solution you'd like

I like to have Impact as a client with forge to use mods like journeymap. How about make a clear universal guide for how to code the update to newer Forge versions (if u are too lazy or don´t have the time to update it everytime or just don´t want to update this specific thing, or, or, or..., so u can let us less educated coders do the work (for sure not me)).

Describe alternatives you've considered

The modules are just mods so it would be possible to make an Impact forge modpack for newer versions (maybe with some missing features), or not?

Additional context

If i´m just saying some bullcrab delete this post or simple say no if nothing will happen in this direction. I am not into coding the only thing i coded was a .bat.
I respect u guys and ur work really much.
This suggestion is just from a guy who is too dumb to do it himself.

@metl-play metl-play added the enhancement New feature or request label Jul 30, 2020
@5HT2
Copy link

5HT2 commented Aug 10, 2020

Impact Forge 1.12.2 is unsupported and iirc future Forge versions will not be supported

@LeafHacker
Copy link
Contributor

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 srg mappings.

@5HT2
Copy link

5HT2 commented Aug 16, 2020

Yea. The way Impact 1.12.2 forge does it already breaks a lot of things. This is probably won't fix but I'd want leafs opinion first

@LeafHacker
Copy link
Contributor

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 indefinitely

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants