[Orespawn Crash Error]

It seems to be a known ID declaration issue. try to see if you find a solution here:

 

[When I open my mod pack the vanilla version just opens]

Your modpack link is dead by now, I hope you found a solution

[ModPack Doesnt Load (different modpack)]

I can see this in your pastebin file :

java.lang.RuntimeException: Can't fit all textures, use lower resolution texture packs or remove mods.

Also, I can see that it seems to be a related Fastcraft issue.

[New modpack only launches vanilla]

You link is dead. Hope you found a solution.

[Custom Modpack Crashes]

On 10/28/2019 at 10:35 PM, Chrantix said:

Hi, I've been trying to create custom modpack so a few friends can join the server without manually changing anything after I add more mods or make any changes. 

I added the forge universal jar into a bin folder and renamed it modpack.

I created a mods folder with all the mods I want.

I created a config folder.

Then I zipped them to a dropbox and changed the ?=0 to ?=1 so it becomes a direct download link and uploaded it as a hidden modpack.

However, whenever I click on play the launcher disappears for a second and then reappears.

Attached is the pastebin for my console log. 

https://pastebin.com/0ej5gYB5

Modpack Link: https://www.technicpack.net/modpack/bears-world.1558296

 

Resolved: Rechecked the guide for distributing mods. After adding the config files, the error was fixed.

By the way, your modpack direct link is no longer working and so, we can't download your modpack.

[How to update forge?]

On 12/4/2019 at 8:53 PM, KingLazarusOG said:

I'm trying to do the same thing with a 1.7.10 pack, and when I load in the newly named modpack.jar file, it just crashes as soon as it hits the main menu

 

Do you have any crash report to show us? You can found them into your modpack folder itself inside the technic folder.

[Not launching modpacks]

Is it happening only with one modpack or also with other complete different modpacks? Because for me it seems to be a modpack issue. You can always try to reinstall completely the Launcher.

[Custom Modpack Updates]

If you're pushing correctly any new modpack version after adding the new modpack zip, it's not supposed to cause any problem related to the Launcher. It might be a Launcher issue. It might be a Launcher issue. I don't know more about it.

[My Modpack]

Is it possible to have some links to have a better visualization of your modpack?

[Launching custom modpack in vanilla]

Are you sure your modpack.jar is correct?

[Issue Modpack location Github direct links]

Hello everyone,

I'm encounting an issue with the modpack settings. When I'm trying to enter a direct link in the 'Modpack Location' setting, this one isn't accepted. My link is supposed to be a valid direct link from Github (available here). 

You can see more details in the included image. By the way as you can see, it makes the data from the inputs temporarily disappear.

 

Thank you for your answers !

[I need help with my own Modpack.]

After some tests, it seems that Mystcraft is the problem. Removing it will solve the problem. also, be careful about Optifine. It can be an issue sources sometimes (it's not now, it's just a warning).

 

Cordially.

[Github direct link of releases not valid in Technic?]

hello everyone,

As a modpack owner, I've tried to integrate a github asset link from a release to the modpack direct link option. But it doesn't works. The platform doesn't want to accept my link from an asset linked to the release (except for the "source code" zip link). Has anyone an idea? 

Thank you very much

[I need help with my own Modpack.]

Check your logs in the technic launcher's folder. I think it may be a mod incompatibility, because some of your mods are in Alpha/Beta versions. Like AE2 I think so.