Jump to content

Recommended Posts

Posted

Prior to Minecraft 1.6.1, there was only one version of everything and the mods folder was located in the main .minecraft folder.  No problem.

 

Now, we have the versions folder and the ability to have multiple versions of Minecraft (both modded and unmodded) installed.  Based on a couple of tutorials I read/watched, it sounded like the mods folder needs to be under the specific version rather than the .minecraft folder.  Example:

 

Old way:

 

\AppData\Roaming\.minecraft\mods

 

New way:

 

\AppData\Roaming\minecraft\versions\Forge8.9.0.762\mods

 

However, it looks like Forge is still trying to load mods from the \AppData\.minecraft\mods folder.  From the log file (entire file included at the end of this post):

 

2013-07-03 18:35:42 [iNFO] [ForgeModLoader] Searching C:\Users\Chris\AppData\Roaming\.minecraft\mods for mods

 

 

Note: I have the latest version of Forge and used the installer to insall it.

 

Is this correct or have I mis-installed something?

 

 

Full log:

 

  Reveal hidden contents

 

Posted

Thanks for the response.

 

So if Forge is still using the original mods folder location (i.e. \AppData\Roaming\.minecraft\mods) how will it be possible to have different versions with different mods?  My understanding is that that is one of the reasons for the new launcher to support multiple profiles/versions.  With the current behavior, any version of minecraft you add Forge to will just load all the mods in the \AppData\Roaming\.minecraft\mods folder.

 

Posted

The strcture of the mods folder is changing I beleive right now it it /mods/{version}

Eventually, we want to make it so you dont have that flat folder for mods. We want to have it like the libraries folder:

/mods/cpw/mods/ironchests/1.6.1r1/ironchests-1.6.1r1.jar

/mods/cpw/mods/ironchests/1.6.1r2/ironchests-1.6.1r2.jar

etc.. And then we build a proper list of mods from a configuration file that modpacks, and the like ship.

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Posted
  On 7/4/2013 at 5:05 AM, LexManos said:

The strcture of the mods folder is changing I beleive right now it it /mods/{version}

Eventually, we want to make it so you dont have that flat folder for mods. We want to have it like the libraries folder:

/mods/cpw/mods/ironchests/1.6.1r1/ironchests-1.6.1r1.jar

/mods/cpw/mods/ironchests/1.6.1r2/ironchests-1.6.1r2.jar

etc.. And then we build a proper list of mods from a configuration file that modpacks, and the like ship.

Lex, please think of the not-so-enlightened that build their own packs.

Read the EAQ before posting! OR ELSE!

 

  Quote
This isn't building better software, its trying to grab a place in the commit list of a highly visible github project.

 

www.forgeessentials.com

 

Don't PM me, I don't check this account unless I have to.

Posted
  On 7/4/2013 at 10:50 AM, luacs1998 said:

  Quote

The strcture of the mods folder is changing I beleive right now it it /mods/{version}

Eventually, we want to make it so you dont have that flat folder for mods. We want to have it like the libraries folder:

/mods/cpw/mods/ironchests/1.6.1r1/ironchests-1.6.1r1.jar

/mods/cpw/mods/ironchests/1.6.1r2/ironchests-1.6.1r2.jar

etc.. And then we build a proper list of mods from a configuration file that modpacks, and the like ship.

Lex, please think of the not-so-enlightened that build their own packs.

 

Personally, I would have preferred something like:

/mods/(ForgeVersionName)/ModPack(s).jar

 

Nice and simple, allows for switching between mods based on the version they use in the minecraft launcher profiles.

 

Food for thought...

Posted
  On 7/4/2013 at 10:50 AM, luacs1998 said:

  Quote

The strcture of the mods folder is changing I beleive right now it it /mods/{version}

Eventually, we want to make it so you dont have that flat folder for mods. We want to have it like the libraries folder:

/mods/cpw/mods/ironchests/1.6.1r1/ironchests-1.6.1r1.jar

/mods/cpw/mods/ironchests/1.6.1r2/ironchests-1.6.1r2.jar

etc.. And then we build a proper list of mods from a configuration file that modpacks, and the like ship.

Lex, please think of the not-so-enlightened that build their own packs.

If you can't type 'domain:name:version' Then you really shouldn't be making a mod pack...

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Posted

One question... and suggestion:

 

Now that we have profiles, could the mods's config be stored separately for each profile?

It's really annoying, when you play on different servers, having to switch configuration files.

 

See ya!

Posted

I think that all mod loaders should use a mods folder in the minecraft directory selected by the profile.

Both 1.5.2 and 1.6.1 the servers.dat file is the one pointed to by the directory entry in the profile.

Have that directory structure containing all of the data for that profile only make since.

 

I don't know how many times I have accidentally loaded SSP world with a mod pack I had used for it missing and had blocks and items vanish. It really sucks.

 

  On 7/4/2013 at 12:28 PM, ShadowComedus said:

  Quote

  Quote

The strcture of the mods folder is changing I beleive right now it it /mods/{version}

Eventually, we want to make it so you dont have that flat folder for mods. We want to have it like the libraries folder:

/mods/cpw/mods/ironchests/1.6.1r1/ironchests-1.6.1r1.jar

/mods/cpw/mods/ironchests/1.6.1r2/ironchests-1.6.1r2.jar

etc.. And then we build a proper list of mods from a configuration file that modpacks, and the like ship.

Lex, please think of the not-so-enlightened that build their own packs.

 

Personally, I would have preferred something like:

/mods/(ForgeVersionName)/ModPack(s).jar

 

Nice and simple, allows for switching between mods based on the version they use in the minecraft launcher profiles.

 

Food for thought...

 

The only reason to have a version under the mods directory would be useful if for some reason you were running different versions in the same directory, but you would still run into the problem of blocks/items not supported in one version or another vanishing. So I think it would be better just to keep them separate and just move the save to the version you wanted to play it on.

 

Right now I'm just renaming into the libraries directory and adding into the jason file for the version so I can have different versions with different mods, now if I can only figure out how to stop them from trying to update.

 

In the future it looks like mods will be going in resource packs. See https://gist.github.com/Dinnerbone/5662824

 

This post contains mostly my opinions and I take full responsibility for the ones that are mine.  ;D

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



×
×
  • Create New...

Important Information

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