Version 3.5.2

Tested on Beat Saber 1.39.1

3.5.2

• Fixed bloom font causing black screen when Enhancements was not installed

3.5.1

• Added a setting to allow hit score text to be shown while "No Texts and Huds" is enabled
• Fixed bloom font showing over notes and environment objects
• Fixed "assumeMaxPostSwing" not adding the full post swing score to the total score, which was causing lower judgment thresholds to be used
• Moved settings to the left screen and tweaked some interface elements' scale

Version 3.5.0

• Added a toggle in configs that will decide, when the note is first cut, if the score display will show the max possible after cut score

"assumeMaxPostSwing": true

Note: it is recommended to set doIntermediateUpdates to false in order for this to be noticeable. This setting is generally only useful if you're swinging extremely slow, like on "poodle" maps, for instance.

• Added the %d token which, when used in format display mode, will be replaced with an arrow that points in the direction relative to the cut line towards the center line of the note

"judgments": [
    { "threshold": 0, "text": "%d%n%s", "color": [1, 1, 1, 1] },
]

Version 3.4.3

• Updated for Beat Saber 1.37.4

Full Changelog: 3.4.0...3.4.3

Version 3.4.0

For Beat Saber v1.37.0

• Added a button to toggle score effect's italics
• Added judgments for chain head notes. These work the way that normal judgments work but are only applied when a chain is cut. Example below

"chainHeadJudgments":[
  { "threshold": 85, "text": "<size=250%><b>•", "color": [1, 1, 1, 1] },
  { "threshold": 78, "text": "<size=120%>%B%c", "color": [1, 1, 1, 1] },
  { "threshold": 0, "text": "<size=120%><alpha=#88>%B%c", "color": [1, 1, 1, 1] }
]

• Added configuration of chain segment (aka. chain links) display. Example below

"chainLinkDisplay": {
  "text": "<alpha=#66>%s",
  "color": [1, 1, 1, 1]
}

• The mod will now only attempt to load .json files in the configs folder
• Some minor optimizations

Full Changelog: 3.3.8...3.4.0

HitScoreVisualizer 3.3.3

⚠️ Important info

Works up to Beat Saber v1.29.1

This is mainly a stopgap, and thus a pre-release version. (I was told to mark it as the latest stable release anyways)
HSV currently doesn't support burst sliders yet and will thus fallback to the default game behavior for those.
Support for them is still in the works and will be released in an upcoming version.

📝 What's changed

• Updated for BS 1.20.0 and 1.21.0. Thanks @Hei5enberg44 for helping out.
• Bumped dependency versions

HitScoreVisualizer 3.3.2

⚠️ Quickfix in 3.3.1 actually broke config switching at runtime, should be properly fixed now.

📝 What was changed in 3.3.1

• Quickfix for crash when trying the tutorial

📝 What was changed in 3.3.0

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

HitScoreVisualizer 3.3.1

⚠️ Quickfix for crash when trying the tutorial

📝 What was changed in 3.3.0

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

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.