YouSmellLikeAGypsy
-
Posts
18 -
Joined
-
Last visited
Posts posted by YouSmellLikeAGypsy
-
-
Please note that one must append "?download=1" (without quotes) to a copy.com link to correctly make it a direct link.
I know.
-
Awfully hard to debug a pack I cannot download. The download URL in your pack settings points to a file that does not exist.
That's why I'm copying up the next version right now.
-
Forge Multipart goes in your mods<MCVERSION> folder, where <MCVERSION> is the version number of MC you are using. For 1.6.4 it would be mods1.6.4. Delete all your current Forge Multipart JAR files and download the latest version for 1.6.4 from here: http://files.minecraftforge.net/ForgeMultipart//index_legacy.html
I did, but it always downloads a different version when I start it up and then whines that there's more than one of that type of file.
-
K only problem is with forgemultipart if you know about that. For my modpack I need 1.0.0.244 or higher, so I got 1.0.0.250. After that, it told me that it was conflicting with 1.0.0.227. So I deleted it and put .250 in its place. After that, it made a new .227 and continued to whine that it was conflicting with .250. You know how to change that?Because you deleted the modpack.jar, you also moved all mods from the mods directory to the 1.6.4 directory inside mods.
Take a step back. The previous version was better.
-
K just a couple more downloads and it should be fine.Because you deleted the modpack.jar, you also moved all mods from the mods directory to the 1.6.4 directory inside mods.
Take a step back. The previous version was better.
-
Because you deleted the modpack.jar, you also moved all mods from the mods directory to the 1.6.4 directory inside mods.
Take a step back. The previous version was better.
I deleted it? Crap.
Oh. Perhaps I misunderstood you.
-
To figure this one out you need to fix this:
K now it's running vanilla again http://www.technicpack.net/modpack/details/asdfmovie-99.535031
-
You need to walk away and come back tomorrow. Take note that the only critical error you made is number 1. After fixing this the pack will load as a modded minecraft
https://copy.com/Hytq0wISv8S9yTqt
It opens now, but when it tries to load it crashes. At least it's trying.
-
You need to walk away and come back tomorrow. Take note that the only critical error you made is number 1. After fixing this the pack will load as a modded minecraft
Alright cool thanks!
-
Sorry to hear this.
Is there a video or something explaining what you said before because I'm not even sure I'm trying to read English anymore.
-
I give up.
-
It is opening.... vanilla minecraft.
Your pack is in a directory called "Pack". This is wrong. Prepare the directories and zip them together (bin, mods and config).
Delete all directories from your mods directory. Leave only the 1.6.4 folder with contents.
The bin directory should only have the modpack.jar file. Delete the rest.
After all this I'll take a look again at the pack and one more thing... no configs? This can be catastrophic for a 1.6.4 pack.
Edit:
I said it will be catastrophic, here are your ID conflicts:
3972: resonant:multiPart from ResonantEngine - aluminumWire from GalacticraftCore Suggested Ranges: 563-899 (337 IDs), 2856-3119 (264 IDs), 3398-3649 (252 IDs)
I knew it would be something obvious
alright, 1.2a is up. Not sure if it works because wifi where I am is too slow to even download it now apparently. -
You're not running 64bit java
Oh I hadn't thought of that. Mine runs 64bit by default.
-
Yeah i do that, but like the max on that dropdown box is 1GB.
Then idk. Do you have a good computer?
-
When in the pack selection screen, click the gear in the top right by the exit button and there'll be the option to change the max memory to as high as 3GB or as low as 512MB.
If you mean that that isn't working then idk.
-
My new custom modpack isn't loading. It opened as vanilla at the beginning but after that I looked it up on here and found that I need to delete a few files in the different .jar folders. Most of the mods on my pack are from different packs that are compatible with 1.6.4. The ones that aren't I downloaded the safer/recommended 1.6.4 versions of each so that it would be more likely to run properly.
After I deleted the files mentioned I tried running it again. It didn't run vanilla anymore, it just didn't bother and sent me back to pack selection. After I did all I found I was supposed to do, I decided to upload that as the new version to avoid being told to do things I already did, and labeled it as the 1.1a version.
My pack is http://www.technicpack.net/modpack/details/asdfmovie-99.535031
and here is the report from my latest crash:
-
My radar is set up with 20 safe, 80 alarm, and my EMP is set to 80 and disrupt missiles, both are powered, the missiles fired from 100 blocks away, there is a redstone line leading from the radar to the EMP tower, and redstone is in all 8 blocks around the radar tower. But it's not working. The radar doesn't send a redstone signal. Any ideas?
alright, 1.2a is up. Not sure if it works because wifi where I am is too slow to even download it now apparently.
Custom modpack not opening
in Platform Pagoda
Posted
1.4.3a