Creating a pack, where to get base?

[Demosthenex]

The excellent guidelines specify what files and folders are applied to the base Minecraft + Forge files to apply your modpack, specifically minecraft/{config,mods}.

Where do you get the base Minecraft + Forge files from, in an FTB aware fashion?

Yes, I could redownload vanilla from Mojang. Then files could end up in places FTB doesn't expect. Then I can add Forge manually.

Yep, I found that Vanilla 1.6.4 is in the launcher under third party packs. And then I can't find where it installed to. In my FTB folder it appears to have only placed the saves in mojang_vanilla.

Yes, I've done modded Minecraft before with several launchers. I'm trying to test against what FTB should supply in their launcher, hence the request for the FTB base.

Any ideas?

 

[Watchful11]

You don't. As the guidelines say, you only give us the configs and mods. The launcher handles the rest. Also, the guidelines say to specify if you want a specific forge version.

 

[Demosthenex]

You don't. As the guidelines say, you only give us the configs and mods. The launcher handles the rest. Also, the guidelines say to specify if you want a specific forge version.

So for integrating the mods locally (ie: dev/test) I would wait for the launcher?

I intended to give you a completed product.

 

[Demosthenex]

So for integrating the mods locally (ie: dev/test) I would wait for the launcher?

I intended to give you a completed product.

I should say that I understand the launcher composes MC + Forge locally, and then applies the contents of the zip on top of that.

I'm trying to perform the same process for testing of the zip content. It's hard to produce a patch if you don't have something to patch. Yes I can download and patch up vanilla, I simply asked if there was an accepted method given I am trying to follow FTB standards.

 

[Watchful11]

That's why we only take the mods and configs folders. You can test it with any launcher you want, then just send us those folders. It won't run any differently.

 

[Demosthenex]

That's why we only take the mods and configs folders. You can test it with any launcher you want, then just send us those folders. It won't run any differently.

Ok, I can appreciate that. I'd be happy to set it up myself.

May I suggest that there be a third party "Forge Only" or "Modpack Development" install to use as a starting point which is self contained in it's own folder much like the other FTB packs? Perhaps by code so it doesn't clutter the launcher?

Thanks.

 

[Watchful11]

The FTB launcher isn't really intended for that. We are fine with people add or removing a few mods from a pack, but the launcher is intended as a distribution platform for end users. Use MultiMC if you are developing a modpack.

 

[Demosthenex]

The FTB launcher isn't really intended for that. We are fine with people add or removing a few mods from a pack, but the launcher is intended as a distribution platform for end users. Use MultiMC if you are developing a modpack.

I can appreciate that. I wouldn't have had questions if I had found documentation on the directory layout the launcher creates.

I'm content to build it myself, and perhaps try MultiMC which is new to me. Perhaps you don't want to lower the bar of proficiency it requires to create a modpack for the launcher to prevent trivial requests. I can respect that too.

I program enough in my day job to ask for a dev environment that will match production due to caution and change control. If it's really so trivial and everyone else uses MultiMC, then so shall I.