plowmanplow

This post belongs in Platform Pagoda. Additionally, don't do multiple posts or cross post for the same issue. If you intend on including IndustrialCraft for 1.6.4 I highly recommend looking at this post: The contents of your modpack archive is just another ZIP file. Your archive should directly contain the folders: bin, config, mods.

My understanding is that the issue comes from mods not properly using the Forge Entity Registry. That won't really help you resolve the issue, but more specifics are useful.

Combustion engines have decent power output (6 MJ/t) but have a propensity to explode. Thermal Expansion's engines (Steam, Magmatic) will never explode, although they can "lock up" if run for too long with no drain of power. Thermal Expansion's engines also have no cycle time since they don't have to cool off before restarting. Thermal Expansion provides a Redstone Energy Cell which can store MJ (Buildcraft Energy). This can allow you to build a mechanism which only runs the combustion engines when there is a significant amount of work to be done while always keeping power available for your machines. Buildcraft wooden conductive pipes ALWAYS extract power and cannot be turned off. Buildcraft conductive pipes will explode if too much power builds up inside them. Thermal Expansion Redstone Energy Conduits never explode and only pull power when something needs it. They are more expensive/challenging to make than conductive pipes, but they are superior in every way. One of your first goals should be to get a system set up to make Redstone Energy Conduits. Keep in mind that you can use Power Converters to convert from one kind of power to another. This would let you make IC2 energy (EU) and convert it to MJ to run your Buildcraft or Thermal Expansion machines.

Block ID conflicts will either halt the client and create an IDConflicts.txt file or it will crash back to the launcher. For the latter you will need to look at the details of the crash in the ForgeModLoader-client-0.log file to find the conflicting block ID. Block IDs need to be <=4095. Item ID conflicts will not (usually) crash the client, but it will make portions of mods unusable because their items have been overwritten with items from other mods. For these you need to check your ForgeModLoader-client-0.log file for the word CONFLICT. There will be detailed information about which mods are conflicting and on which ID. Keep in mind that the ID listed in the config file is usually shifted down by 256 from the one you see in-game. You can use NEI to dump a full list of in-game IDs to a CSV file (Google this). The CSV file will allow you to find unused IDs which will allow you to resolve the conflicts. In-game IDs must be <=31999 so the config file entry needs to be <=31743.

If it is not your modpack you will need to try to follow up with the pack creator. Since you would have no way to permanently fix the pack, suggesting fixes won't get you anywhere. Many, many modpacks are either abandoned or poorly maintained. You may be experiencing one of those.

net.minecraft.network.packet.Packet24MobSpawn One of the mods in your pack is not properly handling entity spawns. I see this all the time with OreSpawn, but you don't have that in your pack. Been dealing with that particular error for many moons and have never gotten a good answer for what is specifically conflicting.

Not sure what to suggest. The pack works fine for me both in my test environment and as a normal pack. Are you able to use other packs, including the built in Technic ones, without trouble?

Yep, that's an odd one. The glass.png texture seems totally fine. Correct color scope, correct bit depth, transparency looks find, format is correct, size is correct.

Most likely cause is that you have a client-only mod in your server mods folder. These are the mods which need to be removed: NEIAddons NEIPlugins NotEnoughKeys Zan's Minimap

Yep

Are you sure about upgrading Java? Take a look at this thread: '?do=embed' frameborder='0' data-embedContent>>

If you provide a link to the texture pack I'll take a look at the textures to see what's up with the glass.

In the future, this is a spoiler tag: And it would look like this: As for the pack, it has a couple problems: The bin folder has too much stuff in it. It should only contain the file "modpack.jar". There are a couple item ID conflicts which should be resolved. The pack works fine for me. Make sure you have the latest build of Java 7 for your OS installed.

Client Setup: You need to update your IndustrialCraft 2 mod in your client before proceeding. I recommend looking at this post: You should remove worldofdinos-1.0 mod as it is only relevant when you also include Tropicraft mod which you do not have. It looks like you have an item ID conflict between two CFM items. Might want to look into that. Server Setup: Download the Cauldron installer: http://files.minecraftforge.net/maven/net/minecraftforge/cauldron/1.6.4-1.965.21.89/cauldron-1.6.4-1.965.21.89-installer.jar Install Cauldron to a folder on your local PC. We'll refer to that folder as SERVER. Copy the config and mods folders from your client modpack to SERVER. Remove client-only mods from the SERVERmods folder: rei_minimap folder and contents NEIAddons mod NEIPlugins mod NotEnoughKeys mod ReiMinimap mod At this point you are all done with the server build and just need to copy it to your Linux machine or ZIP up the server and copy that over and extract it. You'll need a launch script for the server. There are better resources than this for doing things in the most optimal way, but this will get you started: launch.sh #!/bin/bash java -Xmx2048m -Xms2048m -XX:PermSize=256m -jar cauldron-1.6.4-1.965.21.89-server.jar nogui

which makes little sense unless you aren't using the correct URL or something. If it were me I would put a sniffer on the line and see exactly what is going on with the data between you and Technic's servers.

If you are unable to copy & paste that full command above and have it complete successfully you have something else going on that is getting in the way of communication with Technic's servers/services and is unrelated to Solder specifically. The big question is what is getting in the way and how can it be resolved.

Try copying this and executing it: wget -O mcversions.json http://www.technicpack.net/api/minecraft That worked fine for me and should for you.

Are you sure the server you are running Solder on is retrieving that file correctly? You might try doing a wget on that URL from the server just to make a sanity check.

This likely belongs in Platform Pagoda (if anywhere). It is challenging to diagnose problems with a modpack without a link to the modpack in question.

Hmm, I know I had to do some manual manipulation of the database contents when I first installed Solder to get around a problem. Wonder if it was related to what you are experiencing. So long ago my memory isn't behaving. I do know that when I had that (or a similar) problem I just went into the code and saw what it was looking for and massaged the database to make it work the first time, after which I had no more problems.

My memory is fuzzy but I seem to remember something about one of the weapons stations causing problems in certain circumstances. Take a look at your ForgeModLoader-server-0.log or server.log files to see if those provide more information, specifically about which block/location is causing the error. You could then use MCEdit to remove that block.

@SXScarecrow: Your Cauldron downloads in the OP are incomplete. Cauldron no longer automatically retrieves its library files. One must run the Cauldron installer to get all the required libraries. It would be helpful to reference which version of Cauldron you are providing. It would be helpful to provide a link to the official Cauldron downloads. http://files.minecraftforge.net/Cauldron/

You may want to start here if you wish to make a server: '?do=embed' frameborder='0' data-embedContent>>

A quick Google search turns up some info: '?do=embed' frameborder='0' data-embedContent>>

Sound like an issue which would belong in the Tracker for the Launcher. The link is at the top of the page. Make sure you are using the latest build of Java 7 for your OS.