plowmanplow

Making a dropbox link public (this works with your link): https://www.dropbox.com/help/201/en You have somehow managed to mess up your mod files in the mods folder. For instance: "orespawn164v13.zip" is actually just a renamed copy of "Morph-Beta-0.7.1.zip". You have 11 mods that are like this. It is clear that you are not testing this locally before trying to publish it. You need to have made a local working version of your pack before you try uploading a complete version to a public location. Start with just Forge. Get that working with no other mods. Then, in the same folder as your working Forge pack start methodically adding mods either singly or in logical groups (mods with their dependencies) and test as you go. That way you end up with a working pack, a complete set of configs, and you'll know immediately if/when you add something that has a problem or a conflict.

If you google "minecraft mekanism" the very first link is the author's post/thread about his mod.

The version check failing just means that the mod isn't able to retrieve the file to compare versions against. The end of that log file looks "normal".

Are we supposed to just guess as to what the source of the problem might be? No logs, no technic pack page URL, no API URL. Hard to do anything with that.

Always, always download the mods from the author's preferred distribution channels. To do otherwise risks virus infections and not having the proper versions or installations.

Get the latest version of Mekanism from the mod author's preferred distribution channels.

The URL for your modpack on your pack settings page is not a "direct" URL. The config files come from your pack folder once you get the pack working properly locally.

19.05 16:18:21 [Server] INFO We appear to be missing one or more essential library files. You seem to missing one or more library files. Try launching the server locally. If it downloads the libraries correctly you will have a libraries folder with some files/folders inside. You can simply transfer this whole folder up to your server.

If you are having problems with one of the built-in Technic packs you need to be using the Tracker for problems. InfiniX is a custom pack and you should be contacting the pack authors. That being said, it is impossible to debug problems without more information. Log files, crash reports, system settings, memory allocations, etc.

Server: Unless you are planning on having 20 concurrent users on your server you are much better off allocating less memory. 3G will be plenty for 3 or 4 people and your collection of mods. Client: The little gear in the top right of the launcher allows you to set how much memory is allocated to the client. It shouldn't be set over 3G except in VERY rare circumstances.

I posted a link to the MCPC+ builds. Which one did you get?

If you are on a 64bit OS with 4G+ of RAM and the launcher only lets you select a max of 1G allocation then the launcher is only seeing 32bit Java. Uninstall all Java entries in your Programs and Features then re-install the latest Java 7 JRE.

Midrag's 1.7.2 modpack: https://copy.com/WHSzkK42fThR Note: Modpack needs to be hosted by you. The above download link will likely be removed sometime in the next couple weeks. Mod changes: NEI used in favor of TMI Mo' Furnaces used in place of Better Furnaces as BF is not updated to 1.7.2 More Wolves not updated to 1.7.2 Added Waila because racecar

Allocate 3G for the client and no more than 3G for the server. See how that runs.

It depends on which version of Forge/MC you are building your pack for. Damage Indicators used to need to be installed server side but recent versions do not.

Disable AM2 mod Start client and enter new SSP world Open inventory Click "Options" in bottom left Click Tools Change Potions options to ALL and dump IDs Open the dumped CSV file and find an open ID (or multiple if needed) Edit AM2 config to change ID to open ID

Just like any other ID conflict. Dump the potions IDs with NEI (with AM2 disabled) and then change AM2's config to use an empty ID.

That error has no impact on the server. It is more a warning to mod authors and to let you know that unless the author fixes the mod that the item/block won't survive an upgrade.

Error from your log file: java.lang.IllegalArgumentException: Overwriting already-registered Potion am2.buffs.ArsMagicaPotion@490c6d69 @ 35 You have a potion ID conflict.

The tiny screenshot has your error: entityLandmine Exception: java.lan.OutOfMemoryError: PermGen space You need to increase the PermSize setting of your server command line arguments.

You still haven't fixed the name of your modpack.jar. It's still named "modpack.jar.jar"

MCPC+: http://ci.md-5.net/job/MCPC-Plus-164/ It just goes wherever your current MCPC+ jar is located.

Oh dear lord, what have you done? Why did you rename every single mod and remove the version numbers? Your problem likely involves having OpenBlocks mod but not the dependency mod OpenModsLib (which the author clearly states is required RIGHT on the page where you download OpenBlocks). I hope this solves your problem(s). Unless you revert everthing back to the filenames as created by the mod authors I am done supporting this pack.

Pixelmon has no affiliation with Technic. You haven't said whether you are talking about some server he uses or playing in single player. If he got banned from a server he plays on then find another server to play on. The only thing you could have paid for is Minecraft from Mojang. Technic has no affiliation with Mojang.

You have a very old version of MCPC+. Get the latest build (B262 as of this post).