plowmanplow

Any server capable of executing Forge or Cauldron/MCPC+ as the server binary should theoretically be capable of hosting a custom modpack server. Keep in mind that modded servers are much more hungry for RAM and CPU resources than vanilla and the bare minimums for even a small pack can drastically exceed the minimums for a modded server. Beyond those non-specific statements it is difficult to say without host specific information and details about a particular pack.

Happens to the best of us. Don't beat yourself up about it

Unless you have a valid backup of the region files in which those chunks reside then no, there is no way to get them back.

From the Platform Pagoda forum page: http://forums.technicpack.net/forum/65-platform-pagoda/ There is a "Start New Topic" on the right side near the top.

I believe your URL needs to be this: http://solder.unknowncraft.us/index.php/api/

@NNanoKightt: Start a new support thread in this forum.

As mentioned before in the other threads you have posted in or created, this issue belongs in the tracker. (likely antivirus related).

If some mod authors do not want you to put their mod in your private modpack and you choose to do so anyway, there is little to fear. While it might be the "nice" thing to refrain from including such a mod <chuckle> no one will hunt you down in the dead of night seeking vengeance.

DiddlyDoo802: You are missing the required libraries. Are you using MCPC+ (Now called Cauldron)? If so then you need to be using the latest version (Build #272 if I'm not mistaken).

The Technic team has stated multiple times that "Tekkit Lite" is frozen and will not be updated. Times have changed. That being said, I have a 1.6.4 modpack that is essentially Tekkit Lite. Everything (with a couple notable exceptions) is just the original mods updated or switched to their spiritual successors. JCLite: http://www.technicpack.net/modpack/details/jclite.349189 There is even a server pack there. Note: You CANNOT updated your Tekkit Lite 1.4.7 world to work with this pack. Don't bother trying.

@Simsari: I have a 1.6.4 modpack that is essentially Tekkit Lite. Everything (with a couple notable exceptions) is just the original mods updated or switched to their spiritual successors. JCLite: http://www.technicpack.net/modpack/details/jclite.349189 There is even a server pack there. Note: You CANNOT updated your Tekkit Lite 1.4.7 world to work with this pack. Don't bother trying.

You only need one thread to get help on your custom modpack. It makes it very difficult (and frustrating) to provide assistance when I'm trying to find context for your issues across 3 different threads. Have you made changes to the pack and re-published/updated your pack settings? If so I will download the pack again and go through it.

The original error indicates you have included a client-only mod in your server's mods folder. As for the permsize issue, please provide links to your client pack page or API URL as well as the contents of the script you are using to launch the server.

The URL you posted is not a direct link. You would need to change it to this for it to be a direct link (direct links are required by the launcher): https://dl.dropboxusercontent.com/s/scbakv1z7rnlfxx/Modpack%20template.zip You have removed the version numbers from all of the mod names. Don't do that. It makes it almost impossible to debug anything. You have included Forge for 1.5.2 but have mods for 1.6.4. Which version of Forge/MC are you trying to build a pack for? What do you have your Technic pack settings configured to be? You have NotEnoughItems mod but not the required dependency mod CodeChickenCore. You have OpenBlocks mod but not the requried dependency mod OpenModsLib. Fix all of these issues, including re-downloading the mods so the file names have the version numbers in them and then come back here if you are still having troubles.

Unfortunately, sometimes it works, sometimes it doesn't. An admin or other Technic person would need to weigh in to get you a better answer.

This support request belongs in the Tracker for BTeam. There is a link at the top of this very page.

@supawupaa: Don't hijack someone else's thread. Start a new one if you have problems. However, I'll short-circuit things this time by saying that the pack author needs to fix his pack. There is nothing you can do to fix it short of making your own pack. Contact the author.

Each time we get to a new page in the thread please include a current link to your modpack/API URL so that I don't have to search through page after page of posts to get the correct URL. Client: Your client still has extra stuff in the bin folder. The bin folder should ONLY contain modpack.jar. You really need to update ProjectRed to the latest version. The version you have has known issues. Mods to remove from server mods folder: Damage Indicators NEI Addons NEI Plugins Optifine Rei's Minimap Making the above changes and remove the client only mods listed above allowed me to start a server and connect with your client.

Why are you renaming all the mod files (names and CAPS) from the names applied by the mod authors? It is highly distracting and unnecessary. You have dozens of item ID conflicts between mods which must be resolved. Check your ForgeModLoader-client-0.log file. BetterDungeons/ChocolateQuest is not installed properly. You are missing the top level Chocolate folder. Re-download the mod from the author's preferred distribution channels and install correctly. You have an enchantment ID conflict from ForbiddenMagic. Must be resolved. You have not included any config files in your pack. Your pack is so large and complex that this is fatal. The default config files have almost 70 block ID conflicts which must be resolved before we can continue debugging the pack.

Your bin folder contains extraneous files. It should only contain modpack.jar. Remove all the other files and folders inside the bin folder. Better Dungeons/Chocolate Quest is not installed correctly. You are missing the top level "Chocolate" folder. Re-download the mod from the author and install it correctly. You have item ID conflicts between: ExtraBees & EnderIO, TMechworks & ExtraTrees, Forestry & ProjectRed, Factorization & ProjectRed

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

Client modpack concerns: Your modpack.jar file is much larger than it should be. The one you have is almost 500K larger than expected. The modpack.jar file is just the Forge universal binary jar downloaded and renamed to "modpack.jar". Nothing more, nothing less. No need to extract it and re-compress it. You have three item ID conflicts between ICBM and Statues mods. These will need to be fixed before attempting to get a server working. The version of Optifine is a couple revisions out of date. An update is highly recommended. You have a couple API zips in your mods folder that can/should be removed: Resonant Engine Development API, UE API ProjectRed desperately needs to be updated to the latest version (known crash problems). Mods removed for server pack: Armor Status HUD Status Effect HUD Not Enough Keys Optifine TiCToolTips Zan's Minimap Doing all of the above allowed me to connect to the server pack with your (fixed) client.

You cannot use (to my knowledge) Mediafire to reliably host your pack. They frequently change their direct download links which will break integration in the Platform/Launcher. Use something like copy.com instead. You have not installed Tropicraft correctly. Only get your mods from the mod author's preferred distribution channels. This not only ensures you don't get scam/virus/adware/malware on your system, but you will also get the correct installation instructions. In this case you have one of the six mods required to run Tropicraft. You have something like 50 block ID conflicts in the default config files generated by the mods in your pack. All of these (along with any item ID conflicts) will need to be resolved. After that you MUST include the full set of working configs in your modpack archive.

@Alpha2Beta: It is muchly preferred for users requesting help for a specific problem to start a new thread and not hijack existing requests for assistance. Even though your problems may be (or seem) similar they are often different in some way and distract from the current thread's narrative.

You will find more direct support for Launcher issues by using the Tracker (top of this very page) for the Launcher.