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

Clawdancer Archetype Lacks Automation #14870

Closed
1 of 6 tasks
Rovoska opened this issue May 27, 2024 · 3 comments
Closed
1 of 6 tasks

Clawdancer Archetype Lacks Automation #14870

Rovoska opened this issue May 27, 2024 · 3 comments
Labels
bug Functionality that is not working as intended

Comments

@Rovoska
Copy link

Rovoska commented May 27, 2024

What happened?

When adding the clawdancer archetype, Foundry does not add the given stances, nor the given attacks by said stances. Both the stance actions and attacks do not appear to exist at all.

What ways of accessing Foundry can you encounter this issue in?

  • Native App (Electron)
  • Chrome
  • Firefox
  • Safari
  • Other

Reproduction Steps

Opening foundry in Firefox, making or remake a character to add the clawdancer archetype, and observe that the system does not add the expected content to the character sheet

What core version are you reporting this for?

Version 11 355

Relevant log output

No response

Bug Checklist

  • The issue occurs while all Modules are disabled
@Rovoska Rovoska added the bug Functionality that is not working as intended label May 27, 2024
@aaclayton
Copy link

Redirecting to the PF2E repo

@aaclayton aaclayton transferred this issue from foundryvtt/foundryvtt May 28, 2024
@DocSchlock
Copy link
Collaborator

Clawdancer automation was added in 5.16.1. Update your system and refresh the Dedication.

@DocSchlock DocSchlock closed this as not planned Won't fix, can't repro, duplicate, stale May 28, 2024
@Roghain
Copy link

Roghain commented Jun 22, 2024

I am having the same issue. I am running Foundry V12 stable Build 327 and PF2E 6.0.4
I have disabled all modules and the issue persists. The advice given above in refreshing doed not change the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Functionality that is not working as intended
Projects
None yet
Development

No branches or pull requests

4 participants