plokami666

Also, this http://forums.technicpack.net/threads/lamp-solder-installation.43471/

I don't think GDrive will work. And worldtothend, I wasn't blaming you. I was just saying ^^

People have been making this mistake with dropbox so often that I think we need a sticky thread about it...

Basically the solder server expired and was never unlinked. SCT fixed this for peng yesterday (or the day before not sure). The update is still being worked on by the BE staff though as there's kinks that need to be worked out still.

Did it not once occur to you to actually click on the "add new pack" icon? Really? Not even once?

First of all: java -jar TechnicLauncher.jar should be the correct command. Second: Where exactly are you trying to cd to? If you downloaded it through a browser it should be cd /home/<YourUserName>/Downloads Tbh, it seems to me like you're trying to run this command cd java -jar technin-launcher-latest.jar Which is wrong. You don't cd to java to run an application. The "cd" command stands for change directory. For the sake of eliminating the case of you missing java, since your explanation is pretty vague try running this sudo apt-get install openjdk-7-jdk Here's a quick tutorial: After you get Tekkit running, close out of it. Download LWJGL from http://www.lwjgl.org/ Open Nautilus (or Thunar, whatever xubuntu uses) and navigate to where you installed technic. This is usually at /home/<YourUserName>/.technic If you can't view that directory, click on "view" at the top bar and click on "show hidden files and folders" Enter the .technic/tekkit/bin/ directory. Replace jinput.jar, lwjgl.jar and lwjgl_util.jar with the ones from the archive you downloaded. Replace all the natives. Congratz, no more sticky keys and weird mouse issues.

As this has been the source of confusion for quite a few people, I thought I would write a quick guide to explain how to use Solder. Most of this information can be found in the original Solder API thread but I thought I would simplify it EVEN further and put it all together for easy access. This guide assumes the following: You have already installed Solder and it's fully functional. You have FTP/FTPS/SFTP or Terminal access to the public and application/config directories of the solder installation. You know how to use an archiver (such as winrar/7zip/etc) Your Solder installation is located in /var/www/solder/ Your IQ is at least 90. I can't dumb this down any more than I already have bellow. For the purpose of this guide, I am going to use the following as examples. modpack.jar coremodexample.jar modexample.jar Your modpack is called ExampleCraft You solder installation URL is solder.example.com Step one: Repo setup. Inside the /var/www/solder/public/ directory, create a new directory called repo. Go to the /var/www/solder/application/config/ directory and open the solder.php file with some sort of text editor. Locate this line: 'repo_location' => '', Change it to: 'repo_location' => '/var/www/solder/public/repo/', Locate this line: 'mirror_url' => '', Change it to: 'mirror_url' => 'http://solder.example.com/repo/', Save and reupload to /var/www/solder/application/config/ Go back to the /var/www/solder/public/repo/ directory. Create a new directory named mods and enter that. Step two: Properly packaging the mods for Solder and uploading. On your computer, go to the directory where your modpack.jar, coremodexample.jar and modexample.jar are located. Create a modexample directory. Within that directory, create a mods directory and inside of that mods directory drop your modexample.jar. If you have altered the config file that came along with modexample.jar you will need to create a config directory within the modexample one and drop your config file in the config directory. With your archiver program, compress both the mods and config directories to one zip file named modexample-1.0.0.zip . The numbers in this are the version of the mod. You should enter the correct version of the mod you are using. Upload the modexample directory to /var/www/solder/repo/mods/ Do the same for coremodexample.jar and modpack.jar. Instead of a mods folder, you need to create a coremods folder for coremodexample.jar and a bin folder for modpack.jar Every mod you will add to solder will need to have the above done to it. Every mod-x.x.x.zip will need to be in it's own directory named after it. Step three: Getting solder to recognize your mods and adding them to a modpack. Go to solder.example.com and log in. Click on Mod Library at the top. Click on Add a Mod at the left. Go through the process of adding all the information for the mod you wish to add. In the Mod Slug input, you should put the same name as the director that contains your mod. If you're adding BuildCraft and your directory is called buildcraft, that's what you will need to enter. If it's called something else, it will have to be that something else. Finally, click on Add Mod at the bottom. Go to the Mod List. Locate the mod you wish to add a version to and click on Manage to the right. It will take you to an editor page. Click on Mod Versions to the left. You will need to enter ONLY the version. If the mod zip you've uploaded is called modexample-1.1.1.zip you will have to ONLY enter the 1.1.1 part. Click on add version. Now that your mod is recognized by the system, you will have to add it to your modpack. If you don't have a modpack already created, now's the time to do so. To Solder instuctions for that are very clear so I won't bother explaining how. Create a build for your modpack. Refresh the page and click on the Manage button to the right. There will be a pretty dropdown list. Click it, select your mod and on the list to the right, select the version. Click on add mod and refresh the page. And that's it. You've added your very first mod to your modpack. You will need to do this for all mods, coremods and for your modpack.jar And that's basically it.

The harder you try.....

Did you manage to fix this issue yet?

For modpack.jar > Create a bin directory. > Move modpack.jar into that directory. > Archive the directory as modslug-x.x.x.zip . > In the repository, create a directory with the same modslug. > Upload the zip inside that directory. > In solder, add it as you would add any other mod. > Add the proper version. > ???? >Profit! In case you didn't at all know how to add mods to your modpack with solder, this is how you add them. For items that go into the bin folder, you make a bin directory. For mods, a mods directory. For coremods, a coremods directory. If you're a linux user that wants to deliver 2.6 to fix the sticky keys, deliver 2.9 instead. Works fine on linux, windows and afaik, mac. But no you can't have OS specific mods.

As much as I agree with modpacks having permissions for all the mods they contain, approving or disaproving with a person's activity within the MCF community as a basis is quite irrational. As Melfice said, what about people outside the MCF community? What if someone is active AF within the PMC community for example? Of any other Minecraft resource related communities? What if someone has 600 MCF posts and 90% of them are talking about their love for walnut pie? And someone else has 10 total posts and all 10 of them are constructive and well meant critisism towards a mod? What then?

From the AM page Ars Magica is not allowed in modpacks by default. There are a couple special cases: The DireWolf20 pack One other one soon Could this be it? o:

MUST....CRACK...POTENTIAL...CODEY-CODE

Ah okay that makes sense. I feel so stupid now. Thanks for the response mate.

Hello. Ever since a week or maybe 2 ago, every time I click on the "create modpack" link, I'm presented with error 500. I'm not here to bitch about it, as I know technic gets some insane traffic. I'm merely here to confirm that it's not only happening to me, as I've seen no other thread about it.

Have you tried one of the bigger community-made modpacks? Business Elite for example? Does the issue also persist with those?

I'm getting null in the url as well when I click his link. Despite that, the modpack can be added to the launcher. When attempting to download, it tries 3 times to download test-mod-0.1.zip and all 3 times the md5s are miscalculated.

Does it happen with every modpack or just that one? If you haven't tried others, try a different one. If a different modpack works, it's an issue with the pack you're downloading.

Good job with the guide mate. About winrar, it's not free. You are required to pay for it, despite being able to continue using it post expiration.

First of all, this belongs to Platform Pagoda. Second, follow the guide in this thread and see if it works for you afterwards. http://forums.technicpack.net/threads/luke%E2%80%99s-hopefully-comprehensive-modpack-making-guide.44197/

If you look into the stickied "Solder API" thread you will see a link in the OP including my tutorial on how to set solder up. Hosting on a free host on the other hand, you're not gonna have much luck with that. Even the ones with cPanel that provide you with a terminal do not allow php commands, nor do they allow you to install Solder's dependencies. I also doubt you're gonna have much luck with their support. There soon will be. In the meantime, stick to something like dropbox and host a zip instead if you don't want to pay for a VPS.

Oh my, someone actually mentioned Chromium. +1 golden star for you.

How exactly are you trying to run the modpack? And what issue exactly are you having with running it? Be descriptive. Last I checked, we didn't have mind-readers prancing about the forum.

People still use IE? Wat.

Re-reading your original question I see I misunderstood it so my reply to that is mostly irrelevant. Sorry for that. I'm not sure if what you're asking is doable. You can bind a subdomain to that folder if you do what I said above. But about putting the files from the public folder elsewhere, I don't know how Solder itself is set up to read files. I guess you could pull something like that off with symlinks if your server allows that although I'm not sure how exactly you'd go about it. For all I know I'm wrong so take this with quite a bit of salt. More info on symlinks: http://www.cyberciti.biz/faq/unix-creating-symbolic-link-ln-command/ Maybe someone smarter than me can provide a bit more.