-
Posts
4594 -
Joined
-
Last visited
-
Days Won
74
Community Answers
-
plowmanplow's post in ModPack Help was marked as the answer
Any time you change the contents of your modpack archive you must increment the pack version number in your settings page for the Launcher ot be notified of the change.
-
plowmanplow's post in Modpack not woring was marked as the answer
Add Lexmanos' legacyjavafixer-1.0.jar to your pack. This is a Java 8 issue for Forge versions on 1.6.4 and 1.7.2 which is fixed by that mod.
http://t.co/9olGYnwZBi
-
plowmanplow's post in Solder and Apache was marked as the answer
Yes. Unless your Solder install is just insanely busy, there's no practical difference.
-
plowmanplow's post in Question: Is it possible to have multiple authors to a modpack? was marked as the answer
Using Solder, yes, this is possible with accounts and permissions. Using the platform, you'll have to share login information. -
plowmanplow's post in Custom modpack server won't start was marked as the answer
TiCTooltips is a client only mod. Try removing that. The error here:
Caused by: java.lang.NoClassDefFoundError: net/minecraft/world/World indicates that you have a client only mod in your server mods folder.
-
plowmanplow's post in My modpack doesn't launch was marked as the answer
You have MicdoodleCore in your mods folder but none of the mods which require it. Why did you add this dependency mod? It is only used by Galacticraft, which is comprised of 3 mod files: Galacticraft, GalacticraftPlanets, MicdoodleCore. Removing MicdoodleCore allowed me to create a world. You have an item conflict between two different items in CFM. Check your ForgeModLoader-client-0.log file for the word CONFLICT. -
plowmanplow's post in Cusotm Modpack launching as vanilla was marked as the answer
I'm going to say this one last time:
YOUR SMART CURSOR MOD IS STILL MESSED UP.
I don't know how else to state this. Until you fix that mod (or remove it) your pack will never work.
-
plowmanplow's post in Modpack will not download correctly! was marked as the answer
Hehe, I specifically linked you the build server for Openmods (OpenModsLib and OpenBlocks) since the 1.7.10 version isn't on the main page for the mod. You have the 1.6.4 version in your modpack. Get the 1.7.10 version from the link I provided above.
-
plowmanplow's post in I need a server creating for my modpack was marked as the answer
If you can connect locally, but remote clients cannot, the problem lies with communication paths, not with the server software. This is a fact. I'm not trying to be obstinate, it is just difficult to make more specific suggestions without having more information about your local configuration than can readily be provided here.
-
plowmanplow's post in Modpack unzipping error was marked as the answer
Somewhere in the process of extracting and repackaging your modpack archive you have damaged the Millenaire mod's folder structure. You will need to remove all of the files and folders related to Millenaire and re-download/re-install the mod.
-
plowmanplow's post in Is there a similar modpack to what I want or a request website? was marked as the answer
Better Dungeons is not installed correctly. Open the ZIP file and follow the mod author's instructions. You have included (again, improperly installed) Millenaire v0.6.4 which is for Minecraft Beta 1.6.4. Millenaire v5.1.11 is for Minecraft Release 1.6.4. You must make sure to re-add the updated config folder (which includes configs for the new mods) in your new modpack archive. All that being said, I've re-built the pack with the changes. Millenaire is a PITA to deal with because of the way the author publishes the mod. For whatever reason, the files in the mod's folders often cause problems for the ZIP library embedded in the Technic Launcher which causes pack extraction to fail if not done just right.
https://copy.com/VWRPUA8xlPLaYA2I?download=1
-
plowmanplow's post in Help with custom modpack! was marked as the answer
Your current modpack still has the old version of NotEnoughCodecs. You need to be updating the modpack (including incrementing the version number) in order for us to be testing it. You have a 1.7.2 version of MapWriter mod. I'm not sure if there is a 1.7.10 version available, but the 1.7.2 version won't work in 1.7.10. Numina doesn't like something else in the pack. Not sure if it is just Forge or another mod, but it can (and should) be safely removed since nothing in the pack is using it. -
plowmanplow's post in How do i open the Modpack.jar was marked as the answer
The modpack.jar file is simply the Forge universal binary JAR file renamed to modpack.jar. It is a ZIP format archive file and can be opened with any program which can view/extract ZIP files.
-
plowmanplow's post in Help with Modpack Launch was marked as the answer
You have duplicate Chisel mod files in your mods folder. MCHeli mod is not installed correctly. You have OpenBlocks mod but not the dependency mod OpenModsLib. You have no config files in your modpack. This is always bad and often fatal. This post explains a bit about configs: Fix these issues and come back if you are still having difficulties.
-
plowmanplow's post in Failing to Download Files was marked as the answer
Expected MD5: 6499480480a063b69149d96e298efa16 Calculated MD5: 17f49b095c2fb0bd610987995caf85ab The assumption here is that you have changed that ZIP file after adding it to Solder and Solder has the wrong MD5. You can go to that mod and version in your Solder interface and tell it to rehash. Not sure if you will need to create a new build to get the client to realize there is an update, but since that would be the only thing you are changing it wouldn't be a big deal for downloads and such.
-
plowmanplow's post in Crashes on the main screen CUSTOM MODPACK was marked as the answer
You have a 1.6.4 version of AutoUtils mod. This needs to be removed. You have a 1.6.4 version of Chisel mod. You will need the 1.7.10 version if you intend to include the mod. DenofLion's mods are not released for 1.7.10 (denPipes, denLib, etc.). ForgeMultipart belongs in mods1.7.10 not mods. iChun's GravityGun mod has not been released for 1.7.10. Remove the 1.6.4 version you have. You have a 1.6.4 version of Logistics Pipes. This mod has not been released for 1.7.10 and the alpha/betas available are likely unstable and incompatible. I'm going to stop at this point. It is clear that you have a huge mishmash of mods for different versions of Forge/MC. This won't work. You need to get mods for 1.7.10 (if you are building a pack for that version) which are specifically made for that version of Forge/MC. Go back through your mods and make sure you have the correct versions and are following all instructions from mod authors. This post may help you:
-
plowmanplow's post in Cannot download files was marked as the answer
Your modpack download is a RAR format archive. All archive files intended for use by the platform must be in ZIP format only. -
plowmanplow's post in Error unzipping 2 was marked as the answer
The ZIP library used by the Launcher doesn't like color code characters in file names. Look in your shaderpacks folder. Rename the Paolos LagLess Shaders file that has the color code characters in it to something else without those special characters. Many of the weapons packs in the Flan folder are throwing massive errors into the Forge latest log. Not sure what will be the result of that long term, but it looks sketchy. -
plowmanplow's post in Custom Modpack - Error Unzipping a File was marked as the answer
Your modpack archive "modpack.zip" is in 7zip (7z) format. All archive files intended for use in the platform must be in ZIP format only with the compression level set to compatibility or legacy. CodeChickenLib mod belongs in the mods1.6.4 folder, not the mods folder. You have Ender Storage and Not Enough Items mods but not the dependency mod CodeChickenCore (which belongs in the mods folder). You have DenPipes mod but not the dependency mod DenLib. You have a Forge/MC 1.6.2 version ReiMinimap. Get the 1.6.4 version. You have no config files in your modpack. This is always bad. Once you have your pack working successfully and have tweaked/tuned the configs to provide proper interaction and a balanced gameplay the full config folder needs to be included in your modpack archive before you pack is considered "complete". -
plowmanplow's post in server starting then crashing was marked as the answer
MouseTweaks{2.4.4} [Mouse Tweaks] (MouseTweaks-2.4.4-mc1.7.10.jar) Unloaded->Constructed->Pre-initialized->Errored This is a client-only mod.
-
plowmanplow's post in Big Problem with Modpack was marked as the answer
The challenge for me is that your updated download you provided works. The modpack itself does not because you haven't updated the version number and download URL in the pack settings. Until the latter happens your client modpack won't change and you won't get a Forge log.
-
plowmanplow's post in Error unzipping was marked as the answer
The file in your bin folder named "modpack.zip" should be removed. The binmodpack.jar file, which is the only file that should be in that folder, is simply the correct version of the Forge universal binary JAR renamed to "modpack.jar". http://files.minecraftforge.net/ All versions of Forge from 1.6 on do not use a coremods folder in any way. All mods belong in or below the mods folder. However, the Forge universal JAR does not belong in the mods folder at all (see bullet point #1). Your folder named "flan" should be named "Flan" (case matters here). The files that go into the Flan folder should be left as ZIP files. Do not extract them. You have "idfix-1.6.4-1.1.0.jar" in your mods folder. Forge/MC 1.7+ mods do not require ID fixing. This should be removed. Your ChickenBones mods are out of date and should be updated (CodeChickenCore, NEI). After making these changes I was able to start your pack in a test environment.
-
plowmanplow's post in My Modpack Wont load was marked as the answer
You have set an item or block (looks like a block) to ID #200000. Block IDs must be <= 4095 and item IDs should be set to be between 4096 and 31743 in the config files. Find this ID and fix it. This post on fixing conflicts may help you:
-
plowmanplow's post in Can't load modpack, weird crash was marked as the answer
Update your Java version. That error commonly occurs when a mod version does not match the version of Forge/MC for the pack or when mods have conflicting APIs. Without more detailed logs and without the API URL it is impossible to say for sure where the issue is originating. You should be building your pack methodically so that when you add a mod and things start crashing you know right where to look. -
plowmanplow's post in Setting up my first modpack help needed was marked as the answer
You could use the CoFH config files from AoTB as a reference.