-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chroma making in-game modifers not work #16
Comments
I now completely uninstalled Chroma and its dependencies, and then installed NoodleExtensions (which reinstalls the same dependencies). The same problem still happens where I fail and the blocks have arrows even when No Fail and No Arrows is turned on. I then tried disabling Chroma/NoodleExtensions, but left the dependencies enabled, and the bug still happens. So the bug is probably with one of the 3 dependencies (Paperlog, Tracks, CustomJSONData) rather than Chroma itself. |
I do not experience this bug myself as I have been testing for months with No Fail enabled. |
Thank you for replying so quickly. Have you tried it with the No Arrows enabled? I've even gone as far as completely uninstalling and reinstalling Beat Saber and then re-modding it, and the problem still persists. |
No arrows is deemed a bug, no idea why it doesn't work |
I was told to file an issue here because after I'm having a problem where the default in-game modifiers like No Fail and No Arrow don't work whenever Chroma is installed and active on Beat Saber 1.24.
The only mods I have installed are:
Core Mods
Paperlog
Tracks
CustomJSONData
Chroma
Whenever Chroma is installed and turned on, I still fail and the blocks still have arrows even though the two in-game modifiers are turned on. But when Chroma is disabled, No Fail and No Arrows work properly.
Please fix this bug. Thank you in advance.
The text was updated successfully, but these errors were encountered: