Nox13last

According to this logfile, there is a problem with CodeChickenCore (Explained at Line 50). Make sure your stuff is updated. Seeing as it's a Tekkit release, I suggest you go into your Technic Launcher folder (in %AppData%), find the folder to which Tekkit corresponds, and then delete it. Then try downloading it again. If it has a \Saves\ folder in it, you may want to back it up. Also make sure that the Launcher is at the latest version (293, the last time I checked). If it's not, delete that and redownload it.

I disagree, I'm afraid. I figured out kind of towards the beginning of the process that it does not work. I acquired Forge from http://files.minecraftforge.net/minecraftforge/minecraftforge-universal-1.6.2-9.10.1.871.jar (this link was provided by Firefox's download history. And I can certainly see that it says "1.6.2" in it). The only three folders in it are bin (which is provided with only the Forge modpack.jar), a mods folder (containing 68 objects), and config folder (containing more stuff). Yet, when it downloads, the bin is empty, and Technic Launcher's console cannot find the existence of a Forge installation, regardless of whether or not I add it post-download. When your modpack downloads, does it have all of the bin gubbins in it?

Me and the OP have been exchanging Private (and Public) Messages about this. I can confirm that this is an issue that exists. 1.6.4 doesn't provide any useful benefits over 1.6.2 (except for fixing a Handshake exploit, and an AFK-kicker), and few mods support 1.6.4. If you're going to claim that your launcher is 1.6-compatible, please make sure that it is actually compatible with all versions of 1.6. And then instruct people on how to do it. Dammit, guys, you did this with Solder way back: "Here, this is a thing that we put in. Not that we're going to tell you how to use it, or anything." Just on a whim, I looked at the Vanilla installation of Technic Platform, and it is ready for 1.6.4. So, I downloaded it for 1.6.2 (because 1.6.4 doesn't even add anything pertinent, and fewer mods support 1.6.4 than 1.6.2). It downloaded a Minecraft.jar as well as LWGJL files. Correct me if I'm wrong, but these things are absent from a Minecraft Launcher installation.

Ok, to Hell with the edit. I PM'd you with what happened, but I will write here about what happened for others to refer to. The \asset\ folder was not included like I had intended it to. Neither was the \libraries\ folder. The \mods\ folder is downloaded, complete with mods. Just on a whim, I looked at Vanilla, and it is ready for 1.6.4. So, I downloaded it for 1.6.2 (because 1.6.4 doesn't even add anything pertinent, and fewer mods support 1.6.4 than 1.6.2). It downloaded a Minecraft.jar as well as LWGJL files. Correct me if I'm wrong, but these things are absent from a Minecraft Launcher installation. So what fresh hell is going on?

Thank you. Nice to know, at least for now, that this problem isn't being caused by me being unwitting in the new system. Just for the sake of test, I'm adding the \assets\ folder to the zip. Obviously, in this form, the pack will be undistributable, but it may provide additional information. Waiting for Dropbox to finish syncing, so I'll edit this post with the verdict.

Replied. (This post will be edited in a sec to reflect my responses.) No. The modpack.jar does not come through as reflected in the Dropbox package. The Dropbox package specifies [modpack]binmodpack.jar. The downloaded package contains the bin folder, but does not put anything into it. I also added the libraries folder, just for a test, and that was not downloaded either. It also insists on adding a coremods folder and a cache folder, despite them not being necessary (apparently). I don't want to add the assets folder, because that would violate Mojang's TOS (as it is essentially the minecraft.jar). I'm getting the feeling that its assuming, in spite of specification, that this is a pre-1.6 set-up, when I have clearly specified that it is 1.6.2. It is saddling up to play in 1.5.2, looks for a Minecraft.jar (which does not exist anymore), can't find it, and then gives up.

This is a closed modpack, so I'm going to have to redact some of the information I show. It says the following when I select the pack: InstalledPack{info=PlatformPackInfo{name='[Modpack]', displayName='[Modpack]', url='https://dl.dropboxusercontent.com/u/54014114/[Modpack].zip', icon=null, logo=net.technicpack.launchercore.restful.Resource@18879c56, background=net.technicpack.launchercore.restful.Resource@6f28deae, minecraft='1.6.2', forge='null', version='1.0', solder='', forceDir=false}, name='[Modpack]', platform=true, build='recommended', directory='launcher[Modpack]'} When I download it: Valid: Starting download of https://dl.dropboxusercontent.com/u/54014114/[Modpack].zip, with 3 tries remaining And that's it. If I tell it to Launch after having done this, it starts the process anew. This is the stuff that happens to the progress bar beneath the news feed: __% [modpack]-1.0.zip (Runs until completion, go to step 2) (Unpacking various assets, such as Millénaire and mATMOS) (Progress bar vanishes.) It's not even explaining that something is wrong. It just says "Downloading. Unpacking. Welp, my work here is done... Zzzz.".

I tried yesterday, when the Launcher was 285 (or something). It failed back then, too, but it was midnight and I thought I'd wake up with fresh ideas. I notice that the news only says "1.6+ compatible", but there are no cromulent explanations on how to make a 1.6 modpack. Even the ones already in the Technic network are "Manual Installation". Plus, one of the commenters submitted a picture of themselves strangling a cat, and I lost interest in the lack of moderation that goes on in Technic's correspondence.

Doesn't work for me, unfortunately. It downloads the modpack-1.0.zip (not named that, obviously). It downloads it, decompresses stuff, then the progress bar disappears. The Technic Launcher Console reports that the forge for this installation is 'null'. And I've followed instructions such as "get Forge Universal, rename to modpack.jar', then stuff it into modpack.zipbin" and "get the .json from inside Forge Universal, rename to 'version.json', and stuff it into modpack.zipbin". It doesn't want to load for reasons, and the console will not tell me what happens immediately after the stuff is decompressed. It just...stops. I have a 1.6.2 installation that people are waiting for, and it won't even boot. But it will gleefully do using the Minecraft Launcher. Oh, and in spite of my best attempts to instruct it otherwise, it insists on downloading everything to .techniclaunchermodpacks[modpack]. I want it to go to .techniclauncher[modpack] (legacy behaviour). I'm using Launcher Build 290.