Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

classic Ironsworn data in Dataforged-compatible format #47

Open
rsek opened this issue Feb 21, 2022 · 6 comments
Open

classic Ironsworn data in Dataforged-compatible format #47

rsek opened this issue Feb 21, 2022 · 6 comments
Labels
datasworn features specific to ironsworn data

Comments

@rsek
Copy link
Owner

rsek commented Feb 21, 2022

oracle data entry in YAML is basically complete. most of the additional work involved is making will be making sure next can accomodate all ironsworn content gracefully.

@rsek
Copy link
Owner Author

rsek commented Apr 16, 2022

this is at least 75% done at present. most of the work so far has been revising the SelectInput object to accomodate a single Ironsworn asset, Masked (which sets a stat and a condition meter with the same option). it'll make that object more flexible, at least. this means some breaking changes, but that's less of a big deal now that it's packaged in node.

@rsek
Copy link
Owner Author

rsek commented Apr 30, 2022

much of the structure is done... for items that exist in both games, anyways. doing the data entry/revision to bring moves/assets to parity w/ starforged isn't complete -- might be a couple weeks before i can tolerate doing that again, ha

once that's complete, i'll need to revise some of the other datasworn content to match some of the conventions dataforged uses.

@rsek rsek added the datasworn features specific to ironsworn data label May 6, 2022
@ben
Copy link
Contributor

ben commented May 8, 2022

I've found an issue with this: there are two moves with "$id": "Ironsworn/Moves/Delve/Reveal_a_Danger". One of them is a Delve alternate, so it seems like it would be easy enough to just add _alt to the end of the ID.

Once that's fixed, I can merge ben/foundry-ironsworn#345, which will improve the Foundry UI by a leap.

EDIT: one more issue is that the outcomes aren't structured the way Starforged moves are, which I guess I'll also need before I can adopt these wholeheartedly.

@rsek
Copy link
Owner Author

rsek commented May 8, 2022

thanks, it's handy to have the necessary bugfixes in with the rest of the todo! 👍

I've found an issue with this: there are two moves with "$id": "Ironsworn/Moves/Delve/Reveal_a_Danger". One of them is a Delve alternate, so it seems like it would be easy enough to just add _alt to the end of the ID.

i could swear i added something to fix this, but evidently it's missing... or i just plain forgot to rebuild the IS json. ill take a look when i get home, should be pretty quick fix.

complete move outcomes might be a bit longer since that requires more human decision making. can prob automate a good chunk of it though. 🤔

@rsek
Copy link
Owner Author

rsek commented Aug 17, 2022

a draft of outcomes for all standard moves is included in 1.5.0 8cea237

@rsek
Copy link
Owner Author

rsek commented Sep 27, 2022

most recent snapshot of ironsworn data, 2.0 compatible
https://github.com/rsek/dataforged/tree/3b1495601174f6176c91d17dca57863032b1026e/dist/ironsworn

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
datasworn features specific to ironsworn data
Projects
None yet
Development

No branches or pull requests

2 participants