Invalid "env": "unknown" values in modrinth.index.json break modpack installation

[BrammetjeBastiaansen]

Describe the bug
The Create+ modpack (version 6.0.0 Alpha C) contains invalid env values ("unknown") in modrinth.index.json. These values are not part of the Modrinth specification (required, optional, unsupported) and cause strict parsers (such as the one used by the itzg/minecraft-server Docker image) to fail when reading the modpack.

As a result, the modpack cannot be installed or started in environments that validate the Modrinth schema strictly.

---

To Reproduce
Steps to reproduce the behavior:

1. Download the Create+ modpack version 6.0.0 Alpha C from Modrinth

2. Use it with a Modrinth-compatible installer (e.g. itzg/minecraft-server with TYPE=MODRINTH)

3. Start the container / installation process

4. Observe failure during modpack parsing with error:

   Cannot deserialize value of type EnvType from String "unknown"
   

---

Expected behavior
The modpack should conform to the Modrinth specification and install successfully.
All env fields in modrinth.index.json should use valid values:

• required
• optional
• unsupported

---

Screenshots
N/A (error logs available below if needed)

---

Version
6.0.0 Alpha C

---

Additional context

• The issue appears in modrinth.index.json where at least one mod (statuseffectbars) has:

  "env": {
    "client": "unknown",
    "server": "unknown"
  }

• This causes the modpack to fail before installation begins, so it cannot be worked around via exclude lists.

• For this specific mod, a correct fix would be:

  "env": {
    "client": "required",
    "server": "unsupported"
  }

• Applying this change allows the modpack to be parsed and installed correctly.

• There may be additional occurrences of "unknown" that should be reviewed.

This currently makes the modpack incompatible with automated/server environments and strict Modrinth tooling.

[StormDragon-64]

Looking through the file, that is the only occurrence of unknown. Also, I don't modify the index manually in any way. This happens because the way the mod itself was uploaded to Modrinth. See Leclowndu93150/Status-Effect-Bars#2.

[BrammetjeBastiaansen]

Ah, that makes sense! Looking at the issue you referenced, the mod is not actively maintained, so I doubt it will be fixed anytime soon, unfortunately.

I have modified the modrinth.index.json locally to get the modpack working on my server with Docker, easy enough temporary fix.

[Leclowndu93150]

it's not actively maintained because there's nothing to fix on it. but yeah i'll fix this. sorry, github has stopped giving me notifications due to the amount of repos i have

[Leclowndu93150]

and also i absolutely despise modrinth, so i do the minimum effort to upload mods there, using a curseforge to modrinth tool i created. i'll fix the env issue on it.