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

broken end of turn sequence behavior #289

Closed
sebertram847 opened this issue Mar 5, 2024 · 7 comments
Closed

broken end of turn sequence behavior #289

sebertram847 opened this issue Mar 5, 2024 · 7 comments
Labels
bug Something isn't working compatibility Compatibility with other modules

Comments

@sebertram847
Copy link

Only loading SWADE Tools mod. Scenario: 2+ actors in the combat tracker, make all (or the right one) Stunned. End the round. One actor (and only ever one) will get 2 free rolls to unshake before cards are dealt. If both rolls succeed, the 2nd one throws an error since the condition was removed by the first. I cannot figure out why this happens.

Further research is that the stunned condition is not the issue, it's only proving that at the end of the turn, one combatant goes through 2 or 3 other turn sequences before the beginning of the next round. Something in combatcontrol.js or start.js?

image

@lipefl lipefl added bug Something isn't working compatibility Compatibility with other modules labels Mar 5, 2024
@lipefl
Copy link
Owner

lipefl commented Mar 5, 2024

It seems like they changed combat a little, it could get fixed by itself in the next system updates, but i'll see what can be done.

@sebertram847
Copy link
Author

sebertram847 commented Mar 5, 2024 via email

@lipefl
Copy link
Owner

lipefl commented Apr 9, 2024

I wasn't able to reproduce it anymore. I think it fixed itself in the system update.

@lipefl lipefl closed this as completed Apr 9, 2024
@sebertram847
Copy link
Author

Actually I can still reproduce it. At the end of the round one character gets 2 tries to unshake before the new round starts. Same as above.

@lipefl
Copy link
Owner

lipefl commented Apr 11, 2024

You're right, i'll look into it. Thanks

@lipefl lipefl reopened this Apr 11, 2024
@lipefl
Copy link
Owner

lipefl commented Apr 12, 2024

It's fixed now in v1.15.1
Thanks again!

@lipefl lipefl closed this as completed Apr 12, 2024
@sebertram847
Copy link
Author

Yep, works great. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working compatibility Compatibility with other modules
Projects
None yet
Development

No branches or pull requests

2 participants