Jump to content

plowmanplow

Discord Moderator
  • Posts

    4594
  • Joined

  • Last visited

  • Days Won

    74

Everything posted by plowmanplow

  1. Familiarize yourself with how to get the mods: You could use my BareBonesPack as the base for building your own modpack: Build your client pack and come back if/when you are prepared to make a server.
  2. Cauldron (like Forge) is made up of a main JAR file and a folder full of libraries. Cauldron (like forge) must be installed the first time after which you can just replace the main JAR if doing a minor upgrade. Installing the server just extracts the main JAR and downloads the libraries into a folder. Once you have those you can copy them anywhere you like for setting up your local server.
  3. It's just copy.com being wonky sometimes. If you completely reload the page (force reload) it comes up fine.
  4. The options should be "Install Server" and "Extract". You want "Install Server".
  5. Updated 1.7.2 to 1147 Removed older 1.7.2 builds Added 1.7.10 1187
  6. You have a version of Mr. Crayfish's Furniture Mod for Forge/MC 1.6.2. You need to get the latest 1.6.4 version from here: http://www.mrcrayfish.com/furniture.php?p=2 You need to uncheck the box on your pack settings page labeled "Force Directory Change".
  7. The download URL in your pack settings is not a "direct" url. For your link you need to add "?dl=1" (without quotes) to the URL to make it direct. The BetterDungeons/ChocolateQuest is not installed correctly. There is a top level folder named "Chocolate" which is missing. Get the latest version and install correctly. The default generated configs have a block ID conflict between Immibis' mods and TradeBooth. You only have a few of the config files included in your modpack archive. Your archive has 8 config files where the working pack has 116. It is imperative that the full compliment of config files be included in the modpack archive in order to ensure that the clients and server are synchronized. You have an old version of IC2 with known problems. If you intend on including IC2 for 1.6.4 I highly recommend looking through this post: You probably want to update to BigReactors 0.3.4A2 to fix some fatal bugs and provide more features. Fix those and come back if you have more difficulties.
  8. This post belongs in the Platform Pagoda forum. Hopefully one of the mods will move it. This line: java.lang.IllegalArgumentException: Slot 3972 is already occupied by resonant.lib.multiblock.BlockMultiBlockPart@128d0580 when adding micdoodle8.mods.galacticraft.core.blocks.GCCoreBlockAluminumWire@1a95df8b states that Resonant Engine mod is conflicting with Galacticraft mod for block ID #3972. You will need to edit the config file of one or the other mod and change the ID to something different/unused.
  9. Thermal expansion works perfectly fine with BoP. I use that combination on two of my custom modpacks.
  10. You only have a small number of config files because each config file is created when its mod gets injected into Forge/MC. However, your pack is dying very early in the initialization process so none of the other mods are loaded which means their config files do not get created. In your case, you didn't properly install Weather Mod. Weather Mod has four zip files required during installation. You only copied in three of them. Once you get that installed properly you have three block ID conflicts related to CFM which are easily resolved. After the pack starts you need to open your ForgeModLoader-client-0.log file and search for the word CONFLICT. The default configs have five item ID conflicts which will also need resolved.
  11. Please see Seeing as you haven't changed the modpack archive which is referenced by your pack settings in any way, I would expect the pack to still not work. I told you what you needed to do to fix the problem. Failing to follow my advice will result in your pack still not working. If you wish to be more precise (relate exactly what you tried, what you changed, what isn't working, crash-reports, FML logs, etc.) I might be able to offer more assistance.
  12. This question probably belongs in the Tracker for the Launcher: http://forums.technicpack.net/tracker/project-1-technic-launcher/
  13. Yep: files.minecraftforge.net/Cauldron/
  14. For this copy.com share URL: https://copy.com/MnBN4APptrEJ This would be the correct direct link: https://copy.com/MnBN4APptrEJ?download=1
  15. @Zeus: Don't hijack threads. Start a new one with the pertinent information (Pack link, crash report in a spoiler, contextual info, etc.).
  16. Your Dimensional Doors data may be corrupted. If you haven't built anything in pocket dimensions you can try deleting the DimensionalDoors folder in your save (always make a backup).
  17. Your modpack.jar file is actually named "modpack.jar.jar". In order to prevent this you need to set your Explorer to "always show file extensions". Google that phrase. You are using an ancient version of OptiFine. You need to get the latest version. (HD_D1).
  18. Probably with the community it was initially for... but you'll not find too many folks around here who would get worked up about it.
  19. Just uninstall anything listed in your installed programs related to Java and re-install the latest Java 7 64bit JRE.
  20. Your modpack.jar file is corrupted somehow. Normally, the modpack.jar file is simply the Forge universal binary JAR file renamed to modpack.jar. However, it appears as though you are trying to include LiteLoader. As this is a 1.6.4 pack it goes in a little oddly (you have to edit the version.json file inside the Forge jar). I have a Forge JAR for 1.6.4 965 with LiteLoader already integrated here if you wish to use it: https://copy.com/8DhBuUd740kz?download=1
  21. Keep in mind that you log into the Launcher with your Mojang/Minecraft account (your IGN or email address) and password, NOT the account you use to log into these forums or into the modpack management Platform.
  22. In the first response you quoted from me please pay close attention to the names of the files. I say that you need "modpack.jar" and should remove "minecraft.jar". Those are two different file names. The config file you included in your pack is empty. Those config files you talked about? They belong in this folder. You should be providing the config files to the client, not letting it generate them automatically (which is what is happening now). Just because the client starts does not make it correct. Open your ForgeModLoader-client-0.log file and search for the word CONFLICT. I would be willing to bet that you have a number of item ID conflicts which will need to be resolved. Without running the pack as a server (which I won't do until you fix your config file issues), these mods look like they are client only: REIMinimap NEIPlugins NEIAddons
  23. WranglerPack-1.0.0.zip
  24. Client pack analysis: Your bin folder should only contain the modpack.jar file. Remove the minecraft.jar as it is superfluous and violates Mojang's TOS. You have no config files in your modpack. You say that you started with the Tekkit modpack. It includes a full set of configs for the mods in the pack. Why would you remove them? Just as a client pack (no server intended) the pack will never work without a full set of config files. Copy all the config files from the Tekkit pack and then get your pack working locally which will yield a complete set of config files, including the ones for the new mods. The requirement for configs is paramount when intending to have a server for a modpack since the client and server MUST have their configs synchronized and the only way to do that is to provide a full set of configs in the modpack. Since you are building a new pack I would highly recommend updating some of the mods to more recent/stable versions. Mods like BigReactors, Calclavia's mods (you'll end up needing to completely remove CalclaviaCore), ChickenBones' mods, Immibis' mods, etc. all have significant updates. I would normally go on to provide a list of client-only mods which would need to be removed from the pack in order to get the server working. However, the state of the pack is not currently viable as a client. Trying to do a server setup with an invalid client modpack is an exercise in futility.
×
×
  • Create New...