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

[BUG] Conditions between Token and PC Sheet are not synchronized #56

Closed
r-valyar opened this issue Aug 27, 2023 · 3 comments
Closed

[BUG] Conditions between Token and PC Sheet are not synchronized #56

r-valyar opened this issue Aug 27, 2023 · 3 comments
Assignees

Comments

@r-valyar
Copy link

There is no synchronization between the conditions on Token and Sheets, resulting in double maintenance during token heavy play.

The desired functionality is to have condition appear both on token (if placed) and sheet simultaneously, no matter from where the condition is assigned- via token interface or sheet.

@DrOgres DrOgres self-assigned this Aug 30, 2023
@Tarubain
Copy link
Contributor

Tarubain commented Sep 1, 2023

+1 Yes. Tried do get this working with Monks Combat Utilities, but in VAESEN the token status are heavily modified, so the plugin causes errors. Would be great if the system will handle this. :)

Addition: Would be also great if the slow and fast action status would synchronize that other players will know if you still have your fast action left in this round.

@DrOgres
Copy link
Member

DrOgres commented Sep 2, 2023

Addition: Would be also great if the slow and fast action status would synchronize that other players will know if you still have your fast action left in this round.

For tracking of that sort of thing I would say your best bet is to use the YZE Combat Module that's one of the things we built into that, I don't anticipate coding it into the system separately

The effects were coded in before foundry had a decent way to interact with them directly and is on my list to address at some stage. thanks for the feedback!

@DrOgres
Copy link
Member

DrOgres commented Nov 13, 2023

Implemented in v4.0.0 upcoming release this week

@DrOgres DrOgres closed this as completed Nov 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants