Valkon

127.0.0.1

It does. But that's a different launcher.

Step 1: Copy and paste the URL from the pack's page on the Platform into the launcher Step 2: There is no step 2

The tip was for if you needed more blutricity, not EU. But as for camouflaging, a solar panel with 2 slabs above it still functions.

Too bad they missed an obvious April Fools "joke". They could have said they finished the Modding API.

I believe you missed the point completely.

¡

By the way, a tip in case you need more blutricity in the future. If you put a RedPower solar panel on top of an IndustrialCraft solar panel, both will still function, since the RP solars aren't full blocks, so they don't block light.

A special version of the Kinect sensor, specifically designed for Tekkit, will be available, of course. As a bonus feature, you can even activate GregTech Mode on it. Doing so will cause a telescopic robot arm to come out of a hidden hatch on the sensor, pick up the nearest blunt object, and break your hands and wrists before playing.

Decided to try something a little different. Foreground (Beast + grassy hill) done in Photoshop, background (everything else) in Illustrator. Based on the Amiga game Shadow of the Beast. Also, I've realized I'm not as good with Illustrator as I am with Photoshop.

Looks like you switched to Creative mode. I suggest putting NEI back in, reactivating cheat mode, and pressing the "C" button at the top left until you are back to survival (pressing the C button alternates between Survival, Creative, and an alternate Creative). Also, in the future, don't sign your posts.

Yeah, you need three tickets. One for each mission.

I've been looking to do the Mecha Engine tour. Why not. Steam name is Valkon [since there are multiple Valkons, note that my profile picture is of a man punching through a monitor]. My main classes are Soldier, Engineer, Demoman, and Medic, secondary being Scout and Heavy. Basically any class other than Sniper, Spy, and Pyro works for me.

Not who, what. Who uses it.

My God... stealing the oxygne? How could they?!? Well, actually, Tekkit Lite is fo- Well, no, Lite actually refers to the lack of Bukkit, the pack itself has more mods than Cla- I... what? What if the mods now are better than the mods for Minecraft 5? Is this before, during, or after the monopoly game?

I apologize for the infestation of bullfish. I will be sure to tell the higher-ups to hire a professional hunter-diver to take care of them and repair the cable segments they were biting.

Another avatar picture. I decided to remake the one I made for Jorcer. Behold the Viking Hacker in his natural habitat, a subway bench.

I tried to stay in the spirit of your current/original avatar, what with the severely bent arms and unfortunate exotropia.

The magic effect didn't turn out quite how I wanted but eh.

Ah, but one would not want to install ducks into their modpack. After all, the cursed waterfowl is known to be the primary source of computer issues when using the Technic launcher.

I'll just go ahead and pull some quotes from it.

Sort of. The thing I posted was hardly an actual tutorial.

I have nothing else to do right now. So yeah sure why not.

That is not entirely true, as you are about to witness. Perhaps I can help. :cracks knuckles: I'll be "re-explaining" Jay?'s tutorial in a more clear fashion. What this means is to allocate a place in your computer to put together ("pack", if you will) your modpack. Now, allocation can be defined as the distribution of resources for a particular purpose. Therefore, what this step indicates is that you must create a fresh (meaning "empty") folder in your computer's harddrive where you will place all the mods to go. Make sure there are not additional files, for they may corrupt your pack's installation and that would be a very, very distressing outcome to your hard work. This may be one of the more confusing steps. In this section we will be going to the mod author's webpage in which they have listed the mod and it's description. These pages, normally hosted on a website known as the "Minecraft Forums", generally contain instructions for the installation of your mod. Now, this may confuse some people who are newer to installation of software, but you must make sure to follow the installation process and not the uninstallation process, otherwise you would create a catastrophic error and you may be left severely confused, for the instructions will instruct you to perform actions that cannot be performed without the prerequisite steps the installation instructions you hypothetically failed to find would have provided. This is a further explanation of the previous step. In the previous step, we discussed the installation of mods, which the author of said mods usually provides instructions for the aforementioned installation process. Now, in the last step the "Core Mods" folder was also briefly mentioned, though the juxtapositioning of that portion may have provided confusion without the context of this current step, so I decided it would be better to discuss this here. During the installation process, you may see the terms "/mods folder", "/coremods folder", and "/config folder" mentioned. These may confuse those newer to installation of mods, so I figure I should take my time explaining this. The terms in question refer to the respective folders that you must create within an empty folder- you may now remember that in the very first step of this process we allocated space for the pack. This is where that step becomes important, for this allocated space is where these folders will be made and then subsequently filled with the mods you have downloaded and wish to install into your pack. Be sure not to install anything mentioning "minecraft.jar" just yet, we will be discussing that in the next step of the tutorial. But I digress; on with the current step. When you have created these "mods", "coremods", and "config" folders in your allocated space, you must place the mods where the instructions provided by the mod author indicate. Be sure to put the right mods into the right folder, or the final installation of your pack will, regretfully, not function. Since this is a rather important and complicated step, it is going to be split into three sections - that is to say, we will be taking the steps one at a time, explaining each in full detail to make certain that the instructions are followed correctly and there is no chance of error within our installation. Now, on with the installation instructions. In the procedures you will undertake whilst following the instructions provided by the mod author on their Minecraft Forum mod post, you will find that there are select few mods that cannot be installed in the mods or coremods folder. Such mods include important "mod-loading" mods such as the popular "Minecraft Forge" - be sure to install this, or else your modpack will not be able to function, for it is what allows the mods in the mods and coremods folders to be loaded into Minecraft in the first place. For now, this tutorial will assume that you already have identified which mods must be installed into the minecraft.jar file. Now, you must "unarchive" the files which you downloaded. In the folders created by the "unarchiving" process, there will be several files called "Java Class Files". In the spirit of this tutorial, I would normally explain what these are and how they work, but as I am limited on time I will be forced not to. What a shame this is. Continuing on with the current step, you must collect all of these "Java Class Files" into a singular location, preferably separate from the other mods and mod folders in order to prevent mixing of unnecessary files into the file we will be creating in the next step. While this step may indeed be "simple" for a seasoned mod installating veteran, a new user will most likely be confused by such terminology. Then again, that is the sole purpose of this tutorial - to explain as clearly as possible the steps which you must take in order to install mods and create your very own modpack. Once you have finished the previous step (be sure you have not skipped any steps, as that would be a true shame and may induce unwanted results when you attempt to install the pack), you must select all of the "Java Class Files" (remember, these are the same ones previously mentioned in the last step). To do so, you have a few options. For instance, you can "Drag select" multiple files by holding down the mouse button and dragging it over all the files (be sure not to select a file when performing the initial click, or you may accidentally move the file into a place in which it does not belong). You could also click on the first file in the list and then hold down the "Shift" key, located to the left of the Z key or to the right of the / key on your keyboard, and select the files individually, if you so wished. However, be sure that you do not miss a file whilst doing so, or your install will fail to run and you will have to repeat the tutorial. Once you have selected all the files (be sure that it is indeed all the files and not some of the files) you can "Right-Click" (the right-click button is located to the right of the button usually used on your computer's mouse) on any of the files you wish. Then, select the compression software of your choice to add the files to an archive (this tutorial, for the sake of brevity, will assume that you already have experience with the use of archiving software and therefore also have archiving software installed). Now, we are going to deviate slightly from the normal installation tutorials provided by the creators of mods - we will be archiving these files as "Modpack.jar" instead of "Minecraft.jar", as this file will not contain the main installation of the game itself- distributing that would be piracy, a terrible, horrible, evil, vile, disgusting, putrid act that clearly only the most terrible, horrible, evil, vile, disgusting, putrid people would ever have reason to perform. But once again, I digress. Whilst saving the archive as Modpack.jar, be sure that its file format is a ".zip" file, or otherwise the file will fail to function once you have installed it into your copy of Minecraft. The first portion of this step was accidentally explained in the previous step, so if you are confused please refer to it if you are confused by any of the following. When you have your Modpack.jar file (remember, Modpack, not Minecraft- naming it Minecraft will overwrite your game install and cause Minecraft to crash upon loading your pack, wasting your time, which I know is valuable and would never wish to be spent on irrelevant or redundant explanations or actions. That is, of course why I am making this tutorial - to explain to the "layman", as some would say, the actions necessary for the installation of packs as quickly and easily as possible), place it into a folder that will be created alongside the mod, coremod, and config folders. This folder will be called the "bin" folder, as that corresponds to the location in which the Minecraft game files are located in the default installation of Minecraft. Once you have completed this step, along with all the previous steps of this tutorial, you will have completed the assembly portion of tutorial. We will now move on to the final step, which will once again utilize archiving software. As mentioned before, this step will require the use of archiving software. You may apply the same method of multi-file selection as described in the step prior to the previous (if the preceding sentence confused you, it merely indicates two steps prior to the current). Once you have successfully "packed" your mods together as a .zip file, be sure to name it what you wish your pack to be called. It is critical that you do this, or you may lose it if you were to place it in a folder that might contain other .zip files, let alone files of another type. Also be sure that its name is exceptionally clear, or confusion may lead you to upload another file by mistake, which in a worst case scenario may cause embarrassment, rejection from society, imprisonment, and, worst of all, your modpack not functioning in the launcher. Once you have completed this step (that is, the portion of this step in which you create and name your modpack's .zip file), you can upload it a file hosting service, one of the most popular of which being known as the "Drop Box" hosting service. Be sure that it is a service in which a direct link will lead to a download, not one in which you must click, or else the file will fail to download correctly into your launcher and, therefore, the pack will as well. Once you have the link to this download, you can share it via the Technic Platform, located at Technicpack.net, as either a public pack, in which hundreds of thousands of people (for relativity sake, that is more than you can count with standard human limbs) can download and enjoy your pack, which I am sure will be perfect and wonderful and everyone will love, or you could keep it as a private pack, only providing it to those whom you choose, giving you the power to select who gets to enjoy your modpack (assuming, of course, that none of the people you share it with share it with other people whom you do not desire to share it with, but I doubt that would happen as that is indecent and rude). The choice is up to you. This isn't a step in the tutorial, this is simply Jay? being sarcastic and fooling around as usual. When will she learn? Quite clearly not right now, for she has done it yet again! I laugh when I think about the way people often react to her method of assistance, as - despite it's wondrous sense of humor and excellent use of language - people seem to dislike it. Perhaps it is destined to always be this way, though maybe this is not a fate too unfortunate. We moderators share quite a few chuckles at the unnecessary hate we occasionally get, for we have hardy mental constitutions and do not fall to our knees in the face of internet children, no matter how insulting, how common, how unintelligent they can become. But I digress, as this is personal opinion and is not necessary as to the installation of the modpack you will surely create with absolutely no trouble now that you have fully read the tutorial which I have created solely for you, my good friend. With that, the tutorial comes to an end. I bid you a good day, and I hope that we shall speak again - on equal terms, though, not as mentor to student. I look forward to it. -ValkonX11

Not usually, no. PIracy is, though.