Skip to content
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

Bug Report: Game Over Crashes #2214

Closed
2 of 8 tasks
hifishlol opened this issue May 1, 2024 · 3 comments
Closed
2 of 8 tasks

Bug Report: Game Over Crashes #2214

hifishlol opened this issue May 1, 2024 · 3 comments
Labels
status: resolved The issue has been fixed or the suggestion has been implemented. type: minor bug Involves a minor bug or issue.
Milestone

Comments

@hifishlol
Copy link

hifishlol commented May 1, 2024

Please check for duplicates or similar issues, as well performing simple troubleshooting steps (such as clearing cookies, clearing AppData, trying another browser) before submitting an issue.

If you are playing the game in a browser, what site are you playing it from?

If you are playing the game in a browser, what browser are you using?

  • Google Chrome (or chomium based like Brave, vivaldi, MS Edge)
  • Firefox
  • Safari

What version of the game are you using? Look in the bottom left corner of the main menu. (ex: 0.2.7, 0.2.1, shit like that)

0.3.0 prototype

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.

2 ways to crash in gameover:

  1. die before countdown is done
  2. trigger stickersubstate whilst transitioning to playstate, (enter, then esc before the playstate transition happens)

Please describe your issue. Provide extensive detail and images if possible.

the game. crashes!!!! lol

If you're game is FROZEN and you're playing a web version, press F12 to open up browser dev window, and go to console, and copy-paste whatever red error you're getting

@hifishlol hifishlol added the type: minor bug Involves a minor bug or issue. label May 1, 2024
@SilverT4
Copy link

SilverT4 commented May 1, 2024

Running the game from a command prompt (PowerShell or cmd) can be helpful for bug reports on Windows, at least imo. I attempted to recreate both of the methods you mentioned, and got these errors in the console window:

For resetting before song start:

Called from funkin.play.PlayState.update (funkin/play/PlayState.hx line 1013)
Called from flixel.FlxState.tryUpdate (flixel/FlxState.hx line 223)
Called from flixel.FlxGame.update (flixel/FlxGame.hx line 750)
Called from flixel.FlxGame.step (flixel/FlxGame.hx line 680)
Called from flixel.FlxGame.onEnterFrame (flixel/FlxGame.hx line 559)
Called from openfl.events.EventDispatcher.__dispatchEvent (openfl/events/EventDispatcher.hx line 402)
Called from openfl.display.DisplayObject.__dispatch (openfl/display/DisplayObject.hx line 1399)
Null Object Reference
Called from openfl.display.DisplayObject::__dispatch openfl/display/DisplayObject.hx line 1399
Called from openfl.events.EventDispatcher::__dispatchEvent openfl/events/EventDispatcher.hx line 402
Called from flixel.FlxGame::onEnterFrame flixel/FlxGame.hx line 559
Called from flixel.FlxGame::step flixel/FlxGame.hx line 680
Called from flixel.FlxGame::update flixel/FlxGame.hx line 750
Called from flixel.FlxState::tryUpdate flixel/FlxState.hx line 223
Called from funkin.play.PlayState::update funkin/play/PlayState.hx line 1013

For the StickerSubState one, I got this:

Called from funkin.ui.transition.StickerSubState.regenStickers (funkin/ui/transition/StickerSubState.hx line 241)
Called from flixel.util.FlxTimer.onLoopFinished (flixel/util/FlxTimer.hx line 205)
Called from flixel.util.FlxTimerManager.update (flixel/util/FlxTimer.hx line 295)
Called from flixel.FlxGame.update (flixel/FlxGame.hx line 748)
Called from flixel.FlxGame.step (flixel/FlxGame.hx line 680)
Called from flixel.FlxGame.onEnterFrame (flixel/FlxGame.hx line 559)
Called from openfl.events.EventDispatcher.__dispatchEvent (openfl/events/EventDispatcher.hx line 402)
Called from openfl.display.DisplayObject.__dispatch (openfl/display/DisplayObject.hx line 1399)
Null Object Reference
Called from openfl.display.DisplayObject::__dispatch openfl/display/DisplayObject.hx line 1399
Called from openfl.events.EventDispatcher::__dispatchEvent openfl/events/EventDispatcher.hx line 402
Called from flixel.FlxGame::onEnterFrame flixel/FlxGame.hx line 559
Called from flixel.FlxGame::step flixel/FlxGame.hx line 680
Called from flixel.FlxGame::update flixel/FlxGame.hx line 748
Called from flixel.util.FlxTimerManager::update flixel/util/FlxTimer.hx line 295
Called from flixel.util.FlxTimer::onLoopFinished flixel/util/FlxTimer.hx line 205
Called from funkin.ui.transition.StickerSubState::regenStickers funkin/ui/transition/StickerSubState.hx line 241

The 0.3.0 version of the game is a prototype, so not everything will work as expected. I imagine these problems may end up fixed in the next version released.

@Hundrec
Copy link
Collaborator

Hundrec commented Oct 3, 2024

I tried to replicate these crashes in 0.5.1, and fortunately couldn't.
We can probably close this one now!

@EliteMasterEric EliteMasterEric added the status: resolved The issue has been fixed or the suggestion has been implemented. label Oct 15, 2024
@EliteMasterEric EliteMasterEric added this to the 0.5.1 milestone Oct 15, 2024
@AbnormalPoof
Copy link
Collaborator

Shouldn't this be closed if it was resolved?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: resolved The issue has been fixed or the suggestion has been implemented. type: minor bug Involves a minor bug or issue.
Projects
None yet
Development

No branches or pull requests

5 participants