Skip to content

incorrect data extracted for quests #4

Description

@GurgumXIV

I haven't had a chance to look into this, but there is a discrepancy between the quest data before and after 7.4. This appears to be a column offset issue, as you can see that values in the 7.35 data are now appearing in the subsequent fields.:

# 7.35 data
jq '.[] | select(.RowId == 70862)' json/7.35/en/Quest/*.json | grep -A 5 -B 5 ClassJobCategory
  "SortKey": 150,
  "Expansion": {
    "RowId": 5,
    "SheetName": "ExVersion"
  },
  "ClassJobCategory0": {
    "RowId": 142,
    "SheetName": "ClassJobCategory"
  },
  "QuestLevelOffset": 0,
  "ClassJobCategory1": {
    "RowId": 0,
    "SheetName": "ClassJobCategory"
  },

# Latest
jq '.[] | select(.RowId == 70862)' json/latest/en/Quest/*.json | grep -A 5 -B 5 ClassJobCategory
  "SortKey": 4504,
  "Expansion": {
    "RowId": 150,
    "SheetName": "ExVersion"
  },
  "ClassJobCategory0": {
    "RowId": 5,
    "SheetName": "ClassJobCategory"
  },
  "QuestLevelOffset": 142,
  "ClassJobCategory1": null,

The correct data appears on https://exd.camora.dev/sheet/Quest:
Image

I'll be looking into this more, but wanted to give this issue some visibility in case it reflects wider issues with the extracted data. (Note also that Lumina.Excel 7.4.1 is out. I don't think it's related to this, but probably best to test with the latest schema version.)

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