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

🐞 Pathfinder initiative resolution for ties is incorrect #294

Open
3 of 7 tasks
scooper4711 opened this issue Jul 30, 2024 · 2 comments · May be fixed by #295
Open
3 of 7 tasks

🐞 Pathfinder initiative resolution for ties is incorrect #294

scooper4711 opened this issue Jul 30, 2024 · 2 comments · May be fixed by #295

Comments

@scooper4711
Copy link

Check for existing bug reports before submitting.

  • I searched for existing Bug Reports and found no similar reports.

Expected Behavior

With the pathfinder rules, if the player and GM tie for initiative, the tie is resolved in the GM's favor.

There's actually a feat that a player can take to resolve it in the player's favor. I don't think anyone takes it though, since it's such a corner case.

Current behaviour

ties in initiative appear to be resolved in favor of the player.

Reproduction

  1. start combat.
  2. player's initiatives are set to zero in settings
  3. creature's initiatives are rolled.
  4. update the player's initiative to the same as one of the creature's initiative
  5. Notice that the player jumps up above the creature.

Which Operating Systems are you using?

  • Android
  • iPhone/iPad
  • Linux
  • macOS
  • Windows

Obsidian Version Check

1.6.5 and 1.6.5

Plugin Version

13.0.12

Confirmation

  • I have disabled all other plugins and the issue still persists.

Possible solution

No response

@Trantion897
Copy link

I'm working on a patch to let you set the default result of initiative ties, but in the meantime you can drag & drop creatures to manually reorder everyone who got the same initiative roll.

I was about to create a pull request when I found the drag & drop support, and my patch kinda breaks it a bit. So I need a bit more time to sort that out.

@scooper4711
Copy link
Author

Thanks, I knew about the workaround. I was hoping for a fix since I may not always notice that there's a tie.

Cool that you're working on a patch already! Thanks!

@Trantion897 Trantion897 linked a pull request Aug 9, 2024 that will close this issue
14 tasks
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

Successfully merging a pull request may close this issue.

2 participants