-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
Comments
this is at least 75% done at present. most of the work so far has been revising the |
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. |
I've found an issue with this: there are two moves with 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. |
thanks, it's handy to have the necessary bugfixes in with the rest of the todo! 👍
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. 🤔 |
a draft of outcomes for all standard moves is included in 1.5.0 8cea237 |
most recent snapshot of ironsworn data, 2.0 compatible |
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.The text was updated successfully, but these errors were encountered: