Skip to content

cnmts.json missing DLC linkage for title IDs that exist in regional title files #19

@reloxx13

Description

@reloxx13

Hi,

I found an inconsistency in the current titledb data.

For this title:

  • Base title ID: 0100FA301CFA2000
  • Name in US.en.json: Farm Together 2

The regional title file contains DLC title records, for example:

  • 0100FA301CFA3001 Farm Together 2 - Explorer Pack
  • 0100FA301CFA3002 Farm Together 2 - Meadow Pack
  • 0100FA301CFA3003 Farm Together 2 - Gothic Pack

However, cnmts.json does not contain matching DLC CNMT linkage for this base title:

  • no titleType = 130 rows linked to 0100FA301CFA2000
  • no DLC otherApplicationId = 0100FA301CFA2000
  • only update linkage appears present

This causes consumers that rely on cnmts.json for base/update/DLC relationships to miss DLCs that are clearly present in the regional title metadata.

Expected:

  • DLC entries present in regional title files should also have corresponding CNMT linkage in cnmts.json when applicable
  • the DLC app IDs above should be linked back to base title 0100FA301CFA2000

Observed:

  • DLC names exist in US.en.json
  • DLC linkage is missing in cnmts.json

I reproduced this from a fresh clone of blawar/titledb, so this does not appear to be a downstream packaging issue.

Thanks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions