tarkovdata

The repository provides several JSON files containing different categories of game data:

• quests.json: Quest data, including requirements, unlocks, and objectives.
• hideout.json: Hideout data, including station information and requirements.
• items.en.json: Item names in English (short and long) with BSG UIDs.
• traders.json: Trader metadata.
• maps.json: Map metadata.
• item_presets.json: Weapon preset configurations.
• ammunition.json: Ammunition metadata.

A CLI tool is provided for data management and integrity checks. It requires node and npm to be installed. You can use it to verify data integrity or generate new IDs for quests and hideout components.

To see all available commands, run:

npm cli.js help

Common commands include:

• node cli.js verify-quest-data: Checks quest data for mistakes.
• node cli.js verify-hideout-data: Checks hideout data for mistakes.
• node cli.js new-quest-id: Finds the next consecutive quest ID for new quests.
• Similar commands exist for hideout and objectives.

The rotate-interchange-map command fixes GPS coordinate orientation for Interchange map objectives. It iterates through quests.json and, for objectives where location == 4, swaps the topPercent and leftPercent values within the gps object.

node cli.js rotate-interchange-map

Use the verify-hideout-data command to scan hideout.json and hideout.js for common data integrity issues. This command checks for:

• Duplicate hideout module IDs
• Missing hideout module IDs
• Duplicate hideout objective IDs
• Missing hideout objective IDs

node cli.js verify-hideout-data

The check-collector command validates the requirements for the Collector quest (ID 195). It ensures that the require.quests array for the Collector quest correctly contains only the 'leaf node' quests (quests that are not required by any other quest except the Collector).

node cli.js check-collector

The link-quests command converts quest references within quests.json from human-readable titles to their specific numeric IDs. It processes references found in:

• require.quests (including 'one-of' arrays)
• require.fail
• alternatives

This ensures that quest dependencies are linked via stable IDs rather than volatile titles.

node cli.js link-quests

The find-quests command tests an array of quest names (provided via testdata.json) against the existing quest data in quests.json to identify any names that do not match an existing quest title.

node cli.js find-quests

The migrate-hideout-items command attempts to convert hideout module requirements from item names to their corresponding unique IDs. It uses hideout.json as the source and items.en.json as the lookup dictionary. If an item name in a hideout requirement matches a name in the item dictionary, the name is replaced by the item's id.

node cli.js migrate-hideout-items

Use the verify-quest-data command to scan quests.json for common data integrity issues. This command checks for:

• Duplicate quest IDs
• Missing quest IDs (gaps in the ID sequence)
• Duplicate quest titles
• Duplicate objective IDs
• Missing objective IDs
• Quests missing a giver property
• Quests missing a require property
• Undefined quest requirements (where a required quest ID does not exist in the dataset)

node cli.js verify-quest-data

These commands help maintain sequential ID numbering when adding new content to the dataset.

• new-quest-id: Returns the next available integer ID for a new quest in quests.json.
• new-objective-id: Returns the next available integer ID for a new quest objective in quests.json.
• new-hideout-id: Returns the next available integer ID for a new hideout module in hideout.json.
• new-hideout-objective-id: Returns the next available integer ID for a new hideout module objective in hideout.json.

node cli.js new-quest-id
node cli.js new-objective-id