plowmanplow

Without a link to your pack, at least as a download archive, we'll be unable to help you.

Follow this guide: If you get stuck or have troubles I'll help you get through them.

[21:01:51] [Client thread/INFO]: [java.lang.Throwable$WrappedPrintStream:println:-1]: java.lang.OutOfMemoryError: PermGen space It looks like you need to increase the PermSize option for the pack.

Everyone knows this and will either comply with the restriction or not. That being said, the instructions I provided are still quite useful since it is common to restrict blocks or items to specific ranks once players are trusted. This may (and should) have nothing to do with donations.

@The_Doctors_Life: You can use a simple web page I put together to get the metadata for an API URL. This can help diagnose things like a user not incrementing the pack version, or having the incorrect version of MC selected. It also provides a link to download the current pack: http://www.circlecraft.info/platform/ Your pack settings indicate a MC version of 1.7.9. This won't work and should be set to 1.7.10. (visible using the link I provided to The_Doctors_Life) Your modpack archive is in RAR format. All archive files intended for use by the platform must be in ZIP format only. This includes both your pack archive and any mod ZIP files. Forge for MC >= 1.6 does not use a coremods folder in any way. All mod files belong in or below the mods folder. The 1.7.10 folder belongs in mods. PowerCrystalsCore is for <= 1.6.4 and should not be in a 1.7.10 modpack.

Please provide the API URL (the URL you paste into the Launcher to add the pack) when requesting assistance for any custom modpack. Please provide relevant logs by using a pastebin service (don't paste huge logs here). The black font you have used is nearly impossible to read. I would agree that the mods listed there are fairly tame and should not be causing much lag on any system which can run larger packs. The implication is that there is either some odd incompatibility between two or more mods, or that something odd is going on with your system. More information about system specs and configuration would help determine where the issue might be arising.

Always provide the API URL (the URL you paste into the Launcher to add the pack) when requesting help for a custom modpack. Are you able to reproduce this crash with specific actions or conditions? Does it always crash when those conditions are met or only some times? If you don't have specifics, can you provide some idea of what is going on when this happens? Any sort of pattern?

You are zipping the pack up incorrectly. Don't click on the top level folder and tell it to zip up. Go into that folder, select the folders you want in your pack (bin, config, mods) and make those folders into your zip file.

Forge versions for MC >= 1.6 do not use a coremods folder in any way. All mods belong in or below the mods folder. Your TeamCoFH mods are out of date and mismatched. Update all your TeamCoFH mods. Your pack has no config files. This is always bad. Config files are the only way to balance mods against each other and to ensure the pack is set up correctly. Fix these issues and come back if you still have troubles.

Well, I have posted 4 or 5 times on minecraftforum.net providing some assistance and talking to mod authors. I also have some old posts on the BDCraft forums providing texture packs for folks. Maybe he's referring to the 500G/month of bandwidth I provide each month hosting the 64x and 128x Sphax packs for TekkitLite. Who knows.

The Launcher uses your Mojang account credentials. The website uses your Technic account(s). If this is not your problem you should go to the Tracker for the Launcher (top of this page).

Always provide the API URL (the URL you paste into the Launcher to add the pack) when requesting custom modpack assistance. Don't use Java 8. Use the latest Java 7 for your platform. Your Immibis mods are mismatched. You have DimensionalAnchors 55.0.0, but ImmibisScore 55.1.6. Update to DimAnchors 55.0.3. Fix these and come back if you still have troubles.

It has been proven multiple times that there is no end in sight to the clamp down on Bukkit reference/API server software. There is a (slight) possibility that all the Sponge work will be back-ported to 1.7.10. It is exceedingly unlikey that anything will be back-ported all the way to 1.6.4. It is safe to assume that all versions of Bukkit-based servers <= 1.6.4 are now in curator status and will never be updated/changed/added to/etc. With Forge (supposedly) supporting connections by vanilla clients I believe Sponge will also allow non-modded clients to connect. In theory it should be possible to do something like having a non-modded gateway that passes off connections to the appropriate pack/server in a bungeecord type fashion. However, this is all future-maybe/pie-in-the-sky kind of stuff since there isn't even a server for Sponge yet.

For example, for this API URL: http://www.technicpack.net/api/modpack/cheese-ball The slug is "cheese-ball". This is automatically generated based on your pack name when using Technic's interface. Don't use special characters in your pack name or slug.

12.12 04:24:33 [Server] ERROR Could not pass event PlayerInteractEvent to GriefPrevention v9.3 As I previously mentioned: You are using a version of GP for Forge/MC 1.8.

In any practical way (not dealing with theoretical "what ifs") you are 100% correct. There is no way to do this. Maybe once Sponge is up and running and on 1.8+ server, but not for anything below that.

Use a pastbin service to post full logs. Uninstall Java 8 and install the latest Java 7 for your platform (32bit/64bit). Always provide the API URL (the URL you paste into the Launcher to add the pack) when requesting help for a custom modpack. Caused by: java.lang.ArrayIndexOutOfBoundsException: 6990 That block ID must be <= 4095.

Try not using any special characters in either your filenames or pack slugs.

You need to uncheck the box labeled "Force Directory Change" in your pack settings page. You have no config files in your modpack. This is always bad and frequently fatal for 1.6.4 modpacks. This link has information about config files:

The contents of your modpack archive are in a subfolder named "Mo Mo Stuff Modpack". This won't work. The required folders (bin, config, mods) must be at the top level of the folder structure inside the modpack archive. Also, your pack version is still 1.0. If you don't increment this number when you change your modpack archive file the Launcher will never know that the pack has been updated.

Just like anything else you add to the server, check your logs for references to GriefPrevention. If there are errors there it may explain what is going on. Also, please use a pastebin service for large copy/paste data.

I'm just relating how it is "supposed" to be installed. If you are doing something different and it's working for you, go for it. If you are doing something different and the behavior is not what you expect (i.e. the mod working correctly), then maybe a bit of standards compliance is in order.

Griefprevention (GP) works fine in Cauldron. I use it on all my servers. If it's not working for you then something isn't set up correctly, or you are using the wrong version of the plugin. Make sure you are using the latest 9.x for 1.7.10 (I believe this is 9.1). GP does a decent job, but it's not perfect. Some mod items and machines can bypass claims protections. There is no "fix" for this in <=1.7.10. You can usually ban items/blocks totally, or restrict them to ranks, but nothing is perfect.

There is a proper place for this: http://forums.technicpack.net/tracker/project-1-technic-launcher/

I mean that the name of the file from the author for SmartCursor is "SmartCursor-1.3.0-1.7.10.zip". Your file was "smartcursor-130-17107945892.zip". Don't mess with the file provided by the author. Don't extract it, don't rename it, don't add to it, don't edit it. Just download the ZIP file and put it in your mods folder. I would recommend caution because almost every time I see folks with problems like this they are using a Mac. I think there is something which may be automatically extracting ZIP files. Don't do that.