"The status of the file Kevlot (Kevlot 1) has been changed to Rejected Notes: The following files belong to CurseForge-hosted projects, and should therefore not be added directly to zip files: overrides/mods/disenchanter[1.12]1.7.jar overrides/mods/FTBLib-5.4.7.2.jar overrides/mods/FTBUtilities-5.4.1.131.jar These files should, instead, be referenced in the manifest.json file generated by the Twitch Desktop App during a profile export. If you have any questions please contact our support team https://support.curseforge.com."
The issue is that when i go to export, using the export command under the profiles options, It does not give me an option for this said .json file. Could i get a step by step on the location of the file?
I have also contacted the curse forge support and it has been 6 days and still not replay. I set them a follow message but in the meantime is anyone knows the solution i would appreciate it.
i had the same issue with a few texture packs in my pack, i just diabed the exporting of resource packs and it worked but i dont think it will be that simple if you have th eproblem with mods /:
BTW: i have FTB Lib / FTB Utilities inmy pack to and didnt have a problem that was because of it
Yeah, they specifically mentioned that they OWNED those and that i was not allowed to post my modpack with them. I followed what they told me for instructions and it happened again. They aren't helping at this point. I have had a request on the curse support ticket system for almost a month at this point and still not a single reply. No confirmation that they got my message or anything. I do not know what is going on with curse forge but something is not right. They are awful compared to before with their support.
Here is how to fix it you will need to build your modpack from the curse forge launcher, but you can avoid having to redo the whole adding the mods by creating a profile and clicking on view folder. Then drag all you mods into the mods folder. And anything else like config files into the directory that the mods folder is in or the name of your instance folder!
Here is how to fix it you will need to build your modpack from the curse forge launcher, but you can avoid having to redo the whole adding the mods by creating a profile and clicking on view folder. Then drag all you mods into the mods folder. And anything else like config files into the directory that the mods folder is in or the name of your instance folder!
I made the modpack inside the curse forge launcher. I exported using the curse forge launcher. I am having an issue with the moderation of modpacks since they are not explaining clearly what the issue is. This is only happening because they are migrating from the twitch launcher to the curse forge launcher. The mods them selfs listed are the issue. They are saying I am using “their property” by adding and FTC mods. That has not been an issue in the past.
Edit: I should add that this is not my first modpack I have made. I am aware of the process to create edit and export.
I think that this means they are not supporting a mod or it is not on their website still, do you have something or are you using a baseplate of a certain mod I have a feeling that this has something to do with licensing, but i have not seen that error ever before. sorry I meant to send this 30 mins after you posted this message. but I forgot to hit post.
sorry I meant to send this 30 mins after you posted this message. but I forgot to hit post.
Thats fine.
Everything was downloaded throught the curse forge launcher, powered by overwolf not twitch nor the website. The mod/s in question are the FTBUtilities and the FTBLibrary. I highly doubt they are no longer supporting the mod that they helped create if the modpacks they made are still up on their site as well.
EDIT: They specifically said it was the FTB mods and that I did not export them correct. The steps they then gave me were not applicable to the "New" Overworlf powered launcher app.
That’s the thing. I have made modpacks in the past with these said modes and they have been published. The modpack/s, “Down to Roots” had FTB utilities and more that I have made. I exported the modpack the same way I always have. Thank you for supporting this thread. I hope they really fix this issue.
If you were around before twitch acquired curese, curse was much better with the community. Support got handled. Once twitch got hold of them the made it so when you wanted to make a modpack you had to use their twitch launcher mod tab witch only loaded about 1/4 of the time and if u had an issue it rarely got resolved. That said. With twitch acquiring curse, it’s not a bad thing. There was a lot of good that came from wit. It’s just that thy do not hold the same level of standards for the community as before.
My favorite part about this issue I have with the support team right now is that I was sent to file a support ticket and the actually straight up canceled it after me going again and again sending a new message every view days waiting as to not let it time out and void. In a whole month I received not a single message from anyone’s. Only a bit telling me their would be someone that will get to you within 2-3 business days. 😐it’s was a month later and still no person after being told it would be a few days... I stoped replying. Got tired of waiting and they completely voided the support ticket. Not a fan of the new system. That said that was also while it was in beta. I will try again in a few weeks to get this modpack published as I like to be able to play games I enjoy they way I would like to.
ive been making modpacks since 2014. If you weren’t back then prior to twitch acquiring curse, you don’t really have much wiggle room there. If you were playing modpacks around there I fully understand. I’d agree on that end. The twitch launcher is much easier to use than having to create a new folder version of Minecraft with adding a pack of mods into in order to play.
Did you ever figure out the cause of this? I know that this reply is almost a year late, but I found this thread by searching for a similar issue. I had two different versions of the mods listed with this status. I believe that submitting now that I've deleted them will fix the issue. Maybe somebody else sees this that needs it, who knows..
To fix this you need to just go into the curse forge app and then add content to the modpack and select these to mods and install them in that way. This will add them to the manifest file instead as a override.
The issue is that when i go to export, using the export command under the profiles options, It does not give me an option for this said .json file. Could i get a step by step on the location of the file?
I have also contacted the curse forge support and it has been 6 days and still not replay. I set them a follow message but in the meantime is anyone knows the solution i would appreciate it.
i had the same issue with a few texture packs in my pack, i just diabed the exporting of resource packs and it worked but i dont think it will be that simple if you have th eproblem with mods /:
BTW: i have FTB Lib / FTB Utilities inmy pack to and didnt have a problem that was because of it
In reply to ultrax96:
Yeah, they specifically mentioned that they OWNED those and that i was not allowed to post my modpack with them. I followed what they told me for instructions and it happened again. They aren't helping at this point. I have had a request on the curse support ticket system for almost a month at this point and still not a single reply. No confirmation that they got my message or anything. I do not know what is going on with curse forge but something is not right. They are awful compared to before with their support.
yepp Twitch was Better
In reply to ultrax96:
Trust me, it was better before twitch purchased curseforge.
Here is how to fix it you will need to build your modpack from the curse forge launcher, but you can avoid having to redo the whole adding the mods by creating a profile and clicking on view folder. Then drag all you mods into the mods folder. And anything else like config files into the directory that the mods folder is in or the name of your instance folder!
I made the modpack inside the curse forge launcher. I exported using the curse forge launcher. I am having an issue with the moderation of modpacks since they are not explaining clearly what the issue is. This is only happening because they are migrating from the twitch launcher to the curse forge launcher. The mods them selfs listed are the issue. They are saying I am using “their property” by adding and FTC mods. That has not been an issue in the past.
Edit: I should add that this is not my first modpack I have made. I am aware of the process to create edit and export.
In reply to Iceboundjester8:
I think that this means they are not supporting a mod or it is not on their website still, do you have something or are you using a baseplate of a certain mod I have a feeling that this has something to do with licensing, but i have not seen that error ever before. sorry I meant to send this 30 mins after you posted this message. but I forgot to hit post.
In reply to tigerty9:
Thats fine.
Everything was downloaded throught the curse forge launcher, powered by overwolf not twitch nor the website. The mod/s in question are the FTBUtilities and the FTBLibrary. I highly doubt they are no longer supporting the mod that they helped create if the modpacks they made are still up on their site as well.
EDIT: They specifically said it was the FTB mods and that I did not export them correct. The steps they then gave me were not applicable to the "New" Overworlf powered launcher app.
i made a modpack with FTB utilities and librairy so the mods are defently supported. if you want prove: https://www.curseforge.com/minecraft/modpacks/moincraft (yes description is bad)
In reply to ultrax96:
That’s the thing. I have made modpacks in the past with these said modes and they have been published. The modpack/s, “Down to Roots” had FTB utilities and more that I have made. I exported the modpack the same way I always have. Thank you for supporting this thread. I hope they really fix this issue.
In reply to ashishkumarji:
If you were around before twitch acquired curese, curse was much better with the community. Support got handled. Once twitch got hold of them the made it so when you wanted to make a modpack you had to use their twitch launcher mod tab witch only loaded about 1/4 of the time and if u had an issue it rarely got resolved. That said. With twitch acquiring curse, it’s not a bad thing. There was a lot of good that came from wit. It’s just that thy do not hold the same level of standards for the community as before.
My favorite part about this issue I have with the support team right now is that I was sent to file a support ticket and the actually straight up canceled it after me going again and again sending a new message every view days waiting as to not let it time out and void. In a whole month I received not a single message from anyone’s. Only a bit telling me their would be someone that will get to you within 2-3 business days. 😐it’s was a month later and still no person after being told it would be a few days... I stoped replying. Got tired of waiting and they completely voided the support ticket. Not a fan of the new system. That said that was also while it was in beta. I will try again in a few weeks to get this modpack published as I like to be able to play games I enjoy they way I would like to.
In reply to ashishkumarji:
In reply to ashishkumarji:
ive been making modpacks since 2014. If you weren’t back then prior to twitch acquiring curse, you don’t really have much wiggle room there. If you were playing modpacks around there I fully understand. I’d agree on that end. The twitch launcher is much easier to use than having to create a new folder version of Minecraft with adding a pack of mods into in order to play.
In reply to tigerty9:
When I get the chance I will do this. Thank you for your help. This is more help I received than from the support team...
In reply to Iceboundjester8:
Did you ever figure out the cause of this? I know that this reply is almost a year late, but I found this thread by searching for a similar issue. I had two different versions of the mods listed with this status. I believe that submitting now that I've deleted them will fix the issue. Maybe somebody else sees this that needs it, who knows..
In reply to Iceboundjester8:
To fix this you need to just go into the curse forge app and then add content to the modpack and select these to mods and install them in that way. This will add them to the manifest file instead as a override.
Hope I can help!
TigerTy9,
Discord: tigerty9#0059
My Modpack: Envulgations