Thanks for the detailed report and screenshots.
It’s possible that this issue might occur if the content was packaged and uploaded manually from a local build instead of directly through the Modkit.
To help us look into it further, could you please share the detailed steps you followed when uploading the mod?
For example, did you upload it directly via the Modkit, or did you first package it locally and then upload it manually?
Your information will help us better understand what’s happening — thanks in advance!
All my MODs are first successfully published on CurseForge, and then downloaded from the platform for use. Every MOD I use is a downloaded version, not a local file. Local files are removed from the folder after testing. The 1-2 day gap between publishing to CurseForge and publishing to Canvas exists specifically for this reason—I always wait until the MOD is approved and can be downloaded perfectly before releasing it to Canvas. Therefore, the issue you mentioned does not exist in my workflow.
All my MODs are first successfully published on CurseForge, and then downloaded from the platform for use. Every MOD I use is a downloaded version, not a local file. Local files are removed from the folder after testing. The 1-2 day gap between publishing to CurseForge and publishing to Canvas exists specifically for this reason—I always wait until the MOD is approved and can be downloaded perfectly before releasing it to Canvas. Therefore, the issue you mentioned does not exist in my workflow.
If the system does not automatically display the MODs included in this preset, providing a manual configuration option would be an acceptable solution.