diff --git a/HitScoreVisualizer/changelog.md b/HitScoreVisualizer/changelog.md
index 996411f..385bfe0 100644
--- a/HitScoreVisualizer/changelog.md
+++ b/HitScoreVisualizer/changelog.md
@@ -1,5 +1,19 @@
 ## Changelog
 
+### 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
+```json
+"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
+```json
+"judgments": [
+    { "threshold": 115, "text": "%d%n%s", "color": [1, 1, 1, 1] },
+]
+```
+
 ### 3.4.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
diff --git a/HitScoreVisualizer/manifest.json b/HitScoreVisualizer/manifest.json
index 45ed472..b0ced70 100644
--- a/HitScoreVisualizer/manifest.json
+++ b/HitScoreVisualizer/manifest.json
@@ -4,8 +4,8 @@
 	"name": "HitScoreVisualizer",
 	"description": "Visualizes the scores of your hits! Overly complex config options! Numbers? All the pros use it, except the ones who don't. (But they should.)",
 	"author": "Eris",
-	"gameVersion": "1.37.5",
-	"version": "3.4.3",
+	"gameVersion": "1.38.0",
+	"version": "3.5.0",
 	"dependsOn": {
 		"BSIPA": "^4.3.5",
 		"BeatSaberMarkupLanguage": "^1.12.0",