I'm going to try and throw something together for new modpack creators.
If I leave something out just let me know and I'll add it in.
This is simply a quick guide to making modpacks. It is by no means the full extension of the inner workings.
(That is put up to the pack creators. The more you enjoy your own pack, more than likely others will too)
To start, a good modpack can't be handled like a bag of laundry. (Don't just make a folder and throw in a bunch of mods)
If you're looking to make a modpack to enjoy and like most other modpack creators you want others to enjoy it as well. I mean, what's the point in making one that no one can play right?
Modpacks take a lot of time and care. Each mod changes the ingame experience of minecraft in some form or fashion. There is another side of this for the creator. Imagine being like an auto mechanic. Yeah he may test drive the car but most of the time, he's under the hood fixing something. Trying to make things look better, run smoother, get more power or just fix something.
Ok, now you have a folder full of mods you would like to make work together right? Cause that would be awesome and it sounds like a fun time.
1. Most modpack creators use MultiMC. If you don't have it, I recommend it as it's super user friendly and simply a powerful tool.
2. Now would be a good time to make sure you have all your mod permissions in order. (Permissions are typically per mod, per pack.) Meaning, yes, you can update the mods as updates are put out. Unless specified otherwise by that specific mod author. (Usually they will let you know on their post somewhere)
Do you have permission for all of them?
Do you have screen shots to have proof of the ones you had to ask for?
Is the permission information IE: URLS and what not accurate?
3. Did you install MultiMC from earlier? If so, run the program and fill out the necessary information.
(You will end up looking at something like this)
[Img A]
4. Create a new instance.
(An instance is going to be your new home)
[Img B]
This is not a MultiMC tut so I will leave you with that. The rest you can browse around the program and pretty much get the idea from there.
5. Once you have your instance created, run it by simply double clicking it. Once it loads all the way to the main menu screen you can go ahead and close it.
6. Okay, you can now begin to fill it with mods by more ways than one. I prefer opening the instance folder then the mods folder. From there you can edit what you want in the pack in bulk and be able to hop over to the config folder by backing out of the mods folder and into ...instances/[packnamehere]/minecraft
From this point you can get into the inner workings of your pack.
7. After you have your pack tweaked to your hearts content. You have a choice of who you want to launch your awesome modpack.
There are several places to go from here at Curse, to FTB to Technic or what ever one you prefer as there are several. If your launcher isn't listed don't sweat it, Just lemme know and I'll add it.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI'm going to try and throw something together for new modpack creators.
If I leave something out just let me know and I'll add it in.
This is simply a quick guide to making modpacks. It is by no means the full extension of the inner workings.
(That is put up to the pack creators. The more you enjoy your own pack, more than likely others will too)
To start, a good modpack can't be handled like a bag of laundry. (Don't just make a folder and throw in a bunch of mods)
If you're looking to make a modpack to enjoy and like most other modpack creators you want others to enjoy it as well. I mean, what's the point in making one that no one can play right?
Modpacks take a lot of time and care. Each mod changes the ingame experience of minecraft in some form or fashion. There is another side of this for the creator. Imagine being like an auto mechanic. Yeah he may test drive the car but most of the time, he's under the hood fixing something. Trying to make things look better, run smoother, get more power or just fix something.
Ok, now you have a folder full of mods you would like to make work together right? Cause that would be awesome and it sounds like a fun time.
1. Most modpack creators use MultiMC. If you don't have it, I recommend it as it's super user friendly and simply a powerful tool.
2. Now would be a good time to make sure you have all your mod permissions in order. (Permissions are typically per mod, per pack.) Meaning, yes, you can update the mods as updates are put out. Unless specified otherwise by that specific mod author. (Usually they will let you know on their post somewhere)
3. Did you install MultiMC from earlier? If so, run the program and fill out the necessary information.
(You will end up looking at something like this)
[Img A]
4. Create a new instance.
(An instance is going to be your new home)
[Img B]
This is not a MultiMC tut so I will leave you with that. The rest you can browse around the program and pretty much get the idea from there.
5. Once you have your instance created, run it by simply double clicking it. Once it loads all the way to the main menu screen you can go ahead and close it.
6. Okay, you can now begin to fill it with mods by more ways than one. I prefer opening the instance folder then the mods folder. From there you can edit what you want in the pack in bulk and be able to hop over to the config folder by backing out of the mods folder and into ...instances/[packnamehere]/minecraft
From this point you can get into the inner workings of your pack.
7. After you have your pack tweaked to your hearts content. You have a choice of who you want to launch your awesome modpack.
There are several places to go from here at Curse, to FTB to Technic or what ever one you prefer as there are several. If your launcher isn't listed don't sweat it, Just lemme know and I'll add it.
Oh and HERE's a place to check mod permissions!
I hope this post lives to serve new modpack creators well.