Your mod currently is only marked to be compatible with Forge in the Curseforge metadata.

This should probably be changed, to allow applications to correctly handle this mod.

Hi there,
Thanks for alerting me to this. I am however a little confused - I have done nothing that would categorise PlayerEx as Forge only.

The way I understand it, Curseforge puts mods in the Forge and/or Fabric sections via modloader tags attached to the actual mod files when uploaded. Since June, all uploaded files have only been for Fabric and have only had the Fabric modloader tag attached to them. Before then the mod was for Forge. This is why PlayerEx shows up in both Forge and Fabric searches.

That said, I am not aware of any options or configs that mark the entire project as Forge or Fabric, I thought it was only the tags attached to the project files that defined what loader the project supported?

I'd be happy to make whatever changes need to be made for my mod to show up correctly for #25, but I would request some instruction on this as I don't know how to change the project's Curseforge metadata.

Thanks.

Hey, thanks for your help!

Interesting, your are right with the fact that there is no config option for this, but this just raises the question to me: Why is it only your mod that does not have the autogenerated Fabric flag?

As the official documentation for the Curseforge API is not out yet, I don't really know how this modLoaders array is generated, I am probably better off ignoring it in the future to support cases like yours.

If this bothers you anyways, is it maybe a possibility for you to conctact the Curseforge support?

I think I may indeed contact support about it. I would be curious to see if the same modLoaders array is present for other previously-Forge-now-Fabric mods; perhaps it is a relic of mods that were published before Curseforge added support to Fabric?.

Hi,
The modLoaders field is part of the old (undocumented) CurseForge API - the new one (https://docs.curseforge.com) should be used.

It is now fixed on the old API as well, but still, pacmc should use the new API as the old one will be deprecated soon

Excellent, thank you for your help.