HitScoreVisualizer 3.3.0

📝 What's changed

• Updated for BS 1.19.0
• Migrated to SiraUtil 3
• Minor code cleanup
• Some more unnoticeable internal QoL and build pipeline changes

HitScoreVisualizer 3.2.1

📝 What's changed

• Updated for BS 1.18.0
• Reworked internal transpiler
• Added forced config re-validation after config migration
• Some more unnoticeable internal QoL changes

ℹ️ Notice

Last update introduced some changes to the HSV config format. Migrated configs won't work on the Quest version of HSV anymore until the config changes have been adopted. Older Quest HSV configs can still be loaded (and migrated) by the PCVR HSV version though.

HitScoreVisualizer 3.2.0

📝 What's changed

• Updated for BS 1.17.1
• Config changes:
  • Configuration file change regarding FixedPosition serialization. The separate X, Y and Z properties have been merged into a single property.
  • UseFixedPos property got removed. This will now be assumed based on whether the FixedPosition isn't filled in or not.
  • Added new property TargetPositionOffset (basically allows you to offset the target position of the hitscore fade animation).
    Remark: FixedPosition takes priority over this one (as described in documentation)
  • Added support for %t, %% and %n formatting tokens in TimeDependencyJudgements (Thank you @incertia)
• Toggle added for HitScore bloom effect. The bloom effect got removed from the basegame hitscores in the 1.13.4 update, but it's back now. (Thank you @Exomanz)
• Fixed and extended migration logic after being semi-broken for almost year... seems like it wasn't too bad as nobody had reported it during that period of time
• Removed SaveOnMigration toggle. Configs are now automagically backed up and saved when migration is required.
• Bumped dependency versions
• Some more unnoticeable internal QoL changes

ℹ️ Notice

Given that the HSV config format changed a bit this time around. Migrated configs won't work on the Quest version of HSV anymore until the config changes have been adopted. Older Quest HSV configs can still be loaded (and migrated) by the PCVR HSV version.

HitScoreVisualizer 3.1.1

What's changed

• Updated for BS 1.16.3
• Bumped dependency versions
• Compatibility with BSIPA 4.2.0
• Some other minor changes

HitScoreVisualizer 3.1.0

What's changed

• Updated for BS 1.16.1
• Bumped dependency versions
• Removed the underline when an HSV config is being used. (still visible when no config is in use)
• Now assumes perfect post-swing in the initial score calculation (thanks @kirhgoph for contributing this)
• Some other minor changes

Remarks

The assumed perfect post-swing in the initial calculation may result in your scores slightly decreasing while the score calculation is being finalized. In previous versions, the score could possibly increase during finalization.
This change isn't configurable (yet?), but I believe this one is at least better than assuming that you will get a 0 points for the post-swing. 😅

HitScoreVisualizer 3.0.9

What's changed

• Updated for BS 1.13.5
• Bumped dependency versions
• Reworked like half of the internals

Remarks

Make sure that you have at least version 4.1.6 of BSIPA installed

HitScoreVisualizer 3.0.7

What's changed

• Updated for BS 1.13.2
• Bumped dependency versions
• Some smaller internal changes