-
Posts
4594 -
Joined
-
Last visited
-
Days Won
74
Everything posted by plowmanplow
-
The contents of your modpack are in a subfolder inside the archive. All the required folders (bin, config, mods) MUST be in the top level of the folder structure inside the modpack archive. It looks like you have renamed ForgeMultipart to be your modpack.jar in the bin folder. You need to get the Forge universal binary jar file and rename that to be your modpack.jar. Fix that and see how far you get.
-
You need to uncheck the box in your pack settings labeled "Force Directory Change". You cannot change the name in the URL for the modpack. That is your pack "slug" and is set when first created. If you want a different URL/slug you will need to make a new pack.
-
Worth a shot Let me know if it's fixed (while using the latest versions of Immibis' mods). I'd love to include it.
-
I think this is related to the whole "cables are invisible" thing you have going on. I have the same version of Chisel you are now using and everything works as expected.
-
You have included the entire client contents of the bin folder. The ONLY file that should be in there is modpack.jar. You have files in the coremods folder. Forge/MC 1.6+ does not use the coremods folder in any way. All mods belong in or below the mods folder. You have the Forge installer jar in the coremods folder. This file should be remove completely. As I mentioned in the post the last time I tried to help you, you do not have Better Dungeons installed correctly. You need to follow the author's instructions. (open that zip and look inside). Your CraftableSpawners mod looks like it is for Forge/MC 1.6.2. This might be a problem. You have an ancient version of IndustrialCraft 2. If you intend to include IC2 you will want to look at this post: (check the versions and compatibility of ALL the other IC2 mods you have included as well) As I mentioned in your previous thread. You MUST include a full set of configs with your modpack. These are generated in the config folder where you are testing the pack as you assemble it. You are testing it locally, right? Always, always include this entire folder with your pack. Fix all of those and come back when you hit another snag.
-
Your modpack archive download link/URL is not "direct". If you click on the link or paste it in the browser and it opens a page with a download button, that's not a direct link. The only file in your bin folder is "Farm Pack.jar". So many things wrong with that. 1) The file should be named "modpack.jar". 2) The file MUST be in ZIP format, not RAR format. 3) The contents of the file are inside a subfolder. Do not mess with the Forge universal jar file in any way unless you know what you are doing. Just rename the Forge jar to modpack.jar and put it in the bin folder. Give that a shot and hop back here if there are more problems.
-
That happens if you include a "servers.dat" file in the top level of your folder structure in your modpack archive. This file is created automatically when you create a server entry in the client. Simply start with a "clean" file (remove it) and make your server entry after starting the client. Include this file in your modpack.
-
Don't set the "server-ip" field in server.properties. This should be left blank. Are you able to connect to your "internal" IP address for the server? If you are inside your network you should be using the local address, not your public IP to connect to the server. Make sure that the port listed in server.properties is the port you have opened in your DLink and that the redirect is pointing at the correct internal IP address. Make sure the port is open in the firewall of the machine running the server (if the firewall is on).
-
Modpack ID conflicts that I don't know how to fix.
plowmanplow replied to Mister_E99's topic in Platform Pagoda
@ggoo132: Don't necro-post hijack another thread. Always start a new one with a new problem/pack. As for your problem, part of making a "correct" modpack includes placing a full compliment of config files in the modpack archive inside the config folder. Use the "fixed" collection of config files to do so. -
[DIFFERENT] ModPack Crashing Upon World Loading
plowmanplow replied to NuclearNarwhal's topic in Platform Pagoda
I have no experience using Java on a Mac, but it is my understanding that older versions of MacOS/whatever come with Java 6 and it is somewhat tricky to get things updated to Java 7. Google may be your friend here. -
Caused by: java.lang.RuntimeException: Duplicate stat id: "achievement.whatdidyoueat" and "achievement.divineintervention" Looks like an achievement ID conflict between DivineRPG and some other mod. Hopefully it is possible to change the ID in the config.
-
[DIFFERENT] ModPack Crashing Upon World Loading
plowmanplow replied to NuclearNarwhal's topic in Platform Pagoda
The crash report you posted clearly shows that your client is using Java 6. -
Start Hexxit.jar instead of minecraft_server.jar.
-
I can not pick up items in voltz modpack in my server
plowmanplow replied to gustavoma12's topic in Platform Pagoda
You are probably starting the minecraft_server.jar instead of the Voltz.jar. -
[DIFFERENT] ModPack Crashing Upon World Loading
plowmanplow replied to NuclearNarwhal's topic in Platform Pagoda
Trying to run 1.7.2 mods with Java 6 is going to end poorly (as previously mentioned). -
ModPack Crashing Upon World Loading
plowmanplow replied to NuclearNarwhal's topic in Platform Pagoda
Without looking at a new crash report now that you switched to a current Java 7 install it is impossible to say. -
Your pastebin has been removed. Please provide another crash-report and/or ForgeModLoader log file as well as your API URL to the modpack.
-
@saarsc: Assuming they are using this pack: http://www.technicpack.net/modpack/details/ultra-modded-survival-pack.266012 , that pack is managed by Solder and there is no single modpack archive to download. This thread should be dead.
-
ModPack Crashing Upon World Loading
plowmanplow replied to NuclearNarwhal's topic in Platform Pagoda
This problem is caused by using Java 6 on your PC. ChickenBones' mods require Java 7, and a recent version at that. Update your Java version to Java 7 64bit JRE for Mac. -
This should be posted in the Tracker following the guidelines there.
-
List of good places to host your modpack file
plowmanplow replied to FatsackTony's topic in Platform Pagoda
@acmr212: Yes, you do have to pay to have an entire folder where all files contained within are automatically shared. However, you can simply share individual files with ease with only the free account. Dropbox works fine for modpack hosting. -
@RavioliMonster: Client Only mods: Mob-Dismemberment Voxelmap
-
Custom pack launches to Vanilla Minecraft?
plowmanplow replied to Aidoboy's topic in Platform Pagoda
Works fine for me. What kind of errors are you having? This is where using pastebin.com or other file sharing service to post your crash-report and FMLClient log would be helpful.