-
Notifications
You must be signed in to change notification settings - Fork 11
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
Moves Not Clickable or Expanding? #7
Comments
Are you on the appropriate build of Foundry? I think the highest supported version is 0.8.8. If you are running a newer version, there are inconsistencies (such as what you're reporting). |
Then it's a me problem. 🤣 Sorry I thought it was compatible with v9 based on the version notes. My bad. |
Sorry I meant compatibility notes on the fvtt page. |
I am not experiencing this issue, however, there are some newer issues that are surfacing due to some changes in the original raw data that the moves are derived from. As a manual fix, you could try importing all the Starforged Moves from the compendium. Right-click on Starforged Moves --> Import All Content. This presumes that your Starforged Moves has all the moves in there. You will likely need to create a new character for them to be automatically added to the character sheet. |
There should be a . between v and 0. https://raw.githubusercontent.com/DiceT/starforged/v.0.8.0/system.json |
Cheers! I wonder why that error comes up when I try use the official foundry system menu to install it? Is it just me getting this then? |
No, it's not just you, I get the same zip not found error, even when using the https://raw.githubusercontent.com/DiceT/starforged/v.0.8.0/system.json URL. |
The URL is fixed in 0.8.1 It's going to take some work to get the Moves updated, as in a full rewrite of the data importer, as Dataforged has significantly changed. |
Is this just a me problem or are others experiencing it? On the character sheet, when I click the moves tab, no moves are clickable or expand as per the YT video. Any ideas?
The text was updated successfully, but these errors were encountered: