-
Notifications
You must be signed in to change notification settings - Fork 33
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
note glitch #848
Comments
Tested this and it didnt happen to me |
this isnt really something i can easily fix, i could fix it but then if you used a 3d noteskin and then changed the char back to bf then it would look weird |
probably because you're using an older version of JS engine and you need to upgrade to the newest |
im using the latest commit. |
ironic |
true |
Describe your bug here. If you are modding, try testing your bug in a clean version of the engine instead. Also, if you're using an older version of JSE, please try the latest version/action build. Also, be sure to check the pinned 'JS Engine: Known Issues' issue, to check if your issue hasn't already been found!
the opponent change event glitches the note skin and turns it back to normal (this was tested in the most recent version so please don't yell at Me and say that it's outdated)
Command Prompt/Terminal/Crash logs (if existing)
none
Have you identified any steps to reproduce the bug? If so, please describe them below in as much detail as possible. Use images if possible.
simply change the note skin in the chart editor and use the change opponent event
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
no source code was edited
If you use 1.12.0 or earlier, did you have Optimized Chart Loading turned on?
None
Did you check for any similar issues to what you're reporting? Check, then come back here. If there is a similar issue, then do not report the issue, otherwise it will be marked as a duplicate.
Yes
The text was updated successfully, but these errors were encountered: