Jump to content

Recommended Posts

Posted

https://www.dropbox.com/s/a89zdydqu9ncu0y/Enigmatic%20Expanse.zip

That's the dropbox link that I used to input into the box that asks for the Platform URL. After copying the resulting URL:

http://www.technicpack.net/api/modpack/enigmatic-expanse-pack

and pasting it in the Technic Launcher in the box that asks for the Platform URL, the launcher recognizes the pack and even briefly displays the name, but lo' and behold, Vanilla Minecraft is on instead of the mod pack. Anyone know how to fix this?

Posted

I'm having the same problem, and I'm so glad that I'm seeing I'm not the only one.

Trust me, as I just recently posted in a different thread, I followed every single step and still got Vanilla. I even tried so many different things to see if I was just missing something, still Vanilla.

I hope someone knows the answer to this problem.

Posted

Alright, I'm back after looking through more Threads. It looks like the Vanilla issue is quite common, but has seemingly been resolved.

This is the Thread that seems to be most help right now - http://forums.technicpack.net/threads/compiling-a-modpack.40032/

I read through a bunch of comments and such and it looks like one of the most common problems is the modpack.jar having been named incorrectly. For example, it needs to be named modpack.jar and not modpack.jar.zip

Now, I already was making sure that it was named modpack.jar, but according to said Thread, it can still have that extra .zip extension without you actually seeing it.

So in order to fix that, we are supposed to change the computer settings to allow us to see that extra extension and rename it properly.

It seems like maybe this might work.

I think I'll go give it a shot. If it works for me, I'll post here. If not... I'll post here lol

Posted

Nope, no luck. I went into "Folder and Search Options" clicked on the 'View' tab and unchecked "Hide extensions for known file types". After that, I looked at my modpack file and it was modpack.jar

Seems like my problem was not the extension.

God I seriously hate feeling like I am incapable of grasping something as mundane as this.

Back to reading and troubleshooting.. -_-

  • 2 months later...
  • Moderators
Posted

having the same problem, most hatefull thing is that even if its a commen problem non of the technic staff seems to boder with any of this problem -_-''

Spreading these kinds of comments is not what OP needs.

If you think you can help, then help. Show us your talent, keyboard warrior!

Posted

most hatefull thing is that even if its a commen problem non of the technic staff seems to boder with any of this problem -_-''

Why is it the Technic teams fault? Did they hack his computer and jokingly changed something to make it load vanilla? Its a PICNIC.

Also, bad necro. Look at the date of the last post.

If anyone else is having issues, THIS is stickied for a reason.

Posted

Why is it the Technic teams fault? Did they hack his computer and jokingly changed something to make it load vanilla? Its a PICNIC.

Also, bad necro. Look at the date of the last post.

If anyone else is having issues, THIS is stickied for a reason.

Because it's there system who doesnt read the modpack.jar somehow...

Posted

Because it's there system who doesnt read the modpack.jar somehow...

Really? I never noticed that with the twenty or thirty modpacks I have made. Very few people have had any problems when looking al the guide I linked to in the above post. Maybe I should go look into that. You need to go tell every modpack maker of the thousands of custom packs that technic can't read their jar files and it has just been working by total fluke. You have greatly improved our humble community with this completely unknown knowledge.

:suicide:

Posted

Because it's there system who doesnt read the modpack.jar somehow...

Right, because the possibility of people having problems because they're doing it wrong is completely nil.

Posted

Really? I never noticed that with the twenty or thirty modpacks I have made. Very few people have had any problems when looking al the guide I linked to in the above post. Maybe I should go look into that. You need to go tell every modpack maker of the thousands of custom packs that technic can't read their jar files and it has just been working by total fluke. You have greatly improved our humble community with this completely unknown knowledge.

:suicide:

wauw that was a whole loud of wasted bytes ¬_¬

sure there are a lot of people out there who can run there modpack without any wasted time, but for the guys who come in first (and arent so lucky) get a lot of trouble in the prosess...

anyway to make this post atleast a bit useful and relenevand to this thread,

I compared my Modpack.jar with one of someone els's modpack and it looks like we have look a like folders with the same aab.class, aal.class ,ect files however the maps are differend.

i have the normal forge maps, but the voltz+ modpack got none of those maps in his Modpack.jar, instead he got a ctm map what isnt from forge (could be opifine i dont know for sure).

gone test out of my modpack will work ik i use the same .jar

Posted

You have no idea, do you?

I stuck my head in the modpack story a week ago, give me a break.

I just post what i discorver in the hope it will trigger others to a idea to crack this problem

Posted

Its not a problem with the platform, its a P.I.C.N.I.C. (Problem In Chair, Not In Computer) You clearly have just not learned how to use the platform. Go learn like the thousands of others who have.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...