Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Update for Beat Saber 1.12.1

See original GitHub issue

New version of the game has been released.

There’s an untested version of this mod for v1.12.1 on the update/1.12.1 branch. Currently any further work and testing is blocked by BS_Utils.Plugin.LevelData.GameplayCoreSceneSetupData returning null. https://github.com/opl-/beatsaber-http-status/tree/update/1.12.1

Issue Analytics

State:
Created 3 years ago
Comments:9 (4 by maintainers)

Top GitHub Comments

8reactions

opl-commented, Nov 5, 2020

Seems Kyle removed the Gamemode.GameMode in favor of just accessing data on LevelData in this commit https://github.com/Kylemc1413/Beat-Saber-Utils/commit/a2ccce30ba453c16cb7a1065979a9767d4e18491 which, as far as I can tell, was released in v1.6.0. I was testing on an early, unreleased version of the plugin that hasn’t yet changed that, hence the errors.

The property can now be accessed using this fun, easy to remember snippet: BS_Utils.Plugin.LevelData.GameplayCoreSceneSetupData.difficultyBeatmap.parentDifficultyBeatmapSet.beatmapCharacteristic.serializedName.

I pushed this change to the branch in 7d96af9. Below is a development build that I only tested in standard solo and in multiplayer (I believe spectating hasn’t yet been tested properly). No guarantees that things won’t break. If they do, feel free to report back here.

BeatSaberHTTPStatus-1.11.3-dev-bs1.12.1-7d96af9c.zip

1reaction

opl-commented, Jan 1, 2021

I can finally close this one. You can download v1.12.0 from the releases page. It will appear on Beat Mods (and in mod managers) when it gets approved.

If you find any bugs, please open a new issue.

(All the debug logging was left in totally on purpose and not because I completely forgot about it. I’m sure it will be useful diagnostic information for when things inevitably turn out to be broken in some way.)

@tehbiga I’m not sure what you mean. The version you changed it to is the deprecated one, which I’m specifically not using. Unless the websocket-sharp version on BeatMods is awfully outdated (which I doubt) or you somehow ended up with an outdated version from git, it should work just fine as is. (Edit: Perhaps you got websocket-sharp from nuget? The version there hasn’t been updated since 2016.)

@rynan4818 Thanks for pointing those issues out. Both should be fixed.