All packs now caught up. Lets hope that never happens again.
Status updates for private mod pack owners
- Thread starter Watchful11
- Start date
- Status
We are looking in to a sync issue where the normally reliable curseCDN is not picking up the new versions of packs. Hopefully should be fixed sometime today.
For now you can just switch to a server other than that one in the advanced options menu.
For now you can just switch to a server other than that one in the advanced options menu.
HQM has changed their permission policy back to notify. If you're pack contains the mod, you'll need to notify them via a private message or comment on curseforge before your next update.
Just a note for anyone who happens to read this. CoFH lib just consists of some library files, it's not even a mod. The classes are packaged inside CoFH core. You don't need it in your modpack. Try it, take the thing out and see what happens.
Another technical note that doesn't affect many people.
Java code is normally distributed in jar files(or zips, there's no difference). However, it is typical when developing code to just run the .class files. By extension, it's possible to take a jar, unzip it to get the class files, and run those. This can technically be done with mods. MultiMC, and I assume the vanilla launcher, supports this. The FTB launcher, for a number of reasons, does not. In most cases, if you run into this, it's possible to just zip up the CONTENTS of the folder of class files(not the folder itself), and put that in the mods folder instead of the folder.
There are one or two mods that break when this happens and want you to extract anyway. Go bug the mod author about it.
Java code is normally distributed in jar files(or zips, there's no difference). However, it is typical when developing code to just run the .class files. By extension, it's possible to take a jar, unzip it to get the class files, and run those. This can technically be done with mods. MultiMC, and I assume the vanilla launcher, supports this. The FTB launcher, for a number of reasons, does not. In most cases, if you run into this, it's possible to just zip up the CONTENTS of the folder of class files(not the folder itself), and put that in the mods folder instead of the folder.
There are one or two mods that break when this happens and want you to extract anyway. Go bug the mod author about it.
Everyone please welcome @karmarcharger, @Wavebrother, @Strikingwolf, @jordsta95 and @Baphometis to the team!
Please also excuse any small mistakes as they get up to speed.
Please also excuse any small mistakes as they get up to speed.
We're currently experiencing some problems with the repo. Updates will be processed, but won't be available on the launcher until the repo gets sorted.
No ETA, but I'm hopeful for a few hours.
No ETA, but I'm hopeful for a few hours.
Lots of changes to the guidelines. See them here and here.
Most notable is that fastcraft has opened up it's permissions. However, you must include a comment in your description that follows the license. I suggest the following.
We have also decided to enforce notification permission for fastcraft. While not strictly required by his license, it will help us know when to verify descriptions.
Most notable is that fastcraft has opened up it's permissions. However, you must include a comment in your description that follows the license. I suggest the following.
Code:
This pack contains <a color="aqua" href="http://forum.industrial-craft.net/index.php?page=Thread&threadID=10820">Fastcraft</a>, by Player, enabled by default. Fastcraft enhances Minecraft with increased performance. Bug reports being made directly to Mod Authors should state Fastcraft is enabled.We have also decided to enforce notification permission for fastcraft. While not strictly required by his license, it will help us know when to verify descriptions.
AtomicStryker has opened up his permission policy for modpacks. You no longer have to request permission for public packs.
3rd party team applications are open again.
Our main upload repo is down again. Uploads will still be processed, but they won't go live until approximately 11 PM EST time tonight.
We're doing some maintenance that's taking longer than expected. Packs may not sync out to the launcher for the next 8 hours.
There is a known launcher bug with the experimental branch of forge. Forge versions 1389, 1391, 1393, 1394 and 1395 will not launch.
Error code similar to this "Error while gathering assets: java.lang.NumberFormatException: For input string: "1395-1710ls""
We're working on a fix and are hopeful to have it out tomorrow evening(Monday evening est time). For now people will have to downgrade forge or wait until the fix comes out.
Error code similar to this "Error while gathering assets: java.lang.NumberFormatException: For input string: "1395-1710ls""
We're working on a fix and are hopeful to have it out tomorrow evening(Monday evening est time). For now people will have to downgrade forge or wait until the fix comes out.
Last edited:
The new launcher build is live and and the bug is fixed. Experimental branch of forge is now supported.
We have moved from from the spreadsheet to a brand new website. More details here.
After a few months of work, curse syncing for third party packs is finally here. This will let you maintain a pack through the normal FTB third party system and have it automagically appear on the curse client.
Here are the steps to opt in to this. Create a curse modpack project using this form. You will need to fill in all the fields, including uploading a square image at least 400x400 pixels. Find the curse project ID in the url. It is just the number part, for example 231835 is the ID for "http://minecraft.curseforge.com/modpacks/231835-the-hubris-of-magic". Reply to your modpack thread saying your want to opt in to the curse syncing system and give the project ID. You need to either be updating your pack at the same time or have updated your pack in the last two weeks. We will respond when the ID has been added to our system. It may take up to a few hours for your pack to convert the first time, especially if you have a lot of old versions. Future updates should only take 15-20 minutes.
What will be synced:
What will not be synced:
If you already have your modpack on the client, you can still use the existing project ID and new versions will simply be added(EDIT: Realized I had that wrong. Old versions on curse will be overwritten by the old versions on FTB. So if you're depending on different versions, this system is not for you). Versions added on the curse side will not sync back to the FTB side.
You must have a public modpack, listed or unlisted, to be eligible. Private modpacks are not currently allowed. In standing with our no profit policy, you may not turn on curse reward points for your project if it goes through this system.
Since this system goes through the normal FTB permission checks, it bypasses the curse permission checks, allowing you to use any mods you can get permission for.
I'm intentionally only posting to this thread for now. I want to test it out for a few days with only the packs from the relatively limited number of people who read this before slamming the system with dozens of packs.
Edit: Since this thread isn't open, feel free to PM me with any questions
Here are the steps to opt in to this. Create a curse modpack project using this form. You will need to fill in all the fields, including uploading a square image at least 400x400 pixels. Find the curse project ID in the url. It is just the number part, for example 231835 is the ID for "http://minecraft.curseforge.com/modpacks/231835-the-hubris-of-magic". Reply to your modpack thread saying your want to opt in to the curse syncing system and give the project ID. You need to either be updating your pack at the same time or have updated your pack in the last two weeks. We will respond when the ID has been added to our system. It may take up to a few hours for your pack to convert the first time, especially if you have a lot of old versions. Future updates should only take 15-20 minutes.
What will be synced:
- All existing modpack versions
- All future modpack versions
- The current recommended version on the launcher will be marked recommended on the client
What will not be synced:
- Images
- Author
- Description
- Mod list in the description (unsupported by curse)
- Server files (unsupported by curse)
If you already have your modpack on the client, you can still use the existing project ID and new versions will simply be added(EDIT: Realized I had that wrong. Old versions on curse will be overwritten by the old versions on FTB. So if you're depending on different versions, this system is not for you). Versions added on the curse side will not sync back to the FTB side.
You must have a public modpack, listed or unlisted, to be eligible. Private modpacks are not currently allowed. In standing with our no profit policy, you may not turn on curse reward points for your project if it goes through this system.
Since this system goes through the normal FTB permission checks, it bypasses the curse permission checks, allowing you to use any mods you can get permission for.
I'm intentionally only posting to this thread for now. I want to test it out for a few days with only the packs from the relatively limited number of people who read this before slamming the system with dozens of packs.
Edit: Since this thread isn't open, feel free to PM me with any questions
Last edited:
- Status