Closed Protected closed 2 years ago
What does that do exactly? If it sends out data of the previously cut notes, I decided to not add that to live data as it would then be sending too much data. What I could do is store that in the map data that only gets sent periodically.
It would independently deliver information for each note when it's spawned, cut, or missed (including bombs). That's 2 events per note, one at the moment of spawning and one at the moment of cutting or missing.
You can do this with just two events per note: https://www.twitch.tv/videos/1486707220?t=00h17m38s
I would deliver these separately from other live updates, of course. You could even make them optional - just add a toggle to turn them on when they are wanted (with the tradeoff that you need a good enough CPU, I guess).
This is how the data was structured in BeatSaberHTTPStatus (which is no longer to be updated): https://github.com/opl-/beatsaber-http-status/blob/master/protocol.md#note-cut-object
I understand the old noteFullyCut event no longer makes sense in 1.20+ scoring, but that's fine - it's not important.
I'd like to update the Note History overlay from HTTP Status for 1.18 to use DataPuller for 1.22+ .