Skip to content

Add Tournament Engine#1539

Open
Ape wants to merge 1 commit into
YARC-Official:devfrom
Ape:pr/tournament-engine
Open

Add Tournament Engine#1539
Ape wants to merge 1 commit into
YARC-Official:devfrom
Ape:pr/tournament-engine

Conversation

@Ape

@Ape Ape commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

This commit adds a new Tournament Engine. This has been a long-standing wishlist item for me and many other players. The engine is intented for players who care about competitive precision playing. Unlike any of the existing engines, this one can easily separate high-level players even on songs where they are likely to full combo.

This PR is my take on this feature. I have been play testing this implementation and I think it fits my ideal vision well. I'm open to comments of course!

This engine is not available on vocals since I don't even know what it would do there.

Needs accompanying Core PR YARC-Official/YARG.Core#407.

Details

Star power is disabled

  • In my opinion, star power doesn't really fit high-level competitive play. I mostly care about drums, though. (Maybe guitar players still like SP?)
  • I wanted to have one engine for the leaderboards where nobody has star power since it obviously affects scoring.

Score is based on timing accuracy

  • Hitting the note within +-10ms will give the full points
    • That window exactly corresponds to the middle 5 bars in the current note offsets histogram.
  • Barely registering a hit will give 50% points
  • Anything in between these is scored with a linear interpolation

The scoring percentage is based on the score

  • For competitive play, it's easier to compare the percentages than absolute scores
  • In this mode, the percentage is calculated by dividing the score by the potential maximum score for that song

Multiplier (1x..4x) is unchanged

Some people have called out for removing the multiplier for competitive play, but I think it's still an effective and important way to punish overhits / overstrums.

We could consider limiting the multiplier to go up to 2x only.

In-song accuracy indicator will be implemented separately

We will need some way to visualize the timing accuracy during play, but that's out of scope of this PR and can be done separately.

Implications in practice

For songs that I could previously get around 99.7%, I can get something around 90% in Tournament Engine.

With this engine it's possible to FC with a score like 95%. That's fine. FC remains a motivating achievement.

Related discussion

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 this pull request may close these issues.

1 participant