validate against the schema using yarn validate.edit files in campaigns or return_campaigns.sync: copy TypeScript definitions and generated JSON files to your ArkhamCards projectĪ typical workflow for editing the data is :.verify: run various checks on the generated campaigns JSON file.build:return-to: build Return To campaigns by merging Return To modifications with original campaign.build:campaign-logs: build campaign logs JSON file.build:all-campaigns: build campaigns JSON file.build: build JSON files ArkhamCards needs.validate: validate JSON files against the schema (it builds Return To campaigns).definitions: generate TypeScript definitions based on the JSON Schema.
The following scripts are available to build the project using Yarn or NPM : To implement a campaign like experience, you will need to understand and interpret a card repository. ArkhamDBĪll card codes referenced in the schema share the numeric scheme of ArkhamDB.
ARKHAM GITUP FULL
The schema shows some of the state space, but as the Arkham Horror: LCG becomes more complex over time, new control inputs and flows will be needed to capture the full nuance. The complexity comes with the definition of steps. With all input and changes expressed as deltas, it should be possible to capture only the input choices and 'replay' the log to reproduce the final state given the guide. The structure of flow is controlled by 'steps', which are then referenced by the 'setup', 'resolutions' and other 'steps' (to implement conditional control flow). These names are unique to the campaign, but all data should be prefixed with campaign code to make them unique. Scenarios and InterludesĮach scenario/interlude has its own file, referenced by the scenario name. CampaignĬampaign overview info is held in the campaign.json fold, including chaos bag and initial campaign sections. Basic StructureĬampaign data lives primary in the /campaigns folder, structured by three-letter campaign code. Repo for campaign guide data for ArkhamCards app.
0 kommentar(er)
