plowmanplow

Forbiddenguy sent me a link to his server setup out of band. His server setup contained bukkitforge. This is what I was referencing.

With MCPC+ you just download the latest build for your Forge/MC version (currently #251 for 1.6.4) and the first time you start that it will retrieve all the required libraries.

I highly recommend switching to MCPC+ for your Forge + Bukkit server needs. Give that a shot and let us know what happens.

I have noticed a trend recently. I spend a fair amount of time on these forums mostly doing custom modpack support while also trying to contribute elsewhere as I can. Lately, I will respond to a request for help in a thread only to have the original poster start responding with the extra needed information (like links and logs) in personal messages to me. This causes a few challenges. First, I'm only one person. There are a lot of brilliant, helpful folks on these forums and as soon as the responses go private they all lose the opportunity to contribute. Second, there are a lot of folks who come here looking for help and search the forums for solutions to their problems. If all they find are questions without answers it detracts from the community and creates more work for folks such as myself who like to help. And last, but not least, sending me a separate personal message half way through a thread trying to solve a problem is very distracting and requires that I take a not insignificant amount of time figuring out the context of the message. I help a lot of different people and I don't really remember who has what problems. Keeping the information in the original threads will reduce my distraction and and let me focus on what I enjoy: fixing custom modpacks. Each thread is a narrative that starts with the original post and often flows through many responses before reaching a conclusion. Breaking that story by taking responses out of band I feel is a detriment to the community. Let's keep things focused and organized so we can all provide the best support possible.

Use MCPC+ for the server jar. Remove any mods that are "client only" like minimaps and GUI stuff.

If this happened after you added mods the implication is that one of the mods was compiled against a different version of Scala than what your server jar uses. Without more info (your pack page, modpack URL, etc.) it will be difficult to diagnose.

'?do=embed' frameborder='0' data-embedContent>>

Sooo, before I get started on the contents of the pack we need to talk about how to package a modpack. It should look something like this: bin -> modpack.jar config -> bunch of config files mods -> all your mods Some mods, such as Flan's Mod, would need a top level "Flan" folder with weapon packs in it, but the vast majority of packs will/should look like the above. Your pack has a TON of other stuff in it. You have basically zipped up your entire modpack folder and this just won't work. Additionally, the fact that there is an extra copy of your pack in the "cache" folder doubles the size of your download. An item of note: You have some very old versions of some of these mods which have known bugs and instabilities. I would highly recommend updating. Mods Removed to get a server running: mapwriter NEIPlugins NotEnoughKeys REIMinimap Here's the kicker. I'm using MCPC+ for the server and for whatever reason it wasn't downloading the libraries properly. I ended up having to copy them from an existing server installation. After that everything worked fine.

This is typicall provided by using Bukkit plugins on a MCPC+ server. Plugins like Essentials is quite common for this which allows you to specify a "kit" for starting players.

There is a better place than the Platform/custom modpack related forum to try to seek help with BTeam, a Technic sponsored pack. Asking for help and providing no pertinent information such as system specs, logs, settings, etc. seldom yields results.

Your Buildcraft is outdated (4.1.2 vs. 4.2.2). Update this. Mekanism includes the BuildCraft API and since his included version is newer than the one in your version of BC, Crashy McCrashter. You have an extraneous file "DynamicLights_1.6.4.zip". This file looks to be the installation download from the mod author. Remove this. You have some very old versions of your chosen mods. You say you are trying to add Mekanism but are not using the most recent version (by a fair margin). You have existing ID conflicts between: Atomic Science and Glenn's Gasses, Glenn's Gasses and ICBM (just because a pack starts doesn't mean there are no conflicts... one must check the logs) Once you address these issues there will be some ID conflicts between Mekanism and your existing mods, but I'm sure you are up to resolving those.

You still have the exact same old version of forge. You updated TreeCapitator... to the 1.7.2 version of the mod. You need to be using the 1.6.4 version. The RottenFleshToLeather mod for 1.6.4 I have never gotten to work. However, the 1.5.1 version works fine (surprisingly enough). You still aren't including any of your config files. Making these changes allowed the pack to start up however, you have item ID conflicts between Pixelmon and FLabsBF. About config files: You need to be testing your pack locally before you try making it into a modpack which is published through the platform. You can use something like my BareBonesPack modpack to do so. The big point of that is once you start the mods for the first time they will create their config files. These config files can be used to fix things like those ID conflicts you have. Once the config files are tweaked and tuned you would include the entire config folder in your published pack.

No worries, and you aren't annoying. It is almost always better to learn how to do a thing than to follow some procedure you don't understand because if even one thing in that procedure needs to change you will have no idea how to continue.

It should be trivial to stand in that chunk and type "//chunk" followed by "//regen" assuming you are using MCPC+ and have WorldEdit installed. If you don't I suggest it.

You are including the entire contents of the bin folder in your pack. This should just contain "modpack.jar". You probably don't want to distribute your pack with IDFixMinus in it. That is only for "fixing" your pack before distribution. You have the wrong version of IC2. The last/latest/final 1.6.4 build is #397. If you plan on using IC2, I highly recommend including some or all of this: >industrial craft tekkit 1.6.4 - Tekkit Discussion - Technic Forums Your version of Optifine is incompatible with your mod selection. Using the latest 1.6.4 HD fixed the conflict. Your version of ShadersModCore is for 1.6.2. Upgrade to the 1.6.4 version. Making these changes allowed me to start your pack with the lancher memory reservation set to 1.5G.

A link to your pack page, URL download, logs, crash reports, etc. might help us assist you.

Seeing a complete log for an entire startup procedure could be helpful.

I can't know for certain without looking at your pack (hint, hint), but it looks like you might have the ChickenShed mod 1.1.2 for Forge/MC 1.5+ up to Forge Build #953 but are using Forge Build #965. You would need the proper mod if this is the case. That is a very large number of mods for only allocating 1G to the launcher. This could be your problem. (wild guess) I'm fairly certain that RC will work fine with most of your mods (personal experience) and I double checked the APIs included in RC and don't see any obvious sources of conflict with other mods.

This is because your pack is invalid. The BareBonesPack (my pack) has no mods in it. It always works. What will make it not work (what you identify as "never loads") is putting in mods that aren't compatible or not configured properly. It is the job of all modpack creators to methodically assemble the desired mods and supporting files in order to achieve a working modpack. The BareBonesPack is just one tool which can be used to start the process. Check your logs. That's what I have attempted to relay in my previous posts to you: Also, you already had a thread started. It is much easier to continue working on that than to start a whole new thread and lose all that contextual information in the old one. As for your pack development, one does not simply collect mods and files from other packs and random locations on the internet. One must figure out what mods one wishes to include and proceed to retrieve those mods and the proper installation procedures from the authors' preferred distribution channels. If you want to continue debugging your modpack I recommend continuing your previous thread. Make sure you include or reference current links to your pack page and downloads.

I'm not going to do this for you. The next time you need to do this because you updated your pack or some other reason you'll have no idea how to proceed. There is a pinned thread discussing the best options for hosting your pack. Personally, I use copy.com but there are multiple solutions.

This is not a direct link and I'll not keep it there forever. You need to host this yourself using copy.com or dropbox or whatever (using a direct link).

Surprisingly enough, from the "config" folder.

No crash logs. No Forge logs. No server details (pack version, java, plugins, etc.). Makes it very hard to offer any assistance.

This is not the "make a pack" section, but since I already did all the work to figure out the bugs and get it working I'll provide a link to my work. Note that this is a temporary link and will go away some time in the not too distant future. Also note that this contains NEI and Waila since I use them during testing (makes debugging a lot easier): https://copy.com/y0SR4by9C0jB

If you "know for sure" it is an ID conflict (where the only way to know for sure is to identify which mods and IDs are conflicting) you would know how to fix it immediately. You have posted to details, no logs and no pack page or link. Without these things we are mostly unable to help.