-
Notifications
You must be signed in to change notification settings - Fork 32
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
Help me!!! #761
Comments
are you using like this: doTweenY('smth', 'sprite.y', smth, smth, 'smth')
^^
remove that |
thats a stage json issue |
dont worry, i had this issue before |
i think at least |
hello?? |
If i remove the script.lua then it works. |
This is not a stage problem |
function onUpdate(elapsed) local angleshit = 2;
end |
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!
What is this problem???
Every time i load my song with modchart this error disappears.
If i delete modchart the it works.
Command Prompt/Terminal/Crash logs (if existing)
Uncaught Error: The property "y" is not numeric.
flixel/tweens/misc/VarTween.setStartValues() [line 103]
flixel/tweens/misc/VarTween.update() [line 55]
flixel/tweens/FlxTween.update() [line 1263]
flixel/FlxGame.update() [line 747]
flixel/FlxGame.step() [line 679]
flixel/FlxGame.onEnterFrame() [line 558]
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.
No response
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
If you use 1.12.0 or earlier, did you have Optimized Chart Loading turned on?
No
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: