Skip to content

Resourcepack rejected by client (26.2): missing "supported_formats"/"formats" fields in generated pack.mcmeta on beta-10 #5452

Description

@onurfly

Terms

  • I'm using the very latest BETA version of ItemsAdder and the dependencies are updated.
  • I am sure this is a BETA VERSION ONLY and it's not reproducible on previous public releases of the plugin.
  • I am sure this is a bug and it is not caused by a misconfiguration or by another plugin.
  • I've looked for already existing issues on the Issue Tracker and haven't found any.
  • I already searched on the plugin wiki to know if a solution is already known.
  • I searched the #beta-ia channel on Discord for similar issues.
  • I searched the #itemsadder-forum channel on Discord for similar issues.
  • I tested that this issue persists on a bare-minimum Server as described in #4187.

Discord Username (optional)

noobfly

What happened?

The custom resourcepack that ItemsAdder generates does not load anymore after updating to beta-10. The client rejects it with a JsonParseException about missing "supported_formats" and "formats" fields in pack.mcmeta.

I compared the generated pack.mcmeta between beta-8 and beta-10. On beta-8 the overlays entries always contain a "formats" array (the new schema key required by newer clients) together with the old "min_format"/"max_format" keys. On beta-10 it looks like there is a version check that decides to write ONLY the old "min_format"/"max_format" keys OR only the new "formats"/"supported_formats" keys, not both like before. In my case it picked the old-only path and the pack.mcmeta ends up missing the fields the client needs, so the whole pack gets rejected with "Invalid pack metadata, ignoring all".

Downgrading the plugin jar back to beta-8 (keeping everything else the same, same server, same config) fixes it immediately and the pack loads fine again. So it does not seem related to my configs or contents folder, it happens specifically with the beta-10 build.

Steps to reproduce the issue

  1. Run a server on a recent Minecraft client version that uses a high pack_format (in my case pack_format 87, client version 26.2)
  2. Update ItemsAdder to beta-10
  3. Join the server and let ItemsAdder generate/send the resourcepack
  4. Check client latest.log, you will see JsonParseException lines like:
    "Pack declares support for version newer than 64, but is missing mandatory fields min_format and max_format"
    and for overlays:
    "Overlay missing required field formats, must be present in all overlays for any overlays to work across game versions"
  5. The pack gets fully rejected with "Invalid pack metadata ... ignoring all"
  6. Downgrade the jar to beta-8, restart, the same pack now loads without errors

Server version

Purpur version 26.2-DEV-ver/26.2@5ad64ac (1970-01-01T00:00:00Z) (Implementing API version 26.2.local-SNAPSHOT) - Custom my made Server Fork

ItemsAdder Version

ItemsAdder version 4.0.18-beta-10

ProtocolLib Version

ProtocolLib version 5.5.0-SNAPSHOT-0e267a5

Full Server Log

Client: https://mclo.gs/0CRg0FV Server: https://mclo.gs/nmA5Iq9

Error (optional)

com.google.gson.JsonParseException: Pack declares support for format 32, but game versions supporting formats 17 to 64 require a supported_formats field. Add "supported_formats": [32, 64] or require a version greater or equal to 65.0.

com.google.gson.JsonParseException: Overlay "ia_overlay_1_20_5_plus" missing required field formats, must be present in all overlays for any overlays to work across game versions

com.google.gson.JsonParseException: Pack declares support for version newer than 64, but is missing mandatory fields min_format and max_format

Problematic items yml configuration file (optional)

Other files, you can drag and drop them here to upload. (optional)

No response

Screenshots/Videos (you can drag and drop files or paste links)

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    type: duplicateThis issue or pull request already exists

    Type

    No type

    Projects

    Status
    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions