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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why 1.3? #8

Closed
Madis0 opened this issue May 20, 2022 · 2 comments
Closed

Why 1.3? #8

Madis0 opened this issue May 20, 2022 · 2 comments

Comments

@Madis0
Copy link

Madis0 commented May 20, 2022

Of all possible versions, why port Minecraft Forge 1.3.2 specifically? Seems a bit arbitrary 馃槃
I'm aware that the codebase was simpler back then, but I recall the first big refactor only happening in 1.8, so why didn't you choose 1.7.10 for example?

@thecatcore
Copy link
Member

thecatcore commented May 20, 2022

Reasons:

  1. It's the oldest Minecraft version that both Legacy Fabric and Forge support
  2. It's old Forge so less patches to port.
  3. It's old Forge so no dealing with LaunchWrapper so easier to make work.
  4. It's close to Forge 1.2.5 that has really basic support in Fabric Loader.
  5. I plan to go up in Minecraft/Forge versions over the time.

@Madis0
Copy link
Author

Madis0 commented May 20, 2022

Thanks!

@Madis0 Madis0 closed this as completed May 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants