Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
xml:loaders [2019/06/23 07:25]
ryantheallmighty Add choose information
xml:loaders [2019/06/23 07:28] (current)
ryantheallmighty [History of loaders in ATLauncher]
Line 7: Line 7:
 Before June 2019, if you wanted to install Forge loader into your pack, you had to use a special tool on the ATLauncher admin panel. This also meant that when Forge updated, you had to also re run and do the work to get it working with your pack. Before June 2019, if you wanted to install Forge loader into your pack, you had to use a special tool on the ATLauncher admin panel. This also meant that when Forge updated, you had to also re run and do the work to get it working with your pack.
  
-Forge for 1.13 changed the way they install and no longer was it just a bunch of static jar files that had to be loaded in order to get Forge to work, you now had to run an installer, which would then run some programs in order to generate jar files for mappings. Since this could no longer be done on the client ​side,+Forge for 1.13 changed the way they install and no longer was it just a bunch of static jar files that had to be loaded in order to get Forge to work, you now had to run an installer, which would then run some programs in order to generate jar files for mappings. Since this could no longer be done on the server ​side without hosting the output jars ourselves, we moved towards adding loader support within the ATLauncher client itself. 
 + 
 +This means easier configuration of loaders for you, and easier for us to maintain and update as neededas well as more support for loaders as new ones come out.
  
 ===== How to add loaders ===== ===== How to add loaders =====
xml/loaders.txt · Last modified: 2019/06/23 07:28 by ryantheallmighty
CC Attribution-Share Alike 4.0 International
Driven by DokuWiki Recent changes RSS feed Valid CSS Valid XHTML 1.0