While you may have run Minecraft many of times, you must not have run version 1.6.2 at all,otherwise you wouldn't be getting this message.
To run 1.6.2 on the new launcher, go to the left of the giant "Play" button and click on "Edit Profile". A new window will pop up, with a drop down menu about halfway down. Select "release 1.6.2" from that list, then click save. Now that profile will run 1.6.2 unless you change it again. Run minecraft and let it load up to the main screen,then close it down again and run Forge's installer. It should go through without a problem.
Who hosts the game, you or him? And is a crash report generated when this happens? You can check for a report by going to your .minecraft folder, then into the folder named "crash reports". The last file in the folder will be the newest one, but double check the name of the file just in case. If there is one, please paste it here, using spoiler tags:
[spoiler] -insert crash report here- [/spoiler]
Another thing to double check is that you both are running the same version of Buildcraft and of Forge.
Hello there. I'll be more than happy to help you install Minefantasy. I myself installed it last week, and love it so far.
First off, make sure you've run Minecraft version 1.5.2 at least once. You can switch versions in the launcher by going to "Edit Profile" (Located to the left of the giant play button), then halfway down the new dialog box that will pop up will be a "Use Version" drop down menu. Scroll down and select "Release 1.5.2", then click save.
Once you've done that, you can go and download Forge, as Minefantasy does not use Modloader. It is recommended that you download the launcher for build 738, which should be the second line on this page. You can run the installer from wherever you downloaded it to, there's no need to move it. The installer will copy the minecraft.jar and minecraft.json, and install Forge for you, so there's no need to open up the .jar and .json and mess around with it (But for future reference, open up your .minecraft folder, then find/open the "versions" folder. All the versions of minecraft you've run will have a labelled folder there containing the .jar and .json). It will also create a new profile for you in the launcher( it will call it "Forge"),which will be set by default to the Forge version you just installed. Once you've done this, launch the game using the "Forge" profile. You don't need to go into a world, just let it load to the main screen,then close it out.
Let me know when you've done this, and I'll give you further instructions from there. c:
MCP IS being updated, but it's 6 people and over 500,000 lines of changed coding, not to mention that item ID's have been completely changed. The 1.7x update is massive,and updating the coding will take some time.
The people at Forge have estimated that we shouldn't expect any major mod updates until at least December.
You must need some of your mods to be updated(1.5.2)...
Download Id resolver mod too...
It will help you fix ids...
Some mod versions meant for 1.5.1 will also work with 1.5.2, but the current problem is neither with them or with ID's, as an ID-conflict error would start with "Slot xyz is already occupied blahblahblah".
I'd delete that folder just in case, and run minecraft again after that. If it still crashes, take out your mods folder completely.At this point you can do one of two things: either launch the game without the mods folder (which will cause the game to create a new,empty mods folder), or you can, in the .minecraft folder, Right Click -> New Folder, and rename that "mods". Drag the MCA mod file into the new folder and launch the game again.
The error log you posted earlier is picking up on two instances of MCA,which is why it's spitting back the error.
To put the solution out there, make sure you can see your file extensions (Windows 7 how-to here).
Then once you do that, right click the file and select "Rename", and remove the ".zip" from the end, replacing it with ".jar".
On a Mac, the file extensions should be visible already, so just replace the ".zip" with ".jar".
Go into your .minecraft folder. There should be a number of files within it called ForgeModLoader-client-#.log.
ForgeModLoader-client-0.log will be the newest one. Open that up, and paste the text within it either here (be sure to use spoilers) or over at pastebin.com (and give us the link to it).
I am finding this strange. It appears as though this error is being caused by a NullPointerException, though what is causing that I can't tell.
Could you also post the Forge log please? It will show more details about what's doing what.
Another thing to try is deleting the config file for pixelmon, so when the game is launched it will create a new file for it.
If I can't figure anything out from the Forge log, I'm afraid I'm going to have to send you over to the Pixelmon thread or their forums.
That is what we're going to start testing for. If his game will load IC2 by itself, then we know there's an incompatibility somewhere with the other mods, and the long,frustrating process of putting each mod back in one at a time, loading minecraft each time, will begin.
The answer is, none. Extracting the .zip will make Forge not recognize it's there, as Forge will only detect .jars and .zips.
This is not entirely true, I believe.It depends on how the internal mechanics of the mod are set up. I have a number of mods installed that are not .jars or .zips, but are placed in the mods folder as folders and run just fine.At least this is true on a Mac, things may be a bit different on PCs, as by default Safari will automatically unzip .zip files into folders.
And I do believe I spoke a little too soon in my previous post. I decided to test run Pixelmon as an unzipped folder, and it ran just fine for me. So, Kuuu, I apologize.
At this point, I think that unzipping the pixelmon file is worth a try, as short of re-downloading Pixelmon again , or downgrading minecraft (and Forge) to version 1.6.2 and attempting to run pixelmon on that version, I'm not sure what else to try.
MrLittleThor, could you please post the most recent crash report in spoiler tags for me?
[spoiler] -insert crash report here- [/spoiler]
I was checking over my Forge log from my attempt at crashing pixelmon and noticed that the entry line for pixelmon ran a bit differently than mine did (mine shows the complete file name, while yours is just showing "pixelmon"). This may just be a PC vs Mac thing, but it doesn't hurt to check it out.
No.
Extracting the .zip file will not fix the problem you are having. The way the internal mechanics of the mod are set up, it will look for a .zip file with the name "Pixelmon 2.5.2.zip" , and if this isn't found, the mod will NOT run.
I'm going to do a bit of testing myself and see if I can replicate the crash on my end.
First of all, why are you trying to launch the game through bootstrap 5?
Second, I'd recommend completely deleting your .minecraft folder (back up any saves you have and wish to keep), then running Minecraft through it's launcher to download a fresh copy of the files. Since you're trying to mod version 1.6.4, run that version in this initial launch. Once you do that, close out of minecraft and download the Forge installer for build 944,which is the latest build. Run the installer, then once that's done launch minecraft again (the Forge profile should be selected in the launcher), and Forge shouldn't have any problems this time.
0
To run 1.6.2 on the new launcher, go to the left of the giant "Play" button and click on "Edit Profile". A new window will pop up, with a drop down menu about halfway down. Select "release 1.6.2" from that list, then click save. Now that profile will run 1.6.2 unless you change it again. Run minecraft and let it load up to the main screen,then close it down again and run Forge's installer. It should go through without a problem.
0
Another thing to double check is that you both are running the same version of Buildcraft and of Forge.
3
First off, make sure you've run Minecraft version 1.5.2 at least once. You can switch versions in the launcher by going to "Edit Profile" (Located to the left of the giant play button), then halfway down the new dialog box that will pop up will be a "Use Version" drop down menu. Scroll down and select "Release 1.5.2", then click save.
Once you've done that, you can go and download Forge, as Minefantasy does not use Modloader. It is recommended that you download the launcher for build 738, which should be the second line on this page. You can run the installer from wherever you downloaded it to, there's no need to move it. The installer will copy the minecraft.jar and minecraft.json, and install Forge for you, so there's no need to open up the .jar and .json and mess around with it (But for future reference, open up your .minecraft folder, then find/open the "versions" folder. All the versions of minecraft you've run will have a labelled folder there containing the .jar and .json). It will also create a new profile for you in the launcher( it will call it "Forge"),which will be set by default to the Forge version you just installed. Once you've done this, launch the game using the "Forge" profile. You don't need to go into a world, just let it load to the main screen,then close it out.
Let me know when you've done this, and I'll give you further instructions from there. c:
0
The people at Forge have estimated that we shouldn't expect any major mod updates until at least December.
0
If you have any more problems or questions about MCA or mods in general, feel free to message me.c:
0
Some mod versions meant for 1.5.1 will also work with 1.5.2, but the current problem is neither with them or with ID's, as an ID-conflict error would start with "Slot xyz is already occupied blahblahblah".
1
The error log you posted earlier is picking up on two instances of MCA,which is why it's spitting back the error.
0
Then once you do that, right click the file and select "Rename", and remove the ".zip" from the end, replacing it with ".jar".
On a Mac, the file extensions should be visible already, so just replace the ".zip" with ".jar".
0
Go into your .minecraft folder. There should be a number of files within it called ForgeModLoader-client-#.log.
ForgeModLoader-client-0.log will be the newest one. Open that up, and paste the text within it either here (be sure to use spoilers) or over at pastebin.com (and give us the link to it).
0
You may want to take out the extra copy of MCA from your mods folder. You only need one.
1
Could you also post the Forge log please? It will show more details about what's doing what.
Another thing to try is deleting the config file for pixelmon, so when the game is launched it will create a new file for it.
If I can't figure anything out from the Forge log, I'm afraid I'm going to have to send you over to the Pixelmon thread or their forums.
0
0
And I do believe I spoke a little too soon in my previous post. I decided to test run Pixelmon as an unzipped folder, and it ran just fine for me. So, Kuuu, I apologize.
At this point, I think that unzipping the pixelmon file is worth a try, as short of re-downloading Pixelmon again , or downgrading minecraft (and Forge) to version 1.6.2 and attempting to run pixelmon on that version, I'm not sure what else to try.
MrLittleThor, could you please post the most recent crash report in spoiler tags for me?
I was checking over my Forge log from my attempt at crashing pixelmon and noticed that the entry line for pixelmon ran a bit differently than mine did (mine shows the complete file name, while yours is just showing "pixelmon"). This may just be a PC vs Mac thing, but it doesn't hurt to check it out.
0
Extracting the .zip file will not fix the problem you are having. The way the internal mechanics of the mod are set up, it will look for a .zip file with the name "Pixelmon 2.5.2.zip" , and if this isn't found, the mod will NOT run.
I'm going to do a bit of testing myself and see if I can replicate the crash on my end.
0
Second, I'd recommend completely deleting your .minecraft folder (back up any saves you have and wish to keep), then running Minecraft through it's launcher to download a fresh copy of the files. Since you're trying to mod version 1.6.4, run that version in this initial launch. Once you do that, close out of minecraft and download the Forge installer for build 944,which is the latest build. Run the installer, then once that's done launch minecraft again (the Forge profile should be selected in the launcher), and Forge shouldn't have any problems this time.