Jump to content

digitalNacht

Members
  • Posts

    4
  • Joined

  • Last visited

digitalNacht's Achievements

Tree Puncher

Tree Puncher (2/8)

0

Reputation

  1. Ah, I see the problem. You need to download the installer, not the launcher. That will install 1.13.2 Forge so you can set up a new configuration for it. Right click the .jar file, and select "Open with" and find your javaw.exe executable to run the file. I don't know what the launcher is for, I just used the installer.
  2. Probably. Something to understand is that a lot of later code is written based on earlier code and rewriting earlier code to "fix it" can have unforseen consequences and break something completely unrelated creating a much harder to fix problem because fixing what obviously broke because of the fix might require chasing down what actually is causing the new problem somewhere in between the newly written code and what just broke. Call it a ghost in the machine problem. I imagine they could fix the earlier code, but consider that it took a year to re-code Forge with better code and less clutter and Minecraft is likely a lot more complex than Forge. I don't want to know how long that re-code would take. So, sometimes, as Cadiboo said, if it ain't broke, don't fix it.
  3. Are you running MultiMC or the default launcher? If you're running the default launcher, try seeing if the installer actually set up 1.13.2 Forge already and has a profile called "forge" on the MC version drop down menu for creating a new profile with 1.13.2-forge-25.0.107 as the jar. MultiMC doesn't play nicely with the recoded Forge right now.
  4. Players will tend to stay with what they like when they already have the game experience they want. If players are sticking with 1.7 at least a few modders will stick with it as well because they are likely playing 1.7 as well. It really just comes down to personal preference.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.