plowmanplow

You need to allocate more memory to the launcher: java.lang.OutOfMemoryError: Java heap space It looks like you are allocating a very small amount of RAM. This is a fairly sizable pack. Allocating less than 2G is going to end poorly.

I was able to successfully add your modpack to my launcher and start a SSP world. Try removing the pack from your launcher and re-adding it.

We need to stop here until you address all the problems from my first post in this thread.

Uncheck the box in your modpack settings for "Force Directory Change".

When the pack tries to launch the configs will get created. Check your modpack folder under .technic. for the config folder. There will be config files inside. Fix those then include them in your pack.

As I mentioned previously, "The modpack.jar is just the Forge universal binary jar renamed to modpack.jar." Nothing more, nothing less (except in very rare circumstances you can safely ignore). The config files get generated in the config folder when the mods load for the first time.

Look for entries with "SEVERE" or "exception". Something with SEVERE isn't necessarily fatal, just something to be aware of.

Flans mod or something to do with the weapons packs is not properly using the ore dictionary for log/wood types. Contact the author.

How about that. So, working now?

No, I mean what are you trying to "make". I didn't see anything with the word "weapon" or "box" in the name that used wood.

See my previous post: With all due respect, the modpack in its current state is a hot mess.

Heh, I am not sure. I try to impart the knowledge to find and fix these problems. Give it a shot and see if it: Works Has a "clean" ForgeModLoader client log. (no resolvable conflicts, no glaring errors)

@IanAsh: If you have the "same thing" happening to you then you also have unresolved ID conflicts in your pack or have not properly synced your client and server configs. @both: Keep in mind that just because a client pack starts does not mean that it is "finished". Item ID conflicts will seldom cause a pack to crash outright during the startup phase. However, you'll get weird crafting issues or odd issues when breaking some blocks/machines in SSP. When trying to use a pack with ID conflicts in an SMP environment you will not only have the same kind of problems, but you can get ID mismatches. Your pack isn't done until: All conflicts have been resolved when possible (some mods report conflicts even when they are working correctly) All mod blocks have been properly added to Forge/Immibis/whatever microblock configs Mods like TreeCapitator have had their config files tweaked to support the collection of mods in the pack (custom trees, leaves, axes, etc.). Mod interactions such as power production, ore generation, etc. have been addressed between all mods. Only then should you try making a server from your pack. If these points are followed then making the server is as simple as removing a few client only mods.

Your modpack is so broken that I would basically have to start over. I am unwilling to do that.

You would be better off getting the current version from the author's build site (as recommended by the author): http://ci.md-5.net/job/Cauldron-164/ This should fix your problem.

I have already explained this but I'll try again from a different direction: Your client modpack still has the Penny Arcade (PA) mod in it and still has the two item ID conflicts I spoke about previously. The server, since it does not have the PA mod, does not have this conflict. What is happening is that the client has a different item at the same ID number than the server due to the conflict. If you either fix the client ID conflict and then copy the changed configs from the client to the server, or if you simply remove the PA mod from the client you should be fine.

Please provide links to your Technic pack page and/or the API URL.

From your FML Client log: java.lang.IllegalArgumentException: Slot 1225 is already occupied by resonantinduction.core.resource.fluid.BlockFluidMaterial@ae8086 when adding resonantinduction.core.resource.fluid.BlockFluidMaterial@c676113 Your ResonantInduction.cfg has the same value (1225) for two different blocks.

You are using a very old version of IC2 with known problems. If you intend to include IC2 in your pack I highly recommend looking at this post: You have an item ID conflict between one of the Flan's weaponpacks and craftguide. (check your ForgeModLoader client log for CONFLICT) What exactly are you having trouble crafting? What ID or exact item name?

What version of MCPC+/Cauldron are you using? Only the most recent versions will properly download their libraries.

No, the config folder gets populated when each mod is loaded into Forge. That full folder is what you need.

Go back to to your client pack and make sure you don't have any item ID conflicts showing up in your Forge Mod Loader client log. If you do (and you probably do) then fix them. After you have as many resolved as possible you will need to copy the config folder from your client pack over to the server again. (as I mentioned previously)

From your log: Caused by: java.lang.OutOfMemoryError: PermGen space You need to increase PermSize in your server startup command: -XX:PermSize=256m

If you changed block and item IDs in your configs and your FML client log is EXACLTY the same I would be extraordinarily surprised. However, since your modpack settings currently point at a modpack archive that doesn't exist I cannot be more helpful.

I'm not sure how you could be getting any errors. The exact steps I followed were to do PRECISELY what I posted above and it works. If you are seeing something different then you are doing something different.